Silas
Pulling my weight
depends where in oz they are ;-)
I'm in Perth, Western Australia. Thankfully no fires near my home!depends where in oz they are ;-)
HelloYep - we love it here - close to the perfect Perth beaches!
So I've got the bits you've suggested on order (in the mail). Also emailed HikVision to request a password code/file, but as I expected they have given me the "we don't deal with consumers directly" nonsense. Very frustrating. Contacted several local security firms and all want a $150 call-out fee, then extra per hour to 'fix' it. No guarantee of a fix either, so could be $150 down the toilet.
Once the bits are here, what's next? I'm assuming I'm going to a do a firmware re-install to the NVR via the Serial port? Or is there a way to get the password out through PuTTY terminal session?
That's good, you've got it hooked up correctly.When it boots, I'm getting all the log data coming through the PuTTY Terminal.
This program will upgrade software.
*******************************************************
* ATTENTION!! PLEASE READ THIS NOTICE CAREFULLY! *
* Don't reset machine,or anything that interrupt it. *
* The upgrade process must finish in 10 minutes! *
* If this program fails,machine might be unusable, *
* and you will need to reflash again. *
* If you find this too risky,power off machine now. *
*******************************************************
Now press [u/U] key to upgrade software:
HKVS # printenv
bootcmd=tftp 0x80400000 $(bootfile);bootm 0x80400000;
default=cramfsload 0x80400000 uImage;
sec=tftp 0x80400000 uImage_sec;bootm 0x80400000;
verify=n
bootdelay=1
baudrate=115200
mdio_intf=rgmii
ipaddr=192.0.0.64
serverip=192.0.0.128
gatewayip=192.0.0.1
netmask=255.255.255.0
bootfile=uImage
device_type=DS-7604NI-E1/4P/A
identification=0000000100000001000002000000002a00000001000000020005
update_ip=192.0.0.64
phyaddr1=7
bootargs=mem=177M console=ttyS0,115200n8
ethaddr=bc:ad:28:87:7e:c4
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2010.06-svn (Aug 15 2015 - 15:18:43)
Environment size: 577/4092 bytes
HKVS #
setenv ipaddr 192.168.1.214
setenv serverip 192.168.1.99
sf probe 0
sf read 0x80400000 0x00000 0x10000
tftp 0x80400000 mtdblock0 0x10000
sf read 0x80400000 0x10000 0x20000
tftp 0x80400000 mtdblock1_part1 0x20000
sf read 0x80400000 0x30000 0x20000
tftp 0x80400000 mtdblock1_part2 0x20000
sf read 0x80400000 0x50000 0xFB0000
tftp 0x80400000 mtdblock2 0xFB0000
HKVS # setenv ipaddr 192.168.1.214
HKVS # setenv serverip 192.168.1.99
HKVS #
HKVS # sf probe 0
16384 KiB hi_sfc at 0:0 is now current device[4K erase supported]
HKVS #
HKVS # sf read 0x80400000 0x00000 0x10000
HKVS # tftp 0x80400000 mtdblock0 0x10000
timeout for link [4999]!
MAC: BC-AD-28-87-7E-C4
TFTP to server 192.168.1.99; our IP address is 192.168.1.214
Upload Filename 'mtdblock0'.
Upload from address: 0x80400000, 0.064 MB to be send ...
Uploading: # [ Connected ]
0.064 MB upload ok.
HKVS # sf read 0x80400000 0x10000 0x20000
HKVS # tftp 0x80400000 mtdblock1_part1 0x20000
timeout for link [5000]!
MAC: BC-AD-28-87-7E-C4
TFTP to server 192.168.1.99; our IP address is 192.168.1.214
Upload Filename 'mtdblock1_part1'.
Upload from address: 0x80400000, 0.128 MB to be send ...
Uploading: # [ Connected ]
#
0.128 MB upload ok.
HKVS # sf read 0x80400000 0x30000 0x20000
HKVS # tftp 0x80400000 mtdblock1_part2 0x20000
timeout for link [5000]!
MAC: BC-AD-28-87-7E-C4
TFTP to server 192.168.1.99; our IP address is 192.168.1.214
Upload Filename 'mtdblock1_part2'.
Upload from address: 0x80400000, 0.128 MB to be send ...
Uploading: # [ Connected ]
#
0.128 MB upload ok.
HKVS #
HKVS # sf read 0x80400000 0x50000 0xFB0000
HKVS # tftp 0x80400000 mtdblock2 0xFB0000
timeout for link [5000]!
MAC: BC-AD-28-87-7E-C4
TFTP to server 192.168.1.99; our IP address is 192.168.1.214
Upload Filename 'mtdblock2'.
Upload from address: 0x80400000, 15.704 MB to be send ...
Uploading: # [ Connected ]
################################ [ 2.888 MB]
################################ [ 5.752 MB]
################################ [ 8.616 MB]
################################ [11.480 MB]
################################ [14.344 MB]
###############
15.704 MB upload ok.
HKVS #
It looks like it all worked - here are the files (attached). FINGERS CROSSED!Assuming that all works OK, zip up the mtdblock1_part1 and mtdblock1_part2 files and attach here.
I should be able to extract the camera passwords, which hopefully will match the NVR password.
Good luck!
So far, so good.It looks like it all worked
You are a champion! That's it. Thanks for your help on this. Now to plug it in and see if I can get all the cameras to reset as well.So far, so good.
Let's see. Camera passwords as follows for admin :
g373skk1987 Spa Area
g373skk1987 Driveway
g373skk1987 Front Door
g373skk1987 Front Door
Now - if that works for the NVR, great.
But if it doesn't, at least it's the camera paswords (for which no compatible firmware could be found) which would allow the NVR to be reset without orphaning the cameras.
That's a great result!You are a champion! That's it.
You shouldn't have to do anything on the cameras except get them connected to the same NVR PoE ports that there were originally set up on.Now to plug it in and see if I can get all the cameras to reset as well.
I seem to have a problem with this. I don't know which camera was in each port and now they won't work. I've tried plugging one camera in at a time, moving it across each of the 4 ports. It comes up with "Detecting" in the Camera Menu, but then after 20 sec or so it comes up with a Status Triangle with red exclamation mark. And no picture. Strange thing is that in the Camera config page it has 4 cameras listed even when I don't have any plugged in. Is that normal?That's a great result!
You did pretty well hooking up the serial console, and follwoing the instructions.
You shouldn't have to do anything on the cameras except get them connected to the same NVR PoE ports that there were originally set up on.
SADP will help there.
Cross-reference the IP addresses seen in SADP with the camera configuration details in the NVR web GUI.
You may have to just have one connected at a time to be sure which is which.
Yes, that's normal.Strange thing is that in the Camera config page it has 4 cameras listed even when I don't have any plugged in. Is that normal?
That's good - almost there it seems.So after a bit more mucking around - reverting to the old password, then plugging in each camera - I have got it working. I have also now been able to change the Password and it has pushed the new Password to the camera's. Success!
Do you mean the NVR is rejecting the camera with that error message?Now that camera is coming up with "Incorrect language"
I'm speculating that the cameras are actually CN cameras running 'hacked to English' firmware.Sooooooo - the question is.... how do I get that 2nd camera back to the correct (presumably English) language?
camera's that are working all have an option to 'Upgrade'.
That sounds like the NVR VGA/HDMI interface, which does have an ability to push updates to the cameras via a USB stick source for the firmware.Should i do this? I'm assuming that they have sourced a new version over the internet (I have connected the NVR to my home network)
One of the working camera's serial numbers is : DS-2CD2345-I20170320AAWR730894444A clue that may confirm this would be to look at the camera serial numbers as seen in the System Information page of the camera web GUI, or via SADP when the PC can see the cameras on the NVR PoE ports.
The letters CCCH in the serial number would be a clue.