D-Link Forums

D-Link IP Cameras for Home => DCS-2330L => Topic started by: leviny on November 19, 2015, 12:27:15 PM

Title: 2330L fails after a few hours
Post by: leviny on November 19, 2015, 12:27:15 PM
I have 3 2330Ls and 1 2332L. Two of the 2330L's "fail" consistently after a few hours. They begin to show video in "false" color, and they do not generate notifications on the mobile app, nor are they reachable on it (shows a red X).

They are connected with Ethernet cables, not wireless (my third 2330L is wireless and doesn't do this... not sure that's related.) Both are the latest FW 1.11 but were doing this with the previous fw too. rebooting solves the problem, until it happens again a few hours later. I have the cameras set to reboot each morning at 7am. I usually lose them before lunch.

anyone seeing this on your cameras? any ideas?

"false color" (and mobile app cannot connect to camera, no push notifications)
(http://leviny.ddns.net/Capture.PNG)

Normal (after rebooting)
(http://leviny.ddns.net/Capture2.PNG)
Title: Re: 2330L fails after a few hours
Post by: FurryNutz on November 19, 2015, 12:49:10 PM
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)


What Mfr and model is the main host router?
What wireless modes are you using?
What is the distance between the Camera and the main host router?
I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool: 192.168.#.23 and .24 and so on.  DHCP (http://forums.dlink.com/index.php?topic=58017.0)

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com (http://forums.dlink.com/index.php?topic=62395.0)

I recommend trying a factory reset, manually re-load FW, factory reset once more then test for problem. If the problem still happens then these units are faulty and needs to be RMAd. Let us know how it goes.
Title: Re: 2330L fails after a few hours
Post by: leviny on November 19, 2015, 03:55:42 PM
USA
router is netgear R7000
not using wireless, using wired connection. distance appx 60 feet (wired).
Static IP used.
uPnP and port forwarding enabled and working.
factory reset has been done several time, but I will try the fw reload and report.
thanks!
Title: Re: 2330L fails after a few hours
Post by: FurryNutz on November 20, 2015, 06:23:40 AM
 ;)
Title: Re: 2330L fails after a few hours
Post by: leviny on November 23, 2015, 06:53:10 PM
Updated to fw 1.12
one of the cameras had only 1 failure in 3 days, the other had zero.
seems like reloading the fw does help. Probably not the specific fw update, just  reloading ANY good fw.
I'll give it a few more days, then reload the one that failed. hopefully that fixes it in both camera.

will report in a few days...
Title: Re: 2330L fails after a few hours
Post by: FurryNutz on November 24, 2015, 12:31:18 PM
Keep us posted...
Title: Re: 2330L fails after a few hours
Post by: leviny on December 17, 2015, 07:53:11 AM
So this is still going on, but much less frequently. About once every other day. Which is why it's taking so long to troubleshoot.

So far I've tried to disable each feature separately to see if it stops failing. Events, continuous recording, etc. The only thing that (so far) seems to be the cause is SAMBA. When I disabled sending video to my NAS after motion detection, the problem went away. When I re-enabled it with SAMBA (as it was before) it came back. Right now I have it on with FTP, no failure yet (3 days).

This is going on with two 2330L's, while my third one if fine (never fails, and uses SAMBA to send to NAS).

Stand by...
Title: Re: 2330L fails after a few hours
Post by: FurryNutz on December 17, 2015, 07:59:02 AM
Try swapping camera positions to see if the problem follows?
Title: Re: 2330L fails after a few hours
Post by: leviny on December 17, 2015, 01:28:29 PM
First I'm going to test for a few more days to make sure this is the problem. Then, back to FW 1.02, since the camera that works well is still on that version. The other two are on 1.12, both having this problem.

If none of that works, I'll swap cameras.
Title: Re: 2330L fails after a few hours
Post by: FurryNutz on December 17, 2015, 02:02:14 PM
Ok, let us know how it goes.
Title: Re: 2330L fails after a few hours
Post by: RYAT3 on December 17, 2015, 03:24:10 PM
Are the cameras over heating by chance?
Looks directly like it could be getting sun. And with all the extra sd card work, that generates more heat.

Title: Re: 2330L fails after a few hours
Post by: leviny on December 22, 2015, 02:03:04 PM
Heat could certainly be a cause, but I'm not accessing the card at for about two weeks now, with continuous recording off and recording on motion going to a server. Both cameras are shaded nearly all day.

I haven't had any failures in 5 days, so I'm starting to think the cause is simply a "bad" firmware update. This is because I now have one camera on fw 1.12, and the other I reverted to 1.02. Neither is failing. Both are back on SAMBA (rather than ftp). I'll give it a few more days, then try to bring the one back to 1.12... at least this tells me the cause is not hardware.
Title: Re: 2330L fails after a few hours
Post by: RYAT3 on December 22, 2015, 02:52:10 PM
Do you see any "set heater on" in Log files?
Title: Re: 2330L fails after a few hours
Post by: leviny on December 27, 2015, 10:53:49 PM
I see heater hold, and heater off. What does that tell us?

Had zero failures in a week with fw 1.02, but it wasn't sending emails on motion, which is how it was back when 1.02 was current. so I uploaded 1.12, and it now sends the emails but crashes after a few minutes, so far twice in less than an hour.
Title: Re: 2330L fails after a few hours
Post by: leviny on December 28, 2015, 09:23:24 AM
I'm ready to trash this camera. It fails after about 10-15 minutes now, on fw 1.12. (by fail I mean no push notification, false colors, the mobile app shows it as disconnected)

Reverted back to 1.02, so none of that happens, but it doesn't send email on motion... which is a feature I need.

Not planning to change anything or post anymore, unless someone here has news or fixes... the heater thing is interesting, but I need a working camera, not an explanation.

Thanks for all the previous posts, happy new year!
Title: Re: 2330L fails after a few hours
Post by: FurryNutz on December 28, 2015, 09:43:19 AM
You might review this thread and see if there is some help on getting v1.12 working:
http://forums.dlink.com/index.php?topic=63617.0 (http://forums.dlink.com/index.php?topic=63617.0)

Some are having luck on it.

Did you do the camera swap to see if the problem followed?
Title: Re: 2330L fails after a few hours
Post by: leviny on December 30, 2015, 01:49:17 PM
I've not had any problems upgrading to 1.12 several times (going back and forth from 1.02 to 1.12). The upgrade process seems to work fine, with or without a 'factory reset' before and after upgrading. But every time I use 1.12, the camera fails. 1.02 works great except it doesn't send email on event.
Title: Re: 2330L fails after a few hours
Post by: FurryNutz on December 31, 2015, 12:13:34 PM
I'd stick with v1.02 for now. I'm sure D-Link is aware of the issues. I would phone this in and log a case number with them. The more they get calls about this, I presume the sooner a fix would be forth coming.
Title: Re: 2330L fails after a few hours
Post by: leviny on January 01, 2016, 06:48:14 PM
Much appreciated, I will follow your advice. Just to experiment, I brought one of the two problem cameras to 1.12, but turned the IR light off. No problem so far... it's been 2 days. The other is on 1.02 with IR on (auto), no problem (but no email).
Title: Re: 2330L fails after a few hours
Post by: FurryNutz on January 02, 2016, 10:12:39 AM
So I wonder if there is a upgrade issue or a configuration issue on v1.12?
Title: Re: 2330L fails after a few hours
Post by: leviny on January 04, 2016, 04:32:55 PM
Back on 1.12 on both cameras, first with IR off, worked well. Now with IR light on schedule, works well. It went nuts when I put the IR on 'sync', by that I mean that the iOS app lost contact with both cameras, as well as with my 2332L...! which I had to delete and reinstall in the app.

both cameras logs' show booting every 2 hours or so. Which is better than failing. No longer getting the false color, and the app continues to see the cameras. But I'm concerned about rebooting every 2 hours.

2016-01-03 10:38:55 admin FROM XXX.XXX.XXX.3 LOGIN OK
2016-01-03 10:39:09 admin FROM XXX.XXX.XXX.3 LOGIN OK
2016-01-03 11:02:33 SYSTEM BOOTING
2016-01-03 11:02:33 SYSTEM SET IR LIGHT OFF
2016-01-03 11:02:36 SD CARD SIZE 15538848 KB
2016-01-03 11:02:38 SYSTEM SET HEATER HOLD
2016-01-03 11:02:38 SYSTEM SET HEATER OFF
2016-01-03 12:02:06 admin FROM 172.56.41.123 LOGIN OK
2016-01-03 13:56:11 admin FROM XXX.XXX.XXX.11 LOGIN OK
2016-01-03 13:56:12 admin FROM XXX.XXX.XXX.11 LOGIN OK
2016-01-03 14:13:52 admin FROM XXX.XXX.XXX.7 LOGIN OK
2016-01-03 14:13:56 admin FROM XXX.XXX.XXX.7 LOGIN OK
2016-01-03 14:14:36 admin FROM XXX.XXX.XXX.XXX LOGIN OK
2016-01-03 14:15:30 admin FROM XXX.XXX.XXX.XXX SET IR LIGHT SCHEDULE MODE
2016-01-03 14:15:30 admin FROM XXX.XXX.XXX.XXX SET IR LIGHT RANGE 1700 to 0700
2016-01-03 14:25:48 IP CAMERA Received MOTION Trigger
2016-01-03 14:25:48 MOTION STOPPED
2016-01-03 14:26:15 IP CAMERA Received MOTION Trigger
2016-01-03 14:26:16 MOTION STOPPED
2016-01-03 14:27:09 IP CAMERA Received MOTION Trigger
2016-01-03 14:27:09 MOTION STOPPED
2016-01-03 14:27:25 IP CAMERA Received MOTION Trigger
2016-01-03 14:27:25 MOTION STOPPED
2016-01-03 14:28:20 IP CAMERA Received MOTION Trigger
2016-01-03 14:28:21 MOTION STOPPED
2016-01-03 14:28:26 IP CAMERA Received MOTION Trigger
2016-01-03 14:28:26 MOTION STOPPED
2016-01-03 14:29:15 IP CAMERA Received MOTION Trigger
2016-01-03 14:29:15 MOTION STOPPED
2016-01-03 14:29:32 IP CAMERA Received MOTION Trigger
2016-01-03 14:29:33 MOTION STOPPED
2016-01-03 14:29:42 IP CAMERA Received MOTION Trigger
2016-01-03 14:29:42 MOTION STOPPED
2016-01-03 14:29:51 IP CAMERA Received MOTION Trigger
2016-01-03 14:29:51 MOTION STOPPED
2016-01-03 14:30:02 IP CAMERA Received MOTION Trigger
2016-01-03 14:30:02 MOTION STOPPED
2016-01-03 14:30:09 IP CAMERA Received MOTION Trigger
2016-01-03 14:30:09 MOTION STOPPED
2016-01-03 14:41:02 admin FROM XXX.XXX.XXX.11 LOGIN OK
2016-01-03 15:03:35 admin FROM XXX.XXX.XXX.XXX LOGIN OK
2016-01-03 15:03:56 admin FROM XXX.XXX.XXX.XXX SET IR LIGHT RANGE 1701 to 0700
2016-01-03 15:49:11 SYSTEM BOOTING
2016-01-03 15:49:11 SYSTEM SET IR LIGHT OFF
2016-01-03 15:49:14 SD CARD SIZE 15538848 KB
2016-01-03 15:49:16 SYSTEM SET HEATER HOLD
2016-01-03 15:49:24 SYSTEM SET HEATER OFF
2016-01-03 15:55:14 IP CAMERA Received MOTION Trigger
2016-01-03 15:55:14 MOTION STOPPED
2016-01-03 16:03:18 IP CAMERA Received MOTION Trigger
2016-01-03 16:03:19 MOTION STOPPED
2016-01-03 16:04:13 admin FROM XXX.XXX.XXX.11 LOGIN OK
2016-01-03 16:05:01 admin FROM XXX.XXX.XXX.XXX LOGIN OK
2016-01-03 17:06:32 admin FROM XXX.XXX.XXX.XXX SET TIMEZONE (UTC-08:00) Pacific Time (US & Canada)
2016-01-03 17:06:33 SYSTEM SET IR LIGHT ON
2016-01-03 18:04:48 IP CAMERA Received MOTION Trigger
2016-01-03 18:04:48 MOTION STOPPED
2016-01-03 18:39:57 IP CAMERA Received MOTION Trigger
2016-01-03 18:39:58 MOTION STOPPED
2016-01-03 19:32:36 SYSTEM BOOTING
2016-01-03 19:32:36 SYSTEM SET IR LIGHT ON
2016-01-03 19:32:39 SD CARD SIZE 15538848 KB
2016-01-03 19:32:40 IP CAMERA Received MOTION Trigger
2016-01-03 19:32:41 SYSTEM SET HEATER HOLD
2016-01-03 19:32:42 MOTION STOPPED
2016-01-03 19:32:57 SYSTEM SET HEATER OFF
2016-01-03 19:44:10 IP CAMERA Received MOTION Trigger
2016-01-03 19:44:11 MOTION STOPPED
2016-01-03 19:45:09 IP CAMERA Received MOTION Trigger
2016-01-03 19:45:10 MOTION STOPPED
2016-01-03 19:47:23 IP CAMERA Received MOTION Trigger
2016-01-03 19:47:24 MOTION STOPPED
2016-01-03 19:48:22 IP CAMERA Received MOTION Trigger
2016-01-03 19:48:23 MOTION STOPPED
2016-01-03 19:55:51 IP CAMERA Received MOTION Trigger
2016-01-03 19:55:51 MOTION STOPPED
2016-01-03 20:16:19 IP CAMERA Received MOTION Trigger
2016-01-03 20:16:20 MOTION STOPPED
2016-01-03 20:25:34 IP CAMERA Received MOTION Trigger
2016-01-03 20:25:34 MOTION STOPPED
2016-01-03 20:25:42 admin FROM XXX.XXX.XXX.3 LOGIN OK
2016-01-03 20:27:28 admin FROM XXX.XXX.XXX.3 SET MOTION BLOCK TABLE
2016-01-03 20:43:36 IP CAMERA Received MOTION Trigger
2016-01-03 20:43:37 MOTION STOPPED
2016-01-03 20:44:35 IP CAMERA Received MOTION Trigger
2016-01-03 20:44:36 MOTION STOPPED
2016-01-03 21:03:02 IP CAMERA Received MOTION Trigger
2016-01-03 21:03:03 MOTION STOPPED
2016-01-03 21:04:05 IP CAMERA Received MOTION Trigger
2016-01-03 21:04:05 MOTION STOPPED
2016-01-03 22:11:00 IP CAMERA Received MOTION Trigger
2016-01-03 22:12:29 SYSTEM BOOTING
2016-01-03 22:12:29 SYSTEM SET IR LIGHT ON
2016-01-03 22:12:32 SD CARD SIZE 15538848 KB
2016-01-03 22:12:34 SYSTEM SET HEATER HOLD
2016-01-03 22:12:34 IP CAMERA Received MOTION Trigger
2016-01-03 22:12:34 MOTION STOPPED
2016-01-03 22:12:54 SYSTEM SET HEATER OFF
2016-01-04 01:23:14 SYSTEM BOOTING
2016-01-04 01:23:14 SYSTEM SET IR LIGHT ON
2016-01-04 01:23:17 SD CARD SIZE 15538848 KB
2016-01-04 01:23:19 SYSTEM SET HEATER HOLD
2016-01-04 01:23:19 IP CAMERA Received MOTION Trigger
2016-01-04 01:23:20 MOTION STOPPED
2016-01-04 01:23:43 SYSTEM SET HEATER OFF
2016-01-04 02:59:58 IP CAMERA Received MOTION Trigger
2016-01-04 02:59:58 MOTION STOPPED
2016-01-04 05:58:27 SYSTEM BOOTING
2016-01-04 05:58:27 SYSTEM SET IR LIGHT ON
2016-01-04 05:58:30 SD CARD SIZE 15538848 KB
2016-01-04 05:58:32 SYSTEM SET HEATER HOLD
2016-01-04 05:58:32 IP CAMERA Received MOTION Trigger
2016-01-04 05:58:32 MOTION STOPPED
2016-01-04 05:58:52 SYSTEM SET HEATER OFF
2016-01-04 06:41:36 admin FROM XXX.XXX.XXX.11 LOGIN OK
2016-01-04 06:41:37 admin FROM XXX.XXX.XXX.11 LOGIN OK
2016-01-04 07:00:01 SYSTEM SET IR LIGHT OFF
2016-01-04 07:02:33 admin FROM XXX.XXX.XXX.XXX LOGIN OK
2016-01-04 07:03:36 admin FROM XXX.XXX.XXX.XXX SET IR LIGHT RANGE 1701 to 0640
2016-01-04 07:24:44 IP CAMERA Received MOTION Trigger
2016-01-04 14:44:56 SYSTEM BOOTING
2016-01-04 14:44:56 SYSTEM SET IR LIGHT OFF
2016-01-04 14:44:59 SD CARD SIZE 15538848 KB
2016-01-04 14:45:01 SYSTEM SET HEATER HOLD
2016-01-04 15:30:01 IP CAMERA Received MOTION Trigger
2016-01-04 15:30:01 MOTION STOPPED
2016-01-04 15:30:21 IP CAMERA Received MOTION Trigger
2016-01-04 15:30:21 MOTION STOPPED
2016-01-04 15:30:27 IP CAMERA Received MOTION Trigger
2016-01-04 15:30:28 MOTION STOPPED
2016-01-04 15:30:44 IP CAMERA Received MOTION Trigger
2016-01-04 15:30:44 MOTION STOPPED
2016-01-04 15:31:50 IP CAMERA Received MOTION Trigger
2016-01-04 15:31:50 MOTION STOPPED
2016-01-04 15:31:56 IP CAMERA Received MOTION Trigger
2016-01-04 15:31:56 MOTION STOPPED
2016-01-04 15:32:05 IP CAMERA Received MOTION Trigger
2016-01-04 15:32:05 MOTION STOPPED
2016-01-04 15:32:14 IP CAMERA Received MOTION Trigger
2016-01-04 15:32:14 MOTION STOPPED
2016-01-04 15:32:24 IP CAMERA Received MOTION Trigger
2016-01-04 16:16:39 SYSTEM BOOTING
2016-01-04 16:16:39 SYSTEM SET IR LIGHT OFF
2016-01-04 16:16:42 SD CARD SIZE 15538848 KB
2016-01-04 16:16:44 SYSTEM SET HEATER HOLD
2016-01-04 16:16:44 SYSTEM SET HEATER OFF
2016-01-04 16:25:04 admin FROM XXX.XXX.XXX.3 LOGIN OK
2016-01-04 16:29:40 admin FROM XXX.XXX.XXX.3 LOGIN OK
Title: Re: 2330L fails after a few hours
Post by: FurryNutz on January 06, 2016, 12:16:32 PM
I recommend you phone contact D-Link support and ask them about the reboots. Not sure if thats normal or not.
Title: Re: 2330L fails after a few hours
Post by: leviny on April 27, 2016, 08:52:25 AM
So after months observing this, my conclusion is that the problem is with automatic switching from day/night of the ICR. With ICR in auto, I get all the symptoms described in the original post, most importantly the camera is removed from the list of available cameras on myDlink/Dlink app and doesn't generate push notifications. With ICR on "schedule" mode, this doesn't happen. The camera (two cameras for me) still reboot about every other hour for no reason, making it unavailable on myDlink/app for about 30 seconds, and interrupting the continuous recording. This is a problem, but not as bad as the other problem described above.

Both cameras that exhibit this are currently on 1.12 and this did not happen in either camera in earlier FW, but earlier FW's had a bug with not sending emails and I prefer to receive emails than to resolve this by using an earlier FW. (I have a third camera on 1.02, it doesn't have this problem, it doesn't reboot, but it doesn't send emails.)

I don't plan on contacting Dlink because I can live with this as it is, but I would certainly appreciate if anyone affiliated with Dlink on this forum pass the info along so this can be fixed.
Title: Re: 2330L fails after a few hours
Post by: FurryNutz on April 27, 2016, 09:23:56 AM
Thanks for the feed back and troubleshooting info. I'll pass this along to D-Link for review.