Door Switch 2

FoxLab

Hello I have dedicated myself once again to the topic of door switches now using a simple reed switch. Among other posts, I took a closer look at this post again:
https://duet3d.dozuki.com/Wiki/Using_M581_-_External_Triggers_and_Building_a_Control_Panel

Anyway, I have not really gleaned success.
First, here are the actual global specifications :
Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.1.1 (2020-05-19b2)

In an old door switch setup, with a Duet Maestro, I used a light barrier to switch like this:
M950 J1 C "e0stop"
M581 P1 S0 T1 C1

Now I want to use a reed switch with a 3,3V falling edge over I/O pin 4 "E2_STOP" and connect it to pin 30 against GND. The circuit is tested and does what it should.
Analog to the code shown above I have modified the code as follows without success:
M950 J2 C "e0stop"
M581 P2 S0 T1 C1

Even I have taken a look at Pin Name formate I have also tested different writings without success.

Anyones comment is appreciated.

Phaedrux

@FoxLab said in Door Switch 2:

M581 P2 S0 T1 C1

I think part of the problem may be your C parameter as it's not used in 3.1.1

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

The formatting of the command will vary based on your firmware version.

FoxLab

Thank you for your answer.

I have modified my code as suggested with no positive result. .
It now looks like this:
M950 J2 C"e2stop"
M581 P2 S0 T1 R1

I have cross checked it with my previouse setting for a Photocell using the C parameter and it works when I use the above shown code for e0stop.

Any other ideas?

Phaedrux

@FoxLab said in Door Switch 2:

e2stop

I think you'll need to change the pin name, e2stop doesn't exist in that name. You'd need to use exp.e2stop I think.

https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Pin_names_for_Duet_2_WiFi_Ethernet

FoxLab

Thank you!!!
This solved my issue.

Phaedrux

Sometimes it helps to test changes in the console first before putting them in config.g. This lets you see any error messages that would get missed during startup. Another option is to send M98 P"config.g" which executes config.g as a macro and you can see any error messages then. I'm pretty sure it would have complained about the pin name not existing.

Glad it's sorted out though.