owlcms-firmata 2.0.6

Changes since 2.0.0

• 2.0.6: fixed the configuration selection to work on Linux and Raspberry Pi.
• 2.0.5: clientId now less than 23 characters to prevent spurious error message in owlcms
• host/port/username from last connection are saved and restored on next start
• The Windows setup was not copying the default configuration files to the owlcms/devices directory in the user HOMEDIR.
• The detection of the remote platforms has been made more robust.
• The default port is now 8090 to avoid conflicts with owlcms

Release 2.0

• Complete rework of the user interface

  • See the INSTRUCTIONS.md file in the repository

• A single instance of the program can handle multiple connected devices

• Detection of the connected devices.

• The name of the firmware is used to locate the matching configuration file by default.

Known issues

• If several browsers are run at the same time display between browsers will not be synchronized. Normally only one at a time is needed anyway.

owlcms-firmata 2.0.5

Changes since 2.0.0

• clientId now less than 23 characters to prevent spurious error message in owlcms
• host/port/username from last connection are saved and restored on next start
• The Windows setup was not copying the default configuration files to the owlcms/devices directory in the user HOMEDIR.
• The detection of the remote platforms has been made more robust.
• The default port is now 8090 to avoid conflicts with owlcms

Release 2.0

• Complete rework of the user interface

  • See the INSTRUCTIONS.md file in the repository

• A single instance of the program can handle multiple connected devices

• Detection of the connected devices.

• The name of the firmware is used to locate the matching configuration file by default.

Known issues

• If several browsers are run at the same time display between browsers will not be synchronized. Normally only one at a time is needed anyway.

owlcms-firmata 2.0.4

Changes since 2.0.0

• host/port/username from last connection are saved and restored on next start
• The Windows setup was not copying the default configuration files to the owlcms/devices directory in the user HOMEDIR.
• The detection of the remote platforms has been made more robust.
• The default port is now 8090 to avoid conflicts with owlcms

Release 2.0

• Complete rework of the user interface

  • See the INSTRUCTIONS.md file in the repository

• A single instance of the program can handle multiple connected devices

• Detection of the connected devices.

• The name of the firmware is used to locate the matching configuration file by default.

Known issues

• If several browsers are run at the same time display between browsers will not be synchronized. Normally only one at a time is needed anyway.

owlcms-firmata 2.0.3

Changes since 2.0.0

• The Windows setup was not copying the default configuration files to the owlcms/devices directory in the user HOMEDIR.
• The detection of the remote platforms has been made more robust.
• The default port is now 8090 to avoid conflicts with owlcms

Release 2.0

• Complete rework of the user interface

  • See the INSTRUCTIONS.md file in the repository

• A single instance of the program can handle multiple connected devices

• Detection of the connected devices.

• The name of the firmware is used to locate the matching configuration file by default.

Known issues

• If several browsers are run at the same time display between browsers will not be synchronized. Normally only one at a time is needed anyway.

owlcms-firmata 2.0.2

Changes since 2.0.0

• The Windows setup was not copying the default configuration files to the owlcms/devices directory in the user HOMEDIR.
• The default port is now 8090 to avoid conflicts with owlcms

Release 2.0

• Complete rework of the user interface

  • See the INSTRUCTIONS.md file in the repository

• A single instance of the program can handle multiple connected devices

• Detection of the connected devices.

• The name of the firmware is used to locate the matching configuration file by default.

Known issues

• None, but this is a brand-new release, so test accordingly.

owlcms-firmata 2.0.1

Changes since 2.0.0

• The Windows setup was not copying the default configuration files to the owlcms/devices directory in the user HOMEDIR.

Release 2.0

• Complete rework of the user interface

  • See the INSTRUCTIONS.md file in the repository

• A single instance of the program can handle multiple connected devices

• Detection of the connected devices.

• The name of the firmware is used to locate the matching configuration file by default.

Known issues

• None, but this is a brand-new release, so test accordingly.

owlcms-firmata 2.0.0

Changes since 2.0.0-alpha01

• Internal code clean-up only, cleaner logging messages.

Known issues

• When running on Windows after using the installer, the program fails when run for the first time and the configuration files are not copied from the installation.
  Workaround: copy the configuration files manually from the app/devices folder in the installation directory (right-click on the icon to open it).

Release 2.0

• Complete rework of the user interface

  • See the INSTRUCTIONS.md file in the repository

• A single instance of the program can handle multiple connected devices

• Detection of the connected devices.

• The name of the firmware is used to locate the matching configuration file by default.

owlcms-firmata 2.0.0-alpha01

New in this release

• Complete rework of the user interface
• A single instance of the program can handle multiple connected devices
• Detection of the connected devices.
• The name of the firmware is used to locate the matching configuration file by default.
• See the INSTRUCTIONS.md file in the repository

Known issues

• None, but this is a brand-new release, so test accordingly.

owlcms-firmata 1.3.4

New in this release

• Interference between owlcms applications has been fixed.
• The port names are now shown so that it is easier to run multiple devices on the same machine

To create your own device mappings:

1. Use the .xlsx files below. The files are also available in the installation directory, in the app/devices folder

2. The configuration file is uploaded using the user interface. Keep your definitions in a safe place.

   Note: If you install a new version of the package, you need to copy your definitions again (unfortunately we cannot change that behavior).

To run on Windows download and run the .exe installer below.

• This will create a desktop icon and start menu entries.
• To uninstall, use the "Installed App" system settings menu.

To run on macOS or Linux

You currently have to install Java 17 once, beforehand. Instructions for installing Java on macOS are found here. You can download the .pkg file from here -- select aarch64 if you have a recent M1 or M2 Mac. The JRE package is sufficient. For Linux, OpenJDK is available as an apt package (openjdk)

Then download the .jar file below and run.

java -jar owlcms-firmata.jar

owlcms-firmata 1.3.2

New in this release

• Workaround for running several owlcms/owlcms-firmata applications on same machine

To create your own device mappings:

1. Use the .xlsx files below. The files are also available in the installation directory, in the app/devices folder

2. The configuration file is uploaded using the user interface. Keep your definitions in a safe place.

   Note: If you install a new version of the package, you need to copy your definitions again (unfortunately we cannot change that behavior).

To run on Windows download and run the .exe installer below.

• This will create a desktop icon and start menu entries.
• To uninstall, use the "Installed App" system settings menu.

To run on macOS or Linux

You currently have to install Java 17 once, beforehand. Instructions for installing Java on macOS are found here. You can download the .pkg file from here -- select aarch64 if you have a recent M1 or M2 Mac. The JRE package is sufficient. For Linux, OpenJDK is available as an apt package (openjdk)

Then download the .jar file below and run.

java -jar owlcms-firmata.jar