Software release version 2.0

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

Version 2.0

Added genlock, overclock, and web user interface improvements.

Version details

Build host: contra-lx
Built by: tfischer
Build date: 20140911165611
Build tag: ssc1
Build hash: 7298f6b

Release Notes

  • Overclock support added.
  • Genlock support added.
  • Web user interface improvements, including movable button box and unmount feature which should be used before removing a storage device.
  • Disable trigger if there isn't enough room to store the captured video file.
  • External trigger has more predictable timing with the trigger time relative to the start of the trigger frame recorded in the metadata file.
  • 16 Gigabyte (16GB) DDR3 video capture memory support.
  • Storage unmount button
  • Trigger for external flash (may require external trigger controller)

Resolved defects

201401101440 - Web browser doesn't have the right aspect ratio when setting the height and width
The Web browser user interface does properly scale the live preview video images for some height and width values. The video is recorded correctly.

201312111442 - Video file metadata has user configured duration not actual video file duration
If you trigger the camera before the pre-trigger buffer is full, the duration reported in the video file metadata is wrong (issue #181).

201312111442 - Video file metadata has user configured duration not actual video file duration
The metadata file was updated to include several new key/value pairs including Frame count and Pre-trigger frames.

201312111058 When memory card is full playback and download buttons are inactive
You should be able to play the last saved video when the memory card is full, but the playback and download buttons are inactive (issue #179)

SDK API changes

  • Added get_camstatus() that includes the FPGA and image sensor temperature.
  • Added 'requested_overclock' and 'requested_genlock' to dictionary passed to configure_camera() along with API returning actual value used.
  • Defined status bits 18 and 19 to indicate no genlock signal and lost genlock respectively.
  • Added overclock and genlock information to default_setting.txt and the video metadata file.
  • Added get_caminfo() that returns camera information.
  • Added erase_all_files() to delete the video and metadata files from the storage device. It is recommended you do not use format_storage().
  • Added unmount() to verify all data has been written to the storage devices before they are removed.

Known defects

The following is the list of known defect in the version 2.0 release.

201409120935 Updating camera fails if there is a space in the update tarball filename

If you download the update tarball more than once, some operating systems put a space in the file name (e.g. " (1)" so the file being downloaded will have a unique filename. If you use the file with the space in the filename, the update will fail. To work around the defect, remove the big SD card, delete the file with a space in the filename and store the original file on the big SD card. The camera will then update correctly.

201409091802 Cancel trigger at the end of capture misbehaves

On occasion, if you cancel the trigger just as the post trigger capture buffer is being filled, the camera will calibrate then save the video data instead of properly handling the cancel. Simply trim the video to get back to filling the pre-trigger buffer.

201408271324 Genlock false triggers

This defect only occurs when using the Genlock feature with multiple cameras and a genlock cable.

Plugging in genlock cable may trigger both master and slave cameras. Unplugging genlock cable may trigger both master and slave cameras. Powering off a genlocked camera may trigger any other connected cameras.

201408260814 URL /trigger does not properly handle optional filename

If you pass an optional filename to /trigger, the filename is ignored.

201407211330 Refreshing browser during a save causes the camera's trigger bar to disappear

If the user refreshes the browser screen while the camera is saving video or while the post trigger bar is filling it will cause the trigger bar to disappear. The save progress bar will be visible and in most cases it will fill as normal but it may otherwise appear static. The camera's LEDs still work in this case so the user can see where the camera is in it's capture-save cycle.

201407011124 Unmounting the active storage device does not cause the camera to automatically switch to another storage device

If you unmount the active storage device, you have to first remove that storage device to get the camera to switch to using another installed storage device.

Work around: physically remove the device after you have unmounted it.

201406231552 IP address reported by file on SD card is wrong if the static IP address has been manually set

You can set the camera's static IP address by manually editing the /etc/network/interfaces file. When you take the network down and back up again, the camera's address changes, but the address reported by the file on the big SD card is wrong. The System LED that reports if a static or DHCP address is used; may give the wrong indication as well.

Thanks to Craig for reporting this defect.

201406180730 Device loses some settings during device software update

Settings stored in the micro SD card read/write partition are erased during a device update. Currently only manually configured network settings are stored in the read/write partition.

201312111624 File timestamp is in GMT

The camera was intentionally designed to use GMT for the timezone when saving video files. Some might consider this a defect (issue #182).

201312021613 Browser forward and back buttons may change camera settings

If you browse to another site and then use the browser back button to return to viewing the camera, your camera settings may have changed.

201311041114 Playing last recorded video can fail in rare cases

The camera will automatically switch which storage device is used when the current storage device fills up and another, non-full, storage device is available. You can not play the video recorded right before the switch occurs.

201311101454 CAMAPI does not detect new space on mounted storage device

CAMPI handles changes in storage status using an interrupt scheme (mdev). If your SD card is full and you telnet into the camera and delete some files, no event occurs, so CAMAPI doesn't detect there is now room and the memory full message is displayed.

Workaround: after deleting the files, remove and reinsert the storage device to create a change in storage status event.