Duet firmware 2.03beta3 available

[whosrdaddy]

Ran a 2 hour print on my CoreXY yesterday, no problems to report

[boldnuts]

Ran a 3 hour print on my Delta yesterday, no problems to report

[DaveA]

@dc42 I just tried this again and ran a G32 followed by M500 and a reboot. Now when I run G28 and do a G1 Z0 the nozzle is now above the bed by about .65 which is about double the trigger height of .32.

Any idea what I'm doing wrong here?

0_1553688682980_config.g
0_1553688695343_config-override.g
0_1553688905882_bed.g

[dc42]

@DaveA, what type of Z probe is it, and how did you measure the trigger height?

Please check with M115 that you really are running firmware 2.03beta3.

[DaveA]

@dc42 I'm using a smart effector and the firmware is 2.03b3.
I set the trigger height by trapping a 4mil (.102mm) feeler guage. I then reset to zero with G92 Z0. Then step up about 20mm and do G30 S-1. I was getting the distance from M114 but then used the value reported in the little G30 status box. I then update the G31 value in config.g and then do a G32. Then reboot.

I have partially solved the issue by changing the bed.g file to use S6 instead of S9 for the last G30. I'm somewhat confused as I've not changed the bed.g file since last August and the printer has been printing fine. I do a G32 as part of my start script.

[dc42]

@davea said in Duet firmware 2.03beta3 available:

I have partially solved the issue by changing the bed.g file to use S6 instead of S9 for the last G30.

1. Have you tried S8? I can't rule out the possibility that the adjustment to the homed carriage heights after auto calibration doesn't correctly take account of changes to the rod lengths.

2. What happens if you run a second auto calibration - is the Z0 height still wrong?

[brunofporto]

Just to organize things! I wrongly posted at the beta2 thread but the issue is happening with beta3:

When using G29 it is using nozzle reference and not the probe. And the height map shows as it was measuring the bed as the nozzle where the probe.

I do not have any tool offsets and the probe offset is correctly defined.

I'll copy the config.g line here later.

I did not have this issue with 2.02RC6 that was using before.

[DaveA]

@dc42 Just tried S8. No obvious difference from S6. Nozzle may be slightly different depending upon the drag of the feeler. Change to S9 and the nozzle gives a pretty good whack into the bed. Needed to move up by .35mm to regain clearance. Back to S8 and things seem OK again.

Tried to do back to back S9 and the first time it hit the bed. Second time I'm left about 1mm above the bed. Seems not consistent.

[brunofporto]

ps.2: Just found the issue.... The G31 command for the probe had a comment without the ";" so it did not read that line.... Sorry.. MY fault.

Did some tests and for sure after upgrading from 2.02RC6 to 2.03beta3 it puts the nozzle and not the z-probe when using G32 (that I use to align both leadscrews) and G29.

config.g and bed.g attached.

[0_1553976980746_config.zip](Uploading 100%)

ps.: Downgraded to the latest stable (2.02) and have the same issue!

[zerspaner_gerd]

Is that a security measure that only large M650.G filename extension can be created?

[dc42]

@brunofporto said in Duet firmware 2.03beta3 available:

ps.2: Just found the issue.... The G31 command for the probe had a comment without the ";" so it did not read that line.... Sorry.. MY fault.

Did some tests and for sure after upgrading from 2.02RC6 to 2.03beta3 it puts the nozzle and not the z-probe when using G32 (that I use to align both leadscrews) and G29.

config.g and bed.g attached.

[0_1553976980746_config.zip](Uploading 100%)

ps.: Downgraded to the latest stable (2.02) and have the same issue!

Your upload failed. Please try again. Meanwhile, check that your G31 command is later in config.g than your M558 command, and that you don'r have G31 commands in config-override.g.

[dc42]

@zerspaner_gerd said in Duet firmware 2.03beta3 available:

Is that a security measure that only large M650.G filename extension can be created?

Go to Settings/User Interface and uncheck "Always convert G-codes to uppercase".

[zerspaner_gerd]

@dc42 said in Duet firmware 2.03beta3 available:

Go to Settings/User Interface and uncheck "Always convert G-codes to uppercase".

Does not make a difference for me!

[Iamturbo1978]

I've ran a few 8-12 hour prints with my coreXY printer. No issues to report at this time. Now to try a 20+ hour print. Thank you for the continued support.

[dc42]

@zerspaner_gerd said in Duet firmware 2.03beta3 available:

@dc42 said in Duet firmware 2.03beta3 available:

Go to Settings/User Interface and uncheck "Always convert G-codes to uppercase".

Does not make a difference for me!

Earlier today I created a file called m650.g without any problem.

[brunofporto]

@dc42 The problem is already solved and was my mistake - nothing related to the beta that is running smoothly since. Thank you!

The problem was that after the command I have a comment and when I updated the Z calibration of my z-probe I deleted the " ; " in front of the comment. The firmware smartly ignored that line and that leads to the issue.

Would be nice if the firmware warned me about ignored lines

Also, another thing is bothering me. I do use the filaments management and inside the config.g of each filament I have only three parameters: pressure advance, firmware retraction and filament monitor parameters. IT loads the config.g correctly when I load the filament using DWC but if the printer is restarted or turned off and on again these configurations are not applied (eg. pressure advance is zero after a reset). Even when M703 is present at the tool config file. I need to mannually execute M703 to lad the current filament configuration.

[Phaedrux]

@brunofporto said in Duet firmware 2.03beta3 available:

I need to mannually execute M703 to lad the current filament configuration.

I'm not exactly sure what the intended behaviour is, but as a work around you could try adding M703 to the end of the main config.g, or the end of config-override.g if you use it?

[zerspaner_gerd]

@dc42 said in Duet firmware 2.03beta3 available:

@zerspaner_gerd said in Duet firmware 2.03beta3 available:

@dc42 said in Duet firmware 2.03beta3 available:

Go to Settings/User Interface and uncheck "Always convert G-codes to uppercase".

Does not make a difference for me!

Earlier today I created a file called m650.g without any problem.

Correct,
If a small "m" is written, the "g" also becomes small

m350 -> small m350.g
M350 -> big M350.G

[brunofporto]

@phaedrux I think that should do it! The intended behavior is keeping the configurations between turn offs and resets.

Thank you!

[dc42]

@zerspaner_gerd said in Duet firmware 2.03beta3 available:

@dc42 said in Duet firmware 2.03beta3 available:

@zerspaner_gerd said in Duet firmware 2.03beta3 available:

@dc42 said in Duet firmware 2.03beta3 available:

Go to Settings/User Interface and uncheck "Always convert G-codes to uppercase".

Does not make a difference for me!

Earlier today I created a file called m650.g without any problem.

Correct,
If a small "m" is written, the "g" also becomes small

m350 -> small m350.g
M350 -> big M350.G

Quite so - how strange! It's the same in DWC 1.22.6 and 2.0.0RC6. But after created M654.G, I find I can rename it to M654.g.