Software releases

From edgertronic slow-motion video camera
Jump to: navigation, search

Contents

Version 2.2.1

Improvements over software release version 2.1.7:

Update file

You can get the update tarball file from:

Version details

Build host: contra-lx
Built by: tfischer
Build date: 20170224142314
Build tag: ssc1
Build hash: f5963b5
Build version: v2.2.1rc8

Release Notes

  • Added support for SC2 and SC2+ edgertronic cameras
  • Video overlay frame number, camera capture information, and company logo on each video frame in the movie file
  • Added saving and reloading favorite camera settings
  • Added selective save where a starting frame number and ending frame number can be specified
  • Added review mode when the video can be reviewed to select the starting frame number and ending frame number to save
  • Faster live preview frame rate
  • Improved lost connection handling
  • Version 2.2.0 was released on July 5th, 2016 but due to a change made by the DDR3 memory module supplier, the memory initialization algorithm didn't work for a few modules on SC1 cameras, so we pulled the release and SC1 camera have been shipping with version 2.1.7.
  • Metadata text file includes time since last calibration and additional temperature values measured at the time of the last calibration. Because the camera is always filling the pre-trigger buffer, the camera can track if it needs a calibration cycle, but it cannot calibrate since that would loose data in the pretrigger buffer. If the camera has been running for hours and the user knows they are about to capture data, it is recommended to call CAMAPI run() again. This can be done via the web U.I. by entering the configuration settings and immediately exiting without changing any settings.
  • Added human readable camera model string to web UI about tab, metadata file, and CAMAPI get_caminfo() dictionary model_string key.

Resolved defects since 2.1.7

  • 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 and the camera capture settings are stored in the read/write partition.

  • 201607151434 new DDR3 memory modules in SC1 camera may not initialize properly

Due to a change made by the DDR3 memory module supplier, the memory initialization algorithm didn't work for a few modules on SC1 cameras. The initialization algorithm was enhanced to work with the new memory modules.

SDK API changes since 2.1.7

  • Separated out constant values used in the python camera application to camconstants.py. Install camconstants.py into camera's file system in http://10.11.12.13/static/host directory. This is not a backwards compatible change. You will need to update any python programs that include hcamapi.py.
  • Simplified hcamapi.py so you no longer need to pass in a logger. This is not a backwards compatible change. You will need to update any python programs that include hcamapi.py.
  • Added favorites related methods to CAMAPI - get_favorite_ids(), get_favorite(), save_favorite(), and delete_favorite()
  • CAMAPI flags changed, unused flags deleted, new flags added to distinguish between storage media not present and storage media not mounted
  • Added CAMAPI mount() method
  • camstatus includes an event count. Each time the camera's state or status flags change the event count is incremented. The counter is reset at power on.
  • camstatus include a configuration count. Each time the camera settings are modified or favorite settings are saved, the configuration count is incremented. At power on, the configuration count is set to a unique number (based on the serial number) for each camera.
  • CAMAPI selective_save() method added to allow a subset of a captured video to be saved. The file name can also be specified. Available when requested_review key is set in the dictionary passed to CAMAPI configure_camera() and run() methods.
  • CAMAPI review_frame() method added to allow the host to retrieve the specified frame from the specified capture buffer. Available when requested_review key is set in the dictionary passed to CAMAPI configure_camera() and run() methods.
  • CAMAPI get_video_info() method added which returns a dictionary with the number of filled captured buffers, and the starting and ending frame in each buffer. Available when requested_review key is set in the dictionary passed to CAMAPI configure_camera() and run() methods.
  • Added review and selective save CAMAPI methods get_captured_video_info(), review_frame(), and selective_save() to hcamapi.py.
  • Added extract_metadata() method to hcamapi.py to read in a video metadata txt file into a python dictionary.
  • Updated hcamapi_example_usage.py to show how to use the new CAMAPI methods and to use camconstants.py.
  • CAMAPI configure_camera() and run() support requested_trigger_debounce dictionary key. If set, a 5ms trigger input debounce is enabled for external trigger. Enabled by default, which is a non-backwards compatible change meaning by default the camera will trigger 5sm later with this software update unless requested_trigger_debounce is set to 0 or False.

Developer changes since 2.1.7

  • New http://10.11.12.13/live URL support added so you can browse to the camera without causing a calibration. Useful for monitoring the camera when another computer is controlling the camera. Also useful in video booth where the client isn't allowed to modify any settings.
  • New http://10.11.12.13/ext URL to allow you to see what user added URLs are available.
  • Moved network handling to a later point in the boot process - this means the blinking yellow system LED stays around longer
  • Improved HTTP header fields to properly describe client cacheing options.
  • Added app_ext - more general solution to allow multiple user added extensions, hardware watchdog example provided favorites
  • Set fixed IP address via user provided network interfaces file
  • Change video capture / encoding via user provided GStreamer pipelines file
  • Set DNS server via user provided resolv.conf file
  • Added /live URL so you don't always have to configure/run the camera when you browse to it
  • Added CIFS (SMB, windows share) network storage support
  • Updated many of the software packages used internal to the camera
  • The /etc/version file now contains a text name for the software release
  • Image quality improvement by removing the 1.2 gain factor that was perviously applied to all pixels.
  • Switched python from pyo files to pyc files
  • Added favicon.ico
  • Simplified how storage change detection is implemented. Now uses web server /check_storage URL instead of the tcp socket 5472.
  • Adjusted memory map to accommodate large size video frames.
  • Removed wifi related packages since we don't support USB wifi dongles.
  • Enhanced servo control algorithm to increase servo life.
  • Support mechanism for adding file that will be run during power up.

Known defects

The following is the list of known defect in the version 2.1.x releases.

201607011045 Power on camera with USB storage may cause camera to not properly detect available storage

If you have a USB flash thumb drive or USB hard disk connected directly to the camera and turn the camera on, depending on the USB device, the available storage will not be detected.

Work around: There are several work arounds -

  • Use a powered USB hub between the storage device and the camera
  • Remove the USB storage device before powering on the camera
  • Remove and reinsert the USB storage device after the camera has powered on

201606301612 After factory reset or device update the system LED may report the incorrect network setting

The system LED may be left blinking yellow or blinking blue after a factory reset or device update.

Work around: Ignore the LED, remove the network cable, count to 15 and reconnect the network cable, or power cycle the camera.

201412161349 Multishot Genlock buffering can get out of sync due to power cycle or selective save

No fix defect -- there are no plans to fix this defect.

If you are in the middle of a Genlocked Multishot sequence and power cycle one of the cameras, the buffering will be out of sync once the camera is powered back on. Until the cameras configured for genlock talk to each other over the network cable, there is not way to resynchronize which multishot buffer is being used.

Work around: Power cycle all cameras that are configured and cabled for multishot and genlock.

Similarly, if you are in the middle of a Genlocked Multishot sequence and decide to save your video set, you cannot just press the save button on the Master camera's GUI since only the videos on the master will be saved.

Work around: you must press the save button on the master and all the slave camera GUIs.

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

No fix defect -- This is really not a defect.

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.

Work around: This is a race condition. The user thinks the camera is still capturing data when they press cancel, but in fact the camera has already switched to saving the captured video. Simply trim the video to get back to filling the pre-trigger buffer.

201408271324 Genlock false triggers

No fix defect -- there are no plans to fix this defect; the hardware design doesn't support any means to fix the issue.

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.

Work around: connect all genlock cables before powering on the cameras.

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

No fix defect -- there are no plans to fix this defect.

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.

Work around: The camera web user interface is not designed to work with the back / forward or refresh buttons. Avoid this defect by not using those browser features.

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.

201312111624 File timestamp is in GMT

No fix defect -- there are no plans to fix this defect.

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

No fix defect -- there are no plans to fix this defect.

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.

Work around: either don't browse to another web site or don't use the back button when you do; simply browse to the IP address of the camera.

201311041114 Playing last recorded video can fail in rare cases

No fix defect -- there are no plans to fix this defect.

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 since the active storage device has changed.

Work around: You can remove the storage device and properly play the video by retrieving the video file from the non-active storage device.

201311101454 CAMAPI does not detect new space on mounted storage device

No fix defect -- there are no plans to fix this defect.

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.

Older releases

Anticipated features

Let us know what features you would like to see added to the edgertronic high speed camera. Here are some requests we have received:

  • Over the network software update
  • Auto exposure where the camera helps you select the best ISO setting value.
  • Camera auto discovery on the network
  • User name and password to control who can browse to the camera
  • Underclocking (may improve image quality)
  • Image based triggering
  • Add support for <video> tag in HTML served up by the camera
  • Add support for camera telling web U.I. when a status change occurs
  • RAW support
  • User supplied gamma correction table.

Requested feature that will not be supported

Click on the links below to find out why the requested feature will not be supported.

  • Sound based triggering - Use Trigger Trap
  • Halogen color temp setting - decreased use in halogen lighting with the improvements to LED lighting mean the feature is less requested.
Personal tools