RepRapFirmware 3.01beta1 released

dc42

@kraegar said in RepRapFirmware 3.01beta1 released:

And removing the nested if's to replace with && crash it

Thanks, I've reproduced the crash by adding that line to my own script. I will look into it. Even if you do make a syntax error, you should get a helpful error message.

PS - now I know that the new crash handler I added for uncaught exceptions works!

Last software reset at 2020-01-15 16:35, reason: Terminate called, spinning module GCodes, available RAM 9464 bytes (slot 2)

kraegar

Trying to test if move.initialDeviation.deviation is 0.000

if move.initialDeviation.deviation != 0
  echo "one " ^ move.initialDeviation.deviation

I've tried using 0.000 as well, with the same result. == 0.000 or == 0 doesn't match, even though it is.

(I'm trying to determine if leveling has been run at all yet, my only clear method for now is to see if initial and calirbated deviation and mean are all 0.000)

dc42

Just done some tests. There is a problem with equality between floats.

The other problem you had is because the GCode line was too long. I changed it to throw an exception when that happens, but the exception isn't caught.

This is all very new code, so I was expecting some bugs.

kraegar

Yep, I'm just playing, happy to just keep reporting. Variables will clean the code up a lot, but that's a big ask

kraegar

Once variables are implemented, if they're "system wide" and not constrained to the macro they're called in, I would set a "is_level = false" in config.g, and set to true once leveling is run. Negating the need for this method of checking.

But I can't resist playing

dc42

Thanks for your reports. These two issues are now fixed in the latest builds at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0.

kraegar

Can I just say, HUGE thank you!
I've already made a script to tune PA, Temp, and Extrusion % (just call the macros via layer change) as well as the auto-leveling and a "pre-print" systems readiness check.

This is amazing!

kraegar

Float comparisons are now working, and the other errors gracefully:

Error: in file macro, line 20 column 1: GCode command too long

Thanks!

dc42

Thanks for confirming. FWIW, maximum GCode line length excluding leading white space, line number and checksum (if present) and comments is currently 160 characters.

kraegar

We're going to need line numbers in the file editor in DWC now

4lathe

Can I use that new duet2combinedfirmware.bin on my maestro? The 3.01 was duetmaestrofirmware.bin.

DIY-O-Sphere

@4lathe
It's still DuetMaestroFirmware.bin

DIY-O-Sphere

@dc42
Hi David, maybe I have found a bug....
For testing I was back on 2.05 on a Maestro (DWC 2.06) and I was not able to get back directly to 3.01b.
Flashing 3.0 stable worked.

dc42

@DIY-O-Sphere said in RepRapFirmware 3.01beta1 released:

For testing I was back on 2.05 on a Maestro (DWC 2.06) and I was not able to get back directly to 3.01b.

Read the upgrade notes!

gtj0

@dc42 said in RepRapFirmware 3.01beta1 released:

Thanks for confirming. FWIW, maximum GCode line length excluding leading white space, line number and checksum (if present) and comments is currently 160 characters.

Are you sending them via text message???

DIY-O-Sphere

@dc42 said in RepRapFirmware 3.01beta1 released:

Read the upgrade notes!

Sorry....The one who can read is in advantage

dc42

@gtj0 said in RepRapFirmware 3.01beta1 released:

@dc42 said in RepRapFirmware 3.01beta1 released:

Thanks for confirming. FWIW, maximum GCode line length excluding leading white space, line number and checksum (if present) and comments is currently 160 characters.

Are you sending them via text message???

Hadn't you noticed your smartphone bills going up every time you print?

gtj0

@dc42 said in RepRapFirmware 3.01beta1 released:

@gtj0 said in RepRapFirmware 3.01beta1 released:

@dc42 said in RepRapFirmware 3.01beta1 released:

Thanks for confirming. FWIW, maximum GCode line length excluding leading white space, line number and checksum (if present) and comments is currently 160 characters.

Are you sending them via text message???

Hadn't you noticed your smartphone bills going up every time you print?

Ah that makes sense now. I though it was the cat texting his buddy across the street.

garyd9

@kraegar said in RepRapFirmware 3.01beta1 released:

Here is the version that works well:

I like this, but it seems unnatural to have to repeat the same G30 commands twice in the same script. This is more significant with a delta printer (that often has many more probe points.)

I'm wondering what alternatives might exist. I see there's no do/while (which would be my first thought), but I'm wondering if it would work to put the list of G30 gcodes in a different file (bed-probes.g)

@dc42, do the variables from the object model available survive across different scripts? For example, if I had file called "bed-ProbePoints.g" that contained something like:

G30 P0 Xn Yn 
...
G30 P18 X0 Y0 S6

And then my bed.g contained:

M561
G28
M98 P"bed-ProbePoints.g" 
while true
    if iterations > 5
        abort "something needs tightening..."
    if abs(move.initialDeviation.deviation - move.calibrationDeviation.deviation) <= 0.01
       break
    M98 P"bed-ProbePoints.g"

Would this work? Would the deviation values be updated across the scripts?

Thank you
Gary

kraegar

@garyd9 This was my very rough first iteration (and still is early, room for improvement, etc etc). Only posted in this thread due to the bugs I was noticing.

Anyway, see my post here where I did split the G30 segment out into a macro:
https://forum.duet3d.com/topic/13890/auto-tramming-a-railcore-using-conditional-gcode