Posts made by wdenker

@droftarts It is not on the expansion board I don't know where you're seeing that.

@jay_s_uk your right I did have to add the ! but doesn't solve my duet 3 problem which after more testing I think is interferance or cable length.

@droftarts wired similarly and to a duex5 they don't work on a duet 2 wifi endstop port oddly enough. The configuration is M591 D0 P2 C"duex.e2stop" S1 ; where the configuration on the duet 3 is M591 D0 P2 C"io4.in" S1 ;

@Phaedrux one motor cable but we moved it away from it temporarily with no luck.

@jay_s_uk So we tried swapping from high to low and low to high to validate it isn't just positioning of the sensor. So basically trick it to say no filament when there is filament and there is filament when there isn't. It doesn't pop the error in this case only when configured correctly and filament is in and reads filament is in. This is mind boggling to me. I also just moved this sensor to another printer that I know it works on. Am I missing something with a config file or something since I am on 3.4.6 to where I can tell it it has to read no filament for a certain amount of time?

@jay_s_uk the funny part of these sensors is that they will not work on a duet 2 wifi but will on a duex 5. So I have tried these sensors on the duet 3 io0-3 at this point on 3.3v or the 5v and the sensor works no problem and reports correctly when I query it with the M591 D0 but still reports every 30 seconds on the dot without any changes no filament and I could query at the same exact time every time and it would report I do have filament and then pop up a split second later saying no filament. Almost like a bug in the firmware.

@jay_s_uk reads at 4.96 so I should be good there.

@jay_s_uk I was able to fix that I basically gave it a mcu temp to look at to turn on. Now if I could just figure out this filament sensor I would be golden. I have tried io.0-2 and 3 different sensors that work fine on a duex 5 but coincidentally will not work on the duet.

@wdenker ah ok well any other things I could try at this point?

@jay_s_uk The other thing I am curious about is if the sensor number out of range error in the M98 p"config.g" if that may be somehow causing it but it doesn't give any reference to what is out of range and there are 3.

@jay_s_uk no none of them work with the 3.3 manufacturer claims they are 3.5 from everything I've seen and I have five working ones that I tried on the 3.3 and moved over to the duex 5 And they all work with the 5 volt.

@droftarts I would think that I would have only damaged that one port if that was the case. I have tried multiple ports to validate that.

@jay_s_uk we have tried the 3.3 on the duet and it does not work so we figured we have to use the 5 volt.

@Phaedrux any ideas?

@jay_s_uk Here are the pics. I have also updated config to reflect going to io2.in vs out

@wdenker Well I got ahead of myself still getting the error just not as often.

@jay_s_uk ah you were right. We had to switch it to 5v vs 3.3 and didn't have it on in after we swapped to the 5v. So all of my issues are resolved at this point.

@jay_s_uk we've tried both in and out.

@wdenker can't even get it to report 3 out of 4 times.

12/20/2023, 4:25:15 PM	M591 D0
12/20/2023, 4:25:12 PM	M591 D0
Simple filament sensor on pin (io1.out,serial1.tx), enabled, output high when no filament, filament present: no
12/20/2023, 4:25:00 PM	M591 D0
12/20/2023, 4:24:59 PM	M591 D0
12/20/2023, 4:24:41 PM	M591 D0

@jay_s_uk any ideas on the filament error I get literally every 30 seconds no matter no filament movement?