Scribd
Upload
65 views2 pages

GraphWorX64 - Camera Control

This document provides instructions for connecting an IP camera to GraphWorX64 software and viewing the camera stream. It discusses setting security credentials, adding a video control to GraphWorX64, supported camera formats and limitations, and remote PTZ camera control. Precise steps are given for configuring camera access and properties.

Uploaded by

azhar saddiq
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
65 views2 pages

GraphWorX64 - Camera Control

This document provides instructions for connecting an IP camera to GraphWorX64 software and viewing the camera stream. It discusses setting security credentials, adding a video control to GraphWorX64, supported camera formats and limitations, and remote PTZ camera control. Precise steps are given for configuring camera access and properties.

Uploaded by

azhar saddiq
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

GraphWorX64 – Camera Control

Application Note April 2018

Description: Guide to connecting a camera control to an IP http://172.16.0.40/onvif/device_service.


camera.
General Requirement: Basic knowledge of GraphWorX64.
Prerequisites for Windows Servers: Desktop Experience and
Media Packages.

Introduction
In addition to various other controls, GraphWorX64 provides a
Camera control to view IP Camera stream in your GraphWorX64
display.

This application note will walk you through all the necessary Figure 2 - Camera Properties

steps to view camera streams.


5. You may decide to show the GUI for remote control or
enable audio.
Setting Security Credentials
NOTE: Volume control is not supported for MJPEG protocol.
For security reasons cameras require a client to authenticate.
Hence you need to specify the username and password for the
communication between the camera and the FrameWorX Server,
which plays the client role.

1. Open Platform Services Configuration e.g. via Workbench


2. Go to Passwords tab and add FWX  Camera item
3. Fill in the username and password which should FrameWorX
server use when connecting to the camera.

Figure 3 - Camera Control in GraphWorX64

Figure 1 - Specify Security Credentials for Camera Access


Supported Formats and Limitations
Adding Video Control to GraphWorX64 There are several requirements and limitations which should be
considered before you deploy a camera. Below you can see the
1. Open a GraphWorX64 list of protocols that are supported for normal and Silverlight
2. Select Controls ribbon and then click on Camera Control. version of GraphWorX64, and few more requirements.
3. Click and drag anywhere on the display to create a new
Video Control in GraphWorX64 display.
4. In the properties you need to fill in the appropriate URL. Standard version of GraphWorX64
 VideoUrl – Fill in the IP camera address or name such  RTSP (h264) protocol streaming
as rtsp://172.16.0.40:554/axis-media/media.amp or a. Direct access in local network or via VPN
http://172.16.0.40/mjpg/video.mjpg. b. For access from different network you need to
 OnvifUrl – If you want to control the camera you need run RTSP proxy by Streamcoders
to specify the appropriate Url the camera exposes for  MJPEG protocol streaming
remote control such as a. Direct access in local network or via VPN
© 2018 ICONICS, Inc. Page 1 of 2 GraphWorX64 - Camera Control
GraphWorX64 – Camera Control

Application Note April 2018

b. For access from different network you need to NOTE: If the camera requires Digest authentication, there is no way to
make it work properly with FIPS enabled. FIPS does not support MD5
use Mjpeg proxy hash that is used in Digest to authenticate the user, therefore if the
c. Does not support Audio camera is password protected, the user will not be verified and it will not
 PTZ (Pan-Tilt-Zoom) work.
a. Supported
b. Possible to create new presets There are two options how to solve it:

NOTE: Mjpeg proxy is installed into IIS server automatically with


GENESIS64 1) Disable password encryption on the camera. This option means the
camera will use Basic authentication instead of Digest. NOTE: This will
result in sending the user name and password as plain text over the
network!
Silverlight version of GraphWorX64
 RTSP (h264) protocol streaming
2) Make Video stream and Onvif publicly available.
a. For all connections, remote or local, requires
RTSP proxy by Streamcoders In case your camera supports Motion and Noise detection, you
 MJPEG protocol streaming will be able to connect an AlarmWorX Viewer to the camera and
a. Direct access in local network or via VPN read these alarms.
b. For access from different network you need to
use Mjpeg proxy You can use the following alarm subscriptions for:
c. Does not support Audio  Realtime alarms
 PTZ (Pan-Tilt-Zoom) o cam:<CameraDetectorsURL>
a. Supported  Historical alarms
b. Possible to create new presets o awx:Alarms/cam:<CameraDetectorsURL>

Remote control – PTZ Compatible Hardware


For PTZ control ONVIF requires the time difference between a All devices which use the supported protocols can be connected.
client and the camera to be the maximum of 5 seconds. ICONICS tested the control with the following cameras:

NOTE: ONVIF is an open industry forum for the development of a


 Axis M5014 – RTSP, MJPEG, PTZ
global standard for the interface of IP-based physical security products.
The ONVIF specification will ensure interoperability between products  Planet ICA-HM126 – RTSP
regardless of manufacturer.

In our case the client is our FrameWorX server and hence you
need to synchronize the time of the FrameWorX server machine
with the camera time. Cameras typically allow synchronization
with an NTP server or you can manually synchronize the time
using the web interface of the camera. In case the time is not
synchronized, TraceWorX will post a “Bad request” message on
the level of 400. However, please note that this message could
be posted for another reason as well.

NOTE: It is only the FrameWorX Server which communicates with the


camera; therefore remote clients to the FrameWorX server do not have
to synchronize time with the camera.

© 2018 ICONICS, Inc. Page 2 of 2 GraphWorX64 - Camera Control

You might also like