![]() ![]() The app can only be used on device with USB OTG (host mode) support. ![]() The cameras that required the firmware downgrade were DS-2CD2742FWD-IZS, downgrade to firmware 5.5.0 from 5.5.53, this should also be attached to this post.Helicon Remote is a utility for tethered shooting and camera remote control compatible with all recent Nikon and Canon DSLR cameras (except for D3000 / D3100 / D3200 / D3300 / D3400 - these are NOT SUPPORTED. The cameras that were accessed using Palemoon alone were DS-2DE2A404IW-DE3 using firmware 5.5.16 (the latest as of this post, it is attached. Hopefully this helps someone who is struggling to find an answer that actually works. It's nice because I don't have windows in my house that afford me that view of my driveway. I will details my camera models below and the actions I took with each to get them working.Īs a side note, I also use MyIPcam plugin for chrome to have instant access to a live view. Trust me, lots and lots of time was spent to get the two simple answers that solved my problems. I had to downgrade the firmware of the camera that did not to get it to work. The next problem I needed to sort out was that one model of camera worked fine, the other did not. That was fixed by displaying only the navigation and bookmarks tool bars in palemoon. The first problem I had was that the camera view shifted positions in the browser such that it obstructed screen controls. ![]() I got the best results with palemoon 28.9.3, it kind of worked but it had its issues too. I tried seamonkey NPAPI, palemoon, IE tab and bunch of others. ![]() I had zero issue using a web interface with the Hikvision cameras until some nameless update to chrome. The browser interface is the nicest one that I have found for setting them up. Given all the discussion of other browsers to access Hikvision cameras, and the fact I own several of them, I thought I would share particular details to my situation. If you've not edited Camera 1 in the camera menu of the NVR, the Plug and Play mechanism will activate the camera and you'll be up and running. Then connect it again (without programming anything) to camera 1 on the NVR. This will return it to it's deactivated status. Your easiest option would be to press the reset button on the camera while powering it up. You would only set the camera to the same 192.168.0.xxx network if you are connecting it on your LAN, to your router for example, NOT to the NVR port. You are experiencing problems because you have a camera connected to the NVR PoE port with an address on the same subnet as the NVR LAN port. At that point, with virtual host enabled in the NVR, navigating to 192.168.0.101:65001 would connect you to the camera plugged into camera 1 port of the NVR - 192.168.254.2 (or whatever address the NVR had allocated) Note that without additional configuration, you would only be able to connect to the cameras web page using virtual host from a computer on your local network (192.168.0.xxx) The cameras LAN connection (192.168.0.101) is separated from the NVR's camera network which is addressed 192.168.254.1 by default (the NVR is accessible at that address if you connect a PC to a spare camera port) Connecting an unactivated camera to one of the ports will allow the NVR to allocate an address (using plug and play) in the range - camera 1 would become 192.168.254.2, camera 2 would be 192.168.254.3 and so on (these may become out of sequence as cameras are added removed, swapped around but it doesn't matter). I'm guessing if you had the camera directly plugged into the NVR Camera 1 PoE port, that you must have activated and programmed it BEFORE plugging its into the NVR - this was unnecessary. ![]()
0 Comments
Leave a Reply. |