Software releases

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


Version 2.2.2

  • Added support for SC2X.

Update file

Copy the v2.2.2g3 update tarball file to the big SD card, power on the camera, and wait around 7 minutes for the camera to finish updating.

The g3 release resolves a dark line issue which was noticed on some SC2+ and SC2X cameras and add overclock support for SC2+ and SC2X cameras.

Version details

Build host: edge-vm
Built by: edgertronic
Build date: 20171022224256
Build tag: ssc1
Build hash: fdce23e
Build version: v2.2.2g3

Release Notes

Improvements since software release version 2.2.1:

  • Overclock support for SC2+ and SC2X similar to SC1 overclock support.
  • Improved web U.I. response time when configuring camera.
  • Reduced time from post trigger buffer full until the next multishot can be triggered. Time reduced to around 100 ms.
  • Improved SC2 and SC2+ image quality by reducing image sensor noise.
  • Clean up user supplied configuration file line endings when the files are installed into the camera.
  • Added support to pipelines file to allow preview while saving to be disabled to improve file save performance.
  • Improved camera temperature range for a few cameras that didn't tolerate colder temperatures. Thanks to the Boise camera owner who reported the problem.
  • Fixed defect where in review mode if you relocate the status boxes then would jump around to a different location.
  • Improved user experience when using the overlay notes helper buttons to add camera specific information to the notes field.
  • Fixed defect where the web UI didn't work properly if the cookie was in an unexpected format. No clue how that customer created a browser cookie in an unexpected format.
  • Added support for keyboard control when in review before save. Tab, space, left arrow, right arrow, page up, and page down now allow the review sliders to be controlled via the keyboard. This is helpful in sunlit areas when the laptop screen is hard to read.

Resolved defects

  • 20170401123456 User supplied configuration files with DOS line endings are ignored

SDK API changes

  • None

Developer changes

  • Enabled DOS/Unix line ending conversion tools.
  • Reduced DHCP client daemon logging when no DHCP server is available.
  • Added support for adjusting the shutter servo movement.
  • Read the image sensor, FPGA, and DRAM temperature sensors when the trigger occurs instead of when the save starts. This can make a difference if the save was interrupted due to full storage.
  • Increased web U.I. EULA and software release button size and coloring.
  • Cleaned up startup scripts so logging is done is a consistent manner.
  • Allow the video filename extension to be specified in the pipelines configuration file.
  • Improved CIFS support.
  • Fixed FTP daemon initialization so FTP can be used to transfer video files.
  • Web server marks version file as text so contents are displayed instead of file being downloaded.

Known defects

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

20170823081416 Network multicast trigger not working

If you add a multicast-trigger.conf user supplied Configuration File the camera will not properly boot. You will not be able to browse to the camera.

Work around:

  • Request a custom camera firmware build. The problem has been fixed but we didn't have enough testing to feel comfortable including it in the v2.2.2 release.

20170802174312 Using the buttons to add parameters to overlay notes field are not shown on overlay

In the settings model, overlays tab, click on any of the white note parameter buttons, like Trigger Time, and then click outside the modal to close the setting box. The added parameter does not show up in the notes overlay on the video.

Work around:

  • After adding a parameter, click inside the notes field and use the keyboard to make a change (like add a space character).

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 no 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

All cameras can safely downgrade to version 2.2.1. Software versions older than 2.2.1 have been removed due to hardware changes that make older version incompatible with some cameras.

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:

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

Requested feature

  • Sound based triggering - This will not be supported as there are very powerful trigger accessories like TriggerTrap
  • Halogen color temp setting - Because of the decreased use in halogen lighting this feature is less useful over time.
  • Multi-trigger in multi-shot capture - Trigger capturing the next video while the current video is being captured, with no frames being dropped.
Personal tools