Had to power cycle one camera after 1 day of usage..... (frozen cam)

[Cobalty2004]

Just had two 8mp IB8M-T2599 2.8mm installed at my residence yesterday. It has the latest FW that was released last month.

After a long morning of hosting a garage sale where one of my cameras was undoubtedly recording every second of it, I came back inside to this camera having a no signal alert in BI. I couldn't even login to the camera over its IP address, yet I could ping the camera, and my router said it had a good connection. The Amcrest IP tool could also see this camera, but couldn't interact with the camera in any way.

I cycled the PoE connection and when it restarted it was fine.

Anything I could be doing to warrant a freeze like this? Is my camera bad? Thing doesn't even have 24hrs of uptime!

The cameras are connected via cat6, and the runs are much less than the 300' that this cable can hold.

[Revo2Maxx]

Hello and Welcome to the Forum

I would double check that your camera is Infact connected to a Cable that is PURE COPPER and not CCA.. If you look at your cable and there is anything that even looks like fake rating or says CCA at any distance over 130ft on a low current rated camera will or can be damaged. This also goes up when the heat of the day or area of where the camera cables are ran (In the heat of an Attic or Direct Sunlight). Something you could do is move a Power supply to the camera and power the camera at the camera. This will not protect the camera 100% but will be better then fast cooking the camera.

Outside of that I don't know why it would not work well in BI unless you maybe didn't setup a Static IP and your network rebooted giving the camera a different IP.

[Cobalty2004]

Hello and Welcome to the Forum

I would double check that your camera is Infact connected to a Cable that is PURE COPPER and not CCA.. If you look at your cable and there is anything that even looks like fake rating or says CCA at any distance over 130ft on a low current rated camera will or can be damaged. This also goes up when the heat of the day or area of where the camera cables are ran (In the heat of an Attic or Direct Sunlight). Something you could do is move a Power supply to the camera and power the camera at the camera. This will not protect the camera 100% but will be better then fast cooking the camera.

Outside of that I don't know why it would not work well in BI unless you maybe didn't setup a Static IP and your network rebooted giving the camera a different IP.

I will have to ask the electricians I hired what kind of cable they used. My runs are probably 50' at most, I have them going to a female jack behind my loft TV which has the PoE switch that powers these units. Next to those female jacks is another that goes to my basement router.

Hopefully heat won't be an issue, today is very comfortable, but Ohio summers can really heat an attic up.

[Cobalty2004]

I confirmed they used CAT6 UTP Riser cable. So that is a plus!

[Pogo]

Could still be stranded pair, though 50' and terminated properly should make zero difference in IP camera performance.

I'd examine the cam config itself with what's configured in Blue Iris. A discrepancy could cause the problem if BI just gives up trying to accommodate the difference in configs. Check the Status window for bouncing, frame rate, etc., of the particular camera.

And as mentioned, a changing IP address is also a possibility if the IP address isn't reserved for the camera in the dhcp server/router.

[Cobalty2004]

This is definitely a camera or cable termination issue. When I get a No Signal in BI I cannot login to the webinterface directly to the camera. Yet I can see it on my router.

I'm going to have my electricians come back and verify both ends and the cable itself. If that checks out I will have a new camera at the ready to be installed and just return this other one. (I don't have a ladder that can go this high).

Ok now the camera is going in and out between working properly with view and 'No Signal'. Definitely screams cable termination or maybe they got to heavy handed when they were affixing it to my attic trusses.

[Pogo]

If you can ping the address you have a data path. From a command prompt, type> ping xxx.xxx.xxx.xxx -l 2048 -t

This will hammer the camera IP address with a 2048 byte long packet until you terminate it by pressing ctrl C.

This will also display the packet loss results as a percentage. You can let it run in the background all day if you like. If the camera loses its BI connectivity but there's no packet loss (or a very low percentage <5%), that will scream misconfiguration and require appropriate investigation to correct the problem as previously suggested.

[Cobalty2004]

If you can ping the address you have a data path. From a command prompt, type> ping xxx.xxx.xxx.xxx -l 2048 -t

This will hammer the camera IP address with a 2048 byte long packet until you terminate it by pressing ctrl C.

This will also display the packet loss results as a percentage. You can let it run in the background all day if you like. If the camera loses its BI connectivity but there's no packet loss (or a very low percentage <5%), that will scream misconfiguration and require appropriate investigation to correct the problem as previously suggested.

When looking for misconfiguration am I just confirming the video settings in BI match what I'm using on the webinterface for the camera?

Basically resolution and fps? Sorry for the basic questions, I'm new to this.

I do have static IPs assigned to each camera.

I ran for a few minutes that ping command on each camera IP, the one in question had a 5% PL, my other (which is working flawlessly) is 0%.

[Pogo]

Sounds like a connectivity problem in that cable run (or at one end or the other). You reduce the packet size to 1024 or 512 and see what happens, but my guess is there will still be packet loss.

Otherwise...

The parameters you mentioned are the ones I'd check first. You could also compare them to the other camera for easier reference/confirmation. Make sure the sub stream info (if used) matches. You may also just want to try deleting the camera and re-adding it in case something got squirrely the first time around.

Which cameras are we talking about? And did you let BI do its automated thing to add them or enter your own parameters? Are you referring to any of the YouTube channels? There are several real good ones, each with its own style and pace, but all are pretty good and worth a look if you're new to BI. I've been running BI for a little over a year and still watch em occasionally for reference or if trying a new feature.

Anyway, sorry for the ramble. If the config stuff comes up fine, feel free to scream at me for second guessing your initial assessment! LOL

Good luck with it.

[Revo2Maxx]

I would also look at your cable. If it is CCA in the attic it could be problematic in the hot of day over cooler nights, However if the length is long it could have issue both day and night because of the extra resistance CCA has over real copper cables. Something to try if able, Move a power supply to the camera location even if this means you need to run an Extension cable to the location. This can test and if the issue go away with 12v power at camera site it could be bad cable, bad cable ends and posted before and or even a hard kink or bend in the cable could cause issue. Also distance can play a factor. If there is any exposed and wind hits it can cause data loss.

So something easy to do right away. Is try a Different Port on our Router/Hub/Switch and or POE NVR however your cable is connected. Try a different port and see if the issue goes away as Hardware can fail as well. If you have a Managed Hub looking at the Logs can help with Packet loss info and might even show other data that can help find and fix the cause of the issues. Some Switches even offer cable test that could point to where the damage is in your run.