Narcissus
Getting the hang of it
Thanks. Using web UI now.
[FIXED]Help Needed: Cameras keep disconnecting and reconnecting after Dahua NVR firmware update to V4 from V3.
- Thread starter Narcissus
- Start date
bigredfish
Known around here
The only part that doesn’t make sense to me is that error message you showed. Never seen it and not finding anything on it…
Narcissus
Getting the hang of it
Appreciate you, and others, taking the time to help me with this. This is bloody frustrating.
bigredfish
Known around here
It’s odd because it was working prior to fw update. That tells me something got lost in translation. It acts like an IP conflict, been there done that. But can’t put my finger on how as the internal switch is assigning unique IPs per your registration screen
bigredfish
Known around here
Im 7 months from retirement and practicing my killing time skills ..
Probably something wonky in the update didn't take or write over correctly, which is why we recommend the factory resets BEFORE and AFTER a firmware update!
Last edited:
Parley
Known around here
I have been doing some research and ran across this article. I am trying to get a handle on all of this. 
What is Bitrate in NVR and Why is it So Important? | SCW (getscw.com)
What is Bitrate in NVR and Why is it So Important? | SCW (getscw.com)
bigredfish
Known around here
I remember reading that some years back. It was at a time when many manufacturers including Dahua didn’t spell out incoming bandwidth clearly. It is helpful though.
The NVR here is capable of 320 Mbps or 320,000 Kb/s. A 2MP camera running 30fps will use roughly 10,000 Kb/s, so you could expect to run 32 2MP cameras at that rate.
So if the problem was too much incoming bandwidth , lowering bitrate as well as FPS would indeed help.
This is different than decoding ability which is the ability to stream/view video vs record it.
www.getscw.com
The NVR here is capable of 320 Mbps or 320,000 Kb/s. A 2MP camera running 30fps will use roughly 10,000 Kb/s, so you could expect to run 32 2MP cameras at that rate.
So if the problem was too much incoming bandwidth , lowering bitrate as well as FPS would indeed help.
This is different than decoding ability which is the ability to stream/view video vs record it.
Understanding Encoding and Decoding in Video Compression
Wondering why you can't find that security camera with ah HDMI connection? Learn the reason why and alternative solutions.
www.getscw.com
Last edited:
Parley
Known around here
Thanks for that and so true. I view 16 cameras at one time using Hikvision IVMS-4200 and the decoding capacity can and does become a problem with that software. I have noticed it even with the monitors at the NVR's. So, If the OP was only looking at say 2 or maybe 4 cameras at one time, he should be able to see them. If he is trying to look at all 6 cameras at one time, I would think that would be a problem depending on what device he was using. I hope I have all of the right.
bigredfish
Known around here
Yessir I believe so
So its a matter of are they recording or is it purely a problem with decoding/viewing all at once? Which the OP should clarify as that would help a lot.\
Typically on Dahua NVRs/XVrs if you exceed incoming bandwidth they'll drop the last camera and so on until they get under the max bandwidth limit,
Also typically if its a decoding issue, they'll display something about "Out of Resources"
The OP is getting this which is odd and led me to the IP conflict theory as Ive seen that when connecting multiple cams at 192.168.1.108. The system will flash on then off as they fight for that IP. This error suggests the camera and the port on the NVR arent matching IP?
But again I come back to "it was working before the fw update"
So its a matter of are they recording or is it purely a problem with decoding/viewing all at once? Which the OP should clarify as that would help a lot.\
Typically on Dahua NVRs/XVrs if you exceed incoming bandwidth they'll drop the last camera and so on until they get under the max bandwidth limit,
Also typically if its a decoding issue, they'll display something about "Out of Resources"
The OP is getting this which is odd and led me to the IP conflict theory as Ive seen that when connecting multiple cams at 192.168.1.108. The system will flash on then off as they fight for that IP. This error suggests the camera and the port on the NVR arent matching IP?
But again I come back to "it was working before the fw update"
With that error, could it be that 10.1.1.65 was a different camera prior to the update and for some reason the update started a soft re-initialization and then it ended up momentarily with two 10.1.1.65 IPs?
And we know what we say about "it working before the fw update" LOL
bigredfish
Known around here
Yeah thats my thinking, but on a new system or one that hasnt been messed with as far as networking settings, I can take a camera from one PoE port and exchange it with another and both will automagically assume the new port and work. I've done it a lot this week while installing my new cameras on a 5216-16P-4KS2
bigredfish
Known around here
LOL. I just noticed his bandwidth usage showing at the bottom of the error message screen. It’s been so long since I’ve used the machine interface I didn’t know it displayed that…
Parley
Known around here
Good catch. ^^^^^
Narcissus
Getting the hang of it
All six cameras displayed on the monitor simultaneously. The two 12MP, fisheye cameras are running in M mode; the remaining 4 4K cameras in S1 mode. This was not an issue with the V3 firmware that came with the NVR.
Narcissus
Getting the hang of it
They are recording when not disconnected from the network, just checked.
Parley
Known around here
For my education, what is the M mode and what is the S1 mode?
Narcissus
Getting the hang of it
Apologies. Referring to Switch Streams: M = Main Stream; S1 = Sub Stream 1. Under "Camera" then "Encode" menus.
Narcissus
Getting the hang of it
What's the significance? I'm asking out of pure ignorance and a desire to know. I made sure to include since bandwidth had been queried a few times.
Parley
Known around here
I thought that might be the case, but I was not sure.