hello, I tried all the solution above, but still the xcarve lost the connection during the job, never at the spot.
PORT ERROR: Writing to COM port (GetOverlappedResult): Unknown error code 31.
- Change USB port (I tried 5 different port (USB2, 3, 3.1).
- turn USB port spleeping mode to disable
- Used different Gcode sender (easel, open build, transfer).
- change USB cable
To date, the issues is still present and I can’t run the job.
Could it be the arc generated by the drawing?
there is a similar error 31 in OpenBuilds thread on the OpenBuilds Forum over there: error code 31 | OpenBuilds
the solution in that case was to move the laptop itself away from the EMI source.
Here’s a list of the grbl error codes and their meanings for future reference
||Expected command letter
||G-code words consist of a letter and a value. Letter was not found.
||Bad number format
||Missing the expected G-code word value or numeric value format is not valid.
||Grbl ‘$’ system command was not recognized or supported.
||Value < 0
||Negative value received for an expected positive value.
||Homing cycle failure. Homing is not enabled via settings.
||Value < 3 usec
||Minimum step pulse time must be greater than 3usec.
||EEPROM read fail. Using defaults
||An EEPROM read failed. Auto-restoring affected EEPROM to default values.
||Grbl ‘$’ command cannot be used unless Grbl is IDLE. Ensures smooth operation during a job.
||G-code commands are locked out during alarm or jog state.
||Homing not enabled
||Soft limits cannot be enabled without homing also enabled.
||Max characters per line exceeded. Received command line was not executed.
||Step rate > 30kHz
||Grbl ‘$’ setting value cause the step rate to exceed the maximum supported.
||Safety door detected as opened and door state initiated.
||Line length exceeded
||Build info or startup line exceeded EEPROM line length limit. Line not stored.
||Jog target exceeds machine travel. Jog command has been ignored.
||Invalid jog command
||Jog command has no ‘=’ or contains prohibited g-code.
||Laser mode requires PWM output.
||Unsupported or invalid g-code command found in block.
||Modal group violation
||More than one g-code command from same modal group found in block.
||Undefined feed rate
||Feed rate has not yet been set or is undefined.
||Invalid gcode ID:23
||G-code command in block requires an integer value.
||Invalid gcode ID:24
||More than one g-code command that requires axis words found in block.
||Invalid gcode ID:25
||Repeated g-code word found in block.
||Invalid gcode ID:26
||No axis words found in block for g-code command or current modal state which requires them.
||Invalid gcode ID:27
||Line number value is invalid.
||Invalid gcode ID:28
||G-code command is missing a required value word.
||Invalid gcode ID:29
||G59.x work coordinate systems are not supported.
||Invalid gcode ID:30
||G53 only allowed with G0 and G1 motion modes.
||Invalid gcode ID:31
||Axis words found in block when no command or current modal state uses them.
||Invalid gcode ID:32
||G2 and G3 arcs require at least one in-plane axis word.
||Invalid gcode ID:33
||Motion command target is invalid.
||Invalid gcode ID:34
||Arc radius value is invalid.
||Invalid gcode ID:35
||G2 and G3 arcs require at least one in-plane offset word.
||Invalid gcode ID:36
||Unused value words found in block.
||Invalid gcode ID:37
||G43.1 dynamic tool length offset is not assigned to configured tool length axis.
||Invalid gcode ID:38
||Tool number greater than max supported value.
Thanks, I just bought another USB cord, and (cross finger) no more problem. Brand new USB are not equal apparently. The USB need to be as short as possible and got a ferite bulb at one end. The one provided with the Xcarve was apparently of very poor quality.