@ketirange Turns out a motor connector and cable was faulty, and after replacing it im able to perform a calibration move.
Best posts made by ketirange
-
RE: Unable to tune motor in closed loop mode
Latest posts made by ketirange
-
RE: Software crash while collecting closed loop data
@timschneider Thanks for sharing. Now i doubt it is CAN related problem. Maybe SPI communication is not keeping up with all this data being transfered and written to sd card? Im curious if this problem happens for standalone users.
-
RE: Software crash while collecting closed loop data
@timschneider How many boards you have connected to the CAN bus?
-
RE: Software crash while collecting closed loop data
@dc42 This is what i got this morning:
M122:
M122 B30.0 (Which is 1HCL board that was doing data collection during crash)
-
Software crash while collecting closed loop data
Hello. I'm having issue while trying to tune my stepper motors working in closed loop. I'm using closed loop plugin and the printer keeps crashing during data collection moves. The messages that pops up are "SPI connection has been lost" and "Board 52 reconnected" The crashes happen at random time. Sometimes just after move starts, or at the end. I have noticed that lowering the amount of data (by reducing samples and move length) reduces chance of crash, so it got me wondering if this issue is related to CAN bus communication being overloaded with messages due to large numbers of satellite boards connected to it.
I also had occasional crashes during input shaping data collection moves, but they were less frequent.
My setup:
DSF and RRF - newest 3.6
Hardware is Duet3 6XD in SBC with two toolboards, six 1HCL and two expansion boards. -
RE: Unable to tune motor in closed loop mode
@ketirange Turns out a motor connector and cable was faulty, and after replacing it im able to perform a calibration move.
-
RE: Unable to tune motor in closed loop mode
@ketirange So im able to succesfully execute closed loop tunning move on both Y axis motors. X axis motor still gives same error while executing M569.6. Is there some debug mode for closed loop i can use to check what is going on? I already checked wiring and it looks the same as Y. I also checked continuity from encoder to 1HCL and measure voltage on B and A pins and it looks ok.
-
RE: Unable to tune motor in closed loop mode
@dc42 Yes, i was able to calibrate drives on 3.5.4 too. I will try tuning on my Y axis. If the same problem occurs, i will get back to you.
-
RE: Unable to tune motor in closed loop mode
@dc42 Motor does not have brake, and is doing 10mm move before switching to closed loop. Im checking wiring now, but cl worked for me on RRF 3.4.6
-
RE: Building Duet3expansion 3.6-dev
@dc42 Oh i was not aware you have forked version on your github. It compiles fine now. Thanks for help.