LW3 preconfigured profiles
What program is used to catch basic mouse movements in a slow frame rate? 
I used peek (https://github.com/phw/peek) at 15fps
Which branch can i find this profile feature?
master
@quillford Thx
+Peter van der Walt I agree but this is something we need to work out. There are a few very specific E2 features which are not needed by other users.
I am open to suggestions on how these are handled within master.
Perhaps the Emblaser branch is purely for UI and that is where the E2 features are revealed?
Calibration offset is something specific to each machine. It is a value that allows for small differences in customer machines and will be specific to a customer’s Emblaser. Its a one-off calibration made and then this value is stored for all gcode generation.
This value could be present in LW and by default set to zero. We could reveal it in the E2 branch for customers to set.
With respect to whether a customer uses a cutting mat (aka sacrificial board) and the thickness of their material, this can potentially be combined. So if they are using no mat and their material is 3mm thick, then its 3mm from the base to the top of the material. If they have a 10mm sacrificial board and 3mm material, then they could enter 13mm as their material thickness.
I am not sure what you mean by the material db.
LW4 has material databases which will save the materials and their settings for you to reuse rather than remember and renter every time
The calibration offset is commonly used in CNC machines. It’s also known as tool offset. There is really no difference between what we need and tool offset. I am not sure why this is considered deviating from standards?
We are certainly happy to re-think our approach to the specific requests we need. Making everything standard is definitely the way we want to go.
The E2 is not a standard CNC machine. It has some features that need a little more attention to make it as easy as possible to use for customers.
For instance, it has an optional air-assist nozzle attachment. When installed this limits the laser height movement to 10mm before it makes contact with the top of the material.
Do we help customers prevent this from accidentally happening by placing some logic in the software or do we keep everything standard and let accidentally them break their machine?
Our deviating requirements are mostly related to the fact our laser head can move up and down 50mm. I’m sure we can find some good standard compromises for this in LW.
+Peter van der Walt @Domenic_Di_Giorgio Peter, what is your proposal for Emblaser? Are you suggesting that Emblaser ship with the generic master version of Emblaser? The branch is supposed to be a release branch with code for emblaser-specific features. I wasn’t aware that you had objections to that. What is your alternative for getting a stable release for Emblaser 2?
+Peter van der Walt @Domenic_Di_Giorgio OK, well, I haven’t been very active on the merging lately, but let me see if I can help that out in the next few days (still traveling right now). Might make it better if we get them closer. I’m not trying to make Emblaser diverge much, but I don’t want to take a lot of new experimental features into it for stability. The comms stuff seems like good changes, though, and should be easy to merge. It should also be easy to merge the Electron changes back to master if you want them.