@tom SOLVED, thanks Tom, that command line prompt showed me that I needed to voxl-configure-extrinsics. Thank you!
Best posts made by Jeremy Frederick
-
RE: VOXL2 QVIO Pipeline Failing to Run
-
RE: Voxl 2 and Herelink Slow Video stream
@tom We're running v1.0.1 SDK. However, we were actually just able to get the RTSP stream working over Herelink with virtually no latency. Using the SiYiQgroundControl application on the Herelink, the RTSP works completely fine. I believe the issue is in the QGC firmware that ships stock with the Herelink controller. For now you can consider this thread solved. Thanks again!
Latest posts made by Jeremy Frederick
-
M0014 vs M0149 tracking cameras for indoor VIO
Hello,
I was searching through the product catalog and was wondering what the difference between the M0014 and M0149 cameras for indoor flight were. I see that the M0149 module is higher quality resolution, but there isn't much else on this specific sensor.
What are the main advantages of the M0149 over the M0014, does it provide a higher quality position hold with less risk for fall back?
-
RE: voxl-px4 service pipeline uORB failure
Alex, picking up this thread where swickliff left off. We tried a full partion wipe and are still having issues. Attached to this post is a .txt file with the entire PX4 startup output from command to crash.
voxl2:/$ voxl-px4
[INFO] Reading from /etc/modalai/voxl-px4.conf
Found DSP signature file
[INFO] Daemon mode enabled
GPS=AUTODETECT
RC=CRSF_RAW
ESC=VOXL_ESC
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_MUORBINFO [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_MUORBINFO [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_MUORBINFO [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_MUORBINFO [muorb] SLPI: Successfully created px4 task PX4_test_MUORB with tid 2097653
INFO [muorb] muorb test passed
| ___ \ \ \ / / / |
| |/ / \ V / / /| |
| __/ / \ / /| |
| | / /^\ \ ___ |
_| / / |_/px4 starting.
INFO [px4] startup script: /bin/sh /usr/bin/voxl-px4-start 0
INFO [muorb] SLPI: Advertising remote topic log_message
INFO [parameters] Starting param sync THREAD
INFO [muorb] SLPI: Starting param sync THREAD
GPS: AUTODETECT
RC: CRSF_RAW
ESC: VOXL_ESC
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 qshellINFO [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 1509 bytes, decoded 1509 bytes (INT32:29, FLOAT:41)
INFO [logger] logger started (mode=all)
Starting IMU driver with no rotation
INFO [qshell] Send cmd: 'icm42688p start -s'
INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
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: 3176c8a0
INFO [muorb] SLPI: Ok executing command: icm42688p start -s
INFO [uORB] Advertising remote topic qshell_retval
INFO [muorb] SLPI: >>> ICM42688P this: 3176c8a0
INFO [qshell] qshell return value timestamp: 380545341, local time: 380552974
INFO [muorb] SLPI: >>> ICM42688P this: 3176c8a0
INFO [muorb] SLPI: Register interrupt b21d3364 e6201b9c 3176c8a0
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: 380601909, local time: 380603599
Looking for qmc5883l magnetometer
INFO [qshell] Send cmd: 'qmc5883l start -R 10 -X -b 1'
INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO [muorb] SLPI: qshell gotten: qmc5883l start -R 10 -X -b 1
INFO [muorb] SLPI: arg0 = 'qmc5883l'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 0x80d09 527625
INFO [muorb] SLPI: >>> ICM42688P this: 3176c8a0
ERROR [muorb] SLPI: i2c probe failed
INFO [muorb] SLPI: PX4_qshell: no instance started (no device on bus?)
ERROR [muorb] SLPI: Failed to execute command: qmc5883l start -R 10 -X -b 1
INFO [qshell] cmd returned with: -1
INFO [qshell] qshell return value timestamp: 380665246, local time: 380666868
ERROR [qshell] Command failed
Looking for 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
ERROR [muorb] SLPI: i2c probe failed
INFO [muorb] SLPI: PX4_qshell: no instance started (no device on bus?)
ERROR [muorb] SLPI: Failed to execute command: ist8310 start -R 10 -X -b 1
INFO [qshell] cmd returned with: -1
INFO [qshell] qshell return value timestamp: 380701724, local time: 380702898
ERROR [qshell] Command failed
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 2097647
INFO [muorb] SLPI: Ok executing command: gps start
INFO [qshell] qshell return value timestamp: 380731993, local time: 380733860
Looking for ncp5623c RGB LED
INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO [qshell] Send cmd: 'rgbled_ncp5623c start -X -b 1 -f 400 -a 56'
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: Set i2c address 0x38, fd 3
ERROR [muorb] SLPI: i2c probe failed
INFO [muorb] SLPI: PX4_qshell: no instance started (no device on bus?)
ERROR [muorb] SLPI: Failed to execute command: rgbled_ncp5623c start -X -b 1 -f 400 -a 56
INFO [qshell] cmd returned with: -1
INFO [qshell] qshell return value timestamp: 380774191, local time: 380776550
ERROR [qshell] Command failed
Starting VOXL ESC driver
INFO [uORB] Advertising remote topic sensor_baro
INFO [qshell] Send cmd: 'voxl_esc start'
INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO [muorb] SLPI: qshell gotten: voxl_esc start
INFO [muorb] SLPI: arg0 = 'voxl_esc'INFO [muorb] SLPI: arg1 = 'start'
INFO [uORB] Advertising remote topic actuator_outputs
INFO [muorb] SLPI: Ok executing command: voxl_esc start
INFO [muorb] SLPI: Opened UART ESC device
INFO [qshell] qshell return value timestamp: 380907621, local time: 380909607
Starting CRSF RC driver
INFO [uORB] Advertising remote topic esc_status
INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO [qshell] Send cmd: 'crsf_rc start -d 7'
INFO [muorb] SLPI: qshell gotten: crsf_rc start -d 7
INFO [muorb] SLPI: arg0 = 'crsf_rc'INFO [muorb] SLPI: arg1 = 'start'
INFO [muorb] SLPI: arg2 = '-d'
INFO [muorb] SLPI: arg3 = '7'
INFO [muorb] SLPI: Ok executing command: crsf_rc start -d 7
INFO [muorb] SLPI: Crsf serial opened sucessfully
INFO [muorb] SLPI: Crsf serial is single wire. Telemetry disabled
INFO [uORB] Advertising remote topic input_rc
INFO [qshell] qshell return value timestamp: 380966325, local time: 380968275
INFO [qshell] Send cmd: 'voxlpm start -X -b 2'
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 [muorb] SLPI: baudrate set to 9600
INFO [muorb] SLPI: Sending initial CFG_VALSET. Attempt: 1
INFO [muorb] SLPI: Sending initial CFG_VALSET. Attempt: 2
INFO [muorb] SLPI: Sending initial CFG_VALSET. Attempt: 3
INFO [muorb] SLPI: Set i2c address 0x6a, fd 4
INFO [muorb] SLPI: baudrate set to 9600
INFO [muorb] SLPI: Sending initial CFG_VALSET. Attempt: 1
INFO [muorb] SLPI: Sending initial CFG_VALSET. Attempt: 2
terminate called after throwing an instance of 'qmi_error'
what(): qmi_client_send_msg_sync() failed, (client_id=)0, result=0: qmi error (-16)
/usr/bin/voxl-px4: line 147: 5263 Aborted GPS=$GPS RC=$RC ESC=$ESC POWER_MANAGER=$POWER_MANAGER DISTANCE_SENSOR=$DISTANCE_SENSOR OSD=$OSD EXTRA_STEPS=$EXTRA_STEPS px4 $DAEMON -s /usr/bin/voxl-px4-start
voxl2:/$ ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running
ERROR [px4] PX4 server not running -
RE: VOXL 2 IO Board troubleshooting - Driver will not start
@Alex-Kushleyev I appreciate it, all is working now
-
RE: VOXL 2 IO Board troubleshooting - Driver will not start
@Eric-Katzfey I'm not looking to run RC through the IO board, I'm using external RC commands for control. I'm looking to utilize the PWM outputs on the board to control a servo for a dropper mechanism. I made the change and am commanding the start of the voxl2_io driver successfully. As of now I am still unable to drive a servo through the QGC actuators tab, all the correct parameters have been loaded.
-
RE: VOXL 2 IO Board troubleshooting - Driver will not start
@Jeremy-Frederick Alex, thanks for the quick response. It looks like PX4 is still expecting to find the IO board on port 2, where do I need to update the uart number? Originally I thought updating the UART number in the flashing bash script was all that is necessary but now I see why that was an incorrect assumption.
-
RE: Mavlink camera Manager (0.9) functionality in SDK 1.0.0
@Eric-Katzfey This is working great, been playing around with it for the last week or so. The next thing I'll be working on will be the order in which the cameras streams are displayed to QGC. It seems right now on boot the initial stream that comes up in randomized over the various camera being fed into QGC.
-
VOXL 2 IO Board troubleshooting - Driver will not start
Hello,
I just received my new VOXL IO board with the updated bootloader and I'm working to integrate it now. Here is an explanation of my setup and the programming steps I've taken so far.
Goal:
Manipulate a servo using the VOXL IO board's PWM output.Setup:
VOXL2 running SDK 1.1.2, VOXL IO board with latest bootloader, plugged into port J19, VOXL_ESC for ESC and EXTERNAL for RC command.Programming Steps:
Flashed the updated firmware with the UART 7 edit made for J19 utilization, flashed the voxl_io parameters using the px4-configure wizard. Everything during this process seems to have worked fine.Issue:
Whenever I try to start the voxl2_io driver, I receive the following: -
Tips For Reducing the amount of time the microhard modems take to connect
Working with the pMDDL 2350 modems with VOXL 2 and SDK 1.1.2.
Currently we're experiencing anywhere from 45-90 second connection times before a link is made between QGC and VOXL. I was wondering if the community had any tips on reducing this connection time at all through the configuration.
-
RE: Support for Video to Parent Computer through QGC
@Eric-Katzfey Apologies I missed a typo in the topic line, what I meant to ask was in regards to support for recording video through QGC and saving it to the parent computer instead of locally on the VOXL 2.
-
Support for Video to Parent Computer through QGC
Just wanted to check in on this feature and see when it will be supported.