Template:Software release version 2.5.3

From edgertronic high speed video camera
Jump to navigation Jump to search

Version 2.5.3

  • Better user experience when using a tablet to control the camera.
  • Improved accuracy in trigger time value. First set of measurements showed +/- 10 ms or better of accurate time when using stratum 1 NTP server.
  • Manual save mode for easier integration into a larger data acquisition system.
  • Detects and reports via webUI if an unsupported exFAT file system formatted storage device is installed.

Update file

Update your edgertronic camera by copying the v2.5.3rc31 update tarball file to the big SD card, powering on the camera, and waiting around 7 minutes for the camera to finish updating.

If you are updating from 2.4.1g6 or earlier, you will need to perform a factory reset after the update.

Version details

Build host: linux-vm
Built by: tfischer
Build date: 20240304145102
Build tag: ssc1
Build hash: 6dd23f0a
Build version: v2.5.3rc31

CAMAPI documentation

Python class exposing edgertronic CAMAPI via HTTP: v2.5.3rc27 documentation

Release Notes

Improvements since software release version 2.5.2:

  • Better settings layout on iPad to get rid of the extra whitespace. This resulted in a minor reordering of a couple of settings in the Options tab.
  • Changed reported trigger time from an integer to a floating point number. Tested the accuracy of the reported trigger using a stratum 1 NTP server connected on the local network. Improved how trigger time is captured to compensate for the non-real-time nature of the Linux operating system.
  • Improved memory BIST reporting.
  • Manual save mode for easier integration into a larger data acquisition system.
  • webUI detects and reports if an unsupported exFAT file system formatted storage device is installed.
  • The webUI help system now points to internet edgertronic wiki instead of cached wiki in camera.

Resolved defects

202309051411 Passing a parameterized filename via multicast trigger truncates filename at the ampersand character

If you include in the multicast trigger UDP packet a filename like behind_home_plate_inning_1_pitch_27_&T the actual file saved will be behind_home_plate_inning_1_pitch_27_.mov.

20210611094523 Factory reset may be required after camera software update

After updating to v2.5.1 or newer from a version v2.4.1 or older, you may need to do a factory reset after the update. The camera remembers all your customized camera settings during the update process. Somehow one of those settings is not being accepted by v2.5.1 or newer. Note that a factory reset will erase any custom interfaces file with a fixed IP address other than 10.11.12.13, which may cause you to temporarily lose your connection to the camera until you figure out which address is being used by the camera.

This is due to unmodified default configuration files being saved which keeps newer software releases from using their updated default configuration files. The defect was fixed by deleting unmodified configuration files before the new software runs, forcing the new software to install its default version of the configuration file. The issue caused problems due to an update to the lighttpd web server configuration file to work around an ipad security change.

This defect was resolve in release 2.5.2rc33, which wasn't widely distributed.

20220909151902 Camera doesn't properly handle the network gateway setting

This defect goes to show if you don't test properly, it likely won't work. Hope is not a successful develop strategy. I didn't have a complex enough network setup to test the gateway functionality. Now I do. This defect has been resolved.

202301083425 Camera wasn't properly reporting temperatures below freezing

When the camera internal temperature dropped below 0 Celsius, the calculation of the negative value wasn't done properly. This defect has been resolved.

20230214082349 CAMAPI cancel() doesn't propage changes made using reconfigure_run()

When in review-before-save mode, if you change the camera's settings via the webUI (or reconfigure_run()) those changes do not properly propagate to the future captures when you invoke the CAMAPI cancel() method. This defect has been resolved.

20230227173428 WebUI overclock setting not being handled properly on an SC2 camera

There was a javascript error when running with an SC2 8GB camera. This defect was introduced in a beta release, so most customers were not effected by the issue. This defect has been resolved.

SDK API changes

Developer changes

  • New manual save mode.
  • CAMAPI get_captured_video_info() trigger time is a floating point number instead of an integer and includes the anticipated filename that will be used unless overridden (e.g. via CAMAPI [selective_save() parameter). If the user parameter was set, then get_captured_video_info() returns the user parameter as well.
  • Metadata file reports trigger time as a floating point number instead of an integer.
  • Better logging of all allowed values when CAMAPI run() is invoked.
  • The update tarball is moved to the SD card installed directory instead of being deleted.
  • Potential backwards compatibility issue for software reading metadata files. The trigger time is now a float instead of an integer.
Retrieved from "https://edgertronic.mywikis.wiki/w/index.php?title=Template:Software_release_version_2.5.3&oldid=5710"