DS-7604NI-E1/4P Help

I don't understand, I have a dual intel nic card and motherboard nic. I have the motherboard nic set up in the picture. and tha cable from NVR plugged into it.

my internet is on the intel nic. I don't know know wher the 127..1 is coming from. is the gateway wrong? please help.
 
Your PC is not using the required 192.0.0.128 IP address.
If you check your tftp updater screenshot - it's using 'localhost' on 127.0.0.1
Do you have WiFi enabled, is the PC wired to your router / switch?

That is not always the case. There are times where even changing the NIC's IP to 192.0.0.128, the TFTP updater visibly does not change the address its allegedly listening on, (it's also capable of listening on multiple NICs) yet it really is listening on 192.0.0.128. Even with that being the case, the NVR needs a serial connection to forcefully invoke the recovery process. He's setting everything up the way you would do it with an IP camera. But as I described in another thread, the NVR isn't going to look for a TFTP server unless the flash is corrupted or is serially invoked. Neither of which are true in his case. Since this is a 7600, TTL is required.
 
Is your NVR inaccessible? Why exactly are you using TFTP? Upgrades should be done through the web interface, or copying digicap.dav to a flash drive and performed directly on the NVR from the maintenance menu. TFTP is generally for recovery/last ditch effort/OMG HALP! Scenarios.


Sent from my iPhone using Tapatalk
 
I used the wrong update, I did you usb did you see the gibberish for password? I tried several times with usb.

I am still not 100% sure what firmware to use because I am getting different answers. why am I getting 127.0.0.1 it's pinging the nic?
 
I don't understand, I have a dual intel nic card and motherboard nic. I have the motherboard nic set up in the picture. and tha cable from NVR plugged into it.
3 NICs? Despite the Hikvision instructions saying that directly wiring the NVR and PC is the way to do the update - several posts have reported problem when doing this.
It definitely works best when both are wired as normal to your switch or router. And it does not have a configuration to specify which interface it's bound to, so you may just have to experiment with which interface it picks when it runs.

But as I described in another thread, the NVR isn't going to look for a TFTP server unless the flash is corrupted or is serially invoked.
Whilst agreeing that the serial console update method is much more convenient, and preferable if you have the USB-TTL serial interface and cabling - it saves messing with IP address settings, I've used it maybe into 3 figures - the classic Hikvision tftp update method still works just fine on my 7816s even when they are running perfectly functional firmware.
 
The NVR is going to reject the firmware if it's wrong typically. I've had this happen on many occasions and it has saved me.

Back with early versions of 3.x.x, (pre-3.3.x) upgrading to later versions of 3.x.x (3.3.x+) would cause the NVR to scramble up the login information. On 7700s, the workaround was to use 3.1.7 as intermediary firmware, then upgrade to the latest version. This prevented the lockup from happening. In my case, this worked 100% of the time provided you factory reset before doing anything.

In the case of the 7600, that was not a viable option as it would still brick. However, I recently upgraded a 7600 from 3.0.3 to 3.4.2 and while it did scramble up the login information, it at least let me go into settings to perform a factory reset. That took care of everything in 2 steps, no TTL required.

Moral to the story, you may not have flashed the wrong firmware, it may have simply just been a fluke much like the ones I described. In any case, if no matter what it won't let you in, then a USB-TTL adapter and some soldering (UART connector can help you avoid soldering, I could never find one) may be required to recover it.

This is the correct firmware:
http://www.hikvisioneurope.com/port...) 7700NI-E4/V3.4.6 build160405 Multi-lingual/

Why does your computer have 3 NICs? While I've successfully had the TFTP tool work on wifi and Ethernet simultaneously, by no means do I recommend it. Unhook 2 or disable them until your sort this out. Don't make yourself more problems than you already have.


Sent from my iPhone using Tapatalk
 
3 NICs? Despite the Hikvision instructions saying that directly wiring the NVR and PC is the way to do the update - several posts have reported problem when doing this.
It definitely works best when both are wired as normal to your switch or router. And it does not have a configuration to specify which interface it's bound to, so you may just have to experiment with which interface it picks when it runs.


Whilst agreeing that the serial console update method is much more convenient, and preferable if you have the USB-TTL serial interface and cabling - it saves messing with IP address settings, I've used it maybe into 3 figures - the classic Hikvision tftp update method still works just fine on my 7816s even when they are running perfectly functional firmware.

Perhaps the 7800s are different, but in countless cases I've tried the standard TFTP method with 7600 and 7700 models with no luck. Similar errors as to what he posted. You're right though, serial is much more reliable.
 
Perhaps the 7800s are different, but in countless cases I've tried the standard TFTP method with 7600 and 7700 models with no luck. Similar errors as to what he posted. You're right though, serial is much more reliable.

I kept at it, reset NVR to Factory Defaults then updateded firmware with DS-76xxNI-E1(E2)P/DS-76xxNI-E1(E2)P_USA_Firmware_V3.3.6_151229

Everything looks ok and this firmware is displayed when logged in.

I have no lower case letters when setting a password and no shut down or reboot options in the menu. I updated with usb.
 
So you solved your problem? ☺️ do you need more help?

Sent from my A0001 using Tapatalk



USB-TTL serial interface and cabling, where can I read about this method? Can a serial cable to serial ports

from NVR to PC work, is TFTP still used with serial method?
 
Many embedded Linux devices support a 'serial console' for debugging purposes. Hikvision cameras and NVRs are no exception.
To access it you can use an RS-232 to 'TTL level' serial to USB convertor.
Normal RS-232 signal are bipolar, 3 - 15v, but with the 3.3v powered circuitry on many small board computers the signal levels are unipolar and similar to classical 'TTL' voltage levels, hence the terminology.
Here is a good exemple posted by @snikinl https://www.ipcamtalk.com/showthrea...kvision-DS-2CD2032F-I?highlight=serial+manual
 
Last edited by a moderator:
If it says HIKVISION, it's US. if it's in Chinese characters, well, obviously, it's Chinese. Very simple.


Sent from my iPhone using Tapatalk
 
The NVR is going to reject the firmware if it's wrong typically. I've had this happen on many occasions and it has saved me.

Back with early versions of 3.x.x, (pre-3.3.x) upgrading to later versions of 3.x.x (3.3.x+) would cause the NVR to scramble up the login information. On 7700s, the workaround was to use 3.1.7 as intermediary firmware, then upgrade to the latest version. This prevented the lockup from happening. In my case, this worked 100% of the time provided you factory reset before doing anything.

In the case of the 7600, that was not a viable option as it would still brick. However, I recently upgraded a 7600 from 3.0.3 to 3.4.2 and while it did scramble up the login information, it at least let me go into settings to perform a factory reset. That took care of everything in 2 steps, no TTL required.

Moral to the story, you may not have flashed the wrong firmware, it may have simply just been a fluke much like the ones I described. In any case, if no matter what it won't let you in, then a USB-TTL adapter and some soldering (UART connector can help you avoid soldering, I could never find one) may be required to recover it.

This is the correct firmware:
http://www.hikvisioneurope.com/port...) 7700NI-E4/V3.4.6 build160405 Multi-lingual/

Why does your computer have 3 NICs? While I've successfully had the TFTP tool work on wifi and Ethernet simultaneously, by no means do I recommend it. Unhook 2 or disable them until your sort this out. Don't make yourself more problems than you already have.


Sent from my iPhone using Tapatalk

I ordered the parts from the ttl post, but it's like giving a cow a hammer...what is the procedure, what software communicates with nvr? any videos available?