sudden 'Driver x error: phase B short to Vin' on Fly E3 Pro
-
I have a sand table (so it's only using two axes) running RRF on a Fly E3 Pro. It has been working fine for months and months, but in the last couple of days started reporting 'Driver 0 error: phase B short to Vin'. There was no change to wiring immediately before this. It typically does a couple of 'prints' after a reset until it comes up with this fault, but then that axis stops working.
I was using drivers 0 and 3 (ie what would customarily be X and E0) as my X and Y axes.
Thinking maybe I had actually managed to short something (the board was for a while 'kicking around', though it has been installed in the sand table frame for some months since then) I shifted along one driver and set it up to uses driver 1 and 3 as my X and Y. However, on the second print after doing that, I get 'Driver 1 error: phase B short to Vin'.
What is this likely to indicate? Until the last few days all was fine. The stepper is a perfectly ordinary 200 step 34mm Nema 17 from Ooznest, bought new for this build in November last year. Nothing changed just before the faults happened - no wiring change or config change. When I opened up the table to move to the next driver I put a brand new Meanwell 24V PSU in, but it managed a print after I put it back together before producing the error. I have never done any unplugging or plugging of cables with the board powered (on steppers or endstops - one axis homes by stall detection, one by optical endstop).
I'm assuming it's probably bot actually a firmware or config issue, but I'm very unsure where I start debugging this, and don't want to discard all the hardware and start again, so any advice from teh hive mind about what a short to Vin is likely to be would be useful. Thanks.
-
@achrn if it followed the motor then there's an issue with the motor or its wiring
-
@jay_s_uk thanks.
On the very next 'M999' and then homex I got 'Driver 1 error: phase A short to Vin' so it's apparently both phases that are upset (I had only noticed phase B before).
Are there tests I can do for that? I have multimeters and oscilloscope. Just putting multimeter across the coils at the board end (ie to check both motor and wiring at once) I get jumping between 1.9 or 2.0 ohms on both (the data sheet says 2.1 +/- 10%). (That's using my meter that is most reliable at low resistances - I have a supposedly better / more expensive true RMS one that's rubbish at low resistances - teh expensive one reckons about 38 ohms.)
Having put it all back together after measuring coil resistances, it's currently working again.
-
@achrn it could also be the crimps that's the issue. I would just monitor them and maybe look at redoing them if it happens again.
-
@jay_s_uk OK, thanks. I'll try redoing the cables if it happens again.