Print

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

[Mackerel]

I have found an odd behaviour in DViewCam V3.0: All of the cameras have a short period of Signal Lost, occurring like clockwork, coming about roughly every 2 hours and 10 minutes (+/- 3 minutes), and taking between 5 and 20 seconds. And it happens staggered, about 5 minutes apart for all cameras...

My guess is some internal memory management routine, trying to do garbage collection per camera, but I saw it happen, but never thought about looking in the System Log to find out how often it happened. It is mighty regular, and also happens on all cameras. In one case it was happening at the wrong moment, as something that needed to be recorded only got recorded with a huge gap at the moment of highest need.

Do other people have this same issue, and can anybody explain what exactly is happening here? I love puzzles, so this would be one I would like to solve. I am going to switch around cameras (on IP addresses) to see if that makes any difference, but I expect no change as all of them have it in roughly the same interval.

[ECF]

Are you still having this issue after try version 3.01? Also check to see if your PC is running a program or a scan every 2 hours...maybe anti-virus software.

[Mackerel]

Could be related to the 920's used themselves (as it happens staggered per camera), but I will install/run 3.01 on (32-bit W7) production-box to verify whether cyclic process-behaviour remains. I only have 920's, no other types... There are scheduled processes, but I have checked on tasks (Norton 2010, W7, Tune-Up) and none of them have something on that time-scale.

So I will give you feedback after a day of running V3.01...

UPDATE 20100430: Still happening in V3.01 roughly every 2h17m (+/- 2 min) for about 10-20 seconds (varying). It is related to the camera, as when (fairly quickly) powering off/on camera (while keeping DViewCam running) the signal-loss cycle (for that camera only) was moved forward. Cycle-length still same 2h17m...
Saw same behaviour occur in DviewCam V2.0x. I assume V3 has had a lot of recoding in the engine (different storage method, etc), so this could be purely hardware-related.

[Mackerel]

Added info: When running 3.01 on 64-bit I get an additional 3-4 second dip in network troughput every 6 minutes. There is no info in the System-log on this, so I assume it is in the DViewCam itself. The dip goes down 90% of original speed. I have a nice graph image from the Windows Task Manager network-graph to show cyclic behaviour, if needed.

The 2h15min interval signal loss is independent of the machine/win-os-ver/32-64 bit, so that must be purely camera-related (hardware).

EDIT: The additional dip is caused by a router (EBR-2310), which somehow throttles everything for a few secs every 6 minutes. So that part is NOT related to either the cameras or the DViewCam software. Probably need to use a different router in the path (and it goes over switches, AP's and routers from cameras to recording computer)...

[ECF]

I am seeing a signal loss at about every 10 hours and 20 minutes if I go back and review the log from this weekend however it does not seem to be very consistent.