VideoSecu DVC1612: Difference between revisions

From LinuxTVWiki
Jump to navigation Jump to search
(More information)
m (Miscellaneous minor updates)
Line 5: Line 5:


== Introduction ==
== Introduction ==
The [http://www.videosecu.com/16-ch-dvr-video-audio-capture-card-dvc1612/ VideoSecu DVC1612] is a 16-channel PCI capture card with 4 Conexant Fusion 878A chips behind a PCI bridge. As suggested by its name, it is designed for security systems and comes with a CD containing a copy of the [[EyeONet]] DVR software.
The [http://www.videosecu.com/16-ch-dvr-video-audio-capture-card-dvc1612/ VideoSecu DVC1612] is a 16-channel PCI capture card with 4 [[Conexant Fusion 878A]] chips behind a PCI bridge. As suggested by its name, it is designed for security systems and comes with a CD containing a copy of the [[EyeONet]] DVR software.


The card has two VGA ports which are used for two VGA-to-BNC splitters (not real VGA). It seems that any of the 16 video inputs can be connected to any of the four Bt878a chips as long as the correct GPIO values are written, as already discovered by whoever added support for the Tibet Systems CS16.
The card has two VGA ports which are used for two VGA-to-BNC splitters (not real VGA). It seems that any of the 16 video inputs can be connected to any of the four Bt878a chips as long as the correct GPIO values are written, as already discovered by whoever added support for the Tibet Systems CS16.
Line 14: Line 14:


== Using the Card ==
== Using the Card ==
My intention is to try to have working autodetection for this card, but that may not be possible. Use '''<code>card=131,131,131,131</code>''' as a parameter to the '''<code>bttv</code>''' kernel module in the meantime. Video input 1 is named Composite0; Video input 16 is named Composite15. You will know that bttv was not loaded with the proper parameters if Composite0 is connected to video input 16 and video input 16 is the only input that works.
This card unfortunately lacks the necessary PCI identification to be autodetected. Use '''<code>card=131,131,131,131</code>''' as a parameter to the '''<code>bttv</code>''' kernel module in order to use this card. Video input 1 is named Composite0; Video input 16 is named Composite15. You will know that bttv was not loaded with the proper parameters if Composite0 is connected to video input 16 and video input 16 is the only input that works. If you are using software such as ZoneMinder that can be configured to capture from multiple inputs on the same /dev/videoX device, be sure to only designate four inputs to each /dev/videoX device. It would probably work to capture all 16 inputs through one /dev/video device, but in that case you would not be making use of one out of the four bt878 chips on this card and you would have extremely low framerate due to input-switching delays.

I also found it useful to add the '''<code>bit_test=1</code>''' parameter to the '''<code>i2c_algo_bit</code>''' kernel module, as suggested by the bttv documentation. (Note that you may have to update your initramfs image for this change to take effect.) Without this it took waaay too long to insert the bttv module, causing udev's workers to time out, which caused systemd-logind to time out and get killed by systemd, which then even interfered with the login screen.


[[Category:Capture Devices]] [[Category:Analog]] [[Category:Hardware]] [[Category:PCI]] [[Category:Analog PCI Cards]]
[[Category:Capture Devices]] [[Category:Analog]] [[Category:Hardware]] [[Category:PCI]] [[Category:Analog PCI Cards]]

Revision as of 21:10, 6 March 2018

VideoSecu DVC1612 top.jpg
VideoSecu DVC1612 bottom.jpg

Very similar (and probably driver-compatible) cards seem to be sold under the names EverSecu ES-1612, EyeMax DVB1920, and Tibet Systems Progress DVR CS16. The latter's preexisting support in the kernel was how I managed to get this card working. The IDR X016S may also be compatible—the layout of integrated circuits and other components on the card look similar to the VideoSecu DVC1612.

Introduction

The VideoSecu DVC1612 is a 16-channel PCI capture card with 4 Conexant Fusion 878A chips behind a PCI bridge. As suggested by its name, it is designed for security systems and comes with a CD containing a copy of the EyeONet DVR software.

The card has two VGA ports which are used for two VGA-to-BNC splitters (not real VGA). It seems that any of the 16 video inputs can be connected to any of the four Bt878a chips as long as the correct GPIO values are written, as already discovered by whoever added support for the Tibet Systems CS16.

VideoSecu DVC1612 front.jpg

The RCA connector on the left side is presumably for output to an analog screen. To my knowledge, neither this functionality nor audio is currently working.

Using the Card

This card unfortunately lacks the necessary PCI identification to be autodetected. Use card=131,131,131,131 as a parameter to the bttv kernel module in order to use this card. Video input 1 is named Composite0; Video input 16 is named Composite15. You will know that bttv was not loaded with the proper parameters if Composite0 is connected to video input 16 and video input 16 is the only input that works. If you are using software such as ZoneMinder that can be configured to capture from multiple inputs on the same /dev/videoX device, be sure to only designate four inputs to each /dev/videoX device. It would probably work to capture all 16 inputs through one /dev/video device, but in that case you would not be making use of one out of the four bt878 chips on this card and you would have extremely low framerate due to input-switching delays.

I also found it useful to add the bit_test=1 parameter to the i2c_algo_bit kernel module, as suggested by the bttv documentation. (Note that you may have to update your initramfs image for this change to take effect.) Without this it took waaay too long to insert the bttv module, causing udev's workers to time out, which caused systemd-logind to time out and get killed by systemd, which then even interfered with the login screen.