some background. I recently started playing with Duet, so I could be considered complete noob (though I have plenty of 3d printer and CNC experience)

I picked up a Duet mini5+, a 1HCL board (ver 1.0a), and a magnetic encoder (v0.3).
Upgraded the firmwares to 3.5.1
I've got it setup very minimally on the desk just getting used to the software/setup.

I'm trying to follow the guide, (still can't post links) but the Plugin never allows me to select a driver. "No data available"

I can move the motor in open and closed loop.
and even do a manual M569.5, then open the subsequent file in the plugin.
I just can't get the plugin to cause the recording/tuning moves.

I thought maybe it was my version, Started with RRF Version 3.5.1 on all, Updated to 3.5.4 on Mini 5+ 1HCL and DWC. uninstalled and reinstalled the ClosedLoop plugin 3.5.1. Same situation. Can move, can record, cannot get the plugin to cause the move.

is there something obvious i'm just missing?

Config.g

; Configuration file for RepRapFirmware on Duet 3 Mini 5+ Ethernet
; executed by the firmware on start-up

; General
G91 ; Relative coordinates
M83 ; relative extruder moves
M550 P"TestSaw" ; set hostname

; Network
M552 P192.168.1.14 S1 ; configure Ethernet adapter
M553 P255.255.255.0 ; set netmask
M554 P0.0.0.0 ; set gateway
M586 P0 S1 ; configure HTTP

; Wait a moment for the CAN expansion boards to become available
G4 S2

; Closed Loop Drivers
M569.1 P50.0 T3 E0.0:0.0 S200 R40 I0 D0 ; only magnetic shaft encoder

M569 P50.0 S1 D4 ; driver 123.0 goes forwards (extruder 0) FEED

; Axes
M584 E50.0 ; set axis mapping
M350 E16 ; configure microstepping 
M906 E800 ; set axis driver currents

; (micro)Steps/mm Calculation:
; E: Driver 16 microsteps
; E: Motor 400steps/rev (89080.1598:1) {6400}
; E: Belt Reduction 1/2 (0.5)(222.7003995:1) {12800}
; E: Harmonic Reduction 1/100 (0.01)(111.35019977:1) {12800000}
; E: Pinch Roller Radius 7.212148 mm (circ 45.3153) (1.1135:1) {28246.530421/mm}
; E: Encoder Roller Diameter 12.954 mm (circ 40.6962)(1,610.371484 ticks/mm)
M92 E28246.530421 ; configure microsteps per mm 
M566 E0 P1 ; set maximum instantaneous speed changes (mm/min)
M203 E17.7 I0.1 ; set maximum speeds (mm/min)
M201 E5462.962963 ; set accelerations (mm/s^2) 

; Kinematics
M669 K0 ; configure Cartesian kinematics

; Spindles
M950 R0 C"nil + io1.out" Q500 L60:10000 ; configure spindle #0 ;P"io1.out" 

; Tools
M563 P0 S"Blade" D0 F0 R0 ; create tool #0

; Miscellaneous
M453 ; select CNC mode
T0 ; select first tool

; Remove Requirement for homing
G92 E0 ;

This would also help me,
With BiSS-C I would be able to select an appropriate encoder for my desired setup (17+ bit resolution required)

There's a post I found where someone was supposedly able to "read" a BiSS-C encoder with SPI in the "SimpleFOCproject" community forum. (can't post links yet, but search for SPI BiSS-C SimpleFoc and it'll likely come up. )

Ah, didn't even consider that an Extruder axis would be different according to the plugin, But it makes sense.

I changed the setup to X axis for testing, and the plugin is working as expected. Might be a good thing to note in the tuning documentation that Extrusion axis needs the custom Gcode.

@T3P3Tony said in Having troubles with Closed Loop tuning Plugin:

You may want to check the magnet is centered, the reported agc value you showed in the video in the M122 report is not bad.

Is there documentation somewhere I can look into that explains the outputs of the M122 for the 1HCL? I have looked, but haven't seen anything explaining AGC, or much of the rest either.

Was able to get some screengrabs of the issue
Thought a minute and a half was a bit long, so I cut it off and made another grab directly after the first.
ClosedLoop1.mp4
ClosedLoop2.mp4
from fresh boot of the boards.
config.g is a bit different than above (as seen in vid) but same results
start in Assisted open loop, motor moves just fine,
clear and calibrate the encoder, then drop into closed loop with macro.
confirm closed loop
start plugin, select options.
When Clicking on "Record" nothing happens. no movement, no results.
but I can manually send the M569.5 and get movement valid results.
record stays grey,
stop plugin and refresh,
Try again with options, click record nothing happens.
Again send M569.5 and get movement and valid results.

@T3P3Tony said in Having troubles with Closed Loop tuning Plugin:

It confuses me that you mention using the quadrature encoder. if you are using the Magnetic encoder then that is in place of a quadrature encoder.

I need to replicate your setup to see if i have the same issues with the plugin. will do that and get back to you.

I'm not sure where beyond the notes I am mentioning the quadrature encoder. Some of those notes are wrong/out of date, I've gone to a 200step motor instead of the 400 I was playing with before, so my microsteps/mm are wrong for the current setup. but I'd assume that's moot for the problems I'm having with the plugin not working as I expected.

I do have a quadrature encoder connected to the 1HCL as well, I configured the Closed Loop just as Magnetic encoder on the back of the motor. (M569.1 T3)

Baby stepping here to get familiar with the system/controls, So I figured I'd practice tuning the motor with only magnetic before "leveling up" to the quadrature and magnetic (M569.1 T1)

Figured I might as well try the 3.6.0-Beta3 because why not.

updated firmwares to that. upgraded the plugin to 3.6.0-beta.1

Now I can get the driver to show in the plugin, but any command I give, it does not move the motor when clicking record.
Then record remains greyed out until I stop and restart the plugin.

I can still send manual logging commands and view the logged file with the plugin.

some background. I recently started playing with Duet, so I could be considered complete noob (though I have plenty of 3d printer and CNC experience)

I picked up a Duet mini5+, a 1HCL board (ver 1.0a), and a magnetic encoder (v0.3).
Upgraded the firmwares to 3.5.1
I've got it setup very minimally on the desk just getting used to the software/setup.

I'm trying to follow the guide, (still can't post links) but the Plugin never allows me to select a driver. "No data available"

I can move the motor in open and closed loop.
and even do a manual M569.5, then open the subsequent file in the plugin.
I just can't get the plugin to cause the recording/tuning moves.

I thought maybe it was my version, Started with RRF Version 3.5.1 on all, Updated to 3.5.4 on Mini 5+ 1HCL and DWC. uninstalled and reinstalled the ClosedLoop plugin 3.5.1. Same situation. Can move, can record, cannot get the plugin to cause the move.

is there something obvious i'm just missing?

Config.g

; Configuration file for RepRapFirmware on Duet 3 Mini 5+ Ethernet
; executed by the firmware on start-up

; General
G91 ; Relative coordinates
M83 ; relative extruder moves
M550 P"TestSaw" ; set hostname

; Network
M552 P192.168.1.14 S1 ; configure Ethernet adapter
M553 P255.255.255.0 ; set netmask
M554 P0.0.0.0 ; set gateway
M586 P0 S1 ; configure HTTP

; Wait a moment for the CAN expansion boards to become available
G4 S2

; Closed Loop Drivers
M569.1 P50.0 T3 E0.0:0.0 S200 R40 I0 D0 ; only magnetic shaft encoder

M569 P50.0 S1 D4 ; driver 123.0 goes forwards (extruder 0) FEED

; Axes
M584 E50.0 ; set axis mapping
M350 E16 ; configure microstepping 
M906 E800 ; set axis driver currents

; (micro)Steps/mm Calculation:
; E: Driver 16 microsteps
; E: Motor 400steps/rev (89080.1598:1) {6400}
; E: Belt Reduction 1/2 (0.5)(222.7003995:1) {12800}
; E: Harmonic Reduction 1/100 (0.01)(111.35019977:1) {12800000}
; E: Pinch Roller Radius 7.212148 mm (circ 45.3153) (1.1135:1) {28246.530421/mm}
; E: Encoder Roller Diameter 12.954 mm (circ 40.6962)(1,610.371484 ticks/mm)
M92 E28246.530421 ; configure microsteps per mm 
M566 E0 P1 ; set maximum instantaneous speed changes (mm/min)
M203 E17.7 I0.1 ; set maximum speeds (mm/min)
M201 E5462.962963 ; set accelerations (mm/s^2) 

; Kinematics
M669 K0 ; configure Cartesian kinematics

; Spindles
M950 R0 C"nil + io1.out" Q500 L60:10000 ; configure spindle #0 ;P"io1.out" 

; Tools
M563 P0 S"Blade" D0 F0 R0 ; create tool #0

; Miscellaneous
M453 ; select CNC mode
T0 ; select first tool

; Remove Requirement for homing
G92 E0 ;

@T3P3Tony Email sent, thanks for your help.

@T3P3Tony @dc42
I was able to get one of those 12mm off the shelf motors in hand, and played around with it and the duet Magnetic encoder board.

With correct magnet spacing and the encoder thickness I have ~6mm clearance from board face (on motor side) with minimal modifications to my system.
The mag encoder board is a 1.5mm, so that means max component height of 4.5mm on the "back" side of the board, (and on the "front" side 2mm) if the same is used.

Do you think it'd be feasible to get all the components on the board with that restriction? In a design that Duet would be able to market/sell? Or are my systems requirements a bit too niche?

@Aurimas That's pretty ingenious.
Though personally I wouldn't care about anyone's patent, so long as I'm not selling the equipment, or building and providing that equipment to potential customers of the patent.

Maybe I'm in the wrong with my thoughts, but to me most of this is a hobby and not stealing their profits.

@T3P3Tony OH, thanks for explaining that. Magnets are magic to me.

@T3P3Tony Good call, I didn't think about heat. The current motors never get above 40c, a thinner might get hotter due to the same energy in a smaller package (or less efficient), will have to test.
Magnets are all rated to 54c and 80c depending on diameter so I think/hope I'll be fine there.

for the widest use case, the 6mm makes perfect sense.
I'm just on the far end of the curve, so I get(have) to look at all options, and if a 10mm magnet is more accurate that can't hurt if it also gives more space to work with.