Print

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

[acellier]

We bought a new DCS-931L to try again - having tried and returned one last summer.
These cameras have an unfortunate tendency to garble the image, as you can see at:

<url>http://smg.photobucket.com/user/acellier/media/DCS-931L_Errors/CamN_2014020517293501.jpg.html</url>
<url>http://smg.photobucket.com/user/acellier/library/DCS-931L_Errors</url>

It's really too bad, as otherwise this model; has a lot going for it.
BTW, we did install the latest v1.02 firmware.

[JavaLawyer]

Do the image artifacts appear on both MJPEG and H.264? My camera is usually set to MJPEG and I haven't encountered this issue.

[acellier]

This is in mjpeg.
I guess I keep getting the bad cameras.

[JavaLawyer]

LOL. . . I don't use motion detection on that particular camera, so it's possible my camera has the same issue, I'm just not catching it.  I'll need to setup motion detection to see if I'm hitting any false positives.

[acellier]

seems to USUALLY corrupt the first image upon motion detection ...

[JavaLawyer]

I setup motion detection with FTP image notification to try to replicate this issue. For testing consistency, what are your video, motion detection, and image capture settings?

[acellier]

Video:   MJPEG 640x480, VeryHigh, Auto:  Default: MJPEG
Moption Detection:   Enable, Time: Always; 65%; all boxes ON
FTP:   Passive: Yes (does not matter)
    Schedule: Enable upload - Motion
    Image frequency: 1 frames/second
    Date/Time Suffix, 0.5 hour

[JavaLawyer]

Video:   MJPEG 640x480, VeryHigh, Auto:  Default: MJPEG
Moption Detection:   Enable, Time: Always; 65%; all boxes ON
FTP:   Passive: Yes (does not matter)
    Schedule: Enable upload - Motion
    Image frequency: 1 frames/second
    Date/Time Suffix, 0.5 hour

I've mirrored your settings. With what frequency are you getting frames with image artifacts?

[acellier]

not every "event", but too many to count, usually at onset.
A shame that this error persists.
My money is on a circuit timing issue.

[JavaLawyer]

So I ran motion detection with FTP using the settings you provided for approximately 5 days.  The area I was monitoring has some moderate activity during certain parts of the day, so there were a good number of valid motion detection events. All said, the FTP directory contained over 11,000 images, most of which were due to valid activity, while a smaller percentage were due to changing light conditions which I could have eliminated had I changed the sensitivity, but I was mirroring your settings.  

Of all 11,000+ images, there were only "5" that had image artifacts that looked identical to what you experienced, three of which occurred on the same day. All things being equal, that would equate to an average of one artifact per day.

[acellier]

Your experience is *much* more benign that mine.
Just to randomly sample a few 1/2 hour intervals -
Wed, Feb 12, 11:00 AM ... 39 images - 3 bad
Tue, Feb 11, 08:30 AM ... 32 images - 1 bad
Wed, Feb 12, 02:30 PM ... 41 images - 1 bad
Sat, Feb 08, 10:30 AM ... 9 images - 1 bad
Fri, Feb 07, 01:00 PM ... 5 images - 1 bad
Thu, Feb 13, 08:00 AM ... 30 images - 0 bad
Wed, Feb 12, 02:30 PM ... 41 images - 1 bad

[JavaLawyer]

I misread the time stamps. It looks like all 5 instances took place over a two hour window during that five day period, which makes this all the more confounding.

Could these artifacts be caused by some form of intermittent environmental interference (e.g. electrical)? This is the only root cause that I can come up with that would explain the indeterminacy and extreme difference in frequency on different cameras of the same model. It would be interesting to test a camera known to have these issues on another off-premise network to see if there's any change in behavior.

     

[acellier]

this happens with 2 different routers, to 2 different servers

[JavaLawyer]

I passed my findings, as well as all of the related DCS-931L and DCS-933L links, to D-Link.  I'll post back if I hear anything.   

As an FYI, aside from posting in this forum, D-Link often escalates issues based on the quantity of reports they receive through their support desk. A large volume of tickets with the same issue raises a flag. You may want to log this issue with technical support for that reason alone: 1-888-851-6464

[gajego]

I passed my findings, as well as all of the related DCS-931L and DCS-933L links, to D-Link.  I'll post back if I hear anything.   

As an FYI, aside from posting in this forum, D-Link often escalates issues based on the quantity of reports they receive through their support desk. A large volume of tickets with the same issue raises a flag. You may want to log this issue with technical support for that reason alone: 1-888-851-6464

I've been waiting in a queue for 40 min. gave up ...