ODIN Firmware

On this page you can download images for the ODIN sensor. Currently there are two branches. The 1.3 and 1.4 branch. If you are not sure, which one you need, pick the 1.4 branch.

Flashing new firmware

Installation instructions:

1. Download the image.
2. Download a flash program  e.g. Balena etcher, rpi-imager, UNetbootin, dd …
3. Flash the image onto the µSD card. The card should have at least 16 GB size.
4. Plug in the µSD card into the sensor. The “up” side is facing the multi-purpose “DIN” socket.
5. Turn on the sensor
   • The first time it will automatically extract the firmware and format the µSD card, this takes some time. Afterwards the sensor tries to reboot.
   • If the µSD card has previously been used, the sensor will ask for  confirmation to format the main partition. If you deny, it might keep your files (and some of your changes). This is an implementation detail and might not work in the future, so save your files beforehand.
   • The sensor might not reboot properly, in that case, turn it off by long pressing the power button and turn it back on with a short press.
6. Finish.

Firmware-Images:

• ODIN 1.5.0
  Note: This firmware only works with sensor produced in 2024 (check the Copyright on the sensor label). If you have a sensor produced before, you can sent it in to us (see Imprint), and we will do the hardware upgrade of the sensor free of charge.
• VELOMIR 1.0.1

Current user manual:

• ODIN 1.5.0

In place update

1. Backup all files, all your data will be lost
2. To perform an in place update, copy the ODIN_OS.img from one of the download links on the right to the sensor, for example using an USB drive, wget or a network share.
3. Open the file manager on ODIN
4. Navigate to /boot (Filesystem root-> boot)
5. Delete the ODIN_OS.img present in the folder
6. Copy the new ODIN_OS.img into the folder. If you did not delete the original ODIN_OS.img beforehand, you might get an error about insufficient storage.
7. Extract the EXTRACT_FOR_RECOVERY.zip, e.g. with the archive extractor into the /boot folder, overriding the present BOOT.bin. The new file should be larger than the old one.
8. Reboot
   1. This takes long, as the sensor overrides the OS with the new version
   2. If asked to format, you CAN say no, this MIGHT perserve your data, but do not count on that. If you say yes, you get a completely clean OS.
9. The sensor reboots itself again, booting into the new firmware.
10. Confirm the update by launching ODIN control, clicking “Help”, “About”, and checking the version with the downloaded version.

Firmware ODIN_OS files:

• ODIN 1.5.0

Changelog

ODIN 1.5.0

• Added API to control the trigger pins from external software. The pins provide a resolution of 10 ns and run synchronous with the sensor image aquisition, allowing e.g. sorting with the sensor image data and external processing.
• Added a basic UI mode, (disable by clicking Help and unchecking the “Advanced mode” switch). This simplifies the handling and removes lot of UI clutter.
• Changed the blue color of the indication for the bw_feature_ attributes to increase readability of the text.
• Small detail improvements.

ODIN 1.4.6

• Fix typo when saving a experiment making it diffcult to load the regions in ODIN control or other software
• Fix a race condition when using the parameter log leading to mangled filenames. When the filename gets mangled, the log will be generated in the home directory
• Clicking on a region will change to plot to the parameters the region is defined in
• Loading of settings cannot enter an hang with malformed EXP files
• The input field for the path to store measurements was validating too strictly. Now it is possible to add “:” in the path. Note: This might be an invalid filename/foldername under Windows.
  This allows the use of GVFS mounted network paths for storing measurements. GVFS is used by the file manager when mounting SMB shares.
• Trigger pins could be switched in the software (Trigger 1 triggered by software Pin 1 and vice versa) this should now be correct.