Using Axis Camera's 'Virtual Inputs'

caseyd
caseyd
edited April 2016 in SecuritySpy
I'm using the 'Virtual Input' capabilities of Axis' OS via calls - for example

http://192.168.0.95/axis-cgi/virtualinput/activate.cgi?schemaversion=1&port=1
http://192.168.0.95/axis-cgi/virtualinput/deactivate.cgi?schemaversion=1&port=1

Does Security Spy have a way of responding to Virtual Inputs?

Comments

  • Ben
    Ben
    Interesting. SecuritySpy already supports Axis physical input ports, so it would be quite easy to extend this to virtual inputs as the protocol is similar. However I can't seem to find out much information about virtual inputs - what are they?
  • caseyd
    caseyd
    From what I've gleaned the example I gave above is for 5.5, the VAPIX doc I've been able to find uses a different notation. Neither source gives limit to the number of virtual inputs.

    I think that there are 16 'virtual inputs' maintained in the Axis OS. However I can't tell you why I have that number in my mind. :P

    They can be scanned by on-camera rules, and probably used by on-camera scripts via the event engine.

    I don't know if their state can be queried. I think SSpy could easily enough trip the virtual input.

    In my case I am switching on the input via some node.js listening to my Elk M1 security system

Categories