Skip to main content

DC IN and I/O Connector

Note

This page includes information regarding both the original Makito X1 chassis and the Makito X1 chassis v2. The Network connector and DC IN/IO connector on v2 have been changed in order to meet higher vibration requirements. 


DC IN & I/O (Power, Audio & Serial) Connector v2


On Unit

Mating Connector

ManufacturerLEMOLEMO
Connector TypeDC IN & I/ODC IN & I/O
Part NumberHEN.2M.312.XLNP

FGN.2M.312.XLCT

For the connector and cable, see Power up the Makito X1 Encoder.

DC IN & I/O Connector Pinout v2

LEMO P1 Contact #Contact NameRS-232 ConnectionsRS-422 Connections
1AUDIO_IN2+

2AUDIO_IN2_GND

3AUDIO_IN1+

4AUDIO_IN1_GND

5

COM 0_TXD+


TXD+
6COM 0_TXD-TXDTXD-
7+5VDC IN

8PSU RETURN

9N/C

10GND SERIALGNDGND
11COM 0_RXD-RXDRXD-
12COM 0_RXD+
RXD+
DC IN & I/O (Power, Audio & Serial) Connector


On UnitMating Connector
ManufacturerHiroseHirose 
Connector TypeDC IN & I/ODC IN & I/O
Part NumberLF13WBRB-11S

LF13WBP-11P

For the connector and cable, see Power up the Makito X1 Encoder.

DC IN & I/O Connector Pinout


Description
Hirose P1 Contact #RS-232
Connections
RS-422
Connections
1

RXD

RXD-
2N/CRXD+
3TXDTXD-
4

N/C

TXD+
5COM 0_GND
Audio / Power
6AUDIO IN CHANNEL 1+
7AUDIO IN CHANNEL 1 GND
AAUDIO IN CHANNEL 2+
BAUDIO IN CHANNEL 2 GND
CPSU RETURN
D+5VDC IN

COM1 Management Pinout (on DB9 connector)

Contact #Signal RS-232Signal RS-422
8
RXD+
7
TXD+
6

5GroundGround
3TXDTXD-
4

1

2RXDRXD-


Note

The COM1 pins are DTE (Data Terminal Equipment) which defines the direction of the signals (IN/OUT).

The COM1 pins are configured by default for Metadata mode but may be switched to Management mode (to connect to a computer for management of the encoder) using the metadata CLI command. The metadata command may also be used to  select the transceiver mode for the metadata capture (i.e., RS-232 or RS-422). For details, see  metadata in the  Makito X1 Rugged Encoder User's Guide .


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.