SD49225T-HN frequent restarts

[Q™]

I have same as @QTM

I just flashed my SD49225T-HN to the following (PAL version) firmware which is located here...

SD49225T-HN | Dahua Technology

Here what is now being reported as installed on my camera...

• Device Type SD49225T-HN
• System Version 2.623.0000000.2.R.R4.2510.9A.NR, Build Date: 2018-09-13
• WEB Version 3.2.1.631181
• ONVIF Version 16.12(V2.4.3.579540)
• PTZ Version 3.02.93.RHNZ_170518_22722

The flashing process is simple and needs to be done two (2) steps (3 if you count the factory default reset):

1. Step 1: Flash the PAL (or NTSC) firmware
2. Step 2: After the flash process reboots your camera log in and flash the PTZ firmware
3. I then reset my camera to the factory defaults and then reconfigured my camera

Flashing firmware gives me great anxiety ever since I bricked an Ambra 486 back in 1998 . I haven't bricked anything since then, but ever since flashing FW gives me the willies.

 

[JayS_IPCams]

Thanks Q™ let me know if that fixes your rebooting issue! I

 

[Q™]

Thanks Q™ let me know if that fixes your rebooting issue

Are you certain your camera is actually rebooting? A SD49225T-HN reboot seems to take several minutes, yet my SD49225T-HN seems to become unresponsive for much longer. Blue Iris reports these "unresponsive events" as "No Signal," as shown in the image below. And, yes, after my firmware update these events are still haunting my SD49225T-HN.

 

[Tinman]

Are you certain your camera is actually rebooting? A SD49225T-HN reboot seems to take several minutes, yet my SD49225T-HN seems to become unresponsive for much longer. Blue Iris reports these "unresponsive events" as "No Signal," as shown in the image below. And, yes, after my firmware update these events are still haunting my SD49225T-HN.

View attachment 35696

How about the camera's log itself....any clues there ?

 

[Q™]

How about the camera's log itself....any clues there ?

That is a good idea Sherlock! I cleared the camera log to clean it out and I'll keep an eye on it. I'm also running a "timed ping" on the camera's IP address with this command...

ping -t 192.168.1.200|cmd /q /v /c "(pause&pause)>nul & for /l %a in () do (set /p "data=" && echo(!date! !time! !data!)&ping -n 2 192.168.1.200>nul" >C:\Users\Admin\Desktop\logs\pingtest.txt

 

[Q™]

Hmmm. Perhaps the camera is rebooting. The Blue Iris log shows that the camera becomes unresponsive for a couple of minutes which seems to be approximately the time it takes for the camera to reboot...

11/29/18 18:57 Signal: restored
11/29/18 20:12 Signal: network retry
11/29/18 20:12 Signal: refused; check IP address and port
11/29/18 20:12 Signal: network retry
11/29/18 20:12 Signal: refused; check IP address and port
11/29/18 20:13 Signal: network retry
11/29/18 20:13 Signal: restored
11/29/18 20:22 Signal: network retry
11/29/18 20:22 Signal: timeout; check IP address and port
11/29/18 20:22 Signal: network retry
11/29/18 20:22 Signal: refused; check IP address and port
11/29/18 20:23 Signal: network retry
11/29/18 20:23 Signal: restored
11/29/18 20:29 Signal: network retry
11/29/18 20:29 Signal: network retry
11/29/18 20:29 Signal: refused; check IP address and port
11/29/18 20:30 Signal: network retry
11/29/18 20:30 Signal: restored
11/29/18 20:37 Signal: network retry
11/29/18 20:37 Signal: timeout; check IP address and port
11/29/18 20:38 Signal: network retry
11/29/18 20:38 Signal: refused; check IP address and port
11/29/18 20:38 Signal: network retry
11/29/18 20:38 Signal: restored
11/29/18 20:47 Signal: network retry
11/29/18 20:48 Signal: timeout; check IP address and port
11/29/18 20:48 Signal: network retry
11/29/18 20:48 Signal: refused; check IP address and port
11/29/18 20:48 Signal: network retry
11/29/18 20:48 Signal: restored
11/29/18 20:55 Signal: network retry
11/29/18 20:55 Signal: network retry
11/29/18 20:56 Signal: network retry
11/29/18 20:56 Signal: timeout; check IP address and port
11/29/18 20:56 Signal: network retry
11/29/18 20:57 Signal: timeout; check IP address and port
11/29/18 20:57 Signal: network retry
11/29/18 20:57 Signal: timeout; check IP address and port
11/29/18 20:57 Signal: network retry
11/29/18 20:57 Signal: refused; check IP address and port
11/29/18 20:58 Signal: network retry
11/29/18 20:58 Signal: restored
11/29/18 20:59 Signal: network retry
11/29/18 21:00 Signal: timeout; check IP address and port
11/29/18 21:00 Signal: network retry
11/29/18 21:00 Signal: timeout; check IP address and port
11/29/18 21:00 Signal: network retry
11/29/18 21:01 Signal: timeout; check IP address and port
11/29/18 21:01 Signal: network retry
11/29/18 21:01 Signal: timeout; check IP address and port
11/29/18 21:01 Signal: network retry
11/29/18 21:02 Signal: timeout; check IP address and port
11/29/18 21:02 Signal: network retry
11/29/18 21:02 Signal: restored
11/29/18 21:18 Signal: network retry
11/29/18 21:18 Signal: timeout; check IP address and port
11/29/18 21:18 Signal: network retry
11/29/18 21:19 Signal: timeout; check IP address and port
11/29/18 21:19 Signal: network retry
11/29/18 21:19 Signal: restored
11/30/18 1:52 Signal: network retry
11/30/18 1:53 Signal: timeout; check IP address and port
11/30/18 1:53 Signal: network retry
11/30/18 1:53 Signal: timeout; check IP address and port
11/30/18 1:53 Signal: network retry
11/30/18 1:53 Signal: restored
11/30/18 2:18 Signal: network retry
11/30/18 2:18 Signal: refused; check IP address and port
11/30/18 2:18 Signal: network retry
11/30/18 2:18 Signal: refused; check IP address and port
11/30/18 2:19 Signal: network retry
11/30/18 2:19 Signal: restored
11/30/18 3:42 Signal: network retry
11/30/18 3:43 Signal: timeout; check IP address and port
11/30/18 3:43 Signal: network retry
11/30/18 3:43 Signal: timeout; check IP address and port
11/30/18 3:43 Signal: network retry
11/30/18 3:43 Signal: restored
11/30/18 6:22 Signal: network retry
11/30/18 6:22 Signal: timeout; check IP address and port
11/30/18 6:22 Signal: network retry
11/30/18 6:23 Signal: timeout; check IP address and port
11/30/18 6:23 Signal: network retry
11/30/18 6:23 Signal: restored
11/30/18 8:30 Signal: network retry
11/30/18 8:30 Signal: timeout; check IP address and port
11/30/18 8:30 Signal: network retry
11/30/18 8:31 Signal: refused; check IP address and port
11/30/18 8:31 Signal: network retry
11/30/18 8:31 Signal: restored
11/30/18 18:00 Signal: network retry
11/30/18 18:00 Signal: network retry
11/30/18 18:01 Signal: network retry
11/30/18 18:01 Signal: network retry
11/30/18 18:02 Signal: timeout; check IP address and port
11/30/18 18:02 Signal: network retry
11/30/18 18:02 Signal: restored
11/30/18 19:15 Signal: network retry
11/30/18 19:16 Signal: timeout; check IP address and port
11/30/18 19:16 Signal: network retry
11/30/18 19:16 Signal: refused; check IP address and port
11/30/18 19:16 Signal: network retry
11/30/18 19:17 Signal: restored

 

[JayS_IPCams]

Q I believe I have the exact same issue! I noticed that just before my camera rebooted, I couldn't do anything with it... Any feed already attached (so BlueIris) kept is image, but couldn't send PTZ commands. And my phone using tinyCam couldn't make a new connection to it, and the web interface wouldn't respond. (like you, pings did). After about 5-10min, the camera rebooted and full access was fine again.


I get in the camera log just before reboots:

Time: 2018-12-02 09:03:49
Username: System
Type: Abort
Content:
Time: 2018-12-02 09:02:31

I also have in the camera log lots of Login/Logout logs from the BlueIris server IP... I can only assume that is BlueIris doing something? Looks to be Onvif, which i would guess is PTZ commands.

 

[JayS_IPCams]

The other way I know its rebooting, is because I have it set to goto a specific spot on startup. Which i find it at several times a day. I then move it far off that spot so I can see if it happens again.
Thankfully I'm not suing this camera for anything security important/tracking, so I will likely just live with this nuisance
Hopefully I don't keep running into the same issue as you, and I did just today, that the camera stops responding all together for 5-10 minutes before reboots.

If i get a warm enough day, i'll run a 12v dedicated power line to it.

 

[Tinman]

Just a thought, do NOT use tinycam at all during the test. It may sound stupid but I have seen tinycam cause a Dahua cam to switch its video type from h.264 to mpeg. This was not the same model, so may have no bearing at all. Also would check your encoding settings. I will post mine since mine NEVER reboots. Try them and see if there is any change.

 

[looney2ns]

Just a thought, do NOT use tinycam at all during the test. It may sound stupid but I have seen tinycam cause a Dahua cam to switch its video type from h.264 to mpeg. This was not the same model, so may have no bearing at all. Also would check your encoding settings. I will post mine since mine NEVER reboots. Try them and see if there is any change.

View attachment 35774

What exact camera model and firmware version are you using?

 

[Tinman]

What exact camera model and firmware version are you using?

Same as his: SD49225T-HN frequent restarts

 

[JayS_IPCams]

Thanks @Tinman - I copied your settings on video (i had it at 20FPS and a higher bitrate as i want to record fast motion, but will try the lower settings).
I also disable the secondary stream, which I used for just quick remote viewing, just in case. Lets see if that makes it more stable.

Also, are you powering it via PoE+ or 12v adapter?

 

[Tinman]

Thanks @Tinman - I copied your settings on video (i had it at 20FPS and a higher bitrate as i want to record fast motion, but will try the lower settings).
I also disable the secondary stream, which I used for just quick remote viewing, just in case. Lets see if that makes it more stable.

Also, are you powering it via PoE+ or 12v adapter?

POE+ on a
GS1200-5HP

 

[JayS_IPCams]

POE+ on a
GS1200-5HP

Right, think you said that before or in the other post, sorry, and thanks. I have one on order as I want to add more cameras to that location anyways.
Hopefully its just a Firmware issue they haven't resolved due to my video settings, I've copied yours and finger crossed that does it!

 

[Q™]

Right, think you said that before or in the other post, sorry, and thanks. I have one on order as I want to add more cameras to that location anyways. Hopefully its just a Firmware issue they haven't resolved due to my video settings, I've copied yours and finger crossed that does it!

As an FYI, IMO the SD6CE245U-HNI Starlight 45x is a MUCH better camera, albeit more expensive.

 

[Dark_Chocolate]

As an FYI, IMO the SD6CE245U-HNI Starlight 45x is a MUCH better camera, albeit more expensive.

I don’t mind paying more for more advanced and better camera. The problem is all their ultra series PTZ cameras are huge and heavy. And I can’t mount them in front of my house. To make matter worse, they don’t make compact mount. All their mounts will stick out the camera by a foot. My camera needs to be discreet and not intimidate my neighbors.

 

[Q™]

 

[Q™]

They draw their bedroom curtains and cower at the awesome power of this fearsome video beast!

 

[JayS_IPCams]

well... setting change didn't work
Strange too how my reboots seem to be so sporadic... went over 12hrs without one over night (a really cold one) the other day, then yesterday and overnight last night, several... two just this am.
so the search for the issue continues.

Hopefully its warm enough i can get to the re-wire today for 12v direct power and test that.

 

[Tinman]

well... setting change didn't work
Strange too how my reboots seem to be so sporadic... went over 12hrs without one over night (a really cold one) the other day, then yesterday and overnight last night, several... two just this am.
so the search for the issue continues.

Hopefully its warm enough i can get to the re-wire today for 12v direct power and test that.

Well, that is one step we can cross off the list. Next one will be power, but still need to eliminate the possibility of a cable issue as well too. Could be bad cable crimp. The last resort will be to bench test the cam with a short new cable and 12v power to it....not what you wanted to hear.