Just updated from 2.0 and now during my cutting on a Creality Falcon A1, the Air Assist stops midway through the cut.
I restarted from the beginning and it happened again. It had never done this with prior versions.
If you can reproduce it, try to export the gcode and upload it. Then we can check if it’s actually a command or something else.
It is reproducible. Here is the gcode for it. Thank you.
halloween.gc (466.4 KB)
You have your laser configured as Grbl LPC,
Any particular reason for that?
Go to Devices > select your profile and double click
Change from LPC to normal GRBL,
The device was set up that way since I began using it (2 months). I’ll try your suggestion. Thanks.
I changed the Device as you suggested, but the Air Assist still stopped. I have tried using my Macro to restart the air, but it failed to do so.
I just did the job using version 1.7.08. I had no issue with the Air Assist. This leads me to suspect the new version 2.0.00.
Ok could I ask you to save it the gcode from 1.7.08 and 2.0.01 and share those files?
If you can make them simple jobs (a couple of rectangles for example), it will be easier to notice any gcode differences.
Also if I could trouble you to export bundle configurations from both versions?
This will help us potentially reproduce the issue.
Thanks,
Jon
Okay. Thanks!
2001RC1.gc (358 Bytes)
1708.gc (276 Bytes)
I get an error at Forum when trying to upload bundles from each version.
That’s odd. @Rick can you check why that might be the case?
Thanks for the gcode, I’ll take a look to see what’s going on.
Hmm. Ok, I’m guessing it’s not the same project file you used, because the coordinates are different. I’m also noticing that your 1.7.08 file was generated with a GRBL-LPC profile as opposed to a GRBL profile in 2.0.01.
Otherwise, there is only a single line of difference, and that’s an extra G1 S0 before the M9 line in the 2.0.01 file.
Until @Rick can tell me why you can’t upload the .lbzip bundles to verify the configuration, I’m going to be spinning my wheels as to what differences there maybe between your 1.7.08 and 2.0.01 running profiles.
It is not the same file as I was asked to send files from a simple geometric shape. Earlier in the thread, I sent the original files.
The GRBL-LPC profile on v17… was how things were done until I was asked to change to just GRBL.
You may get a better understanding when you review the entire thread.
Thanks!
Oh I missed the original gcode file. My apologies.
Either way, the issue still remains if the M9 (air assist off) triggers before the end of the move sequence.
I still need to see the device configuration from 1.7 and 2.0 to verify that the conversion from 1.7 to 2.0 didn’t break or cause any changes in defaults.
No problem. Since I cannot upload the lbzip files, would a screenshot of each help you?
That would definitely be a good way to start.
Ideally if you can show me this tab in particular, that would be of great help:
Thanks
As mentioned with internal communication, there is a file size limit. Any file over 5mb should be hosted in the cloud and share a link, or send directly to support@lightburnsoftware.com, and include a link to this post for context.
Here are the links. Thanks.
Thank you!
I have to say I don’t quite grasp what the issue is here - the gcode generated seems to be consistent.
There’s an option in 2.0.01 that was set that adds an extra G1 S0
line, but that shouldn’t explain the issue you’re having from what I can see. We’re digging in deeper to understand this.