[f5soh]

yes, this command will made the uploader and GPS firmware:

Code: [Select]

make uploader fw_gpsplatinum

[TheOtherCliff]

Is the Windows version of OpUploadTool still broken?  Is there a Jira to fix it?

[kicekilla]

I will look into it soon as I might need to update my opgpsv9 platinum. I have solid PH on 16.09 but have noticed I get a red x health status occasionally. I'll need to look to see if there were lost packets.

[kicekilla]

Also, I thought the gps firmware updated automatically when connected? Or is that just the ublox configs automatically?

[f5soh]

Firmware update is not automatic, just settings with autoconfig.

Take a look at second post in this thread
If you build the uploader from next, the windows command line uploader should works now.

[kicekilla]

well looked at my gps and def getting the packet errors every few seconds...

unfortunately I am completely lost in flashing the firmware, can't even find where to start with the instructions from the 2nd post haha I don't think I have the programming skills to get it done : /

[f5soh]

Code: [Select]

B - Firmware

This is performed using the uploader tool.
Connect a usb serial adapter or a CC/CC3D/revo configured with combridge at 57600.

Run the following command
UploaderTool -p ./build/fw_gpsplatinum/fw_gpsplatinum.opfw -t COMxx

Where COMxx is the serial com port from your USBSerial or Virtual Com Port using CC3D/Revo in Combridge config.

Quickly attach the gps using MCU+GPS port
it should show the sync succeded message and start uploading the firmware.
If it fails retry

You can also connect and start the tool without the initial wait progressbar if you find that more easy to do:
UploaderTool  -i -p ./fw_gpsplatinum.opfw -t COMxx
Combridge setup like here but 16.09 do not need baudrate settings :
https://librepilot.atlassian.net/wiki/display/LPDOC/Setup+a+bluetooth+for+telemetry#Setupabluetoothfortelemetry-CC3D-VirtualCOMport-Combridge

[TheOtherCliff]

Just for clarification, updating the GPSv9 (gpsplatinum) firmware is not a requirement.  The old GPSv9 firmware only looses a small percentage of packets (not a humanly noticeable flight difference) and it has always been this way; even back to the OP days.  It used to simply ignore these bad packets.

It's only now that these bad packets are fixed in the current GPSv9 firmware that the missed packets are reported in the FC firmware; so you know that there is an issue that you can fix by updating the GPS firmware.