Endstops triggered without anything connected

Eman74

Hi all, I think I found the solution looking into an unrelated post for X an Y issues (wiring follows duet recommendations with all 3 pins connected):

this was my not working config:
; Endstops
M574 X1 S1 ; Set active high endstops
M574 Y2 S1 ; Set active low endstops, Y endstop is high(max).

this is how I suppose I fixed my issue:

; Endstops
M574 X1 S1 P"!xstop" ; Set active high endstops
M574 Y2 S1 P"!xstop" ; Set active low endstops, Y endstop is high(max).

When I check from the web interface I can finally see the endstops not triggered and when I manually trigger them their status change correctly from the web interface.

Now the only thing I'm not sure if it's normal is that the endstop red led is switched on when led are not triggered and of when I trigger them manually, is that normal for cartesian config?
I have another duet with cartesian config and it does exactly the opposite (leds are normally switched off and they lights up only e=when the endstop is triggered), do you guys know if for cartesian configs is an expected behaviour?

fcwilt

@Eman74

You posted that you were running firmware 2.05.1.

The syntax you changed to is for firmware 3.x.

So what firmware are you running?

Frederick

Eman74

@fcwilt said in Endstops triggered without anything connected:

running firmware 2.05.1

I am running running firmware 2.05.1 I have no clue why this is working this way I also managed to home X and Y axis, and I can grant you I double checked I'm on 2.05.1:

Board: Duet WiFi 1.02 or later + DueX5
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05.1 (2020-02-09b1)
Duet WiFi Server Version: 1.23

alankilian

From THIS page:

Each input has a pullup resistor and red LED between the STP pin and +3.3V.

The LED will be illuminated when an endstop switch or other device connected to the input holds the voltage close to 0V (ground).

Whether the LED is illuminated when the endstop switch is triggered or not triggered depends on whether your endstop switch produces and active-high or active-low output:

An endstop switch with an active-high output holds the input pin at about 0V when the switch is not triggered, and about +3.3V when it is triggered. A typical example is a normally-closed microswitch. The LED on the Duet will be illuminated when the switch is connected but not triggered.

An endstop switch with an active-low output holds the input pin at about 3.3V when the switch is not triggered, and about 0V when it is triggered. One example is a normally-open microswitch (which is not recommended, because a normally-closed switch is safer). Another example is a Hall sensor with an open-drain output that is connected directly to the Duet endstop input. The LED on the Duet will be illuminated when the switch is connected and triggered.

Eman74

@alankilian said in Endstops triggered without anything connected:

From THIS page:

Each input has a pullup resistor and red LED between the STP pin and +3.3V.

The LED will be illuminated when an endstop switch or other device connected to the input holds the voltage close to 0V (ground).

Whether the LED is illuminated when the endstop switch is triggered or not triggered depends on whether your endstop switch produces and active-high or active-low output:

An endstop switch with an active-high output holds the input pin at about 0V when the switch is not triggered, and about +3.3V when it is triggered. A typical example is a normally-closed microswitch. The LED on the Duet will be illuminated when the switch is connected but not triggered.

An endstop switch with an active-low output holds the input pin at about 3.3V when the switch is not triggered, and about 0V when it is triggered. One example is a normally-open microswitch (which is not recommended, because a normally-closed switch is safer). Another example is a Hall sensor with an open-drain output that is connected directly to the Duet endstop input. The LED on the Duet will be illuminated when the switch is connected and triggered.

Thank you very much, this resolve my doubts, still not sure why I'm able to use new gcodes on 2.05.1 but may be this option was available before the jump too, I may have simply found an EasterEgg of high value for my config (I'll probably upgrade to latest version later on, I just went for the version I was already familiar with....)

Now it's time to look into triple-z homing with BLTouch... wish me luck!

fcwilt

@Eman74 said in Endstops triggered without anything connected:

I cannot understand how v3 syntax can work on v2 firmware.

If you haven't already done so please execute M98 P"config.g" from the DWC console and let us know if there are any warnings or error messages displayed.

Thanks.

Frederick

Phaedrux

@fcwilt said in Endstops triggered without anything connected:

I cannot understand how v3 syntax can work on v2 firmware.

Well the first half of the M574 command is the same, so it's just ignoring the second half with the pin name.

M574 X1 S1 is the same in RRF2 or RRF3. The only difference for RRF3 is that it adds the pin name P"!xstop"

https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M574_Set_endstop_configuration

fcwilt

@Phaedrux said in Endstops triggered without anything connected:

@fcwilt said in Endstops triggered without anything connected:

I cannot understand how v3 syntax can work on v2 firmware.

Well the first half of the M574 command is the same, so it's just ignoring the second half with the pin name.

M574 X1 S1 is the same in RRF2 or RRF3. The only difference for RRF3 is that it adds the pin name P"!xstop"

https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M574_Set_endstop_configuration

Thanks.

I wrongly assumed that the firmware validated the entire line of code (stopping at comments) to insure that all was correct.

That still doesn't explain why his change worked - his posts suggests he left the "v2" part unchanged.

Frederick

Phaedrux

I'm guessing some combination of wiring and command syntax.

Eman74

@fcwilt said in Endstops triggered without anything connected:

M98 P"config.g"

M98 P"config.g"

HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

this is what I get, anyway I'll soon update to RRF3, my understanding is it's way more powerful and has more development potential

fcwilt

@Eman74 said in Endstops triggered without anything connected:

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

Well there are no warnings or errors so that is good.

'll soon update to RRF3, my understanding is it's way more powerful and has more development potential

Wise choice. For a little bit of effort you will have a much better system.

Frederick

Phaedrux

@Eman74 said in Endstops triggered without anything connected:

I'll soon update to RRF3

If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them. Reboot after each. Use M115 to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip
That will get your firmware and DWC up to date.

You can see the change logs here:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/Start

Backup your existing config files in the sys folder in case you want to switch back to RRF3. IT’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

These documents will come in handy during the conversion.
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
https://duet3d.dozuki.com/Wiki/Gcode