Print

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

[BeachDuc]

I have two cameras, the 7010L and the 2132L.  The latter seems to behave well and works consistently.  The 7010L just won't stay connected.  I have both cameras set up, almost identically, to continuously record to a network drive.  The 2132 keeps on recording.  The 7010 will record for a few hours to a few days and then stop, until I power it off and back on.  Obviously this defeats the purpose of a security camera as it can't be relied upon if I am away.  I find that access the 7010 from a web browser or the D-Link app is also temperamental.  Accessing the settings page of the server will often fail but after trying to do so the camera will seem to wake up and start working again.  The log file says SYSTEM BOOTING at around that time (see below), with no other entries since the last time it was actually working.  It is was though the camera is going to sleep.  Any help on getting it working would be appreciated. 

My setup:
The 2132 is wireless.  The 7010 is wired to a PoE hub (from which it is powered), this hub is then wired to my main router (an Apple Time Capsule).  Both cameras record (or are supposed to!) to a RAID HDD attached by USB to the Time Capsule.  My internet modem is wired to the same Time Capsule which serves a number of other devices (some wired, some WiFi), none of which seem to have any issues.  I have SD cards in both cameras but don't use them.
Everything has the most up to date firmware and software.  I did try going back to firmware 1.01 on the 7010 as it seemed to start playing up after upgrading to 1.02, but doing so hasn't helped so I am back to 1.02.

Log file:
2013-10-25 12:01:53 SYSTEM SET IR LIGHT ON
2013-10-25 12:01:57 MOTION STOPPED
2013-10-25 12:52:25 IP CAMERA Received PERIODIC Trigger
2013-10-25 13:52:31 IP CAMERA Received PERIODIC Trigger
2013-10-25 14:52:32 IP CAMERA Received PERIODIC Trigger
2013-10-25 15:01:02 IP CAMERA Received MOTION Trigger
2013-10-25 15:01:04 MOTION STOPPED
2013-10-26 18:19:01 SYSTEM BOOTING
2013-10-26 18:19:01 IP CAMERA Received PERIODIC Trigger
2013-10-26 18:19:02 SD CARD SIZE 31154688 KB
2013-10-26 18:19:02 SYSTEM SET IR LIGHT OFF
2013-10-26 18:19:03 IP CAMERA ACQUIRE DHCP IP 10.0.1.13
2013-10-26 18:19:07 SYSTEM SET IR LIGHT ON
2013-10-26 18:19:08 SYSTEM SET IR LIGHT OFF
2013-10-26 18:19:08 SYSTEM SET IR LIGHT ON
2013-10-26 18:25:24 admin LOGIN OK FROM 10.0.1.2

[RecordEverything]

I've got a similar setup (7010L recording to Windows Share) and I noticed my camera behaved exactly the same the other day. I've only had it for a few days so I don't know if it's happened before. Unfortunately because it seems to fix itself if you try the webpage it's difficult to know if it's done it and not been noticed.

v1.02 software.

[BeachDuc]

I have no idea what is going on.  It will sometimes record for a few hours and sometimes not at all.  The Log files stop sending as well.  I haven't had any recording since the 30th September now.  All the status lights are working though.

[RYAT3]

I have no idea what is going on.  It will sometimes record for a few hours and sometimes not at all.  The Log files stop sending as well.  I haven't had any recording since the 30th September now.  All the status lights are working though.

How many things are you having the camera do?

Motion ftp video? motion ftp images? sd recording? nas? 

Can you back it down to 1 thing that is important, and test only that?  I would guess you are overloading the camera.

Can you set a priority on this F/W like some others for events?

[BeachDuc]

I'm only asking for a 'continuous' recording to HDD and an hourly log.  The 2132 manages it fine.  Since posting I have done a factory reset and things seem to be working again - with exactly the same settings I was using before.  Who knows what the problem is!

[RecordEverything]

I had 2 7010L's doing exactly the same thing with exactly the same config. Continuous record and motion detection. One rebooted or stopped recording consistently, one was fine. Both going to the same server, powered from the same POE switch, etc.

Factory reset didn't fix it, but removing the motion detect did. I think its just getting confused when it has to do more than one thing.