Topics created by callielli

@callielli said in G-Code to slow down printing at corners of objects.:

Is there an override somewhere I might be missing?

Some slicers can set the jerk value in the sliced gcode, so check your sliced gcode to see what's actually being executed.

You can also send M566 by itself in the gcode console during a print to see what the value is actually set to to check if it's been changed from what you have in config.g

There's also acceleration to consider.

@callielli said in G-Code to slow down printing at corners of objects.:

down to 12 mm/min from 100 mm/min in the config

Can you post your config file?

Are you running latest firmware on both main and expansion boards? use M115 to check. latest is 3.1.1 on the main board and 3.1.0 on the expansion board.

Its a development printer, until it ready would like to leave any pics, specs etc in house.

M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2020-05-19b2

Sorted - thanks mate!

@Phaedrux said in Issues after installing IR Probe Z Printing in the air?:

And your heightmap only has 4 points? Or are you using more now?

Expanding your gcode for the start of the print we get

M561 ; Clear any bed transform
G91 ; relative positioning
G1 H2 Z5 F2400 ; lift Z relative to current position
G1 H1 X235 Y145 F2400 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X-5 Y-5 F2400 ; go back a few mm
G1 H1 X235 Y145 F300 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X100 Y40 F2400 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed
M561 ; clear any bed transform
G29 ; probe the bed and enable compensation
G29 S1 ; Enable mesh compensation

I don't think there's anything wrong in there.

Thanks for you time reading.

The problem has been solved but rather frustratingly, I still don't know why.

I ended up opting for the nuclear solution and erasing the SD, installing a known config and changing everything I thought I had changed previously one-by-one.

So in short, I have no idea what was causing the in-air print at layer one... the G Code I was using previously is the same one so I am confident it was an error in my Duet code somewhere...

This will be chewing at my brain forever haha

@dc42 said in Burnt Y-Axis Motor on brand new board?:

It sounds like an infant mortality failure of the driver chip. Assuming it's a genuine Duet, your board will be replaced under warranty. Please contact your supplier.

Thanks for the prompt response. I imagine this is a rare fault?

I will head over to the original supplier tomorrow and complete the warranty.

@Veti thanks mate! That worked great! It definitely required some cleaning up.
Appreciate your help.