This chapter describes the Sirius series pinout and gives details about the supported communication interfaces.
Below figure shows the pin configuration of the Xsens Sirius series robust tracker.
.png?Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiaHR0cHM6Ly9kemY4dnF2MjRlcWhnLmNsb3VkZnJvbnQubmV0L3VzZXJmaWxlcy8yNzc1NC8zNTEzNS9ja2ZpbmRlci9pbWFnZXMvcXUvMjAyNi9pbWFnZSgxKS5wbmciLCJDb25kaXRpb24iOnsiRGF0ZUxlc3NUaGFuIjp7IkFXUzpFcG9jaFRpbWUiOjE3ODA2NzM0ODF9fX1dfQ__&Signature=W0LJQb58lXk5LRPlA0csgSVGMAhWWf973ovylR~akOHlCMCd2X8CJfadxTk9lTBbk4iIjicFDc8JqDgkZYwla-pz6Dsuc~cT6evZjDEmNO5dZ6m4lnjRiNs3MI5cFTfBiTyjdUKdiaDsR8vAaDmXbVqol9aH18J8irZyEeIPwKhOf37dqP9U2X2WBJbiQItiE-nP1GB0JTX1s-yK~XWFw67C2F1D77a~Jh8~ddUJUxUyqN5U6XP8Kx1Am5CuFOqacxmtkeoAQxMJIx71HDXOenhaFpFtwSWSmsqjOVMQgeM22MgJxaMKqyO5-FCR-J~VN-LpN3LQ3vd7lGSc~v91tQ__&Key-Pair-Id=K2TK3EG287XSFC)
Pin configuration of the Xsens Sirius series robust tracker: IMU/VRU/AHRS (left) and GNSS/INS (right)
Below table shows the pin descriptions of the Xsens Sirius series robust tracker based on the interface variant.
Pin descriptions Rugged Sirius Host Interface with RS232
|
Pin |
Name |
I/O type |
Description |
|
1 |
CAN_H |
I/O |
CAN(-FD) bus differential high side |
|
2 |
CAN_L |
I/O |
CAN(-FD) bus differential low side |
|
3 |
SYNC_IN1 |
I |
Multifunctional synchronization input |
|
4 |
SYNC_IN2 (IMU/VRU/AHRS)
PPS_OUT (GNSS/INS) |
I (IMU/VRU/AHRS)
O (GNSS/INS) |
Multifunctional synchronization input (IMU/VRU/AHRS)
Pulse per second output from GNSS module (GNSS/INS) |
|
5 |
VIN |
PWR |
Power input |
|
6 |
RS232_CTS |
I |
RS232 Clear To Send input from host |
|
7 |
RS232_RxD |
I |
RS232 receiver input from host |
|
8 |
RS232_TxD |
O |
RS232 transmitter output to host |
|
9 |
RS232_RTS |
O |
RS232 Ready To Send output to host |
|
10 |
GND |
PWR |
Ground |
|
11 |
SYNC_OUT |
O |
Configurable synchronization output |
|
12 |
GND |
PWR |
Ground |
Pin descriptions Rugged Sirius Host Interface with RS422
|
Pin |
Name |
I/O type |
Description |
|
1 |
CAN_H |
I/O |
CAN(-FD) bus differential high side |
|
2 |
CAN_L |
I/O |
CAN(-FD) bus differential low side |
|
3 |
SYNC_IN1 |
I |
Multifunctional synchronization input |
|
4 |
SYNC_IN2 (IMU/VRU/AHRS)
PPS_OUT (GNSS/INS) |
I (IMU/VRU/AHRS)
O (GNSS/INS) |
Multifunctional synchronization input (IMU/VRU/AHRS)
Pulse per second output from GNSS module (GNSS/INS) |
|
5 |
VIN |
PWR |
Power input |
|
6 |
RS422_B |
I |
RS422 inverted receiver input from host |
|
7 |
RS422_A |
I |
RS422 non-inverted receiver input from host |
|
8 |
RS422_Z |
O |
RS422 inverted transmitter output to host |
|
9 |
RS422_Y |
O |
RS422 non-inverted transmitter output to host |
|
10 |
GND |
PWR |
Ground |
|
11 |
SYNC_OUT |
O |
Configurable synchronization output |
|
12 |
GND |
PWR |
Ground |
Pin descriptions Sirius RTK GNSS/INS RTCM corrections connector
|
Pin |
Name |
I/O type |
Description |
|
1 |
V_BCKP |
PWR |
Backup supply for GNSS (3.3V) |
| 2 | GND | PWR | Ground |
| 3 | RTCM_RxD | I | RS232 receiver input from RTCM host |
| 4 | RTCM_TxD | O | RS232 receiver output from RTCM host |
The rugged Sirius series supports CAN(-FD), and RS232 or RS422 interfaces for host communication. For more detailed information on the interfaces please refer to the Sirius series Hardware Integration Manual.
A Controller Area Network (CAN bus) is a robust standard designed to allow communication between devices in applications without a host computer. By default the CAN interface of the Sirius series does not have a termination resistor enabled. It can be used in a CAN bus that already incorporates the required termination. If used in a single device connection or when placed at the end of a CAN bus, the internal 120 Ω termination resistor can be enabled.
The RS232 interface complies with the standard RS232 voltage levels. It includes hardware flow control (from firmware version 1.1.0 onwards) through the RTS and CTS lines. The RS232 frame configuration is 8 data bits, no parity and 1 stop bit (8N1).
The CTS signal is an input for the device. The device checks the state of the CTS line at the start of every byte it transmits. If CTS is high, the module transmits the byte. Otherwise, it postpones transmission until CTS is raised. When during the transmission of a byte the user lowers the CTS signal, then the device completes transmission of that byte before postponing further output. The device will not retransmit this byte. Figure 1 shows the behavior of the TX and CTS lines.
.png?Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiaHR0cHM6Ly9kemY4dnF2MjRlcWhnLmNsb3VkZnJvbnQubmV0L3VzZXJmaWxlcy8yNzc1NC8zNTEzNS9ja2ZpbmRlci9pbWFnZXMvcXUvMjAyNi9pbWFnZSgyKS5wbmciLCJDb25kaXRpb24iOnsiRGF0ZUxlc3NUaGFuIjp7IkFXUzpFcG9jaFRpbWUiOjE3ODA2NzM0ODF9fX1dfQ__&Signature=p~QJUGkBSUxIE7TUxGbDxfIX-zPD0zVglTKxYOZuWnwmDrS7BkYPMtm1snSbrNN6-FsUs9Yp5aagcC~aNyIEfYv89dhrMnofm3tVyTl0~8U8QGoYQlZ-FdIw8E4K6pLGKoL~UJtWqkuYsbKI7E4qsxVAHuX-ovMeHoXjwIt13y~ODtWo0UDNb4MbigDq6O~sPTpDvRX-dcgf3rFsQLU5wxT565JZatcu3-IgLQTCMkIFb1-IKzs15xOHU~bjOyamF2d3BzYj2Sft9sDg9RnxCmHGAXKAPv0p163CrThom-RRCIe8IXaWIN1k7bKGKmgIR~vv~YMRE254svc~~maRbg__&Key-Pair-Id=K2TK3EG287XSFC)
Figure 1: Data transmit behavior under CTS
The RTS signal is an output of the device. If the RTS line is low, the device is busy and unable to receive new data. Otherwise, the device’s UART is idle and ready to receive. After receiving a byte the direct memory access (DMA) controller of the device will transfer the byte to its receive first-in-first-out (FIFO) buffer. The device will pull down the RTS signal during this transfer. Therefore, with every byte received, the device lowers the RTS line shortly. Figure 2 shows this behavior.
.png?Policy=eyJTdGF0ZW1lbnQiOlt7IlJlc291cmNlIjoiaHR0cHM6Ly9kemY4dnF2MjRlcWhnLmNsb3VkZnJvbnQubmV0L3VzZXJmaWxlcy8yNzc1NC8zNTEzNS9ja2ZpbmRlci9pbWFnZXMvcXUvMjAyNi9pbWFnZSgzKS5wbmciLCJDb25kaXRpb24iOnsiRGF0ZUxlc3NUaGFuIjp7IkFXUzpFcG9jaFRpbWUiOjE3ODA2NzM0ODF9fX1dfQ__&Signature=R73SDaN4DP~B3jyKd4utfqkkfVQypLdfPoBu4FZFFJDhCs5ahLPcdFVpMiZVijblVmOC58YKKMh5Tge~rpmT7JZbdtyjFDqvYuFjMRCB3nY0Tsj67CdPj4Gljwa7UzXKGg-bGk9mgyqcegBg2sX~uzw1JY1r5xllyEHK9c6cTs0TUXhBxSgzbN5hxe8OGPc5wI0V8iy~mMy2LYLbVGD6YkiD~un8g9DxBLWaqKzFNO8B2uu-uGtbkLdEuXf83nEhXphsGHXwUwvreP~AUoFLK6M-A0jE99Y5hUd9om2QFTrRD~n6aiIExaZo-JEL-XZxj26kl3gLcSpxEM~og9WnaQ__&Key-Pair-Id=K2TK3EG287XSFC)
Figure 2: RTS behavior during data reception
The user can use this communication mode without hardware flow control. In this case, the user must tie the CTS line high (e.g. VIN) to make the device transmit.
The RS422 interface complies with the standard RS422 voltage levels. It replaces the RS232 lines of the default interface. The RS422 frame configuration is 8 data bits, no parity and 1 stop bit (8N1). The RS422 interface does not support flow control.
The RTCM/SPARTN input port on the Sirius RTK-GNSS/INS (product code S1R43x) can be used to provide correction messages using the RTCM or SPARTN protocol. The port uses RS232 signaling with 8 data bits, no parity and 1 stop bit. The default baud rate on this port is 38400 bit/s, but a higher baud rate can be configured. Refer to the table below for available baud rates. Setting the baud rate is possible using MT Manager or using low level commands. Please refer to the low-level communication document for details on the SetPortConfig command and how to configure it.
The input port also outputs a GGA message at a 1 Hz interval. This GGA message is often required by NTRIP providers.
RTCM input port baud rates
|
Baud Rate [bits/s] |
|
38k4 (default) |
| 57k6 |
| 115k2 |
| 230k4 |
| 460k8 |
| 921k6 |