decrepit said..
I'm getting that, "server index not found" error when I try to update the firmware, can't find the fix, search on this forum is useless.

Flex2 said..
Not sure if anyone else noticed this but been running an older BN220 unit alongside a BE180 (M10) unit for the last 4+ weeks (27 sessions). Consistently the newer M10 unit shows much better battery life as expected but the distance displayed on the unit (on sleep screen) is considerably less always showing +10% less distance. This is regardless of speed and whether chugging or planning at start. Other stats like 2s/Alpha agree but hr/NM may be affected by this distance glitch??. I keeping forgetting to check distance in realtime as I usually don't stop. The data files however match perfectly using KA72, GPSSeedreader, GPSAR etc and also ballpark Apple Watch so is trivial issue as data itself is fine. Both units running v5.78. Only difference in the configs is the M10 has GPS+GLONAS+GALILEO where the older unit has GPS+GLONAS. Older unit always display correct distance.
Image below: Left, Green/Blue is BN220 and on right blue/red is BE180/M10

decrepit said..
On another M10 difference note.
It seems that at 10hz the latest esp32 firmware has more missed points at 10hz, than the older 5.76. Has anybody else noticed this?

decrepit said..
On another M10 difference note.
It seems that at 10hz the latest esp32 firmware has more missed points at 10hz, than the older 5.76. Has anybody else noticed this?

sailquik said.. >> Also, please adjust the settings in the device FW so the mac address is displayed in the file name. This identifies files from the approved devices.

sailquik said..





Yes. The files I have seen from the later than FW V5.76 have an unacceptable number of missed points @10Hz. Changing back to FW V5.76 seems to solve this. Still a few missed points, but order of magnitude less, and acceptable..

From what we have seen, please stick to V5.76 for GPSTC approved devices until further notice.

Also, please adjust the settings in the device FW so the mac address is displayed in the file name. This identifies files from the approved devices.

sailquik said..





Yes. The files I have seen from the later than FW V5.76 have an unacceptable number of missed points @10Hz. Changing back to FW V5.76 seems to solve this. Still a few missed points, but order of magnitude less, and acceptable..

From what we have seen, please stick to V5.76 for GPSTC approved devices until further notice.

Also, please adjust the settings in the device FW so the mac address is displayed in the file name. This identifies files from the approved devices.

what about those of us still running with the BN220 GPS? Are the missing points there as well? I can supply some files if needed. se noticed this?

sailquik said..







I think it is just an M10 problem, as I have not seen that issue with M8 based units.

But it would be good if someone with M8 based units can report.

rp6conrad said..




I did just some changes (sw 5.80), and had a short test M10@10 Hz, settings only gpy file on, UBX NAVSAT OFF. No missing points :
File: Ali_M10_2310231721.gpy
No problems reading Ali_M10_2310231721.gpy

Observed time distribution (in ms):
100 20471

0 time errors (0 above 5.0 knots), about 0 missing points
32 filtered points:
SDOP/sAcc 27 points; max speed: 7.0 kn
Acceleration 6 points; max speed: 7.7 kn

Make sure that LOG UBX NAF SAT OFF setting is used. Even if no ubx file is saved, it this setting is on, these messages are send by the gps and processed by the esp. As the message length of NAV SAT is equal to nr of sats in the nav solution, this can possible give a buffer overrun.
I will change the sw, so that this setting is only active when setting the rate @5 Hz are lower and ubx file is on.
Greetings, Jan.

Rolz said..




So if we use the ubx file and the M8 we're still ok?

all my users (inc me) use KA72 to upload so the gpy file isn't supported.

JulienLe said..
M10 are underclocked because uBlox's goal was to close the gap with lower power competition. You can now bring them back to normal: content.u-blox.com/sites/default/files/documents/u-bloxM10-with-25Hz-Navigation-UpdateRate_IN_UBX-23006557.pdf

DavidRice said..
GPS DIY lessons
Having made a pair recently, with a lot of patient help from Captain Anita, I still managed to make some mistakes which may be helpful to future DIYers.Don't use a medium sized soldering iron with relatively thick cored soldering wire. The Captain was able to do so with the help of very high standard magnifying tools and incredibly steady hands, but I managed to make a mess of several joints, including too much flux, so we had to 'unsolder' them using woven copper tape to soak up the excess solder and flux. The copper tape worked surprisingly well.
Learning: buy a small tip soldering iron and some fine soldering wire for work on electronics (not the plumbing type which has a different type of flux). I also bought from Jaycar a heavy based tool with an LED magnifier and arms to hold small bits in place while soldering them. Only around $29.Learning: the soldered 'bridges' are tricky. Cut a short length of wire and solder that to the three terminals, rather than trying to bridge with solder alone.Don't be too firm pushing the assembled unit into the case. I broke one of the glass reed switches.
Learning: cut a slither off the Lilygo board, the nibs that protrude on the RHS close to the locating holes. A Dremmel tool worked really well. Only cut off a slither (say ? mm) but it made a difference.Before gluing the clear polycarbonate window onto the outside protection box, check the electronics are working - not just by taking it for a drive to check the display functions, but also check it will charge.
Learning: one of my units did not charge because I mistakenly but the ferrite below the battery instead of above. I knew where it had to go but made simple a mistake which meant I had to knock the window off to fix it.
When gluing the window onto the protection box, make sure the joint is well sealed, so the potting epoxy does not seep out. I actually anticipated this and taped around the outside, however, the potting mix still seeped out. I was able to stem this seepage by shoving the plastic surround over the tape, but by this time it was pretty messy.
Learning: paint around the joint with Rustoleum and let if cure before adding the potting mix. You can spray some Rustoleum into a glass jar and then dip the brush into it. This worked well for the second unit.
Don't put a messy, sticky unit in the sun to try and cure it more quickly, even after a couple of days. The potting mix was still just slightly fluid and a small amount seeped out which meant I had to top it up yet again. Learning: be patient, it takes many days to make these units.
Ricey

Flex2 said..
Not sure if anyone else noticed this but been running an older BN220 unit alongside a BE180 (M10) unit for the last 4+ weeks (27 sessions). Consistently the newer M10 unit shows much better battery life as expected but the distance displayed on the unit (on sleep screen) is considerably less always showing +10% less distance. This is regardless of speed and whether chugging or planning at start. Other stats like 2s/Alpha agree but hr/NM may be affected by this distance glitch??. I keeping forgetting to check distance in realtime as I usually don't stop. The data files however match perfectly using KA72, GPSSeedreader, GPSAR etc and also ballpark Apple Watch so is trivial issue as data itself is fine. Both units running v5.78. Only difference in the configs is the M10 has GPS+GLONAS+GALILEO where the older unit has GPS+GLONAS. Older unit always display correct distance.
Image below: Left, Green/Blue is BN220 and on right blue/red is BE180/M10