ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Voxl2 Spektrum Receiver error

    VOXL 2
    4
    90
    2022
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Chase RileyC
      Chase Riley @Chase Riley
      last edited by

      @ben-grocholsky @Eric-Katzfey I attempted to run voxl-px4 again after a power cycle and encountered this error. Similar to the error before but looks to be showing the info that was cut off in the previous deb file.

      voxl2:/$ voxl-px4
[INFO] Reading from /etc/modalai/voxl-px4.conf
Found DSP signature file
[INFO] Daemon mode enabled

*************************
GPS=HOLYBRO
RC=SPEKTRUM
POWER MANAGER=VOXLPM
DISTANCE SENSOR=NONE
OSD=DISABLE
DAEMON_MODE=ENABLE
SENSOR_CAL=ACTUAL
EXTRA STEPS:
*************************

INFO  [px4] mlockall() enabled. PX4's virtual address space is locked into RAM.
INFO  [px4] assuming working directory is rootfs, no symlinks needed.
INFO  [muorb] Got muorb init command
Sending initialization request
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
Got topic data before configuration complete
INFO  [muorb] SLPI: muorb aggregator thread running
INFO  [muorb] muorb protobuf initalize method succeeded
INFO  [muorb] succesfully did ADVERTISE_TEST_TYPE
INFO  [muorb] SLPI: Creating pthread test_MUORB

INFO  [muorb] SLPI: Successfully created px4 task PX4_test_MUORB with tid 2097656
INFO  [muorb] succesfully did SUBSCRIBE_TEST_TYPE
INFO  [muorb] SLPI: Creating pthread test_MUORB

INFO  [muorb] SLPI: Successfully created px4 task PX4_test_MUORB with tid 2097655
INFO  [muorb] succesfully did TOPIC_TEST_TYPE
INFO  [muorb] SLPI: Creating pthread test_MUORB

INFO  [muorb] SLPI: Successfully created px4 task PX4_test_MUORB with tid 2097654
INFO  [muorb] succesfully did UNSUBSCRIBE_TEST_TYPE
INFO  [muorb] SLPI: Creating pthread test_MUORB

INFO  [muorb] SLPI: Successfully created px4 task PX4_test_MUORB with tid 2097653
INFO  [muorb] muorb test passed

______  __   __    ___ 
| ___ \ \ \ / /   /   |
| |_/ /  \ V /   / /| |
|  __/   /   \  / /_| |
| |     / /^\ \ \___  |
\_|     \/   \/     |_/

px4 starting.

INFO  [muorb] SLPI: Advertising remote topic log_message
INFO  [px4] startup script: /bin/sh /usr/bin/voxl-px4-start 0
INFO  [parameters] Starting param sync THREAD
INFO  [muorb] SLPI: Starting param sync THREAD

*************************
GPS: HOLYBRO
RC: SPEKTRUM
POWER MANAGER: VOXLPM
DISTANCE SENSOR: NONE
OSD: DISABLE
EXTRA STEPS:
	
*************************

Running on M0054
INFO  [muorb] SLPI: before starting the qshell_entry task
INFO  [muorb] SLPI: Creating pthread qshell

INFO  [muorb] SLPI: Successfully created px4 task PX4_qshell with tid 2097652
INFO  [muorb] SLPI: qshell entry.....
INFO  [muorb] SLPI: after starting the qshell_entry task
INFO  [muorb] SLPI: Init app map initialized
INFO  [param] selected parameter default file /data/px4/param/parameters
INFO  [muorb] SLPI: Marking DeviceNode(parameter_client_reset_request) as advertised in process_remote_topic
INFO  [uORB] Marking DeviceNode(parameter_client_reset_response) as advertised in process_remote_topic
INFO  [muorb] SLPI: Advertising remote topic parameter_update
INFO  [muorb] SLPI: Marking DeviceNode(parameter_client_set_value_request) as advertised in process_remote_to
INFO  [uORB] Marking DeviceNode(parameter_server_set_used_request) as advertised in process_remote_topic
INFO  [muorb] SLPI: Marking DeviceNode(parameter_server_set_used_response) as advertised in process_remote_to
INFO  [uORB] Marking DeviceNode(parameter_client_set_value_response) as advertised in process_remote_topic
INFO  [parameters] BSON document size 3333 bytes, decoded 3333 bytes (INT32:50, FLOAT:104)
INFO  [logger] logger started (mode=all)
Starting IMU driver with no rotation
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [qshell] Send cmd: 'icm42688p start -s'
INFO  [muorb] SLPI: qshell gotten: icm42688p start -s
INFO  [muorb] SLPI:   arg0 = 'icm42688p'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI:   arg2 = '-s'

INFO  [muorb] SLPI: *** SPI Device ID 0x26000a 2490378
INFO  [uORB] Advertising remote topic sensor_accel
INFO  [uORB] Advertising remote topic sensor_gyro
INFO  [muorb] SLPI: ICM42688P::probe successful!
INFO  [muorb] SLPI: on SPI bus 1
INFO  [muorb] SLPI: icm42688p #0 on SPI bus 1
INFO  [muorb] SLPI: 

INFO  [muorb] SLPI: >>> ICM42688P this: 3176eb30
INFO  [muorb] SLPI: Ok executing command: icm42688p start -s
INFO  [uORB] Advertising remote topic qshell_retval
INFO  [muorb] SLPI: >>> ICM42688P this: 3176eb30
INFO  [qshell] qshell return value timestamp: 262948496, local time: 262952979
INFO  [muorb] SLPI: >>> ICM42688P this: 3176eb30
INFO  [muorb] SLPI: Register interrupt b21d3164 e6205e9c 3176eb30
INFO  [uORB] Advertising remote topic sensor_gyro_fifo
INFO  [uORB] Advertising remote topic sensor_accel_fifo
INFO  [uORB] Advertising remote topic imu_server
INFO  [qshell] Send cmd: 'icp101xx start -I -b 5'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: icp101xx start -I -b 5
INFO  [muorb] SLPI:   arg0 = 'icp101xx'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI:   arg2 = '-I'

INFO  [muorb] SLPI:   arg3 = '-b'

INFO  [muorb] SLPI:   arg4 = '5'

INFO  [muorb] SLPI: *** I2C Device ID 0xb76329 12018473
INFO  [muorb] SLPI: icp101xx #0 on I2C bus 5
INFO  [muorb] SLPI:  address 0x63
INFO  [muorb] SLPI: 

INFO  [muorb] SLPI: Ok executing command: icp101xx start -I -b 5
INFO  [qshell] qshell return value timestamp: 262991650, local time: 262992261
Starting ist8310 magnetometer
INFO  [qshell] Send cmd: 'ist8310 start -R 10 -X -b 1'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: ist8310 start -R 10 -X -b 1
INFO  [muorb] SLPI:   arg0 = 'ist8310'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI:   arg2 = '-R'

INFO  [muorb] SLPI:   arg3 = '10'

INFO  [muorb] SLPI:   arg4 = '-X'

INFO  [muorb] SLPI:   arg5 = '-b'

INFO  [muorb] SLPI:   arg6 = '1'

INFO  [muorb] SLPI: *** I2C Device ID 0x60e09 396809
INFO  [muorb] SLPI: ist8310 #0 on I2C bus 1
INFO  [muorb] SLPI:  (external)
INFO  [muorb] SLPI:  address 0xE
INFO  [muorb] SLPI:  rotation 10
INFO  [muorb] SLPI: 

INFO  [muorb] SLPI: Ok executing command: ist8310 start -R 10 -X -b 1
INFO  [qshell] qshell return value timestamp: 263025555, local time: 263026330
INFO  [qshell] Send cmd: 'gps start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: gps start
INFO  [muorb] SLPI:   arg0 = 'gps'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI: Creating pthread gps

INFO  [muorb] SLPI: Successfully created px4 task PX4_gps with tid 2097648
INFO  [muorb] SLPI: Ok executing command: gps start
INFO  [qshell] qshell return value timestamp: 263048076, local time: 263048948
Starting Holybro LED driver
INFO  [muorb] SLPI: >>> ICM42688P this: 3176eb30
INFO  [qshell] Send cmd: 'rgbled_ncp5623c start -X -b 1 -f 400 -a 56'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: rgbled_ncp5623c start -X -b 1 -f 400 -a 56
INFO  [muorb] SLPI:   arg0 = 'rgbled_ncp5623c'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI:   arg2 = '-X'

INFO  [muorb] SLPI:   arg3 = '-b'

INFO  [muorb] SLPI:   arg4 = '1'

INFO  [muorb] SLPI:   arg5 = '-f'

INFO  [muorb] SLPI:   arg6 = '400'

INFO  [muorb] SLPI:   arg7 = '-a'

INFO  [muorb] SLPI:   arg8 = '56'

INFO  [muorb] SLPI: *** I2C Device ID 0x7b3809 8075273
INFO  [muorb] SLPI: rgbled_ncp5623c #0 on I2C bus 1
INFO  [muorb] SLPI:  (external)
INFO  [muorb] SLPI:  address 0x38
INFO  [muorb] SLPI: 

INFO  [muorb] SLPI: Ok executing command: rgbled_ncp5623c start -X -b 1 -f 400 -a 56
INFO  [qshell] qshell return value timestamp: 263082514, local time: 263084020
INFO  [qshell] Send cmd: 'modal_io start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: modal_io start
INFO  [muorb] SLPI:   arg0 = 'modal_io'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [uORB] Advertising remote topic sensor_mag
INFO  [uORB] Advertising remote topic actuator_outputs
INFO  [muorb] SLPI: Ok executing command: modal_io start
INFO  [muorb] SLPI: Opened UART ESC device
INFO  [qshell] qshell return value timestamp: 263170284, local time: 263173206
Starting Spektrum RC
INFO  [uORB] Advertising remote topic sensor_baro
INFO  [qshell] Send cmd: 'spektrum_rc start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: spektrum_rc start
INFO  [muorb] SLPI:   arg0 = 'spektrum_rc'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI: Creating pthread spektrum_rc_main

INFO  [muorb] SLPI: Successfully created px4 task PX4_spektrum_rc_main with tid 2097645
INFO  [muorb] SLPI: Ok executing command: spektrum_rc start
INFO  [qshell] qshell return value timestamp: 263217799, local time: 263218642
INFO  [muorb] SLPI: Spektrum RC: Read no bytes from UART
INFO  [uORB] Advertising remote topic actuator_outputs_debug
INFO  [uORB] Advertising remote topic esc_status
ERROR [muorb] SLPI: Spektrum RC: Got 6 bytes. Protocol byte is 0x52
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: voxlpm start -X -b 2
INFO  [muorb] SLPI:   arg0 = 'voxlpm'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [muorb] SLPI:   arg2 = '-X'

INFO  [muorb] SLPI:   arg3 = '-b'

INFO  [muorb] SLPI:   arg4 = '2'

INFO  [muorb] SLPI: *** I2C Device ID 0xd24411 13779985
INFO  [qshell] Send cmd: 'voxlpm start -X -b 2'
INFO  [muorb] SLPI: Set i2c address 0x6a, fd 3
INFO  [muorb] SLPI: Set i2c address 0x44, fd 3
INFO  [uORB] Advertising remote topic battery_status
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [muorb] SLPI: voxlpm #0 on I2C bus 2
INFO  [muorb] SLPI:  (external)
INFO  [muorb] SLPI:  address 0x44
INFO  [muorb] SLPI: 

INFO  [muorb] SLPI: Ok executing command: voxlpm start -X -b 2
INFO  [uORB] Advertising remote topic power_monitor
INFO  [qshell] qshell return value timestamp: 263251129, local time: 263253445
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [qshell] Send cmd: 'sensors start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: sensors start
INFO  [muorb] SLPI:   arg0 = 'sensors'

INFO  [muorb] SLPI:   arg1 = 'start'

INFO  [uORB] Advertising remote topic sensor_selection
INFO  [uORB] Advertising remote topic sensors_status_imu
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [uORB] Advertising remote topic vehicle_acceleration
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [uORB] Advertising remote topic vehicle_angular_velocity
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [uORB] Advertising remote topic sensor_combined
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [uORB] Advertising remote topic vehicle_air_data
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [uORB] Advertising remote topic vehicle_gps_position
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Timeout waiting for parameter_server_set_used_response for SENS_MAG_MODE
INFO  [uORB] Advertising remote topic sensors_status_baro
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [uORB] Advertising remote topic vehicle_magnetometer
INFO  [uORB] Advertising remote topic sensor_preflight_mag
INFO  [uORB] Advertising remote topic vehicle_imu
INFO  [uORB] Advertising remote topic vehicle_imu_status
INFO  [muorb] SLPI: Ok executing command: sensors start
INFO  [uORB] Advertising remote topic sensors_status_mag
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [qshell] qshell return value timestamp: 263462076, local time: 263466609
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [qshell] Send cmd: 'ekf2 start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: ekf2 start
INFO  [muorb] SLPI:   arg0 = 'ekf2'

INFO  [muorb] SLPI:   arg1 = 'start'

ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [uORB] Advertising remote topic vehicle_attitude
INFO  [uORB] Advertising remote topic vehicle_local_position
INFO  [uORB] Advertising remote topic estimator_event_flags
INFO  [uORB] Advertising remote topic estimator_innovation_test_ratios
INFO  [uORB] Advertising remote topic estimator_innovation_variances
INFO  [uORB] Advertising remote topic estimator_innovations
INFO  [uORB] Advertising remote topic estimator_sensor_bias
INFO  [uORB] Advertising remote topic estimator_states
INFO  [uORB] Advertising remote topic estimator_status_flags
INFO  [uORB] Advertising remote topic estimator_status
INFO  [muorb] SLPI: Ok executing command: ekf2 start
INFO  [qshell] qshell return value timestamp: 263750947, local time: 263755362
INFO  [uORB] Advertising remote topic ekf2_timestamps
INFO  [uORB] Advertising remote topic vehicle_odometry
INFO  [uORB] Advertising remote topic estimator_aid_src_baro_hgt
INFO  [uORB] Advertising remote topic estimator_aid_src_fake_pos
INFO  [uORB] Advertising remote topic estimator_aid_src_fake_hgt
INFO  [uORB] Advertising remote topic estimator_aid_src_mag_heading
INFO  [uORB] Advertising remote topic estimator_aid_src_mag
INFO  [uORB] Advertising remote topic estimator_aid_src_gravity
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [qshell] Send cmd: 'mc_pos_control start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: mc_pos_control start
INFO  [muorb] SLPI:   arg0 = 'mc_pos_control'

INFO  [muorb] SLPI:   arg1 = 'start'

ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [uORB] Advertising remote topic takeoff_status
INFO  [muorb] SLPI: Ok executing command: mc_pos_control start
INFO  [qshell] qshell return value timestamp: 263841868, local time: 263843014
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [qshell] Send cmd: 'mc_att_control start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: mc_att_control start
INFO  [muorb] SLPI:   arg0 = 'mc_att_control'

INFO  [muorb] SLPI:   arg1 = 'start'

ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [muorb] SLPI: Ok executing command: mc_att_control start
INFO  [qshell] qshell return value timestamp: 263905079, local time: 263906174
INFO  [muorb] SLPI: baudrate set to 9600
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [muorb] SLPI: Sending initial CFG_VALSET. Attempt: 1
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [qshell] Send cmd: 'mc_rate_control start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: mc_rate_control start
INFO  [muorb] SLPI:   arg0 = 'mc_rate_control'

INFO  [muorb] SLPI:   arg1 = 'start'

ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [uORB] Advertising remote topic rate_ctrl_status
INFO  [muorb] SLPI: Ok executing command: mc_rate_control start
INFO  [qshell] qshell return value timestamp: 264001370, local time: 264002881
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [qshell] Send cmd: 'mc_hover_thrust_estimator start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: mc_hover_thrust_estimator start
INFO  [muorb] SLPI:   arg0 = 'mc_hover_thrust_estimator'

INFO  [muorb] SLPI:   arg1 = 'start'

ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [muorb] SLPI: Ok executing command: mc_hover_thrust_estimator start
INFO  [qshell] qshell return value timestamp: 264045767, local time: 264046812
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [qshell] Send cmd: 'mc_autotune_attitude_control start'
INFO  [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO  [muorb] SLPI: qshell gotten: mc_autotune_attitude_control start
INFO  [muorb] SLPI:   arg0 = 'mc_autotune_attitude_control'

INFO  [muorb] SLPI:   arg1 = 'start'

ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
INFO  [uORB] Advertising remote topic autotune_attitude_control_status
INFO  [muorb] SLPI: Ok executing command: mc_autotune_attitude_control start
INFO  [qshell] qshell return value timestamp: 264095634, local time: 264096726
ERROR [muorb] SLPI: Spektrum RC: Got 16 bytes. Protocol byte is 0x00
      ben grocholskyB 1 Reply Last reply Reply Quote 0
      • ben grocholskyB
        ben grocholsky @Chase Riley
        last edited by

        @Chase-Riley In the first of these two runs you were getting 0x01 protocol byte like I see on my DX7 transmitter. In that state with this binary you should see rc_input uorb messages and be able to try the Radio Calibration tool tab on QGroundControl.

        In the second run you're seeing 0x00 protocol byte and unfortunately I'm not sure what that means.

        If you can get the first case working repeatedly using one of the voxl-bind-spektrum options -t -f -s then we're on the path to a fix. Which did you use and have you tried them all?

        Chase RileyC 1 Reply Last reply Reply Quote 0
        • Chase RileyC
          Chase Riley @ben grocholsky
          last edited by

          @ben-grocholsky I am using a DX8 Transmitter during these test. Would the voxl-bind-spektrum be needed/do anything if I am not using the Spektrum bind board from Modal AI? I currently have the Spektrum receiver hooked directly to J19 on the VOXL2. When I was using SDK .0.9.5 I had the same receiver connected to the VOXL I/O board, and it worked great. Unfortunately the I/O board is not supported in SDK 1.0.0.

          ben grocholskyB 1 Reply Last reply Reply Quote 0
          • ben grocholskyB
            ben grocholsky @Chase Riley
            last edited by

            @Chase-Riley I didn't realize that had changed in V1.0. If you have access to a an alternative px4 fmu you could use the QGC pairing function to change the spektrum mode connected to that fmu and then plug it back into the voxl2. That could help check if one of the three options is more reliable. I'm not sure why you saw different data packets on a restart. Need to resolve that or try a different transmitter.

            Chase RileyC 1 Reply Last reply Reply Quote 0
            • Chase RileyC
              Chase Riley @ben grocholsky
              last edited by

              @ben-grocholsky @Eric-Katzfey I got it to work using by using the DSM2 binding method with another Px4 FMU. I do have a question though. I am now not able to get the actuators tab to show up in QGC for my ModalAI ESC. Would you DEB file have something to do with this? I have checked all my params in QGC and all seems to be correct. This was just the only other variable I could think of and wanted to check. Should I go back to running a standard DEB file? If so where would I find that now that I am running the custom debug one?

              Eric KatzfeyE 1 Reply Last reply Reply Quote 0
              • Eric KatzfeyE
                Eric Katzfey Dev Team @Chase Riley
                last edited by

                @Chase-Riley The standard px4 Debian package will set up the data correctly such that the actuators tab will be visible. For SDK 1.0 the packages are all available at http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.0/binary-arm64/. To grab the px4 package use wget http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.0/binary-arm64/voxl-px4_1.14.0-2.0.34_arm64.deb

                Chase RileyC 1 Reply Last reply Reply Quote 0
                • Chase RileyC
                  Chase Riley @Eric Katzfey
                  last edited by

                  @Eric-Katzfey Unfortunately once I switch back to the standard Debian package the Spektrum error is back. I had it working every power up with the Debian Package from Ben.

                  ben grocholskyB 1 Reply Last reply Reply Quote 0
                  • ben grocholskyB
                    ben grocholsky @Chase Riley
                    last edited by ben grocholsky

                    @Eric-Katzfey the test deb file was just voxl-dev branch with the one line change to accept (0x02|0x01) protocol bytes with the error output shortened below 80 characters + debug print bools and macros in DSM parsing forced on. I can fly that one line change on a Sentinel to look for any unexpected consequences. It'd be great to coordinate on how to get such a change merged into the dev branch and a non-debug deb to Chase.

                    Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                    • Eric KatzfeyE
                      Eric Katzfey Dev Team @ben grocholsky
                      last edited by

                      @ben-grocholsky That would be great! Just submit a PR and I can merge it in and then cut a new release.

                      ben grocholskyB Chase RileyC 2 Replies Last reply Reply Quote 0
                      • ben grocholskyB
                        ben grocholsky @Eric Katzfey
                        last edited by

                        @Eric-Katzfey https://github.com/modalai/px4-firmware/pull/42

                        Chase RileyC 1 Reply Last reply Reply Quote 0
                        • Chase RileyC
                          Chase Riley @Eric Katzfey
                          last edited by

                          This post is deleted!
                          1 Reply Last reply Reply Quote 0
                          • Chase RileyC
                            Chase Riley @ben grocholsky
                            last edited by

                            @ben-grocholsky @Eric-Katzfey That would be great if I could get this working. How long would this take to get merged?

                            Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                            • Eric KatzfeyE
                              Eric Katzfey Dev Team @Chase Riley
                              last edited by

                              @Chase-Riley I made version 1.14.0-2.0.54 with the Spektrum RC changes in it. You can get it with wget http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.54-202310161035_arm64.deb. Can you try it out and see if it fixes your issue?

                              Chase RileyC 2 Replies Last reply Reply Quote 0
                              • Chase RileyC
                                Chase Riley @Eric Katzfey
                                last edited by

                                @Eric-Katzfey Spektrum now works with that deb file, however I am not able to get the actuators tab in QGC just like @ben-grocholsky's deb file.

                                Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                                • Eric KatzfeyE
                                  Eric Katzfey Dev Team @Chase Riley
                                  last edited by

                                  @Chase-Riley Okay, glad that Spektrum is now working. Can you create a new post for the actuator tab issue. That is something completely different than the Spektrum RC issue. Thanks!

                                  Chase RileyC 1 Reply Last reply Reply Quote 0
                                  • Chase RileyC
                                    Chase Riley @Eric Katzfey
                                    last edited by

                                    @Eric-Katzfey I can make a new post if that is what you want me to do, however the issue that no actuator tab showing up has to do with the Debian Package Files that you and Ben have provided.

                                    Ben's: https://drive.google.com/file/d/1XJBdAKxR0C0tYPDgfOB1uUGCJ6Pv_3kV/view?usp=sharing

                                    Eric's: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.54-202310161035_arm64.deb

                                    If I flash the standard Debian Package File (http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.0/binary-arm64/voxl-px4_1.14.0-2.0.34_arm64.deb) the actuators tab appears as normal. The only time the actuators tab does not appear for me is when I am running a custom Debian Package supplied by you or Ben. Both the your's and Ben's Debian Package files solve the Spektrum issue but they both break the ESC functionality. Please reference the post below where you told me that the standard Debian Package file sets up the data correctly for the actuators tab.

                                    @Eric-Katzfey said in Voxl2 Spektrum Receiver error:

                                    @Chase-Riley The standard px4 Debian package will set up the data correctly such that the actuators tab will be visible. For SDK 1.0 the packages are all available at http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.0/binary-arm64/. To grab the px4 package use wget http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.0/binary-arm64/voxl-px4_1.14.0-2.0.34_arm64.deb

                                    Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                                    • Eric KatzfeyE
                                      Eric Katzfey Dev Team @Chase Riley
                                      last edited by

                                      @Chase-Riley Ah, sorry, didn't realize the correlation there. The one I prepared is an updated one from the SDK version that worked so it should be setting everything up correctly. But apparently something is wrong. We'll test and see if we can figure it out.

                                      Chase RileyC 1 Reply Last reply Reply Quote 0
                                      • Chase RileyC
                                        Chase Riley @Eric Katzfey
                                        last edited by

                                        @Eric-Katzfey Thanks for taking a look. I am standing by to see what you find out.

                                        Eric KatzfeyE 1 Reply Last reply Reply Quote 0
                                        • Eric KatzfeyE
                                          Eric Katzfey Dev Team @Chase Riley
                                          last edited by

                                          @Chase-Riley I started from scratch and flashed SDK 1.0.0 and could see the actuators tab on QGC 4.2.4. I then upgraded voxl-px4 to voxl-px4_1.14.0-2.0.54-202310161035_arm64.deb. I still see the actuators tab. Since Ben's Debian was based on an older px4 that didn't yet properly support the actuators tab it's possible that something got corrupted in that change.

                                          Chase RileyC 2 Replies Last reply Reply Quote 0
                                          • Chase RileyC
                                            Chase Riley @Eric Katzfey
                                            last edited by

                                            @Eric-Katzfey I will try that out and report back.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Powered by NodeBB | Contributors