MultiTech / Mbed OS Dot-AT-Firmware

AT command firmware for MultiTech Dot devices.

Fork of mDot_AT_firmware by MultiTech

Dot Library Not Included!

Because these example programs can be used for both mDot and xDot devices, the LoRa stack is not included. The libmDot library should be imported if building for mDot devices. The libxDot library should be imported if building for xDot devices. The AT firmware was last tested with mbed-os-5.4.7. Using a version past mbed-os-5.4.7 will cause the build to fail. The library used with the AT firmware has to match the mbed-os version.

Dot Library Version 3 Updates

Dot Library versions 3.x.x require a channel plan to be injected into the stack. The Dot-Examples and Dot-AT-Firmware do this by defining a macro called "CHANNEL_PLAN" that controls the channel plan that will be used in the examples. Available channel plans will be in the Dot Library repository in the plans folder.

Revision 20 and earlier of Dot-Examples and revision 15 and earlier of Dot-AT-Firmware should be used with Dot Library versions prior to 3.0.0.

Fota Library

Th Fota Library must be added to compile for mDot 3.1.0 with Fota support. Latest dev libraries and 3.2.0 release will include Fota with libmDot/libxDot.

AT Firmware Description

This AT Firmware is what ships on mDot and xDot devices. It provides an AT command interface for using the mDot or xDot for LoRa communication.

AT command documentation can be found on Multitech.com.

The firmware changelog can be found here. The library changelog can be found here.

Dot Libraries

Dot Library Limitations

The commit messages in libmDot-mbed5 and libmDot-dev-mbed5 specify the version of the Dot library the commit contains and the version of mbed-os it was compiled against. We recommend building your application with the version of mbed-os specified in the commit message of the version of the Dot library you're using. This will ensure that you don't run into any runtime issues caused by differences in the mbed-os versions.

Stable and development libraries are available for both mDot and xDot platforms. The library chosen must match the target platform. Compiling for the mDot platform with the xDot library or vice versa will not succeed.

mDot Library

Development library for mDot.

libmDot-dev

Stable library for mDot.

libmDot

xDot Library

Development library for xDot.

libxDot-dev

Stable library for xDot.

libxDot

CommandTerminal/CmdCustomSerialNumber.cpp@42:23e2df6714f4, 5 months ago (annotated)

Committer:
Jason Reiss
Date:
Wed Dec 06 13:33:52 2023 -0600
Revision:
42:23e2df6714f4
Parent:
36:b586cd6e91f3 
TestMode: reset appnonce to 0 on reset to accomodate LCTT 3.12.0 and earlier. If the test suite changes to test AppNonce loaded from NVM this will fail tests.

Who changed what in which revision?

UserRevisionLine numberNew contents of line
Jason Reiss 36:b586cd6e91f3 1 #include "CmdCustomSerialNumber.h"
Jason Reiss 36:b586cd6e91f3 2
Jason Reiss 36:b586cd6e91f3 3 CmdCustomSerialNumber::CmdCustomSerialNumber() :
Jason Reiss 36:b586cd6e91f3 4 #if MTS_CMD_TERM_VERBOSE
Jason Reiss 36:b586cd6e91f3 5 Command("Custom Serial Number", "AT+CSN", "Configure custom serial number", "(string:16)")
Jason Reiss 36:b586cd6e91f3 6 #else
Jason Reiss 36:b586cd6e91f3 7 Command("AT+CSN")
Jason Reiss 36:b586cd6e91f3 8 #endif
Jason Reiss 36:b586cd6e91f3 9 {
Jason Reiss 36:b586cd6e91f3 10 _queryable = true;
Jason Reiss 36:b586cd6e91f3 11 }
Jason Reiss 36:b586cd6e91f3 12
Jason Reiss 36:b586cd6e91f3 13 uint32_t CmdCustomSerialNumber::action(const std::vector<std::string>& args)
Jason Reiss 36:b586cd6e91f3 14 {
Jason Reiss 36:b586cd6e91f3 15 if (args.size() == 1)
Jason Reiss 36:b586cd6e91f3 16 {
Jason Reiss 36:b586cd6e91f3 17 CommandTerminal::Serial()->writef("%s\r\n", CommandTerminal::Dot()->getCustomSerialNumber().c_str());
Jason Reiss 36:b586cd6e91f3 18 }
Jason Reiss 36:b586cd6e91f3 19 else if (args.size() == 2)
Jason Reiss 36:b586cd6e91f3 20 {
Jason Reiss 36:b586cd6e91f3 21 if (CommandTerminal::Dot()->setCustomSerialNumber(args[1]) == mDot::MDOT_OK)
Jason Reiss 36:b586cd6e91f3 22 {
Jason Reiss 36:b586cd6e91f3 23 CommandTerminal::Serial()->writef("Set ID: %s\r\n", args[1].c_str());
Jason Reiss 36:b586cd6e91f3 24 }
Jason Reiss 36:b586cd6e91f3 25 else
Jason Reiss 36:b586cd6e91f3 26 {
Jason Reiss 36:b586cd6e91f3 27 return 1;
Jason Reiss 36:b586cd6e91f3 28 }
Jason Reiss 36:b586cd6e91f3 29 }
Jason Reiss 36:b586cd6e91f3 30
Jason Reiss 36:b586cd6e91f3 31 return 0;
Jason Reiss 36:b586cd6e91f3 32 }
Jason Reiss 36:b586cd6e91f3 33
Jason Reiss 36:b586cd6e91f3 34 bool CmdCustomSerialNumber::verify(const std::vector<std::string>& args)
Jason Reiss 36:b586cd6e91f3 35 {
Jason Reiss 36:b586cd6e91f3 36 if (args.size() == 1)
Jason Reiss 36:b586cd6e91f3 37 return true;
Jason Reiss 36:b586cd6e91f3 38
Jason Reiss 36:b586cd6e91f3 39 if (args.size() == 2) {
Jason Reiss 36:b586cd6e91f3 40
Jason Reiss 36:b586cd6e91f3 41 if (args[1].size() > CUSTOM_FIELD_LENGTH) {
Jason Reiss 36:b586cd6e91f3 42 #if MTS_CMD_TERM_VERBOSE
Jason Reiss 36:b586cd6e91f3 43 CommandTerminal::setErrorMessage("Invalid length, expects (string:16)");
Jason Reiss 36:b586cd6e91f3 44 #endif
Jason Reiss 36:b586cd6e91f3 45 return false;
Jason Reiss 36:b586cd6e91f3 46 }
Jason Reiss 36:b586cd6e91f3 47
Jason Reiss 36:b586cd6e91f3 48 return true;
Jason Reiss 36:b586cd6e91f3 49 }
Jason Reiss 36:b586cd6e91f3 50
Jason Reiss 36:b586cd6e91f3 51 #if MTS_CMD_TERM_VERBOSE
Jason Reiss 36:b586cd6e91f3 52 CommandTerminal::setErrorMessage("Invalid arguments");
Jason Reiss 36:b586cd6e91f3 53 #endif
Jason Reiss 36:b586cd6e91f3 54 return false;
Jason Reiss 36:b586cd6e91f3 55 }