Problem on io7.in
-
@Tinchus ahh right, I misread what you said previously, i thought it was detecting the plug/unplug event. Which board is it?
-
@T3P3Tony it is a duet3, version 1.01
-
@T3P3Tony have a surprise jajajaja. Since I dont know what to measure on the board to check if the pin is faulty or not, I tried on another board, this one is a v1.02. This board has the same exact configuration and the sensor BUT io7.in was being used, so in this case I had io5.in free so I connected the sensor there... and it doesnt work, exactly the same failure like with the other board.
I modified the config in order to use io7.in... and the sensor works perfect.
I go again to the V1.01 board, change config to use io5.in... and works!
This is very strange!
Update: I have tested a third board, V1.01b, in this one io7.in is also failingIs there any value I can measure on the board or something ??
-
@Tinchus with nothing connected to io7 you could measure the voltage between io7_in and ground using a multimeter. It should read 3.3V if the pullup resistor is present.
-
-
@Tinchus on the 6HC (but not the Duet 3 Mini) you can use an io.out pin as an input. Use the ^ symbol in the pin name string to enable the pullup resistor.
-
@dc42 thanks, I this this would be the last: if I use ou7.in for a swich and out.out for the other swith, both will share GRND, right. Any problem with that config?
In formware would be
M950 J4 C"!io7.in"
M950 J7 C"^io7.out"With this config something is wrong: I connect both switches and the status on the boject model changes. If I activate (manually) the switches, there is no response. Both switches are NC
-
@Tinchus if the switches are NC then you should use "^!io7.out" as the pin name for the second one. You should see the value change in the object model when you press the switches.
-
This post is deleted! -
-
@Tinchus I suggest you post an update here because it will relate to the original issue that you posted about.