# Electrical Interfaces & Connectors

{% hint style="danger" %}
**WARNING:**  All electrical signal connections and disconnections must be made with the device in a powered-off state.
{% endhint %}

## Laser Emission Interlocks (all configurations)

All Axsun laser engines expose interlock inputs for the swept laser emission and aiming laser emission, as shown in the detailed diagrams below for each engine configuration.

If the **Swept Laser Interlock** is tripped (i.e. pulled to GND or allowed to float by an external circuit), the swept laser emission will be disabled within 2 microseconds.  

A tripped Swept Laser Interlock will latch the swept laser emission into a disabled state, and two distinct steps are then required to re-enable swept laser emission:

1. Reconnect the Swept Laser Interlock input to \~3.3V, *then*
2. Explicitly re-issue the "Swept Laser Emission -> ON" command, either via software interface (API or GUI tool) or by toggling the Swept Laser Emission On/Off Control input.

A tripped **Aiming Laser Interlock** does not latch the aiming laser into the disabled state and thus the aiming laser emission can be reenabled by reconnecting the Aiming Laser Interlock input to \~3.3V (no additional emission-on command is needed).

{% hint style="info" %}
**NOTE:**  Disabling swept laser emission or aiming laser emission in response to a tripped interlock input is accomplished in hardware logic only; there is no software or firmware interaction involved in this behavior.
{% endhint %}

{% hint style="info" %}
**NOTE:**  Axsun laser engines typically ship with a temporary mating connector for the **Auxiliary & Interlocks** receptacle whose pins are jumpered appropriately to allow laser emission (i.e. the interlocks are *not* tripped when this connector is installed).  The user is expected to replace this temporary mating connector once external watchdog circuitry is implemented in order to control the laser emission interlock behavior.
{% endhint %}

## Azmyth™ OEM Laser Engine

The Azmyth OEM engine is provided with a 100-240 VAC external auto-switching power supply which supplies 12 V / 3.3 A. The external power supply is plugged into the power socket of an adapter cable provided with the Azmyth engine.  Outputs for the Sweep Trigger and K-clock (if installed) are available on both SMA (single-ended signaling) and SATA (differential signaling) connector types.

<figure><img src="/files/uMl9x8P8r5WI98oeCcW4" alt=""><figcaption></figcaption></figure>

## Benchtop Enclosure

The Benchtop Enclosure configuration is provided with an external AC/DC converter which supplies \~12 VDC from 100-240 VAC mains.  This external power supply's cable is plugged into the "12 VDC" socket on the rear panel of the enclosure.

![](/files/-MUVSjGzJrFKnHCFw_7b)

## Standard OEM Engine

The OEM engine is provided with a 100-240 VAC external auto-switching power supply which supplies 12 V / 3.3 A. The external power supply is plugged into the power socket of an adapter cable provided with the OEM engine.&#x20;

![](/files/-MUVSt_mDyiDbGtC36uM)

## Small Form Factor Engine

The SFF engine is provided with a 100-240 VAC external auto-switching power supply which supplies 12 V / 3.3 A. The external power supply is plugged into the power socket of an adapter cable provided with the SFF engine.

![](/files/-MUVT2WMRhfz1sWAF7Yk)

## Integrated Engine w/ Ethernet DAQ

The OEM engine with Ethernet DAQ is provided with a 100-240 VAC external auto-switching power supply which supplies 12 V / 3.3 A. The external power supply is plugged into the power socket of an adapter cable provided with the OEM engine.

![](/files/-MUVT9SRzEHQo6AyTNFI)

![](/files/-MUVTFCji88urbtqRlNg)

## Integrated Engine w/ Camera Link DAQ

The OEM engine with Camera Link DAQ is provided with a 100-240 VAC external auto-switching power supply which supplies 12 V / 3.3 A. The external power supply is plugged into the power socket of an adapter cable provided with the OEM engine.

![](/files/-MUVTNL3rhADWpmWyOrf)

![](/files/-MUVTR1pZYal5bD1oAV4)

## PCIe DAQ (500 MS/s)

![](/files/-MVICjerZ9frGdJU8slT)

## PCIe DAQ (900 MS/s)

AXP52013-1 & AXP52013-2&#x20;

<figure><img src="/files/u070dxv3lR3il7lrKZ6H" alt=""><figcaption></figcaption></figure>

**Ch 1 & Ch 2 Input**

Connect via supplied [SATA cable](/axsun-knowledge-base/ref-manual/ss-oct-laser-engine/accessories.md#sata-cables) to OCT Balanced Receiver output on Laser Engine.

**K-clock & Sweep Trigger Input**

Connect via supplied [SATA cable](/axsun-knowledge-base/ref-manual/ss-oct-laser-engine/accessories.md#sata-cables) to K-clock & Sweep Trigger output on Laser Engine.

**Power Input**

Connect via supplied DC [Power Y Cable](/axsun-knowledge-base/ref-manual/ss-oct-laser-engine/accessories.md#power-y-cable) to [AC/DC Power Adapter](/axsun-knowledge-base/ref-manual/ss-oct-laser-engine/accessories.md#ac-dc-power-adapter-and-ac-power-cord) and mains power, or deliver power according to:

<table><thead><tr><th valign="top">Pinout</th><th valign="top">Connector</th></tr></thead><tbody><tr><td valign="top"><ol><li>12 Vdc INPUT</li><li>GND</li><li>no connect</li><li>12 Vdc INPUT</li><li>GND</li><li>no connect</li></ol></td><td valign="top"><p>Molex Micro-Fit 3.0</p><p></p><p>Receptacle:  MOLEX 43045-0608</p><p>Plug Housing:  MOLEX 43025-0600</p></td></tr></tbody></table>

{% hint style="info" %}
**NOTE:** This board can also be PCIe bus-powered. See [here](/axsun-knowledge-base/how-tos/using-bus-power-for-the-pcie-daq.md) for instructions.
{% endhint %}

**USB 2.0**

Connect to host PC via supplied [USB A to Mini-B cable](/axsun-knowledge-base/ref-manual/ss-oct-laser-engine/accessories.md#usb-cable) (or any USB cable with a Mini-B connector).

**1G Ethernet**

Connect to host PC via Cat 6 Ethernet cable (not supplied; needed only if using Ethernet interface).

**Sweep Trigger Output**

Connect via SMA-terminated coax cable to an external device (if needed for synchronization of external device to the laser sweep trigger).

**Aux I/O (Front)**

<table><thead><tr><th valign="top">Pinout</th><th valign="top">Connector</th></tr></thead><tbody><tr><td valign="top"><ol><li>Differential LVDS(+) INPUT</li><li>Differential LVDS(-) INPUT</li><li>GND</li><li>Single-Ended LVCMOS INPUT</li><li>GND</li><li>Sweep Trigger OUTPUT (2.5V)</li></ol></td><td valign="top"><p>Molex CLIK-Mate</p><p></p><p>Receptacle:  MOLEX 503175-0600</p><p>Plug Housing:  MOLEX 502578-0600</p></td></tr></tbody></table>

**Aux I/O (Rear)**

<table><thead><tr><th valign="top">Pinout</th><th valign="top">Connector</th></tr></thead><tbody><tr><td valign="top"><ol><li>Single-Ended LVCMOS2 INPUT</li><li>GND</li><li>Single-Ended LVCMOS INPUT</li><li>GND</li><li>n/c</li><li>n/c</li><li>Differential LVDS(+) INPUT</li><li>Differential LVDS(-) INPUT</li><li>thru 12.  n/c</li></ol></td><td valign="top"><p>Molex iGrid </p><p></p><p>Receptacle:  MOLEX 501876-1240</p><p>Plug Housing:  MOLEX 501646-1200</p></td></tr></tbody></table>

{% hint style="info" %}
**NOTE:** Configure the external signal source input line on the Front or Rear Aux I/O connector to be used for initiating a Burst Record operation and for selecting the Image\_sync input according to [Advanced DAQ Features](/axsun-knowledge-base/ref-manual/gigabit-ethernet-daq-board/advanced-operation.md#selecting-the-image_sync-input) via the [Hardware Control Tool](/axsun-knowledge-base/software-tools/hardware-control-tool.md#miscellaneous) GUI or [AxsunOCTControl\_LW API](/axsun-knowledge-base/api-references/axsunoctcontrol-lightweight.md) function calls.
{% endhint %}

## Interface Board (SATA to SMA Connectors)

Refer to [this page](/axsun-knowledge-base/how-tos/using-the-interface-board.md) for more information about connecting the Interface Board.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.axsun.com/axsun-knowledge-base/ref-manual/electrical-interfaces-and-connectors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.