Topics created by groupo

@groupo yes all the code is open sourced for this exact purpose - if you wish to make updates, you can fork your own instance of the repository - make your edits, compile, flash the deb onto your voxl2 and then provided everythign works as expected you can make an MR on gitlab from your fork to the dev branch and one of us will review and test prior to adding into the next release.

@groupo Yes, we have used px4-listener <topic name> for external monitoring of PX4 topic data in other applications.

Thank you @ben-grocholsky! I should be more clear, when I ran px4-listener sensor_gps I received something along the lines of "GPS never published". I just went to go get the verbatim output but everything seems to be working. I do indeed see the uorb now. Puzzling

@Vinny I had to QDL the drone again. I am not sure why this is happening. The first time was extremely obvious but these last two I am not sure what has went wrong. I will be extremely explicit about 'poweroff -f' going forward. Anyway I wiped and flashed it again. I am getting 13 satellites on one now and 20 on the other. This is obviously an improvement. A theory I had is maybe they are looking at different constellations? that would not make sense as I just wiped the 'bad' drone and do not recall ever seeing an option to change the constellation, let alone changing it. I asked earlier.... if I cannot resolve this can we either order a new antenna or send the drone back to have the antenna swapped? I am worried our pilots will not fly if the GPS is sub-optimal

@groupo I responded to your new post.

@groupo Exactly

hey not sure if this is an @tom or @modaltb inquiry, but when following the steps for the kernel build guide, stuff is off with the drone. It boots up and I can adb fine, but there are issues with the wifi, similar to another post Tom helped me with two weeks ago, but for definitely not the same hardware-related reason. The wifi adaptable does not turn on and when you run voxl-wifi the mac address is undefined. I remember stepping through those scripts while troubleshooting the hardware issues and recall that script queries to find its mac address, which must be returning something invalid.

I have tested this with both of my drones. I can very easily flash them back with https://docs.modalai.com/sentinel-factory-reset/ and they operate as expected. While my desire is to edit part of the usb driver scripts, the kernel I am attempting to put on the drone is the unchanged version following the steps here https://docs.modalai.com/voxl2-kernel-build-guide/. The only deviation from the guide is that the guide is written for SDK 1.1.3. I have put 1.3.0 on both of my drones, and from my understanding the docker scripts pull the default branch of each repo which has the same commit tags as 1.7.8. I have included the output of dmesg for both the 1.3.0 image available from the downloads page, and the results when following the custom kernel build steps.

https://drive.google.com/drive/folders/14L5gLbAOfF2OcSW2rHFTI4VIoREkTCFJ?usp=sharing

@groupo Yeah that option in voxl-configure-modem is correct, I should update it in the future to make it more clear.

This is what gets run on boot with that option: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/blob/master/scripts/voxl-modem-start?ref_type=heads#L122

For that modem, voxl-modem just acts as a wrapper for qmicli: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/blob/master/scripts/voxl-modem-start?ref_type=heads#L147

and udhcpc: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/blob/master/scripts/voxl-modem-start?ref_type=heads#L160

Feel free to modify the script as needed to fit your application