Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[acellier]

Here is a collection of observed bugs with our DCS-930L, operating with the latest firmware v1.03 build 3.

DCS-930L Processor appears to be overloaded, seen in frequent unresponsiveness and long  (and variable) ping times. By comparison, the DCS-932L is quite fast in response, showing that the less comples 930 should be able to perform more reliably. Perhaps the firmware needs a tuneup based on the 932? [But without the 932’s unfortunate fixed 15 fps in motion detection + ftp].

[Our system is MacOS 10.6.8, iMac (2008), Firefox v6.01, Linksys WNDR3700 router]

1.  Symptom of overload - Ping times - DCS-930L   12 trials
PING 10.0.1.31 (10.0.1.31): 56 data bytes
64 bytes from 10.0.1.31: icmp_seq=0 ttl=64 time=155.391 ms
64 bytes from 10.0.1.31: icmp_seq=1 ttl=64 time=583.864 ms
64 bytes from 10.0.1.31: icmp_seq=2 ttl=64 time=370.908 ms
64 bytes from 10.0.1.31: icmp_seq=3 ttl=64 time=749.338 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
64 bytes from 10.0.1.31: icmp_seq=4 ttl=64 time=2204.646 ms
64 bytes from 10.0.1.31: icmp_seq=5 ttl=64 time=2900.869 ms
64 bytes from 10.0.1.31: icmp_seq=6 ttl=64 time=2297.654 ms
64 bytes from 10.0.1.31: icmp_seq=7 ttl=64 time=1514.244 ms
64 bytes from 10.0.1.31: icmp_seq=8 ttl=64 time=1811.168 ms
64 bytes from 10.0.1.31: icmp_seq=9 ttl=64 time=974.263 ms
64 bytes from 10.0.1.31: icmp_seq=10 ttl=64 time=1840.455 ms
64 bytes from 10.0.1.31: icmp_seq=11 ttl=64 time=1104.301 ms
--- ping statistics ---
12 packets transmitted, 12 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 155.391/1375.592/2900.869/818.587 ms

Ping times - DCS-932L   12 trials
PING 10.0.1.32 (10.0.1.32): 56 data bytes
64 bytes from 10.0.1.32: icmp_seq=0 ttl=64 time=1.859 ms
64 bytes from 10.0.1.32: icmp_seq=1 ttl=64 time=1.743 ms
64 bytes from 10.0.1.32: icmp_seq=2 ttl=64 time=1.878 ms
64 bytes from 10.0.1.32: icmp_seq=3 ttl=64 time=1.156 ms
64 bytes from 10.0.1.32: icmp_seq=4 ttl=64 time=1.212 ms
64 bytes from 10.0.1.32: icmp_seq=5 ttl=64 time=1.893 ms
64 bytes from 10.0.1.32: icmp_seq=6 ttl=64 time=1.350 ms
64 bytes from 10.0.1.32: icmp_seq=7 ttl=64 time=1.203 ms
64 bytes from 10.0.1.32: icmp_seq=8 ttl=64 time=1.087 ms
64 bytes from 10.0.1.32: icmp_seq=9 ttl=64 time=20.314 ms
64 bytes from 10.0.1.32: icmp_seq=10 ttl=64 time=1.664 ms
64 bytes from 10.0.1.32: icmp_seq=11 ttl=64 time=1.241 ms
--- ping statistics ---
12 packets transmitted, 12 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.087/3.050/20.314/5.214 ms

2.  Another example of overload - Set for Motion Detection + ftp, the camera sometimes sends no image, or just the very top of a frame, and often not a sequence of frames showing the moving object. There is a rather long delay - several seconds - before anything is sent.

3.  Another indication of overload - the 930 occasionally sends the ftp server a spurious, unused dated folder inside the already-created dated folder, e.g. 20110904 inside 20110904

4.  Misleading, sometimes incorrect date/time report on browser’s Status page, http://xxxx/stsdev.htm - The time advances even when the camera is off - this is a false indication of continuing operation. Apparently a java script running alone.

5.  If user enters a Primary DNS in the Network Setup pane but has selected DHCP (which does not need DNS specified), that Primary DNS appears as Secondary DNS in the Status pane. Probably should not appear in Status?

6.  The DCS-930L actual frame rate (in Live Video viewed at mydlink.com) seems to vary randomly, sometimes dropping as low as 200kbps, rarely staying at level corresponding to selected fps. Image seems to freeze at times.

7.  Another example of overload -  the live video window  (http://x.x.x.x/jview.htm) sometimes comes up blank, and has to be refreshed. The Date/Time header sometimes does not appear, and is sometimes garbled:

[acellier]

    Our weather temperatures were significantly cooler this weekend, and the DCS-930L behaved somewhat better. But still quite flakey. This points to a definite thermal problem - not sure if it's just my unit, or a generic design issue.
    I have the DCS-930L and DCS-932L sitting side-by-side looking out a window, and settings identical. No valid reason for the disparity in behavior.
    I'm going to go for an RMA, preferably a swap for a 932.

[JavaLawyer]

I recall reading another thread some time ago about a DCS-930 (I think) that had issues that looked temperature related. Unit behaved erratically only when positioned in front of a window. . . I presumed the direct sunlight caused issues.

[acellier]

not in direct sunlight at all