Review-EmpireTech IPC-B52IR-X3 1/2.8" CMOS 3 × 2 MP bullet cam

Well its 3.6mm which is what I use at most of my entrances.

Remember this is a 2MP camera and all 3 lenses face the exact same direction. It would need to be mounted pretty low otherwise you would get a reasonable image of your entryway with the near lens, and up close shots of your sidewalk concrete grain with the other two
 
Yep problem isn't the camera. Mine works just fine in BI.

It is likely a network bottleneck that BI is detecting.

Or insufficiently powering the camera - ironically I have seen when a POE port is failing because those errors start popping up. When I changed power, the error went away.
Thanks for pointing me to the network bottleneck. I pinged the cam and noticed the pings jump from 64 to 65. Consistent with the stutters.

Was using built in pc nic, swapped to the spare on the dual nic and it's like a floodgate was opened. I should've done it from the start, but I figured the cams wouldnt need a super fast port.

Appreciate you and bigredfish for the quick help
 
Well its 3.6mm which is what I use at most of my entrances.

Remember this is a 2MP camera and all 3 lenses face the exact same direction. It would need to be mounted pretty low otherwise you would get a reasonable image of your entryway with the near lens, and up close shots of your sidewalk concrete grain with the other two
Good call. Makes sense. That’s what I want sure of is if there was any lens shifting.
 
Good call. Makes sense. That’s what I want sure of is if there was any lens shifting.

There is lens shifting up and down within the camera GUI, but all 3 move at the same rate, so you can't make one move up and one down, etc.
 
This one arrived this evening. No surprise, it's a good bit larger than a turret, but nowhere near as large as so many PTZ units. What surprised me most was the surplus of wires coming from the camera. One RJ-45 Ethernet jack, two RCA-phono-style jacks for Audio In and Audio Out, another two-conductor with connectors for 12VDC Out, and what appears to be (I haven't grabbed my glasses and magnifier to read the incredibly tiny type) Ethernet/RJ-45 signals? I'd read the included manual to find out for certain, but it's text is rather small, as well.
 
  • Like
Reactions: bigredfish
ANNNNNNDDDDDDDD . . . While the password set facility allows the use of '&' ampersand characters in passwords, the HTML web GUI and login screen FAILS to accept a password containing an ampersand. One bug report, coming up. @EMPIRETECANDY Please communicate this issue to your contacts at Dahua?
 
  • Like
Reactions: EMPIRETECANDY
ANNNNNNDDDDDDDD . . . While the password set facility allows the use of '&' ampersand characters in passwords, the HTML web GUI and login screen FAILS to accept a password containing an ampersand. One bug report, coming up. @EMPIRETECANDY Please communicate this issue to your contacts at Dahua?
Hey buddy, which firmware you are using now, i am checking with them if have a newer fw to release.
 
  • Love
Reactions: VorlonFrog
Hey buddy, which firmware you are using now, i am checking with them if have a newer fw to release.
Wow, what a FAST reply!! :wave: Thank you, Andy. I don't have the camera online right now, but will let you know as soon as it's alive again. THANK YOU!!!

Okay, got it cabled up, here'sall the firmware version information:

ONVIF Version 23.12(V3.1.0.1921813)
System Version V3.142.0000000.1.R, Build Date: 2024-08-01
Web Version V5.01.0.1983768
Algorithm Version V4.7.25.0
Security Baseline Version V2.4
H5Player Version V3.01.1
Copyright 2024, all rights reserved.
 
Last edited:
Are you using BI?
Yes, and autodetection did not provide the profile strings / media paths. :(
Interestingly enough, when I forced the camera manufacturer to Dahua, it provided the URL/path.
/cam/realmonitor?channel={CAMNO}&subtype=0&authbasic={AUTH64}
 
Last edited:
You're not seeing this?
View attachment 225100

For the different channels, just change the channel number in the string. (1,2,3)
Thank you for those profile strings. Nope, autodetect did not provide these strings.
Here's the initial output from autodetect:

Opening 192.168.1.78 port 80...
HTTP Get / request...
OK
ONVIF GetSystemDateAndTime
2025-07-22T23:31:44.000Z
Requesting device information...
Invalid response. Is the password correct? (actually, yes, it is correct)
GetCapabilities...
Querying services
Has Imaging services: /onvif/imaging_service
Has media services: /onvif/media_service
Has RTP_RTSP_TCP, requesting profiles
Has Event services: /onvif/event_service

I think I figured out the problem. I did not delete the previous camera, simply changed the password and IP address. I'll try deleting the camera altogether and re-adding it. Nope, something about the autodetection doesn't seem to be working properly.
 
Last edited:
That is the problem- your ONVIF password is wrong, or rather the camera thinks it is wrong. That can happen if you changed password or it corrupted.

Their are two user and passwords.

Go to account and go to ONVIF manager and change the admin password to the current password, or create a new user and password.
 
  • Like
Reactions: VorlonFrog
It apparently has some default password set for the Onvif user 'admin' and I cannot change it without that original password. Kinda frustrating... It also will not allow deleting the admin Onvif user. Guess I'll try setting up another username in the Onvif tab. Yup, that did it. Created an 'admin2' Onvif account, used that for autodetect, and the Onvif profile strings appeared. It seems this camera firmware is extremely half-baked and not-quite-ready-for-prime-time.
 
Last edited:
is the zoomed version of this able to license plates, or not the intension in this application? I have an idea where I may use this to shoot down my drive, wide captures more yard and all, but as it zooms down it captures the mailbox, etc However, angle slightly and i capture every car driving by... just a thought