# VOXL 2 J18 port for External FC

Source: https://forum.modalai.com/topic/4850/voxl-2-j18-port-for-external-fc
Category: General Questions (https://forum.modalai.com/category/2/general-questions)
Posted: 2025-11-04 07:31:33 UTC by Jetson Nano
Replies: 14 · Views: 1290

## Jetson Nano · 2025-11-04 07:31:33 UTC

Hey @Vinny @Eric-Katzfey ,
guys I am trying to use the J18 port on voxl 2 for connecting the external FC ( flight core v2).
While I try to run it , the voxl-mavlink-server is throwing error.

I assigned the autopilto_uart_bus to 12 as mentioned in the documentation.

```
voxl2:/$ voxl-mavlink-server 
loading our own config file
=================================================================
Parameters as loaded from config file:
primary_static_gcs_ip:        192.168.168.2
secondary_static_gcs_ip:      192.168.8.11
onboard_port_to_autopilot:    14556
onboard_port_from_autopilot:  14557
gcs_port_to_autopilot:        14558
gcs_port_from_autopilot:      14559
en_external_uart_ap:          1
autopilot_uart_bus:           12
autopilot_uart_baudrate:      921600
autopilot_mission_delay_start:      -1
autopilot_mission_delay_sound:      0
autopilot_mission_notif_dur:      0.10
udp_mtu:                      500
gcs_timeout_s                 4.50
en_external_ap_timesync:      1
en_external_ap_heartbeat:     1
=================================================================
Sending library name request: libslpi_qrb5165_io.so
Sending initialization request
Received standard error event SNS_STD_ERROR_NOT_SUPPORTED
Couldn't configure flight_controller sensor
ERROR:   fc_sensor_initialize failed
ERROR:   Failed to initialize slpi
ERROR:   Encountered error while initializing bus 12
ERROR: Unable to configure bus 12 (baudrate 921600) with voxl_io
Stopping autopilot io module
Stopping gcs io module
Stopping pipe io module
closing remaining client pipes
closing remaining server pipes
Removing PID file
exiting

```

## Reply by Jetson Nano · 2025-11-04 07:36:11 UTC

the error mentioned above was caused by the voxl-px4 server, once I disabled it was solved.
Still I was not able to see the data from the external FC

```
voxl2:/$ voxl-mavlink-server 
loading our own config file
=================================================================
Parameters as loaded from config file:
primary_static_gcs_ip:        192.168.168.2
secondary_static_gcs_ip:      192.168.8.11
onboard_port_to_autopilot:    14556
onboard_port_from_autopilot:  14557
gcs_port_to_autopilot:        14558
gcs_port_from_autopilot:      14559
en_external_uart_ap:          1
autopilot_uart_bus:           12
autopilot_uart_baudrate:      921600
autopilot_mission_delay_start:      -1
autopilot_mission_delay_sound:      0
autopilot_mission_notif_dur:      0.10
udp_mtu:                      500
gcs_timeout_s                 4.50
en_external_ap_timesync:      1
en_external_ap_heartbeat:     1
=================================================================
Sending library name request: libslpi_qrb5165_io.so
Sending initialization request
Successfully opened bus 12 at baudrate 921600
starting qrb5165 external AP receive thread
Adding primary GCS IP address from conf file to list: 192.168.168.2
Added new UDP connection to 192.168.168.2
Adding secondary manual gcs IP address to udp connection list: 192.168.8.11
Added new UDP connection to 192.168.8.11
Init complete, entering main loop

```

## Reply by Jetson Nano · 2025-11-04 10:12:30 UTC (in reply to Jetson Nano)

@Jetson-Nano 
now it is getting data from fc , it was a issue with baudrate, the J18 port can not handle 3000000 baudrate.
still i am facing an issue, where the QGC is not getting connected, the qgc is loading,then getting disconnected, again regaining connection this is going in a loop.
I tried increasing the udp_mtu still no change, same behaviour.

The error is mentioned below.
```
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message
--- msg_id: 1033
--- topic name: uart_data
Sending topic message

```

**MAVLINK-server**

```
 "primary_static_gcs_ip":        "192.168.168.100",
        "secondary_static_gcs_ip":      "192.169.168.2",
        "onboard_port_to_autopilot":    14556,
        "onboard_port_from_autopilot":  14557,
        "gcs_port_to_autopilot":        14558,
        "gcs_port_from_autopilot":      14559,
        "en_external_uart_ap":  true,
        "autopilot_uart_bus":   12,
        "autopilot_uart_baudrate":      921600,
        "autopilot_mission_delay_start":        -1,
        "autopilot_mission_delay_sound":        false,
        "autopilot_mission_notif_dur":  0.1,
        "en_external_ap_timesync":      1,
        "en_external_ap_heartbeat":     10,
        "udp_mtu":      800,
        "gcs_timeout_s":        1
}
```

after this issue, the mavlink server is shuting down and showing the below error

```
Couldn't locate SUID for flight_controller
Failed to detect flight controller sensor
ERROR:   fc_sensor_initialize failed
ERROR:   Failed to initialize slpi
ERROR:   Encountered error while initializing bus 12
ERROR: Unable to configure bus 12 (baudrate 921600) with voxl_io
Stopping autopilot io module
Stopping gcs io module
Stopping pipe io module
closing remaining client pipes
closing remaining server pipes
Removing PID file
exiting
```

rebooting and running again gives

```
voxl2:~$ voxl-mavlink-server 
loading our own config file
=================================================================
Parameters as loaded from config file:
primary_static_gcs_ip:        192.168.168.200
secondary_static_gcs_ip:      192.169.168.1
onboard_port_to_autopilot:    14556
onboard_port_from_autopilot:  14557
gcs_port_to_autopilot:        14558
gcs_port_from_autopilot:      14559
en_external_uart_ap:          1
autopilot_uart_bus:           12
autopilot_uart_baudrate:      921600
autopilot_mission_delay_start:      -1
autopilot_mission_delay_sound:      0
autopilot_mission_notif_dur:      0.10
udp_mtu:                      800
gcs_timeout_s                 1.00
en_external_ap_timesync:      1
en_external_ap_heartbeat:     1
=================================================================
existing instance of voxl-mavlink-server found, attempting to stop it
Sending library name request: libslpi_qrb5165_io.so
Sending initialization request
Successfully opened bus 12 at baudrate 921600
starting qrb5165 external AP receive thread
Adding primary GCS IP address from conf file to list: 192.168.168.200
Added new UDP connection to 192.168.168.200
Adding secondary manual gcs IP address to udp connection list: 192.169.168.1
Added new UDP connection to 192.169.168.1
Init complete, entering main loop
CONNECTED to GCS at 192.168.168.200
Detected Autopilot Mavlink SYSID 188
WARNING: UART parser dropped 1 packets from external AP at i=346
WARNING: UART parser dropped 1 packets from external AP at i=359
WARNING: UART parser dropped 1 packets from external AP at i=437
Detected Autopilot Mavlink SYSID 1
WARNING: UART parser dropped 1 packets from external AP at i=527
WARNING: UART parser dropped 1 packets from external AP at i=543
WARNING: UART parser dropped 1 packets from external AP at i=738
WARNING: UART parser dropped 1 packets from external AP at i=6
WARNING: UART parser dropped 1 packets from external AP at i=132
WARNING: UART parser dropped 1 packets from external AP at i=353
WARNING: UART parser dropped 1 packets from external AP at i=833
WARNING: UART parser dropped 1 packets from external AP at i=57
WARNING: UART parser dropped 1 packets from external AP at i=20
WARNING: UART parser dropped 1 packets from external AP at i=5
Detected Autopilot Mavlink SYSID 57
Detected Autopilot Mavlink SYSID 55
WARNING: UART parser dropped 1 packets from external AP at i=0
Detected Autopilot Mavlink SYSID 57
```

The mavlink sysid is changing
```
voxl2:~$ voxl-mavlink-server 
loading our own config file
=================================================================
Parameters as loaded from config file:
primary_static_gcs_ip:        192.168.168.200
secondary_static_gcs_ip:      192.169.168.1
onboard_port_to_autopilot:    14556
onboard_port_from_autopilot:  14557
gcs_port_to_autopilot:        14558
gcs_port_from_autopilot:      14559
en_external_uart_ap:          1
autopilot_uart_bus:           12
autopilot_uart_baudrate:      921600
autopilot_mission_delay_start:      -1
autopilot_mission_delay_sound:      0
autopilot_mission_notif_dur:      0.10
udp_mtu:                      500
gcs_timeout_s                 1.00
en_external_ap_timesync:      1
en_external_ap_heartbeat:     1
=================================================================
Sending library name request: libslpi_qrb5165_io.so
Sending initialization request
Successfully opened bus 12 at baudrate 921600
starting qrb5165 external AP receive thread
Adding primary GCS IP address from conf file to list: 192.168.168.200
Added new UDP connection to 192.168.168.200
Adding secondary manual gcs IP address to udp connection list: 192.169.168.1
Added new UDP connection to 192.169.168.1
Init complete, entering main loop
CONNECTED to GCS at 192.168.168.200
Detected Autopilot Mavlink SYSID 1
WARNING: UART parser dropped 1 packets from external AP at i=128
WARNING: UART parser dropped 1 packets from external AP at i=302
Detected Autopilot Mavlink SYSID 65
WARNING: UART parser dropped 1 packets from external AP at i=84
Detected Autopilot Mavlink SYSID 1
WARNING: UART parser dropped 1 packets from external AP at i=68
WARNING: UART parser dropped 1 packets from external AP at i=92
WARNING: UART parser dropped 1 packets from external AP at i=34
WARNING: UART parser dropped 1 packets from external AP at i=141
DISCONNECTED FROM GCS 192.168.168.200
CONNECTED to GCS at 192.168.168.200
DISCONNECTED FROM GCS 192.168.168.200
CONNECTED to GCS at 192.168.168.200
DISCONNECTED FROM GCS 192.168.168.200
CONNECTED to GCS at 192.168.168.200
Detected Autopilot Mavlink SYSID 28
DISCONNECTED FROM GCS 192.168.168.200
CONNECTED to GCS at 192.168.168.200
DISCONNECTED FROM GCS 192.168.168.200
CONNECTED to GCS at 192.168.168.200
DISCONNECTED FROM GCS 192.168.168.200
CONNECTED to GCS at 192.168.168.200
DISCONNECTED FROM GCS 192.168.168.200
CONNECTED to GCS at 192.168.168.200
```

## Reply by Eric Katzfey (ModalAI staff) · 2025-11-04 17:51:01 UTC (in reply to Jetson Nano)

@Jetson-Nano Can you try a lower baudrate, like 57600, and see if that works better?

## Reply by Jetson Nano · 2025-11-04 18:27:33 UTC (in reply to Eric Katzfey)

@Eric-Katzfey I tried lower baudrate also, the behaviour is similar.

## Reply by Eric Katzfey (ModalAI staff) · 2025-11-04 21:31:39 UTC (in reply to Jetson Nano)

@Jetson-Nano Do you still get those messages from voxl-mavlink-server about dropped packets from external AP?

## Reply by Eric Katzfey (ModalAI staff) · 2025-11-04 21:32:46 UTC (in reply to Jetson Nano)

@Jetson-Nano Are you using WiFi to connect with QGC?

## Reply by Jetson Nano · 2025-11-05 10:50:33 UTC (in reply to Eric Katzfey)

@Eric-Katzfey yes I still had that messages popping up

## Reply by Jetson Nano · 2025-11-05 10:51:42 UTC (in reply to Eric Katzfey)

@Eric-Katzfey No I was using the Microhard module. Irrespective of the communication module, these many time should the sysid change and the packet lose should not occure, right?

## Reply by Jetson Nano · 2025-11-05 12:55:05 UTC (in reply to Eric Katzfey)

@Eric-Katzfey 

I changed the Mavlink version to what you had mentioned here, I felt the errors were similar
[Link](https://forum.modalai.com/post/24270)
**this is when baudrate is 57600**

```
voxl2:~$ voxl-mavlink-server 
loading our own config file
=================================================================
Parameters as loaded from config file:
primary_static_gcs_ip:        192.168.168.200
primary_static_gcs_ip_port:   14550
secondary_static_gcs_ip:      192.169.168.2
secondary_static_gcs_ip_port: 14550
onboard_port_to_autopilot:    14556
onboard_port_from_autopilot:  14557
gcs_port_to_autopilot:        14558
gcs_port_from_autopilot:      14559
en_external_uart_ap:          1
autopilot_uart_bus:           12
autopilot_uart_baudrate:      57600
autopilot_mission_delay_start:      -1
autopilot_mission_delay_sound:      0
autopilot_mission_force_restart:      0
autopilot_mission_notif_dur:      0.10
udp_mtu:                      0
gcs_timeout_s                 1.00
en_external_ap_timesync:      1
en_external_ap_heartbeat:     1
=================================================================
Sending library name request: libslpi_qrb5165_io.so
Sending initialization request
Successfully opened bus 12 at baudrate 57600
starting qrb5165 external AP receive thread
Adding primary GCS IP address from conf file to list: 192.168.168.200:14550
Added new UDP connection to 192.168.168.200:14550
Adding secondary manual gcs IP address to udp connection list: 192.169.168.2:14550
Added new UDP connection to 192.169.168.2:14550
Init complete, entering main loop
CONNECTED to GCS at 192.168.168.200:14550
Waiting to detect autopilot sys id...
Waiting to detect autopilot sys id...
Waiting to detect autopilot sys id...
Waiting to detect autopilot sys id...
Waiting to detect autopilot sys id...
Waiting to detect autopilot sys id...
^C
received SIGINT Ctrl-C
Waiting to detect autopilot sys id...
Starting shutdown sequence
Stopping autopilot io module
exiting read thread
qrb5165 external ap interface stopped
Stopping gcs io module
WARNING: Received 12 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 41 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 32 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 36 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 18 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
exiting gcs udp listener thread
udp gcs io stopped
Stopping pipe io module
closing remaining client pipes
closing remaining server pipes
Removing PID file
exiting
```

**this is when baudrate is 921600**

```
voxl2:~$ voxl-mavlink-server 
loading our own config file
=================================================================
Parameters as loaded from config file:
primary_static_gcs_ip:        192.168.168.200
primary_static_gcs_ip_port:   14550
secondary_static_gcs_ip:      192.169.168.2
secondary_static_gcs_ip_port: 14550
onboard_port_to_autopilot:    14556
onboard_port_from_autopilot:  14557
gcs_port_to_autopilot:        14558
gcs_port_from_autopilot:      14559
en_external_uart_ap:          1
autopilot_uart_bus:           12
autopilot_uart_baudrate:      921600
autopilot_mission_delay_start:      -1
autopilot_mission_delay_sound:      0
autopilot_mission_force_restart:      0
autopilot_mission_notif_dur:      0.10
udp_mtu:                      0
gcs_timeout_s                 1.00
en_external_ap_timesync:      1
en_external_ap_heartbeat:     1
=================================================================
Sending library name request: libslpi_qrb5165_io.so
Sending initialization request
Successfully opened bus 12 at baudrate 921600
starting qrb5165 external AP receive thread
Adding primary GCS IP address from conf file to list: 192.168.168.200:14550
Added new UDP connection to 192.168.168.200:14550
Adding secondary manual gcs IP address to udp connection list: 192.169.168.2:14550
Added new UDP connection to 192.169.168.2:14550
Init complete, entering main loop
CONNECTED to GCS at 192.168.168.200:14550
Detected Autopilot Mavlink SYSID 130
WARNING: UART parser dropped 1 packets from external AP at i=8
WARNING: UART parser dropped 1 packets from external AP at i=1
WARNING: UART parser dropped 1 packets from external AP at i=1
WARNING: UART parser dropped 1 packets from external AP at i=7
WARNING: UART parser dropped 1 packets from external AP at i=6
WARNING: UART parser dropped 1 packets from external AP at i=0
WARNING: UART parser dropped 1 packets from external AP at i=1
WARNING: UART parser dropped 1 packets from external AP at i=8
WARNING: UART parser dropped 1 packets from external AP at i=1
WARNING: UART parser dropped 1 packets from external AP at i=10
WARNING: UART parser dropped 1 packets from external AP at i=1
WARNING: UART parser dropped 1 packets from external AP at i=1
WARNING: UART parser dropped 1 packets from external AP at i=1
WARNING: UART parser dropped 1 packets from external AP at i=0
^C
received SIGINT Ctrl-C
Starting shutdown sequence
Stopping autopilot io module
exiting read thread
qrb5165 external ap interface stopped
Stopping gcs io module
WARNING: Received 11 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 54 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 11 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 10 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 7 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 9 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 12 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 10 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 10 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
WARNING: Received 11 bytes of data from SLPI while SLPI uart not in use (topic uart_data)
exiting gcs udp listener thread
udp gcs io stopped
Stopping pipe io module
closing remaining client pipes
closing remaining server pipes
Removing PID file
exiting
voxl2:~$ 
````

## Reply by Jetson Nano · 2025-11-05 12:58:00 UTC (in reply to Jetson Nano)

@Eric-Katzfey 
voxl-mavlink-server -z

```
voxl2:~$ voxl-mavlink-server -z
Enabling UDP to slpi recv debugging
Enabling qrb5165 external AP recv debugging
Enabling UDP to slpi send debugging
Enabling qrb5165 external AP send debugging
Enabling UDP GCS recv debugging
Enabling UDP GCS send debugging
loading our own config file
=================================================================
Parameters as loaded from config file:
primary_static_gcs_ip:        192.168.168.200
primary_static_gcs_ip_port:   14550
secondary_static_gcs_ip:      192.169.168.2
secondary_static_gcs_ip_port: 14550
onboard_port_to_autopilot:    14556
onboard_port_from_autopilot:  14557
gcs_port_to_autopilot:        14558
gcs_port_from_autopilot:      14559
en_external_uart_ap:          1
autopilot_uart_bus:           12
autopilot_uart_baudrate:      57600
autopilot_mission_delay_start:      -1
autopilot_mission_delay_sound:      0
autopilot_mission_force_restart:      0
autopilot_mission_notif_dur:      0.10
udp_mtu:                      0
gcs_timeout_s                 1.00
en_external_ap_timesync:      1
en_external_ap_heartbeat:     1
=================================================================
Sending library name request: libslpi_qrb5165_io.so
Sending initialization request
Successfully opened bus 12 at baudrate 57600
starting qrb5165 external AP receive thread
Adding primary GCS IP address from conf file to list: 192.168.168.200:14550
Added new UDP connection to 192.168.168.200:14550
Adding secondary manual gcs IP address to udp connection list: 192.169.168.2:14550
Added new UDP connection to 192.169.168.2:14550
Init complete, entering main loop
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:   0 compid: 196
to AP msg ID:     0 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
from GCS    ID:   0 port: 14550 IP: 192.168.168.200 
CONNECTED to GCS at 192.168.168.200:14550
to AP msg ID:     0 sysid:255   to bus: 12
from gcs pipe ID:   0  compid: 190
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
from gcs pipe ID:   0 compid: 100
to GCS      msgid:    0 compid 100
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
Waiting to detect autopilot sys id...
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:130   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:130   to bus: 12
```

## Reply by Eric Katzfey (ModalAI staff) · 2025-11-05 18:24:45 UTC (in reply to Jetson Nano)

@Jetson-Nano Looks like you are never receiving anything FROM the AP. Only sending stuff TO it. Can you put an oscilloscope on the RX / TX UART lines to see what the traffic looks like. For some reason it doesn't seem like the UART is setup properly on either the FC or the DSP so with an oscilloscope you can better see what is going on.

## Reply by Jetson Nano · 2025-11-07 14:35:29 UTC (in reply to Eric Katzfey)

@Eric-Katzfey I am facing a different error,

```
voxl2:/$ voxl-mavlink-server 
loading our own config file
=================================================================
Parameters as loaded from config file:
primary_static_gcs_ip:        192.168.168.200
primary_static_gcs_ip_port:   14550
secondary_static_gcs_ip:      192.169.168.2
secondary_static_gcs_ip_port: 14550
onboard_port_to_autopilot:    14556
onboard_port_from_autopilot:  14557
gcs_port_to_autopilot:        14558
gcs_port_from_autopilot:      14559
en_external_uart_ap:          1
autopilot_uart_bus:           12
autopilot_uart_baudrate:      921600
autopilot_mission_delay_start:      -1
autopilot_mission_delay_sound:      0
autopilot_mission_force_restart:      0
autopilot_mission_notif_dur:      0.10
udp_mtu:                      0
gcs_timeout_s                 1.00
en_external_ap_timesync:      1
en_external_ap_heartbeat:     1
=================================================================
existing instance of voxl-mavlink-server found, attempting to stop it
Sending library name request: libslpi_qrb5165_io.so
Sending initialization request
Successfully opened bus 12 at baudrate 921600
starting qrb5165 external AP receive thread
Adding primary GCS IP address from conf file to list: 192.168.168.200:14550
Added new UDP connection to 192.168.168.200:14550
Adding secondary manual gcs IP address to udp connection list: 192.169.168.2:14550
Added new UDP connection to 192.169.168.2:14550
Init complete, entering main loop
Detected Autopilot Mavlink SYSID 1
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SP
```

## Reply by Jetson Nano · 2025-11-07 14:40:01 UTC (in reply to Jetson Nano)

These mentioned errors were only observed while using microhard unit
```
voxl2:/$ voxl-mavlink-server -z
Enabling UDP to slpi recv debugging
Enabling qrb5165 external AP recv debugging
Enabling UDP to slpi send debugging
Enabling qrb5165 external AP send debugging
Enabling UDP GCS recv debugging
Enabling UDP GCS send debugging
loading our own config file
=================================================================
Parameters as loaded from config file:
primary_static_gcs_ip:        192.168.168.200
primary_static_gcs_ip_port:   14550
secondary_static_gcs_ip:      192.169.168.2
secondary_static_gcs_ip_port: 14550
onboard_port_to_autopilot:    14556
onboard_port_from_autopilot:  14557
gcs_port_to_autopilot:        14558
gcs_port_from_autopilot:      14559
en_external_uart_ap:          1
autopilot_uart_bus:           12
autopilot_uart_baudrate:      921600
autopilot_mission_delay_start:      -1
autopilot_mission_delay_sound:      0
autopilot_mission_force_restart:      0
autopilot_mission_notif_dur:      0.10
udp_mtu:                      200
gcs_timeout_s                 1.00
en_external_ap_timesync:      1
en_external_ap_heartbeat:     1
=================================================================
Sending library name request: libslpi_qrb5165_io.so
Sending initialization request
Successfully opened bus 12 at baudrate 921600
starting qrb5165 external AP receive thread
RECV  msg ID:    74 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
RECV  msg ID:    31 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
RECV  msg ID:   105 sysid:  1 from bus: 12
RECV  msg ID:    31 sysid:  1 from bus: 12
RECV  msg ID:    32 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
RECV  msg ID:   331 sysid:  1 from bus: 12
RECV  msg ID:     1 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
RECV  msg ID:   105 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
RECV  msg ID:    31 sysid:  1 from bus: 12
RECV  msg ID:   105 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
RECV  msg ID:    32 sysid:  1 from bus: 12
RECV  msg ID:   331 sysid:  1 from bus: 12
RECV  msg ID:   411 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
RECV  msg ID:    31 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
RECV  msg ID:   105 sysid:  1 from bus: 12
RECV  msg ID:   132 sysid:  1 from bus: 12
RECV  msg ID:    31 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
RECV  msg ID:    32 sysid:  1 from bus: 12
RECV  msg ID:   331 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
RECV  msg ID:   111 sysid:  1 from bus: 12
RECV  msg ID:   105 sysid:  1 from bus: 12
RECV  msg ID:   141 sysid:  1 from bus: 12
RECV  msg ID:    83 sysid:  1 from bus: 12
RECV  msg ID:   245 sysid:  1 from bus: 12
RECV  msg ID:    85 sysid:  1 from bus: 12
RECV  msg ID:    36 sysid:  1 from bus: 12
RECV  msg ID:    74 sysid:  1 from bus: 12
RECV  msg ID:   106 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
RECV  msg ID:    31 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
Adding primary GCS IP address from conf file to list: 192.168.168.200:14550
Added new UDP connection to 192.168.168.200:14550
Adding secondary manual gcs IP address to udp connection list: 192.169.168.2:14550
Added new UDP connection to 192.169.168.2:14550
RECV  msg ID:   105 sysid:  1 from bus: 12
to GCS      msgid:  105 compid   1
RECV  msg ID:    32 sysid:  1 from bus: 12
to GCS      msgid:   32 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to GCS      msgid:   30 compid   1
Init complete, entering main loop
RECV  msg ID:   331 sysid:  1 from bus: 12
to ob pipe  ID: 331  compid:   1
to gcs pipe ID: 331  compid:   1
to GCS      msgid:  331 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    32 sysid:  1 from bus: 12
to ob pipe  ID:  32  compid:   1
to gcs pipe ID:  32  compid:   1
to GCS      msgid:   32 compid   1
RECV  msg ID:   331 sysid:  1 from bus: 12
to ob pipe  ID: 331  compid:   1
to gcs pipe ID: 331  compid:   1
to GCS      msgid:  331 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   132 sysid:  1 from bus: 12
to ob pipe  ID: 132  compid:   1
to gcs pipe ID: 132  compid:   1
to GCS      msgid:  132 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:    32 sysid:  1 from bus: 12
to ob pipe  ID:  32  compid:   1
to gcs pipe ID:  32  compid:   1
to GCS      msgid:   32 compid   1
RECV  msg ID:   331 sysid:  1 from bus: 12
to ob pipe  ID: 331  compid:   1
to gcs pipe ID: 331  compid:   1
to GCS      msgid:  331 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   111 sysid:  1 from bus: 12
to AP msg ID:   111 sysid:  1   to bus: 12
to AP msg ID:   111 sysid:  1   to bus: 12
to gcs pipe ID: 111  compid:   1
to GCS      msgid:  111 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:   141 sysid:  1 from bus: 12
to ob pipe  ID: 141  compid:   1
to gcs pipe ID: 141  compid:   1
to GCS      msgid:  141 compid   1
RECV  msg ID:    83 sysid:  1 from bus: 12
to ob pipe  ID:  83  compid:   1
to gcs pipe ID:  83  compid:   1
to GCS      msgid:   83 compid   1
RECV  msg ID:    85 sysid:  1 from bus: 12
to ob pipe  ID:  85  compid:   1
to gcs pipe ID:  85  compid:   1
to GCS      msgid:   85 compid   1
RECV  msg ID:    36 sysid:  1 from bus: 12
to ob pipe  ID:  36  compid:   1
to gcs pipe ID:  36  compid:   1
to GCS      msgid:   36 compid   1
RECV  msg ID:    74 sysid:  1 from bus: 12
to ob pipe  ID:  74  compid:   1
to gcs pipe ID:  74  compid:   1
to GCS      msgid:   74 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:   111 sysid:  1 from bus: 12
to gcs pipe ID: 111  compid:   1
to GCS      msgid:  111 compid   1
RECV  msg ID:   106 sysid:  1 from bus: 12
to ob pipe  ID: 106  compid:   1
to gcs pipe ID: 106  compid:   1
to GCS      msgid:  106 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    32 sysid:  1 from bus: 12
to ob pipe  ID:  32  compid:   1
to gcs pipe ID:  32  compid:   1
to GCS      msgid:   32 compid   1
RECV  msg ID:   331 sysid:  1 from bus: 12
to ob pipe  ID: 331  compid:   1
to gcs pipe ID: 331  compid:   1
to GCS      msgid:  331 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   132 sysid:  1 from bus: 12
to ob pipe  ID: 132  compid:   1
to gcs pipe ID: 132  compid:   1
to GCS      msgid:  132 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:    32 sysid:  1 from bus: 12
to ob pipe  ID:  32  compid:   1
to gcs pipe ID:  32  compid:   1
to GCS      msgid:   32 compid   1
RECV  msg ID:   331 sysid:  1 from bus: 12
to ob pipe  ID: 331  compid:   1
to gcs pipe ID: 331  compid:   1
to GCS      msgid:  331 compid   1
RECV  msg ID:     0 sysid:  1 from bus: 12
Detected Autopilot Mavlink SYSID 1
to ob pipe  ID:   0  compid:   1
to gcs pipe ID:   0  compid:   1
to GCS      msgid:    0 compid   1
RECV  msg ID:   111 sysid:  1 from bus: 12
to AP msg ID:   111 sysid:  1   to bus: 12
to AP msg ID:   111 sysid:  1   to bus: 12
to gcs pipe ID: 111  compid:   1
to GCS      msgid:  111 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:   106 sysid:  1 from bus: 12
to ob pipe  ID: 106  compid:   1
to gcs pipe ID: 106  compid:   1
to GCS      msgid:  106 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:    32 sysid:  1 from bus: 12
to ob pipe  ID:  32  compid:   1
to gcs pipe ID:  32  compid:   1
to GCS      msgid:   32 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   331 sysid:  1 from bus: 12
to ob pipe  ID: 331  compid:   1
to gcs pipe ID: 331  compid:   1
to GCS      msgid:  331 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:  1   to bus: 12
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:   410 sysid:  1 from bus: 12
to ob pipe  ID: 410  compid:   1
to gcs pipe ID: 410  compid:   1
to GCS      msgid:  410 compid   1
RECV  msg ID:   410 sysid:  1 from bus: 12
to ob pipe  ID: 410  compid:   1
to gcs pipe ID: 410  compid:   1
to GCS      msgid:  410 compid   1
RECV  msg ID:   410 sysid:  1 from bus: 12
to ob pipe  ID: 410  compid:   1
to gcs pipe ID: 410  compid:   1
to GCS      msgid:  410 compid   1
RECV  msg ID:   410 sysid:  1 from bus: 12
to ob pipe  ID: 410  compid:   1
to gcs pipe ID: 410  compid:   1
to GCS      msgid:  410 compid   1
RECV  msg ID:   410 sysid:  1 from bus: 12
to ob pipe  ID: 410  compid:   1
to gcs pipe ID: 410  compid:   1
to GCS      msgid:  410 compid   1
RECV  msg ID:   410 sysid:  1 from bus: 12
to ob pipe  ID: 410  compid:   1
to gcs pipe ID: 410  compid:   1
to GCS      msgid:  410 compid   1
RECV  msg ID:   410 sysid:  1 from bus: 12
to ob pipe  ID: 410  compid:   1
to gcs pipe ID: 410  compid:   1
to GCS      msgid:  410 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    32 sysid:  1 from bus: 12
to ob pipe  ID:  32  compid:   1
to gcs pipe ID:  32  compid:   1
to GCS      msgid:   32 compid   1
RECV  msg ID:   331 sysid:  1 from bus: 12
to ob pipe  ID: 331  compid:   1
to gcs pipe ID: 331  compid:   1
to GCS      msgid:  331 compid   1
onboard  pipe  ID: 331 compid: 197
to AP msg ID:   331 sysid:  1   to bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:  1   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:  1   to bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   132 sysid:  1 from bus: 12
to ob pipe  ID: 132  compid:   1
to gcs pipe ID: 132  compid:   1
to GCS      msgid:  132 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:    32 sysid:  1 from bus: 12
to ob pipe  ID:  32  compid:   1
to gcs pipe ID:  32  compid:   1
to GCS      msgid:   32 compid   1
RECV  msg ID:   331 sysid:  1 from bus: 12
to ob pipe  ID: 331  compid:   1
to gcs pipe ID: 331  compid:   1
to GCS      msgid:  331 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
onboard  pipe  ID: 331 compid: 197
to AP msg ID:   331 sysid:  1   to bus: 12
RECV  msg ID:   111 sysid:  1 from bus: 12
to AP msg ID:   111 sysid:  1   to bus: 12
to AP msg ID:   111 sysid:  1   to bus: 12
to gcs pipe ID: 111  compid:   1
to GCS      msgid:  111 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:  1   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:  1   to bus: 12
onboard  pipe  ID:   0 compid: 196
to AP msg ID:     0 sysid:  1   to bus: 12
RECV  msg ID:   141 sysid:  1 from bus: 12
to ob pipe  ID: 141  compid:   1
to gcs pipe ID: 141  compid:   1
to GCS      msgid:  141 compid   1
RECV  msg ID:    83 sysid:  1 from bus: 12
to ob pipe  ID:  83  compid:   1
to gcs pipe ID:  83  compid:   1
to GCS      msgid:   83 compid   1
RECV  msg ID:    85 sysid:  1 from bus: 12
to ob pipe  ID:  85  compid:   1
to gcs pipe ID:  85  compid:   1
to GCS      msgid:   85 compid   1
RECV  msg ID:    36 sysid:  1 from bus: 12
to ob pipe  ID:  36  compid:   1
to gcs pipe ID:  36  compid:   1
to GCS      msgid:   36 compid   1
RECV  msg ID:    74 sysid:  1 from bus: 12
to ob pipe  ID:  74  compid:   1
to gcs pipe ID:  74  compid:   1
to GCS      msgid:   74 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:   106 sysid:  1 from bus: 12
to ob pipe  ID: 106  compid:   1
to gcs pipe ID: 106  compid:   1
to GCS      msgid:  106 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   111 sysid:  1 from bus: 12
to gcs pipe ID: 111  compid:   1
to GCS      msgid:  111 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
onboard  pipe  ID: 331 compid: 197
to AP msg ID:   331 sysid:  1   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:  1   to bus: 12
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:   410 sysid:  1 from bus: 12
to ob pipe  ID: 410  compid:   1
to gcs pipe ID: 410  compid:   1
to GCS      msgid:  410 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    32 sysid:  1 from bus: 12
to ob pipe  ID:  32  compid:   1
to gcs pipe ID:  32  compid:   1
to GCS      msgid:   32 compid   1
RECV  msg ID:   331 sysid:  1 from bus: 12
to ob pipe  ID: 331  compid:   1
to gcs pipe ID: 331  compid:   1
to GCS      msgid:  331 compid   1
RECV  msg ID:   111 sysid:  1 from bus: 12
to AP msg ID:   111 sysid:  1   to bus: 12
to AP msg ID:   111 sysid:  1   to bus: 12
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:  1   to bus: 12
to gcs pipe ID: 111  compid:   1
to GCS      msgid:  111 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:   141 sysid:  1 from bus: 12
to ob pipe  ID: 141  compid:   1
to gcs pipe ID: 141  compid:   1
to GCS      msgid:  141 compid   1
RECV  msg ID:    83 sysid:  1 from bus: 12
to ob pipe  ID:  83  compid:   1
to gcs pipe ID:  83  compid:   1
to GCS      msgid:   83 compid   1
RECV  msg ID:    85 sysid:  1 from bus: 12
to ob pipe  ID:  85  compid:   1
to gcs pipe ID:  85  compid:   1
to GCS      msgid:   85 compid   1
RECV  msg ID:    36 sysid:  1 from bus: 12
to ob pipe  ID:  36  compid:   1
to gcs pipe ID:  36  compid:   1
to GCS      msgid:   36 compid   1
RECV  msg ID:    74 sysid:  1 from bus: 12
to ob pipe  ID:  74  compid:   1
to gcs pipe ID:  74  compid:   1
to GCS      msgid:   74 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:   106 sysid:  1 from bus: 12
to ob pipe  ID: 106  compid:   1
to gcs pipe ID: 106  compid:   1
to GCS      msgid:  106 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
onboard  pipe  ID: 331 compid: 197
to AP msg ID:   331 sysid:  1   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:  1   to bus: 12
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   132 sysid:  1 from bus: 12
to ob pipe  ID: 132  compid:   1
to gcs pipe ID: 132  compid:   1
to GCS      msgid:  132 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:    32 sysid:  1 from bus: 12
to ob pipe  ID:  32  compid:   1
to gcs pipe ID:  32  compid:   1
to GCS      msgid:   32 compid   1
RECV  msg ID:   331 sysid:  1 from bus: 12
to ob pipe  ID: 331  compid:   1
to gcs pipe ID: 331  compid:   1
to GCS      msgid:  331 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
onboard  pipe  ID: 331 compid: 197
to AP msg ID:   331 sysid:  1   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:  1   to bus: 12
RECV  msg ID:   111 sysid:  1 from bus: 12
to AP msg ID:   111 sysid:  1   to bus: 12
to AP msg ID:   111 sysid:  1   to bus: 12
to gcs pipe ID: 111  compid:   1
to GCS      msgid:  111 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:   141 sysid:  1 from bus: 12
to ob pipe  ID: 141  compid:   1
to gcs pipe ID: 141  compid:   1
to GCS      msgid:  141 compid   1
RECV  msg ID:    83 sysid:  1 from bus: 12
to ob pipe  ID:  83  compid:   1
to gcs pipe ID:  83  compid:   1
to GCS      msgid:   83 compid   1
RECV  msg ID:   245 sysid:  1 from bus: 12
to ob pipe  ID: 245  compid:   1
to gcs pipe ID: 245  compid:   1
to GCS      msgid:  245 compid   1
RECV  msg ID:    85 sysid:  1 from bus: 12
to ob pipe  ID:  85  compid:   1
to gcs pipe ID:  85  compid:   1
to GCS      msgid:   85 compid   1
RECV  msg ID:    36 sysid:  1 from bus: 12
to ob pipe  ID:  36  compid:   1
to gcs pipe ID:  36  compid:   1
to GCS      msgid:   36 compid   1
RECV  msg ID:    74 sysid:  1 from bus: 12
to ob pipe  ID:  74  compid:   1
to gcs pipe ID:  74  compid:   1
to GCS      msgid:   74 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
onboard  pipe  ID: 330 compid: 197
to AP msg ID:   330 sysid:  1   to bus: 12
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:   111 sysid:  1 from bus: 12
to gcs pipe ID: 111  compid:   1
to GCS      msgid:  111 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:   106 sysid:  1 from bus: 12
to ob pipe  ID: 106  compid:   1
to gcs pipe ID: 106  compid:   1
to GCS      msgid:  106 compid   1
onboard  pipe  ID: 331 compid: 197
to AP msg ID:   331 sysid:  1   to bus: 12
RECV  msg ID:    32 sysid:  1 from bus: 12
to ob pipe  ID:  32  compid:   1
to gcs pipe ID:  32  compid:   1
to GCS      msgid:   32 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   331 sysid:  1 from bus: 12
to ob pipe  ID: 331  compid:   1
to gcs pipe ID: 331  compid:   1
to GCS      msgid:  331 compid   1
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:  1   to bus: 12
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
onboard  pipe  ID: 331 compid: 197
to AP msg ID:   331 sysid:  1   to bus: 12
onboard  pipe  ID:  84 compid: 197
to AP msg ID:    84 sysid:  1   to bus: 12
RECV  msg ID:   111 sysid:  1 from bus: 12
to AP msg ID:   111 sysid:  1   to bus: 12
to AP msg ID:   111 sysid:  1   to bus: 12
to gcs pipe ID: 111  compid:   1
to GCS      msgid:  111 compid   1
RECV  msg ID:   105 sysid:  1 from bus: 12
to ob pipe  ID: 105  compid:   1
to gcs pipe ID: 105  compid:   1
to GCS      msgid:  105 compid   1
onboard  pipe  ID: 331 compid: 197
to AP msg ID:   331 sysid:  1   to bus: 12
RECV  msg ID:   111 sysid:  1 from bus: 12
to gcs pipe ID: 111  compid:   1
to GCS      msgid:  111 compid   1
RECV  msg ID:    31 sysid:  1 from bus: 12
to ob pipe  ID:  31  compid:   1
to gcs pipe ID:  31  compid:   1
to GCS      msgid:   31 compid   1
RECV  msg ID:    32 sysid:  1 from bus: 12
to ob pipe  ID:  32  compid:   1
to gcs pipe ID:  32  compid:   1
to GCS      msgid:   32 compid   1
RECV  msg ID:    30 sysid:  1 from bus: 12
to ob pipe  ID:  30  compid:   1
to gcs pipe ID:  30  compid:   1
to GCS      msgid:   30 compid   1
RECV  msg ID:   331 sysid:  1 from bus: 12
to ob pipe  ID: 331  compid:   1
to gcs pipe ID: 331  compid:   1
to GCS      msgid:  331 compid   1
RECV  msg ID:   106 sysid:  1 from bus: 12
to ob pipe  ID: 106  compid:   1
to gcs pipe ID: 106  compid:   1
to GCS      msgid:  106 compid   1
onboard  pipe  ID: 331 compid: 197
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
onboard  pipe  ID:  84 compid: 197
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
onboard  pipe  ID: 330 compid: 197
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
onboard  pipe  ID: 331 compid: 197
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
onboard  pipe  ID:  84 compid: 197
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
onboard  pipe  ID: 330 compid: 197
onboard  pipe  ID: 331 compid: 197
onboard  pipe  ID:  84 compid: 197
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
onboard  pipe  ID: 331 compid: 197
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
onboard  pipe  ID:  84 compid: 197
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
onboard  pipe  ID: 330 compid: 197
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
onboard  pipe  ID: 331 compid: 197
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE
onboard  pipe  ID:  84 compid: 197
ERROR:   Received error from ring_buf_push in p_slpi_receive_callback: ERR_NO_SPACE

```

## Reply by Jetson Nano · 2025-11-10 10:04:32 UTC (in reply to Jetson Nano)

@Eric-Katzfey 
hey,
I observed something while the above behaviour still persists. 
The modem and the camera server is showing not running while checking through the inspect services command.
I do not know whether this is related to this issue, but the voxl 2 is rebooting after sometime, the reboot is not constant and I am not able to able to find the reason for the reboot. Can everything be related to each other.
I am using the Microhard modem

![Screenshot from 2025-11-10 15-27-45.png](https://forum.modalai.com/assets/uploads/files/1762769045502-screenshot-from-2025-11-10-15-27-45.png) 

![Screenshot from 2025-11-10 15-30-27.png](https://forum.modalai.com/assets/uploads/files/1762769045568-screenshot-from-2025-11-10-15-30-27.png)
