@phaedrux

@droftarts we figured it out. The bltouch had a small metal shaving in the pins from factory. Then the fans the config.g somehow didn't get copied over. So I got a little ahead of myself with this post.

@dc42 I sure would love to! I have a corexyuvab utilizing 4 leadscrews, two independent gantries and heads. Would love this capability.

Wondering if there is documentation I am not finding on idexx machines. I have my dual gantry dual head corexy printing and was wanting to start a dual head print in ditto mode. But I'm not finding the documentation on it.

@dc42 Has this changed at all? It would be nice to have it pause and only stop heating the heater that faulted not the bed. Can this be changed somehow? Also if it was a true pause instead of timing out and going away after so long would be awesome as well. Most of the time the print stops in the middle of the night and I don't wake up early enough to get to it. I don't see any reason for making it time out or having the other heater stop.

@Veti you are right sorry I pulled from my 2.05 version. and 3.1 I only have working on duet 3 so far.

Wondering if there's a way to do baby steps for individual lead screws? I have a fairly large format printer I have four lead screws that I would like to be able to babystep individually. The mechanical leveling and mesh leveling doesn't get it as close as I would like.

@phaedrux no but my infrared thermometer shows it is accurate.

@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.

@owend of it was stuck on because of a hardware fault shutting down the board wouldn't resolve it either.

@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.