TP-Link NC450 camera and SecuritySpy
  • I've just purchased a TP-Link NC450 HD Pan/Tilt camera to use stand alone with the TP Camera App when the Mac isn't running. It works well, but I haven't been able to use it with SecuritySpy as yet. It finds the camera in preferences auto-discover or I can enter the IP address to view within a browser. However, SecuritySpy doesn't actually connect to it - yet. I'm sure it's just a case of trial and error to get the video up, but I haven't sussed it yet. The drop-down options for TP-Link cameras don't list the NC450, so any advice will be gratefully accepted.

    http://www.tp-link.com.au/products/details/cat-19_NC450.html
  • Hi,

    Under the Auto-Discovered Devices menu in SecuritySpy, does the camera appear under the ONVIF section, or under the Bonjour section?

    If it's the former, then you should use the ONVIF profile to connect to the camera. If it's the latter, then please let me know and I will supply further information to see if we can get this working for you.
  • The camera appears in the Boujour section and when selecting the 'Open in Web Browser' button to the right of the 'Discovered Devices' button, it opens in the browser at the camera's 'logon' screen. Entering the logon details does then display the video in the camera's admin screen.
  • OK, use that address, and enter the camera's username and password in SecuritySpy.

    Then select the "Manual Configuration" profile, and the "RTSP" Format.

    Enter h264_vga.sdp as the Request.

    Does this work? If so, I'll see if we can add a custom profile that also enables the pan/tilt commands.
  • I'm sure we a are nearly there!

    Here's what I get with the various options with h264_vga.sdp in the Request box:

    - RTSP TCP (video and audio) = Unrecognised Request, check device type
    - RTSP UDP (video and audio) = Unrecognised Request, check device type
    - RTSP-over-HTTP Video and audio) = Unrecognised Request, check device type
    - HTTP (video only) = Unrecognised Request, check device type

    Without the h264_vga.sdp in the Request box, the 2 RTSP options UDP and TCP give the Unrecognised device message. the HTTP options gives Error 801 and RTSP-over-HTTP gives 'communication error'

    I hope this helps in some way.
  • Checking the web and searching for RTSP - there is a link generator that SHOULD work with the NC450. If I put this in Safari, it opens Qicktime Player with a 'live broadcast' but the window is just black.

    rtsp://admin:**********1@192.168.1.**/h264_vga.sdp
  • I wonder if the latest firmware update for this camera prevents any access other than by the TP-Link app? By all accounts, using h264_vga.sdp should work for RTSP. It's a shame as the video quality for indoor monitoring is good in daylight and passable at night and the camera isn't too expensive either.
  • There is some talk on Github about getting the NC 250 model working. Might help?
    https://github.com/reald/nc220/issues/4
  • This is strange, because h264_vga.sdp should be the correct request. Are you sure there are no extraneous characters or whitespace when you are entering the request?

    Try this:

    - Set the Format to HTTP
    - Enter stream/video/mjpeg as the Request
    - If that doesn't work, try video.mjpg as the Request

    Any luck?
  • No, I'm still getting "Unrecognised request, Check Device Type' in the setup tab window when using:

    - Set the Format to HTTP
    - Enter stream/video/mjpeg as the Request
    - If that doesn't work, try video.mjpg as the Request

    I'm using copy and paste from your posts as well as typing in the request manually, so I think I'm OK there.

    If I choose 'Manual Config' and put nothing in the Request box, this is what I get:

    - HTTP (Video Only) = Error 801 (see log)
    - RTSP TCP (video and audio) = Unrecognised request, Check Device Type
    - RTSP UDP (video and audio) = Unrecognised request, Check Device Type
    - RTSP-over-HTTP (video and audio) = Communication error

    These are the errors from the log - although not necessarily in the order listed above.

    24/05/2017 11:22:38: Error communicating with the network device "Network camera". 4.1.4,70280,404 Failed to obtain video frame from network device. File not found.

    24/05/2017 11:24:53: Error communicating with the network device "Network camera". 4.1.4,70280,404 Failed to obtain video frame from network device. File not found.

    24/05/2017 11:26:45: Error communicating with the network device "Network camera". 4.1.4,80210,404 Failed to obtain video frame from network device. File not found.

    24/05/2017 11:26:47: Error communicating with the network device "Network camera". 4.1.4,80210,404 Failed to obtain video frame from network device. File not found.

    24/05/2017 11:26:57: Error communicating with the network device "Network camera". 4.1.4,89900,8800 Failed to obtain video frame from network device. The server closed the connection.

    24/05/2017 11:26:58: Error communicating with the network device "Network camera". 4.1.4,70219,8801 Failed to obtain video frame from network device.

    24/05/2017 11:27:06: Error communicating with the network device "Network camera". 4.1.4,70291,801 Failed to obtain video frame from network device. Data from network device not as expected.

    24/05/2017 11:27:06: Error communicating with the network device "Network camera". 4.1.4,70291,801 Failed to obtain video frame from network device. Data from network device not as expected.

    24/05/2017 11:29:57: Error communicating with the network device "Network camera". 4.1.4,89900,8800 Failed to obtain video frame from network device. The server closed the connection.

  • Meatsuit, thanks for the pointer, I am making progress now. Using VLC this does display a picture.

    rtsp://admin:***************@192.168.1.112:554/h264_hd.sdp
  • OK, cooking on gas now!

    I have a picture :)

    Settings are Manual, RSTP TCP (video and audio) and h264_hd.sdp in the request box.

    The only tings I've done differently during this testing is to use the cameras admin panel to change the frame rate from 15 to 30 fps (still no picture) then back to 15 fps (still no picture).

    The breakthrough came when I changed the SecuritySpy frame-rate from Default to 15 fps and the picture appeared immediately.

    Changing the frame rate was one of the hints in the link that Meatsuit gave, so I'm not sure if it was the change using the admin panel or the change in SecuritySpy preferences that did the trick - more testing to follow.

    I can't get the PTZ controls up for the NC450 yet, but I'm working on that.

    EDIT: I don't think that I can access the PTZ controls for a camera setup manually?
  • Great to hear that!

    For the PTZ commands, there doesn't appear to be any technical information published by TP-Link about this, so we'll have to try to find out the commands by other means.

    Are you able to control the camera's pan/tilt using a web browser (e.g. Safari) on your Mac, by connecting to the camera's IP address to view its web interface?
  • Ben, yes, connecting to the camera admin interface using Safari I can pan/tilt using the controls on the page.

    I can view the admin page source code, but I don't really know what I'm looking for.
  • Not sure if this helps, mouse down to pan 'e' and stop when mouse button is released.

    args.data.operation = "start";
    args.data.direction = "e";

    common.setAjax.init(args);

    INTERVAL_TIMER = setInterval(function(){
    common.setAjax.init(args);
    },TIME_INTERVAL);

    }).mouseup(function(){
    args.data.operation = "stop";

    clearInterval(INTERVAL_TIMER);

    common.setAjax.init(args);
  • Here's how you can determine what these PTZ commands are:

    - Download the trial version of the HTTP Scoop software.

    - If the camera’s HTTP interface runs on any port other than 80, go to the Preferences, and add the actual HTTP port, as follows (e.g. if it runs on 88):

    image

    - Select the network interface that your Mac uses to connect to your network, and then press the Scoop button:

    image

    - Then, perform some pan/tilt movements via the camera’s web interface. HTTP Scoop should then display each of these requests in its main window:

    image

    - Double-click on any of these to show the detail of the request. Under the Setup tab, it is the "Request URL" that is the important information

    image

    - Please copy and paste here the request URLs that correspond to the camera’s movements.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!