Ive started an Openpnp/Duet config/gcode page for the Openpnp group. Please help keep the page accurate and up to date. The current example is based off my current machine a CHMT36V using a 6HC and x2 1XD's.
Thanks Wayne

@dc42
Ok got comms sorted. I got this initially

Looks like the MISO line isnt pulled up locally on the the BTT board. I guess this makes sense as the board is meant to plug into 'step stick port' on a BTT driver board. In all the literature I read from BTT/Biqu makes no mention of pullups or active line jumpering. Any way pulled the MISO line up to 3V via 10k and now I get the following;

DWC is also reporting semi resonable values so now just some tuning and firmer wiring to get the ball rolling. I have a Duet PT100 dtr board coming from filastruda and I dont think ill have it for a week. I also ordered an Adafruit MAX31865 bob that should be here tomorrow so Ill follow up this thread on how that gos.

Huge thanks for this Forum and support, the best

@owend
Will do, I need to get the mechanicals back together first.
If you dont know what this is, it's the aftermath drag pin machine crash. The pin with the bent tip slides up and down within the blue coil of the selenoid with the bent frame.

I hope to get fixed tonight and put some of my new and improved RRF commands to work

Thanks again.

@fcwilt THANK YOU! The schem answers all questions.
For my app I will drive an off board FET driver board via V_OUT's set to 12V.

@dc42 said in Getting stared with Closed Loop:

4. Use standard Nema 17 motors + magnetic encoder boards (coming soon!) + EXP1HCL expansion boards.

Waiting anxiously for this option. I have several diff magnet encoder/driver boards S42B, S42C, S57B, Servo42C. Ive gotten them to mostly work after decoding the uart protocols personally because there is no real support, they still kinda suck compared the cheapo optical encoder/drivers. The mags seem to oscillate if not tuned just right and tuning them is a nightmare w the nonexistent UIs to set them up correctly.

You can get and I do have a nema17 optical encoder/driver, but the physical size and cable management of it is way too much for small machines. I mostly use the optical encoder drivers on nema 23 and up.

For me the real benefit to using closed loop is for some of my custom machines that have heavy tool heads on the Z. Closed loop keeps the tools out of harms way while using much less energy without producing a lot of extra heat.

I have x2 1HCL boards just sitting in a box and would love to tinker w the Duets answer to magnetic encoding. Is there any documentation we can peruse as we wait for the hardware?

@blt3dp I have to agree w Jay about not recommending the BTT 12864. I got one all set working on my mini 5 and then I when I went to go mount it to the machine, an ender, the touch screen would stop working and buzzer would sound intermittently. Googling revealed this is a common issue and theres grounding gremlins with that display. I tried insulating and while mouning it and nothing seemed to work. It worked fine free hanging, but not when mounted anyway I could figure.

If you can get it to work ok for you great, but I'd be mildly surprised if you do.

I know Duet is working on encoder motor add on options is there an update on this?

I have several machines running duet mini 5+ and 6HC controller boards with a mix of nema17 and nema23 motors. All the nema24 I use are all closed loop, either clearpath or the cheapo 'servos' with external drivers and they all work very well. They all stay quiet and cool.

Now Im looking to update my 3d printer motors to closed loop. They're all nema17 due to size/mech constraints. I already have x2 unused Duet 1HCL's that I never put into action and boxes of unused nema17's. I'd like to try the HCL's Im having difficulty figuring out best encoder option to try and adapt to. Any ideas?

@dc42 Hmm, So what is best pratice for the following end use;

I have 2 Servos and 4 selonoid(2ch pos/vac pneumatic control);

;Servos
M950 S0 C"io1.out" ;"Servo1"
M950 S1 C"io3.out" ;"Servo2"
M950 P2 C"out1"    ;"Valve_Mstr"
M950 P3 C"out2"    ;"Valve_Ch_Slct"
M950 P3 C"out3"    ;"Valve_Ch1_Vac"
M950 P3 C"out4"    ;"Valve_Ch2_Vac"

Im empirically generating my own tool paths and attempting to trigger timed valve sequences and things gets very confusing/later unreadable using the following syntax;

G1 Xmove Ymove
M280 P0 S100; Spin servo1 90deg
M42 P2 S1; +Pressurize Ch1.
G4 P200 ; Dwell stabilize.
G1 Xmove Ymove
M42 P4 S1; Retract
G4 P200 ; Dwell stabilize.
M42 P2 S0; Depressurize.

Since I cant find a way to use/call tool names in gcode created via M563 Im creating globals for literals to replace tool indexes and using in a const manner.

global Servo1=0
global Servo2=1
global Valve_Mstr=2
global Valve_Ch_Slct=3
global Valve_Ch1_Vac=4
global Valve_Ch2_Vac=5

Which is much make macro more readable as;

G1 Xmove Ymove
M280 P{global.Servo1} S{global.Servo1_90}; Spin servo1 90deg
M42 P{global.Valve_Mstr} S1; +Pressurize.
G4 P200 ; Dwell stabilize.
G1 Xmove Ymove
M42 P{global.Valve_Ch_Slct} S1; Retract
G4 P200 ; Dwell stabilize.
M42 P{global.Valve_Ch1_Vac} S; Depressurize.

But doing the above every M280 or M42 will require a M400 command preceeding it? Am I going about this completely wrong? What is best practice to accomplish this?

@dc42 Thanks again. I rolled back from 3.5 to 3.4.5 because of an issue with CNC mode within DWC; Jogging via DWC throws 'missing u parameter' error. Ill be happy to test 3.5 once that gets resolved

@dc42 Yes, M400 resolves the issue. Thank you

@OwenD
No I think youre right. I have and HC6 in a pick and place machine and debug reports everything... Im not sure why the mini 5 is not...

@wayneosdias
Heres what Im doing https://youtu.be/FzovkhonvkI
In the vid is correct movment using constants, changing the constants to globals as the above posted macro the 2nd and 3rd rotation trigger 3 movements early. I can take another video, but it wont have tray loaded because it crashes...

@OwenD Heres what Im running is exactly what Im running

M929 P"eventlogGlobal.txt" S3 ;
;USB_H2_Dispense
;Get head out of way
G54 
G0 U46 V46
;Set offset to H2 for the Case
G58
M280 P1 S{global.Servo2_90};70;
;1st Point of USB
G0 X3.8 Y13.5
G0 V1
;trigger on
G4 P200
G1 V5 F200
;trigger off
G0 X10.5 Y20.7
G0 V1
;Trigger on
G4 P200
G1 X3.8 Y13.5 F600
G1 X10.5 Y20.7 V1.5 
G1 X3.8 Y13.5 V2.5
G1 X10.5 Y20.7 V3.5
G1 X3.8 Y13.5 V4.5
G1 X10.5 Y20.7 V5
;Trigger off
G0 V10
M280 P1 S{global.Servo2_180};130;
G0 X50 Y14
G0 V1
;trigger on
G4 P200
G1 V5 F200
;trigger off
G0 X44.3 Y22
G0 V1.5
;trigger on
G1 X50 Y14 F600
G1 X43.3 Y22 V1.5 
G1 X50 Y14 V2.5
G1 X43.3 Y22 V3.5
G1 X50 Y14 V4.5
G1 X43.3 Y22 V5
;trigger off
G0 V10
M280 P1 S{global.Servo2_135};100;
G0 X35.5 Y11.5
G0 V2
;trigger on
G1 X18.5 Y11.5 F600
G1 X35.5 Y11.5 V2.5
G1 X18.5 Y11.5 V3.5
G1 X35.5 Y11.5 V4.5
G1 X18.5 Y11.5 V5
;trigger off
G54
G0 U46 V46 
M929 S0 ;

Im executing it via

M98 P"/macros/USB_H2_Dispense"

In the console

@wayneosdias
sorry let me redo w the commands inline w the macro and not in the console
this is all I see in the eventlog

2023-01-25 14:41:05 [info] Event logging started at level warn
2023-01-25 14:41:05 [info] Running: Duet 3 Mini5plus WiFi: 3.4.5 (2022-11-30 19:41:16)
2023-01-25 15:00:51 [info] Event logging stopped
2023-01-25 17:22:07 [info] Event logging started at level debug
2023-01-25 17:22:07 [info] Running: Duet 3 Mini5plus WiFi: 3.4.5 (2022-11-30 19:41:16)
2023-01-25 17:26:53 [info] Event logging stopped
2023-01-25 17:26:53 [info] Event logging started at level debug
2023-01-25 17:26:53 [info] Running: Duet 3 Mini5plus WiFi: 3.4.5 (2022-11-30 19:41:16)
2023-01-25 17:32:11 [info] Event logging stopped
2023-01-25 17:32:11 [info] Event logging started at level debug
2023-01-25 17:32:11 [info] Running: Duet 3 Mini5plus WiFi: 3.4.5 (2022-11-30 19:41:16)
2023-01-25 17:32:40 [info] Event logging stopped