trouble initializing new Empire Tech EmpireTech IPC-T54IR-ZE-S3 - IP segment, etc.

Feb 5, 2024
16
5
United States
So like most home networks, mine uses 0 in the third octet, and so of course I can't log in to my new Empire tech camera which defaults to 1in that slot.

I found Andy's you-tube video on this, which recommends downloading the Dahua ipconfig took. Problem is that Windows doesn't trust the download file and I guess I don't either.

I have the Amcrest IP config tool, and I used it to located the dahua camara but I don't see an edit button, so I don't know if it has the same functionality to change the IP. Can anyone help?
 
Easiest way, connect a lan cable from your PC > Camera (power the camera via power cable if you have one) set a static IP address of your PC to be 192.168.1.10 subnet 255.255.255.0 then go into web browser and type 192.168.1.108 and you should hit your cameras login page.
1722502877514.png

From there set the ip address of the camera to your range 192.168.0.x (remember what you set it too) revert your changes you made above back to Obtain an IP automatically plug everything back in as it was before and you should now be able to access your camera on your network.
 
Easiest way, connect a lan cable from your PC > Camera (power the camera via power cable if you have one) set a static IP address of your PC to be 192.168.1.10 subnet 255.255.255.0 then go into web browser and type 192.168.1.108 and you should hit your cameras login page.
View attachment 200035

From there set the ip address of the camera to your range 192.168.0.x (remember what you set it too) revert your changes you made above back to Obtain an IP automatically plug everything back in as it was before and you should now be able to access your camera on your network.
If you don't have an external power supply for the camera, but do have a POE(+) switch or a POE+ power injector, put that between the computer and camera. That will give you both network and power for the camera connection.
 
+1 to all the above but I might add this: Make the IP for the new camera unique, static and outside of the router's DHCP pool. :cool:

If you don't know what that DHCP pool range is, you can log into the router's webGUI with a browser using the router's LAN/gateway IP. If the DHCP pool range is, say 192.168.0.2 to 192.168.0. 199, you can choose a unique (not already used) static IP for the cam between 192.168.0.200 and 192.168.0.255.

That DHCP pool range (beginning IP to ending IP) can also be changed by YOU to suit your needs if so desired but generally not required.
 
Last edited:
It worked. Now I just gotta figure out why my BI rig keeps shutting down

If you mean the PC running BI is shutting down that is a whole different fault finding session. You could start quick and easy, look at the event log for reason why it is shutting down and move from there, check strange processes running, check AV.. Check thermal paste on processor and fan etc.
If just the BI is crashed on the PC, check you have the most recent stable version is installed, check your drivers (video) are up to date...etc again event log is your friend (could be memory issues, memory leakage) but these are all fault finding tricks and tips
 
  • Like
Reactions: TonyR
It worked. Now I just gotta figure out why my BI rig keeps shutting down

I spent months trying to track down the cause of my BI PC shutdowns. For me, it appeared to be thermal related, but it eventually turned out to be something related to the version of CodeProject I had installed.

I had been using CodeProject.AI.Server-2.1.9 and updating to CodeProject.AI-Server-2.6.5 stopped the shutdowns.

What does it show in your Window’s Event Viewer > Windows Logs around the time of your shutdown?