yes this is possible and it was one of my wishes too, in fact I did some trials in the past with a program called "motion". This program is still present in the firmware (/usr/bin/motion) including basic config files (see /usr/etc folder). But it never came to implementing it in the webinterface. One of the things was the variety of usb camera's and drivers needed. I compiled a lot as modules. but in that time the firmware only run on the spd8020 and nwsp1 with limited resources and the video processing was too much for the small system memory. On the nwsp2 it should work ok.
I just checked it and it works on the nwsp2. I enabled the basic drivers for usb video in the kernel and I guess pwc based and uvc based webcam drivers should be recognized, but they also might need a specific driver dependnent on the brand used.
Anyhow the kernel I am running it recognized my webcam without a problem (uvc based)
- Code: Select all
root@fvdwsl-nwsp2:/ # lsusb -t
1-1:1.2: No such file or directory
1-1:1.3: No such file or directory
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=orion-ehci/1p, 480M
|__ Port 1: Dev 2, If 0, Class='bInterfaceClass 0x0e not yet handled', Drive r=uvcvideo, 480M
|__ Port 1: Dev 2, If 1, Class='bInterfaceClass 0x0e not yet handled', Drive r=uvcvideo, 480M
|__ Port 1: Dev 2, If 2, Class=audio, Driver=, 480M
|__ Port 1: Dev 2, If 3, Class=audio, Driver=, 480M
And then fired up motion by just using the command
- Code: Select all
motion
on the command line after accessing it via ssh.
It gave some remarks about unknown options but the daemon loaded
- Code: Select all
root@fvdwsl-nwsp2:/ # motion
[0] Processing thread 0 - config file /usr/etc/motion.conf
[0] Unknown config option "ffmpeg_cap_new"
[0] Unknown config option "ffmpeg_cap_motion"
[0] Unknown config option "ffmpeg_timelapse"
[0] Unknown config option "ffmpeg_timelapse_mode"
[0] Unknown config option "ffmpeg_bps"
[0] Unknown config option "ffmpeg_variable_bitrate"
[0] Unknown config option "ffmpeg_video_codec"
[0] Unknown config option "ffmpeg_deinterlace"
[0] Unknown config option "movie_filename"
[0] Unknown config option "timelapse_filename"
[0] Unknown config option "sql_log_image"
[0] Unknown config option "sql_log_snapshot"
[0] Unknown config option "sql_log_mpeg"
[0] Unknown config option "sql_log_timelapse"
[0] Unknown config option "sql_query"
[0] Motion 3.2.11 Started
[0] Motion going to daemon mode
root@fvdwsl-nwsp2:/ #
and I could connect to it using my browser and the address
http://ip-nas:8081 and got a picture
motion.JPG
so if your usb camera is detected by the system nothing can stop you to develop the video surveillance :whistle
Ps if you are going to store pictures or video, be sure not to do that in the system partition as that is limited in space , create use a shared folder for that (/share/1000/name-of-shared-folder). That makes it also easier to access and view the pictures
ps I am using the kernel to be used in fvdw-sl-13-0, this kernel is more sophisticated then the one currently used by 12-1 but the usb video settings at compile them were the same.
- Code: Select all
CONFIG_V4L_USB_DRIVERS=y
CONFIG_USB_VIDEO_CLASS=y
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
CONFIG_USB_GSPCA=m
CONFIG_USB_M5602=m
CONFIG_USB_STV06XX=m
CONFIG_USB_GL860=m
CONFIG_USB_GSPCA_BENQ=m
CONFIG_USB_GSPCA_CONEX=m
CONFIG_USB_GSPCA_CPIA1=m
CONFIG_USB_GSPCA_ETOMS=m
CONFIG_USB_GSPCA_FINEPIX=m
CONFIG_USB_GSPCA_JEILINJ=m
CONFIG_USB_GSPCA_KONICA=m
CONFIG_USB_GSPCA_MARS=m
CONFIG_USB_GSPCA_MR97310A=m
CONFIG_USB_GSPCA_NW80X=m
CONFIG_USB_GSPCA_OV519=m
CONFIG_USB_GSPCA_OV534=m
CONFIG_USB_GSPCA_OV534_9=m
CONFIG_USB_GSPCA_PAC207=m
CONFIG_USB_GSPCA_PAC7302=m
CONFIG_USB_GSPCA_PAC7311=m
CONFIG_USB_GSPCA_SN9C2028=m
CONFIG_USB_GSPCA_SN9C20X=m
CONFIG_USB_GSPCA_SONIXB=m
CONFIG_USB_GSPCA_SONIXJ=m
CONFIG_USB_GSPCA_SPCA500=m
CONFIG_USB_GSPCA_SPCA501=m
CONFIG_USB_GSPCA_SPCA505=m
CONFIG_USB_GSPCA_SPCA506=m
CONFIG_USB_GSPCA_SPCA508=m
CONFIG_USB_GSPCA_SPCA561=m
CONFIG_USB_GSPCA_SPCA1528=m
CONFIG_USB_GSPCA_SQ905=m
CONFIG_USB_GSPCA_SQ905C=m
CONFIG_USB_GSPCA_SQ930X=m
CONFIG_USB_GSPCA_STK014=m
CONFIG_USB_GSPCA_STV0680=m
CONFIG_USB_GSPCA_SUNPLUS=m
CONFIG_USB_GSPCA_T613=m
CONFIG_USB_GSPCA_TV8532=m
CONFIG_USB_GSPCA_VC032X=m
CONFIG_USB_GSPCA_VICAM=m
CONFIG_USB_GSPCA_XIRLINK_CIT=m
CONFIG_USB_GSPCA_ZC3XX=m
...more
<snip>
"m" means the driver is compiled as module and need to be loaded.
"y" means it is included in the kernel
With the test above I did not load any usb-video module, the V4L_USB drivers apparently support my usb camera
You do not have the required permissions to view the files attached to this post.