Save mobile device profile preferences to the LoRa device (presumably based on the MAC of the BT chip)

vaderj · May 25, 2020, 4:28am

I was just thinking that as the project matures, it may be useful to start being able to save some kind of configuration template or profile. This is assuming that there will eventually be configuration options, and for testing multiple types of devices it will certainly ease things.

Perhaps these settings can be saved to the ESP32 at some point? And then exported via XML, CSV, etc from the mobile app?

geeksville · May 25, 2020, 4:40am

Totally agree. And in some ways much of that is already implemented on the device side - just no GUI for it yet in the app.

The device keeps a “RadioConfig” object inside its flash filesystem, and sends it to the phone. The phone can any time it wants squirt down a new RadioConfig. RadioConfig contains both “UserPreferences” - general settings and “ChannelSettings” - the information for the Channel pane.

It is pretty painless to add new things to UserPreferences, just add the entry in the .proto file and then run “bin/regen-protos.sh” to regenerate the C code for reading/writing that stuff.

For testing multiple configs I really prefer the python “meshtastic” command rather than the android app - because though no gui, you can read/write/save any of the current settings (and it learns automatically from the protobuf file - so no code needs to be added to it to support new settings).

Some ‘okay’ documentation on these highlighted lines:

github.com

meshtastic/Meshtastic-protobufs/blob/master/mesh.proto#L357-L444


// Full settings (center freq, spread factor, pre-shared secret key etc...)
// needed to configure a radio for speaking on a particlar channel This
// information can be encoded as a QRcode/url so that other users can configure
// their radio to join the same channel.
message ChannelSettings {
  int32 tx_power = 1;

  // We now select channel number by hashing the name of the channel.  We do
  // this on the device and it is opaque to the phone.  Therefore no need to
  // show this in channel settings uint32 channel_num = 2;

  enum ModemConfig {
    // Note: these mappings must match ModemConfigChoice in the device code.
    Bw125Cr45Sf128 = 0;   ///< Bw = 125 kHz, Cr = 4/5, Sf = 128chips/symbol, CRC
                          ///< on. Default medium range
    Bw500Cr45Sf128 = 1;   ///< Bw = 500 kHz, Cr = 4/5, Sf = 128chips/symbol, CRC
                          ///< on. Fast+short range
    Bw31_25Cr48Sf512 = 2; ///< Bw = 31.25 kHz, Cr = 4/8, Sf = 512chips/symbol,
                          ///< CRC on. Slow+long range
    Bw125Cr48Sf4096 = 3; ///< Bw = 125 kHz, Cr = 4/8, Sf = 4096chips/symbol, CRC

This file has been truncated. show original

Topic		Replies	Views
Device profiles in app? Android	3	537	October 24, 2020
Anyone want to try custom channel settings? Python API	39	2360	March 18, 2021
Network configuration with Serial Plug-In Development	0	450	April 20, 2021
BT + LoRa mesh - the people's comms Development	3	537	January 23, 2023
Relationship between channels and frequency/SF? Support	3	1496	August 10, 2020

Save mobile device profile preferences to the LoRa device (presumably based on the MAC of the BT chip)

Related Topics