Can't configure End stops

Andy Cohen

@norder yes… if this were a typical machine which has a z end stop switch activated when the bed is drawn up to 0.
This is the E3d Toolchanger. The end stop gcode is from E3d. The end stop switch also acts as the z probe and it is mounted on the coupler carriage.

Norder

@andy-cohen
Sorry I don't have a crystal ball.
You should have written about it right away.
The more information... the easier and faster we can help you.

Google Translate
--- Original Text ---

Sorry das ich keine Glaskugel habe.
Du hättest es gleich dazu schreiben sollen.
Um so mehr Infos... desto einfacher und schneller kann Dir geholfen werden.

Andy Cohen

@norder My first sentence is its a Toolchanger.
I tried ...
M574 Z1 S1
M574 C1 S3

C is the tool coupler and it uses amps from motor stall as well as Y axis for end stop on my machine.
It did not work either.
I also switched out the zhome script with another written by E3D... no difference. It keeps saying the same error. Weird.
I need help from the RRF gods!

Phaedrux

Do you have a Z endstop and a Z probe?
Post your homing files.
When exactly are you getting that error?

Can you send M98 P"config.g" and copy paste the output?

Rushmere3D

My TC config has the same settings but I wonder if the order in which you have it is causing a issue? I.e you have the motor setting etc after the endstop settings?

Andy Cohen

@rushmere3d Yeah... the end stop def was before. I switched it and it still returned the same error.

So next I swapped out the homing scripts from mine to those from the E3D sample files. My older files had M574 commands in them which could easily have fired off the error. Now I get something quite different:
"Error: Probe already triggered at start of probing move"
Which to me indicates it's expecting a closed switch not an open one.

Andy Cohen

@phaedrux On this machine the Z switch is on the tool coupling carriage which rides on the X axis rail. When no tool is on it it acts as the Z end stop and the mesh compensation probe.

I was getting the error right after the first homing move which tells me it was in the homez script. I changed that to the sample E3D script on their website and now I get the message:
"Error: Probe already triggered at start of probing move"

here's the output per your request:
8/28/2022, 11:36:16 AM HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 1 predicted maximum temperature at full power is 496°C
Warning: Heater 2 predicted maximum temperature at full power is 512°C
Warning: Heater 3 predicted maximum temperature at full power is 547°C
Error: Heater 5 not found
Error: Heater 6 not found
Error: Heater 7 not found
8/28/2022, 11:36:15 AM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

Note I have yet to run PID control routines on my heaters.

Andy Cohen

@andy-cohen DOH!!! The "!" in the zstop label! AH!

Thank you to all here who replied to my post I appreciate the help.

Chances are though I'm not ready to print just yet and may have more things like this.

Rushmere3D

@andy-cohen I'm confused you didn't have the ! in the config when you posted, then you added it and you said it made no difference.

So is your original issue fixed?

Rushmere3D

@andy-cohen So it was the homing files and then the ! In the endstop config?

I should have said I have a duet 3 on my TC.

Andy Cohen

@rushmere3d The heart of my problem was that I simply edited the S labels to H in all my Homing scripts. Bad idea. I should have simply swapped out the old files for e3d’s new homing files. My old files used the M574 command which reset the end stops incorrectly for the update. I have no idea why the m574 command was in the original homing scripts…

The second problem was because I had not read the ALL of the docs on the pin out labels. As such I had assumed the exclamation mark was on all pinout names. I went back and ready the whole thing and found the ! Sets the polarity of the connections.

Heaters all tuned. Almost ready to print. Again thanks to all for the help.
And… yeah I’ll talk about the update in the 3d Printing Today podcast.