Knowledge Base

Summary

We tested network cameras from three manufacturers with Elvis: Advantech, Axis and Mobotix.

Details

Basically, we are interested in standardized solutions. For the integration of video images in Windows programs, the ActiveX interface is to be regarded as standard. As a result, all components (camera, video server, driver and interface) can be supplied from a single source and therefore ideally matched to each other. Elvis only needs to be able to include the ActiveX element – and he can do that very well!

Note: Unfortunately, the property pages of the ActiveX are often intended as modal pages (properties dialog with OK button). However, Elvis uses non-modal dialogs that allow you to continue working with an open properties dialog. This sometimes leads to problems when transferring the changed data (data is not saved because the properties dialog does not get an “OK”).
Remedy in these cases:
1. We have a control element property page where the data is applied correctly. This property page looks a bit raw, as it lists the properties. Press the Ctrl and Shift keys when opening the properties dialog.
2. Use the operator station’s event processing (see examples below).

Advantech

Advantech offers an inexpensive camera for indoor use.
We tested the ADAM-6090 .
The supplied ActiveX must be installed. In order to integrate the camera into the network, the IP address of the camera must be changed. With the control element available to us (Gif89), it was not possible to store the IP address.
However, this is not a problem with the event processing of the page:

Sub Form_Load() Form.Gif1.RemoteHost = "192.XXX.XXX.XXX" Form.Gif1.Play End Sub

Notes: Gif1 = the name of the control element (can be freely assigned).
Instead of the constant IP address, a text data point can of course also be used:

Sub Form_Load() Form.Gif1.RemoteHost = Database.Datapoint("IP Adresse Kamera").ActualValue Form.Gif1.Play End Sub

Axis

Axis has several cameras available for both indoor and outdoor use.
We tested the 2120 .

Since until recently provided by Axis control element “CamImage” also had problems saving the IP address. Solution as above, but instead of RemoteHost, the URL property must be set here:

Form.CamImage1.URL = "http://192.XXX.XXX.XXX/axis-cgi/mjpg/video.cgi" bzw. Form.CamImage1.URL = "http://" & Database.Datapoint("IP Adresse Kamera").ActualValue & "/axis-cgi/mjpg/video.cgi"

For the network server 2400+, the individual channels can be addressed in the event processing as follows (/2/ stands for the channel number here):

Form.CamImage1.URL = "http://192.XXX.XXX.XXX/mjpg/2/video.mjpg"

The new control element “Axis Media Control” from Axis works without any problems (the IP can be entered directly in the control element and is also remembered). Download directly from Axis: http://www.axis.com/techsup/software/amc/index.htm

Mobotix

The M22M camera was tested.

For a long time, no ActiveX was available for Mobotix cameras; this has now changed: the control element can be downloaded from http://developer.mobotix.com/ocx/MxPEG_ActiveX.html . The page says that the control element only works in Internet Explorer, but according to our tests, it also works well in Elvis. Unfortunately, you have to do some work to install it:

• extract the MxPEG_ActiveX.ocx from the CAB file to any directory (e.g. with WinZIP)
• and then register as described in KB000001 .

To overlay the camera image on a page:

• Create the “MxPEG_ActiveX Control” control element (from the “MxPEG_ActiveX ActiveX Control Module” library.
• enter the IP address, user name and password in the properties dialog on the “General” page