I created a file using Easel and exported as two gcode files. Bothe the rough cut and fine detail files are producing a lot of this one erro code. When it does the machine pauses and I have to hit continue in the Gsender software. The job eventually finishes but has defects in the carve. Are these errors a result of Easel or is this a problem with gSender? Is there and app I can pre-flight the code and fix these errors before I run the job?
I don’t know Easel. Do you pick a post processor when it produces gcode? Initial googling indicates that may not be a thing so we may need to manually tweak your gcode.
I like ncviewer to visualize gcode outside of the gsender environment. It’s easy to step through each line. That may help you identify the lines or command causing the issue.
24 appears to deal with a command not having an expected axis mentioned with it.
1 Like
I get the error 24 multiple times when doing 2.5D carves with SLB. I can run same files with original longboard without any issues.
Interesting data point.
Do either of you have a 4th axis installed or have turned the option on in the firmware?
@wcr What CNC do you have, Jim? When you create the gcode files, what post processor are you choosing?
I have the latest Longmill 2.5 with the Longboard that was sent with the starter package. I don’t get an option from Easel. I simply export the two files as gCode and import into gSender.
@wcr Interesting. I’ve never used Easel and the online docs that I can find are lacking in how to use it only as CAD/CAM and not as the code sender. Maybe someone here will be able to join in on how to choose the post processor it is using.
Since you have the LM 2.5, you are using the SuperLongBoard, not the LongBoard. Correct? If so, in gSender, you should be choosing the Hal option, not the grbl option. Are you doing that?
I don’t believe so. I see my error files have the grbl tag. Do I cghange in the firmware settings once I’m connected to machine?
I’m in the gSender software with machine connected and looking through the firmware setup and don’t see an option for HAL. Comm port and error logs show grblHAL only.
@wcr No, this is not a firmware change. Go to this page
and scroll down to the section on “connecting to your SLB”. Ensure that you select the option “use grblHal at 115200 baud” on whatever com port you are connected to.
Edit: we were typing at the same time. I misspoke. I should have said grblHal. Sorry about that.
1 Like
Before I saw this I changed the port from Com1 to Ethernet. I knew you were onto something when I saw all the red lines disappear from the preview. Job ran first bit without any errors and now running the detail file bit change without any hitch. Thanks.
@wcr I should have asked if you were connecting with USB or ethernet. Sorry about that. Since I connect with ethernet, you would think that would be an obvious question.
I’m glad that things are working for you now, though. I’ll close the topic, Jim.