fix uBlox M8N detection

[brunotl]

Ublox Neo M8N "UBX-MON-VER" payload size is 250, don't fit inside GNSSbuf[240].

• update ubloxProcessData for truncate received data instead of discard all.
• add extended version info to boot log

boot log :

19:56:50.272 -> Reset reason: 0
19:56:50.272 -> POWERON_RESET
19:56:50.272 -> Free heap size: 203820
19:56:50.272 -> Vbat power on reset
19:56:50.272 ->
19:56:50.272 -> EEPROM version: 93
19:56:50.272 -> SX1276 RFIC is detected.
19:56:50.412 -> WARNING! Barometric pressure sensor is NOT detected.
19:56:50.412 -> INFO: TTGO T-Beam GPS module (rev. 05) is detected.
19:56:50.412 -> Flash memory ID: EF4016
19:56:50.833 -> INFO: GNSS module HW version: 00080000
19:56:50.833 -> INFO: GNSS module FW version: EXT CORE 3.01 (107900)
19:56:50.833 -> INFO: GNSS module extension: ROM BASE 3.01 (107888)
19:56:50.833 -> INFO: GNSS module extension: FWVER=SPG 3.01
19:56:50.833 -> INFO: GNSS module extension: PROTVER=18.00
19:56:50.833 -> INFO: GNSS module extension: MOD=NEO-M8N-0
19:56:50.833 -> INFO: GNSS module extension: FIS=0xEF4015 (200037)
19:56:50.833 -> INFO: GNSS module extension: GPS;GLO;GAL;BDS
19:56:50.833 -> INFO: GNSS module extension: SBAS;IMES;QZSS
19:56:51.208 -> Hostname: SoftRF-b99fcc
19:56:51.208 -> Wait for WiFi connection.
19:56:51.208 -> ....................
19:57:01.223 -> Can not connect to WiFi station. Go into AP mode.
19:57:01.270 -> Setting soft-AP configuration ... Ready
19:57:01.270 -> Setting soft-AP ... Ready
19:57:01.270 -> IP address: 192.168.1.1
19:57:01.270 -> UDP server has started at port: 12389
19:57:02.627 -> HTTP server has started at port: 80

[lyusupov]

1. what is the issue # this PR is intended to fix ?

2. reproducing instructiions ?

I have plenty of different Ublox G6, G7 and G8 modules.
Three of them are G8s with different firmware revisions. They all three were doing fine last time I've validated them (in fall '18)

I am not going to give this PR a go if I will not be able to validate your report with the hardware I have.

3. Ublox gen. Id has no noticeable effect for current SoftRF firmware behavior except:

• WebUI status page ;
• some NMEA filtering and G-factor applied

4. The GNSSHelper.cpp file is in use by all the hardware platforms supported. Including low RAM and flash memory ones, such as Ti's CC1310.
   'Debug print' sections of this PR has no chance to applied at all due to limited space constraints of this hardware.

[brunotl]

2. device used is "Wemos® TTGO T-Beam with NEO-M8N GPS module"

   • in WebUI, GNSS module shown is "NMEA"
   • legacy NMEA feeds over Bluetooth LE is corrupted ( too much data )

3. agree, WebUI is not a noticeable effect, and can be ignored, but failed to apply NMEA filtering can't be ignored, because that broke the NMEA output using BTH LE.
   In fact the PR is more a workaround than a fix, alike one you did for issues garbage in GPS data #1
   the real problem can be in "ESP_Bluetooth_loop" or "ESP32_Bluetooth_write" if too much are sent, some of them are discarded...

4. agree, that only a debug facility and can be removed or disable using "#ifdef DO_GNSS_DEBUG", as you prefert

[brunotl]

additional info :

After reading M8 firmware 3.01 release note, it's seem's only M8 with this new firmware could be concerned.

cf section 4.1 of this documents :
https://www.u-blox.com/sites/default/files/GNSS-FW3.01_ReleaseNotes_%28UBX-16000319%29_Public.pdf

with this release UBX-MON-VER payload include 1 more line, so it's size is now 250 byte ( 220 byte with firmware 2.01 )

[lyusupov]

I don't have version of the T-Beam with NEO-8 readily available here.
So processing of this PR will be postponed until I'll get it.

Throughput of BTLE on ESP32 in 'serial emulation' mode is actually really slow.
I mostly consider this option as a 'demo', rather than true, mature feature.
Even if no extra GNSS NMEA sentences being delivered - BTLE flow is becoming broken anyway when the unit is receiving signal from 4-5+ Legacy/OGN/PAW/FANET traffic (which causes 4+ $PFLAA sentences emission).
I recommend users to avoid use of BTLE when able and deal with 'classic' SPP instead.

Please, remove all the space consuming 'fat' from your PR and keep only the 'beef'.
When I'll be able to evaluate T-Beam/NEO8 board and will see that the issue is confirmed - I will return to processing of your PR.

Resolution: deferred.

P.S. What's up with Paolo ? Is he doing well ?
I don't see his activity on GitHub since February last year: https://github.com/pventafridda

[lyusupov]

Date when I will be able to validate the issue on T-Beam/NEO8 board is uncertain.
This could take as long as 6 months.

They manufacture the boards in batches. Each particular batch can be sourced from different parts distributor. So particular revision of firmware may vary from batch to batch.

Some of G8 modules that I have are using 3.x firmware version.
All of them are having ROM based firmware code:

pi@raspberrypi:/run/tmp/SoftRF/SoftRF $ sudo ./SoftRF
NRF905 RFIC is detected.
ubloxExpectedDataLength = 160
INFO: GNSS module HW version: 00080000
INFO: GNSS module FW version: ROM CORE 3.01 (107888)

As you may see, your reported issue is not reproduced on such 3.x revision(s).

My proposal to you is:
could you provide temporary remote access for me to your T-Beam board with use of VirtualHere ?

[brunotl]

ok, i need few days for that, when it's ready i send the connection setting by mail ...