@deckingman Just in case you are still around, I’ve tried out my idea, and it seems to work! I can only test it in a simplistic way, but I don’t see why it shouldn’t work scaled up. So…
In my config.g I assign a dummy driver number to X and Y. My first (and only) ‘real’ axis is defined as U and V. So driver assignments are:
M584 X5 Y6 Z2 U0 V1 E3
This is just on a Duet 2 WiFi, so drivers 5 and 6 aren’t there, but need to be defined, otherwise it defaults to driver 0 and 1.
For the kinematics, I told it to move U/V to move with X/Y, for the same X and/or Y input move, with:
M669 X1:1:0:1:1 Y1:-1:0:1:-1 Z0:0:1:0:0 U0:0:0:1:1 V0:0:0:1:-1
This shows the matrix as (I've formatted it to show the gcode input axis as rows, and shows how it affects each axis in the columns):

M669 Kinematics is modified CoreXY, matrix: Motor driver: 5(X) 6(Y) 2(Z) 0(U) 1(V) (G1 input) (X) 1.00 1.00 0 1.00 1.00 (Y) 1.00 -1.00 0 1.00 -1.00 (Z) 0 0 1.00 0 0 (U) 0 0 0 1.00 1.00 (V) 0 0 0 1.00 -1.00

So a move in X eg G1 X10 causes a move in dummy motors X/Y, and real motors U/V. The X position in DWC changes, but the U position does not. A move in U cause the U/V motors to move and their position is reported in DWC, but not the X or Y position.

I also tested motor current. I set M906 X100, and G1 X10. U and V motors moved correctly, and X10 reported in DWC. I waited for idle hold and did it again, U and V motors moved correctly. I then sent M906 X1000 U100 and tried it again. U motor stalled on moving. So it would seem that the axes keep their individual motor settings this way.

This setup allows for individual ‘Core’ axes homing, with each motor pair being able to have it’s own motor settings. You’d set X/Y as the dummy axis (though there are no motors attached, so you would just set it with G92 X0 Y0), and define the other 3 Core axes pairs as U/V, A/B, C/D, which can be homed individually. From there, normal X and Y movement inputs would cause all three axis pairs to move together. Care would be needed to set accelerations and speeds to settings that all axes are capable of, though.

Ian

Sounds like the cause would be in the slicer area. The firmware doesn't have a concept of infill.

@Phaedrux said in M305 Thermistor Values for the Duet 2 WiFI on the Ender 3 Pro?:

Try M305 P0/P1 T100000 B3950 and see if it matches more closely to the previous temp tower performance.

@Phaedrux, thanks! That seems to work better and align with what would be acceptable temperatures.

Perhaps give this calibration method a try.

https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+4:+Calibration/40

What is the filament path like? Does the filament feed smoothly or is there friction and resistance?

I think a hi point mesh and reloading the grid is the way togo. How stable is your bed, is it removable ? If your printer is mechanically stable i dont see an issue with reloading the grid.

I'm seeing those blobs and they are annoying, they just don't seem to go. Happens most on solid infil layers and then the nozzle catches them on travel moves

I bought my Tronxy X5SA-Pro 500 and it has the same ribbon cable from the back to the front. I'm putting a Duet 3 on it, so i'll be stripping wires and re-crimping a lot. I don't think i'll use the ribbon cable. What did you end up doing?

@fcwilt Thanks fcwilt

Glad you got it sorted. I'll add a note to the page about adding the jumpers back to the second Z driver port as it certainly may not be obvious to the uninitiated.

By the way, if you already have a probe you don't really need to use the dual z endstop method at all, but if it's working for you, rock on.

@morf33 said in mesh bed leveling issue:

M92 X100.00 Y100.00 Z400.00 E409.00 ; set steps per mm

You'd have to do the calculation knowing your belt tooth pitch and pulley tooth count as well as stepper resolution and microstepping, but I think your correct steps for X and Y is actually 80.

xy_steps_per_mm = (motor_steps_per_rev ∗ driver_microstep) / (belt_pitch ∗ pulley_number_of_teeth)

@bearer thank you for pointing me in the right direction - i got it to work 🙂
btw I am really looking forward to the use of variables - than we can use more potential of the board

What is your usage case?
If you're not FDM printing, but instead trying to control an external device via the relay (like say a welder), you could probably set the machine up in laser mode.
See M542
https://duet3d.dozuki.com/Wiki/Gcode#Section_M452_Select_Laser_Printer_Mode

I just understood what i've done, I opened the editor by the button on System folder:

9a8c524d-ae44-408e-9bdd-fb1020a274b8-image.png

i was thinking it was the actual configuration, but it's the first Json config i've made, probably the mistake come from there...

sorry if i gave you some wrong info 😆

@bot
That's what i thought to, but it didn't do it when i tried a single extruder slice at least.

@Phaedrux
Unfortunately all my experiments with frequency have failed. I am still running the old fan with my finger.
The only thing I can add is that "always on fan" only works with a direct connection to the board.
When fan is connected to "smart effector", "always on" does not work the same way.
Regards.

P.S. I understand that this is not a lot of information, but there is always hope that an idea will come to your bright mind.

@andyvirus I stumbled across this thread with a similar issue to yours. I figured I'd reply in case anyone else finds this thread looking for a solution. I fixed my issue by removing any "T" commands from my Tpost/Tfree/TPre macros. I had a T-1 in the beginning of a few of them and I believe this was causing my G-code for lowering the bed to be run twice.

@evomotors said in Toolboard BLTouch connection in configurator tool.:

So it is a just a online configurator issue?

Yes, and hopefully it will be fixed soon. However, to get the most out of Duet, you’re going to have to get comfortable editing the system files, and understanding the gcodes. But the forum will support you, plugging gaps in knowledge and pointing to documentation as necessary.

Ian

I bet it's the Simplify3D thing.

Time to move to PrusaSlicer! 🙂

No problem. It can get a bit daunting at times and we tend to overthink it which can lead us astray. Usually, when in doubt, getting a config from the configurator will show us the correct syntax to start with.

@droftarts Looking at the motor specs for the 42-40 , current rating 1.5amps , my cura settings for retract is 45m/s which is the same for the cr10s pro with the same dual gearing as my ender 5 plus, I can't hear it missing any steps .
Most of the settings was from the configurator using the ender 3 profile.

I've only taken out 4 wires from the control box , 2 powering the motherboard and set going to the mosfet .
I've a few test prints and can't see any differences from the stock motherboard, now it time it pull it apart.