many thanks... I'll get it ordered today... I'll leave you guys be for a while... headed to Cancun after christmas so it will be after that before I can get to this project... have a great holiday
Best posts made by supertb1
-
RE: Duet 3 6HC micro SD socket damaged, need to send for repair
-
RE: closed loop nema 17/23 driver/controller for Duet 3 6hc board
@dc42 Hello DC42, the suspense is breathtaking on the completion of the closed loop duet stepper controller... any good news?
-
RE: Duet 3 6HC configure firmware dual Z motors Please Help
Update, I looked at another forum page and saw that some one changed there "P" value in there G31 P500 X10 Y10 Z2.5 ; set Z probe trigger value, offset and trigger height line from P500 to P100 and they claimed that this solved their problem. I made this same change with no effect. then I ran a 2 meter long cable outside of the wire tray to the sensor and vwala, it is homing and printing perfectly. So in my case it appears that EMF and wire length plaid a role in the culprit
-
RE: Duet3D 1HCL - Closed Loop Controller Beta test
@jay_s_uk increased S1 to S3:
; Drives
G4 S3 ;wait for expansion boards to start
M569.1 P50.0 S1 T2 C20 E20 R100 I0 D0 ; Configure the 1HCL board at CAN address 50 with a quadrature encoder on the motor shaft that has 20 steps per motor full step.
M569.1 P51.0 S1 T2 C20 E20 R100 I0 D0 ; Configure the 1HCL board at CAN address 51 with a quadrature encoder on the motor shaft that has 20 steps per motor full step.
M569 P50.0 D4 S1 ; Configure the motor on the 1HCL at can address 50 as being in closed-loop drive mode (D4), Open loop (D2) and not reversed (S1) X axis
M569 P51.0 D2 S1 ; Configure the motor on the 1HCL at can address 51 as being in closed-loop drive mode (D4), Open loop (D2) and not reversed (S1) Y axis
M569 P0.0 S1 ; physical drive 0.0 goes forwards Z 1-2 axis
M569 P0.4 S1 ; physical drive 0.4 goes forwards Extruder
M584 X50.0 Y51.0 Z0.0:0.1 E0.4 ; set drive mapping
M671 X-122.25:689.20 Y0:0 S3.0 ; leadscrews at left (connected to Z0) and right (connected to Z1) of X axis
M350 X32 Y32 Z32 E16 I1 ; configure microstepping with interpolation
M92 X106.5 Y257 Z795.00 E339.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X1000 Y3000 Z3000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
M917 X0 Y0 ; Set the closed loop axes to have a holding current of zero -
RE: closed loop nema 17/23 driver/controller for Duet 3 6hc board
@chernogorsky I agree, I would be willing to put some money on this for pre-order.
-
RE: closed loop nema 17/23 driver/controller for Duet 3 6hc board
@dc42 Hello dc42, it is that time of the month and I am as excited as I have been to take part in field testing the new closed loop controller and steppers. How close is Duet3D to coming to market? As always best regards.
-
RE: closed loop nema 17/23 driver/controller for Duet 3 6hc board
@dc42 OH MY GOD... the chip set on the new 1HCL boards are so much more efficient than the drivers on the Duet 3 6HCL boards.... I love it... you guys are awesome!!!!!
-
RE: 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