ok so I built it and did a run on my electric scooter, but how do I get it to stop so I can upload my tracks for comparison?
it just keeps cycling through screen?
After your session, you have to switch it off with the magnet : the reedswitch must be activated for >2s, then the unit will save the session and close all files. You could do the same with pushing the GPIO39 for 2s. When you are back in range of your SSID (@home), you switch the unit back on with a short activation of the reed switch. It will boot and directly connect to your SSID. The IP adress is showing in the screen, just put this IP-adress in your browser and the webserver shows all the files on the sd. Download the preferred files and you can upload them to GP3S / GPSTC...
See docs.google.com/document/d/1j86kj3bNMID3sHCRT7QTYyrL7IHeQnGPec1LajsDfB4/edit#
Greetings, Jan.
Select to expand quoterp6conrad said..
After your session, you have to switch it off with the magnet : the reedswitch must be activated for >2s, then the unit will save the session and close all files. You could do the same with pushing the GPIO39 for 2s. When you are back in range of your SSID (@home), you switch the unit back on with a short activation of the reed switch. It will boot and directly connect to your SSID. The IP adress is showing in the screen, just put this IP-adress in your browser and the webserver shows all the files on the sd. Download the preferred files and you can upload them to GP3S / GPSTC...
See docs.google.com/document/d/1j86kj3bNMID3sHCRT7QTYyrL7IHeQnGPec1LajsDfB4/edit#
Greetings, Jan.
ah good old RTFM! 
I need to position the reed switch in a better spot then!
first test looks good! other gps I used was a gw60
once I get reed switch sorted I'll do another test with a min-motion as well
ok worked out how to turn off and on the device... I know all about how reed switches work 
Below are screenshots of mini-motion, gw60 and esp-gps
Was interesting the GW60 took a little bit to find a good sat signal, but when it did it all lined up ok.
Also seems I need to check timezone on mini-motion
Super happy with it!
Would we be better off having a separate topic for hardware validation (for gpst) it could otherwise get lost in here pretty easily.
Waiting for my waterproofing to arrive and then next comes the real test! 
In GPS SpeedReader, if you click Settings|About it will show the filenames and graph colours.
I'm betting green is the GW60 because of the high SDoP.
But which is blue? that's a bit problematic with persistent low spikes and loss of accuracy. The red line is by far the best. I'm betting on the motion, as the accuracy is steady but not as good as the best of the blue. The esp, can receive more sats than the motion so can have slightly higher accuracy.
If I'm correct, the ESP is under-performing for some reason, did it have the same sky view as the others?
It would be good to sort this before potting.
Select to expand quotedecrepit said..
I'm betting green is the GW60 because of the high SDoP.
But which is blue? that's a bit problematic with persistent low spikes and loss of accuracy. The red line is by far the best. I'm betting on the motion, as the accuracy is steady but not as good as the best of the blue. The esp, can receive more sats than the motion so can have slightly higher accuracy.
If I'm correct, the ESP is under-performing for some reason, did it have the same sky view as the others?
It would be good to sort this before potting.
Yup!
I'm still waiting for my waterproofing paint to arrive, so pulled it all a part again.
I wanted to ask what way up should the gps module be facing? I had it name up, but now looking at it, it might be the other way might be better?
Also I had it floating loose in mount, but thanks to Freezers doco I'll use the packing foam that came with the esp32 unit to make sure it doesn't rattle around... possibly also causing signal discrepancy
Yep, I made that mistake with one of the ones I made, blank side is the antenna, writing side is the electronics.
So now you see why we have to test them, it's all too easy to get something wrong.
There is a new update of the sw, with support for gpx and gpy format. I did some testing with next results :
With a Sandisk Ultra 16GB card :
@5Hz, ubx, gpy, sbp and gpx logged together with no lost points
@10Hz, ubx, gpy, sbp and gps logged together gives lost points
@10Hz, ubx, gpy and sbp logged together no lost points.
The open source gpy format is mainly the work of Peter, you find more info on his github : github.com/prichterich/compactgnss
As for now, only gps-speedreader can handle this format. The main advantages of this format : file size is only 22% compared to ubx. Only the needed fields are in it, no overhead. And it is open source !!!
As this is the first draft, be aware that there still might be some issues.
* SW5.63 : github.com/RP6conrad/ESP-GPS-Logger
* Added GPX file format
* Added GPY file format
* If no config file : Wifi AP waiting time = 120 s
* Bugfix config webserver : no switching to km/h if knots was set
* Added support for BN266 e-paper
* Changed GPS-parser union to struct, every ubx message has its own struct now
* Added ubx nav dop Msg for extracting HDOP
* Added ubx mon ver Msf for extracting sw / hw version ublox
* Changed baudrate ublox to 38400, necessary for 10Hz navDOP + navPVT
* Correction timestamp list files with FTP
* Added sail logo "Severne" = 10
* Added board logo "F2" = 10
* Bugfix for SSID with white space
* Added watchtdog for WAKE UP screen (hangs sometimes after OTA)
* Added loadbalance for flushfiles()
Greetings, Jan
Thanks for all your efforts jan and everyone else involved. I'm sure you all worked hard to get the update out before Christmas.
merry Christmas everyone and look forward to some wind after Christmas!
cheers Shannon.
Thanks again Jan, I've updated one of mine for the time being. and just set it to UBX and GPY. If there any bugs I'm sure to find them.
And thanks for fixing the units persistence in the config adjustment. I caught caught a couple of times, with my speeds reverting to km/hr.
Nice work thank you.
A couple of small things. Ignore if it's just me.
- The two seconds between screens seems a little fast, configurable?
- I'm afraid to connect both of mine to home wifi at the same, they seem to have the same AP name.
- config updateable in AP mode? Wouldn't work on Chrome on Android.
Select to expand quoteremery said..
- I'm afraid to connect both of mine to home wifi at the same, they seem to have the same AP name.
- config updateable in AP mode? Wouldn't work on Chrome on Android.
There's a warning somewhere about doing that
Select to expand quoteremery said..
- The two seconds between screens seems a little fast, configurable?
- I'm afraid to connect both of mine to home wifi at the same, they seem to have the same AP name.
- config updateable in AP mode? Wouldn't work on Chrome on Android.
Two seconds between stat screens will be made configurable (next update).
If you are on your home wifi, you can connect to multi loggers at the same time : Every logger will get his own IP adress, and over the IP you connect to the logger.
On AP-mode, only 1 logger can be active, as both will have the same "ESP32AP" SSID name.
The configuration can be accessed and changed in AP-mode (just tried it an my S7 Android phone with Chrome). Downloading files should also be possible in AP-mode.
However, update with a new firmware (OTA, over the air update) is not possible, as Internet connection is here mandatory.
Greetings, Jan.
Thanks for that. Before I posted the menu button on my S20/Chrome just flashed when in AP mode instead of bringing up some choices. I'll give it another go.
Awesome work Peter and Jan on the new GPY format, nice small files to download andeasy to process with GPS Speedreader.
Many thanks to all the developers of this brilliant concept, it started out good and is only getting better.
EDIT!!
Looks like I put the magnet too close to the unit when I packed up, this one turned on for the drive to the beach! No wonder it was reading high.
I downloaded the file again and now it opens without a fuss. So relax everybody, nothing to see here!
I have a problem with the latest firmware, it says it's reading in knots but the numbers are much to big,
2s says 42 instead of 34 distance says 58 instead of 45, this is consistent through all results.
Also I get an error when I try to process the GPY file. I get an invalid java checksum, I'll try the ubx file and see if I can process that, if not I'll reload the firmware and see if it works better tomorrow.
And another one, if I compare the ubx and gpy files, there is an 8 hour difference, It appears the gpy file is +16hrs although it's set to +8hrs. Although it's possible this old head is having trouble again and the gpy is at GMT
There is an issue with timezones and gpy files, Peter is working on it. The time savings should be as followed :
ubx nav pvt protocol : Every timestamp is UTC time (this is Greenwich time), all over the world
gpy : The same, timestamp should be UTC
sbp : The same, timestamp should be UTC
I all analysis software, this UTC time has to be changed to local time. This is mostly done by the settings from your (local) computer. Here is the bug, we are working on it.
There is another problem with the gpy files from the esp : @10Hz, a bad frame is sometimes written with garbage in it. Speedreader will refuse to read this, are report different dates.
Can you send me the gpy ubx file with the wrong numbers in it ?
Greetings, Jan.
There was something odd about the live speed readout in large font with 5.63. I wish I could provide more detail (I was looking where I was going!) other than it seemed about half. 2 sec 10sec Nm were normal.
Select to expand quoteFreezer said..Freezer said..K888 said..Freezer said..
I received my M10 yesterday. Will hook it up next week and see if it works and is better on accuracy and power compared to BN220 and BN280.
Cool, I presume it is the Mateksys M10-5883?
www.mateksys.com/?portfolio=M10-5883
I guess it can't be anything else based on the photos. :D
Correct, it should be plug and pray ;)
Hooked it up today, but only partially success. I should use the 5V (4.8V) rather than the VCC+ (3.9V) since the M10 requires 4-9V. It boots up and also gets a gps lock. I got up to 43 satellites. But the ublox communication is not working properly. Baudrate or string different... some more puzzling to do (and praying ??)
I received a M10 Mateksys from Freezer to figure out how to get it working on the ESP_GPS. The problem was that the M10 has totally different configuration commands. But with some patience (and the Ucenter2 sw from ublox), it is now working fine.
In comparison with the Beitian M8n, it needs less power (ca 20 mA vs 40 mA). But it seems that @10Hz and 3GNSS, lost points are common. The sAcc and nr of sats is better in comparison with the M8, so I guess that the accuracy is better.
The bright green LED on the M10 starts to blink @1Hz when there is a fix, so it is not visible @ which rate the M10 is working.
I will make a separat bin file for the M10, for who is willing to try this out.
Testfiles (gpy and txt) : drive.google.com/file/d/1GXxoRrvdi5GkaEafR-ntQffE_uyBcBNW/view?usp=sharing
A merry Christmas and a happy New Year !
Select to expand quoteremery said..
There was something odd about the live speed readout in large font with 5.63. I wish I could provide more detail (I was looking where I was going!) other than it seemed about half. 2 sec 10sec Nm were normal.
Take it for a drive in your car Rob
Hold that thought, as advised, I tested in the car, maybe it was just refresh delay.
Another day another M10 test (car drive, under the windshield) ! This time with the settings GPS + GLONAS + GALILEO @10 Hz
1 Beitian BN280 with ROM2.0 (only GPS + GLONAS)
1 Beitian BN280 with ROM3.0 (GPS + GLONAS + GALILEO)
1 Beitian BN280 with ROM3.0 (GPS + GLONAS + GALILEO)
1 Mateksys ublox M10s ROM5.10 (GPS + GLONAS + GALILEO)
Remarkable : this time no lost points for the M10 ! It seems that if Beidou is enabled, the 10Hz can not be guaranteed.
Again were the sAcc values for the M10 much better (red curves).
The BN280 with ROM2(only 2 GNSS) performs the least.
The BN280 with ROM3 (3 GNSS) are in the middle of the field.
All tests were done with gpy files, which makes file handling a lot faster ! 
There is a new SW version 5.65 with bugfixes for the gpy format, and time between stat-screens is now configurable.
github.com/RP6conrad/ESP-GPS-Logger
SW5.64
Bugfix garbage frame in gpy / ubx
Reboot ESP : ublox_off for 1s !!
Added support for ublox M10 (Mateksys maxM10s), define in Rtos.h
Time stat screen toggle configurable
bdrate back to 19200BD, should be ok for 10*100 (nav_pvt) + 10*26 bytes(nav_dop)
Added support for GNSS GPS + GALILEO + BEIDOU for M8 + M10
Correction time on sleep-screen with timezone
SW5.65
Bugfix stat screen time
Greetings, Jan.
Select to expand quoterp6conrad said..
bdrate back to 19200BD, should be ok for 10*100 (nav_pvt) + 10*26 bytes(nav_dop)
You got me there. In one of my units, I configured the chip in u-center to write NAV-SAT or NAV-SVINFO sentences, which it now does by default. Even at 5 Hz, that produces too much data for 19200 baud, so the unit is loosing lots of points after updating to 5.65. Took me a while to figure out why, it was working perfectly fine before with an older firmware version that I had modified to write NAV-SAT sentences. It would be an easy fix at home, but I did not bring the serial-to-USB cable to Oz. Maybe Decrepit has one that I can use. Would be a bummer if I have to go back to the modified 5.51 version, lots of good stuff has been added since then.
