Chronos API Documentation

Chronos > Software Dev

(1/3) > >>

ieSe:
Hi I'm using Chronos 1.4 32GB Build: 0.4.0~beta38 in a research project and I'm really satisfied with the API. As I use Matlab to control the whole operation. Now I'm able to start - stop recording, changing parameters and even make black calibration. But I'm still facing some problems:

* I can't get the available storage in my SD card. I can't get any useful data from externalStorage parameter and this information is not even exist in the web UI (image 1). Although I can find the available size in the camera UI (image 2).
* Parameter disableRingBuffer which is responsible for not overwriting when the buffer is full and automatically stop recording dose not work when changed to true.
* Bug: I can start recording while the camera is saving a video. That could lead to unexpected behavior.
* To fix bug number 3 is there any parameter, that would store the camera status so i can check it before do any operation?
Thank you.

skronstein:

--- Quote from: ieSe on April 30, 2020, 06:28:05 AM ---Hi I'm using Chronos 1.4 32GB Build: 0.4.0~beta38 in a research project and I'm really satisfied with the API. As I use Matlab to control the whole operation. Now I'm able to start - stop recording, changing parameters and even make black calibration. But I'm still facing some problems:

* I can't get the available storage in my SD card. I can't get any useful data from externalStorage parameter and this information is not even exist in the web UI (image 1). Although I can find the available size in the camera UI (image 2).
* Parameter disableRingBuffer which is responsible for not overwriting when the buffer is full and automatically stop recording dose not work when changed to true.
* Bug: I can start recording while the camera is saving a video. That could lead to unexpected behavior.
* To fix bug number 3 is there any parameter, that would store the camera status so i can check it before do any operation?
Thank you.

--- End quote ---

1.
You'll have to switch to the unstable software release to get the size and free space of the storage devices.
The easiest way to switch to the unstable repository is probably to flash an SD card with the latest unstable image. Compressed SD card images can be found here: http://debian.krontech.ca/builds/
A guide on how to flash the card can be found here: http://forum.krontech.ca/index.php?topic=531.0

With the latest software on unstable, you should be able to get the capacity and free space of a storage device by sending a GET request for that device.

For the first partition on an SD card, use the URL:
http://<Camera IP address>/cgi-bin/storageInfo?mmcblk1p1

For the first partition on an USB stick, use the URL:
http://<Camera IP address>/cgi-bin/storageInfo?sda1

2. and 3.
Thanks, I've reported these bugs. The Unstable release will receive fixes before the Voyager (stable) release does.

4.
You can check videoState here to see if the camera is currently saving:
https://github.com/krontech/pychronos#display-parameters

ieSe:

--- Quote from: skronstein on April 30, 2020, 09:19:47 PM ---1.
You'll have to switch to the unstable software release to get the size and free space of the storage devices.
The easiest way to switch to the unstable repository is probably to flash an SD card with the latest unstable image. Compressed SD card images can be found here: http://debian.krontech.ca/builds/
A guide on how to flash the card can be found here: http://forum.krontech.ca/index.php?topic=531.0

With the latest software on unstable, you should be able to get the capacity and free space of a storage device by sending a GET request for that device.

For the first partition on an SD card, use the URL:
http://<Camera IP address>/cgi-bin/storageInfo?mmcblk1p1

For the first partition on an USB stick, use the URL:
http://<Camera IP address>/cgi-bin/storageInfo?sda1

2. and 3.
Thanks, I've reported these bugs. The Unstable release will receive fixes before the Voyager (stable) release does.

--- End quote ---

Thank you for your fast replying. I think I will wait until the release of the new unstable version to check them all.

--- Quote from: skronstein on April 30, 2020, 09:19:47 PM ---4.
You can check videoState here to see if the camera is currently saving:
https://github.com/krontech/pychronos#display-parameters

--- End quote ---
As I mentioned above, I'm using Matlab and I'm not preferring to change my project to python. Because I control another equipment from Matlab either. Is there any other request that I can send to camera server to get the status?

NiNeff:

--- Quote from: ieSe on May 01, 2020, 04:10:07 AM ---
--- Quote from: skronstein on April 30, 2020, 09:19:47 PM ---4.
You can check videoState here to see if the camera is currently saving:
https://github.com/krontech/pychronos#display-parameters

--- End quote ---
As I mentioned above, I'm using Matlab and I'm not preferring to change my project to python. Because I control another equipment from Matlab either. Is there any other request that I can send to camera server to get the status?

--- End quote ---
As i understand it you'd have to run the pychronos script on the camera itself, not externally. You should therefore be able to create a hook for your matlab-code to connect to.

ieSe:

--- Quote from: skronstein on April 30, 2020, 09:19:47 PM ---4.
You can check videoState here to see if the camera is currently saving:
https://github.com/krontech/pychronos#display-parameters

--- End quote ---

--- Quote from: NiNeff on May 01, 2020, 05:30:03 AM ---As i understand it you'd have to run the pychronos script on the camera itself, not externally. You should therefore be able to create a hook for your matlab-code to connect to.

--- End quote ---
My bad. I found the right parameters in <http://<camerIP>/apidoc/>, which are state and videoState. Thanks

Navigation

[0] Message Index

[#] Next page

Go to full version