Questions?


Get in touch with us today and our team of imaging professionals will be pleased to assist you.

Contact Us

Synchronize Area-Scan Cameras with PTP in eCapture Pro

Use Precision Time Protocol (PTP) in eCapture Pro to start area-scan cameras from a shared PTP timing reference and keep camera timestamps aligned.

This topic describes a typical workflow for configuring and verifying PTP synchronization for area-scan cameras in eCapture Pro.

What PTP does

PTP synchronizes the clocks on connected cameras so they can use a common time reference.

A PTP grandmaster clock is the timing source that provides the shared time reference for the synchronized cameras.

In eCapture Pro, PTP works together with the camera acquisition settings, trigger settings, and frame-rate settings. PTP synchronization is applied when the cameras start streaming.

Note: When you start cameras with PTP enabled, eCapture Pro sets the PTP acquisition gate time for the cameras. Do not manually configure PTP acquisition gate time for this workflow unless Emergent support instructs you to do so.
How PTP synchronization works for area-scan cameras in eCapture Pro

Figure 1: How PTP synchronization works for area-scan cameras in eCapture Pro

PTP use cases

PTP supports different timing workflows.

  • PTP frame synchronization: Area-scan cameras start acquisition from a shared PTP-based timing reference. If you also need frames to stay aligned by frame number, use the same frame rate on all cameras in the synchronized group.
  • PTP timestamping: Cameras use synchronized clocks to timestamp frames, while another mechanism, such as hardware triggering, controls image acquisition.

This topic focuses on PTP frame synchronization for area-scan cameras in eCapture Pro.

Note: Some systems use hardware triggering to control image acquisition and PTP to provide synchronized timestamps. In that workflow, the hardware trigger determines when frames are captured, while PTP keeps camera timestamps aligned. This topic does not describe that workflow.

Example setup

This procedure assumes a system with:

  • One host computer running eCapture Pro.
  • One or more supported NICs.
  • Two or more area-scan cameras.
  • A PTP timing source that all synchronized cameras can use.

This example uses a group of area-scan cameras configured with the same PTP, acquisition, trigger, and frame-rate settings so frames stay aligned by frame number.

Before you begin

Before you configure PTP synchronization, complete these tasks:

  1. Add the local server, NICs, and cameras in System view.
  2. Confirm that the cameras appear in Live View.
  3. Confirm that each camera in the synchronized group supports the selected PTP mode.
  4. Stop streaming before you configure camera parameter values.
Important: To keep frames aligned by frame number, configure the same Frame Rate on all area-scan cameras in the synchronized group. Cameras with different frame rates can still be PTP-synchronized and can start acquisition at the same PTP time, but their frame numbers will not stay aligned. For example, frame 10 from one camera might not have the same timestamp as frame 10 from another camera.
Note: After you change image format, resolution, pixel format, or related camera settings, recheck the frame rate on each camera in the synchronized group.

For more information, see the Software Quick Start Guide.

Configure the PTP and acquisition settings

Configure the same PTP, acquisition, trigger, and frame-rate settings on each area-scan camera in the synchronized group.

  1. In Live View, select the first area-scan camera in the synchronized group.
  2. In the Parameters panel, set Acquisition Mode to MultiFrame.
  3. Set Trigger Mode to On.
  4. Set Trigger Source to Software.
  5. Set Acquisition Frame Count to 1.
  6. Set Ptp Mode to the mode required by the PTP timing source:
    • Use OneStep if the PTP timing source sends one-step PTP packets.
    • Use TwoStep if the PTP timing source sends two-step PTP packets.
  7. To keep frames aligned by frame number, set the same Frame Rate on each area-scan camera in the synchronized group.
  8. Apply the same PTP, acquisition, trigger, and frame-rate settings to each area-scan camera in the synchronized group. If appropriate, broadcast the required parameter values to the other cameras.
Configured Trigger Mode and Trigger Source settings in the LIve View Parameters panel

Figure 2: Trigger Mode and Trigger Source settings in the LIve View Parameters panel

Verify PTP synchronization in Live View

After you configure the cameras, start streaming in Live View to verify that PTP synchronization is working.

  1. In Live View, select each camera in the synchronized group.
  2. Confirm that each camera reports Ptp Status = Slave.
    Note:
    If Ptp Status does not update in the Parameters panel, click the refresh button to poll the camera again.
  3. Start streaming on the cameras.
  4. Confirm that each camera shows a live feed.
  5. Confirm that the camera’s green status square in Live View shows P.
  6. Confirm that Ptp Offset is stable and acceptable for the application.
  7. In Status view, you can monitor PTP offsets and configure error and warning levels for them.
  8. If you configured the cameras with the same frame rate, confirm that frames stay aligned by frame number.
Note: The P indicator shows that the camera started streaming with PTP. Use Ptp Status, Ptp Offset, the live feed, and any available frame timing information to verify synchronization. Do not rely only on the status indicator.
Live View shows the information about PTP synchronization

Figure 3: Live View shows information about PTP synchronization

Troubleshooting

Issue Possible Cause Action
Cameras do not show live video after you start streaming in Live View. The PTP settings are incorrect, the cameras have not locked to the PTP timing source, or the displayed status has not updated. Confirm that each camera reports Ptp Status = Slave. If the status does not update, click the refresh button in the Parameters panel. Check Ptp Mode, the PTP timing source, and the network path.
Ptp Status does not reach Slave. The camera has not locked to the PTP timing source, or the displayed status has not updated. Click the refresh button in the Parameters panel to poll the camera again. Check the selected Ptp Mode, PTP timing source, and network path. Confirm that all cameras can access the same PTP timing source.
Ptp Offset is unstable or too large. Network timing is unstable, the timing source is unstable, or the network path is not suitable for the selected PTP configuration. Check the PTP timing source, network path, and camera PTP settings. The acceptable offset depends on the application requirements.
Cameras acquire frames, but frame numbers do not stay aligned. The cameras use different frame rates, or the PTP, acquisition, or trigger settings do not match. To align frames by frame number, configure the same frame rate on all cameras in the synchronized group. Confirm that the PTP, acquisition, and trigger settings match across the group.
Broadcast settings are unavailable. One or more cameras are streaming. Stop streaming, then broadcast the parameter values again.
Synchronization behavior does not meet application requirements. The standard PTP settings may not match the application requirements. Confirm which timing requirement applies to the application: shared acquisition start, accurate timestamps, frame-number alignment, or PTP offset range. Then review the camera PTP settings, trigger settings, frame-rate settings, and Ptp Offset.

See also

Updated on
June 16, 2026
Questions?


Get in touch with us today and our team of imaging professionals will be pleased to assist you.

Contact Us