RaspCam Code
Brought to you by:
schnoog
File | Date | Author | Commit |
---|---|---|---|
config | 2013-08-25 |
![]() |
[275b6a] First complete running version |
doc | 2013-08-03 |
![]() |
[d1c6a3] Next cleanup |
functions | 2013-08-03 |
![]() |
[739090] Should run now |
input_output | 2013-08-25 |
![]() |
[275b6a] First complete running version |
locks | 2013-08-25 |
![]() |
[275b6a] First complete running version |
scripts | 2013-08-25 |
![]() |
[275b6a] First complete running version |
triggers | 2013-08-25 |
![]() |
[275b6a] First complete running version |
.hgignore | 2013-08-03 |
![]() |
[71a15d] Next cleanup step, gpsdata path exported2 |
README | 2013-08-02 |
![]() |
[9826fd] Documentation started 2 |
main_config.cfg | 2013-08-02 |
![]() |
[370bf5] CleanUp Done, CFGs merged, main_config cleaned |
master.log | 2013-08-25 |
![]() |
[275b6a] First complete running version |
nohup.out | 2013-08-25 |
![]() |
[275b6a] First complete running version |
sys_starter.sh | 2013-08-25 |
![]() |
[275b6a] First complete running version |
RaspCam is a script collection to use a raspberry pi with camera board as a motorcycle action cam in a very special way. RaspCam records, when started, the video-stream from the Raspberry Pi Camera board and split it up into segments. When trigger is set (my idea is to use a trigger connected via GPIO), the software saves the segments, beginning from the last X segments until the trigger is set again. Un-triggered segments will be ereased cyclically. Furthermore an attached gps-device server the GPS position which will be recorded into gpx files for each recorded segment. Requirements: A raspberry pi + power supply + raspbian image A raspberry pi camera board connected to the rpi A suitable clock reference this could be a) a Rasclock device ( http://afterthoughtsoftware.com/products/rasclock ) and / or b) a gps device FFMPEG, compiled to allowe splitting into segments PSIPS (https://github.com/AndyA/psips) GPSBABEL (if you want to capture the GPS position) How it works: A script is running in loops of a defined length (for example 1 hour = 3600s = 3600000ms) and capturing the camera stream. Those records gets splitted in segment of a specified length (for example 60s). This script will be started again until the triggerfile referenced in $RC_LOCK_SYSRUNNING or $RC_LOCK_CAPTURECAM contains a 0 (Which means: Even if you stop the system, the video capturing will be continued until the last looptime is over) In parallel, if configured, the gps data collected during the segment recording is written in gpx format to a file If the triggerfile referenced in $RC_LOCK_SAVESEGMENTS is set to 1 the actual, and also the last X segements will be saved, if set to 0 the segments will be pruned during the next cleanup For more details see the files in the doc folder