• Support Home
  • Getting Started
    • Connecting Your Camera
    • 3rd Party Software Getting Started Guides
  • Tech Ref Manuals
    • Arena SDK Documentation
    • HTP003S – Helios2+ ToF 3D
    • HLT003S – Helios2 ToF 3D
    • HLS003S – Helios ToF 3D
    • HLF003S – Helios Flex ToF 3D
    • ATX245S – Atlas10 24.5 MP
    • ATX204S – Atlas10 20.4 MP
    • ATX162S – Atlas10 16.2 MP
    • ATX124S – Atlas10 12.3 MP
    • ATX081S – Atlas10 8.1 MP
    • ATX051S – Atlas10 5.0 MP
    • ATL314S – Atlas 31.4 MP
    • ATL196S – Atlas 19.6 MP
    • ATL168S – Atlas 16.8 MP
    • ATL120S – Atlas 12.3 MP
    • ATL089S – Atlas 8.9 MP
    • ATL071S – Atlas 7.1 MP
    • ATL050S – Atlas 5.0 MP
    • ATL028S – Atlas 2.8 MP
    • ATP200S – Atlas IP67 20 MP
    • ATP120S – Atlas IP67 12.3 MP
    • ATP089S -Atlas IP67 8.9 MP
    • ATP071S – Atlas IP67 7.1 MP
    • ATP028S – Atlas IP67 2.8 MP
    • TRI200S – Triton 20.0 MP
    • TRI120S – Triton 12.3 MP
    • TRI122S – Triton 12.2 MP
    • TRI089S – Triton 8.9 MP
    • TRI071S – Triton 7.1 MP
    • TRI064S – Triton 6.3 MP
    • TRI054S – Triton 5.4 MP
    • TRI050S-P/Q – Triton 5.0 MP Polarized
    • TRI050S – Triton 5.0 MP
    • TRI032S – Triton 3.2 MP
    • TRI028S – Triton 2.8 MP
    • TRI023S – Triton 2.3 MP
    • TRI016S – Triton 1.6 MP
    • TRI004S – Triton 0.4 MP
    • TRI02KA – Triton 2K Line Scan
    • PHX200S – Phoenix 20.0 MP
    • PHX120S – Phoenix 12.3 MP
    • PHX122S – Phoenix 12.2 MP
    • PHX089S – Phoenix 8.9 MP
    • PHX064S – Phoenix 6.3 MP
    • PHX050S-P/Q – Phoenix 5.0 MP Polarized
    • PHX050S – Phoenix 5.0 MP
    • PHX032S – Phoenix 3.2 MP
    • PHX023S – Phoenix 2.3 MP
    • PHX016S – Phoenix 1.6 MP
    • PHX004S – Phoenix 0.4 MP
  • Application Notes
    • Bandwidth Sharing in Multi-Camera Systems
    • Combine Helios 3D Point Cloud with RGB Color
    • I2C Support on LUCID Cameras
    • Using GPIO on LUCID Cameras
    • Using PTP & Scheduled Action Commands
    • Helios2 And Triton Synchronization
  • Knowledge Base
  • Additional Support
    • Product Change Notifications (PCN)
    • Contact Support
  • Log In
  • Support Home
  • Getting Started
    • Connecting Your Camera
    • 3rd Party Software Getting Started Guides
  • Tech Ref Manuals
    • Arena SDK Documentation
    • HTP003S – Helios2+ ToF 3D
    • HLT003S – Helios2 ToF 3D
    • HLS003S – Helios ToF 3D
    • HLF003S – Helios Flex ToF 3D
    • ATX245S – Atlas10 24.5 MP
    • ATX204S – Atlas10 20.4 MP
    • ATX162S – Atlas10 16.2 MP
    • ATX124S – Atlas10 12.3 MP
    • ATX081S – Atlas10 8.1 MP
    • ATX051S – Atlas10 5.0 MP
    • ATL314S – Atlas 31.4 MP
    • ATL196S – Atlas 19.6 MP
    • ATL168S – Atlas 16.8 MP
    • ATL120S – Atlas 12.3 MP
    • ATL089S – Atlas 8.9 MP
    • ATL071S – Atlas 7.1 MP
    • ATL050S – Atlas 5.0 MP
    • ATL028S – Atlas 2.8 MP
    • ATP200S – Atlas IP67 20 MP
    • ATP120S – Atlas IP67 12.3 MP
    • ATP089S -Atlas IP67 8.9 MP
    • ATP071S – Atlas IP67 7.1 MP
    • ATP028S – Atlas IP67 2.8 MP
    • TRI200S – Triton 20.0 MP
    • TRI120S – Triton 12.3 MP
    • TRI122S – Triton 12.2 MP
    • TRI089S – Triton 8.9 MP
    • TRI071S – Triton 7.1 MP
    • TRI064S – Triton 6.3 MP
    • TRI054S – Triton 5.4 MP
    • TRI050S-P/Q – Triton 5.0 MP Polarized
    • TRI050S – Triton 5.0 MP
    • TRI032S – Triton 3.2 MP
    • TRI028S – Triton 2.8 MP
    • TRI023S – Triton 2.3 MP
    • TRI016S – Triton 1.6 MP
    • TRI004S – Triton 0.4 MP
    • TRI02KA – Triton 2K Line Scan
    • PHX200S – Phoenix 20.0 MP
    • PHX120S – Phoenix 12.3 MP
    • PHX122S – Phoenix 12.2 MP
    • PHX089S – Phoenix 8.9 MP
    • PHX064S – Phoenix 6.3 MP
    • PHX050S-P/Q – Phoenix 5.0 MP Polarized
    • PHX050S – Phoenix 5.0 MP
    • PHX032S – Phoenix 3.2 MP
    • PHX023S – Phoenix 2.3 MP
    • PHX016S – Phoenix 1.6 MP
    • PHX004S – Phoenix 0.4 MP
  • Application Notes
    • Bandwidth Sharing in Multi-Camera Systems
    • Combine Helios 3D Point Cloud with RGB Color
    • I2C Support on LUCID Cameras
    • Using GPIO on LUCID Cameras
    • Using PTP & Scheduled Action Commands
    • Helios2 And Triton Synchronization
  • Knowledge Base
  • Additional Support
    • Product Change Notifications (PCN)
    • Contact Support
  • Log In
home/Knowledge Base/Arena Software/Using ADLINK PCle-GIE72/74 PRO with Trigger Over Ethernet (ToE)

Using ADLINK PCle-GIE72/74 PRO with Trigger Over Ethernet (ToE)

1138 views 3 April 21, 2021 Updated on July 12, 2021

Adlink-Trigger-over-Ethernet

ADLINK’s PCIe-GIE72/74 is a PCI ExpressR x4 lane, GigE Vision PoE+ (Power Over Ethernet Plus) frame grabber that supports 2/4CH independent Gigabit Ethernet ports for multiple GigE Vision device connections with data transfer up to 1 Gb/s per port. The following instructions describe how ADLINK Smart GigE Tool is used to send Action Commands to software trigger LUCID cameras and display in ArenaView.

System Specifications

  • Windows 10 Pro 64-bit, version 2004, Build 19041.867
  • ADLINK Smart GigE Tool, GiE Version:1.5.5.0315 (Driver: 1.2.3.0320, Library: 1.3.5.0315, GIGE Tool: 1.2.5.0324)

Prerequisites

Install the ADLINK Frame Grabber Ethernet interface card into your computer and connect all your LUCID cameras to the card. The card supports PoE but to make sure you have adequate power for all cameras please connect the auxiliary power connector (from your PC power supply) to the internal AUX power supply port on the interface card.

Make sure you have downloaded and installed:

  • PCle-GIE72/74 PRO SmartPoE SDK (execute .exe as administrator)
  • PCle-GIE 72/74 PRO Network Driver (Intel I120 LAN driver)
download adlink sdk

Ethernet IP Address Set up

Assign proper TCP/IP for each PCIe-GIE7x LAN port. (Intel I210 Gigabit Network Connection).

Control Panel -> Network and Internet-> Network and Sharing Center -> Change Adapter setting -> Properties -> Internet Protocol Version 4 (TCP/IPv4) Properties

ipaddress-config1

(Camera IP set to 169.254.1.1)

ipaddress-config2

(Camera IP set to 169.254.2.1)

Camera IP Address Setup

Assign proper persistent IP addresses for each camera in Arena in the following order as shown below:

  • Assign proper GevPersistentIPAddress and GevPersistentSubnetMask.
  • Set GevCurrentIPConfigurationPersistentIP flag to true, GevCurrentIPConfigurationDHCP flag to false, and GevPersistentARPConflictDetectionEnable to false.
  • Power cycle the camera.
camera1-setup-arena
camera2-setup-arena

Camera ToE Parameter Setup

Set TriggerMode to On, and TriggerSource to Action 0 on all cameras:

ToE Arena Setup1
  • Set Action Unconditional Mode On
  • Assign device key, group key, group mask for each camera.
Action-Control1
Action-Control2

Start Streaming

Start Streaming

Using ADLINK Smart GigE Tool

Located: C:\Program Files\ADLINK\GIE Series\GigE Tool

Set up the ToE parameter.

  • Set > Device Key > Group Key > Group Mask
  • Set Action Command for each port:
ADlink SDK ToE

Trigger camera in ADLINK Smart GigE Tool then check the image acquisition on ArenaView.

ADlink-SDK2

Using ToE Samples

Located: C:\Program Files\ADLINK\GIE Series\Samples\ToE Samples\VC\x64\Release

Set up the ToE parameter.

  • Set > Device Key > Group Key > Group Mask
  • Set Action Command for each port:
ToE Samples

Trigger camera in ToE samples then check the image acquisition on ArenaView.

ToE Samples2

For more information on ADLINK’s PCle-GIE72/74 PRO with Trigger Over Ethernet (ToE), please visit ADLINK product page

Was this helpful?

3 Yes  1 No
Related Articles
  • Tonemapping images from LUCID’s TRI054S-CC IMX490
  • Factors for Selecting a PCIe card
  • Default Network Ports for LUCID Cameras
  • Using LUCID’s ArenaView with JupyterLab
  • Using Application Switchover with LUCID Cameras
  • Using Multiple ROIs with LUCID Cameras

Didn't find your answer? Contact Us

  Using Auto Exposure and Auto Gain on LUCID Cameras

Installing PCIE-POE1-MG2 Driver  

© 2023 LUCID Vision Labs Inc.
Looking to purchase our cameras?
Visit the LUCID Webstore at thinklucid.com