Q-SEE QCN8099B camera pinout

I had to work on an IP camera that had the pigtail cut off. It is a Q-SEE (Hikvision) QCN8099B camera, and had a pigtail with an RJ45 jack built-in. However, the wire colors that the company used inside the camera were not the standard colors normally encountered in CAT6 cabling. 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.

I figured out that there were two pairs being used for communication, and one pair being used for POE.

cam wires3

I cut apart the remains of the jack which still had wires attached to it.
IMG_0826

From 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.


CAMERA T568B POE-B
1 BROWN ORN/WH
2 PURPLE ORN
3 ORANGE GRN/WH
4 YELLOW BLU DC+
5 (NONE) BLU/WH DC+
6 BLUE GRN
7 GRAY BRN/WH DC-
8 (NONE) BRN DC-

I taped the ends of the CAT6 cable and camera cable together to remove stress from the individual wires. I used 3M Scotchlok UY2 connectors to splice the wires of the CAT6 cable to the wires of the camera. (I didn’t get a picture of the splices)

Initially, I tried connecting the resulting cable to a POE switch to see if it would recognize the camera. 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. After a minute or so the camera came up!

I found no pinout documentation online, nor any info about a default IP address for these cameras. It appears that they were made for use only with their own brand NVR. 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.

Trouble (and solution) getting Hanwha XNV-6011 to record on Pelco Digital Sentry

Korean military supplier Hanwha bought the company Samsung and has been updating some of the products with their new brand and some new features. The company for which I work uses a lot of Samsung IP cameras, and now Hanwha. Up until yesterday, I’ve had no issue with connecting to the cameras, either through the generic ONVIF method, or through RTSP streams.

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. 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. It worked fine with the previous version, the Samsung SNV-6013 mini-dome. The new camera is supposed to be ONVIF S compliant, which is what the Pelco unit requires.

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. I tried placing the username and password in the RTSP URL, but that didn’t work either.

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. 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!

I still don’t know why this was an issue, since the Digital Sentry had the proper username and password.

IP Cameras – trouble with plugins for viewing

I install rather a lot of IP cameras for security. I’ve been seeing a recurring issue with manufacturers using plugins in order to view the camera feed. 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. Once this installs, the browser is supposed to close and reopen and be able to view the camera. Sometimes that works, like on my laptop. But other times, it keeps going back to the plugin install page. On those computers, I’ve never been able to get the browser to view the camera. I can view an RTSP stream, just not the built-in program for configuring the camera. No idea what the difference is between the two systems. If Samsung would drop the plugin and go with HTML5, then the program would be compatible with any browser.

Vicon uses built-in Java for viewing and configuring their cameras. But the version of Java on the camera is older day by day, and so Windows quickly does not trust it and each camera has to be entered into the Java exception screen in Control Panel. Java then wants to reset this list for safety reasons. Ridiculous waste of time just to be able to configure the camera.

Netgear switches (GS110TP) that I use to hook the laptop to the IP cameras also use a Java plugin to view the switch layout. Clicking the link doesn’t install the plugin, it just redirects to the Sun Java homepage, which is useless. Besides 64-bit Firefox cannot install such a plugin. Browsers are moving away from such approaches and going with HTML5. Thus there is a part of the switch I have that I cannot access due to the manufacturer deciding to use a plugin instead of a standard web page or HTML5. I can’t get my laptop to install the plugin because I have 64-bit and Firefox. I can still do most functions on the switch menu, but am blocked from other sections.
I’ve read on Netgear forums that this problem is marked “solved”, but all they said was “please open a trouble ticket” and then closed the thread. Yo Netgear, that isn’t solving the problem! So what if you “are aware” of the issue. You’ve “been aware” for YEARS now. Hire some programmers and dump plugin entirely.

Harumph!