Posts made by bforejt

@dc42 I didn't actually run an M450 prior to downgrading the platform, but I will finish up some work and then try the upgrade and report back here. Will perhaps take a while. That said, I'm guessing you are looking to ensure the board actually went into CNC mode and didn't stay in printer/laser mode, which is understandable.

I can tell you for certain that M3 (with the proper params) would start the spindle and M5 would stop it. I was playing with the M950 command to tie a fan header to the spindle relay, which was working also. I believe the only way M3/M5/M950 will work is if you are in CNC mode, so that is another indicator that CNC mode was actually active.

@dc42 We have our system in standalone mode.

Re: No movement when position command sent without G0/G1

I'm seeing the same issue as was mentioned in this post, with version 3.3 or 3.4b3. I can switch back to 2.05.1 and the issue disappears for the same GCODE CNC jobs.

For example, the following GCODE was generated by Carveco Maker, using their WorkBee postprocessor. (In inches here, but we also tried mm with the same result.) When I typed them in by hand, I noted that they all worked until the "Y" move. This and any subsequent Y move is ignored.

T1
G17
G20
G90
G0Z2.000
G0X0.000Y0.000
M3 S15000
G0X0.000Y0.000Z1.481
G0Y0.000
G1Z0.865F40.0
G1X5.400F115.0
Y0.100
X0.000
Y0.200
X5.400
Y0.300
.....

We found this out by trying to upgrade to 3.3 today, so as I mentioned we failed it back to 2.05.1 and the same jobs worked as expected. Definitely have M453 set in config.g. I also tried the Carveco Maker "GRBL" postprocessor generated files, same result. (And they generally seem to follow the same rules for creating GCODE, so really didn't look very different to me.)

If there's something off about these gcode jobs, I'll be happy to reach out to the Carveco folks for some guidance, but it would be helpful to know what needs changed. In the previous forum question I've referenced, it sounded like using this format is acceptable in CNC mode, so I'm not sure if this is a bug or perhaps a postprocessor issue.

Thanks for the support!

My version 3.3 config.g:
config.g