Just wanted to put a notice out there that D-Link has changed their DCS-900 product to a Revision B. In short...it is not that great. In the past I have used the Revision A DCS-900 and got a solid 10FPS using the path of /video.cgi. Well, the path of video.cgi on the Rev B camera will get you no where so you resort to /image.jpg which will only produce 3FPS no matter what settings you throw at either zoneminder or the camera itself.
Personally, I am really getting sick of Dlink and I am about to convert to recommending only Axis from now on.
I am going to miss my little Rev A DCS-900 cams...they were an inexpensive solution for some of the non-profits that I deal with.
Strange that a revised firmware should break performance so much. Does it do anything else extra to make up for it?
Wed Sep 06, 2006 5:59 pm
Joined: Wed Jan 11, 2006 1:19 pm Posts: 442
Might not just be the firmware - I know Linksys sometimes change everything between versions on some of their products, including processor, embedded OS etc.
My guess is that they've found a cheaper way of producing the product using cheaper or fewer components and either the initial firmware is full of bugs, or they've cynically accepted that the revised hardware is "Good enough for some".
The lower cost IP cams I've tried (except gadspot) seem to be marketted as "remote low-res webcams" instead of what we here expect, something capable of capturing a moving image and being able to make out a face. I suspect the manufacturers are relying heavily on the novelty value to a market that doesn't really need them or who don't know better - Geeky Gizmos.
Thu Sep 07, 2006 7:02 am
Joined: Mon Sep 18, 2006 6:06 pm Posts: 13
This issue IS a bug in the firmware (a change in the jpeg stream that is sent).
To work around, use the URL /mjpeg.cgi and turn OFF regex matching.
I'm seeing up to 30fps using a DCS-900.
I'll update/create a wiki page here shortly.
Tue Oct 10, 2006 3:53 pm
Joined: Fri Apr 06, 2007 10:23 am Posts: 1
30 fps with DCS-900 A or B?
Yesterday, I installed D-Link DCS-900 rev B2, but I'm getting 5fps at average. Load of the system is about 2.
11:28:00 up 1:52, 2 users, load average: 2.09, 2.40, 1.79
Have you got some suggestions, how to improve these bad results?
I have configured the camera in Zone minder like this:
Source Type: Remote
Remote host name: user:firstname.lastname@example.org
Remote host port: 80 (the wiki sais its the default port and I havent change it).
Remote Host path: I have tried everyting: -still.jpg
And nothing works. I have tried as well with regex matching off and on. Nothing
What am I doing wrong?. I can use the camera through its web interface but I cant get it working with zone minder.
PD: Also I get a 1 or 2 seconds lag when I see the image no matter how much compresion I use. Guess thats normal for that cam. Its not problem of the lan cause I have connected the camera to a Gig swight and from there to the computer through a Gig ethernet card. Can someon confirm that the 1 or 2 second la is normal?
Tue Apr 10, 2007 3:46 pm
Joined: Sun Apr 08, 2007 11:03 pm Posts: 17
Please, can someone help? I cant get it working with zm.
Thu Apr 12, 2007 12:57 pm
Joined: Wed Jun 08, 2005 9:07 pm Posts: 5078 Location: Midlands UK
i think i rember dlinks being poorly supported on linux. But have you checked you matched your monitor settings to the cam image, and what is in your logs
Thanks for the reply I have been three days trying to get the camera working and looking over the internet but I just can get my mind on what it is.
The camera works fine if I acces direcly through firefox so I guess its no a linux problem.
The log I get in zmwatch.log is this:
04/12/07 19:49:20.799929 zmwatch.ERR [Can't get shared memory id '7a6d2001', 1: No such file or directory]
04/12/07 19:49:20.800145 zmwatch.INF [Restarting capture daemon for Cam1, shared memory not valid]
04/12/07 19:49:20.927068 zmwatch.INF ['zmc -m 1' starting at 07/04/12 19:49:20, pid = 26280]
To work around, use the URL /mjpeg.cgi and turn OFF regex matching. I'm seeing up to 30fps using a DCS-900.
Have you tried this path at all?
The other option is to put the cam in the wild Like W. suggested and someone from the forum can have a go at it.
The big thing is you got to get around the 404 error Which suggests that you are talking to the cam but it is either rejecting the request because your not authorized or the path is not valid.
Users browsing this forum: No registered users and 1 guest
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum