QTFM Gen-2 Configuration Profiles

Configuration Settings Overview

Advanced users who want to script these settings address-by-address can find the EEPROM addresses for every option in the EEPROM Address Reference table near the bottom of this page.

Vector Mode: Survey vs Stable

When Vector Mode is enabled, the sensor can run its vector output in one of two measurement schemes. Toggle with decimal command 227; the choice persists across reboots and is captured by every profile (built-in and user-saveable).

The active scheme appears as #Vector Mode Type: in the boot banner and the response to decimal command 115.

What is a Configuration Profile and Why Should You Use It?

It’s a single command (a specific ASCII string like ~Vector_Survey_Pro~) that instantly loads a complete, pre-tested group of settings onto your sensor.

• Speed: It’s much faster than setting each of the 20+ parameters one by one.
• Reliability: It prevents errors or dropped commands that can happen when sending many individual settings.
• Consistency: It guarantees your sensor is configured exactly the same way for every survey, which is critical for repeatable, high-quality data.

Note: All survey and base station profiles automatically enable ‘Auto-Start’ mode. The sensor will begin measurements immediately after the profile is applied and reboots. The only exception is the ~Stop~ utility command.

Custom User-Saveable Profile Slots

Sometimes none of the built-in profiles is an exact match for how you want to run the sensor — for example you have your own preferred combination of data rate, IMU print flags, and filter that you switch back to every time. Custom user-saveable profile slots let you capture the sensor’s current configuration under any name you choose, then re-apply it any time with a single tilde command. There are three slots available.

Typical workflow

1. Get the sensor into the exact configuration you want to keep. This can be done in any way: manually applying individual settings via the QuSpin UI, starting from a built-in profile (e.g. ~Vector_Survey_Pro_MP~) and then tweaking a few values, or any combination.
2. Pick a slot number (1, 2, or 3) and a name (up to 16 ASCII characters; letters, digits, and underscores work everywhere; avoid spaces, tildes, and punctuation in the name).
3. Send ~SaveSlotN_name~. The sensor confirms with #Profile saved to slot N: 'name'. The save does not reboot the sensor — you can keep using it in its current state.
4. Any time later, send ~LoadSlotN~ — or the bare-name form ~name~, just like a built-in profile — to restore that configuration. The sensor applies all the saved settings, changes the baud rate if needed, and reboots so the new configuration takes effect cleanly.

Custom-profile commands

A slot snapshot captures the configuration settings listed in the Configuration Settings Overview table at the top of this page. Deep tuning parameters (PID gains, FPGA timing, light-level setpoints, cell / laser heater auto-time) are not captured in the slot — they live with the built-in profile that established the deep tuning.

Things to know

• Active profile is printed at boot. If the sensor’s current configuration exactly matches one of your saved slots, the boot banner (and the response to decimal command 115) includes a line like #Active user profile: 'GroundSurvey_250' (slot 1). Useful for confirming at a glance which profile is currently loaded after a power cycle. The line is silent when no slot matches (e.g. when running a built-in profile or after manually tweaking settings away from a saved snapshot).
• Names are case-sensitive in the bare-name form. ~GroundSurvey~ will not find a slot saved as ~SaveSlot1_groundsurvey~.
• Built-in names take precedence in the bare-name form. If you save a slot named Vector_Survey_Pro and then send ~Vector_Survey_Pro~, the built-in profile applies, not your slot. Use the ~LoadSlotN~ form (and pick a non-colliding name when you save) to keep things unambiguous.
• Slots persist across reboots and across firmware updates. They live in the sensor’s EEPROM. A V1_44 to later V1_xx update preserves saved slots unless we explicitly call out a layout change in the release notes.

How to Apply a Profile

You can send a profile command using any serial terminal program (e.g., the QuSpin UI, PuTTY, Tera Term). The sensor will apply all settings and then automatically reboot.

1. Find the desired Profile Name from the tables below.
2. Copy the full string, including both tildes.
3. Send the complete string to the sensor.

Recommended & High-Performance Profiles

Standard Series (115200 Baud)

Pro Series (230400 Baud, 921600 Baud)

Utility Commands

Special commands for controlling sensor state without changing survey parameters.

Direct EEPROM Address Writes V1_44+

V1_44 firmware adds a family of tilde commands that write directly to the EEPROM addresses listed in the Configuration Settings Overview table at the top of this page.

Single-address write — ~ADDR,VAL~

Writes integer VAL to EEPROM address ADDR. Accepts any address in the uC EEPROM range (0–400), so you can also poke advanced settings beyond the profile list. Confirmation print: #EEPROM[ADDR] = VAL. Floats are not supported by this shorthand — for the few float-valued addresses (laser PID gains, etc.) use the older =ADDR\r\nVAL\r\n direct-write form which still works.

Examples

• ~30,1~ — Master mode (address 30 = 1)
• ~279,4~ — Data rate 4 ms / 250 Hz output
• ~290,1~ — Enable timestamp print
• ~291,3~ — Baud rate selector to 921600 (reboot required for baud to take effect)
• ~285,1~ — 60 Hz notch filter preset

Coupled shortcuts — ~ADDR,VAL,PARAM~

A few configuration settings live across multiple coupled EEPROM addresses. Setting them one address at a time works, but the three-argument shortcuts below set the whole feature in one command.

Verify and apply — ~report~, then ~apply~ or ~Start~

~report~ prints every address listed in the EEPROM Address Reference table below along with its current EEPROM value and a short friendly label. Use it to confirm what is currently stored before applying the changes.

You have two ways to make the EEPROM changes take effect:

• ~apply~ re-reads the EEPROM into the sensor’s live runtime variables without rebooting. Most everyday settings (print flags, data rate, ZC counts, vector mode, cycle rate) take effect on the next ISR tick. The Filter coefficients (285, 293–296) are reloaded by calling Filter_startup(), and the derived float at address 354 is recomputed from address 355. Baud rate (291) is the one setting that still requires a reboot — mid-session baud change would break the serial link unless the host coordinates a simultaneous switch.
• ~Start~ enables autostart-on-power (sets address 269 = 1) and reboots the sensor. The reboot picks up every EEPROM value cleanly from cold — including baud rate — and the sensor then runs the normal autostart sequence. Use this when you are done configuring and ready to start measurements.

Typical integrator workflow

1. Send ~report~ to confirm the sensor’s current state.
2. Issue any number of ~ADDR,VAL~ or ~ADDR,VAL,PARAM~ writes for the parameters you want to change.
3. Send ~report~ again to verify the changes landed in EEPROM.
4. Send ~apply~ to push EEPROM into runtime without rebooting, or send ~Start~ to enable autostart and reboot — the sensor will pick up the new configuration from the EEPROM during startup and begin measurements.

EEPROM Address Reference

Every EEPROM address that corresponds to a setting in the Configuration Settings Overview at the top of this page. Sorted by address number. Use this table to find the right address for any ~ADDR,VAL~ or ~ADDR,VAL,PARAM~ write.

Tip: send ~report~ on a live sensor to see this same list with the current value of each address inline. Quicker than checking against this table by hand.