Problem on io7.in
-
Hi. Im trying to use a normal switch, it is a normallly closed one. I have connected 1 of its pins to GND on IO7, and the other pin to IO7.IN
Config is:
M950 J4 C"io7.in"
M581 P4 T3 S1 R0I have triple checked, there in no other J4, P4 or any other ssignment pint to number 4, the same with the P4 assignment.
I manually activate / deactivate the swich and the board cant detect it. If I unplug the connector FROM the board, the status of the input changes ans it wopuld have been activated (I see it in the object model)
Ideas about what could be wrong?
-
@Tinchus something to check then would be the switch with a multimeter to see if you can see it switching ?
-
@T3P3Tony checked, it is ok. Looks like it is the board, i checked the same sensor on another board and it worked. I will check again the crimps... but could io7.in be damaged, io7.out works ok, it is just that pin. The one "failing# is a board 1.01, the one working ok is a board 1.02. I read docimentation to check if there is any difference, look like it doesn´t
-
@Tinchus if the board is seeing the disconnection from the switch on a plug/unplug, that indicates that the input pin is seeing something. A simple switch in NC mode is electrically no different pressing the switch to plugging/unplugging it.
Please try with IO6 on the same board, obvious changing the config as well.
-
@T3P3Tony thnaks for the quick answer. Changed to io6.in and it is working, unplugging the switch on i7.in shown no change on the object model value (it is showing always a value of "1")
Anything I can do to check on the board. Everything else on the board is working ok, this one in paricular has been working for 2 years aI think, it is just now that it came yo my mind use 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.