Releases: nortd/driveboardapp
DriveboardApp
This is a general update of the DriveboardApp recommended for all users. It a minor update over v18.05 making the homing cycle a bit more tolerant to switch precision.
For a standard Lasersaur (Driveboard v14.03, Driveboard Element) everything should work out of the box. Simply download the binary for your platform and double-click it. On Linux you may need to make it executable first. On OSX you may have to Ctrl-click/open it to by-pass a security setting which disallows unsigned apps from being double-click opened.
NOTE: You will also have to run "Flash Firmware" from the UI.
For development, troubleshooting, non-standard machines you should run the app from sources. For this you need python 2.7 with the pillow package installed (raster engraving will fail without pillow). There are two levels on which to change configuration: firmware config files, and app config files. Firmware config files work as always. App config files can now be specified on the command line when starting the app. This makes it very comfortable to play with many custom settings.
Changes
- homing cycle backout move increased
DriveboardApp
This is a general update of the DriveboardApp recommended for all users. It is currently marked as a pre-release until we hear back from people using it successfully in a production environment.
Most changes are incremental improvements but some changes to the firmware and API have been made to make DriveboardApp fully ready for 3-axis applications. This update is also required for machines that run stepper drivers which need a delay after direction changes (DM542). This prevents loosing steps with these drivers.
For a standard Lasersaur (Driveboard v14.03, Driveboard Element) everything should work out of the box. Simply download the binary for your platform and double-click it. On Linux you may need to make it executable first. NOTE: You will also have to run "Flash Firmware" from the UI.
For development, troubleshooting, non-standard machines you should run the app from sources. For this you need python 2.7 with the pillow package installed (raster engraving will fail without pillow). There are two levels on which to change configuration: firmware config files, and app config files. Firmware config files work as always. App config files can now be specified on the command line when starting the app. This makes it very comfortable to play with many custom settings.
Changes
- Windows (driveboardapp.exe), OSX (DriveboardApp.dmg), Linux (driveboardapp)
- improved serial connection handling
- auto connects on usb plugin
- asks to upload firmware on vanilla arduino (CLI)
- revamped configuration files
- loads by default config.json
- has now --config option to load other configurations (CLI)
- has --list-configs to show available configs and config dir (CLI)
- flashing on Linux without having arduino-core installed
- many small optimizations
- revamped homing cycle, faster, better
- smaller, compressed job files (support for larger files on small computers), thx to @adammhaile
- firmware/API changes
- homing cycle improved
- homing works when machine is in limit stop mode
- homing can be configured towards any side
- see: CONFIG_INVERT_X_HOMING, CONFIG_INVERT_Y_HOMING, CONFIG_INVERT_Z_HOMING
- AIR, AUX1, AUX2 changed to AIR, AUX
- TABLEOFF, CUSTOMOFF is now just OFFSET (table offset is hardcoded in firmaware config file)
- more sophisticated ways to deal with offsets (for mapping G54 stuff), running proper retracts while offsets are defined, storing/restoring relative/absolute motion, etc
- see web.py low level API
- /retract
- /jog
- /move
- /supermove
- /offset
- /absoffset
- see web.py low level API
- milling mode with fusion 360 support (experimental)
- completely separate frontend (frontend_mill)
- to enable add a ""mill_mode": true" to your configuration file
- also a new parameter for rpms: "mill_max_rpm": 18000"
- fusion 360 post processing file in backend/jobimport/driveboard.cps
- eventually we can also make this work for laser work
Testing release with stepper direction delay code.
Some stepper drivers (e.g. DM542) seem to have problems running without delay after direction changes. This release includes code to add at least 25us after a direction change.
On Linux (currently the only binary package):
- download binary
- make executable
- right-click > properties > permissions > Allow executing file as program
- or
chmod +x driveboardapp
- double-click
MAKE SURE to click "Flash Firmware" in the burger menu of the UI to load the updated firmware to the controller.
The following describes the issue (but not the solution used here):
DriveboardApp
- self-contained cross-platform binaries
- Windows (driveboardapp.exe), OSX (DriveboardApp.dmg), Linux (driveboardapp)
- tuning of new beam dynamics code on Driveboard Element
- more robustness for bouncy door and chiller lines
- defaults to old beam dynamics code on Driveboard v14.03
- optionally new beam dynamics code on Driveboard v14.03 with /flash/driveboard1403sync
- optionally old beam dynamics code on Driveboard Element with /flash/driveboardusbstepped
DriveboardApp
- self-conteined binaries for Linux, Win, OSX
- GUI window for server backend (use option -c to run in terminal only)
- new json-based config file in permanent drivboardapp dir
- http-only status channel, websockets removed for more robustness
- firmware #-defines for upcoming DriveboardUSB hardware
- improved automatic serial port detection and automatic reconnect
- dynamic pwm frequency and duty cycle. (This solves perforation artifacts while still allowing very low intensity setting)
- AUX outputs reworked (AUX2 is now AUX, AUX1 removed)
- BUGFIX: image raster missing right end
- BUGFIX: intensity mapping (low power)
- BUGFIX: many small ones
First relase of packaged binaries.
- self-conteined binaries for Linux, Win, OSX
- new json-based config file in permanent drivboardapp dir
- http-only status channel, websockets removed for more robustness
- firmware #-defines for upcoming DriveboardUSB hardware
- improved automatic serial port detection and automatic reconnect