stroonzo

Let me reiterate what was already described (but in a different way). FPS has nothing to do with capturing the plate clearly. Shutter is the important factor here. You will need a min shutter of 1/1000. Your FPS should be set at a rate consistent with the number of shots in the scene (that you'd like to have) for which a car passes in an amount of time at a speed of travel. Also, using a Hik NVR you will need to most likely go directly to the camera's IP address on that side of the NVR's firewall to access the web GUI to get to setting such as shutter and day night switch.

Here is one I am hoping someone can guide me on: I have what is apparently a Chinese coded camera that I flashed with a US / English DS-2CD2x12,2x32 IP camera firmware v5.3.0_150513. I was not blocked from flashing the camera via the GUI. However, now when I attempt to access the camera via the GUI I get the following: Access Error: 404 -- Not Found firmware language mismatch: /home/webLib. The camera still functions fine. What I mean is, it still works and it is seen in Digifort and it is fully functional with the same configuration as it had prior to the upgrade (I know because I have this set at 1/1000 min shutter). Different than the 5.2 firmware is the SSH connection. I am presented with: BusyBox v1.19.3 (2015-03-20 17:37:48 CST) built-in shell (ash) Enter 'help' for a list of built-in commands. BusyBox v1.2.1 Protect Shell (psh) Enter 'help' for a list of davinci system commands. See that? Davinci system commands. The commands used on the 5.2 firmware (such as calling a directory) are not part of this OS (if an OS is what this is). Basically, I’d like to know how I can change my camera’s (not the firmware’s – that’s easy) designation to US / English. I think that would be the ultimate fix for this particular camera. Thanks, Jeff

I recently picked up two Hikvision 3MP DS-2CD3232-I5 bullets with 12mm lenses to swap out for my plate cams (where I have been using 8mm Dahuas). These are some good cameras, but specifically one thing I want to point out is the difficulty one will have when or if they ever wanted to swap out or adjust the focus on the lens (compared to all of the Dahua cams I have used). On the Dahua cameras (domes and bullets), all I have ever had to do was remove either the dome cover or the bullet cover. For the Hikvision, it appears as if a complete disassembly of the front end of the camera would be necessary. I have no intention or need to change the lens and fortunately the focus was already good. I just wanted to give a very quick bit of info on what I have found. On a side note, the IR on the Hikvision 3MP DS-2CD3232-I5 is just amazing. The two array LEDs on the camera put out more IR than 50 standard LEDs. I am getting IR response on plates at about 175 feet. I get plate recognition during the day at about 175 feet and at night starting at about 100 feet (depending on which camera and the angle of the approach of the specific vehicle). Pictures attached (please keep in mind these pictures were compressed and the quality degraded to allow for upload at the 500KB limit).

My cameras came with a CD with the user manual in PDF. Shoot me your email in a PM and I will send you a copy of it. The manual is written for and covers a wide range of cameras.

Here are cut & pastes from the user manual: Dynamic Analysis for Motion Normal configuration adopts one set of parameter for motion detection during the day and at night. Tasks: 1. Set the Motion Detection Area. Steps: (1)Enter the motion detection settings interface Configuration > Advanced Configuration> Events > Motion Detection (2)Check the checkbox of Enable Motion Detection. (3)Check the checkbox of Enable Dynamic Analysis for Motion if you want to mark the detected objects with green rectangles. Note: Select Disable for rules if you don’t want the detected objected displayed with the rectangles. Select disable from Configuration-Local Configuration-Live View Parameters-rules. Day/Night Switch Select the day/night switch mode, and configure the smart IR settings from this option. Day, night, auto, schedule, and triggered by alarm input are selectable for day/night switch. Day: the camera stays at day mode. Night: the camera stays at night mode. Auto: the camera switches between the day mode and the night mode according to the illumination automatically. The sensitivity ranges from 0~7, the higher the value is, the easier the mode switches. The filtering time refers to the interval time between the day/night switch. You can set it from 5s to 120s. Schedule: Set the start time and the end time to define the duration for day/night mode. Triggered by alarm input: The switch is triggered by alarm input, and you can set the triggered mode to day or night. Smart IR Smart IR gives user an option to turn ON / OFF the IR LED. Set the smart IR to ON, and Auto and Manual are selectable for IR mode. Select AUTO, and the IR LED changes according to the actual luminance. E.g.: if the current scene is bright enough, then the IR LED adjusts itself to lower power; and if the scene is not bright enough, the IR LED adjusts itself to higher power. Select Manual, and you can adjust the IR LED by adjusting the distance. E.g.: If the object is near the camera, the device adjusts the IR LED to lower power, and the IR LED is in higher power if the object is far.

Oh you mean something like this?

I think it would be beneficial for you to check in on this post as well: viewtopic.php?f=19&t=41165&p=248535#p248535

I am glad to have learned something new. For those who don't quite understand how this is, let me help explain. Once I really began to focus on the above statement it all made sense. The common denominator here is SECOND. You have Frames / Second and Kbits / Second. What you are deciding is over a second how many frames of video you wish to capture, and to that amount of frames, how much compression must be used to limit that second's worth of video to X Kbits of data. The more frames you put into the second, the higher you will define your bit rate (in an effort to maintain the same effective level of video quality). Taking Hikvisions bit rate recommendation chart as an example, you can cross multiply and divide to quickly figure out their recommended bits per frame for any given resolution to achieve either Best, Better, or Good quality. Hikvisions calculations come to this for Best Quality: D1= 102 Kbits per FPS 1MP = 204 Kbits per FPS 1.3MP = 324 Kbits per FPS 2MP = 341 Kbits per FPS 3MP = 512 Kbits per FPS 5MP = 712 Kbits per FPS Based on this, one cannot throw out a blanket statement or suggestion on what to set the bit rate to. As you can see it is directly related to 1 - the desired quality of video 2 - the resolution of the camera, and 3 - how many FPS you wish to capture. Based on this, we can understand fully now how, in fact, resolution and FPS play a factor in storage requirements, but only relative to the desired level of quality of video. However, to calculate the storage requirement, there is no argument to MaxIcon at all. Indeed the bits per second clearly define how much data output the camera is making (with no regard to frames or resolution). What does this all mean? In a nutshell it means that as resolution increases (keeping your desired FPS constant - say 15 FPS and maintaining the desired level of video quality - say Best Quality), the amount of available bits per second processing and output from the camera will have to be increased and your storage requirements will increase to accommodate. This puts these 10 and 12 MP cameras into perspective indeed. Not only have I been weary of these cameras’ sensor sizes, but now let's look at their bit rate capacities. Bits per frame isn't linear over increasing resolution (from the chart Hikvision published you can see this). But taking the amount of increase over resolution seen on that chart, we can estimate that a 10 MP camera would be suggested to run 1190 Kbits sec for each frame sec. At 6 FPS (an unacceptable frame rate), you see that required Kbps to get best quality video is 7140 Kbits per second. Do the math and see how 15 FPS would require 17,850 Kbits per second (2.18 MB of data written every second). Wow, and that is only the main stream of data. Your network will see more to accommodate the secondary substream. You would be writing 7.6 Gigabytes per hour to have a 10MP camera running best quality with the appropriate bit rate set to 17,850 Kbps to accommodate 15 FPS (that is if any present-day 10MP camera could even do 15FPS). Just to top this off - to answer the OP's original question: "How much space in a 24 hour priod for a 10MP camera", let me answer it in a much more calculated way: I would recommended running the 10MP at 7140Kbps to get the best video quality at 6 FPS (the max FPS capability of that camera). In a 24 hour period this would result in 616,896,000 Kbits of data written. That converts to 73.53 Gigabytes.

I would really like to see a demo of these units at night. Something tells me the sensors are not going to be adequately sized for 12MP. Even their 10MP cameras only have a 1/2.3 CMOS. I am weary of low light. Maybe they will have something like Hikvison's EXIR.

These use cases sound reasonable. With audio recording due diligence by the installer / owner of the security system must be performed to verify the legality / requirements. For example, if I were to install audio recording on my property I would be subject to the requirement to post notice to all persons entering the property that audio recording devices are in use. I am not saying audio recording is illegal. I am only warning about the need to understand that it is a different animal (legal wise) than video.

Here are pictures of the back fence camera installation:

8192 kbps works out to 88GB/day for CBR continuous recording. Resolution and frame rate don't matter, only the bit rate. One important consideration for MP choices is the increase in linear resolution, not area resolution. Going from 1080p (1920x1080, 2.1MP) to 10MP (3648x2736, 10MP) looks like a 5x resolution increase, but what most people care about is linear resolution, as it's pixels per foot (or whatever) that makes the difference. 10MP gives a 1.9x (horizontal) and 2.5x (vertical) increase in linear resolution, so going from 1080p to 10MP basically gives you a 2x better image when it comes to identifying details, assuming the image quality is just as good at the higher resolution (which it isn't on the E77). 2MP/3MP is the sweet spot in price/performance right now if you don't specifically need the higher resolution. Thanks! That makes sense. As you can see from my ball park I did exactly that - assumed 5x (which got me close considering 88*5=440)

Here is a copy / paste from another thread where I had this to say: If you are in the United States, you may wish to become familiar with wiretapping laws, Electronic Surveillance with audio, Eavesdropping laws, the Electronic Communication Privacy Act (ECPA) of 1986, and the Fourth Amendment or other laws within your particular jurisdiction... For example, if you do not clearly post notice of AUDIO monitoring and recording, consider if you might jeopardize yourself attempting to use such evidence in court. I know these cameras are being sold with mics, but be careful. I do not think people understand the serious legal issues presented once audio recording is introduced.

So you can see from the analysis, the total Bytes per second for each camera represent the total throughput from the IP camera's two streams (both Main and Sub Stream). Remember, on the camera configuration screen the streams' bit rates are defined as bits per second (not Bytes). You will note when I had my client set to Visualization Profile for all cameras, that was essentially taking a gauge of the total bandwidth for all cameras' substream settings at once (equaling about 4 MB per second) while the other client, the X60, shows you the demand for seeing four channels of substream at once (about 1 MB per second). Compare that to when I placed my client on Recording Profile for all cameras (this is the Main Stream feed from the cams). You can see the bandwidth demand on all 13 came to a total of about 11.2 MB per second. That is about three times more than the all substream demand. So you might be safe to say that a single 2MP camera shown at 1.3MB per second is comprised of a Mainstream feed of about 1 Megabyte per second and a substream feed of 336 Kilobytes per second (with my configuration settings). To recap: the total B/sec seen on the network activity represents both sub and main stream. Selecting the stream to view from your client will determine which portion of that bandwidth is sent for for remote viewing. You can set your mainstream up for recording high and your substream lower to accommodate remote or mobile viewing if you need to. I am not suggesting you use my substream settings. I have mine set this way specifically because I utilize the substream on my NVR for analytics. I am providing this only as an example to explain how this works. Additionally, I have somewhat different internet speed than you:

Here is the network utilization as the result:

Maybe this helps. I hope so, it took me about 30 minutes to get these screen shots and info put together. Here is the way I have my cameras configured and this is the network utilization result. At this time I have ten 2MP Dahua (the 11th one is not being used right now), two 3MP Hikvision, and one VGA SunEyez Glorified baby monitor:

Compression on my mind... What I meant was analytics. With good analytics capabilities, continuous recording would not be needed. For example: Face detection, motion detection, object detection, loitering detection, ANPR, counting, etc... Not knowing the intended use of this camera, we cannot make the determination that 6 FPS is going to be more than enough. Every camera has to be implemented and adjusted for the particular purpose it serves. A 6 FPS limitation is a deal breaker, sorry. Think about the times you've played back at 1/8th. 1/16th, or 1/32 speed trying to get that perfect shot. Another item not mentioned is sensor size. I know it has nothing to do with storage, but I do not trust that 10MP across a 1/2.3" sensor is adequate for good low light (but I also have not ever seen or used this camera). In reality that isn't that much larger of a sensor than a 1/3.2. I am just throwing that out there as a consideration. Maybe you have some info on that to share with the OP. I would suspect anything in 10MP would need to be full frame and if not at least a 1" sensor (to get similar low light performance of a 2MP 1/3" camera). Again, this would come down to the intended use of the camera. With a slow enough shutter I am sure the image will come out. The problem would be the motion blur. I guess I'm just trying to talk him out of the 10MP camera. What do you think?

Why buy a 10MP camera and not maximize the bit rate? Storage is cheap. As for the frame rate on your 10MP camera... 6 FPS is not going to be very good for many situations. If there is any moderate speed action (jogging, bicycle, etc) or fast action like traffic, 6 FPS is not enough to get that "good shot" when you're going to need it. You will miss a lot of action between frames. That action could be someone's face. I am going to ballpark this with no calculator. 10MP cam at 8192 kbps 6 FPS for a 24 hour period......... 500GB per day continuous recording. (this is a complete but calculated guess). Another factor that has not yet been mentioned is your NVR solution and its compression capabilities. I would no get a 10MP camera right now. NVRs, storage, bandwidth, camera capabilties, etc are not there yet. 3MP is great.

I run my two 3MP cams at 8192, eleven 2MP cams at 8192, and another VGA wireless PT camera at something else (who knows - it is a glorified baby cam). The two 3MP cams run at 20FPS (they're used for ANPR with 12mm lenses and a min of 1/1000 shutter on a residential - up to 30 MPH street). Two of the eleven 2MP cameras run at 20 fps while all of the other run at 15 fps. Point is I can run all of that on continuous recording and I get just short of two weeks of footage. I have 10 TB dedicated to my NVR server. I personally think the bit rate should always be maxed.

Here is one of the my two spare Dahua IPC-HDB3200C domes that ended up being displaced after all of the camera rearranging. The lens swap on these is super simple. I ran Cat5e underground to the back fence along with some 12v DC power. The camera is POE, so the 12V is to run two IR illuminators. But wait.... the IPC-HDB3200C isn't a Day/Night mechanical IR cut camera. Well, this would not be the first time I ran one of these with no IR filter on the M12 lens. I thought it would be kind of cool to have just a general overview camera on my back fence (that faces the man blvd of the neighborhood). To get the most view I went ahead and placed an F1.4 2.8mm non IR cut lens in it. I am really impressed with the lens too. I purchased it from Aliexpress and I have to say this is a very nice lens. As for the IR illuminators, I got those on Aliexpress as well. I have never had any luck with any of the IR illuminators I purchased from that site. I am sure these two will last about 3 months before they die. I have two mounted above the camera pointed about 90 degrees off of each other. The 2.8 is so wide the boundary of the IR illuminators is shown now. Before, with a 3.6, this did not happen. Yes the color is weird during the day, but this is no more than a cool factor camera for me anyway. Here is a shot of the camera in the day and at night.

If you are in the United States, you may wish to become familiar with wiretapping laws, Electronic Surveillance with audio, Eavesdropping laws, the Electronic Communication Privacy Act (ECPA) of 1986, and the Fourth Amendment or other laws within your particular jurisdiction... For example, if you do not clearly post notice of AUDIO monitoring and recording, consider if you might jeopardize yourself attempting to use such evidence in court. I know these cameras are being sold with mics, but be careful. I do not think people understand the serious legal issues presented once audio recording is introduced.

I will report that the General_IPC-HX3(2)XXX_Eng_N_V2.212 greatly improves IR performance and noise reduction on the IPC-HFW3200S 2 Megapixel Full HD Network Small IR-Bullet Camera! Wow, what a difference from the former 2.210 firmware I had running. I also started to apply this firmware to all of my IPC-HDB3200C 2 Megapixel Full HD Vandal-proof Network Mini Dome Cameras. The result here is faster response time through the browser and great (as if it was not before) FireFox compatibilty! I also think the WDR settings work better and light sensitivity is better. Is there a PDF to the General_IPC-HX3(2)XXX_Eng_N_V2.212 firmware detailing the changes?

I am confused on what the problem is. I do not see a problem. In all of the PTZ's I have seen, digital zoom is configured to either be on or off and takes over after optical is maxed. I have also seen the ability to configure the limit on digital zoom once it kicks in. Is the limitation in your NVR or is there no NVR / client software even involved (are you using only the camera's web client on a large format monitor connected to a compuetr running a browser). Are you saying your current limitation is in your current camera's or NVR's handling of the PTZ control? Get the higher resolution PTZ and enable digital zoom if you even need to (or just buy a PTZ with adequate optical zoom like to Dahua SD6982A/82C-HN with 30x optical zoom). http://www.dahuasecurity.com/products/sd6982a82c-hn-306.html My friend has a couple of these Dahua PTZs. They are amazing. The thing is - buy the right camera with the best resolution, optics, DSP, and IR that you can justify paying the price for. This all matters. Don't harp on the monitor you're currently utilizing. It will perform its job just fine and putting a higher quality camera in means better data in. One day that display you're currently utilizing is going to break or you will eventually replace it. In fact considering the price of a PTZ like this, why would you not replace the monitor? These days you can buy a 60" LCD 1080P display for half the price of this PTZ. Thanks, Jeff

Let me assure you, compared to an inexpensive 3 LED array illuminator, the two EXIR leds on the Hikvision will put out 10 to 15 times more IR light. I am in no way exaggerating. I've had several 3, 4, and 6 IR array illuminators (the inexpensive type) and I have put them all up against the EXIR. The most recent test was some new 6 array illuminators that I was really hoping would work well. The two EXIR leds were at least 5 times brighter. It is no comparison. I have seen this same type of incredible IR array performance on $1500 Dahua PTZs. I also have a suspicion the lens of the EXIR array is specifically designed for the model / focal length of the camera. One important thing to understand about arrays is the array itself is covered with a lens to control the spread / concentration of the light.

That is not my living room. The network home run, that piece of furniture I built, the cabinet containing the switch, server, modem, UPS, etc is our music / piano room (former, formal living). Additionally the cabinet stays closed, the switch fans are PWM (regulated speed / thermally managed), the exhaust fan at the top of the cabinet (behind the TV under the surface the TV sits on), is silent.