Version 2.2.01 is available now. This patch contains a number of updates and bug fixes, including several improvements to EZCad3 support, listed below.
Existing Feature Updates
- Help > Report a Problem offers Suggest a Feature, Troubleshooting and Report a Bug, and bug reports attach the open project
- Accelaser network discovery and galvo framing
- Acclplanner v0.31.2
- EZCad3 laser status checks follow the Disable Laser State Check and Check Laser State When Marking settings from the imported config
- EZCad3 UV and YAG cut settings use pulse width and frequency in place of power, as EZCad3 does
- EZCad3 laser power follows the Power Map from the imported config
- EZCad3 red pointer uses the laser serial command on UV, YAG, CO2, SPI and some IPG fiber sources
- EZCad3 config imports convert inch configs to mm, read the stop marking input, and bring in internal galvo correction only when EZCad3 uses it
User Interface Updates
- Head camera alignment verification zooms in on the area the camera sees
- Continuous Jog toggle in the camera alignment wizard, on devices that support it
- EZCad3 Laser Type list offers UV/YAG for UV devices, and drops None and UV
- EZCad3 FPK settings are labelled as pulse widths in µs
Performance Improvements
- Camera calibration preview image processing runs on the render thread
Bug Fixes
- LightBurn could fail to start on Windows with Smart App Control enabled
- Quitting could crash or hang
- Importing a JPEG with a CMYK color profile could crash
- xTool, Creality Falcon and Duet devices could crash if LightBurn closed during an upload
- The Extensions tab in Galvo Device Settings misbehaved
- Camera preview could freeze after a reconnect
- Camera alignment wizard crashed when importing an Image-mode Material Library entry
- Camera alignment patterns could show bi-directional scanning offsets
- Camera alignment wizard hid Power in favor of Q-Pulse on sources that support both
- Head camera manual alignment kept points clicked before a jog
- xTool S1 reported an open lid as a “cover open” console error in place of a “Lid opened” message
- EZCad3 UV and YAG machines showed a false Temperature alarm and could not start jobs
- EZCad3 UV and YAG machines got fiber power commands with no pulse width, frequency or laser enable, and could not mark
- EZCad3 SPI and some IPG fiber sources could report the wrong laser alarm
- EZCad3 SPI laser sources got no frequency command
- EZCad3 CO2 and YAG sources with a maximum frequency of 20 kHz or less used the wrong time base
- EZCad3 lasers with a maximum frequency of exactly 1000 kHz used the wrong pulse clock
- EZCad3 PWM On Delay values were always sent as the longest possible delay
- EZCad3 Laser On Lag Time never reached the controller
- EZCad3 machines with 18 or 20 bit galvo scanners got the wrong scanner range
- EZCad3 configs with an SPI or QCW laser source could not be imported
- EZCad3 fiber config imports left Q-Pulse Width off even when EZCad3 had pulse width enabled
- EZCad3 config imports put the laser ready input port into the Ready Light, so an unrelated output switched on and off every job
- EZCad3 config imports reversed the start marking and start framing input polarity, so a foot pedal started jobs on release in place of press
- EZCad3 config imports lost a mirrored galvo axis
- EZCad3 start framing polarity and hardware fly settings from imported configs had no effect