LogoLogo
Software DownloadsDatasheetsRequest Support
  • Axsun Knowledge Base
  • OCT Product Configurations
  • Essential Information Guide
  • Getting Started Guides
    • SS-OCT Laser Engine
    • Integrated Engine (Laser & DAQ)
      • Making Connections
      • Installing Software
      • Operating the Integrated Engine
  • Reference Manuals
    • Dimensions
    • Electrical Interfaces & Connectors
    • Environmental Requirements
    • SS-OCT Laser Engine
      • Advanced Laser Engine Features
      • Laser Accessories
      • Laser Test Report
      • Frequently Asked Questions
      • Laser Troubleshooting
    • Ethernet/PCIe DAQ Board
      • Architecture & Interface Background
      • Basic Operation
      • Advanced DAQ Features
      • FPGA Register Reference
      • Frequently Asked Questions
      • DAQ Troubleshooting
    • Camera Link DAQ Board
  • How-Tos
    • Upgrading Board Firmware
    • Upgrading FPGA Bitstreams
    • Using AxsunOCTControl.dll in C++
    • Operating a Variable Delay Line
    • Using the Interface Board
    • Installing the PCIe Device Driver
  • Using Bus Power for the PCIe DAQ
  • Software Tools
    • OCT Host
    • Hardware Control Tool
    • Image Capture Tool
  • API References
    • AxsunOCTControl (.NET)
      • Using the Control.NET API
      • AxsunOCTControl Function Reference
    • AxsunOCTControl_LW (light-weight)
      • Using the Control_LW API
      • AxsunOCTControl_LW Function Reference
    • AxsunOCTCapture
      • Using the Capture API
      • Linux Installation
      • AxsunOCTCapture Function Reference
  • Other
    • Software Downloads
    • Datasheets
    • References
    • Contact Excelitas For Help
      • Tech Support Request Form
Powered by GitBook

© 2025 Excelitas Technologies

On this page
  • Image Capture Tool
  • Hardware Control Tool
  • API Integration
  • Interfaces
  • Hardware Configuration

Was this helpful?

  1. Reference Manuals
  2. Ethernet/PCIe DAQ Board

Frequently Asked Questions

PreviousFPGA Register ReferenceNextDAQ Troubleshooting

Last updated 3 years ago

Was this helpful?

Image Capture Tool

Q: Why does the Image Capture Tool not display live images after reviewing a set of previously recorded or reloaded images, even though I commanded the DAQ board back into Live Imaging mode?

Check that the Requested Image # control is set to 0. This value returns the most recently captured image, rather than a previously captured and uniquely numbered image which is returned when this control is set to a non-zero value.

Q: Why does the number of A-Scans in a displayed image (the Width) change erratically from one image to the next?

Q: Why are the Image_sync Trigger Too Fast or Image_sync Too Slow (Force Trig) indicators on?

When the Image_sync frequency is too high such that fewer than 256 A-scans are captured between consecutive rising edges, a Trigger Too Fast warning will occur and the image display may appear erratic if synchronization is temporarily lost.

When the Image_sync frequency is too slow or the signal is nonexistent, a Force Trigger event will occur and the displayed image will contain the most recently captured 256 A-scans, in a fashion similar to the way an oscilloscope typically behaves when a trigger signal is not detected.

Q: How do I open .dat buffer files saved using the Image Capture Tool?

Buffer files saved using the Image Capture Tool or the axSaveFile(..) API command use a custom format which includes the image data as well as other metadata and are only interpretable by the Capture API.

Q: Why is the number of pixels per A-line always equal to 1024?

Q: Why do objects in the image appear to flip or "mirror" at the top and bottom of the generated image?

Mirroring artifacts at the top and bottom of images are common in Fourier Domain OCT. Mirroring at the top of the image comes from the complex conjugate property of the Fourier transform, and the mirroring at the bottom comes from aliasing (frequency content higher than Nyquist). These artifacts are not specific to the Axsun system; rather, any FD-OCT system employing an FFT (swept source or spectrometer-based) will exhibit these phenomena.

Q: Why can't I increase the scan depth of my OCT system programmatically?

The maximum scan depth is fixed during system manufacturing and is based on the optical path length delay in the integrated k-clock interferometer. Reduction of the scan depth can be accomplished in software by simply cropping out regions from the generated images after they are retrieved into a client application.

Hardware Control Tool

Q: What is the meaning of the Width (samples) setting in the Windowing LUT Setup?

API Integration

Use AxsunOCTControl.dll if you are creating an application in C# or in a managed language which supports straightforward binding of Microsoft .NET assemblies on a 32- or 64-bit Windows platform, and if you are only interacting with the DAQ's basic features.

Interfaces

Q: Should I use the Ethernet or PCIe interface?

The Ethernet interface enables compact system architectures and requires bandwidth reduction via A-line subsampling when using the Bypass (Pipeline Mode) functionality to access upstream data during system integration, optimization, and debugging. Depending on your PC capabilities and resource usage from unrelated processes, Gigabit Ethernet speeds of approximately 850 Mbps are realizable with minimal or no packet loss.

Hardware Configuration

The image width is determined automatically by the period of the Image_sync synchronization pulse introduced by the user from an external source. Check that the Image_sync connection to the DAQ board is robust and has a constant period. Also check that the .

Use the Image Capture Tool's LOAD BUFFER FROM FILE button on the Buffer tab, or use the axLoadFile(..) API command in .

Each A-line is computed by Fourier transforming an . Due to symmetry properties of the Fourier transform, half of the resulting transformed data is redundant and thus the vector length in all subsequent processing blocks is truncated to 1024 pixels.

Each system produces a specific number of k-clock pulses based on the laser's wavelength tuning range and the k-clock configured scan depth. These k-clock pulses are used to directly control the sampling of the analog-to-digital converters and the number of samples (N)(N)(N) typically falls between 1024 and 2048 (your system's exact value can be found on your ). Because the Fourier transform computation requires input data with power-of-2 length, the sampled data is zero-padded from NNN up to 2048 points in the same step as apodization/windowing and dispersion compensation. The Width (samples) setting is the number of valid points in the programmed window function (should be set = NNN) and then 2048–NNN zeros are automatically appended to make the total number of points equal to 2048. If the Width(samples) setting is higher than the actual valid number of samples produced (N)(N)(N), then invalid or spurious samples may not be zeroed-out and will likely cause artifacts in the computed image.

Q: Should I use the library or library when I'm designing a custom client application?

Use AxsunOCTControl_LW.dll if you are either creating an application for a non-Windows platform or are coding in a language other than C# and would like to avoid . The AxsunOCTControl_LW library is also highly recommended for users interacting with the DAQ's advanced features (beyond basic operational mode selection).

On the other hand, the PCIe interface provides sufficient bandwidth to access Raw ADC Data at full A-line rates up to 100 kHz (without subsampling) but also requires being plugged into the PCIe slot of a desktop or workstation PC, or alternatively requires the use of a PCIe expansion .

Q: I have an Integrated Engine with DAQ in the PCIe configuration, but physical constraints require that my laser and DAQ be so far apart that the legs of the cannot reach both components.

to purchase a second AC/DC supply and cable accessories for powering the two components separately, or procure a jumper to extend one leg of your existing Power Y Cable as needed to reach both components. Due to the wide range of possible physical configurations when the laser and DAQ are separated, Axsun cannot supply a 'one-size-fits-all' Power Y Cable. Connector details are .

AxsunOCTCapture.dll
AxsunOCTControl
AxsunOCTControl_LW
accessing AxsunOCTControl.dll through COM assembly registration
Thunderbolt chassis
Contact Axsun
provided here
input vector with length of 2048
laser test report
Power Y Cable
correct Image_sync input (LVCMOS, LVDS, or internal) is selected