I’m already editing manually and it’s certainly not ideal! Search and replace is not so versatile as the GO destinations are different every time of course.
I am not familiar with the syntax of this statement:
replace with:
M5\n$0\nM3…
What is n&0?
I also have to retract the torch with a G0 Z20.00 command so there’s more to add.
Anyway, the whole point of trying to use LB was to get access to an efficient GCODE creator…or machine control solution (I’m happy to stop using MACH3 as it is a very busy environment - LB is much nicer I think, but may be not so ‘versatile’ for me?)
This is a regular expression (I’m also no expert, I need to google it every time )
It searches for every occurrence of a line starting with G0 (^G0.*) and replaces it with M5 + newline (\n) + the search string ($0) + newline (\n) + M3.
Hi everybody, apologies for the silence today but I have fallen foul of a forum rule that as a newbie you are not allowed to post more than ten messages on your first day…so I have not been able to respond…
There’s some inconsistency with names on LB I fear…you helpful guys have spoken about Machine settings…yet there are no ‘Machines’ in this system…there are ‘Devices’. Ok, so it’s a minor gripe but this sort of thing doesn’t help getting to the bottom of problems…This is no complaint against you guys because when you have a real ‘Device’ you then get ‘Machine Settings’ in the Edit menu… Device Settings appear to cover LB settings for a particular machine and Machine Settings give you access to programmable items in your machine (I think). I’m not sure why these can’t be all in the same menu then…
So, my initial problem was caused by me selecting 'Custom GCODE (Experimental) when I created my ‘Device’. Custom GCODE doesn’t add on/off commands in your GCODE despite me selecting GBRL-M3 in the Custom GCODE menu (Device Settings menu).
This evening I edited my Device to use a GBRL-M3(1.1e or earlier) laser controller and that then DOES add on/off commands between objects. Unfortunately (and I am astonished by this), my initial setup used Custom GCODE as my laser controller, and allows comprehensive custom GCODE (but doesn’t add on/offs between objects) and now that I found a setup that DOES add on/offs between objects, it DOESN’T allow comprehensive custom GCODE instructions!!! It only allows you to create custom GCODE scripts that run at the start of your code and at the end…and not during! Why for heavens sake? So how do I lift the torch up when it turns off so that it doesn’t drag across the work?
I think I might need to ask LB support to resolve this one.
By the way, once I had created a Device with GBRL-M3 as the laser controller, the Machine settings option appeared in the edit menu, as some of you predicted.
The menu will show the machine settings if they are applicable to the device. If you click on it and the machine is off-line, it will be a blank machine settings screen.
My fiber does not have machine settings.
@DamienWalker glad you got somewhere with the board… seems to come down to configuration.
Yes, that appears to be correct. The problem for me is that you get no visibility of all the features because they disappear if they are not available to a particular config. I feel that it is better to retain an item and grey it out than to make it disappear when it is not available…that way, the uninitiated stands a ghost of a chance of asking the right questions.
There must some logic to why they allow custom gcode in some configs, but not in others but I have yet to understand this. I will report back if I do, but I’m again questioning whether I can use LB because of this.
If you had multiple pages of configuration with half of them grayed out it wouldn’t help you much since the machine can’t use it… it also wouldn’t tell you have mis-configured your controller.
Trust me, this was more of a genius move and takes more coding.
There would be a ton of people wondering why they are grayed out… why can’t I use 3dslice on my co2 or diode type questions.
If it’s not applicable, then it’s not shown. If you can’t get it configured correctly, ask here, all are glad to help as most of these issues, if not operator induced, it’s likely a configuration issue.
Aha! you are a star and a gentleman! I had missed the requirement to disable tool state automatic and variable Laser power…My GCODE now looks good…so I’d best get out to the machine and try it!
Unfortunately, I now have a fault with my THC which I am struggling to get to the bottom of…so I can’t test my new code. As soon I have some news, I will update the thread. Thanks again!
)
