RTK Facet - Firmware Update - Stuck in base mode

[CharlesOR]

Hi,

I have purchased two RTK Facet units - let’s call them F1 and F2. F1 appears to work fine in Rover or Base mode - best accuracy has been 3m. F2 has failed to acquire satellites and has not been able to function in Rover or Base mode. In reviewing the support available, I updated the firmware. F1 was in Rover mode when I updated and F2 was in Base mode when I updated - their was no intention, it was just how they were left when I had last shut them off.

F1 updated fine and is sitting next to me with an accuracy of 3.09m - I am hoping if we can fix F2 then this accuracy will improve. It’s screen reads “2692”, cell icon, battery full, accuracy icon: “2.95”, and satellite icon: “23”.

F2 after update has become stuck in what appears to be base mode. The following is what I see on the screen and it’s operational limits.

Screen:

Top left corner: “0000”

Top middle: checkered flag

Top right: battery icon showing 1/2 full

Middle: “Xmitting”

Bottom: “RTCM:” followed by increasing numbers

*The RTCM count increases from 0 every time I turn off and turn the unit back on.

[attachment=0]20221026_121247[1].jpg[/attachment]

Operational limits:

I am able to turn it on and off. The unit does not allow me to switch between “Mark”, “Rover”, “Base”, “Bubble”, “Config” or “E-pair”.

I have attempted to update the firmware on this unit 3 more times. I am not seeing help articles on this particular issue. Can you please advise?

[CharlesOR]

Update: I was able to get the unit to function again by trying different firmware versions. I found that V1.6 allows the unit to function as I had received it. However, even if I switch the unit back to “Rover” or “Mark” and try to update to a newer firmware - it gets stuck again in “Base” mode. I have to revert back to V1.6 to get functionality again.

The original issue that caused me to update the firmware for F2 is still present in the V1.6 firmware as was when I received the unit. It does not acquire any satellites and therefore has a horizontal accuracy of over 30m. Using the V1.6 firmware the MAC address now shows correctly as 8B2E and I can connect via WiFi for the configuration menu.

Is my unit just bad hardware or is there a possible software fix that we can work through? The other unit I purchased F1 appears to function fine, although with less than desirable accuracy ~6m.

[toeknee]

I would try (1) removing and reformatting the SD card, (2) resetting the problematic unit to factory defaults, and (3) upgrading to v2.5 of the firmware. Perhaps there’s some stray setting that’s causing issues, and the newest firmware has fixed many issues and added features. There may be settings files on the SD card, hence the suggestion to format it. There’s also an internal little file system that stores settings, hence the suggestion to reset to factory default settings.

If that doesn’t help, perhaps there is a hardware issue; the SparkFun folks will need to help with that.

[CharlesOR]

Thank you ToeKnee. I have reformatted the SD card and also tried doing the firmware upgrade from placing the file on it. I have reset the factory settings twice. If you read in my post, I have tried to install all versions of the firmware - only 1.6 seems to allow the device to function in a way that it’s not in fixed base mode. However, no matter what firmware version I update to I cannot get it to find any satellites. I will do all of these again just to be safe.

If there is someone with hardware that can help that would be great, I have been dealing with this issue for sometime trying to figure it out on my own. I am in very serious need of the unit to work, I am behind time already with what needs to be done.

[sparky]

I don’t think you have a firmware issue. To save you as much time as possible, you have two ways forward:

1. Return the unit (https://www.sparkfun.com/returns). We’ll get it fixed up and returned to you within a day or two.

2. Continue to troubleshoot via the forum. I’m happy to help, I just worry that you’re on a restricted time schedule.

What does the display say when the device powers on?

https://cdn.sparkfun.com/assets/learn_t … On_Off.jpg

Does it say Facet or something else? Surveyor?

Does the setup button on the Facet do any action other than power on/off?

Just so I understand, you’re loading v1.6 firmware (https://github.com/sparkfun/SparkFun_RT … usVersions) from Sept of 2021 (https://github.com/sparkfun/SparkFun_RT … s/tag/v1.6)? There have been a lot of firmware changes since then but none that align with the issues you’re seeing.

If you’d like to continue troubleshooting, please connect to the COM port (https://docs.sparkfun.com/SparkFun_RTK_ … th_serial/) and report back what the unit reports during power on. The 's’ystem → 'd’ebug → 'r’eset command can be handy to force a reset and see the initial start messages.

Sorry for the hassle! This one really has me head scratching.

[CharlesOR]

These are my current startup screens.

[sparky]

I recommend you move to firmware v2.5.

Does the setup button on the Facet do any action other than power on/off?

If you’d like to continue troubleshooting, please connect to the COM port (https://docs.sparkfun.com/SparkFun_RTK_ … th_serial/) and report back what the unit reports during power on. The 's’ystem → 'd’ebug → 'r’eset command can be handy to force a reset and see the initial start messages.

[CharlesOR]

When I use v1.6 I can switch between “Mark”, “Rover”, “Base”, “Bubble”, “Config”, etc. Other versions it won’t let me do anything but turn on/off.

Here is the output during shutdown to on.

beginLoggingUBX: No date/time available. No file created.

State: Shut Down

ZED-F9P firmware: HPG 1.13

ZED-F9P firmware: HPG 1.13

SparkFun RTK Facet v1.6-Sep 20 2021

microSD online

No config file found. Using settings from EEPROM.

MAX17048 configuration complete

Batt (65%): Voltage: 3.91V Discharging: 0.00%/hr Green

GNSS configuration complete

Accelerometer configuration complete

WiFi Stopped

Bluetooth broadcasting as: Facet Rover-8B2E

State: Rover - No Fix

Batt (65%): Voltage: 3.91V Discharging: 0.00%/hr Green

beginLoggingUBX: No date/time available. No file created.

beginLoggingUBX: No date/time available. No file created.

beginLoggingUBX: No date/time available. No file created.

beginLoggingUBX: No date/time available. No file created.

beginLoggingUBX: No date/time available. No file created.

Batt (65%): Voltage: 3.91V Discharging: 0.00%/hr Green

beginLoggingUBX: No date/time available. No file created.

[CharlesOR]

I have updated to the latest firmware dated October 26 2022. The following is the firmware update log.

Ports Refreshed

Detecting flash size

esptool.py v3.3

Serial port \.\COM5

Connecting…

Device PID identification is only supported on COM and /dev/ serial ports.

.

Chip is ESP32-D0WD-V3 (revision 3)

Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None

Crystal is 40MHz

MAC: b8:d6:1a:0d:8b:2c

Uploading stub…

Running stub…

Stub running…

Manufacturer: 20

Device: 4018

Detected flash size: 16MB

Hard resetting via RTS pin…

Flash size is 16MB

Uploading firmware

Command: esptool.main(–chip esp32 --port \.\COM5 --baud 115200 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x1000 C:\Users\charl\AppData\Local\Temp_MEI81282\RTK_Surveyor.ino.bootloader.bin 0x8000 C:\Users\charl\AppData\Local\Temp_MEI81282\RTK_Surveyor_Partitions_16MB.bin 0xe000 C:\Users\charl\AppData\Local\Temp_MEI81282\boot_app0.bin 0x10000 C:/Users/charl/Downloads/RTK_Surveyor_Firmware_RC-Oct_26_2022.bin)

esptool.py v3.3

Serial port \.\COM5

Connecting…

Device PID identification is only supported on COM and /dev/ serial ports.

…

Chip is ESP32-D0WD-V3 (revision 3)

Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None

Crystal is 40MHz

MAC: b8:d6:1a:0d:8b:2c

Uploading stub…

Running stub…

Stub running…

Configuring flash size…

Auto-detected Flash size: 16MB

Flash will be erased from 0x00001000 to 0x00005fff…

Flash will be erased from 0x00008000 to 0x00008fff…

Flash will be erased from 0x0000e000 to 0x0000ffff…

Flash will be erased from 0x00010000 to 0x00224fff…

Flash params set to 0x024f

Compressed 17984 bytes to 12318…

Wrote 17984 bytes (12318 compressed) at 0x00001000 in 1.4 seconds (effective 105.9 kbit/s)…

Hash of data verified.

Compressed 3072 bytes to 129…

Wrote 3072 bytes (129 compressed) at 0x00008000 in 0.1 seconds (effective 386.6 kbit/s)…

Hash of data verified.

Compressed 8192 bytes to 47…

Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 600.9 kbit/s)…

Hash of data verified.

Compressed 2181184 bytes to 1340934…

Wrote 2181184 bytes (1340934 compressed) at 0x00010000 in 118.4 seconds (effective 147.3 kbit/s)…

Hash of data verified.

Leaving…

Hard resetting via RTS pin…

[CharlesOR]

After updating firmware this is what I see in Tera Term.

No GNSS date/time available for system RTC.

No GNSS date/time available for system RTC.

No GNSS date/time available for system RTC.

Batt (65%): Voltage: 3.91V Discharging: 0.00%/hr Green

No GNSS date/time available for system RTC.

No GNSS date/time available for system RTC.

SparkFun RTK Facet v2.6-RC-Oct 26 2022

** Bluetooth broadcasting as: **

Menu: Main

1. Configure GNSS Receiver

2. Configure GNSS Messages

3. Configure Base

4. Configure Ports

5. Configure Logging

p) Configure User Profiles

r) Configure Radios

s) Configure System

x) Exit

5

Menu: Logging

microSD card is online

Buffer overruns: 0

1. Log to microSD: Enabled

2. Set max logging time: 1440 minutes

3. Set max log length: 1440 minutes

4. Write Marks_date.csv file to microSD: Disabled

x) Exit

x

SparkFun RTK Facet v2.6-RC-Oct 26 2022

** Bluetooth broadcasting as: **

Menu: Main

1. Configure GNSS Receiver

2. Configure GNSS Messages

3. Configure Base

4. Configure Ports

5. Configure Logging

p) Configure User Profiles

r) Configure Radios

s) Configure System

x) Exit

[CharlesOR]

Here is the Shutdown with turn on log from Tera Term.

State: Shut Down

microSD: Offline

ÿZED-F9P firmware: HPG 1.13

LittleFS Started

[ 347][D][esp32-hal-adc.c:210] __analogReadMilliVolts(): eFuse Vref: Supported

[ 347][esp32-hal-adc.c:240] __analogReadMilliVolts(): ADC1: Characterized using eFuse Vref: 1086
[ 354][D][Begin.ino:10] beginBoard(): Board ADC ID: 1654
SparkFun RTK Facet v2.6-Oct 26 2022
[ 904][D][NVM.ino:1076] loadProfileNumber(): Using profile #0
[ 1132][D][Begin.ino:242] beginSD(): SD card detected
microSD: Online
[ 1324][D][NVM.ino:386] loadSystemSettingsFromFileSD(): File /SFE_Facet_Settings_0.txt not found
[ 1344][D][NVM.ino:111] recordSystemSettingsToFileSD(): Settings recorded to SD: /SFE_Facet_Settings_0.txt
[ 1367][D][NVM.ino:141] recordSystemSettingsToFileLFS(): Removing LittleFS: /SFE_Facet_Settings_0.txt
[ 1511][D][NVM.ino:153] recordSystemSettingsToFileLFS(): Settings recorded to LittleFS: /SFE_Facet_Settings_0.txt
[ 1696][D][NVM.ino:386] loadSystemSettingsFromFileSD(): File /SFE_Facet_Settings_0.txt not found
[ 1701][E][vfs_api.cpp:102] open(): /littlefs/SFE_Facet_Settings_1.txt does not exist, no permits for creation
[ 1703][D][NVM.ino:386] loadSystemSettingsFromFileSD(): File /SFE_Facet_Settings_1.txt not found
[ 1716][E][vfs_api.cpp:102] open(): /littlefs/SFE_Facet_Settings_2.txt does not exist, no permits for creation
[ 1721][D][NVM.ino:386] loadSystemSettingsFromFileSD(): File /SFE_Facet_Settings_2.txt not found
[ 1735][E][vfs_api.cpp:102] open(): /littlefs/SFE_Facet_Settings_3.txt does not exist, no permits for creation
[ 1740][D][NVM.ino:386] loadSystemSettingsFromFileSD(): File /SFE_Facet_Settings_3.txt not found
[ 1753][E][vfs_api.cpp:102] open(): /littlefs/SFE_Facet_Settings_4.txt does not exist, no permits for creation
[ 1758][D][NVM.ino:386] loadSystemSettingsFromFileSD(): File /SFE_Facet_Settings_4.txt not found
[ 1771][E][vfs_api.cpp:102] open(): /littlefs/SFE_Facet_Settings_5.txt does not exist, no permits for creation
[ 1777][D][NVM.ino:386] loadSystemSettingsFromFileSD(): File /SFE_Facet_Settings_5.txt not found
[ 1790][E][vfs_api.cpp:102] open(): /littlefs/SFE_Facet_Settings_6.txt does not exist, no permits for creation
[ 1795][D][NVM.ino:386] loadSystemSettingsFromFileSD(): File /SFE_Facet_Settings_6.txt not found
[ 1808][E][vfs_api.cpp:102] open(): /littlefs/SFE_Facet_Settings_7.txt does not exist, no permits for creation
[ 1813][D][NVM.ino:386] loadSystemSettingsFromFileSD(): File /SFE_Facet_Settings_7.txt not found
Profile ‘Profile1’ loaded
MAX17048 configuration complete
Batt (65%): Voltage: 3.91V Discharging: 0.00%/hr Green
GNSS configuration complete
Accelerometer configuration complete
[ 3504][D][menuPP.ino:844] beginLBand(): L-Band not detected
No GNSS date/time available for system RTC.
[ 3628][D][RTK_Surveyor.ino:607] setup(): Boot time: 3628
No GNSS date/time available for system RTC.
Batt (65%): Voltage: 3.91V Discharging: 0.00%/hr Green
No GNSS date/time available for system RTC.
No GNSS date/time available for system RTC.
No GNSS date/time available for system RTC.

[CharlesOR]

After updating firmware, this is the display I get. I can only turn it on/off, no other functions available.

[sparky]

Thanks. Please load v2.5 firmware, not the release candidate firmware as it’s not recommended for production. Please report back what the unit reports during power on.

[sparky]

For more info please enter the 's’ystem menu and report back the contents.

I am beginning to think there is a hardware failure. I cannot explain why the Bluetooth MAC address is coming back as all zeros.

[CharlesOR]

Here is the update for Firmware v2.5

Detecting flash size

esptool.py v3.3

Serial port \.\COM5

Connecting…

Device PID identification is only supported on COM and /dev/ serial ports.

.

Chip is ESP32-D0WD-V3 (revision 3)

Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None

Crystal is 40MHz

MAC: b8:d6:1a:0d:8b:2c

Uploading stub…

Running stub…

Stub running…

Manufacturer: 20

Device: 4018

Detected flash size: 16MB

Hard resetting via RTS pin…

Flash size is 16MB

Uploading firmware

Command: esptool.main(–chip esp32 --port \.\COM5 --baud 115200 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x1000 C:\Users\charl\AppData\Local\Temp_MEI146442\RTK_Surveyor.ino.bootloader.bin 0x8000 C:\Users\charl\AppData\Local\Temp_MEI146442\RTK_Surveyor_Partitions_16MB.bin 0xe000 C:\Users\charl\AppData\Local\Temp_MEI146442\boot_app0.bin 0x10000 C:/Users/charl/Downloads/RTK_Surveyor_Firmware_v2_5.bin)

esptool.py v3.3

Serial port \.\COM5

Connecting…

Device PID identification is only supported on COM and /dev/ serial ports.

…

Chip is ESP32-D0WD-V3 (revision 3)

Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None

Crystal is 40MHz

MAC: b8:d6:1a:0d:8b:2c

Uploading stub…

Running stub…

Stub running…

Configuring flash size…

Auto-detected Flash size: 16MB

Flash will be erased from 0x00001000 to 0x00005fff…

Flash will be erased from 0x00008000 to 0x00008fff…

Flash will be erased from 0x0000e000 to 0x0000ffff…

Flash will be erased from 0x00010000 to 0x0022ffff…

Flash params set to 0x024f

Compressed 17984 bytes to 12318…

Wrote 17984 bytes (12318 compressed) at 0x00001000 in 1.4 seconds (effective 105.2 kbit/s)…

Hash of data verified.

Compressed 3072 bytes to 129…

Wrote 3072 bytes (129 compressed) at 0x00008000 in 0.1 seconds (effective 373.2 kbit/s)…

Hash of data verified.

Compressed 8192 bytes to 47…

Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 573.3 kbit/s)…

Hash of data verified.

Compressed 2225008 bytes to 1380429…

Wrote 2225008 bytes (1380429 compressed) at 0x00010000 in 122.1 seconds (effective 145.8 kbit/s)…

Hash of data verified.

Leaving…

Hard resetting via RTS pin…

[CharlesOR]

The units screen on startup with firmware 2.5. I can only turn on and off, no other functionality.

[CharlesOR]

While plugged into the serial port and running Tera Term I was NOT able to shut-down manually using the units “Power Setup” button, I had to shutdown using the terminal shutdown command “S> Shut down”. The output of the shutdown and start up are below:

Menu: System Menu

GNSS: Online - ZED-F9P firmware: HPG 1.13

SIV: 0, HPA (m): 429496.719, Lat: 0.00000000, Lon: 0.00000000, Altitude (m): 0.0

Display: Online

Accelerometer: Online

Fuel Gauge: Online - Batt (64%) / Voltage: 3.91V

microSD: Online

Bluetooth (8B2E): Online

WiFi MAC Address: B8:D6:1A:0D:8B:2C

System Uptime: 0 00:03:27.131 (Resets: 0)

f) Display microSD Files

d) Configure Debug

z) Set time zone offset: 00:00:00

b) Set Bluetooth Mode: Classic

c) Enable/disable WiFi NMEA client (connect to phone): Disabled

n) Enable/disable WiFi NMEA server: Disabled

r) Reset all settings to default

B) Switch to Base mode

R) Switch to Rover mode

W) Switch to WiFi Config mode

S) Shut down

x) Exit

Shutting down…

microSD: Offline

Display started

ZED-F9P firmware: HPG 1.13

LittleFS Started

Display started

ZED-F9P firmware: HPG 1.13

LittleFS Started

SparkFun RTK Facet v2.5-Sep 21 2022

microSD: Online

Profile ‘Profile1’ loaded

MAX17048 configuration complete

Batt (64%): Voltage: 3.91V Discharging: 0.00%/hr Green

GNSS configuration complete

Accelerometer configuration complete

No GNSS date/time available for system RTC.

No GNSS date/time available for system RTC.

Batt (64%): Voltage: 3.91V Discharging: 0.00%/hr Green

No GNSS date/time available for system RTC.

No GNSS date/time available for system RTC.

[CharlesOR]

This is the unit display using v2.5 and plugged into serial with Tera Term. I am unable to turn unit on or off using “Power Setup” button. I have tried short presses and long presses for the button, it does nothing. I have to use the “shutdown” on the menu in Tera Term.

[CharlesOR]

sparky:
For more info please enter the 's’ystem menu and report back the contents.

I am beginning to think there is a hardware failure. I cannot explain why the Bluetooth MAC address is coming back as all zeros.

It only comes up 0000 when I use any other firmware than v1.6. v1.6 reports it back fine as the correct mac address.

Menu: System Menu

GNSS: Online - ZED-F9P firmware: HPG 1.13

SIV: 0, HPA (m): 429496.719, Lat: 0.00000000, Lon: 0.00000000, Altitude (m): 0.0

Display: Online

Accelerometer: Online

Fuel Gauge: Online - Batt (64%) / Voltage: 3.91V

microSD: Online

Bluetooth (8B2E): Online

WiFi MAC Address: B8:D6:1A:0D:8B:2C

System Uptime: 0 00:06:00.151 (Resets: 0)

f) Display microSD Files

d) Configure Debug

z) Set time zone offset: 00:00:00

b) Set Bluetooth Mode: Classic

c) Enable/disable WiFi NMEA client (connect to phone): Disabled

n) Enable/disable WiFi NMEA server: Disabled

r) Reset all settings to default

B) Switch to Base mode

R) Switch to Rover mode

W) Switch to WiFi Config mode

S) Shut down

x) Exit

[CharlesOR]

Is there anyone at SparkFun that knows how the Facet works or someone that knows how to fix the dysfunctional unit you sent me?

This is the worst technical support experience. No number, no experinced techie support persons, just some random forum that people comment on.

This is my first experience with your company and it’s a really shifty one. I was excited by the hype from your videos on how easy the Facet would be to use. So far I have a brick and second unit with greater than 6’ accuracy. The claim of mm accuracy is bullshit and your equipment is crap at this point.

On top of that, your customer service department is no help. They want me to return the unit and wait until someone “repairs” it, which from my experience so far will likely take a month. Who knows if I’ll actually see mm accuracy with two. I’m very skeptical.