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/CmdSerialClearOnError.cpp@33:5c0252521669, 2021-01-29 (annotated)

Committer:
Jason Reiss
Date:
Fri Jan 29 13:04:32 2021 -0600
Revision:
33:5c0252521669
Parent:
28:c222ca8383f4 
Remove moved commands

Who changed what in which revision?

UserRevisionLine numberNew contents of line
Mike Fiore 9:ff62b20f7000 1 #include "CmdSerialClearOnError.h"
Mike Fiore 9:ff62b20f7000 2
Mike Fiore 14:f9a77400b622 3 CmdSerialClearOnError::CmdSerialClearOnError() :
Jason Reiss 28:c222ca8383f4 4 #if MTS_CMD_TERM_VERBOSE
Jason Reiss 28:c222ca8383f4 5 Command("Clear On Error", "AT+SDCE", "Serial clear on error if enabled data that cannot be sent will be discarded", "(0:off,1:on)")
Jason Reiss 27:5fafd3b26ac3 6 #else
Jason Reiss 28:c222ca8383f4 7 Command("AT+SDCE")
Jason Reiss 27:5fafd3b26ac3 8 #endif
Mike Fiore 9:ff62b20f7000 9 {
Mike Fiore 9:ff62b20f7000 10 _queryable = true;
Mike Fiore 9:ff62b20f7000 11 }
Mike Fiore 9:ff62b20f7000 12
jenkins@jenkinsdm1 18:63f098f042b2 13 uint32_t CmdSerialClearOnError::action(const std::vector<std::string>& args)
Mike Fiore 9:ff62b20f7000 14 {
Mike Fiore 9:ff62b20f7000 15 if (args.size() == 1)
Mike Fiore 9:ff62b20f7000 16 {
Mike Fiore 14:f9a77400b622 17 CommandTerminal::Serial()->writef("%d\r\n", CommandTerminal::Dot()->getSerialClearOnError());
Mike Fiore 9:ff62b20f7000 18 }
Mike Fiore 9:ff62b20f7000 19 else if (args.size() == 2)
Mike Fiore 9:ff62b20f7000 20 {
Mike Fiore 9:ff62b20f7000 21 bool enable = (args[1] == "1");
Mike Fiore 9:ff62b20f7000 22
Mike Fiore 14:f9a77400b622 23 if (CommandTerminal::Dot()->setSerialClearOnError(enable) != mDot::MDOT_OK) {
Mike Fiore 9:ff62b20f7000 24 return 1;
Mike Fiore 9:ff62b20f7000 25 }
Mike Fiore 9:ff62b20f7000 26 }
Mike Fiore 9:ff62b20f7000 27
Mike Fiore 9:ff62b20f7000 28 return 0;
Mike Fiore 9:ff62b20f7000 29 }
Mike Fiore 9:ff62b20f7000 30
jenkins@jenkinsdm1 18:63f098f042b2 31 bool CmdSerialClearOnError::verify(const std::vector<std::string>& args)
Mike Fiore 9:ff62b20f7000 32 {
Mike Fiore 9:ff62b20f7000 33 if (args.size() == 1)
Mike Fiore 9:ff62b20f7000 34 return true;
Mike Fiore 9:ff62b20f7000 35
Mike Fiore 9:ff62b20f7000 36 if (args.size() == 2) {
Mike Fiore 9:ff62b20f7000 37 if (args[1] != "1" && args[1] != "0") {
Jason Reiss 28:c222ca8383f4 38 #if MTS_CMD_TERM_VERBOSE
Mike Fiore 14:f9a77400b622 39 CommandTerminal::setErrorMessage("Invalid parameter, expects (0: off, 1: on)");
Jason Reiss 28:c222ca8383f4 40 #endif
Mike Fiore 9:ff62b20f7000 41 return false;
Mike Fiore 9:ff62b20f7000 42 }
Mike Fiore 9:ff62b20f7000 43
Mike Fiore 9:ff62b20f7000 44 return true;
Mike Fiore 9:ff62b20f7000 45 }
Mike Fiore 9:ff62b20f7000 46
Jason Reiss 28:c222ca8383f4 47 #if MTS_CMD_TERM_VERBOSE
Mike Fiore 14:f9a77400b622 48 CommandTerminal::setErrorMessage("Invalid arguments");
Jason Reiss 28:c222ca8383f4 49 #endif
Mike Fiore 9:ff62b20f7000 50 return false;
Mike Fiore 9:ff62b20f7000 51 }