Help DVR Hybrid series DS-9016HFI-ST

kdelci

n3wb
Aug 3, 2016
10
1
Hello,


Hybrid DVR DS-9016HFI-ST (RS232 Serial Port integred).


I end up with a problem since an update.
The login list is empty, as if there were no more registered users.
No more means more users in the database.


I tried to connect the DVR with Hikvision tftp:
- Ip laptop: 192.0.0.68 / 255.255.255.0


I ping 192.0.0.64 and it responds well, do I start tftp.exe it connects and I have an error message:

TFTP server [192.0.0.128] initialized
Open file failure [C: \ TFTP \ econt_Vision-AV2000] failure
Connect customer success [192.0.0.64] Success
econt_Vision-AV2000 failure.


I connect a serial cable between my PC and the DVR I see nothing on the terminal.


I have access to the user web interface no longer exists, I have all tried.


This one week I'm going in circles.


Thank you for your help
 
  • Like
Reactions: Edison P. Rodriguez
TFTP server [192.0.0.128] initialized
Open file failure [C: \ TFTP \ econt_Vision-AV2000] failure
Connect customer success [192.0.0.64] Success
econt_Vision-AV2000 failure.
That's not a real failure and can be simply ignored.
When the DVR/NVR is almost fully started up, it send out probes on the network looking for the 3rd-part products it can be configured to use.
It just so happens that the (A)recont products are discoverable with a tftp broadcast - but this is picked up by the PC tftp server and treated as an error.
I hope that makes sense.

I connect a serial cable between my PC and the DVR I see nothing on the terminal.
Did you use 115,200baud, 8 bits no parity, no flow control for the serial port settings?

*edit* As the DVR is mostly started up - what if anything shows in SADP?
 
Hello thank you for the answer.


SADP captures well the DVR with IP 192.0.0.64 on port 8000.
For serial com 115200bauds configuration, 8 bits without control.


you say just ignore but how?
 
you say just ignore but how?
As I explained - it's not an error associated with the DVR.
It's the tftp server picking up the DVR probing for Arecontvision devices on the LAN and mistakenly complaining about the probe because it is not for it, it's for an Arecontvision device.
So it's OK to ignore it.

SADP captures well the DVR with IP 192.0.0.64 on port 8000.
The DVR is operating.
Do you get the same problem not being able to log in using the VGA/HDMI interface?

For serial com 115200bauds configuration, 8 bits without control.
As this isn't giving and responses it suggests it's not operating as a serial console.
 
Yes the DVR works but has big slowdown and VGA / HDMI's username was empty.
And I tested on another DS-9008HFI-ST model in operation and even Arecont problem with tftp.


So if it comes from the TFTP server (pc), I have to use another program that tftp Hikvision?


On the data sheet DS series9000 it is written:
1 RS-232 interface (for parameters configuration, maintenance, transparent channel);1 RS-485interface (for PTZ control);1 RS-485 keyboard interface (for special keyboard control)
 
To ignore it is necessary to do what? wait because this error after the transmisson of digicap file; dav does not make it blocks this error aercont
 
wait because this error after the transmisson of digicap file;
Your post does not show that digicap.dav has been transmitted.
Check your Windows firewall settings are allowing Inbound to tftpserver.exe (Firewall | Advanced settings | Inbound rules)
does not make it blocks this error aercont
This is not an error - it has nothing to do with the problem - it can be ignored.
 
To ignore it is necessary to do what? wait because this error after the transmisson of digicap file; dav does not make it blocks this error aercont

If you do have the right firmware; just try it a few times with Hikvision TFTP program. Maybe 10-20 times. I have also seen the damn Arecont_Vision_2000 crap with some old units, and it did end up working.
 
I tried several times without success.
Tomorrow I will use a RJ45 cable cross type, we will see what his situation.


I attached a picture below.


Sans titre.jpg
 
Hello back after several test, and always the same econt_Vision-AV2000.


I tried a connection directly right and crossover cable, I used a switch to connect the PC and DVR IP address 192.0.0.128 /255.255.255.0, answer ping 192.0.0.64 is ok. I have disable my firewall and restart several times the DVR.


I think this idea of abandoning this tftp DVR must be blocked or something for tftp.


There does it no other way to update a DVR other than through the TFTP?


Thank you for your help
 
There does it no other way to update a DVR other than through the TFTP?
Presumably the USB method is also broken with the inability to log in to access the menus via the VGA/HDMI interface.

If the NVR bootloader no longer has the tftp update capability, the next method will be by using the serial console connection.
If your RS232 port doesn't provide that capability, there is a serial console connector on the main board.
To use the connector on the main board you need 2 items -
USB to TTL serial convertor.
Search eBay or Amazon for PL2303 - plenty to choose from.
And the connector is usually something like this :
http://www.aliexpress.com/store/pro...d-Male-PCB-connector/1114121_1664241613.html#!
But worth checking your specific NVR.
 
20160818_181816.jpg20160818_181848.jpg

Thank you for the information.
but I do not understand however is the RS232 port on my DVR if it is useless?
In the description it is written RS232 port for maintenance and configuration?


On the circuit it s this white connector is composed of 6 pin
Thank you
 
but I do not understand however is the RS232 port on my DVR if it is useless?
This can be used for multiple purposes - but the purpose needs to be selected.
What I meant was that perhaps the mode=serial console may not have been selected.
But you can easily check by connecting to an RS232 comms program on your PC, trying 115,200baud, 8bits no parity and seeing if there is any activity.

On the circuit it s this white connector is composed of 6 pin
Usually it is a 4-pin connector, but I do not know for your DVR.
The picture is not clear.
 
That's a pretty good picture.
The 6-pin connector does look like a potential candidate - though, in my experience and others on this forum, so far it's been a 4-pin connector for both cameras and NVRs.
Presumably it will be easy enough to check out the RS232 port?
 
What software you use for establishing serial connection to the DVR? For example PuTTY 0.60 or 0.63 (this version has serial connection capability) will do the job perfectly.
Of course make sure you have a working Serial cable and a proper convertor USB->Serial in case you don't have integrated seral port on your PC. Attached you can find a manual for firmware upgrade, although is a little bit outdated (Ctrl+u to stop autoboot, and "u" to start upgrade process).
 

Attachments

  • Like
Reactions: alastairstevenson
Thank you I tested the voltage 5V and I have it is TTL, was not worth buying a converter I have a maxim max232 and a plate of electronic test I'll probably do it tonight and you stay current
 
To answer the question I am using hyperterminal software and putty in serial mode.
When do I start the DVR on the serial port I have nothing no activity,
alastairstevenson has probably reason may be that this serial port is used to send commands at last I know, but he does not speak.


I think this pin identified with a 5V TTL voltage is a good track.


I thank you prepare coffee. :)
 
Thank you I tested the voltage 5V and I have it is TTL
What did you test? Was it a signal level, or a power pin? On the DVR?
Do you have an oscilloscope in your "and a plate of electronic test" to try to find a signal pin?
An RS232 output will be low (negative) when idle.

I'd be surprised to find a 5V level on an RS232 interface.
But it's common to find 5V on a TTL Serial interface, to power the in-line convertor.

From what I can see - the "maxim max232" is a classic RS232 interface, powered by 5V.