G3MSG Controller Interfacing¶

The G3MSG controller contains a rich set of I/O interfaces which are discussed in detail in the following sections. The table below lists the on board connectors and pins, ports and busses available on those connectors.

G3MSG I/O Connectors¶
Connector	Port(s)
J1	USB 2.0 Host Port 2
J2	USB 2.0 OTG Port
J3	Power, RS-232 Port
J4	USB 2.0 Host Port 1
J5	Console (Debug) Port
J6	GigaBit Ethernet
J7	RS-485 Port 2
J8	GPIO
J9	UART, I2C Bus
J11	RS-485 Port 1
J12	CAN Bus
J16	USB 2.0 Host Port 1
J17	USB 2.0 Host Port 2
J18	USB 2.0 OTG Port

See location annotatations in the image below showing I/O connectors listed in the previous table.

../../_images/G3MSG-locations.png — G3MSG I/O Connector Locations¶

Power¶

Connect DC power for the G3MSG controller and the touch panel via J3 1. Although the exact power consumption depends on peripherals as well as the particular touch panel, generally, the package will consume approximately 7W to 15W when the backlight is active.

G3MSG controllers must be driven with a 5V, 3A DC power source.

Footnotes:

1: Use Reach Technology “Y” cable, PN 23-0160-18 for 5 VDC.

Console (Debug) Port¶

Access the controller debug interface via J5 2. This RS-232 level serial port runs at 115.2k Baud, 8-bit, no parity, 1 stop bit. This port should always be connected during product development. You will need a terminal emulator program or shell that understands ANSI color escape sequences. Examples include Tera Term or PuTTY 3 (Windows) or picocom in a bash shell (Linux).

Footnotes:

2: Use Reach Technology debug cable, PN 23-0161-72, if you do not wish to build custom cables.
3: We recommend PuTTY because it supports both serial and network connections as well as both Windows 10 and Linux.

RS-232 Port¶

A standard RS-2324 port5 is also available on J3 6.

Footnotes:

4: Standard RS-232 voltage levels
5: The physical UART is connected to both J3 and J9. Obviously, you can not use the port on both of these connectors simultaneously.
6: Use Reach Technology “Y” cable, PN 23-0173-18, if you do not wish to build custom cables.

GigaBit Ethernet¶

A standard 1000baseT network port is available on J6 7.

Footnotes:

7: Use Reach Technology ethernet cable, PN 23-0148-12, if you do not wish to build custom cables.

USB 2.0 Host Port¶

Connect standard USB 1.0 and USB 2.0 peripherals8 to USB host port 1 (J4 9 or J16 10), or USB host port 2 (J1 9 or J17 10).

Footnotes:

8: Some touch panels with HID touch controllers use one of the USB host ports.
9(1,2): Use any standard micro USB cable with this port.
10(1,2): Use Reach Technology USB cable, PN 23-0166-12, if you do not wish to build custom cables.

USB 2.0 OTG Port¶

Note

Currently, the OTG port is only supported in host mode. Contact Reach Technology if you need to use it in device mode.

If the USB 2.0 Host Ports are already in use,11 or you want to use the G3MSG as a USB device12 rather than as a host, you can use the USB 2.0 OTG port on J2 or J18. This port is capable of being either a host port13 or a device port14; J2 is used with a standard micro USB cable.

Footnotes:

11: For example by an HID touch controller.
12: For example as a Linux Network Gadget for peer to peer USB networking.
13: Use Reach Technology USB Host cable, PN 23-0167-12, if you do not wish to build custom cables.
14: Use Reach Technology USB Device cable, PN 23-0168-12, if you do not wish to build custom cables.

CAN Bus¶

A CAN bus connection is available on J12 15.

Footnotes:

15: Use Reach Technology CAN flying leads cable, PN 23-0146-10, for prototyping.

UART¶

Warning

Refrain from using the logic level UART on J9 at the moment. It is the same UART used on J3, but without the RS-232 transceiver. Unfortunately, there is currently a hardware design error that does not allow the RS-232 receive pin transceiver driver to be disabled. This wil be corrected in the first board spin.

A logic level16 serial port17 is available on J9 18.

Footnotes:

16: CMOS voltage levels.
17: The physical UART is connected to both J3 and J9. Obviously, you can not use the port on both of these connectors simultaneously.
18: Use Reach Technology I²C/UART flying leads cable, PN 23-0149-10, for prototyping.

I²C Bus¶

The I²C Bus is also available on J9 19.

Footnotes:

19: Use Reach Technology I²C/UART flying leads cable, PN 23-0149-10, for prototyping.

GPIO¶

GPIO pins are available on J8 20

Footnotes:

20: Use Reach Technology GPIO flying leads cable, PN 23-0144-10, for prototyping.

RS-485 Port¶

RS-485 peripherals can be connected to J7 and to J11 21. The default mode is full duplex.

Footnotes:

21: Use Reach Technology RS-485 flying leads cable, PN 23-0145-10, for prototyping.

Connector Pinouts and Part Numbers¶

The following sections provide the pinout for each connector and part number for the required mating plug22.

Footnotes:

22: For the USB micro AB connectors, we provide the part number of the on board socket. Any standard micro USB plug should mate with this connector.

J1¶

../../_images/J1-J17.png — G3MSG USB 2.0 Host Port 2 Connection¶

5 pin USB micro AB, MOLEX Part # 0475890001

J1 Pinout¶
Pin	Signal
1	+5V
2	Data -
3	Data +
4	NC
5	GND

../../_images/USB-HP2.png — G3MSG USB 2.0 Host Port 2 Schematic¶

J2¶

../../_images/J2-J18.png — G3MSG USB 2.0 OTG Port Connection¶

5 pin USB micro AB, MOLEX Part # 0475890001

J2 Pinout¶
Pin	Signal
1	+5V
2	Data -
3	Data +
4	USB_OTG_ID23
5	GND

../../_images/USB-OTG2.png — G3MSG USB 2.0 OTG Port Schematic¶

Footnotes:

23: Ground to make J5 a USB Host port.

J3¶

../../_images/J31.png — G3MSG Power / RS-232 Connection¶

8 pin Pico-SPOX, MOLEX Part # 87439-0800

J3 Pinout¶
Pin	Signal
1	TxD output ESD protected24^,25
2	RxD input ESD protected24^,25
3	GND (power and communications)
4	VIN 5VDC input, powers the board
5	VIN 5VDC input, powers the board
6	GND (power and communications)
7	GND (power and communications)
8	GND (power and communications)

../../_images/PWR-RS2322.png — G3MSG Debug Interface, Power, RS-232 Schematic¶

Footnotes:

24(1,2): For ESD protection details, refer to the specifications of the ICL3222E transceiver chip.
25(1,2): This port uses USART2 and is common with the logic level port on J9. It cannot be used simultaneously from both connectors.

J4¶

../../_images/J4-J16.png — G3MSG USB 2.0 Host Port 1 Connection¶

5 pin USB micro AB, MOLEX Part # 0475890001

J4 Pinout¶
Pin	Signal
1	+5V
2	Data -
3	Data +
4	NC
5	GND

../../_images/USB-HP1.png — G3MSG USB 2.0 Host Port 1 Schematic¶

J5¶

../../_images/J51.png — G3MSG Debug Interface Connection¶

5 pin PicoBlade, MOLEX Part # 51021-0500

J5 Pinout¶
Pin	Signal
1	TxD output ESD protected26
2	RxD input ESD protected26
3	CTS
4	GND
5	GND

Footnotes:

26(1,2): Internal ESD protection as specified for the ICL3222E device, +/- 16 KV.

J6¶

../../_images/J61.png — G3MSG GigaBit Ethernet Connection¶

9 pin Pico-SPOX, MOLEX Part # 87439-0900

J6 Pinout¶
Pin	Signal
1	Bi-Directional pair D1+
2	Bi-Directional pair D1-
3	Bi-Directional pair D2+
4	Bi-Directional pair D2-
5	Bi-Directional pair D3+
6	Bi-Directional pair D3-
7	Bi-Directional pair D4+
8	Bi-Directional pair D4-
9	Ethernet Shield/GND

../../_images/Enet2.png — G3MSG GigaBit Ethernet Schematic¶

J7¶

../../_images/J71.png — G3MSG RS-485 Port 2 Connection¶

7 pin PicoBlade, MOLEX Part # 51021-0700

J7 Pinout¶
Pin	Signal
1	Rx H
2	Rx L
3	Tx L
4	Tx H
5	+5V
6	GND
7	GND

../../_images/RS485-2.png — G3MSG RS-485 Port 2 Schematic¶

J8¶

../../_images/J8.png — G3MSG GPIO Connection¶

11 pin PicoBlade, MOLEX Part # 51021-1100

J8 Pinout¶
Pin	Signal
1	GP3
2	GP2
3	GP1
4	GP0
5	GP4
6	GP5
7	GP6
8	GP7
9	+5V
10	GND
11	GND

../../_images/GPIO1.png — G3MSG GPIO Schematic¶

J9¶

../../_images/J9.png — G3MSG UART / I²C Bus Connection¶

10 pin PicoBlade, MOLEX Part # 51021-1000

J9 Pinout¶
Pin	Signal
1	USART2_RX27^,28
2	USART2_TX27^,28
3	USART2_CTS27^,28
4	USART2_RTS27^,28
5	PF229
6	I2C2_SCL_BUF
7	I2C2_SDA_BUF
8	GND
9	+5V
10	GND

../../_images/I2C-UART.png — G3MSG UART / I²C Bus Schematic¶

Footnotes:

27(1,2,3,4): Do Not Use - HW errata on RX
28(1,2,3,4): This port uses USART2 and is common with the RS-232 level port on J3. It cannot be used simultaneously from both connectors.
29: (WTHIT??? Looks like an input, +5 should turn on D5)

J11¶

../../_images/J11.png — G3MSG RS-485 Port 1 Connection¶

7 pin PicoBlade, MOLEX Part # 51021-0700

J11 Pinout¶
Pin	Signal
1	Rx H
2	Rx L
3	Tx L
4	Tx H
5	+5V
6	GND
7	GND

../../_images/RS485-1.png — G3MSG RS-485 Port 1 Schematic¶

J12¶

../../_images/J12.png — G3MSG CAN Bus Connection¶

6 pin PicoBlade, MOLEX Part # 51021-0600

J12 Pinout¶
Pin	Signal
1	CAN +
2	CAN -
3	+5V
4	+5V
5	GND
6	GND

../../_images/CAN1.png — G3MSG CAN Schematic¶

J16¶

5 pin Pico-SPOX, MOLEX Part # 87439-0500

J16 Pinout¶
Pin	Signal
1	+5V
2	Data -
3	Data +
4	GND
5	GND shield

J17¶

5 pin Pico-SPOX, MOLEX Part # 87439-0500

J17 Pinout¶
Pin	Signal
1	+5V
2	Data -
3	Data +
4	GND
5	GND shield

J18¶

6 pin Pico-SPOX, MOLEX Part # 87439-0600

J18 Pinout¶
Pin	Signal
1	+5V
2	Data -
3	Data +
4	USB_OTG_ID30
5	GND
6	GND shield

Footnotes:

30: Ground to make J18 a USB Host port.

G3MSG Controller Interfacing¶

Power¶

Console (Debug) Port¶

RS-232 Port¶

GigaBit Ethernet¶

USB 2.0 Host Port¶

USB 2.0 OTG Port¶

CAN Bus¶

UART¶

I2C Bus¶

GPIO¶

RS-485 Port¶

Connector Pinouts and Part Numbers¶

J1¶

J2¶

J3¶

J4¶

J5¶

J6¶

J7¶

J8¶

J9¶

J11¶

J12¶

J16¶

J17¶

J18¶

I²C Bus¶