Hi, I am trying to figure out how to log RINEX files to the SD card on the FPM. I am using a 32 gb SDHC class 10 card formatted to FAT32. I am able to see log files recorded from the sparkpnt firmware, but the septentrio board is not able to mount to the sd card to record Rinex, or SBF files. I can log into the Septentrio browser via usb and navigate to the logging page where I should be able to mount/unmount an SD card. When I click on Mount or Format, I get an error. When using a terminal to configure the sparkpnt device settings, under the logging menu I see options to log to the “accessible” sd card and the “internal” sd card. I enabled both, and enabled Rinex logging, but am only getting a gnss txt file log. I would love to be able to log SBF or RINEX directly to the device. A wild theory I had was that the internal mosaic board may have a second sd card slot, but the photos and schematics I found online don’t show anything that led me to open up the FPM myself.
Hi @CHENAGAR ,
Welcome!
I think you are the first person to ask this question… And may be the first customer trying to use the internal SD slot. I will take an action to add the internal slot to the docs.
The internal SD slot is on the underside of the main Facet FP PCB:
We don’t install a card in it by default as only the mosaic-X5 is able to access it.
With some careful disassembly, you can install the card yourself. Please let us know if you would like help with that.
Humm… The SparkPNT Facet FP docs are very new and still under construction. I can’t actually find the main board schematic on there at the moment. I will take an action to add that too.
Best wishes,
Paul
Ah, very good! Thanks for such a quick response.
I’m trying to figure out also how to log RINEX files. Do I understand correctly that the only way to do it is to open the device and put an SD card to the internal slot? Logging the RINEX data to the slot that is accessible under the device is not possible?
I want to collect data for sending it to CSRS for PPP processing to get the exact location.
Hi @Samufun ,
This thread is a discussion about logging RINEX data to the internal SD card on Facet FPM. I.e. a Facet FP which uses the mosaic-X5 GNSS.
The mosaic-X5 is able to log RINEX format data directly - to the internal SD card which is connected directly to the X5.
I think you have the Facet FPL? That model uses the LG290P which does not support RINEX logging directly.
You can still log data and have it processed by CSRS for PPP. But you need to log RTCM3 data - to the external accessible SD card via the ESP32. There is a long discussion about which messages to enable in this thread.
For you, working through the RTK Everywhere menus and message rates, you need to:
Disable NMEA RMC, GSV, GSA, VTG and GLL. Set their message rates to zero.
You can leave NMEA GGA enabled if you wish.
Enable RTCM3 1019, 1020, 1041, 1046, 107X, 108X, 109X, 112X.
I suggest message intervals of: 1 second for 107X, 108X, 109X and 112X; 5 seconds for 1019, 1020, 1041 and 1046.
Then use RTKLIB (RTKCONV) to convert the RTCM3 to RINEX before you submit it to CSRS.
PyGPSClient can also convert data to RINEX format. This is a new feature and it (probably) won’t be as complete as RTKLIB. But it is another option for you. Details are here.
I hope this helps,
Paul
I have been able to get the correct data with my FPL, and convert it to RINEX, and get it processed at CSRS.
I also just got an FPMT and of course I became curious to check how close their results are going to be. I went through all the config menus of FPMT but couldn’t figure out how to either get the right RTCM data or RINEX directly. Apparently the problem was that my SD card was in the wrong slot.
Hi @Samufun ,
Apologies. I wasn’t aware that you also had the Facet FPMT.
OK. If you want to log RINEX directly, then, yes, you will need to open up the Facet and install the extra internal SD card. Please let us know if you need instructions on how to do that. We don’t have a photo guide on how to do that - yet. Clearly it is something we should add soon.
If you are happy logging RTCM3 to the accessible SD card, and converting to RINEX, here are the settings:
With RTK Everywhere 3.3
Starting with the FPMT after a factory reset (menu options: s r y)
It takes time for the mosaic to be detected (it takes around 8 seconds for it to boot up)
From the Main Menu, select option 2 “Configure GNSS Messages”
From Menu GNSS Messages, select option 1 “Set NMEA Messages”
On mosaic-X5, you can assign each NMEA message to a stream: Stream1, Stream2, or Off
By default, Stream1 has an interval of 500ms, and Stream2 has an interval of 1s
Set RMC, GSV, GSA, VTG and GLL to “Off”
Set GGA to Stream2
When you are done, it will look like this:
SparkPNT FPMT v3.3
Mode: Rover
** Bluetooth SPP and BLE broadcasting as: SparkPNT FPMT-9BB606 **
Menu: Main
1) Configure GNSS Receiver
2) Configure GNSS Messages
3) Configure Base
4) Configure Ports
5) Configure Logging
6) Configure WiFi
7) Configure TCP/UDP
f) Firmware Update
i) Configure Corrections Priorities
p) Configure PointPerfect
r) Configure Radios
s) Configure System
t) Configure Instrument Setup
u) Configure User Profiles
+) Enter Command line mode
x) Exit
2
Menu: GNSS Messages
Active messages: 5
1) Set NMEA Messages
2) Set Rover RTCM Messages
3) Set Base RTCM Messages
10) Reset to Defaults
x) Exit
1
Menu: Message NMEA
1) Message ALM : Off
2) Message AVR : Off
3) Message DTM : Off
4) Message GBS : Off
5) Message GFA : Off
6) Message GGA : Stream2
7) Message GGK : Off
8) Message GGQ : Off
9) Message GLL : Off
10) Message GMP : Off
11) Message GNS : Off
12) Message GRS : Off
13) Message GSA : Off
14) Message GST : Off
15) Message GSV : Off
16) Message HDT : Off
17) Message HRP : Off
18) Message LLK : Off
19) Message LLQ : Off
20) Message RBD : Off
21) Message RBP : Off
22) Message RBV : Off
23) Message RMC : Off
24) Message ROT : Off
25) Message SNC : Off
26) Message TFM : Off
27) Message THS : Off
28) Message TXTbase : Off
29) Message VTG : Off
30) Message ZDA : Off
31) Stream1 : Interval 500ms
32) Stream2 : Interval 1s
x) Exit
Exit the NMEA menu
Select option 2 “Set Rover RTCM Messages”
Each RTCM message group has an interval
The MSM messages contain the pseudoranges, phaseranges and CNR
MSM4 is 1074, 1084, 1094 and 1124 combined
If you need more resolution, you can log MSM7 (1077, 1087, 1097, 1127) instead of MSM4
1019 is the GPS Ephemerides
1020 is the GLONASS Ephemerides
The mosaic-X5 does not support 1041 - the NavIC Ephemeris message
But it does support 1042 - the BDS (BeiDou) Ephemeris data
1046 is the Galileo I/NAV Ephemeris data
MSM4 has an interval of 1s by default
You can set the interval of 1019, 1020, 1042 and 1046 to 5.0 seconds
When you are done, it will look like this:
SparkPNT FPMT v3.3
Mode: Rover
** Bluetooth SPP and BLE broadcasting as: SparkPNT FPMT-9BB606 **
Menu: Main
1) Configure GNSS Receiver
2) Configure GNSS Messages
3) Configure Base
4) Configure Ports
5) Configure Logging
6) Configure WiFi
7) Configure TCP/UDP
f) Firmware Update
i) Configure Corrections Priorities
p) Configure PointPerfect
r) Configure Radios
s) Configure System
t) Configure Instrument Setup
u) Configure User Profiles
+) Enter Command line mode
x) Exit
2
Menu: GNSS Messages
Active messages: 6
1) Set NMEA Messages
2) Set Rover RTCM Messages
3) Set Base RTCM Messages
10) Reset to Defaults
x) Exit
2
Menu: Message RTCM Rover
1) Message Group RTCM1001|2: Interval 1.0
2) Message Group RTCM1003|4: Interval 1.0
3) Message Group RTCM1005|6: Interval 1.0
4) Message Group RTCM1007|8: Interval 1.0
5) Message Group RTCM1009|10: Interval 1.0
6) Message Group RTCM1011|12: Interval 1.0
7) Message Group RTCM1013: Interval 1.0
8) Message Group RTCM1019: Interval 5.0
9) Message Group RTCM1020: Interval 5.0
10) Message Group RTCM1029: Interval 1.0
11) Message Group RTCM1033: Interval 10.0
12) Message Group RTCM1042: Interval 5.0
13) Message Group RTCM1044: Interval 1.0
14) Message Group RTCM1045: Interval 1.0
15) Message Group RTCM1046: Interval 5.0
16) Message Group MSM1: Interval 1.0
17) Message Group MSM2: Interval 1.0
18) Message Group MSM3: Interval 1.0
19) Message Group MSM4: Interval 1.0
20) Message Group MSM5: Interval 1.0
21) Message Group MSM6: Interval 1.0
22) Message Group MSM7: Interval 1.0
23) Message Group RTCM1230: Interval 1.0
24) Message RTCM1001: Disabled
25) Message RTCM1002: Disabled
26) Message RTCM1003: Disabled
27) Message RTCM1004: Disabled
28) Message RTCM1005: Disabled
29) Message RTCM1006: Disabled
30) Message RTCM1007: Disabled
31) Message RTCM1008: Disabled
32) Message RTCM1009: Disabled
33) Message RTCM1010: Disabled
34) Message RTCM1011: Disabled
35) Message RTCM1012: Disabled
36) Message RTCM1013: Disabled
37) Message RTCM1019: Enabled
38) Message RTCM1020: Enabled
39) Message RTCM1029: Disabled
40) Message RTCM1033: Disabled
41) Message RTCM1042: Enabled
42) Message RTCM1044: Disabled
43) Message RTCM1045: Disabled
44) Message RTCM1046: Enabled
45) Message MSM1: Disabled
46) Message MSM2: Disabled
47) Message MSM3: Disabled
48) Message MSM4: Enabled
49) Message MSM5: Disabled
50) Message MSM6: Disabled
51) Message MSM7: Disabled
52) Message RTCM1230: Disabled
x) Exit
Exit the menus to save the changes and update the GNSS message rates
If you want to start a new log file:
From the Main Menu select option 5 “Configure Logging”
Select option 1 “Accessible microSD logging”
Select option 4 “Start new log”
By default, the logging will stop after 1440 minutes (24 hours)
If you want to, you can set option 3 “Set max log length” to 60, then a new log file will be generated every hour
You can set option 2 “Set max logging time” to zero and it will keep logging forever
Always fully exit the menus to save the changes
I am running a test on Facet FPMT now using the above settings. I will report back once I have collected the data and had it processed by CSRS.
I hope this helps,
Paul
Hi @Samufun ,
Apologies. We have a problem. The log file my Facet FPMT created only contains NMEA. No RTCM3… I have opened an issue for this and will start working on it today.
Best wishes,
Paul
Thank you for the quick fix! I did a short test with the new firmware, looks like I’m getting the correct RTCM data. I also opened the device to see where the additional SD card slot is. The location is not very convenient but it works for RINEX logging.