Page MenuHomeAleph Objects Inc

several unknown commands in gcode produced by CURA LE to mini
Closed, ResolvedPublic

Description

Im not sure why cura LE is producing GCODEs which then seem to be not understood by the selected printer as a mini in this case.

In particular I see in the log:
echo:Unknown command: "G21"

and
echo:Unknown command: "M425 Z"
echo:Unknown command: "M425 Z F0"

and
echo:Unknown command: "M73 P0"

The first one is odd since that Gcode is supposedly just setting to millimeters
The second two of M425 I have not found what they mean.
The last one is a progress update - and maybe is meant to be displayed - except this printer doesn't have an LCD and the LCD box is not checked - so if the mini doesn't understand this command - not sure why cura uses it in the slicing/gcode creation..

Event Timeline

marcio added a subscriber: marcio.Thu, Jan 10, 7:51 AM

M425 - Backlash compensation, custom GCODE not present in upstream Marlin 1.1.9.
M73 - Set print progress, not present in upstream Marlin unless LCD_SET_PROGRESS_MANUALLY is set.

What version of FW are you using and where did you get it?

I thought I was using the most up to date firmware and just updated from cura I think.
checking..

hmm - how do I check which fw version.. I see where I can upgrade automatically (which I think I did before) or custom, but I don't see it reported..

If you click the "Console" button in Cura under the Monitor tab and type M115 it will give you info. Just paste all that info into this ticket,

ok - looks like G115:
and it has 1.1.9.28

10:23:58] M115
< [10:24:00] FIRMWARE_NAME:Marlin FIRMWARE_VERSION:1.1.9.28 EXTRUDER_TYPE:Aerostruder SOURCE_CODE_URL:https://code.alephobjects.com/diffusion/MARLIN PROTOCOL_VERSION:1.0 MACHINE_TYPE:LulzBot Mini EXTRUDER_COUNT:1 UUID:351487b6-ca9a-4c1a-8765-d668b1da6585
< [10:24:00] Cap:SERIAL_XON_XOFF:0
< [10:24:00] Cap:EEPROM:1
< [10:24:00] Cap:VOLUMETRIC:1
< [10:24:00] Cap:AUTOREPORT_TEMP:1
< [10:24:00] Cap:PROGRESS:0
< [10:24:00] Cap:PRINT_JOB:1
< [10:24:00] Cap:AUTOLEVEL:1
< [10:24:00] Cap:Z_PROBE:1
< [10:24:00] Cap:LEVELING_DATA:1
< [10:24:00] Cap:BUILD_PERCENT:0
< [10:24:00] Cap:SOFTWARE_POWER:0
< [10:24:00] Cap:TOGGLE_LIGHTS:0
< [10:24:00] Cap:CASE_LIGHT_BRIGHTNESS:0
< [10:24:00] Cap:EMERGENCY_PARSER:1
< [10:24:00] Cap:AUTOREPORT_SD_STATUS:0
< [10:24:00] Cap:THERMAL_PROTECTION:1
< [10:24:00] ok P15 B4

It looks like those features were not in fact enabled in that FW. We are evaluating what our next steps are. Thanks for reporting this!

karrad added a subscriber: karrad.Thu, Jan 10, 2:14 PM

@derbartman Okay, looks like we have some answers for you!

Unkown Command G21: This command is only required when compiling firmware with inch support on, which we do not. This is a superfluous command and has been removed from all start gcodes in T4945

Unknown Command M73 P0: This command is used to set the GLCD timer, and will be ignored if one is not present. We have instructed marlin to ignore this for machines without an LCD screen in 1.1.9.34

Unkown Command M425 ZX: This is a custom command that compensates for backlash in the Z direction. We had a misspelled variable when compiling, and this was not implemented on accident. This was turned back on in 1.1.9.34, and should stop throwing those errors.

I have attached the fixed firmware if you would like to give it a try. First go to Preferences > Configure Cura > Allow Connections to wrong machines (This firmware version will not match what is included in Cura LE currently)

Then go to Machine > Manage Printers > Update Firmware > Upload Custom Firmware and select the attached .hex file from where you downloaded it.

We plan to run some tests internally before pushing live, but this should get you taken care of. If you would like to get some early testing in, we would love to hear what you think!

karrad claimed this task.Thu, Jan 10, 2:15 PM
karrad triaged this task as Normal priority.
karrad moved this task from Backlog to Next Release (3.6) on the Cura LulzBot Edition board.

ok - I just tried the same print as before and I see no "Unknown" in the log so that's great!

I will say I am/was a bit confused about the firmware install - it was very unclear to me if I should or should not upgrade the EEPROM when doing the firmware update - when should I or should I not do that - the UI screen and the web description of the process seem to be light (understatement) on this detail. Also - I think I read that we no longer need to re-set the e-steps and Z-offset, but it says I should in that pop up firmware screen..

Also - the printing seemed to go ahead even though I didn't check the box on allow connections to wrong machines.. does that mean something to us - like does that mean I did it wrong or such.

- just uploading this as the example that I no longer see those replies from the printer

Glad to hear those errors got sorted! They were not causing any harm or negative affects, but surely annoying.

it was very unclear to me if I should or should not upgrade the EEPROM when doing the firmware update

We have included a checkbox that will automatically do this in Cura now, can you point us to where those directions still live? We thought we had removed all those examples.

Also - I think I read that we no longer need to re-set the e-steps and Z-offset, but it says I should in that pop up firmware screen..

This will be Dependant upon the printer, and if you unchecked the "update eeprom" box. If unchecked, you will not need to update that. If checked that and your steps/offset remain the same, it would indicate your printer was either reset to default w/o updating previously, or you are right in the sweet spot for the build variance. (We did a lot of testing, and set firmware defaults to the median values across 50+ machines)

Also - the printing seemed to go ahead even though I didn't check the box on allow connections to wrong machines.. does that mean something to us - like does that mean I did it wrong or such.

After first uploading custom firmware, the printer will connect automatically. The next time you try to power off and restart cura, you will likely see the warning without that box checked.

karrad closed this task as Resolved.Thu, Jan 10, 3:56 PM

https://www.lulzbot.com/learn/tutorials/firmware-flashing-through-cura

I think this describes how to save and re-assert those values, but it seems to be associated with software before this check box and I don't know If I should still follow these steps always, or only if I do the EEPROM check box , or never because the new SW takes care of it