Difference between revisions of "Pov"

From RevSpace
Jump to navigation Jump to search
(software)
Line 20: Line 20:
 
** used for camera 6 and 11 which are down
 
** used for camera 6 and 11 which are down
  
* constatus [https://github.com/flok99/constatus https://github.com/flok99/constatus]
+
* constatus [https://vanheusden.com/constatus/ https://vanheusden.com/constatus/]
 
** all other cameras
 
** all other cameras
  
Line 34: Line 34:
 
==== constatus ====
 
==== constatus ====
  
* installed from the github repository
+
* installed from the github repository [https://github.com/flok99/constatus https://github.com/flok99/constatus]
 
* installed under /usr/local/constatus
 
* installed under /usr/local/constatus
 
* started (currently, 20170903) from /etc/rc.local
 
* started (currently, 20170903) from /etc/rc.local
 
* each camera has its own constatus process - the idea is that if something crashes, that not all cameras will go down
 
* each camera has its own constatus process - the idea is that if something crashes, that not all cameras will go down
 
  
 
=== recording specificaions ===
 
=== recording specificaions ===

Revision as of 16:06, 3 September 2017

what is it

POV is the (virtual) server managing the webcams. It stores video files of all webcams over the last 2 days.


OS specifications

  • debian stretch
  • 32b
  • virtual machine with 2 cores
  • 1GB ram
  • 10GB root filesystem
  • 100GB storage for camera files


software


motion

  • motion is installed from the debian repository
  • configuration files are under /etc/motion
  • main configuration is motion.conf which includes cam*.conf
  • as by the design of motion, all its cameras (6 + 11) are monitored from 1 process


constatus

  • installed from the github repository https://github.com/flok99/constatus
  • installed under /usr/local/constatus
  • started (currently, 20170903) from /etc/rc.local
  • each camera has its own constatus process - the idea is that if something crashes, that not all cameras will go down

recording specificaions

  • 5 FPS video files
  • 2 FPS HTTP web interface


cameras

  • CAM 1: RTSP, hanging above the 3D printer
  • CAM 2: MJPEG, cantine
  • CAM 3: MJPEG, back side of klusruimte
  • CAM 4: MJPEG, front side of klusruimte
  • CAM 5: RTSP, houtbewerkingsruimte
  • CAM 6: broken
  • CAM 7/8/9/10: MJPEG, source is Verint Nextiva. these produce an RTP stream which are converted to MJPEG by scripting running on the shell server, see https://github.com/Peetz0r/revcaminfra.