Posts made by Anzere

So I have not yet used this command at all but M110 will set your line number in a file (https://duet3d.dozuki.com/Wiki/Gcode#Section_M110_Set_Current_Line_Number). It might help you.

Reprap firmware has protection in place to prevent you from crashing your printer in the form of a homing requirement. You can either home your printer or disable the homing requirement. In order to disable the homing requirement for your printer you can enter the command M564 H0 as stated by @deckingman.

You can edit the heightmap.csv file in notepad, excel or the DWC. Just make sure that you keep the commas and filetype correct and you will be fine. This is what my flat heightmap.csv looked like:

RepRapFirmware height map file v2 generated at 2018-06-09 11:04, mean error 0, deviation 0
xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
0.00,325.00,30.00,380.00,-1.00,30.00,30.00,11,12
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0
0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0

This will not help you get more consistent sensor results but it will allow you to print with some form of bed leveling. Have you tried to change the tolerance of the M558 command with the S parameter. The default according to this is 0.03mm. So raise it from that and see if you can still get reliable results.

I am not sure I understand your message right but you can enable individual probes by reducing the number of Z-probe tries you do with the M558 A parameter. But that is a hacked solution as you will no longer get the benefit of smoothing out multiple erroneous readings.

Ok, thanks! Any chance that this command can use X0 Y0 by default to avoid this in the future?

The S1 is the endstop detection enable flag. This is so that if I have an extremely large print that extends to near the axis limits of my printer, I won't crash my printer. It is unlikely to be material seep because the amount of filament required for the layer is way more than what could ooze out of the nozzle. I also watched the print resume and saw that it was printing about 0.3mm or 1 layer higher than expected. I will try your resume.g code and see what that does for me, and I'll take a look at your link. Thanks!

Alright, thanks for the feedback so far. I will try and reproduce it and let you know if I do along with more information.

@Phaedrux The max feedrate of my machine is set to 3000 for the Z axis with M203, and I am fairly confident that it easily reaches those speeds. That is unless the pause ignored the max speed.

@phaedrux This was my pause.g file:

; pause.g

M83
G1 E-10 F3600
G91
G1 Z5 S1 F360
G90

And this was my resume.g file:

; resume.g

G1 R1 Z5 F6000
G1 R1
M83
G1 E10 F3600

Thanks!

Hello,

I was running a print when I decided to pause the print and tighten down a fan that became loose during the printing. When I pressed resume, the print skipped a layer. The maintenance I did could not have adjusted the nozzle height at all and I did not run any G-code during the pause. Babystepping was also set to 0. Anyone have any idea why this occurred?

Thanks!

Hello,

I am currently using a Duet board and I'm trying to use nested macros to simplify the homing process. I want the homeall.g file to call the homex,homey and homez.g files. However, because the firmware pops the stack after returning from a nested macro, none of the settings configured in the nested macro are saved. Is there a way to get around this and still be able to use nested macros to save settings?

Thanks!

@dc42 Thank you!

Hello,

Recently I have been working on bed leveling a CoreXY printer with an IR z-probe. I am running the G32 command which then runs the bed.g file. The bed.g file consists of numerous different G30 commands. The reason I am using the G32 command in order to level the bed as opposed to the G29 mesh bed leveling is because I found that our z-probe trigger height varied drastically at various points on the bed. I can change the offset of the z-probe trigger height with the H parameter of the G30 command at various points on the bed in order to compensate. The final G30 command is followed by an S parameter with the number of points that have been probed. Currently, I have been able to get this technique to work for 5 points successfully, but I would like to get it to work for more points. I have attempted to do so but I have received the error: "Error: Probe points P0 to P3 must be in clockwise order starting near X=0 Y=0 and P4 must be near the centre". This gives me the feeling that probing more than 5 points is not supported. Still, I have found wiki articles explaining that probing with up to 16 or 64 points is possible. My question is: Is probing more than 5 points for bed leveling compensation possible and I am doing something wrong or am I trying to do something that is not supported? I have included the relevant parts of the bed.g file below. Let me know if you need any more information in order to answer my question.

This file is attempting to run a 3x3 grid bed compensation.
bed.g file G30 commands:
G30 P0 X 371 Y 378 Z -99999 H -0.285
G30 P1 X 191 Y 378 Z -99999 H -0.1
G30 P2 X 41 Y 378 Z -99999 H 0.06
G30 P3 X 41 Y 198 Z -99999 H -0.05
G30 P4 X 191 Y 198 Z -99999 H 0
G30 P5 X 371 Y 198 Z -99999 H -0.34
G30 P6 X 371 Y 30 Z -99999 H -0.285
G30 P7 X 191 Y 30 Z -99999 H -0.187
G30 P8 X 41 Y 30 Z -99999 H -0.06 S9

Thanks,

Floris