KronTalk
Chronos => Software Dev => Topic started by: tesla500 on July 12, 2017, 09:40:53 PM
-
Here's the first software update!
Not a huge amount in this one, basically a few features requested by a few scientific users, and a bunch of low-hanging fruit . More major updates will probably have to wait until after the backlog of Kickstarter rewards and store preorders have shipped, since it's so busy leading up to production. Once we hire a software engineer, updates will be much more frequent and significant.
Features added and bugs fixed:
- Added Triggered Exposure and Shutter Gating modes
- Fixed bug where video can be saved to the mount point if no storage device is present
- Fixed minimum exposure time (now 1uS instead of an impossible 10ns)
- Added "About" tab to Util window, showing software version, serial number, and camera info
- Added missing backer Jared Reabow in backers list
- Added support for LUX1310 image sensor silicon revision 2
- Fixed incorrect bitrate computation in save settings window
- Disabled H264 profile and level controls (certain lower levels caused encoder to crash)
- Fixed incorrect shutter slider and exposure text after changing resolution
- Fixed incorrect updating of ROI indicator in Record Settings
- Fixed allowable range of window offset to proper multiples (16, 2). Record settings would not be applied if offset was set other than proper multiple
- Moved close button on keyboard to bottom right
- Changed arrows on keyboard from text eg. "Up" to unicode arrow characters
Known bugs in added features:
- Horizontal line issue is present in Triggered Exposure and Shutter Gating modes, to be fixed
Installation instructions:
- Unzip the Zip file into the root directory of a FAT32 formatted USB stick
- This should result in a camUpdate folder in the root directory of the stick
- Boot up the camera and insert the USB stick
- Backup your calibration data. Tap "Backup calibration data" and wait for this to complete (about 5 seconds). The cal data is now backed up on the USB drive as cal_[serial number].tar
- To install the update, tap Apply Software Update
- A message box should pop up indicating the software update was found. Tap Yes to install the update.
- The screen will go blank for a few seconds, then the updated application will start.
- Done! No need to restart the camera.
What if something goes wrong?
Don't worry, it's impossible to brick the camera. If the update fails for some reason and the camera won't boot, you can reflash the OS SD card yourself to recover the camera. If you need the image file to do this, let us know. It's just like flashing the OS card for a Raspberry Pi. You will need to restore the backed up calibration data after reflashing the card. If you don't have a backup, we have a copy of the original factory cal, available on request.
Next updates in the pipeline:
- Proper trigger delay setting (Timeline/slider, pretrigger percentage, and setting by time rather than frames)
- Remembering settings across reboots
- Indication of dropped frames on save
- Proper boot splash screen
-
question for you regarding the update and remembering the settings:
I've had issues with white balance, every time I try to set it everything gets a pronounced yellow hue. So far when this has happened I've shut the camera down and re-started to regain the default white balance. I always use the default and it works fine.
Is it possible to reset the settings to default in the firmware version 2.0?
Is it also possible to edit the power-on settings, rather than keep the same settings from one session to the other?
for instance, I'd like to be able to set the encoding to 30fps and the default resolution to 1280x720, but keep everything the same as in version 1.0.
Thanks!
G
-
This is great, can't wait to get those dark pixels out of the way. I know the camera will be amazing with the software development. Congrats, I'll share this update soon!
Update went without a hitch. Also kudos on making it update proof by not using a firmware flash but opening software from the card. Glad to see a device that is ready to go after the update without a reboot. I was put off at first but it's a sweet feature to have.
-
Faultless upgrade. Quick and simple.
Can't wait for persistent settings, everything else I'll enjoy as they come. :)
-
New update trigger issue... I have a report that the new update will allow a trigger delay only for the on-camera trigger but not the BNC trigger input. Can anyone verify, I am not with my camera.
-
New update trigger issue... I have a report that the new update will allow a trigger delay only for the on-camera trigger but not the BNC trigger input. Can anyone verify, I am not with my camera.
I cannot duplicate, trigger and trigger delay works as expected on both V0.1 and V0.2, can anyone else check?
-
BNC trigger delay works fine on 0.2 firmware for us. Both in the low hundreds and high thousands of frames.
-
Went to do the update today, when I tried to backup the calibration data it gave me the error "Error: tar command failed" with a Lexar 16Gb (LJD550-16G). The calibration file was created but it is only ~30Mb, trying again with a different USB drive created a calibration file that was ~60Mb and is populated by about 80 files. I'm not sure what it is about the Lexar but it is strange that the error is related to the tar archive creation and not read/write related.
Otherwise the update went fine, thanks!
-
Went to do the update today, when I tried to backup the calibration data it gave me the error "Error: tar command failed" with a Lexar 16Gb (LJD550-16G). The calibration file was created but it is only ~30Mb, trying again with a different USB drive created a calibration file that was ~60Mb and is populated by about 80 files. I'm not sure what it is about the Lexar but it is strange that the error is related to the tar archive creation and not read/write related.
Otherwise the update went fine, thanks!
A correctly saved calibration backup should be 70,073,856 bytes. The cal folder should have 12 files and one folder called factoryFPN. The factoryFPN folder should contain 80 files.
-
File size and contents is like you said (Windows rounds down and reports it as being 68Mb).
-
Any time line on when the Audio input and the HDMI Output will be supported?
Those 2 items and RAW would make this camera sell like hot cakes.
Three things I noticed that there needed
#1 A factory reset button for all settings or per page.
#2 A percentage meter like you have on the battery but for the amount of storage left.
#3 A button to clear the cash or ram. Unless it's set up for roll over.
If it is there needs to be something in the manual stating it.
I'm just used to cameras you do not edit on. You shoot it. It saves the hole thing. In point at record start. Out at record stop. Perhaps that can be a button we can X on, or X off.
-
I'm just used to cameras you do not edit on. You shoot it. It saves the hole thing. In point at record start. Out at record stop. Perhaps that can be a button we can X on, or X off.
Just reading through the threads and I came across this. I agree that it would be nice to have a "Point and Shoot" option like that. I'm sure I'll have a better idea how things work once I get my camera, but flash storage is cheap nowadays. Just have a couple flash cards to store everything. If you are doing a lot, just dump one card to a laptop while you film with the other.
Not having to edit before saving would be very important when accessing the camera between triggers is impractical. An example would be filming the sawmill at one of the nearby steam thresher reunion cutting the logs into boards. They may let me setup when the saw is shutdown, but they are NOT gonna let me anywhere close a running 5 foot sawblade every time I trigger the camera. This would probably be welcome in scientific environments as well.
Thanks again for the hard work you do.
-
Not sure how that would work, since you still have a max 4 or 8 second record time. At what point would the camera decide, without your interaction, to stop recording and begin flushing the buffer to disk?
Seems that a remote RF trigger would be a good addition to your kit. ;)
-
Not sure how that would work, since you still have a max 4 or 8 second record time. At what point would the camera decide, without your interaction, to stop recording and begin flushing the buffer to disk?
Seems that a remote RF trigger would be a good addition to your kit. ;)
Oh, you would still trigger it like you normally do and then it would start writing to the SD card or whatever you have setup for storage.
You would have to know ahead of time how long it takes to write to the buffer, though once HDMI is working it will be easier to monitor.
Sorry for the confusion.
-
Oh I gotcha. I misunderstood, my bad. Depending on the frame rate, flushing the entire buffer could take many minutes, but at least it would have a head start. :)
I wonder if this would be an opportunity to use a long press of the Record button. Normal press = normal operation. Long press raises a menu of post-trigger options.
-
I have a little problem. Copied the software to the Fat32 SD.
Started the cam and went into Util to press Backup. -> Gives an error, SD not present.
When I press the trigger and make a short clip, I can save to the SD card without a problem. Just Backup Calibration Data tells me there is no card..
/media/NAME is different in the Recording settings and the error message, so I understand the error msg.. just dont understand why it gives 2 different paths, only has one card slot.
error: no device is mounted to /media/sda1
I save in Play/Settings to: /media/mmcblk1p1 (SD card Partition 1) and that works fine every time
Anybody had that before?
regards
Jay
-
I have a little problem. Copied the software to the Fat32 SD.
Started the cam and went into Util to press Backup. -> Gives an error, SD not present.
When I press the trigger and make a short clip, I can save to the SD card without a problem. Just Backup Calibration Data tells me there is no card..
/media/NAME is different in the Recording settings and the error message, so I understand the error msg.. just dont understand why it gives 2 different paths, only has one card slot.
error: no device is mounted to /media/sda1
I save in Play/Settings to: /media/mmcblk1p1 (SD card Partition 1) and that works fine every time
Anybody had that before?
regards
Jay
Calibration data backup and restore only supports USB drives right now, try a USB memory stick or similar.
-
Wups ^^ now I feel stupid ;)
Worked very easy with the stick. Thanks for the help!
-
Any time line on when the Audio input and the HDMI Output will be supported?
Those 2 items and RAW would make this camera sell like hot cakes.
Three things I noticed that there needed
#1 A factory reset button for all settings or per page.
#2 A percentage meter like you have on the battery but for the amount of storage left.
#3 A button to clear the cash or ram. Unless it's set up for roll over.
If it is there needs to be something in the manual stating it.
I'm just used to cameras you do not edit on. You shoot it. It saves the hole thing. In point at record start. Out at record stop. Perhaps that can be a button we can X on, or X off.
If you update to V0.3 beta software: Settings reset is in Utils under "settings" tab. There's also options there for saving and recovering saved settings.
This is a beta feature so please let me know if it works or if there are any issues with it.
Good idea on the storage left indicator. Will look at adding something like that. Right now it will give a warning if you try saving a file that is larger than 4GB or larger than the space left on the device.
The buffer memory will automatically roll over; there should be no reason to clear it.
As for HDMI and Audio - both are looking like they may get into the next update. We have HDMI working partially on a development camera but there are some that need to be overcome before it can be integrated into the application. Audio is in a similar state.
-
Fat 32 is that a less than 4 gb usb stick ?
-
This is common to fat 32 stick drives. It is easy to fix. Also, it is easy to prevent. If you update your drivers. I had this problem with many stick drives. I use them with Arduino, and it gives to many errors to that mini PC. So, I installed a driver updater free (https://thinkmobiles.com/blog/best-free-driver-updater/) and it helped me. Now I just use those stick drives and don’t need to bother with any errors.