Looking For Help - Exacqvision With Hikvision Encoders

The encoder supports RTSP, so use VLC to try to pull a stream.    The tricky part is discovering what the URL is.   I would like to think that Hik support could tell you that.

If you can pull a stream when Exacq is having the issue, then you know for sure it is something in Exacq.

I've been battling this same issue. And if you let it try to reconnect on its own, it will lock out the encoder for too many invalid logins. We're very interested in a solution also.

Update: Exacq has tested the encoder with new firmware v1.01 181024. I contacted Hik and they said that firmware is still in beta but they gave me a download link to try it out. I haven't tried it yet myself.

We found a solution to this. The DS-6716HQHI-SATA are still not working and the best option is the DS-6716HUHI-K. You have to have the latest version of Exacq 9.8 at the time of this post. With special Hikvision patch/update provided by Hikvision. 

I've been dealing with this at a site as well. It cropped up on us during a customer take over in December and hasnt been a tremendous issue thanks to ExacqCloud. It's only happened a small handful of times over the last year and we've been able to respond pretty quickly each time.

I reached out to Exacq today to see if they were aware or had any updates today and they advised updating to 19.03 (of course). I contacted HIK for the proper firmware and was told the firmware listed on exacq's website (181024) was a typo and I should use 180605. I updated the firmware and then Exacq and it wouldn't connect.....Long story short, my next two hours were filled with trial and error rollbacks of Exacq (and the encoder) before I found a version that would work with all the cameras installed on this server and troubleshooting cameras when the exacq config file got backwards during the process. 

Once I got everything back to where it was before I started I get an email form Hik support..."please use the firmware attached for integration with Exacq." The version they sent was 181024. I've wasted enough time today to deal with going through that again right now. 

I don't get it. Why would anyone waste hours upon hours trying fix something that may or may not be fixable, may or may not be reliable and may or may not have evidence when it's needed? Pull the encoders and install a proven encoder and be done with it. 

Install factory approved spark plugs and minimize ignition failure. If the engine doesn't start, it doesn't matter where you want to go. Spending hours looking at the exhaust system isn't going to change that. (Intended to be funny but may or may not have been successful)!

Well, we are certainly done using Hik Encoders with Exacq.

Tested today with 19.03 and firmware 181024 and couldn't get the encoder to even connect. Rolled it back to the tested version of 9.8 for same firmware and it still failed to connect. Both versions gave me an error message about being unable to save the config file for the hik channels. Rolled Exacq back to 8.7 with the old firmware and connection was restored.

We only have this one encoder deployed and are likely going to swap it once we find a suitable replacement.

In order to correct this you have to install IVMS4200, Connect to the encoder and go into the remote config.

Under the Remote Configuration Window go to System, Login Security, and ensure that the Access Lock is deselected.

With this enabled after 5 password attempts it will lock out for 1800s or 30min. We found this the hard way as well spending hours on tech support until we got a competent tech who fixed it in 5 min.

Hope this helps anyone with who still has this problem.. Also only run the encoders with the provided firmware and the approved exacq version number as listed on the website or you will be downgrading exacq to have them work again..