Ability to change movement/feedrate button increments, please

I work with a 8x8x6 meter concrete printer...... 100mm is not very long to move, and 6000mm/sec is just slow af....

Kulitorum

@Kulitorum here.

I tried to use G2 and G3 but they are not interpolated very nice in current firmware and pausing during a G2 or G3 messes up and the printhead moves in random directions. I talked to dc42 about this, but I guess the current use of G2 and G3 is too low for him to spend time with it.

So I use very short lines of a max of 5 mm. With good jerk and acceleration parameters, that moves smoothly and allows me to pause a print at any time within 25mm, in regards to 4-5 commands being buffered in firmware.

Your slicer should keep an eye on overflow (crossing 360 degrees) and if needed "rewind" the rotation back to 0 to untangle your wires.

Now watching thread, if you need more help. Unfortunatly I can't share my code.

Kulitorum

750w servo motor on the x-axis.

https://www.youtube.com/watch?v=nMCpMZPh6Ds

I hope to print at this speed, but I have set the expected speed at 300mm/sec. We'll see what the concrete pumps can do.

Kulitorum

This is the printer:

@t3p3tony Yes, I did that already, so that you can pause the machine quickly if there's a minor issue. I'm cutting all moves into 5mm sections.

How did you get a Duet to be this noisy?

The design is wasting a lot of space on the XY plane, and not gaining much from it. And you move a lot of weight around for no real reason.

The couplers have to be 100% centered, and I doubt these are, as they are tightened from one side.

At least put the motors "outside" the moving area, so they "stick out" of the frame. This will increase your printable area around 10cm on both axes.

Lots of design issues IMHO

Xa Xb Xc, Ya, Yb, Yc ?
D,H,I,J,K,L,M ?

Thank you - turns out the UM2 does not use Thermocoubles, but a PT100 RTD (Resistance Temperature Detectors) Device, so I did have the correct daughter board, I just had to short the solder pins (red circles) and my config (that works) is:

; Heaters
M308 S0 P"spi.cs0" Y"rtd-max31865" ; configure sensor 0 as thermocouple via CS pin spi.cs0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M308 S1 P"spi.cs1" Y"rtd-max31865" ; configure sensor 1 as thermocouple via CS pin spi.cs1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

I can't find anything in any documentation - Where do I install it, and in what orientation?

Tried this - it seemed logical, is this correct?

I'm connecting it to a Ultimaker K-Type thermocoupler - is my configuration correct?

; Heaters
M308 S0 P"spi.cs0" Y"thermocouple-max31855" ; configure sensor 0 as thermocouple via CS pin spi.cs0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M308 S1 P"spi.cs1" Y"thermocouple-max31855" ; configure sensor 1 as thermocouple via CS pin spi.cs1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

Thank you.

I guess we will at most move 9 axies at the same time - XYZEU, 'X'Y'E'U for a two head move - in 1-2 years maybe 18 (with 4 heads)

We have a vertex for every 10mm in the XY plane, and run at 500mm/sec (working towards 1000mm/sec, give it a year)

Kulitorum

So I suppose the lowercase - 'A 'B 'C etc. solution would be the prefered then? - That would release 26 extra axies.

how many axies do we have CPU power to drive?

Kulitorum

But when reading for example a G31 command, you then start looking for K parameter, so why would G31 reserve the K parameter?
We use our own slicer and we are adding a second printhead, adding effectivly another X,E,U axis (Xpos, Extrusion, Nozzle rotation) are are investigating adding two more printheads.

Xa Xb Xc, Ya, Yb, Yc ?
D,H,I,J,K,L,M ?

So it's not possible to do 15 axies? - even with Duet3?

Kulitorum

How many channels can the duet3 control at once? - I know that the duet2 will do 10 axis, what is the limit for the Duet3?

Kulitorum

A customer have found this change in gcode between the uploaded file (Duet2 ethernet) and the file on the computer:

Any idea what might explain this?

Kulitorum

Yep, got it to work with 256 microsteps and 2 steps/mm. Thank you.