Print

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

[Richpat]

hi,
I am seeing these reboot log entry in the camera log file indicating the camera reboot itself after a digital input trigger (i.e. a magnetic door sensor) or a patrol run.

2016-10-07 16:25:55 DIGITAL-IN 1 RISING
2016-10-07 16:26:00 DIGITAL-IN 1 CLEAR
2016-10-07 16:27:17 DIGITAL-IN 1 RISING
2016-10-07 16:27:21 DIGITAL-IN 1 CLEAR
2016-10-07 16:27:52 DIGITAL-IN 1 RISING
2016-10-07 16:27:58 DIGITAL-IN 1 CLEAR
2016-10-07 16:32:48 SYSTEM BOOTING
2016-10-07 16:32:53 SYSTEM SET IR LIGHT OFF
2016-10-07 16:32:57 SD CARD SIZE 30356976 KB
2016-10-07 16:33:03 admin FROM 192.168.3.20 LOGIN OK
2016-10-07 16:56:57 DIGITAL-IN 1 RISING
2016-10-07 16:57:02 DIGITAL-IN 1 CLEAR


This does not happen at every trigger nor patrol run. It is sporadic and quite annoying.

It is because I wanted to record the video when the door is opened, but the camera reboot itself and fails to record the action. It is the same for the patrol run.

The camera is connected via a ethernet cable. I should be not seeing loss connection log entry. But they appeared a few time since last summer. I am not able to duplicated the problem.

2017-01-15 07:13:21 SYSTEM SET IR LIGHT OFF
2017-01-15 12:35:39 NETWORK INTERFACE CHANGE TO WLAN
2017-01-15 12:35:40 NETWORK LOSS
2017-01-15 12:35:42 NETWORK INTERFACE CHANGE TO ETHERNET
2017-01-15 12:35:44 NETWORK RECONNECT
2017-01-15 12:40:14 NETWORK INTERFACE CHANGE TO WLAN
2017-01-15 12:40:14 NETWORK LOSS
2017-01-15 12:40:17 NETWORK RECONNECT
2017-01-15 12:40:17 NETWORK INTERFACE CHANGE TO ETHERNET
2017-01-15 12:42:06 NETWORK INTERFACE CHANGE TO WLAN
2017-01-15 12:42:06 NETWORK LOSS
2017-01-15 12:42:10 NETWORK RECONNECT
2017-01-15 12:42:10 NETWORK INTERFACE CHANGE TO ETHERNET
2017-01-15 16:50:51 SYSTEM SET IR LIGHT ON
2017-01-16 07:24:20 SYSTEM SET IR LIGHT OFF

In additional, I have more than one 5222LB1 camera, I just noticed that some of the camera have the maximum FPS be 25 and others be 30.

They are all installed with latest FW.

What is the reason for that?

Best Regards

[FurryNutz]

Link>Welcome!

• What Hardware version is your DCS? Look at the sticker behind or under the camera.
• Link>What Firmware version is currently loaded? Found on the DCSs web page under status.
• What region are you located?

What Mfr and model is the main host router?
What Mfr and model network LAN switch are you using if any?

Cameras using Static IP address on the cameras or reserved IP address on the router?
How many cameras do you have all connected?
I recommend setting a static IP address ON the cameras outside of the main host routers default DHCP IP address pool as a troubleshooting step: 192.168.#.52 and .53 and so on.  DHCP

Test cameras with uPnP and uPnP Port Forwarding both enabled on ALL cameras: DCS Cloud (L) Series Camera Configuration and Mydlink.com

[Richpat]

hi

HW version is B
FW version is 2.14.04
Region is NA

Main Router Dlink DIR-890L
LAN Switch Dlink DGS1100-08 Easysmart

Camera on DHCP with reserved IP address on the router
18 cameras, not all Dlink

They were on static IP, but now they are on DHCP IP with IP address reserved.
I put all the cameras back on DHCP, it was because the Dlink tech support told me, the DIR890 router only display connected devices on DHCP.

All the Dlink's cameras have the uPnP enable and uPnP port forwarding disable. I had some problem with the camera before and the Dlink tech support told me to disable the uPnP port forwarding.

Should I put a schedule reboot on camera?

Does the camera reboot works in the same way as a power cycle of the camera?

[FurryNutz]

What FW version is loaded on the 890L?

Static IPs are preferred. Specially if you have many cameras.

Can you test one cameras with out it being connected to the switch?
Might try enabling uPnP Port Forwarding and try a static IP address out side the routers IP address pool on this one camera as well to test.

A reboot just reboots the cameras FW is all. Doesn't not power it OFF I believe.

[Richpat]

DIR890 HW A1 FW1.10 The latest firmware is installed.

According to Dlink Support, the DIR890 only display connected clients on DHCP only..... That is why I put all on DHCP.

Even though I put all the connected devices on DHCP, the DIR890 is still unable to display all the connected clients on the network on HOME page.

This sporadic reboot is very difficult to duplicate it. There is no sure way to reproduce it.
I have to repeatedly trigger the digital input or patrol the camera, it may happen once.

I put a schedule on the camera to do a patrol every 30 minutes for monitoring.

I have been told to lower the FPS to see if it makes any difference. It means from 30/25 to 7. It seems to work or it could be the sporadic nature of the fault.

I did a power cycle on all the 5029 cameras and monitor it. For the first 24 hrs, at FPS 7. No reboot.
The 2nd 24hrs at FPS30, so far no reboot. I will keep monitor it for a few days.

I am wondering if reboot from camera web portal is difference from a power cycle.

Also, I wonder if it is a good practise to reboot the camera on a schedule basic rather than have it run on 24/7 until it fails.

anyone else encounter this problem?

You may not notice it unless you check on the camera log file.

Finally, what should be the max fps for 5222L. I have cameras with max 25 others are 30. It is kind of strange.

[RYAT3]

Finally, what should be the max fps for 5222L. I have cameras with max 25 others are 30. It is kind of strange.

What are the exact video specifications?

[FurryNutz]

D-Link is working on a bug with DHCP and connected clients. I see the same thing on mine. I know with my 880L and other routers Static IP devices should be seen. I'll check to see what will be the expected behavior. I see Static devices on my 880L all the time and 890L, sometimes.
They are aware of the 890L issue.
You can still use Static IPs for your cameras that's outside of the DCHP router pool.

DIR890 HW A1 FW1.10 The latest firmware is installed.

According to Dlink Support, the DIR890 only display connected clients on DHCP only..... That is why I put all on DHCP.

Even though I put all the connected devices on DHCP, the DIR890 is still unable to display all the connected clients on the network on HOME page.

This sporadic reboot is very difficult to duplicate it. There is no sure way to reproduce it.
I have to repeatedly trigger the digital input or patrol the camera, it may happen once.

I put a schedule on the camera to do a patrol every 30 minutes for monitoring.

I have been told to lower the FPS to see if it makes any difference. It means from 30/25 to 7. It seems to work or it could be the sporadic nature of the fault.

I did a power cycle on all the 5029 cameras and monitor it. For the first 24 hrs, at FPS 7. No reboot.
The 2nd 24hrs at FPS30, so far no reboot. I will keep monitor it for a few days.

I am wondering if reboot from camera web portal is difference from a power cycle.

Also, I wonder if it is a good practise to reboot the camera on a schedule basic rather than have it run on 24/7 until it fails.

anyone else encounter this problem?

You may not notice it unless you check on the camera log file.

Finally, what should be the max fps for 5222L. I have cameras with max 25 others are 30. It is kind of strange.

[Richpat]

Well, I reported many problem on the 890L to Dlink since I got it a year ago and tested for their FW before.
I received a testing debug FW from them a few days ago, I will test it on next monday as I do not want to update the FW remotely.

But, this sporadic lost connection even on ethernet connection is very strange. Not sure if it is the camera or the 890L router.

I wonder if others have seen it before.

[FurryNutz]

Let us now how it goes with the debug FW on the 890L. There maybe other wifi issues with the 890L.