Z motor on expansion board not moving

wdenker

@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

@wdenker your sensor number out of range is to do with the way you've set your thermostatic fans up. H100 etc isn't valid

wdenker

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

wdenker

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

jay_s_uk

@wdenker did you check you were actually supplying 5v to the 5V_EXT?

wdenker

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

wdenker

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

wdenker

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

Phaedrux

Sounds like the wiring is picking up noise. What other cables does it run near?

wdenker

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

droftarts

@wdenker when you say you are moving it to another printer to test, and it works, is that with a Duet 2 board? Is the non-working configuration your only Duet 3? Or is it the exact same configuration (Duet 3 6HC + 3HC, config.g and wiring)? If not, post the Duet 2 config that works, and how the sensor is wired.

Ian

wdenker

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

jay_s_uk

@wdenker duex5 IOs are inverted as standard I believe so you'll probably have to add a ! To the pin name

wdenker

@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

@wdenker sorry, should have spotted this earlier:

Filament monitors must be connected to the same board as the corresponding extruder motor. This use so that the firmware can correlate the measured filament movement and the commanded extruder movement in real time.

See https://docs.duet3d.com/User_manual/RepRapFirmware/CAN_limitations#permanent-limitations

You have the extruder drive on the mainboard but the filament monitor on the 3HC. Move the filament monitor to the main board, or the extruder to

Ian

wdenker

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

droftarts

@wdenker sorry, I was looking at your config.g you posted earlier, and I could have sworn it said the extruder drive was on 0.0 and the filament sensor was on 1.out1.in!

Could you post your current config.g, in case anything has changed?

Ian