ZoneMinder Wiki - User contributions [en]

Digiflower

2017-08-01T20:50:08Z

Tuxokc: Fix image links

I've recently laid hands on a few Digi-Flower capture cards and found no indication that anyone has ever taken the time to poke at these cards with a digital multi-meter to discover how they are laid out.

I have two versions, the DVR2000B-R02, and the DVR2510-MP2.
First ones were also sold as Huperlab DVR 2400 and probably Leadtek LTR-39608.

[[Media:DVR2000B.jpg|Digi-Flower DVR-2000B-R02: 16 input; 4 Fusion BT878A chips]]

The DVR2000B has four Fusion bt878A decoders and supports 16 composite inputs

Each bt878A device controls a pair of M/D'ers:

<pre>
GPIO[0,1,2] => M/D[1][A,B,C] (select pins)
GPIO[18] => M/D[1][Enable]

GPIO[0,1,2] => M/D[2][A,B,C] (select pins)
GPIO[20] => M/D[2][Enable]
</pre>

When an input has been routed the signal is split between the bt878A's MUX0 and a 4581CS Sync Separator. As far as I can tell the only output of the 4581CS that is used is the Odd/Even field output that is routed to GPIO[15] on the respective 878A

<pre>
74HC4051A
Comp-In (1-8) => M/D[1] (X0-7) -> \ [ L/C/R ] (inductor/
|= [network] capacitor/
Comp-In (9-16) => M/D[2] (X0-7) -> / resistor)

4581CS Sync Separator
L/C/R / Comp-In -> Odd/Even => GPIO[15]
[network] =|
\ 878A: MUX0
</pre>

There is also a fifth pair of Mux/Demux chips that are used to send one of 16 inputs to an RCA jack via a 6db video amp. This routing function is controlled by an Atmel AT89C2051 (8051 family) micro controller. I have not determined how to talk to the micro controller at this time. The I2C pins of the first bt878A is connected to the serial port of the micro controller.

There is also a set of 8 external device I/O ports to send or receive On/Off signals from motion detectors or drive alarm circuits, and an on board WatchDog relay output. These are controlled by GPIO[3-10,12-13] of the first 878A.

Anko no longer lists these cards: http://www.anko-tech.com/

lspci data for the DVR2000B ( these numbers seem very generic.. how can the specific card be known?)
<pre>
02:00.0 PCI bridge [0604]: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) [3388:0021] (rev 11)
03:0c.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0c.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0d.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0d.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0e.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0e.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0f.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0f.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
</pre>

I've been able to get the DVR2000B working with this patch on linux-2.6.32 kernel----

<pre>
diff -uNrp kernel-2.6.32.orig/drivers/media/video/bt8xx/bttv-cards.c kernel-2.6.32.new/drivers/media/video/bt8xx/bttv-cards.c
--- kernel-2.6.32.orig/drivers/media/video/bt8xx/bttv-cards.c 2010-03-31 18:11:38.506042269 -0600
+++ kernel-2.6.32.new/drivers/media/video/bt8xx/bttv-cards.c 2010-04-01 10:32:31.399044056 -0600
@@ -68,6 +68,8 @@ static void tibetCS16_init(struct bttv *
static void kodicom4400r_muxsel(struct bttv *btv, unsigned int input);
static void kodicom4400r_init(struct bttv *btv);

+static void digiflower_dvr2000b_muxsel(struct bttv *btv, unsigned int input);
+
static void sigmaSLC_muxsel(struct bttv *btv, unsigned int input);
static void sigmaSQ_muxsel(struct bttv *btv, unsigned int input);

@@ -326,6 +328,7 @@ static struct CARD {
{ 0x763d800b, BTTV_BOARD_GEOVISION_GV800S_SL, "GeoVision GV-800(S) (slave)" },
{ 0x763d800c, BTTV_BOARD_GEOVISION_GV800S_SL, "GeoVision GV-800(S) (slave)" },
{ 0x763d800d, BTTV_BOARD_GEOVISION_GV800S_SL, "GeoVision GV-800(S) (slave)" },
+ { 0x00000000, BTTV_BOARD_DIGIFLOWER_DVR2000B, "Digi-Flower DVR2000B" },

{ 0x15401830, BTTV_BOARD_PV183, "Provideo PV183-1" },
{ 0x15401831, BTTV_BOARD_PV183, "Provideo PV183-2" },
@@ -2912,6 +2915,25 @@ struct tvcard bttv_tvcards[] = {
.tuner_type = TUNER_ABSENT,
.tuner_addr = ADDR_UNSET,
},
+ [BTTV_BOARD_DIGIFLOWER_DVR2000B] = {
+ .name = "Digi-Flower DVR2000B (master?)",
+ .video_inputs = 16,
+ /* .audio_inputs = 0, */
+ /* .tuner = UNSET, */
+ .svhs = NO_SVHS,
+ .tuner_type = TUNER_ABSENT,
+ .tuner_addr = ADDR_UNSET,
+ /* .radio_addr = ADDR_UNSET, */
+ .no_gpioirq = 1,
+ .gpiomask2 = 0x140007,
+ .muxsel = MUXSEL(2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2),
+ .muxsel_hook = digiflower_dvr2000b_muxsel,
+ .gpiomux = { 0, 0, 0, 0 }, /* card has no audio */
+ .no_msp34xx = 1,
+ .no_tda9875 = 1,
+ .no_tda7432 = 1,
+ .pll = PLL_28,
+ },
};

static const unsigned int bttv_num_tvcards = ARRAY_SIZE(bttv_tvcards);
@@ -4548,6 +4570,21 @@ static void kodicom4400r_init(struct btt
master[btv->c.nr+2] = btv;
}

+/* DB1 = Top connector fan-out. DB2 = Bottom connector fan-out. */
+#define DB1 0x100000
+#define DB2 0x040000
+
+static void digiflower_dvr2000b_muxsel(struct bttv *btv, unsigned int input)
+{
+ static const int masks[] = {
+ DB1, DB1|1, DB1|2, DB1|3,
+ DB1|4, DB1|5, DB1|6, DB1|7,
+ DB2, DB2|1, DB2|2, DB2|3,
+ DB2|4, DB2|5, DB2|6, DB2|7,
+ };
+ gpio_write(masks[input%16]);
+}
+
/* The Grandtec X-Guard framegrabber card uses two Dual 4-channel
* video multiplexers to provide up to 16 video inputs. These
* multiplexers are controlled by the lower 8 GPIO pins of the
diff -uNrp kernel-2.6.32.orig/drivers/media/video/bt8xx/bttv.h kernel-2.6.32.new/drivers/media/video/bt8xx/bttv.h
--- kernel-2.6.32.orig/drivers/media/video/bt8xx/bttv.h 2010-03-31 23:22:03.987043302 -0600
+++ kernel-2.6.32.new/drivers/media/video/bt8xx/bttv.h 2010-03-31 23:21:45.412041507 -0600
@@ -185,6 +185,7 @@
#define BTTV_BOARD_GEOVISION_GV800S 0x9d
#define BTTV_BOARD_GEOVISION_GV800S_SL 0x9e
#define BTTV_BOARD_PV183 0x9f
+#define BTTV_BOARD_DIGIFLOWER_DVR2000B 0xa0

/* more card-specific defines */
</pre>

[[Media:DVR2510-th.jpg|Digi-Flower DVR-2510-MP2: 16 input; 2 Fusion BT878A chips]]

The DVR2510 has two Fusion BT878A chips. A total of 16 composite inputs that are supported. Eight inputs are routed to each 878A chip, so only one M/D is needed for each 878A.

The two additional M/D are used to route inputs to the composite out monitor connection. This card differs most from its larger cousin in that the Enable pins of the M/D's are connected to the Atmel micro-controller, so the card is not usable until the micro-controller has been initialized. This won't be possible until a logic analyzer can be brought to bear on the problem.

Linksys

2015-02-14T17:26:14Z

Tuxokc: Undo SPAM links revision 5630 by Tonyguards (talk)

WVC-210 PTZ

remote host path = /img/video.mjpeg

http://www.zoneminder.com/forums/viewtopic.php?t=13484&highlight=cameras

WVC2300 / PVC2300

A few options for these cameras:

*Base hit uses still image snapshots:
**Remote Host Name: user:password@ip.ad.dr.ess
**Remote Host Path: img/snapshot.cgi?size=3&quality=1
***size=1-3 (160x120, 320x240, 640x480)
***quality=1-5(very high - very low)
*Even better solution is to use pushed jpegs:
**Remote Host Name: user:password@ip.ad.dr.ess
**Remote Host Path: img/mjpeg.jpg
**Use the web administration UI for the camera to set size, quality and framerate throttling
*Would like to use ffmpeg, however this seems to be giving problems - partial image scans etc
**Source Path: http://user:password@ip.ad.dr.ess/img/video.asf
**Seems to use size and quality settings from the administration website
*What doesnt work
**img/video.mjpeg (and other similar urls). Generally barfs on zm_remote_camera_http.cpp:134, and I cant be bothered debugging it.
*Other notes
**See [http://www.lavrsen.dk/foswiki/bin/view/Motion/NetcamMjpegStreamDumps] for information from the 'motion' application (scroll down to Linksys WVC54G which gave me some hints)

WVC54GC

*Source Type: ffmpeg
*Source Path: http://##.##.##.##/img/mjpeg.cgi

[[Category:Network Cameras]]

Digiflower

2010-06-02T00:51:35Z

Tuxokc:

I've recently laid hands on a few Digi-Flower capture cards and found no indication that anyone has ever taken the time to poke at these cards with a digital multi-meter to discover how they are laid out.

I have two versions, the DVR2000B-R02, and the DVR2510-MP2.

[[Image:DVR2000B-th.jpg|Digi-Flower DVR-2000B-R02: 16 input; 4 Fusion BT878A chips]]

The DVR2000B has four Fusion bt878A decoders and supports 16 composite inputs

Each bt878A device controls a pair of M/D'ers:

<pre>
GPIO[0,1,2] => M/D[1][A,B,C] (select pins)
GPIO[18] => M/D[1][Enable]

GPIO[0,1,2] => M/D[2][A,B,C] (select pins)
GPIO[20] => M/D[2][Enable]
</pre>

When an input has been routed the signal is split between the bt878A's MUX0 and a 4581CS Sync Separator. As far as I can tell the only output of the 4581CS that is used is the Odd/Even field output that is routed to GPIO[15] on the respective 878A

<pre>
74HC4051A
Comp-In (1-8) => M/D[1] (X0-7) -> \ [ L/C/R ] (inductor/
|= [network] capacitor/
Comp-In (9-16) => M/D[2] (X0-7) -> / resistor)

4581CS Sync Separator
L/C/R / Comp-In -> Odd/Even => GPIO[15]
[network] =|
\ 878A: MUX0
</pre>

There is also a fifth pair of Mux/Demux chips that are used to send one of 16 inputs to an RCA jack via a 6db video amp. This routing function is controlled by an Atmel AT89C2051 (8051 family) micro controller. I have not determined how to talk to the micro controller at this time. The I2C pins of the first bt878A is connected to the serial port of the micro controller.

There is also a set of 8 external device I/O ports to send or receive On/Off signals from motion detectors or drive alarm circuits, and an on board WatchDog relay output. These are controlled by GPIO[3-10,12-13] of the first 878A.

Anko no longer lists these cards: http://www.anko-tech.com/

lspci data for the DVR2000B ( these numbers seem very generic.. how can the specific card be known?)
<pre>
02:00.0 PCI bridge [0604]: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) [3388:0021] (rev 11)
03:0c.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0c.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0d.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0d.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0e.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0e.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0f.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0f.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
</pre>

I've been able to get the DVR2000B working with this patch on linux-2.6.32 kernel----

<pre>
diff -uNrp kernel-2.6.32.orig/drivers/media/video/bt8xx/bttv-cards.c kernel-2.6.32.new/drivers/media/video/bt8xx/bttv-cards.c
--- kernel-2.6.32.orig/drivers/media/video/bt8xx/bttv-cards.c 2010-03-31 18:11:38.506042269 -0600
+++ kernel-2.6.32.new/drivers/media/video/bt8xx/bttv-cards.c 2010-04-01 10:32:31.399044056 -0600
@@ -68,6 +68,8 @@ static void tibetCS16_init(struct bttv *
static void kodicom4400r_muxsel(struct bttv *btv, unsigned int input);
static void kodicom4400r_init(struct bttv *btv);

+static void digiflower_dvr2000b_muxsel(struct bttv *btv, unsigned int input);
+
static void sigmaSLC_muxsel(struct bttv *btv, unsigned int input);
static void sigmaSQ_muxsel(struct bttv *btv, unsigned int input);

@@ -326,6 +328,7 @@ static struct CARD {
{ 0x763d800b, BTTV_BOARD_GEOVISION_GV800S_SL, "GeoVision GV-800(S) (slave)" },
{ 0x763d800c, BTTV_BOARD_GEOVISION_GV800S_SL, "GeoVision GV-800(S) (slave)" },
{ 0x763d800d, BTTV_BOARD_GEOVISION_GV800S_SL, "GeoVision GV-800(S) (slave)" },
+ { 0x00000000, BTTV_BOARD_DIGIFLOWER_DVR2000B, "Digi-Flower DVR2000B" },

{ 0x15401830, BTTV_BOARD_PV183, "Provideo PV183-1" },
{ 0x15401831, BTTV_BOARD_PV183, "Provideo PV183-2" },
@@ -2912,6 +2915,25 @@ struct tvcard bttv_tvcards[] = {
.tuner_type = TUNER_ABSENT,
.tuner_addr = ADDR_UNSET,
},
+ [BTTV_BOARD_DIGIFLOWER_DVR2000B] = {
+ .name = "Digi-Flower DVR2000B (master?)",
+ .video_inputs = 16,
+ /* .audio_inputs = 0, */
+ /* .tuner = UNSET, */
+ .svhs = NO_SVHS,
+ .tuner_type = TUNER_ABSENT,
+ .tuner_addr = ADDR_UNSET,
+ /* .radio_addr = ADDR_UNSET, */
+ .no_gpioirq = 1,
+ .gpiomask2 = 0x140007,
+ .muxsel = MUXSEL(2, 6, 10, 14, 2, 6, 10, 14, 2, 6, 10, 14, 2, 6, 10, 14),
+ .muxsel_hook = digiflower_dvr2000b_muxsel,
+ .gpiomux = { 0, 0, 0, 0 }, /* card has no audio */
+ .no_msp34xx = 1,
+ .no_tda9875 = 1,
+ .no_tda7432 = 1,
+ .pll = PLL_28,
+ },
};

static const unsigned int bttv_num_tvcards = ARRAY_SIZE(bttv_tvcards);
@@ -4548,6 +4570,21 @@ static void kodicom4400r_init(struct btt
master[btv->c.nr+2] = btv;
}

+/* DB1 = Top connector fan-out. DB2 = Bottom connector fan-out. */
+#define DB1 0x100000
+#define DB2 0x040000
+
+static void digiflower_dvr2000b_muxsel(struct bttv *btv, unsigned int input)
+{
+ static const int masks[] = {
+ DB1, DB1|1, DB1|2, DB1|3,
+ DB1|4, DB1|5, DB1|6, DB1|7,
+ DB2, DB2|1, DB2|2, DB2|3,
+ DB2|4, DB2|5, DB2|6, DB2|7,
+ };
+ gpio_write(masks[input%16]);
+}
+
/* The Grandtec X-Guard framegrabber card uses two Dual 4-channel
* video multiplexers to provide up to 16 video inputs. These
* multiplexers are controlled by the lower 8 GPIO pins of the
diff -uNrp kernel-2.6.32.orig/drivers/media/video/bt8xx/bttv.h kernel-2.6.32.new/drivers/media/video/bt8xx/bttv.h
--- kernel-2.6.32.orig/drivers/media/video/bt8xx/bttv.h 2010-03-31 23:22:03.987043302 -0600
+++ kernel-2.6.32.new/drivers/media/video/bt8xx/bttv.h 2010-03-31 23:21:45.412041507 -0600
@@ -185,6 +185,7 @@
#define BTTV_BOARD_GEOVISION_GV800S 0x9d
#define BTTV_BOARD_GEOVISION_GV800S_SL 0x9e
#define BTTV_BOARD_PV183 0x9f
+#define BTTV_BOARD_DIGIFLOWER_DVR2000B 0xa0

/* more card-specific defines */
</pre>

[[Image:DVR2510-th.jpg|Digi-Flower DVR-2510-MP2: 16 input; 2 Fusion BT878A chips]]

The DVR2510 has two Fusion BT878A chips. A total of 16 composite inputs that are supported. Eight inputs are routed to each 878A chip, so only one M/D is needed for each 878A.

The two additional M/D are used to route inputs to the composite out monitor connection. This card differs most from its larger cousin in that the Enable pins of the M/D's are connected to the Atmel micro-controller, so the card is not usable until the micro-controller has been initialized. This won't be possible until a logic analyzer can be brought to bear on the problem.

Digiflower

2010-06-01T23:45:38Z

Tuxokc:

I've recently laid hands on a few Digi-Flower capture cards and found no indication that anyone has ever taken the time to poke at these cards with a digital multi-meter to discover how they are laid out.

I have two versions, the DVR2000B-R02, and the DVR2510-MP2.

[[Image:DVR2000B-th.jpg|Digi-Flower DVR-2000B-R02: 16 input; 4 Fusion BT878A chips]]

The DVR2000B has four Fusion bt878A decoders. The DVR2000B supports 16 composite inputs

They both can support 16 composite inputs that are multiplexed through pairs of 74HC4051A Analog Multiplexer/Demultiplexers. Which of the 16 inputs is routed to any of the four bt878A's is controlled by GPIO pins.

Each bt878A device controls a pair of M/D'ers:

<pre>
GPIO[0,1,2] => M/D[1][A,B,C] (select pins)
GPIO[18] => M/D[1][Enable]

GPIO[0,1,2] => M/D[2][A,B,C] (select pins)
GPIO[20] => M/D[2][Enable]
</pre>

When an input has been routed the signal is split between the bt878A's MUX0 and a 4581CS Sync Separator. As far as I can tell the only output of the 4581CS that is used is the Odd/Even field output that is routed to GPIO[15] on the respective 878A

<pre>
74HC4051A
Comp-In (1-8) => M/D[1] (X0-7) -> \ [ L/C/R ] (inductor/
|= [network] capacitor/
Comp-In (9-16) => M/D[2] (X0-7) -> / resistor)

4581CS Sync Separator
L/C/R / Comp-In -> Odd/Even => GPIO[15]
[network] =|
\ 878A: MUX0
</pre>

There is also a fifth pair of Mux/Demux chips that are used to send one of 16 inputs to an RCA jack via a 6db video amp. This routing function is controlled by an Atmel AT89C2051 (8051 family) micro controller. I have not determined how to talk to the micro controller at this time. The I2C pins of the first bt878A is connected to the serial port of the micro controller.

There is also a set of 8 external device I/O ports to send or receive On/Off signals from motion detectors or drive alarm circuits, and an on board WatchDog relay output. These are controlled by GPIO[3-10,12-13] of the first 878A.

More information on the Digi-Flower DVR2000B (DVR2510 is not listed here) cards available from Anko: http://www.anko-tech.com/products/df2000.htm

lspci data for the DVR2000B ( these numbers seem very generic.. how can the specific card be known?)
<pre>
02:00.0 PCI bridge [0604]: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) [3388:0021] (rev 11)
03:0c.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0c.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0d.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0d.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0e.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0e.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0f.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0f.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
</pre>

I've been able to get the DVR2000B working with this patch on linux-2.6.24 kernel----

<pre>
--- drivers/media/video/bt8xx/bttv.h.orig 2008-08-19 12:20:13.000000000 -0500
+++ drivers/media/video/bt8xx/bttv.h 2008-08-19 12:15:32.000000000 -0500
@@ -173,6 +173,7 @@
#define BTTV_BOARD_VOODOOTV_200 0x93
#define BTTV_BOARD_DVICO_FUSIONHDTV_2 0x94
#define BTTV_BOARD_TYPHOON_TVTUNERPCI 0x95
+#define BTTV_BOARD_DIGIFLOWER_DVR2000B 0x96

/* more card-specific defines */
#define PT2254_L_CHANNEL 0x10
--- drivers/media/video/bt8xx/bttv-cards.c.orig 2008-08-19 12:02:31.000000000 -0500
+++ drivers/media/video/bt8xx/bttv-cards.c 2008-08-19 12:52:58.000000000 -0500
@@ -81,6 +81,8 @@ static void tibetCS16_init(struct bttv *
static void kodicom4400r_muxsel(struct bttv *btv, unsigned int input);
static void kodicom4400r_init(struct bttv *btv);

+static void digiflower_dvr2000b_muxsel(struct bttv *btv, unsigned int input);
+
static void sigmaSLC_muxsel(struct bttv *btv, unsigned int input);
static void sigmaSQ_muxsel(struct bttv *btv, unsigned int input);

@@ -314,6 +316,7 @@ static struct CARD {
{ 0xd50018ac, BTTV_BOARD_DVICO_FUSIONHDTV_5_LITE, "DViCO FusionHDTV 5 Lite" },
{ 0x00261822, BTTV_BOARD_TWINHAN_DST, "DNTV Live! Mini "},
{ 0xd200dbc0, BTTV_BOARD_DVICO_FUSIONHDTV_2, "DViCO FusionHDTV 2" },
+ { 0x00000000, BTTV_BOARD_DIGIFLOWER_DVR2000B, "Digi-Flower DVR2000B" },

{ 0, -1, NULL }
};
@@ -3005,6 +3008,25 @@ struct tvcard bttv_tvcards[] = {
.tuner_addr = ADDR_UNSET,
.radio_addr = ADDR_UNSET,
},
+ [BTTV_BOARD_DIGIFLOWER_DVR2000B] = {
+ .name = "Digi-Flower DVR2000B (master?)",
+ .video_inputs = 16,
+ .audio_inputs = 0,
+ .tuner = UNSET,
+ .svhs = UNSET,
+ .tuner_type = TUNER_ABSENT,
+ .tuner_addr = ADDR_UNSET,
+ .radio_addr = ADDR_UNSET,
+ .no_gpioirq = 1,
+ .gpiomask2 = 0x140007,
+ .muxsel = { 2,6,10,14, 2,6,10,14, 2,6,10,14, 2,6,10,14 },
+ .muxsel_hook = digiflower_dvr2000b_muxsel,
+ .gpiomux = { 0, 0, 0, 0 }, /* card has no audio */
+ .no_msp34xx = 1,
+ .no_tda9875 = 1,
+ .no_tda7432 = 1,
+ .pll = PLL_28,
+ },
};

static const unsigned int bttv_num_tvcards = ARRAY_SIZE(bttv_tvcards);
@@ -4887,6 +4909,21 @@ static void kodicom4400r_init(struct btt
master[btv->c.nr+2] = btv;
}

+/* DB1 = Top connector fan-out. DB2 = Bottom connector fan-out. */
+#define DB1 0x100000
+#define DB2 0x040000
+
+static void digiflower_dvr2000b_muxsel(struct bttv *btv, unsigned int input)
+{
+ static const int masks[] = {
+ DB1, DB1|1, DB1|2, DB1|3,
+ DB1|4, DB1|5, DB1|6, DB1|7,
+ DB2, DB2|1, DB2|2, DB2|3,
+ DB2|4, DB2|5, DB2|6, DB2|7,
+ };
+ gpio_write(masks[input%16]);
+}
+
/* The Grandtec X-Guard framegrabber card uses two Dual 4-channel
* video multiplexers to provide up to 16 video inputs. These
* multiplexers are controlled by the lower 8 GPIO pins of the
</pre>

[[Image:DVR2510-th.jpg|Digi-Flower DVR-2510-MP2: 16 input; 2 Fusion BT878A chips]]

The DVR2510 has two Fusion BT878A chips. Eight inputs are routed to each 878A chip, so only one M/D is needed for each 878A. The two additional M/D are used to route inputs to the composite out monitor connection. This card differs most from its larger cousin in that the Enable pins of the M/D's are connected to the Atmel micro-controller, so the card is not usable until the micro-controller has been initialized.

File:DVR2510-th.jpg

2010-06-01T23:21:41Z

Tuxokc: Digiflower DVR2510-MP2

Digiflower DVR2510-MP2

Digiflower

2008-09-02T02:51:29Z

Tuxokc: Add the patch

[[Image:DVR2000B-th.jpg|Digi-Flower DVR-2000B-R02: 16 input; 4 Fusion BT878A chips]]

I've recently laid hands on a few Digi-Flower capture cards and found no indication that anyone has ever taken the time to poke at these cards with a digital multi-meter to discover how they are laid out.

I have two versions, the DVR2000B-R02, and the DVR2510-MP2. The DVR2000B has four Fusion bt878A decoders, while the DVR2510 has two. I'm going to concentrate on the DVR2000B. The smaller 2510 seems to have the odd numbered fanout inputs on the first chip, and the even numbered inputs on the second.

They both can support 16 composite inputs that are multiplexed through pairs of 74HC4051A Analog Multiplexer/Demultiplexers. Which of the 16 inputs is routed to any of the four bt878A's is controlled by GPIO pins.

Each bt878A device controls a pair of M/D'ers:

<pre>
GPIO[0,1,2] => M/D[1][A,B,C] (select pins)
GPIO[18] => M/D[1][Enable]

GPIO[0,1,2] => M/D[2][A,B,C] (select pins)
GPIO[20] => M/D[2][Enable]
</pre>

When an input has been routed the signal is split between the bt878A's MUX0 and a 4581CS Sync Separator. As far as I can tell the only output of the 4581CS that is used is the Odd/Even field output that is routed to GPIO[15] on the respective 878A

<pre>
74HC4051A
Comp-In (1-8) => M/D[1] (X0-7) -> \ [ L/C/R ] (inductor/
|= [network] capacitor/
Comp-In (9-16) => M/D[2] (X0-7) -> / resistor)

4581CS Sync Separator
L/C/R / Comp-In -> Odd/Even => GPIO[15]
[network] =|
\ 878A: MUX0
</pre>

There is also a fifth pair of Mux/Demux chips that are used to send one of 16 inputs to an RCA jack via a 6db video amp. This routing function is controlled by an Atmel AT89C2051 (8051 family) micro controller. I have not determined how to talk to the micro controller at this time. The I2C pins of the first bt878A is connected to the serial port of the micro controller.

There is also a set of 8 external device I/O ports to send or receive On/Off signals from motion detectors or drive alarm circuits, and an on board WatchDog relay output. These are controlled by GPIO[3-10,12-13] of the first 878A.

More information on the Digi-Flower DVR2000B (DVR2510 is not listed here) cards available from Anko: http://www.anko-tech.com/products/df2000.htm

lspci data for the DVR2000B ( these numbers seem very generic.. how can the specific card be known?)
<pre>
02:00.0 PCI bridge [0604]: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) [3388:0021] (rev 11)
03:0c.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0c.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0d.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0d.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0e.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0e.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0f.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0f.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
</pre>

I've been able to get the DVR2000B working with this patch on linux-2.6.24 kernel----

<pre>
--- drivers/media/video/bt8xx/bttv.h.orig 2008-08-19 12:20:13.000000000 -0500
+++ drivers/media/video/bt8xx/bttv.h 2008-08-19 12:15:32.000000000 -0500
@@ -173,6 +173,7 @@
#define BTTV_BOARD_VOODOOTV_200 0x93
#define BTTV_BOARD_DVICO_FUSIONHDTV_2 0x94
#define BTTV_BOARD_TYPHOON_TVTUNERPCI 0x95
+#define BTTV_BOARD_DIGIFLOWER_DVR2000B 0x96

/* more card-specific defines */
#define PT2254_L_CHANNEL 0x10
--- drivers/media/video/bt8xx/bttv-cards.c.orig 2008-08-19 12:02:31.000000000 -0500
+++ drivers/media/video/bt8xx/bttv-cards.c 2008-08-19 12:52:58.000000000 -0500
@@ -81,6 +81,8 @@ static void tibetCS16_init(struct bttv *
static void kodicom4400r_muxsel(struct bttv *btv, unsigned int input);
static void kodicom4400r_init(struct bttv *btv);

+static void digiflower_dvr2000b_muxsel(struct bttv *btv, unsigned int input);
+
static void sigmaSLC_muxsel(struct bttv *btv, unsigned int input);
static void sigmaSQ_muxsel(struct bttv *btv, unsigned int input);

@@ -314,6 +316,7 @@ static struct CARD {
{ 0xd50018ac, BTTV_BOARD_DVICO_FUSIONHDTV_5_LITE, "DViCO FusionHDTV 5 Lite" },
{ 0x00261822, BTTV_BOARD_TWINHAN_DST, "DNTV Live! Mini "},
{ 0xd200dbc0, BTTV_BOARD_DVICO_FUSIONHDTV_2, "DViCO FusionHDTV 2" },
+ { 0x00000000, BTTV_BOARD_DIGIFLOWER_DVR2000B, "Digi-Flower DVR2000B" },

{ 0, -1, NULL }
};
@@ -3005,6 +3008,25 @@ struct tvcard bttv_tvcards[] = {
.tuner_addr = ADDR_UNSET,
.radio_addr = ADDR_UNSET,
},
+ [BTTV_BOARD_DIGIFLOWER_DVR2000B] = {
+ .name = "Digi-Flower DVR2000B (master?)",
+ .video_inputs = 16,
+ .audio_inputs = 0,
+ .tuner = UNSET,
+ .svhs = UNSET,
+ .tuner_type = TUNER_ABSENT,
+ .tuner_addr = ADDR_UNSET,
+ .radio_addr = ADDR_UNSET,
+ .no_gpioirq = 1,
+ .gpiomask2 = 0x140007,
+ .muxsel = { 2,6,10,14, 2,6,10,14, 2,6,10,14, 2,6,10,14 },
+ .muxsel_hook = digiflower_dvr2000b_muxsel,
+ .gpiomux = { 0, 0, 0, 0 }, /* card has no audio */
+ .no_msp34xx = 1,
+ .no_tda9875 = 1,
+ .no_tda7432 = 1,
+ .pll = PLL_28,
+ },
};

static const unsigned int bttv_num_tvcards = ARRAY_SIZE(bttv_tvcards);
@@ -4887,6 +4909,21 @@ static void kodicom4400r_init(struct btt
master[btv->c.nr+2] = btv;
}

+/* DB1 = Top connector fan-out. DB2 = Bottom connector fan-out. */
+#define DB1 0x100000
+#define DB2 0x040000
+
+static void digiflower_dvr2000b_muxsel(struct bttv *btv, unsigned int input)
+{
+ static const int masks[] = {
+ DB1, DB1|1, DB1|2, DB1|3,
+ DB1|4, DB1|5, DB1|6, DB1|7,
+ DB2, DB2|1, DB2|2, DB2|3,
+ DB2|4, DB2|5, DB2|6, DB2|7,
+ };
+ gpio_write(masks[input%16]);
+}
+
/* The Grandtec X-Guard framegrabber card uses two Dual 4-channel
* video multiplexers to provide up to 16 video inputs. These
* multiplexers are controlled by the lower 8 GPIO pins of the
</pre>

File:DVR2000B-th.jpg

2008-09-02T02:26:05Z

Tuxokc:

Digi-Flower DVR-2000B-R02: 16 input; 4 Fusion BT878A chips

Digiflower

2008-09-02T02:21:27Z

Tuxokc:

[[Image:DVR2000B-th.jpg]]

I've recently laid hands on a few Digi-Flower capture cards and found no indication that anyone has ever taken the time to poke at these cards with a digital multi-meter to discover how they are laid out.

I have two versions, the DVR2000B-R02, and the DVR2510-MP2. The DVR2000B has four Fusion bt878A decoders, while the DVR2510 has two. I'm going to concentrate on the DVR2000B. The smaller 2510 seems to have the odd numbered fanout inputs on the first chip, and the even numbered inputs on the second.

They both can support 16 composite inputs that are multiplexed through pairs of 74HC4051A Analog Multiplexer/Demultiplexers. Which of the 16 inputs is routed to any of the four bt878A's is controlled by GPIO pins.

Each bt878A device controls a pair of M/D'ers:

<pre>
GPIO[0,1,2] => M/D[1][A,B,C] (select pins)
GPIO[18] => M/D[1][Enable]

GPIO[0,1,2] => M/D[2][A,B,C] (select pins)
GPIO[20] => M/D[2][Enable]
</pre>

When an input has been routed the signal is split between the bt878A's MUX0 and a 4581CS Sync Separator. As far as I can tell the only output of the 4581CS that is used is the Odd/Even field output that is routed to GPIO[15] on the respective 878A

<pre>
74HC4051A
Comp-In (1-8) => M/D[1] (X0-7) -> \ [ L/C/R ] (inductor/
|= [network] capacitor/
Comp-In (9-16) => M/D[2] (X0-7) -> / resistor)

4581CS Sync Separator
L/C/R / Comp-In -> Odd/Even => GPIO[15]
[network] =|
\ 878A: MUX0
</pre>

I've been able to get the DVR2000B working with this patch ----

There is also a fifth pair of Mux/Demux chips that are used to send one of 16 inputs to an RCA jack via a 6db video amp. This routing function is controlled by an Atmel AT89C2051 (8051 family) micro controller. I have not determined how to talk to the micro controller at this time. The I2C pins of the first bt878A is connected to the serial port of the micro controller.

There is also a set of 8 external device I/O ports to send or receive On/Off signals from motion detectors or drive alarm circuits, and an on board WatchDog relay output. These are controlled by GPIO[3-10,12-13] of the first 878A.

More information on the Digi-Flower DVR2000B (DVR2510 is not listed here) cards available from Anko: http://www.anko-tech.com/products/df2000.htm

lspci data for the DVR2000B ( these numbers seem very generic.. how can the specific card be known?)

02:00.0 PCI bridge [0604]: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) [3388:0021] (rev 11)
03:0c.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0c.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0d.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0d.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0e.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0e.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0f.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0f.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)

File:DVR2000B-th.jpg

2008-09-02T02:20:09Z

Tuxokc: 16 input; 4 Fusion BT878A chips

16 input; 4 Fusion BT878A chips

Digiflower

2008-09-02T02:12:58Z

Tuxokc: Digi-flower DVR-2000B

[[Image:DVR2000B.jpg]]

I've recently laid hands on a few Digi-Flower capture cards and found no indication that anyone has ever taken the time to poke at these cards with a digital multi-meter to discover how they are laid out.

I have two versions, the DVR2000B-R02, and the DVR2510-MP2. The DVR2000B has four Fusion bt878A decoders, while the DVR2510 has two. I'm going to concentrate on the DVR2000B. The smaller 2510 seems to have the odd numbered fanout inputs on the first chip, and the even numbered inputs on the second.

They both can support 16 composite inputs that are multiplexed through pairs of 74HC4051A Analog Multiplexer/Demultiplexers. Which of the 16 inputs is routed to any of the four bt878A's is controlled by GPIO pins.

Each bt878A device controls a pair of M/D'ers:

<pre>
GPIO[0,1,2] => M/D[1][A,B,C] (select pins)
GPIO[18] => M/D[1][Enable]

GPIO[0,1,2] => M/D[2][A,B,C] (select pins)
GPIO[20] => M/D[2][Enable]
</pre>

When an input has been routed the signal is split between the bt878A's MUX0 and a 4581CS Sync Separator. As far as I can tell the only output of the 4581CS that is used is the Odd/Even field output that is routed to GPIO[15] on the respective 878A

<pre>
74HC4051A
Comp-In (1-8) => M/D[1] (X0-7) -> \ [ L/C/R ] (inductor/
|= [network] capacitor/
Comp-In (9-16) => M/D[2] (X0-7) -> / resistor)

4581CS Sync Separator
L/C/R / Comp-In -> Odd/Even => GPIO[15]
[network] =|
\ 878A: MUX0
</pre>

I've been able to get the DVR2000B working with this patch ----

There is also a fifth pair of Mux/Demux chips that are used to send one of 16 inputs to an RCA jack via a 6db video amp. This routing function is controlled by an Atmel AT89C2051 (8051 family) micro controller. I have not determined how to talk to the micro controller at this time. The I2C pins of the first bt878A is connected to the serial port of the micro controller.

There is also a set of 8 external device I/O ports to send or receive On/Off signals from motion detectors or drive alarm circuits, and an on board WatchDog relay output. These are controlled by GPIO[3-10,12-13] of the first 878A.

More information on the Digi-Flower DVR2000B (DVR2510 is not listed here) cards available from Anko: http://www.anko-tech.com/products/df2000.htm

lspci data for the DVR2000B ( these numbers seem very generic.. how can the specific card be known?)

02:00.0 PCI bridge [0604]: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) [3388:0021] (rev 11)
03:0c.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0c.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0d.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0d.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0e.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0e.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)
03:0f.0 Multimedia video controller [0400]: Brooktree Corporation Bt878 Video Capture [109e:036e] (rev 11)
03:0f.1 Multimedia controller [0480]: Brooktree Corporation Bt878 Audio Capture [109e:0878] (rev 11)

File:DVR2000B.jpg

2008-09-01T22:06:51Z

Tuxokc: 16 inputs, 4 bt878 chips

16 inputs, 4 bt878 chips

Hardware Compatibility List

2008-09-01T21:46:46Z

Tuxokc: /* Link to Digiflower page */

Zoneminder will work with almost any capture card that is supported by the linux kernel.

AKA; HCL, Hardware Compatibility List

== Capture Cards ==

[[Pico2000]] - 4 port card, one chip bt878, around 2 fps when using all channels

[[Bt878_4chip_8inputs]] - I don't know the name for it, 4 chips bt878, 8 inputs, around 5 fps when using 2 inputs per chip

[[:Image:Karta.jpg| bt878 8 chip 8 input]] - options bttv card=77,77,77,77,77,77,77,77

[[Hauppauge]]

[[Ituner Spectra 8]] [http://www.ituner.com/spectra.htm]

[[Linux Media Labs LMLBT44]] [http://www.linuxmedialabs.com]

[[Hawkeye]]

[[Avermedia]]

[[TView 95/99]]

[[WinFast TV2000 XP]]

[[Osprey 100]]

[[Grandtec Grand X Guard]] [http://www.grandtec.com/xguard.htm]

[[Kodicom 4400r]]

Leadtek WinFast VC 100 - the cheapest bt878 model with no tuner on it, just Com/Svideo in.

[[Digiflower]]

Most other BTTV (bt878, bt848) cards, see /usr/src/linux/Documentation/video4linux/bttv/CARDLIST on your system for a list of some of them.

A note on the bt8x8-based TV-tuner cards: these usually have beside the tuner input, also a Composite and an S-Video input. You can hook up 2 analog cameras to these, and access from ZoneMinder both of them as individual cameras, at max 15Fps. You don't need two separate TV cards for two cameras!

== Analog Cameras ==

Any regular composite or S-video camera connected via a supported capture card. Some analog cameras feature camera control - ZM supports several of these camera's Pan/Tilt/Zoom functions via serial port control, as well as camera Presets, Focus, Iris, etc.
*[[PicturetelControlScript | PictureTel PTZ2N]].

== Network Cameras ==
For Network Cams to work they need to be able to stream MJPEG without the requirement of activex controls. If you see the requirement for the camera calls for IE then there is a good chance it may not work. The other option is to grab JPEG images if the camera supports that option which will work but at a lower frame rate.

* [[Axis]] (just about all recent models, including support for PTZ functions)

* [[D-Link]]

* [[Airlink 101]]

* [[Conceptronic]]

* [[Gadspot]] GS9603 IP Camera with Pan/Tilt, As well as the GS1600(H).

* [[Grandtec]] [[Grandtec_WLAN_Camera|WLAN Camera]] WiFi or III - acceptable indoor quality, no infrared-filter (better nightvision) cheap!

* [[Intellinet]] IPCamera with the new firmware.
* Old Intellinet IPCamera (model MWNC-100) with this (http://www.zoneminder.com/forums/viewtopic.php?t=7500) protocol adapter.

* [[Level One]] [[WCS-1090]]

* OvisLink AirLive WL-5400CAM

* [[Panasonic]]

* [[Sony]] SNC-M1 and SNC-M3 wired and wireless - including PTZ support. Possibly other Sony SNC-, RZ-, and IP- series?

* [[Trendnet]] TV-IP200 / TV-IP200W, TV-IP300 and the TV-IP400 / TV-IP400W with PTZ control support.

* [[Veo Observer IP NetCam]] / Orite IP-Cam IC-301 / Sweex IP Network Camera JA200010 / other clones

* Any network camera that allows access to single JPEG image grabs or '''some but not all''' multi-part JPEG feeds.

== Network Digitizers ==

Like Network Cameras, these devices produce a video stream - but they accept an analog video input from a camera or other video source.

*The [[IP9100 | Aviosys IP9100, Models A, B and Plus]] has four analog video inputs. It produces a ZM compatible video stream from one of the inputs, which is selectable via an HTTP GET command. There might even be a control script for ZM that lets you select the active video input using ''ZM's Camera Control Presets!''

== USB Cameras ==

*Just Zoom USB cam

*Creative Webcam Pro, Webcam 3

*[[Logitech QuickCam Express]], QuickCam Pro 3000, QuickCam Communicate STX

*Logitech Quickcam Orbit/Sphere (experimental basic pan/tilt control has also published for testing and hacking [http://www.zoneminder.com/forums/viewtopic.php?t=9788])

*[[Philips]]

*Any OV511 based USB camera [http://alpha.dyndns.org/ov511/cameras.html]

*Any CPIA based USB camera [http://webcam.sourceforge.net]

*[[LabTec WebCam Pro]]

* Indirectly supports any [[Uvc | UVC/V4L2]] supported cam such as Logitech Quickcam Pro 5000 using [[Uvc | UVC Streaming]] .

'''Note that most USB cameras that can use Video4Linux, and so can be used by ZoneMinder, have older chipsets and can be hard to find new.'''
'''Note that PWC drivers are not included in the kernel. Some distribution's add them in and other may not. Here are some relevant links.'''
[http://www.smcc.demon.nl/webcam/ Old Maintainer]
[http://www.saillard.org/linux/pwc/ Current PWC Maintainer]

== X10 Devices ==
The only device that really needs to be compatable with ZM is the Transceiver, all other x10 devices comunicate through that device.
*[[CM11]] Bi-Directional Transceiver

Other X10 notes:

[http://www.zoneminder.com/forums/viewtopic.php?t=6423&highlight=x10 Topic 6423]

[http://www.zoneminder.com/forums/viewtopic.php?t=7082&highlight=x10 Topic 7082]

== All other hardware as supported by Linux ==
To find out if your hardware is supported, check the HCL at [http://www.linuxquestions.org/hcl/ linuxquestions.org]

[http://kmuto.jp/debian/hcl/ Debian]

[http://fedoraproject.org/wiki/HCL Fedora] [http://fedora-linux.nl/wiki/index.php/HCL Fedora Unofficial HCL]

[http://www.mandriva.com/hardware Mandriva]

[https://hardware.redhat.com/hwcert/index.cgi RedHat]

[http://en.opensuse.org/Hardware Suse]

[http://doc.gwos.org/index.php/HCL Ubuntu]