- Jan 3, 2016
- 262
- 33
EDIT: Fixed! See below.
Today I updated the firmware in my LTS/Hik NVR, after which I had connection problems with my 2 Huisin PTZs. I have a v1 and a v2.
I plugged a laptop into a spare port on the back of the NVR and fired up SADP. It saw the 2 cameras, but they had an unexpected IP: 192.168.254.x. I had expected them to be on 192.168.188.x like the rest of the cameras. OK, whatever. All this stuff is quirky, and Huisun more than most.
I used the "enable DHCP" checkbox in SADP, which reported success for each camera. I figured this would get the cameras talking with the NVR again.
Now is when the news gets really bad. The cameras disappeared from SADP, my laptop can't see them via arp -a, and if I power-cycle the cameras, they don't move any more. Even the Huisun SADP-like tool can't see the cameras.
Any ideas or did I just create two expensive doorstops? No power-on motion seems reallllly bad!
Today I updated the firmware in my LTS/Hik NVR, after which I had connection problems with my 2 Huisin PTZs. I have a v1 and a v2.
I plugged a laptop into a spare port on the back of the NVR and fired up SADP. It saw the 2 cameras, but they had an unexpected IP: 192.168.254.x. I had expected them to be on 192.168.188.x like the rest of the cameras. OK, whatever. All this stuff is quirky, and Huisun more than most.
I used the "enable DHCP" checkbox in SADP, which reported success for each camera. I figured this would get the cameras talking with the NVR again.
Now is when the news gets really bad. The cameras disappeared from SADP, my laptop can't see them via arp -a, and if I power-cycle the cameras, they don't move any more. Even the Huisun SADP-like tool can't see the cameras.
Any ideas or did I just create two expensive doorstops? No power-on motion seems reallllly bad!
Last edited by a moderator: