Difference between revisions of "Known defects"

From edgertronic high speed video camera
Jump to: navigation, search
m
(Replaced content with "{{Template:Known defects}} Category:Troubleshooting")
 
Line 1: Line 1:
= Software release 2.1 =
+
{{Template:Known defects}}
 
 
The following is the list of known defect in the version 2.1 release.
 
 
 
== 201412161349 Multishot Genlock buffering can get out of sync due to power cycle==
 
 
 
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.
 
 
 
== 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).
 
 
 
== 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).
 
 
 
== 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.
 
  
 
[[Category:Troubleshooting]]
 
[[Category:Troubleshooting]]

Latest revision as of 21:40, 29 March 2015

Known defects

The following is the list of known defect in the version 2.5.x releases. [1]

20190302135422 SC2 SC2+ SC2X pretrigger frame count inaccurate on when the pretrigger buffer is not full and a trigger occurs

If you trigger a SC2, SC2+, or SC2X camera before the pretrigger buffer fills, the metadata file will have an inaccurate number for the frames captured before the trigger event. This also effects review mode.

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.

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).

As of 2.4.1 you can create your own filename pattern and not use seconds since 1970 in GMT timezone.

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.

[1] Naming convention for the 'Defect numbers' are in the format YYYYMMDDHHMMSS