@tom
Thank you for the quick response.
However,
it doesn't explain why the same board with the same doodle lab nano radio works with the VOXL 2 previously ( just suddenly doesn't work anymore ) and work with other VOXL 2.
And
we are using
https://techlibrary.doodlelabs.com/doodle-labs-nano-oem-mesh-rider-radio-24002482-mhz
It doesn't require that much power
please let me know if any misunderstanding, any suggestion, or any command/method we can use to verify the J port
Thank you.
we use this board
https://www.modalai.com/products/m0151?variant=47083939791152
with the Doodle lab nano radio
https://doodlelabs.com/product/nano-mesh-rider-radio/
Thank you for the quick response and please let me know if any further quesitons.
To whom it may concern,
Is there a command or diagnostic procedure to verify the operational status of the J port on a VOXL2?
Details:
We have integrated a board that includes a radio device with the VOXL2 via the J port. Initially, the VOXL2 detected the connection and the interface appeared as eth0. However, this VOXL2 has since stopped recognizing the connection. When the same board and radio device are tested with a different VOXL2, the connection is detected normally, which suggests the problem is isolated to this particular unit.
Could you advise on tools, commands, or logs that can be used to determine whether the J port hardware or the associated network interface on this VOXL2 is functioning correctly?
Please let me know if you need more details or questions
Thank you.
@Alex-Kushleyev
Thank you so much for the detailed explanation!
I will keep you posted with the update shortly.
Hello @Alex-Kushleyev and @Moderator ,
Thank you for the response!!!
As Alex pointed out, the baud rate seems to be the issue preventing the motors from spinning through the Actuator Testing feature in QGC. I have another ESC configured with a 2M baud rate, and it works as expected with Actuator Testing.
My question now is: how can I update the baud rate on the ESC?
In QGC, the baud rate is already set to 2M.
In https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/tree/master/voxl-esc-tools,
I came across the command:
./voxl-esc-upload-params.py --params-file ../params/esc_params_modalai_4_in_1.xml
However, I wasn’t able to locate this XML file on the VOXL.
Here's what I found in the VOXL:
In the repo I found is esc_params_modalai_4_in_1_revb_mn1804_2400kv_gemfan5040.xml
Should I upload this xml to /usr/share/modalai/voxl-esc-params/boards/, rename it to esc_params_modalai_4_in_1.xml, and use the python command above?
I also tried to manually change the baud rate to 2M in those XML files but it gets overwritten after a reboot.
Could you please provide more detailed instructions on how to properly update the ESC baud rate?
Thank you.
To whom it may concern,
My VOXL2 Flight Deck is currently running the following SDK version:
The ESC Mini 4-in-1 is using the following firmware version:
I am able to successfully spin the motors using the command:
voxl-esc 3) spin
However, I am unable to spin the motors in QGroundControl using the Actuator Testing feature.
Could you advise if there are any steps I might have missed?
====
Additionally, I have connected the VOXL2 to a QGC instance running on an Ubuntu machine within the same network.
I noticed that the ESC PWM Minimum and Maximum Calibration in QGC requires a USB connection.
I attempted to connect the VOXL2 to the Ubuntu machine via the USB-C port labeled "U" in the VOXL2 datasheet, but it did not establish a connection.
Could you clarify which port should be used for this USB connection to ensure proper calibration support in QGC?
Thank you for your assistance and please let me know if you need more details.
@Eric-Katzfey
Very sorry for the late response and thank you for pointing out the mavlink-router approach, https://github.com/mavlink-router/mavlink-router.
I will try it and keep you posted here.
Thank you for answering my quesiton.
Hello @Nathan-Raras and @Nathan-Raras ,
I don't see any Qualcomm device with running "lsusb".
I also have confirmed that the USB-C cable is able to access another VOXL device.
So I have submitted the RMA
Please let me know if any questions or suggestions.
Thank you very much for supporting.
Hello ModalAI Team,
Here is the HW and SDK info
Thank you.
Hello ModalAI Team,
If you need any additional information regarding the issue I’m currently experiencing, please don’t hesitate to let me know.
I appreciate your time and support on this matter.
Hello,
if you need any other information for this question,
please don't hesitate to let me know.
Thank you for helping!
To whom it may concern,
following this instruction to https://docs.modalai.com/voxl2-unbricking/
slide the SW2 switch into the ON position,
but in QDL Tool, it shows QDL device not connected.
I have confirmed that the USB-C cable works with other VOXL devices.
Any suggestions or anything I missed?
Thank you for your precious time on this.
Re: MAVLink custom port to GCS
Hello @Eric-Katzfey ,
is there any plan for ModalAI to support this request?
I am also interested in having this feature.
Thank you for your precious time on this matter.
Best,
From other discussion,
I add
qshell gps start -d 7 -b 115200
and get the GPS now.
Here is my setting and please let me know if any questions.
Thank you for your precious time on this matter.
AIRFRAME=MULTICOPTER
GPS=AUTODETECT
RC=CRSF_RAW
ESC=VOXL_ESC
POWER_MANAGER=VOXLPM
AIRSPEED_SENSOR=NONE
DISTANCE_SENSOR=NONE
OSD=DISABLE
DAEMON_MODE=ENABLE
SENSOR_CAL=ACTUAL
ARTIFACT_MODE=DISABLE
EXTRA_STEPS=(
qshell gps start -d 7 -b 115200
)
@will-huang-oksi said in SYS_AUTOSTART param missing, shown in QGC, after flashing the flight deck with voxl2_SDK_1.4.1:
Thank you for the feedback.
Before your response, I added "-w" to re-flash the VOXL and resolved the SYS_AUTOSTART issue
./install.sh -w
Now I can calibrate the VOXL 2 flight deck.
If you need the flashing process log, let me know since I don't have privilege to upload any file yet.
NOW the remaining issue I have is no GPS fix.
The output from voxl-inspect-gps isdt(ms) |fix type|Sats|Latitude(deg)|Longitude(deg)| Alt(m) |Vel(m/s)|HorErr(m)|AltErr(m)|
124.9 | NO GPS | 0 | 0.0000000 | 0.0000000 | -17.0 | 0.00 | 4294967.295 | 3794659.840 |^CIn voxl-px4.conf
I tried GPS=AUTODETECT and GPS=MRO, but none of them works.
I connect Taoglas GPS "Classic" M9N w/IST8308 - M10034 to the J19 port.Here is the full configuration in the voxl-px4.conf
AIRFRAME=MULTICOPTER
GPS=AUTODETECT
RC=CRSF_RAW
ESC=VOXL_ESC
POWER_MANAGER=VOXLPM
AIRSPEED_SENSOR=NONE
DISTANCE_SENSOR=NONE
OSD=DISABLE
DAEMON_MODE=ENABLE
SENSOR_CAL=ACTUAL
ARTIFACT_MODE=DISABLE
EXTRA_STEPS=()Also there is no output from
cat /dev/ttyHS0
cat /dev/ttyHS1
cat /dev/ttyHS2
cat /dev/ttyHS3And this is what I have from journalctl -u voxl-px4 -n 100
-- Logs begin at Thu 2023-03-02 12:58:02 UTC, end at Thu 2023-03-02 13:35:18 UTC. --
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [uORB] Advertising remote topic takeoff_status
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: Ok executing command: mc_pos_control start
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: qshell gotten: mc_att_control start
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: arg0 = 'mc_att_control'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: arg1 = 'start'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: Ok executing command: mc_att_control start
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: qshell gotten: mc_rate_control start
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: arg0 = 'mc_rate_controINFO [qshell] Send cmd: 'mc_rate_control start'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] qshell return value timestamp: 2036903088, local time: 2036905841
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] Send cmd: 'mc_hover_thrust_estimator start'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] qshell return value timestamp: 2036964219, local time: 2036966402
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] Send cmd: 'mc_autotune_attitude_control start'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] qshell return value timestamp: 2037021853, local time: 2037025239
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] Send cmd: 'land_detector start multicopter'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] qshell return value timestamp: 2037083571, local time: 2037085728
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] Send cmd: 'manual_control start'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] qshell return value timestamp: 2037144972, local time: 2037146917Any suggestions or any information you need?
Thank you for helping.
I found a mistake
Previously I select flight-deck when re-flash.
This time with -w I select voxl2 flight-deck
Sorry for confusion.
So the only issue I have now is the GPS issue.
Please let me know if any questions or suggestions.
Thank you for the feedback.
Before your response, I added "-w" to re-flash the VOXL and resolved the SYS_AUTOSTART issue
./install.sh -w
Now I can calibrate the VOXL 2 flight deck.
If you need the flashing process log, let me know since I don't have privilege to upload any file yet.
NOW the remaining issue I have is no GPS fix.
The output from voxl-inspect-gps is
dt(ms) |fix type|Sats|Latitude(deg)|Longitude(deg)| Alt(m) |Vel(m/s)|HorErr(m)|AltErr(m)|
124.9 | NO GPS | 0 | 0.0000000 | 0.0000000 | -17.0 | 0.00 | 4294967.295 | 3794659.840 |^C
In voxl-px4.conf
I tried GPS=AUTODETECT and GPS=MRO, but none of them works.
I connect Taoglas GPS "Classic" M9N w/IST8308 - M10034 to the J19 port.
Here is the full configuration in the voxl-px4.conf
AIRFRAME=MULTICOPTER
GPS=AUTODETECT
RC=CRSF_RAW
ESC=VOXL_ESC
POWER_MANAGER=VOXLPM
AIRSPEED_SENSOR=NONE
DISTANCE_SENSOR=NONE
OSD=DISABLE
DAEMON_MODE=ENABLE
SENSOR_CAL=ACTUAL
ARTIFACT_MODE=DISABLE
EXTRA_STEPS=()
Also there is no output from
cat /dev/ttyHS0
cat /dev/ttyHS1
cat /dev/ttyHS2
cat /dev/ttyHS3
And this is what I have from journalctl -u voxl-px4 -n 100
-- Logs begin at Thu 2023-03-02 12:58:02 UTC, end at Thu 2023-03-02 13:35:18 UTC. --
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [uORB] Advertising remote topic takeoff_status
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: Ok executing command: mc_pos_control start
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: qshell gotten: mc_att_control start
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: arg0 = 'mc_att_control'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: arg1 = 'start'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: Ok executing command: mc_att_control start
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: Marking DeviceNode(qshell_req) as advertised in process_remote_topic
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: qshell gotten: mc_rate_control start
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [muorb] SLPI: arg0 = 'mc_rate_controINFO [qshell] Send cmd: 'mc_rate_control start'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] qshell return value timestamp: 2036903088, local time: 2036905841
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] Send cmd: 'mc_hover_thrust_estimator start'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] qshell return value timestamp: 2036964219, local time: 2036966402
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] Send cmd: 'mc_autotune_attitude_control start'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] qshell return value timestamp: 2037021853, local time: 2037025239
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] Send cmd: 'land_detector start multicopter'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] qshell return value timestamp: 2037083571, local time: 2037085728
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] Send cmd: 'manual_control start'
Mar 02 13:31:54 m0054 voxl-px4[4783]: INFO [qshell] qshell return value timestamp: 2037144972, local time: 2037146917
Any suggestions or any information you need?
Thank you for helping.
Because having the missing parameter issue and a lot of sections are in red,
the VOXL flight deck is never armed and therefore there is no px4 log.
Thank you for your precious time on this matter, and please let me know any other log/file will be helpful.