The MeshScape Go OEM Module comes with a development board with screw terminals to facilitate easy connection to input and output channels. The following tables show pin assignment on the two screw terminals (P9 and P10) on the development board.
P9 Screw Terminal Block Pin Assignment |
Pin # |
Pin Label |
Input/Output |
Pin Function |
1 |
GND |
Power |
Digital ground |
2 |
DIO0 / RxD |
I/O or Output Digital |
Input/Output 0 or UART RX |
3 |
DIO1 / TxD |
I/O or Input Digital |
Input/Output 1 or UART TX |
4 |
DIO2 / RTS |
I/O or Input Digital |
Input/Output 2 or UART RTS in |
5 |
DIO3 / CTS |
I/O or Output Digital |
Input/Output 3 or UART CTS out |
6 |
DIO4 |
|
Reserved |
7 |
DIO5 |
|
Reserved |
8 |
SDI |
|
Reserved |
9 |
SDO |
|
Reserved |
10 |
SCK |
|
Reserved |
11 |
DEV_BIND |
|
Reserved |
12 |
MCU_PWR |
|
Reserved |
P10 Screw Terminal Block Pin Assignment |
Pin # |
Pin Label |
Input/Output |
Pin Function |
1 |
GND |
Power |
Digital ground |
2 |
AD0 |
Input |
Analog Input 1 |
3 |
AD1 |
Input |
Analog Input 2 |
4 |
AD2 |
Input |
Analog Input 3 |
5 |
AD3 |
Input |
Analog Input 4 |
6 |
LED1 |
|
Reserved |
7 |
LED2 |
|
Reserved |
8 |
CP_TxD |
|
Reserved |
9 |
CP_RxD |
|
Reserved |
10 |
RFM_RST |
|
Reserved |
11 |
CB_PRSNT |
|
Reserved |
12 |
3.3V |
Power |
Board output power |
Data from all devices in MeshScape Go network is stored in Modbus holding registers in MeshGate’s (gateway) database. Host applications communicating with MeshGate can retrieve data from and send commands to MeshScape Go OEM module by issuing Modbus read and write requests to MeshGate. All wireless devices in the MeshScape network, including the MeshGate, operate as Modbus slave devices; host application communicating with the MeshGate should be the Modbus master.
Data packet from an external device connected to MeshScape Go OEM Module should follow Modbus write command data format with a special header at the beginning. When MeshGate receives this packet it can properly place the data in the correct holding registers for the specified Modbus slave device. Note that MeshScape Go OEM Module only supports interrupt driven data transmission, i.e. the external device such as a sensor or an electric meter should pull the interrupt pin on the UART interface to trigger data transmission. It does not poll the external device.
Data generated by the external device will be stored in MeshGate’s database as Modbus registers identifiable based on the slave ID of MeshScape Go OEM Module that the external device is connected to. The host application communicating with MeshGate can retrieve data of every external device in the MeshScape network by sending a Modbus read request to MeshGate to read specific slave ID register values. For further information on Modbus interface with MeshGate, please contact Millennial Net for additional documentation.