IP5M-B1186EW connection log out

[i86time]

Hello, I am having an issue with IP5M-B1186EW cameras (seemingly) randomly disconnecting and connecting throughout the day. I have a QSee QC826 16 channel NVR (I believe this is a re-branded Dahua unit) and recently two of the QCN8099B cameras (also Dahua rebrands) died. I replaced them with two Amcrest IP5M-B1186EW. They were detected and connected fine, so I ended up purchasing two more to gain more coverage. However, when looking back at recordings, I have noticed that at least once a day since install, and frequently more often, they have had multiple dropouts of about 10-30 seconds, sometimes longer. However not all the Amcrest cams drop at the same time, nor for the same length of time. The camera dropouts correspond to user logout / login events in my log, which look like the attached.

None of the original QC cameras still in service show these issues.
Aside from this there does not appear to be any issues. Any idea what could be causing this behavior? All Amcrest cams have the 2.82 firmware (one I had to upgrade).

[Revo2Maxx]

Hello and welcome to the forum.

How are the cameras connected? Back of NVR POE ports or through Switch?

Changed password or other default settings?

[i86time]

Hello, thank you for the response. The cameras are connected via built in NVR POE ports of the QC826. The account I am using is not the standard admin account as QC has issues where when the default PW of admin account is changed, it would not 'remember' it , causing a log out and eventual lock out requiring re-boot. The workaround is to create a new admin account, but I have been using this account for over 3 years. The only change I made to the Amcrest cameras was to remove the watermark.

[Revo2Maxx]

Ok, Couple of things. Are you sure that your old camera are really dead?

What type of Power supply does your NVR use? Is it one that is built into the NVR or is it one that has a Brick outside the NVR and only thin wire connection (Round Barrel Connector type)

Here is why I ask. If it is the round type it might be that your power supply is starting to die. When you connect a new camera it might be that the Amcrest cameras have less power needs and so they worked. However because the system is having issues as the power supply fails even more.. I just had to replace a Brick Style supply on my 4116E-HS, Was having issues of going offline every other day between daily reboots. I changed HDD, Reset the NVR back to factory and all other things that would normally need to be done and only thing that helped was a new Brick supply. Sometimes with POE cameras connected it can have Power to camera issues..

So one thing to try and not something people want to do.. However take the cameras that you added last and move them to locations on the NVR that the cameras are not going off line all the time. Then see if that changes the issues to the cameras that you moved there and the Amcrest ones stay going...

What I mean is for my NVR's I can't say about yours as I don't have that brand. So for my Amcrest NVRs on a 8 Port POE, There are 4 ports as a system. So what is going on in say first 4 might be better off then the last 4.. SO if I have an issue I can move a camera from say Port 6 to Port 2 and if the same issue isn't there after the change then there can be an issue traced to last 1/2 of the ports rather then the camera.. Also another thing is what type of cables are you using? If they are ones that came with NVR and Cameras maybe a quality that is not good enough for Amcrest cameras? I know some of this might not be easy to understand but one of the biggest issues with Cable Connected Cameras is quality of cables.. Next could be damage behind the walls caused by heat or critters..

[i86time]

Hello,
Yes, I am certain the first two cameras are dead. I verified this for both by connecting them to the NVR via a short Cat6 cable and got no signs of life, no IR LEDs, nothing. I even tried opening them up and pressing what I believed to be the hard reset switch (not a lot of documentation on them), and still nothing.

The power cord plugs directly into the NVR unit, no separate power brick.

The 2nd set of Amcrest cameras I purchased (after replacing the 2 bad ones) were connected to two ports that had not been previously used (it is a 16 channel NVR, but only came with 8 cameras). Are you saying I should switch those with the physical ports where I currently have the original QC cameras without issues? Two of the cables I am using came with the original QC NVR, the other 2 are brand new Cat6.I inspected the cables when I ran the new ones and didn't see any obvious damage. Most of the cabling is in my attic out of the elements and no signs of animals.

One thing I noticed is that the substream for my QC cams is 48 kbps, but the Amcrest defaaulted to 512 kbps. I have all of my main streams @ 6144 kbps CBR. I lowered the Amcrest down to 160 kbps (lowest setting), and will see how that goes. Maybe the NVR can't keep up with the required bandwidth?

[Revo2Maxx]

Yeah I am not sure. What I was talking about was connecting your Amcrest Cameras to ports that your QC are connected. If the passwords are different then you would have to change that. But what I was trying to do was find out if the issue was NVR port related or other issue.

With the low Sub Bit rate it might be why the NVR would kick off the Amcrest camera if maybe there was something where it reboots the camera if it gets out of sync. So testing with less bit rate is good idea. I would personally look over the settings of your current working Qc and see if your Amcrest cameras can work at them settings and see if that keeps them logged in.

There is just so many things that it could be. Then with QC no longer doing these, I don't even think there is a Qc app anymore? Were you able to get an update FW before they closed down? That was sometime in 2020 or 2021? Do they still offer Support or pass along support for the hardware to a different company or are they just gone? Amcrest app should work or DMSS from Dahua. Also ASP should work for PC software as well..

So your NVR is kind of like my 4216E-AI NVR that it has plug in type power supply and 16POE ports. I have others from Amcrest as well that are 16ch but only 8 Poe ports..

I would try running the lower rate and see if that helps if not I would try to change ports as I said to see if maybe there is an issue with the ports they are in. Best way to test is moving working non issue camera to a port that is giving issues and one not to one that is. If the issue follows the camera with issues then it is camera related if it has issues with the cameras that was working before then there is a port issue. Just trying to do what I would do to find out where to start looking for faults..

However with the different bit, Chaning would be first action to see if that helps.. Try to run at same as the working cameras in bit rate and FPS if able. However it is hard to say without different actions and keeping track of the results..

Sorry couldn't be of more help.

Be safe Stay Warm.

[i86time]

Thanks again for the reply. Changing substream properties didn't help as there were more dropouts overnight, and somehow the entire substream for one of the cameras went out and never came back until a reboot.

Other than the admin password issue, I never had a problem with the NVR, so I never bothered to apply any firmware updates. Now I wish I had at least downloaded them. I can't seem to find any archives either, I might join and ask on ipcamtalk. I did see a post on there from a user with similar dropout issues, which he related to static vs DHCP IP, though he mentioned it was specifically for the cameras and not the NVR. I had my NVR on static IP, but switched to DHCP to test. I cannot find a way to assign DHCP to the cams though.

If that doesn't work, I'll go back to basics. I'll connect just one of the Amcrest cams to a known good port and see what happens for a few hours and then slowly add cams back.

[Revo2Maxx]

So I don't know what your system looks like. It has been a long time since I see your menu type. I do have a NVR with it just have to dig it out lol. So looking at the oldest one in my lineup in use. When you go to your NVR's WebUI setup, camera, Remote Device does it look like the picture below? Or something that at least looks like you could click the e to get a connection? You might have to enable it under the normal Network Tab. If you have to enable it there would be a box that says Enable Virtual Host or something to give you the ability to make a connection to your cameras behind your NVR's POE.. If you look at this picture below, Port 8 is in use by the NVR POE port the rest are just normally connected. If I hit the e on the ch8 aka port 8 I will get a NVR ip with a port number and I can log into that camera to make adjustments within that cameras.

Screenshot (3765).png (172.63 KiB) Viewed 691 times

[i86time]

Hello,
Yes, I have a screen that looks like that, but no IE icon to open up any connection. If I double click the Modify or Status icon, it opens the attached window. However clicking on Connect does nothing (for either the original QC cams or newer Amcrest cams) and the Setup button is grayed out.

[Revo2Maxx]

No not that.. That is to mod the connection of the camera..

Look in your Network settings and see if you have a Virtual Host Button to enable... if you don't as some don't have the option then only way would be to use A switch aka POE switch or run power to the camera if it is reachable. Then connect the cable to your router..

So Switch with POE to power the camera connect direct to camera to make changes or An injector or 12v power supply at the camera and cable connected to Router/Hub/ or Switch..