Firmware update¶
Update procedure¶
The
firmware.bin
file is copied to the root of theCONFIG/
volume (refer to Storage volumes).Safely eject the USB volume(s)
Power down the device
Power up the device via USB and wait a few minutes to let the device complete the update
Power LED will flash 5 times to indicate firmware candidate file found
Power LED will flash 5 times to indicate valid firmware file found
Power LED will flash 5 times to indicate firmware updated successfully
Enter the
CONFIG/
volume and delete thefirmware.bin
file (to avoid repeated updates)Open the device.json file to verify that the firmware was updated
Migrate the device configuration if the new firmware uses a changed configuration file1
Warning
It is important that the firmware.bin
file is deleted from the device after a successful firmware update to avoid repeated updates.
CANmod.temp Firmware Files¶
Changelog¶
# Change Log
All notable changes to CANmod.temp firmware will be documented in this file.
Types of changes:
- "Added": New features
- "Changed": Changes to existing functionality
- "Deprecated": Soon-to-be removed features
- "Removed": Removed features
- "Fixed": Bug fixes
- "Known issues": Known issues
- "Warning": Warnings
## [01.04.01] - 2022-04-08
### Changed
- USB always starts in dual mode, with both MSD and CDC active
### Added
- All messages sent by the device to the CAN bus is also mirrored onto the USB CDC port
## [01.03.01] - 2022-01-27
### Added
- Full temperature resolution CAN-bus outputs added
## [01.02.01] - 2021-08-16
### Changed
- Temperature output frequency increased from 1Hz to 5Hz
## [01.01.04] - 2021-05-07
### Changed
- Application not started if an invalid custom configuration file is located in the CONFIG volume (indicated by continuous toggling of the PWR LED)
- Clearer indication of CAN-bus activity on CH1 LED (yellow)
### Fixed
- Fix to how the thermocouple type is loaded from the configuration file
## [01.01.03] - 2021-04-08
### Known issues
- Does potentially not load thermocouple type correctly from configuration file
## [01.01.02] - 2021-04-08
## [01.01.01] - 2021-04-08
- 1
The firmware version numbering is
[MAJOR].[MINOR].[PATCH]
. If either the Major or Minor number has changed, then the device configuration needs to be migrated to the updated configuration file (namedconfig-[MAJOR].[MINOR].json
)