MikeLud1
IPCT Contributor
I am not seeing any ghosting on my IPC-HFW5241E-Z12E. I am on the below firmware.
Settings for IPC-HFW5241E-Z12E
- Thread starter rfj
- Start date
Flintstone61
Known around here
1/4000 switch today. From 1/10000, which was a bit too dark.
My camera is not subject to the vehicle speeds you guys have.
Im getting the Information for the Po-Po so they will come and take a report and give me a case #. That is the camera’s only mission.
My camera is not subject to the vehicle speeds you guys have.
Im getting the Information for the Po-Po so they will come and take a report and give me a case #. That is the camera’s only mission.
Last edited:
Flintstone61
Known around here
Sunset is at like 8:50-8:55.
9:33 and 8:25 images we still had twilight and some ghost trails,,,the 10:43 shot looks better.
But fugget. I'm getting data.
9:33 and 8:25 images we still had twilight and some ghost trails,,,the 10:43 shot looks better.
But fugget. I'm getting data.
MikeLud1
IPCT Contributor
The older 5241 was closer to the 5231. My neighbor has a 5241 from one of the firsts batches and you cannot tell the difference between his 5241 and my 5231.
The newer Z12s use a different chipset than the previous ones and the settings on my recent one I got are completely different from my older 5231-Z12 or neighbors 5241-Z12 settings (that are using my identical 5231 settings).
There are differences in the hardware/chipset between an older 5241-Z12 and a newer 5241-Z12 - probably a result of chip vendor changes. My 5241 has a build date of October 2020. My neighbors 5241-Z12 had a build date of October 2019. The settings are completely different between the two looking at the same spot. I set his up and had placed it next to mine to see if there were any differences.
The newer Z12s use a different chipset than the previous ones and the settings on my recent one I got are completely different from my older 5231-Z12 or neighbors 5241-Z12 settings (that are using my identical 5231 settings).
There are differences in the hardware/chipset between an older 5241-Z12 and a newer 5241-Z12 - probably a result of chip vendor changes. My 5241 has a build date of October 2020. My neighbors 5241-Z12 had a build date of October 2019. The settings are completely different between the two looking at the same spot. I set his up and had placed it next to mine to see if there were any differences.
MikeLud1
IPCT Contributor
bigredfish
Known around here
Exactly
Didn’t mean to sound like a whiny little bitch, just very noticeable vs the 5231 and original 5241’s that I had installed in the past.
I am getting some poor caps intermingled with the good ones. My gut and past experience say it’s not enough IR, I’ll test the next few days and post results. Forgot I have that huge IR laser blaster PTZ mounted on same pole, so I’ll use it to A/B test with
My build dates are Oct 2019 and March 2020.
Firmware on both is V2.800.0000000.22.R, Build Date: 2020-11-19
Firmware on both is V2.800.0000000.22.R, Build Date: 2020-11-19
Flintstone61
Known around here
bigredfish
Known around here
You are right @wittaj Getting good captures for the most part,
....but even with the PTZ laser IR, weird ghost trails...
View attachment HOA Entr_ch3_20220601222730_20220601222745.mp4
....but even with the PTZ laser IR, weird ghost trails...
View attachment HOA Entr_ch3_20220601222730_20220601222745.mp4
Last edited:
bigredfish
Known around here
^^ Where did you get that firmware? I have only seen these 150G00A firmware coming from Andy as beta fixes for things that wildcat reported. All of my firmware on all 21 Dahua cams are 0000000 versions, like V2.800.0000000.22.R or V2.800.0000000.16.R or even 2.622.0000000.7.R.R4.383
bigredfish
Known around here
Came with it from Andy.
That said it was shipped from his PA guy so it may well have been a return that they refurbished? Had some hints of being previously played with but hard to say.
As you can see from the caps it works fine and I’m pleased, I think @wittaj is right that there are differences in the chipset between older and newer models. I’d just never seen trails like that I couldn’t get rid of.
That said it was shipped from his PA guy so it may well have been a return that they refurbished? Had some hints of being previously played with but hard to say.
As you can see from the caps it works fine and I’m pleased, I think @wittaj is right that there are differences in the chipset between older and newer models. I’d just never seen trails like that I couldn’t get rid of.
Futaba
Pulling my weight
- Nov 13, 2015
- 227
- 168
Just received my 5241 from Andy shipped from USA. This is the firmware it comes with:
@samplenhold thanks for your screen shots. They make it very easy for my first round of setup.
@samplenhold thanks for your screen shots. They make it very easy for my first round of setup.
Futaba
Pulling my weight
- Nov 13, 2015
- 227
- 168
After a week or two, I think I have my LPR cam tuned to get good captures. I had ghost trails earlier but with my latest settings it is gone. I don't know what change made it go away. Maybe it is the increased contrast.
I am in a cue-de-sac and I don't get cars drive by often after dark. Especially now the days are longer, it is hard to see a recent capture, see what is wrong with it, and then make some changes, rinse and repeat. Getting focus right was the first problem. I started parking my own car out on the street and run back home to make changes, then run back to move the car, drive around... I got sick of that. So...
Took my phone and iPad out to the car. Had my iPad tethered to the phone for Internet (home wifi is too far). Then VPN back to home network, remote desktop into the virtual machine I use to run Internet Explorer. Now I can tune the camera's settings in real time. After I made some changes, I drove around the circle to get a trigger, looked at the capture, and tuned again.
It went from this a few days earlier:
To this:
Within 30 mins of tuning.
Biggest changes I made were increased contrast from 50 to 60, lowered shutter from 1/2000 to 1/1000 and increased gain 75 for the high number to get a brighter image, and zeroed out Advanced 2D (not sure if this is needed).
Thanks to y'all's help and advice!
I am in a cue-de-sac and I don't get cars drive by often after dark. Especially now the days are longer, it is hard to see a recent capture, see what is wrong with it, and then make some changes, rinse and repeat. Getting focus right was the first problem. I started parking my own car out on the street and run back home to make changes, then run back to move the car, drive around... I got sick of that. So...
Took my phone and iPad out to the car. Had my iPad tethered to the phone for Internet (home wifi is too far). Then VPN back to home network, remote desktop into the virtual machine I use to run Internet Explorer. Now I can tune the camera's settings in real time. After I made some changes, I drove around the circle to get a trigger, looked at the capture, and tuned again.
It went from this a few days earlier:
To this:
Within 30 mins of tuning.
Biggest changes I made were increased contrast from 50 to 60, lowered shutter from 1/2000 to 1/1000 and increased gain 75 for the high number to get a brighter image, and zeroed out Advanced 2D (not sure if this is needed).
Thanks to y'all's help and advice!
Last edited:
bigredfish
Known around here
Congrats! Looks good.
You may play a little with Gain vs Iris. It’s a give and take. Reduce gain buy increments if 5 and increase Iris same, might get rid of that last bit of graininess, but hey looks good.
You can usually get away with 1/1000 if they’re moving slow, say under 20. I have one that I run that on and it works fine.
Great job!
You may play a little with Gain vs Iris. It’s a give and take. Reduce gain buy increments if 5 and increase Iris same, might get rid of that last bit of graininess, but hey looks good.
You can usually get away with 1/1000 if they’re moving slow, say under 20. I have one that I run that on and it works fine.
Great job!