Here is the purpose of adding the settings mentioned in kial
All ATrack devices have a configurable position message format. Such a configuration can be set and requested by the AT$FORM=... command. The ATrack AK11 devices have additional configuration params related to CAN data: AT$FMSC and AT$1708.
So, the platform needs to know such configuration params set on the device to correctly parse all incoming packets from it.
Previously we were sending AT$FORM, AT$FMSC, and AT$1708 requests on every TCP connection after successful ATrack device login.
But most of the ATrack devices have static AT$FORM, AT$FMSC and AT$1708 configuration - users usually set it on the device once, and change it not too often. So we decided to cache such a configuration if the user has a corresponding flespi device instance.
That change resulted in the following:
- the flespi platform will ask the tracking device for such a configuration only once and will no more waste device's traffic asking it on every connection
- users got a REST API and a handy UI to see, change, or cleanup cached configuration in the flespi device instance at the Settings tab (or using SetBox tool)
- when users change AT$FORM, AT$FMSC, or AT$1708 configuration format not through the flespi device instance (or SetBox) but through SMS or USB - they should clean up the cached configuration value in the flespi device instance, so the configuration request will be sent on the next device connection