Vicon uses built-in Java for viewing and configuring their cameras. If Samsung would drop the plugin and go with HTML5, then the program would be compatible with any browser. No idea what the difference is between the two systems. I can view an RTSP stream, just not the built-in program for configuring the camera. On those computers, I’ve never been able to get the browser to view the camera. But other times, it keeps going back to the plugin install page. Once this installs, the browser is supposed to close and reopen and be able to view the camera. For example, when viewing a Samsung (now Hanwha) camera via its IP address, it first pops up a screen with a link to install a plugin. I’ve been seeing a recurring issue with manufacturers using plugins in order to view the camera feed. I install rather a lot of IP cameras for security. I still don’t know why this was an issue, since the Digital Sentry had the proper username and password. Since my camera networks are all private IP based (can’t be viewed from Internet), this wasn’t really an issue, so I checked that box and the video instantly appeared on the Digital Sentry! Then I started looking at the various settings available on the camera itself, and found one that allowed me to use an RTSP stream without authentication. I tried placing the username and password in the RTSP URL, but that didn’t work either. I went in circles checking and double-checking to make sure I hadn’t typed anything wrong, and still no video from these cameras in the Digital Sentry. The new camera is supposed to be ONVIF S compliant, which is what the Pelco unit requires. It worked fine with the previous version, the Samsung SNV-6013 mini-dome. I had no issue viewing the cameras in a browser, or in VLC Player, but the Digital Sentry unit consistently refused to show any video. I recently bought 4 new Hanwha XNV-6011 mini-dome cameras, installed them, and went to add them to our aging Pelco Digital Sentry NVR. Up until yesterday, I’ve had no issue with connecting to the cameras, either through the generic ONVIF method, or through RTSP streams. The company for which I work uses a lot of Samsung IP cameras, and now Hanwha. Korean military supplier Hanwha bought the company Samsung and has been updating some of the products with their new brand and some new features. I’ve seen other blurbs that say “Just type in the IP address into a browser”, but that assumes I know if it has one, and what the address is. It appears that they were made for use only with their own brand NVR. I found no pinout documentation online, nor any info about a default IP address for these cameras. But Q-See likes to keep things proprietary, so I drove back out to the location of the Q-See NVR and plugged the cable into the unit. Initially, I tried connecting the resulting cable to a POE switch to see if it would recognize the camera. I used 3M Scotchlok UY2 connectors to splice the wires of the CAT6 cable to the wires of the camera. I taped the ends of the CAT6 cable and camera cable together to remove stress from the individual wires. I cut apart the remains of the jack which still had wires attached to it.įrom this, I determined which colors went to which pins, and used a cross-reference to the T568B standard to figure out how to splice the wires to a CAT6 cable. I figured out that there were two pairs being used for communication, and one pair being used for POE. And there were only 6 wires instead of 8, and the wires were very thin which meant I couldn’t punch them to a jack directly because they were too fragile. However, the wire colors that the company used inside the camera were not the standard colors normally encountered in CAT6 cabling. It is a Q-SEE (Hikvision) QCN8099B camera, and had a pigtail with an RJ45 jack built-in. I had to work on an IP camera that had the pigtail cut off.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |