Tag: Integrations
Arecont single-sensor cameras with firmware 65218 and 65219 can fail to connect or display video after a Windows 7 exacqVision system restarts. This can occur because exacqVision software changed to the RTSP protocol starting with version 5.4. Arecont plugins in exacqVision versions earlier than 5.4 use TFTP, which is not affected by this issue.
<br>
To obtain beta firmware, visit https://exacq.com/support/ipcams.php and search for your camera model. Then click the link under the Integration Status column for details.
<br>
Also, firmware older than 65218 can be downloaded and installed from Arecont’s support website. If you have firmware 65219 installed, do not update the firmware; Arecont will provide a solution for these and other cameras.
<br>
ARECON1.DOC.pdfRequirements
*This document applies to exacqVision 4.3 and later.
*Serial data can be received using RS-232, HTTP, or TCP/IP. The data must be in an un-encrypted ASCII format. Formatting such as .xml can be used, but the data cannot be parsed.
*If there are questions the data format, see sections 4 and 5.
<br>
exacqVision Serial Data Capabilities
- Serial data is captured in a line-by-line format. This imposes the following limitations:
*Filtering cannot be done on a character basis.
*Filtering characters on a line will filter out the whole line. - It is preferable for each transaction type to have defined a Start of Transaction (SOT) and End of Transaction (EOT).
*If no SOT and EOT are defined, entering “VOID” in the search serial box on the search cameras page will return only the line in each transaction where the “VOID” occurs instead of the whole transaction.
*Characters defined as Line Feed, Form Feed, Carriage Return, and Vertical Tabulation cannot be used as the final character in an SOT, EOT, or mask.
*Each transaction must have a beginning and end even if no SOT or EOT is defined. This means that each transaction must have an end-of-line character such as those listed in 2b. - Event Key Words are not used for filtering. Key Words are used to trigger events defined in Event Linking.
- Live Display and Record Masks will filter out data that matches the string. However, the rules in Step 1 still apply.
- Character substitution is not available.
<br>
Configuring exacqVision
For information on how to setup the exacqVision system, open exacqVision Client. On the Serial Profile and Serial Ports pages, click on the Help button (or press F1).
<br>
Capturing and Analyzing IP Serial Data
Use Wireshark to verify a TCP/IP data stream for integration by completing the following steps:
- Perform a Wireshark capture on the network for the data stream going to the POS/ATM device. For information on capturing traces, see the exacqVision Wireshark Quick Start Guide (sec. 2) at https://www.exacq.com/kb/?kbid=18575.
- Filter the data in the Wireshark trace based on the IP of the device you are interested in. Here is sample data from a Wireshark capture:
- In this example, legible text is displayed. This means that the data is un-encrypted.
- Look at the data and try to find areas that will work as an SOT and EOT. In the example shown, 701.42 (preceding the date) could be used to trigger the start of the transaction, and THANK YOU could be used to trigger the end of the transaction.
<br>
Capturing and Analyzing RS-232 Serial Data
The easiest way to analyze RS-232 serial data is to do the following:
- Create a profile in exacqVision Client that does not contain an SOT or EOT.
- Create a Serial Port with the proper settings to match the sending device.
- Connect the RS-232 ports between the sending device and the exacqVision server.
- In exacqVision Client Live View, drag the name of the Serial Port into the live view area.
- Execute a transaction and watch exacqVision Client. If you see legible text on the screen, that means the data is un-encrypted and can be used for integration. The following image shows an example of un-encrypted data.
<br>
To capture RS-232 serial data to be analyzed later, complete the following steps:
- Use a program such as Putty (http://www.putty.org/) to capture the data on the sending device.
- Use a program such as Netcat (http://netcat.sourceforge.net/) to play back the file captured in step 1.
- The steps to display the data in exacqVision Client are the same as steps 1-5 at the start of this section.
<br>
First, make sure that your Analog camera is using Pelco-D protocol and that its address is set to 1.
<br>
Also, in some versions of the exacqVision software, the speed is not correctly sent to the camera when using the Pan and Tilt functions. To fix this, adjust the speed bar under the Pan and Tilt controls.
<br>
Why-does-my-PTZ-not-work-completely-on-the-ACTi-ACD2100-camera.pdfIP Camera Integration Database
ExacqVision supports thousands of cameras from a large number of manufacturers. The IP Camera Integrations database provides a complete list of test records for supported camera models. Search by brand, model, or firmware version, and filter by camera feature.
The following video describes how to use the database to its full extent:
<br>
What if my camera isn’t listed as supported?
It would be impossible to list every camera ever made. However, just because a camera model isn’t listed doesn’t necessarily mean it will not work with ExacqVision. It DOES, however, mean that we cannot assure any features or functionality.
- If you find that a particular firmware version from your camera manufacturer is listed as supported on another model from the same brand, there is a good chance it will work with the same Plugin/Device Type listed.<br><br>
- If your camera supports Onvif, it may still work if you add it to your system selecting ‘Onvif’ from the Device Type selector. Note, that while Onvif is described as an open standard, not all manufacturers implement it adhering to the standards. Additionally, some advanced functionality may not be supported when using Onvif.
Onvif compliant cameras are not usually considered “plug and play,” meaning that minor software revisions may be necessary to receive metadata regarding motion data or other signals.<br><br> - If your camera provides an RTSP video stream, a final option may be to use the ‘RTSP’ Device Type. This would allow ExacqVision to record the video stream only. Features such as motion data, analytics, and inputs/outputs are not supported via RTSP.
Will Exacq support my camera?
While Exacq supports a very large number of cameras, that cover a wide range of capabilities and features, we also understand that your particular camera or firmware may not be listed as supported.
What can you do? See the below section.
Submit a request for testing
- From the IP Camera Integrations database, click Can’t Find Camera?
- Complete the New IP Camera Integration Suggestion form.
- Check ‘I’m not a robot,’ to pass the Captcha test.
- Click Submit Form.
This form will provide your request to our Product Team for consideration. Please be aware that we plan our releases months in advance, and we can not guarantee that support for your camera will be available in a specific time frame. If you have a sizeable project that requires a camera we do not support please contact Sales to discuss your requirements.
<br>
Some cameras, particularly AXIS and Sony models, display an OSD date with an incorrect year. The time and date of the camera might be set to GMT and the Windows time is correct on the server, yet the OSD on the screen shows something like March 2, 2001.
<br>
This is usually a result of European Date Formatting (dd/mm/yy). Set the camera to USA date format (mm/dd/yy) to resolve the issue.
<br>
Camera-Time-Stamp-Off-by-Years.pdf