Mini-Review EmpireTech IPC-Color4M-T
- Thread starter wittaj
- Start date
Just checked and the settings you mentioned were already set at is.
Audio was enabled, One click disarm enabled, disarm by period disabled.
Edit: not sure why I can't post an attachment but take my word for it, those settings were as you mentioned.
Last edited:
It has been noted in several threads here that for some reason we can't attach photos, which is unfortunate as they tell so much and help tremendously with troubleshooting!
from some time drag & drop for images didn't work - but I was thinking this is forum vs Mac/safari problem..
I used attach files button - this worked..
but now I see even Attach files button don't work.
probably the HDD space ended on the server.. especially for directory used to file upload...
I expect as you have suggested. That your NVR on the old firmware, is not capable of dealing with a camera with the features that are not functioning. Perhaps update the firmware if possible?
bigredfish
Known around here
That unit is EOL but that’s fine,
Last FW was Oct 2024 which is good
Make sure it’s your model
Drop down menu Firmware
Last FW was Oct 2024 which is good
Make sure it’s your model
Drop down menu Firmware
Last edited:
Does it matter if I grab the firmware from the link you provided or from EmpireTech’s website?
I'm sure the respected. "Bigredfish" has verified the link he provided is valid, to be appropriate.
bigredfish
Known around here
Not really. If its the same version.
Unless I'm aware of a specific enhancement that Andy has done, and tested, I'll typically use the Dahua Intl site FW
I have the same NVR, well almost, 5216-16P-4K2SE and mine uses the same FW
I'm at witts end now... tried both versions and they both failed to upgrade. Tried updating thru configtool as well as USB. Went thru the upgrade process and at the end it resets my NVR. No visual update look and no updated version number after re setting up. 
Looks like it might be bricked. Freakin frustrated now.
Looks like it might be bricked. Freakin frustrated now.
Last edited:
I don't remember details as it was years ago. There was one point where you couldn't directly upgrade from an older version to a new one without going through an intermediate version first. I think this came into play if the current firmware was one of the V3 versions. Just throwing this out as a possibility, and hoping one of the members who know how to un-brick can help.
Another major issue is if you have a V1 or V2 5216-4ks2. My understanding is the latest firmware will not run on V1 hardware. How do you tell? If your old firmware was V4 (the newer GUI), one of the info pages would have told you. Can't go back and look now of course. Again from tortured memory, the model # sticker on the bottom of the NVR says it's V2 if it's V2, and gives no version # if it's V1. There's a version discussion here:
NVR5XXX-4KS2_MultiLang_ V4.001.0000003.2.R.201010
Besides the first post, also look at post #13 where I gave a specific version # for V1 hardware.
Another major issue is if you have a V1 or V2 5216-4ks2. My understanding is the latest firmware will not run on V1 hardware. How do you tell? If your old firmware was V4 (the newer GUI), one of the info pages would have told you. Can't go back and look now of course. Again from tortured memory, the model # sticker on the bottom of the NVR says it's V2 if it's V2, and gives no version # if it's V1. There's a version discussion here:
NVR5XXX-4KS2_MultiLang_ V4.001.0000003.2.R.201010
Besides the first post, also look at post #13 where I gave a specific version # for V1 hardware.
bigredfish
Known around here
I'm at witts end now... tried both versions and they both failed to upgrade. Tried updating thru configtool as well as USB. Went thru the upgrade process and at the end it resets my NVR. No visual update look and no updated version number after re setting up.
WHy do you think its bricked?
Are you logging into the NVR via its web GUI using a browser on a PC and going to its IP address? You should be
Well shit. Just my luck.
I took a picture beforehand of my version number in the GUI and it says:
System Version: 3.210.0002.2
Build Date: 07-21-2016
To those who actually need help with the Color4M-T camera I apologize for hijacking this thread. This all kinda went from one thing to another.
It's my best guess, honestly.
I am logging into the NVR, not from the web gui, but from the NVR software itself. I re-setup from the wizard, start adding cameras again (because they were all removed), and the screen freezes. I can't do anything. The NVR eventually force restarts. The cycle continues.
Hopefully somebody can get you back to a running V3. Wish it was me, but it's not. If you're able to get back up you can go at least to a mid-life v4 version like I'm running. I think a 2016 machine is surely V1 hardware, but that's only a semi-educated guess.
bigredfish
Known around here
It's my best guess, honestly.
I am logging into the NVR, not from the web gui, but from the NVR software itself. I re-setup from the wizard, start adding cameras again (because they were all removed), and the screen freezes. I can't do anything. The NVR eventually force restarts. The cycle continues.
You should use the Web GUI with a browser. And do one at a time. Each camera on a remote switch if new will default to the same IP number 192.168.1.108 and create IP conflicts. Each will need to be changed before adding another.
What is the IP of your NVR? it ould be default 192.168.1.108 also and thus the IP conflict and bad stuff happening
And yes seeing where this is going it would be best for you to open a new thread.
bigredfish
Known around here
It's my best guess, honestly.
I am logging into the NVR, not from the web gui, but from the NVR software itself. I re-setup from the wizard, start adding cameras again (because they were all removed), and the screen freezes. I can't do anything. The NVR eventually force restarts. The cycle continues.
Its not bricked if you can login
The NVR always defaults to 192.168.1.108.
My cameras have remained unchanged. Thankfully.