What are you looking for?

Line Scan Acquisition Use cases

Scanning of continuous objects

This case applies to the image scanning of continuous objects.

The Coaxlink acquisition controller is configured as follows:

  • StartOfScanTriggerSource = Immediate.
  • EndOfScanTriggerSource = StopScan.

When the DSStartAcquisition function is called, the scanning starts at the next line boundary.

The acquisition gate closes when the application calls the DSStopAcquisition function.

Depending on the allocated buffer size and the scanning duration, the object image fits in a single buffer or requires multiple buffers.

Each buffer is delivered to the application as soon as it is filled. The last buffer, likely partially filled, is delivered as soon as the last image data are written.

Fixed-length scanning of discrete objects

This case applies to the scanning of discrete objects with a common scan length.

The Coaxlink acquisition controller is configured as follows:

  • StartOfScanTriggerSource = StartScan or any applicable I/O Toolbox event output, for instance: LIN1.
  • EndOfScanTriggerSource = ScanLength.
  • ScanLength = any positive number representing the number of lines required to capture the object image entirely.

When the DSStartAcquisition function is called, the start-of-scan trigger of the acquisition controller is armed.

Then, the acquisition controller waits for the first occurrence of a valid start-of-scan trigger event.

A valid start-of-scan event can be generated:

  • By the application using a StartScan command.
  • By the selected hardware event source, if specified by StartOfScanTriggerSource.

The acquisition controller ignores any Start-of-Scan trigger event while a scanning is in progress.

The acquisition gate opens at the first line boundary following a start-of-scan event.

The acquisition gate closes automatically after the specified number of lines have been acquired or anticipatively when the application calls the DSStopAcquisition function.

Depending on the allocated buffer size, the object image fits in a single buffer or requires multiple buffers. Each buffer is delivered to the application as soon as it is filled. At the end-of-scan, partially filled buffers are immediately delivered. The following image acquisition always begins with a new buffer.

Variable-length scanning of discrete objects

This case applies to the image scanning of discrete objects requiring a variable scan length.

The Coaxlink acquisition controller is configured as follows:

  • StartOfScanTriggerSource = StartScan or any applicable I/O Toolbox event output, for instance: LIN1.
  • EndOfScanTriggerSource = StopScan or any applicable I/O Toolbox event output, for instance: LIN2.

When the DSStartAcquisition function is called, the start-of-scan trigger of the acquisition controller is armed.

Then, the acquisition controller waits for the first occurrence of a valid start-of-scan trigger event.

A valid start-of-scan event can be generated:

  • By the application using a StartScan command.
  • By the selected hardware event source, if specified by StartOfScanTriggerSource.

The acquisition controller ignores any Start-of-Scan trigger event while a scanning is in progress.

The acquisition gate opens at the first line boundary following a start-of-scan event.

The acquisition gate closes at the first line boundary following a valid end-of-scan event or immediately when the application calls the DSStopAcquisition function.

A valid end-of-scan event can be generated:

  • By the application using a StopScan command.
  • By the selected hardware event source, if specified by EndOfScanTriggerSource.

The acquisition controller ignores any End-of-Scan trigger event when no scanning is in progress.

Depending on the allocated buffer size, the object image fits in a single buffer or requires multiple buffers. Each buffer is delivered to the application as soon as it is filled. At the end-of-scan, partially filled buffers are immediately delivered. The next image acquisition always begins with a new buffer.