@Zachary-Lowell Thank you for your answer.
With some struggles, I found that /dev/ttyHS0 'exists' because putting this port doesn't give me any error. (But it could be some other port connected to the ARM, rather than the 4-pin JST port)
Anyway, do you know how to figure out which port name corresponds to the port on the board?
@Eric-Katzfey Thank you for your answer Eric.
Could you tell me about the J18 port, like which part of VOXL SDK is communicating with it?
Hi
I'm trying HITL with gazebo. It would be appreciated if you could help me with these 2 questions.
I'm trying to make a mavlink connection directly to the serial port (not via voxl-vision-px4. I configured it to connect with QGC and ROS via mavros.).
In voxl-px4-hitl.config, I tried
mavlink start -d /dev/uart_esc -b 921600 -m onboard -r 80000
because it seems the ESC is using J18.
https://docs.modalai.com/voxl2-esc-configs/
https://github.com/modalai/px4-firmware/blob/voxl-dev/boards/modalai/rb5-flight/voxl-px4.config#L124
But running voxl-px4-hitl says
ERROR [mavlink] Device /dev/uart_esc does not exist
Which port should I put in the config?
I was working on the voxl-dev branch because px4-firmware submodule in voxl-px4 is pointing to the latest commit in voxl-dev branch.
But the HITL guide is using voxl-master branch. I succeeded to build the target in voxl-master:
DONT_RUN=1 make px4_sitl_default gazebo
But it fails in voxl-dev.
I wonder if it is supposed to work or not.
And I wonder if it is okay to run voxl-dev on VOXL2 for HITL.
Thanks
@Eric-Katzfey Thanks, it works! I didn't know the last part (push the debian package and install there).
Hi
I managed to build the px4 firmware, following the guide:
https://docs.modalai.com/voxl2-px4-build-guide/
But I couldn't figure out how to upload the px4 firmware to VOXL2.
I want to make changes to the firmware.
Could anyone please let me know how?
I'm using Flight Deck and have the adb connection.
Thanks