Why are their youtube videos describing how to do this for previous versions of light burn, and why did this feature get removed in this version of lightburn?
I linked to a previous lightburn message board help question post, in which they show a jpeg of where this setting used to be able to be found with in the lightburn software. I also included a jpeg of what my version of lightburn looks like. It seems to me that they are clearly different in feature and function.
I might be reading into what your saying, but are you suggesting that lightburn’s GUI populates / allows or restricts different features based on what controller the end user is using? That would be weird, but I suppose it’s not unheard of for software.
As a side note, what ever the controller can usually do, the Gui can do. Their are some times where the GUI can even access things that the controller can’t.
eg ( I couldn’t access the water read sensor signal data and choose to turn off the reading capability of it from the controller. I can how ever do this operation from the Lightburn GUI.
an example of how things are equal would be the ability to use Lightburn to move the X axis. the Controller can also do this. In other words the controller can do lots of different things Lightburn can access those things and some times a bit more.
To help sum it up, if the controller has a test fire button that can be physically hooked up to it, and it dose, then lightburn the software can also and should also be able to toggle this function.
I hope this helps with better understanding of the communications that go back and forth between your controller and the software that is lightburn.