@Eric-Katzfey As for now, it is blinking with a red color. I was able to do a compass calibration, but it does not show the location in the map. I'll try to investigate on the matter. Thank you for your responses.

Here's the location database source code. You should be able to figure out how to configure from this

https://gitlab.com/voxl-public/voxl-sdk/services/voxl-tag-detector/-/blob/master/server/locations.c

@Aaky Please follow the instructions in the readme file. https://gitlab.com/voxl-public/rb5-flight/rb5-flight-px4-build-docker/-/blob/master/README.md. It explains how to build the Docker image.

@Moderator Thanks for the clarification, we will not expect a solution to this then.

@camharrisvayu Ok, we should be able to close this issue -- I flashed 1.0.0 and uploaded params for the sentinel model and that made it so the RC inputs could control the drone -- not sure which parameter made the difference, but I may investigate and report back if I find out.

Similar to you both:

voxl-camera-server | Enabled | Running | 71.1% voxl-cpu-monitor | Enabled | Running | 0.1% voxl-dfs-server | Disabled | Not Running | voxl-feature-tracker | Disabled | Not Running | voxl-flow-server | Disabled | Not Running | voxl-imu-server | Enabled | Running | 1.5% voxl-lepton-server | Disabled | Not Running | voxl-mavcam-manager | Disabled | Not Running | voxl-mavlink-server | Enabled | Running | 0.2% voxl-modem | Disabled | Not Running | voxl-portal | Enabled | Running | 60.1%

This is with HIRES, Tracking, Stereo on SDK 1.0. I also disabled large encoding on the HIRES from the camera server. Just bumping to see if this is expected.

@Jgaucin voxl-tflite-server is just a wrapper for standard TensorFlow Lite that has been compiled with the proper configurations to take advantage of QRB5165.

voxl-tflite-server code

So, if you can achieve what you are trying to do using TensorFlow Lite on the desktop, then you should be able to bring over to VOXL 2 in a straightforward manner.

The inference_worker function here is where the models are processed

At this point there is nothing new to share. New hardware designs and new software is required to achieve that use case which is a significant amount of work. We hope to have more to share within the next 12 months, but we don't have more precise estimates beyond that.

@John-Nomikos Can you enable debug output messages on voxl-streamer (Use -v 0) and post the output? Thanks!

Hi @wilkinsaf
I was just thinking about your issue was going to ping you for an update.
Well, yes, good that it is not repeatable, but bummer we do not know why you had it in the first place so we can all learn why.
More importantly, I hope that Voxl2 is functioning correct given the error condition from the non-Quectel modem that was introduced. I also hope you verified your PDB board has the correct grounding scheme.

Ping on us again if you need any extra help/tips/etc.
Best option is always a new thread, or make sure to tag me on on existing threads.

Thanks!

@Vinny

@Vinny said in GPS Not OK with VOXL2 PX4:

Hi @kp-ng
Eric has you covered with all SW.
A small tip: From what I see in your picture, please understand that if you have WiFi and GPS antennas next to that very large power supply and no space between them, your radio link performance will be terrible.
There is a good chance you will not pick up any satellites, and your WiFi link will disconnect often.
For optimal performance, try to mimic the spatial separation that you would expect to see on one of our drone platforms.
Thanks!

^Can you provide an example what the ideal routing for wifi antennae would be on the sentinel drone platform (specifically with the microhard modem carrier add-on)? I came across this post while trying to troubleshoot my own issues and realized that the way I have the antennae routed coming out the back of the flight deck puts one of them right next to the gps module because of how the modem is oriented.

@wilkinsaf , M0027 was never shipped to any customers, as it was a test version of the ESC. So there should only be M0049, M0117, M0134 and M0129 (mini) ESCs out there. Like Vinny said, all of those ESCs have a blue status LED for each MCU.

If your ESC has a larger rectangular shape (as opposed to a square), it could be a really old ESC (Atmel-based, not STM32-based), which we do not really support any more. I hope this helps!

Alex

@Alex-Kushleyev

Confirmed, changing the MODAL_IO_BAUD to 250000 fixed the problem for me. Thank you so much for the help!

@Chad-Sweet Is this issue, reported also here, solved?

@Eric-Katzfey I did what you suggested and it works! Thank you again!