Raúl Ortega

i2cWriteBuffer() function is not deffined for F3 boards, it is missing in src/main/drivers/bus_i2c_stm32f30x.c file.

Please, could you be more explicit about which paramas are not saved? Thanks.

Are you using Ardupilot on your PX4? In Mission Planner you may select mavlink v1 protocol for the telemetry port you desire.

> > > Px4. And mavlink v2 is old so wondering why not update to v2 spec? Because you can select both versions in Mission Planner. Implementing v2 means spending...

Ok, let's try to do it. Please, could you provide a zip file, or a link to the library you exactly would like to use? I also need version number...

That's the idea, replace the v1 with v2 library and compile it. The library is placed at [this folder](https://github.com/raul-ortega/u360gts/tree/master/src/main/tracker/Mavlink). If it doesn't work properly, you have to modify this file...

I think there is no need to have telemetry_provider on the OLED. This param is only taken into account for DIY GPS, FrSky X and FrSky D. I think nobody...

Did you experienced more issues like described? Thanks.

Dear @pmarkiewicz, thanks so much for your contribution. The PR should be done from your development branch to the development branch of u360gts repo. Please, could you merge the code...

Which fc do you have SPRACINGF3?