Print

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

[BAMoh]

Are the cams on WIFI or LAN cable? I suggest you put them on LAN cable. The cams go offline because you have terrible bandwith triggering loss of connection.

[remoteCamsFarAway]

BAMoh....Thanks for your reply.

All the cams are on wifi and yes the ADSL modem to the internet is limited to 1Mb/s.  I agree that a wired connection might be more "predictable".  However, within the home the router is a high-end recent-vintage router and local network bandwidth within that network is high.  The cams should not lose their internal wifi connection to the router due to a low bandwidth internet connection that they normally don't connect to unless I remotely access them.  The problem is not that I can't dump video from them over the internet.  It is that they lose their local wifi connection to the router and don't recover.  Unplugging them and plugging them back in is the only way for them to recover once they get into this state.  Also note that the area where these are located is in a low density residential neighborhood with very little interference from other networks.

Also note that while I have had problems in the past with the two 2630L cams on the same network, they now seem to be stable after I've assigned static IP addresses and put the router/modem/AP on a UPS system.  I also made a recent firmware upgrade to the 2630L cams but I don't know if that made any difference or not.

Again, my beef isn't that they sometimes lose their link.  It is that, assuming that there is not a flakey hardware design flaw that can only be reset by a power cycle, the firmware should recognize that it has lost its wifi link and then attempt to relink to the router.  A hardware design flaw is yet a different issue.

[remoteCamsFarAway]

Firmware version 1.12.

Have dumped logs from 2330 cams that repeatedly fall offline.  There may be a clue for Dlink engineers (one engineer to another) IF YOU ARE LISTENING:

The log shows many instances of the following sequences where the cameras go offline:

First, there are repeated examples where the firmware doesn't get past SYSTEM SET HEATER HOLD. The gap of 6 days in this and many other identical log entries is from the time the camera is lost until I have someone enter the premises to power cycle the camera.  Why does it get stuck at that step?

2016-03-21 23:51:21 admin FROM 127.0.0.1 LOGIN OK
2016-03-22 02:43:37 SYSTEM BOOTING
2016-03-22 02:43:42 SYSTEM SET HEATER HOLD
2016-03-28 09:26:53 SYSTEM BOOTING

Secondly, there are multiple examples of NETWORK LOSS some of which never proceed beyond that step until I get someone in there to perform a power cycle.  Since I don't have corresponding entries at those times in the other cams I assume that this is referring to the local network and not the WAN connection to the internet.  The 3 week gap is the time it took me to get someone in there to power cycle the camera.  Note that other cameras in this network remained online.  Either way, however, a network loss should be followed by a reconnect as I will show following this example of a failure:

2016-03-28 09:26:53 SYSTEM BOOTING
2016-03-28 09:26:58 SYSTEM SET HEATER HOLD
2016-03-28 09:26:58 SYSTEM SET IR LIGHT OFF
2016-03-28 09:26:58 NETWORK INTERFACE CHANGE TO WLAN
2016-03-28 09:27:01 NETWORK LOSS
2016-04-21 14:39:09 SYSTEM BOOTING

The following unedited sequence shows a series of NETWORK LOSSes which DO recover as they should.  Is there a hole in the firmware or a hardware failure mode where the firmware sometimes either gets stuck or gives up trying to recover?  Can the firmware be enhanced to try a little harder to recover?
2016-08-18 18:12:05 SYSTEM BOOTING
2016-08-18 18:12:10 SYSTEM SET HEATER HOLD
2016-08-18 18:12:10 SYSTEM SET IR LIGHT OFF
2016-08-18 18:12:10 NETWORK INTERFACE CHANGE TO WLAN
2016-08-18 18:12:12 NETWORK LOSS
2016-08-18 18:12:12 SYSTEM SET HEATER OFF
2016-08-18 18:12:13 NETWORK RECONNECT
2016-08-18 22:00:58 SYSTEM BOOTING
2016-08-18 22:01:03 SYSTEM SET IR LIGHT OFF
2016-08-18 22:01:03 NETWORK INTERFACE CHANGE TO WLAN
2016-08-18 22:01:03 SYSTEM SET HEATER HOLD
2016-08-18 22:01:05 NETWORK LOSS
2016-08-18 22:01:05 SYSTEM SET HEATER OFF
2016-08-18 22:01:06 NETWORK RECONNECT
2016-08-19 14:35:12 SYSTEM BOOTING
2016-08-19 14:35:17 SYSTEM SET HEATER HOLD
2016-08-19 14:35:17 SYSTEM SET IR LIGHT OFF
2016-08-19 14:35:17 NETWORK INTERFACE CHANGE TO WLAN
2016-08-19 14:35:19 NETWORK LOSS
2016-08-19 14:35:19 SYSTEM SET HEATER OFF
2016-08-19 14:35:20 NETWORK RECONNECT

Dlink engineers......do these log entries tell you anything?  Is there any more info I can gather that would be helpful?  Thanks in advance for your help.

[RYAT3]

CURRENT LOG  v1.01



1. 2016-08-21 14:48:54 admin LOGIN OK FROM 192.168.1.3
2. 2016-08-16 19:28:13 admin LOGIN OK FROM 192.168.1.4
3. 2016-08-15 19:39:09 admin LOGIN OK FROM 192.168.1.4
4. 2016-08-14 22:48:16 admin FROM 192.168.1.4 SET DENOISE 22
5. 2016-08-14 22:48:09 admin FROM 192.168.1.4 SET DENOISE 19
6. 2016-08-14 22:48:05 admin FROM 192.168.1.4 SET DENOISE 10
7. 2016-08-14 22:48:01 admin FROM 192.168.1.4 SET DENOISE 25
8. 2016-08-14 22:47:51 admin FROM 192.168.1.4 SET MIN SHUTTER 1/10000
9. 2016-08-14 22:47:51 admin FROM 192.168.1.4 SET MAX SHUTTER 1/8
10. 2016-08-14 22:47:50 admin FROM 192.168.1.4 SET MIN SHUTTER 1/10000
11. 2016-08-14 22:47:50 admin FROM 192.168.1.4 SET MAX SHUTTER 1/30
12. 2016-08-14 22:47:45 admin FROM 192.168.1.4 SET EXPOSURE TIME Customize1
13. 2016-08-14 22:47:40 admin FROM 192.168.1.4 SET EXPOSURE TIME Low_noise
14. 2016-08-14 22:47:05 admin LOGIN OK FROM 192.168.1.4
15. 2016-08-12 23:57:39 admin LOGIN OK FROM 192.168.1.232
16. 2016-08-12 16:37:23 admin LOGIN OK FROM 192.168.1.232
17. 2016-08-11 16:22:18 DCS-2330L ACQUIRE DHCP IP 192.168.1.46
18. 2016-08-11 16:22:09 NETWORK RECONNECT
[I POWER CYCLED ROUTER]
19. 2016-08-11 14:33:50 SYSTEM SET HEARTER state OFF
20. 2016-08-11 14:33:49 SYSTEM SET HEARTER state ON
21. 2016-08-11 14:33:48 NETWORK LOSS
22. 2016-08-11 14:33:48 NETWORK INTERFACE CHANGE TO WLAN
23. 2016-08-11 14:33:47 SYSTEM SET IR LIGHT OFF
24. 2016-08-11 14:33:47 SYSTEM BOOTING
[POWER OUTAGE 8/11]
25. 2016-08-09 20:02:54 admin LOGIN OK FROM 192.168.1.50
26. 2016-08-07 19:13:15 admin LOGIN OK FROM 192.168.1.3
27. 2016-08-06 21:46:58 admin LOGIN OK FROM 192.168.1.3
28. 2016-08-06 15:41:27 admin LOGIN OK FROM 192.168.1.50
29. 2016-08-06 00:40:41 admin FROM 192.168.1.3 SET EXPOSURE TIME Auto
30. 2016-08-06 00:40:33 admin FROM 192.168.1.3 SET EXPOSURE TIME Low_noise
31. 2016-08-06 00:40:21 admin FROM 192.168.1.3 SET MAX AGC GAIN 24
32. 2016-08-06 00:40:03 admin LOGIN OK FROM 192.168.1.3
33. 2016-08-05 22:54:44 SYSTEM SET IR LIGHT OFF
34. 2016-08-05 22:54:44 admin FROM 192.168.1.3 SET IR LIGHT OFF MODE
35. 2016-08-05 22:54:29 SYSTEM SET IR LIGHT ON
36. 2016-08-05 22:54:29 admin FROM 192.168.1.3 SET IR LIGHT ON MODE
37. 2016-08-05 22:53:36 SYSTEM SET IR LIGHT OFF
38. 2016-08-05 22:53:36 admin FROM 192.168.1.3 SET IR LIGHT OFF MODE
39. 2016-08-05 22:53:21 SYSTEM SET IR LIGHT ON
40. 2016-08-05 22:53:21 admin FROM 192.168.1.3 SET IR LIGHT ON MODE


I don't remember what this was about on 7/15.


70. 2016-07-16 16:44:06 admin LOGIN OK FROM 192.168.1.3
71. 2016-07-15 17:01:48 DCS-2330L ACQUIRE DHCP IP 192.168.1.46
72. 2016-07-15 17:01:47 SYSTEM SET HEARTER state OFF
73. 2016-07-15 17:01:47 SYSTEM SET HEARTER state ON
74. 2016-07-15 17:01:44 NETWORK RECONNECT
75. 2016-07-15 17:01:43 NETWORK LOSS
76. 2016-07-15 17:01:42 NETWORK INTERFACE CHANGE TO WLAN
77. 2016-07-15 17:01:42 SYSTEM SET IR LIGHT OFF
78. 2016-07-15 17:01:42 SYSTEM BOOTING
79. 2016-07-15 07:41:54 SYSTEM SET HEARTER state ON
80. 2016-07-15 07:41:52 DCS-2330L ACQUIRE DHCP IP 192.168.1.46
81. 2016-07-15 07:41:51 NETWORK RECONNECT
82. 2016-07-15 07:41:50 NETWORK LOSS
83. 2016-07-15 07:41:49 NETWORK INTERFACE CHANGE TO WLAN
84. 2016-07-15 07:41:49 SYSTEM SET IR LIGHT OFF
85. 2016-07-15 07:41:49 SYSTEM BOOTING
86. 2016-07-13 00:49:54 admin LOGIN OK FROM 192.168.1.3


I have a 2330L I need to setup. It does have a newer F/W.  I installed a 2330L with upgraded F/W last fall, and they haven't complained about disconnects.

[remoteCamsFarAway]

This is frikken driving me nuts.  Had someone reset my 2330L cams on Aug 16 (about 7 days ago) and I've lost two of the three 2330L cams again.

[RYAT3]

This is frikken driving me nuts.  Had someone reset my 2330L cams on Aug 16 (about 7 days ago) and I've lost two of the three 2330L cams again.

So the daily reboot option isn't panning out?

[BAMoh]

I don't have any 2330's but I do have a 2630. Following installation it have never disconnected and it is far away from the router. I mean really far and no straight path.

Do you have a dual band router? Try putting it on 2.4Ghz instead of 5Ghz for better range.

Try to reserve an IP address for it. Not static.

Try a less crowded channel. Could be interference from your neighbors' router signals or even other non WIFI devices in your home.

Move the cam adjacent to the router temporarily to see if you get the same issue. In fact do this first. If it is sitting next to the router and dropping out then IMO its defective or maybe even defective in design. If a firmware upgrade doesn't fix it I would contact the BBB and your state consumer AG and hammer DLINK. But that would be the "nuclear" option. Try the other steps first.

[FurryNutz]

Really think you should have gone with wired camera system instead of wireless.

My 2 cents.

This is frikken driving me nuts.  Had someone reset my 2330L cams on Aug 16 (about 7 days ago) and I've lost two of the three 2330L cams again.

[remoteCamsFarAway]

This is frikken driving me nuts.  Had someone reset my 2330L cams on Aug 16 (about 7 days ago) and I've lost two of the three 2330L cams again.

So the daily reboot option isn't panning out?

That's correct.  I no longer recommend the daily reboot.  Though my manual experiments showed that it recovered, I have some logs (of course after I left that location) that show that the camera went offline at the time of a scheduled reboot and never came back before a manual power cycle.

[remoteCamsFarAway]

I don't have any 2330's but I do have a 2630. Following installation it have never disconnected and it is far away from the router. I mean really far and no straight path.

Do you have a dual band router? Try putting it on 2.4Ghz instead of 5Ghz for better range.

Try to reserve an IP address for it. Not static.

Try a less crowded channel. Could be interference from your neighbors' router signals or even other non WIFI devices in your home.

Move the cam adjacent to the router temporarily to see if you get the same issue. In fact do this first. If it is sitting next to the router and dropping out then IMO its defective or maybe even defective in design. If a firmware upgrade doesn't fix it I would contact the BBB and your state consumer AG and hammer DLINK. But that would be the "nuclear" option. Try the other steps first.

Two of my five cams are 2630L and they have been really stable.  They remain online continuously while the 2330L cams seem to remain online for only about 10 days give or take a few.  They individually drop out, not as a group.  Distance doesn't seem to be a problem.  Two of the three cams are about 10 feet away from the access point.  The third is about 15 feet away.

All cams are already connected to 2.4GHz.

Not sure what you mean assigning IP addresses that are not static.  I thought an assigned IP address was static.  I've manually assigned all IP addresses.  They are not assigned by DHCP.

While there are other signals getting picked up, they are far away and quite weak as this location is in a sparsely populated area.

It turns out that one of my 2630L cams is the one that is the farthest away.  The two 2630L cams seem to be quite reliable (1.03 firmware) while the 2330L cams (1.12 firmware) are totally unreliable.  As I've said earlier, I do believe that there is a design flaw.  I don't know if it is hardware or firmware.  If a hardware defect, the question is if they can improve their robustness with a firmware workaround such as a deadman timer in the firmware (assuming that the firmware is still running).

[remoteCamsFarAway]

Though I haven't posted lately, I lost the third 2330L cam a couple of days after my August 16 posting.  Was hoping that a power outage would reset them but I don't think we've had one since then.  Today requested caretaker to go in and reset the 2330L cams.

[remoteCamsFarAway]

Really think you should have gone with wired camera system instead of wireless.

My 2 cents.

This is frikken driving me nuts.  Had someone reset my 2330L cams on Aug 16 (about 7 days ago) and I've lost two of the three 2330L cams again.

Something to be said there short of needing to run wires.  However, the 2630L cams don't seem to have the same disease as the 2330L cams so it seems to be dependent on which cams are in the system. 

That said, I am installing two new POE cams in November, 4602EV and 6517.  Hopefully I don't discover a new disease of the POE flavor.

[BAMoh]

I don't have any 2330's but I do have a 2630. Following installation it have never disconnected and it is far away from the router. I mean really far and no straight path.

Do you have a dual band router? Try putting it on 2.4Ghz instead of 5Ghz for better range.

Try to reserve an IP address for it. Not static.

Try a less crowded channel. Could be interference from your neighbors' router signals or even other non WIFI devices in your home.

Move the cam adjacent to the router temporarily to see if you get the same issue. In fact do this first. If it is sitting next to the router and dropping out then IMO its defective or maybe even defective in design. If a firmware upgrade doesn't fix it I would contact the BBB and your state consumer AG and hammer DLINK. But that would be the "nuclear" option. Try the other steps first.

Two of my five cams are 2630L and they have been really stable.  They remain online continuously while the 2330L cams seem to remain online for only about 10 days give or take a few.  They individually drop out, not as a group.  Distance doesn't seem to be a problem.  Two of the three cams are about 10 feet away from the access point.  The third is about 15 feet away.

All cams are already connected to 2.4GHz.

Not sure what you mean assigning IP addresses that are not static.  I thought an assigned IP address was static.  I've manually assigned all IP addresses.  They are not assigned by DHCP.

While there are other signals getting picked up, they are far away and quite weak as this location is in a sparsely populated area.

It turns out that one of my 2630L cams is the one that is the farthest away.  The two 2630L cams seem to be quite reliable (1.03 firmware) while the 2330L cams (1.12 firmware) are totally unreliable.  As I've said earlier, I do believe that there is a design flaw.  I don't know if it is hardware or firmware.  If a hardware defect, the question is if they can improve their robustness with a firmware workaround such as a deadman timer in the firmware (assuming that the firmware is still running).

On some routers you can reserve an IP address. This is different from a static IP address. But if you set a static thats fine. Same purpose. I have reserved an IP address for cams that were flaky and lost connection at first setup. After reserving, they are rock steady and never lose connection. I really have no answer for your 2330 issues except you probably wnat to run a long LAN cable or force DLINK to refund you on the camera.

[webo]

Solved in my case, i have a dcs-933, after tip here about someone replaced the power adapter i tryed that, and it solved my problem.
i have not tested voltage on the old one yet, but i will.
i use the camera outside, and it has been operated in -25deg`c. still good 

[FurryNutz]

Glad you solved your problem. Power adapters have been know to go out. Especially encountering electrical storms and brown outs.

Enjoy.

Solved in my case, i have a dcs-933, after tip here about someone replaced the power adapter i tryed that, and it solved my problem.
i have not tested voltage on the old one yet, but i will.
i use the camera outside, and it has been operated in -25deg`c. still good