Cognex Camera Integration
Snippet download, camera settings, and verification for In-Sight cameras.
1. Overview
This guide explains how to connect Cognex In-Sight cameras to the DataPulse gateway: download the configuration snippet from the HMI, set required camera options, import the snippet into the job spreadsheet, and verify that inspection data and images arrive in DataPulse.
It does not cover detailed Cognex inspection logic or tool programming. Use Cognex In-Sight Explorer (ISE) or In-Sight Vision Suite (ISVS) for job development.
Integration workflow
- Add the camera in DataPulse Setup -> Manage Cameras (gateway IP and camera IP on the same subnet).
- Download the Cognex snippet from Resources.
- Configure camera time (UTC + gateway IP for sync) and audit logging (ISVS only; see section 3.2).
- Import the snippet into the camera spreadsheet and complete required fields until status is Ready.
- Go online, trigger an inspection, and confirm records in Browse.
The factory configuration supports up to three (3) Cognex cameras per gateway. Contact Adams Engineering for special licensing configurations if you need additional cameras.
2. Download the configuration snippet
- Open Resources on the DataPulse HMI.
- Select Cognex Snippets as the resource type.
- Choose your Cognex software and camera model.
- Select the compatible snippet file and click Download.
- Save the file to a known location on your PC.
Import the downloaded snippet at the end of the camera job spreadsheet.
3. Configure camera settings
Configure these before importing the snippet.
3.1 Time settings (required)
Accurate UTC time sync between the camera and gateway is required. Without it, inspection records may transfer but images may not associate correctly.
In-Sight Explorer (ISE):
- Open the camera.
- Go to Sensor -> Date/Time Settings.
- Set time zone to UTC.
- Enter the DataPulse gateway IP (Ethernet 1 / camera network) for time synchronization.
- Save.
In-Sight Vision Suite (ISVS):
- Open the camera in ISVS.
- Open Time Settings.
- Set time zone to UTC.
- Enter the gateway IP for time synchronization and click Add.
- Click OK.
The gateway accepts NTP on UDP port 123 from cameras pointed at the gateway IP.
3.2 Audit logging (In-Sight Vision Suite)
Supported on In-Sight Vision Suite (ISVS) cameras that expose audit or syslog forwarding.
- Open Audit Logging (or equivalent syslog settings) in ISVS.
- Set the destination to the DataPulse gateway IP on the camera network (Ethernet 1).
- Set the port to 5001.
- Enable TCP with TLS using octet-counting framing (RFC 6587), as required by Cognex for syslog collectors such as Fluentd or Syslog Watcher.
- Accept or trust the gateway syslog TLS certificate when prompted.
- Save.
Do not change the audit port unless Adams Engineering directs you to. A wrong port or transport prevents audit logs from reaching the gateway.
3.3 In-Sight Explorer (audit logging)
In-Sight Explorer (ISE) uses a different audit transport (plain TCP, Cognex default port 5753). ISE audit integration with DataPulse is not covered in this guide.
Contact Adams Engineering support for audit log integration on In-Sight Explorer cameras. Include your camera model, firmware, and network layout.
4. Update the camera program
- Open the camera in ISE or ISVS.
- Import or drag the downloaded snippet into the job spreadsheet (at the end).
- When status shows Not Ready, complete the labeled fields (A through G):
| Callout | Field | Meaning |
|---|---|---|
| A | DataPulse IP | Gateway Machine IP (Ethernet 1) - the address cameras use for records, FTP, and time sync |
| B | Tag Group Name | How results are grouped for this camera. Set to the Job Name to keep results for different jobs separate |
| C | Pass/Fail Result | Spreadsheet cell that indicates the inspection result. Expect a 1 (pass) or 0 (fail) |
| D | Tag Names | Label for each tag sent to DataPulse (column in the tag table) |
| E | Tag Reference | Spreadsheet cell (or expression) that supplies the value for that tag name |
| F | Log Tag | When checked, that row’s tag is included in the transfer |
| G | Advanced Configuration | Camera ID, Soft Event Number, DataPulse Server Port, and Communication Switch (details below) |
Also set Enable Saving Good Images / Enable Saving Bad Images as required (bad images enabled by default in the factory snippet).
4.1 Advanced Configuration (callout G)
These cells are under Advanced Configuration. Soft Event Number, DataPulse Server Port, and Communication Switch are disabled by default in the factory snippet - enable them only when you need to change the defaults.
| Setting | Default | Notes |
|---|---|---|
| Camera ID | 1 |
Use different IDs only when cameras trigger simultaneously and write to the same DataPulse gateway, so filenames stay unique when timestamp and counters are not enough |
| Soft Event Number | 7 |
DataPulse drives WriteDevice / WriteImage from soft event 7. Choose another number only if your job already uses event 7 |
| DataPulse Server Port | 3000 |
Ingestion port on the gateway. Must match Setup → DataPulse Server on the HMI. Change both sides together |
| Communication Switch | On | When checked, enables all DataPulse communication (records and images). When unchecked, disables both |
Factory snippets wire WriteDevice and WriteImage to soft event 7 (via SetEvent). Do not bind those writes only to A0 when a Latch (or similar) also uses that event - that can publish stale tag or image data.
Updated snippet packages ship under HMI Resources → Cognex snippets. Re-import after upgrading the gateway.
- Save the program and go online.
- Trigger an inspection and confirm data appears in DataPulse Browse.
Inspection records transfer when the snippet is configured correctly and Communication Switch is on. Images transfer only for enabled good and/or bad image paths.
5. Camera FTP image paths
Cameras upload images over plain FTP on port 2121 to the gateway Machine (Ethernet 1) IP using the account below. Configure this inside the Cognex snippet or job, not on the HMI. Passive FTP data channels use TCP 50000–51000 on the gateway during transfer.
| Username | Password | Port | Protocol |
|---|---|---|---|
DataPulseUser |
d@tapul$e |
2121 | Plain FTP |
The gateway matches inbound inspection records to cameras by source IP (Setup → Manage Cameras). FTP credentials are used for image file transfer when the snippet enables it.
6. Verification checklist
- Gateway powered and reachable at
http://<machine-ip>:8080/dwview/ - Camera listed in Setup -> Manage Cameras with correct IP
- Snippet status is Ready (not Not Ready)
- Camera time zone is UTC and sync points at the gateway IP
- DataPulse IP correct in the snippet TCP/IP section
- Required Log Tag(s) enabled
- ISVS audit (if used): port 5001, TLS + octet-counting, gateway IP on camera network
- Disk space available (Info or Setup -> Storage Management)
7. Troubleshooting
| Issue | Possible cause | Corrective action |
|---|---|---|
| No inspection data | Snippet not imported | Import the correct snippet into the job spreadsheet |
| No inspection data | Snippet Not Ready | Complete all required fields until Ready |
| No inspection data | Log tags disabled | Enable required log tags |
| No inspection data | Wrong gateway IP in snippet | Verify callout A (Machine / Ethernet 1 IP) |
| No inspection data | Communication Switch off | Enable Advanced Configuration → Communication Switch |
| Stale tags / images | Soft event conflict or A0-only writes | Keep Soft Event 7 (or your chosen number) driving both WriteDevice and WriteImage |
| Data but no images | Image save not enabled | Enable save good and/or save bad images |
| Data but no images | Time not UTC / no sync | Fix time settings (section 3.1) |
| Camera disconnected in HMI | Wrong IP in Manage Cameras | Verify camera IP and network |
| Audit logs missing (ISVS) | Audit not enabled | Enable audit on port 5001 with TLS (section 3.2) |
| Audit logs missing (ISE) | ISE not configured | Contact Adams Engineering support (section 3.3) |
For gateway-side issues (HMI, storage, TLS, API, network ports), see the User Manual on the Resources tab.