ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Jetson Nano
    3. Posts
    • Profile
    • Following 2
    • Followers 0
    • Topics 85
    • Posts 414
    • Best 3
    • Controversial 0
    • Groups 0

    Posts made by Jetson Nano

    • RE: Turtle mode compatibility with non Modalai ESC

      @Eric-Katzfey hey, if I would like to implement the same in the main px4 fork (modalai) what all would i have to change.

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: Turtle mode compatibility with non Modalai ESC

      @Eric-Katzfey Thank you for reverting back, why does collision prevention not working with this px4 version.

      The obstacle_distance topic is not showing in any mpc_pos_mod

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: VOXL 2 J18 port for External FC

      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
      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: VOXL 2 J18 port for External FC

      @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
      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: Turtle mode compatibility with non Modalai ESC

      @Alex-Kushleyev ok thank you, I will wait for @Eric-Katzfey reply

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: Turtle mode compatibility with non Modalai ESC

      @Alex-Kushleyev Thank you for the support.
      Also I noticed only the VOXL-FPV-DEV version only have the voxl_esc_t_on option to control the esc through the joystick, The main version of modalai PX4 fork do not have them, is it under development.
      The FPV-dev version do not support collision prevention, so i had to roll up to the main version, which gave me this issue.

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: Turtle mode compatibility with non Modalai ESC

      @Eric-Katzfey So if I built similar driver for on px4 will it cause any errors with existing codes, once i remove the Voxl-esc driver and replace it with the vertiq esc code.

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • Turtle mode compatibility with non Modalai ESC

      Hey @Alex-Kushleyev @Eric-Katzfey @Vinny ,

      I would like to know whether the turtle mode is possible on Flight core v2 with out using the Modal ai ESC.
      I would like to use the vertiq Motors with on motors ESCs. vertiq motor

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: VOXL 2 J18 port for External FC

      @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
      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: VOXL 2 J18 port for External FC

      @Eric-Katzfey

      I changed the Mavlink version to what you had mentioned here, I felt the errors were similar
      Link
      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:~$
      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: VOXL 2 J18 port for External FC

      @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?

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: VOXL 2 J18 port for External FC

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

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: VOXL 2 J18 port for External FC

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

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: VOXL 2 J18 port for External FC

      @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
      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: VOXL 2 J18 port for External FC

      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
      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • VOXL 2 J18 port for External FC

      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
      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: VOXL 2 mini queries

      I found this board which is for TOF , I would like to know whether the micro coax pinout below the tof pinout is compatible with tracking and hires, no confirmation on the same as been mentioned anywhere, i just wanted a confirmation.

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • VOXL 2 mini queries

      Hey @Vinny @Eric-Katzfey
      I had some queries regarding the voxl 2 mini,

      1. Is external FC compatible with the voxl 2 mini
      2. Is Doodle labs compatible with the voxl 2 mini, in the compatible communication modules only Wifi, LTE and microhard are mentioned.
      3. Lepton is compatible with the micro coax board
      4. TOF port is not showed on the latest micro coax board, I would like to know whether you guys are completely removing the TOF from the sensors, or will it be added in the later versions.
      5. If i wanted TOF to be a part of the image sensors , Can i use the interposer or dual image sensor expander for multiple connections with MIPI flex cable based sensors.
      6. It is Mentioned in the datasheet that the Lepton is compatible with USB connection and spi connection is under development. Will you guys will be taking it forward or will coax board required for SPI based lepton connection.

      Thank you for your time

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: Joystick control delay

      @Eric-Katzfey As you suggested .I tested the same configuration in another build, where the Doodle labs module is away from ESC . the testing did not show any loss of data.

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: Joystick control delay

      Hi @Eric-Katzfey,

      Thanks for your feedback.

      I have a few additional clarifications that I would like to request, listed below:

      In my current setup, I am powering the DoodleLabs Nano module using a 5V, 1.5A BEC, and the data interface is configured through the USB Dev port (Port 1).
      With this configuration, the signal/noise readings observed in the DoodleLabs portal are approximately -45 dBm / -85 dBm, respectively.
      Could you please share your suggestions or insights based on these RSSI readings?

      Powering Query

      I would also like to confirm whether the Nano module can be powered directly from the VOXL2.
      I was unable to find detailed specifications regarding the current rating of the VOXL2 port.
      Could you please confirm if the VOXL2 port can supply adequate current to reliably power the DoodleLabs module?
      Your confirmation will help finalize our power configuration.

      Oscilloscope Query

      You had earlier suggested checking the signals on an oscilloscope.
      Since our communication interface uses USB (not UART), I wanted to confirm if it is practical or meaningful to probe USB signals using an oscilloscope in this context.

      Looking forward to your feedback and guidance on these points.

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano