When you wire up your POEs inside enclosures do you wire up a receptacle inside the box?Another thought. If you have power out there, and given that there's probably lighting on poles nearby, you could mount to one of those and use a dedicated wireless link to get the signal back to the building. A Ubiquity Nano Loco M5 would do the trick and can handle, probably eight cameras or more. You would also need an enclosure to house a PoE switch, Ubiquity uses a different PoE standard from cameras and the two don't play well together, and the wall wart for the Loco.
That would give you a much shorter distance to work with in terms of capture. It's all a tradeoff in terms of cost/labor, but it would insure good captures and require much shorter focal lengths.
How much are you selling them for when you get them in stock?The IPC-HFW5241E-Z12E stock using up fast last week than we expected, have some stocks on the way to US amazon warehouse. Should be there next week, thanks for your attention!
Any idea roughly how many plate captures I can store on a 128GB sd card if I use one?
How much are you selling them for when you get them in stock?
Not me. Sorry have not been on for a while as I was traveling.No way the Z4E will get plates reliably at 95 feet... I think it was @samplenhold or @biggen that tried it at 60ish feet and exchanged it for the Z12E
Nice shots! Thanks!Not me. Sorry have not been on for a while as I was traveling.
Here is a capture from the other night using the 5442 Z4E. It is set at 26mm and this plate is about 65-70 feet from the cam. This car was used by perps breaking into cars and homes Wednesday morning. I do not use this cam for LPR, but it worked just fine with all of the light in that intersection. I use the 5241 Z12E's for LPR.
View attachment 117791View attachment 117792
Not me. Sorry have not been on for a while as I was traveling.
Here is a capture from the other night using the 5442 Z4E. It is set at 26mm and this plate is about 65-70 feet from the cam. This car was used by perps breaking into cars and homes Wednesday morning. I do not use this cam for LPR, but it worked just fine with all of the light in that intersection. I use the 5241 Z12E's for LPR.
View attachment 117791View attachment 117792
I will reduce the bitrate andSo first thing is make the main and substream both the same. Most of us here recommend H264. Make sure that you do not have any smart codec on as well. The storage savings is minimal between the two. YMMV.
Is the camera going thru the router? If so, wifi routers are notorious for not being able to keep up with the demands of these cameras. Unlike streaming services like Netflix, these cameras do not buffer, so one lost packet and it has to start over. Especially if you are maxing out the camera. Unplug internet while watching Netflix and it will probably continue for 45 seconds. Do it with this camera and the feed stops instantly.
No reason to run more than 15FPS, and many us have cams running at 10 to 12 FPS. Movies for the big screen are shot at 24FPS, so I do not think we need 30FPS for these cameras LOL. The goal is to get a clean image, not smooth motion. 4096 or 8192 bitrate is all you need. My LPR runs 8FPS and the car is in the frame for less than a half second and I catch every plate. YMMV.
Keep in mind that these type of cameras, although are spec'd and capable of these various parameters, real world testing by many of us shows if you try to run these units at higher FPS and higher bitrates than needed that you will max out the CPU in the unit and then it bugs out just long enough that you miss something or video is choppy or pixelated or you get lost signals. My car is rated for 6,000RPM redline, but I am not gonna run it in 3rd gear on the highway at 6,000RPM...same with these types of units - gotta keep them under rated capacity. Some may do better than others, but trying to use the rated "spec" of every option available is usually not going to work well, either with a car or a camera or NVR.
Look at all the threads where people came here with a jitter in the video or video dropping signal or IVS missing motion or the SD card doesn't overwrite and they were running 30FPS and when people tell them to drop the FPS and they dropped the FPS to 15FPS the camera became stable and they could actual freeze frame the image to get a clean capture. The goal of these cameras are to capture a perp, not capture smooth motion. When we see the news, are they showing the video or a freeze frame screen shot? Nobody cares if it isn't butter smooth...getting the features to make an ID is the important factor. As always, YMMV...
Further, these types of cameras are not GoPro or Hollywood type cameras that offer slow-mo capabilities and other features. They "offer" 30FPS and 60FPS to appease the general public that thinks that is what they need, but you will not find many of us here running more than 15 FPS; and movies are shot at 24 FPS, so anything above that is a waste of storage space for what these cameras are used for. If 24 FPS works for the big screen, I think 15 FPS is more than enough for phones and tablets and most monitors LOL. Many of my cameras are running at 12FPS.
In fact, many times if a CPU is maxing out, if it doesn't drop signal, then it will adhere to the FPS but then slow the shutter down to try to not max the CPU, which then produces a smooth blurry image..that is the video my neighbor gets who insists on running 60FPS. He gets smooth walking people but you can't freeze frame it cause every frame is a blur, meanwhile my 12FPS gets the clean freeze frame. Shutter speed is more important the FPS. We both run the same shutter speed by the way, but his camera CPU is maxing out and something gotta give when you push it that hard.
So first thing is make the main and substream both the same. Most of us here recommend H264. Make sure that you do not have any smart codec on as well. The storage savings is minimal between the two. YMMV.
Is the camera going thru the router? If so, wifi routers are notorious for not being able to keep up with the demands of these cameras. Unlike streaming services like Netflix, these cameras do not buffer, so one lost packet and it has to start over. Especially if you are maxing out the camera. Unplug internet while watching Netflix and it will probably continue for 45 seconds. Do it with this camera and the feed stops instantly.
No reason to run more than 15FPS, and many us have cams running at 10 to 12 FPS. Movies for the big screen are shot at 24FPS, so I do not think we need 30FPS for these cameras LOL. The goal is to get a clean image, not smooth motion. 4096 or 8192 bitrate is all you need. My LPR runs 8FPS and the car is in the frame for less than a half second and I catch every plate. YMMV.
Keep in mind that these type of cameras, although are spec'd and capable of these various parameters, real world testing by many of us shows if you try to run these units at higher FPS and higher bitrates than needed that you will max out the CPU in the unit and then it bugs out just long enough that you miss something or video is choppy or pixelated or you get lost signals. My car is rated for 6,000RPM redline, but I am not gonna run it in 3rd gear on the highway at 6,000RPM...same with these types of units - gotta keep them under rated capacity. Some may do better than others, but trying to use the rated "spec" of every option available is usually not going to work well, either with a car or a camera or NVR.
Look at all the threads where people came here with a jitter in the video or video dropping signal or IVS missing motion or the SD card doesn't overwrite and they were running 30FPS and when people tell them to drop the FPS and they dropped the FPS to 15FPS the camera became stable and they could actual freeze frame the image to get a clean capture. The goal of these cameras are to capture a perp, not capture smooth motion. When we see the news, are they showing the video or a freeze frame screen shot? Nobody cares if it isn't butter smooth...getting the features to make an ID is the important factor. As always, YMMV...
Further, these types of cameras are not GoPro or Hollywood type cameras that offer slow-mo capabilities and other features. They "offer" 30FPS and 60FPS to appease the general public that thinks that is what they need, but you will not find many of us here running more than 15 FPS; and movies are shot at 24 FPS, so anything above that is a waste of storage space for what these cameras are used for. If 24 FPS works for the big screen, I think 15 FPS is more than enough for phones and tablets and most monitors LOL. Many of my cameras are running at 12FPS.
In fact, many times if a CPU is maxing out, if it doesn't drop signal, then it will adhere to the FPS but then slow the shutter down to try to not max the CPU, which then produces a smooth blurry image..that is the video my neighbor gets who insists on running 60FPS. He gets smooth walking people but you can't freeze frame it cause every frame is a blur, meanwhile my 12FPS gets the clean freeze frame. Shutter speed is more important the FPS. We both run the same shutter speed by the way, but his camera CPU is maxing out and something gotta give when you push it that hard.
I was using Chrome I will try Explorer as well.I meant to match the FPS and iframes of the mainstream and substream., not the resolution. 1080 for main and D1 for sub is fine.
Are you using Explorer as the browser? Not Chrome, not Edge, but plain ole Explorer baked into Win10?
It shouldn't be firmware related as this is an older camera and Andy puts the best firmware on it, so it may or may not be the most recent. Mine are running the original firmware that it came with.
I am assuming the computer is powerful enough it can handle the demands of the video stream?
I guess it could be the POE injector.
What about downloading a trial of BI or VLC and see if it can handle the mainstream or VLC? If they can handle it then you know it is maybe something with the browser/firmware. At that point I would try a factory reset and see if that clears out the cobwebs.
But the camera is certainly capable of providing a mainstream. I have never had it switch on me, but I have seen it happen to my neighbor with his cheap laptop that couldn't keep up.
Thanks a lot! I switched to IE and everything else you said and it's working flawlessly. It was Chrome causing the issue. Can you help with setting this up for remote view with dmss? I have a public up for the camera with ports forwarded but I still can't connect through the app. The ISP here does not allow customers access to the router management menu so I am only trusting them that they did it correctly. I am trying to connect via TCP on port 37777 with no luck.Yeah reolink NVR only works with reolinks despite any claims.
The cams are sensitive to Explorer so hopefully that fixes it
15FPS and 15iframes
H264
CBR
8192 bitrate
Some here run 24/7 B/W, while others go in and manually adjust the schedule a couple times a year, while others use the utility written to change it based on sunrise and sunset.
I told you that would be the right choice!
That looks more like a focus issue than anything else.
For night time you will have to set the focus to manual and set the focus number. Best way to do that would be to park a car right there and then focus it for that.
Have you been able to get this camera into the Reolink NVR or are you running it separate? If it is hooked to the NVR, then the utility won't work without being connected to a computer 24/7.
You could set up the schedule profile in the camera, but that would require you to go in a couple times a year and adjust it. Or run 24/7 B/W or pick one schedule and run that. Say it gets dark at 5pm where you are in the winter and then sun is up at 8am. Set up a schedule where from 8am to 5pm it is color and then B/W the rest. That means in the summer you may get evening hours in B/W.