1HCL 1.0 closed loop controller
-
@dc42 I added that line to the first line of code in my home”x” and I’m still getting the same error “ driver 50.0 error: failed to maintain position. It is homing in open loop and is working that way but the error persists… I’m going to put it back in close loop and see what it does. I put it back into closed loop and of course the error persists. I switch the cards around and manually operated the switches by hand, the problem follows the motor. I disconnected the motor leads from the board, ran M122 B50 looking for the raw count being zero, then moved the motor armature and ran M122 B50 again and no change in the raw count so I think I have a bad encoder on my motor. I guess I am back to the drawing board on my end... aside from this issue I have all my other areas of concern addressed. Thank you all for your help @dc42, @Phaedrux
-
@supertb1 what exactly is the sequence that gives rise to that error message? Does it occur during homing; or when homing is complete; or when you attempt an axis movement after homing? Has the driver been switched back to closed loop mode when it occurs?
-
@dc42 it happens immediately upon initiation of homing sequence, on command movement and at board reset in both open and closed loop, it will home in both open and close loop but in close loop it will not maintain position. I am going to take the motor apart to try and understand what is happening better… more to follow
-
@supertb1 I popped the side cover off the motor and found the A+ wire had a bad solder joint, put it all back together and now when I home the axis it still returns 4/22/2022, 8:43:39 PM Error: Driver 50.0 error: failed to maintain position
And then it displays drive 50.0 tuned successfully measured hysteresis 0.17 step… go figure… it is holding position and everything. So last question, how do I get the error to go away? -
@supertb1 so is the only problem now that in open loop mode when you are homing and have not tuned, you are getting the "filed to maintain position" message?
-
@dc42 no it is giving the alarm on a tuned closed loop homing cycle… it is doing it on my other system that I recently updated… the alarm has something to do with one of the updates I think
-
@supertb1 the homing move or moves should aways be done in open loop mode, and should be followed by the basic tuning move before switching to closed loop.
-
@dc42 I am using the recommended homing sequence as prescribed
-
@supertb1 please can you test if this issue is resolved in 3.5b3
-
@T3P3Tony Hi. I am almost scared to update... I am currently working through issues with my new coreXY (https://forum.duet3d.com/topic/32222/corexy-1hcl-issues/2?_=1682288729468). Apparently the close loop tuning maneuver has changed from the previous coding and it may be part of what is going on with this new machine. I will update and see if any errors develope
-
@supertb1 any news?
-
@dc42 said in 1HCL 1.0 closed loop controller:
@supertb1 the homing move or moves should aways be done in open loop mode, and should be followed by the basic tuning move before switching to closed loop.
You mean after homing, switch to closed loop and THEN do the tuning maneuvre? The documentation states it that way...?
Still having trouble with my Nema34's closed loop so i'm looking at everything right now.