Note the following details of the code protection feature on Microchip devices:
YSTEM
CERTIFIED BY DNV
== ISO/TS 16949==
•Microchip products meet the specification contained in their particular Microchip Data Sheet.
•Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the
intended manner and under normal conditions.
•There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our
knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data
Sheets. Most likely, the person doing so is engaged in theft of intellectual property.
•Microchip is willing to work with the customer who is concerned about the integrity of their code.
•Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not
mean that we are guaranteeing the product as “unbreakable.”
Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our
products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts
allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act.
Information contained in this publication regarding device
applications and the like is provided only for your convenience
and may be superseded by updates. It is your responsibility to
ensure that your application meets with your specifications.
MICROCHIP MAKES NO REPRESENTATIONS OR
WARRANTIES OF ANY KIND WHETHER EXPRESS OR
IMPLIED, WRITTEN OR ORAL, STATUTORY OR
OTHERWISE, RELATED TO THE INFORMATION,
INCLUDING BUT NOT LIMITED TO ITS CONDITION,
QUALITY, PERFORMANCE, MERCHANTABILITY OR
FITNESS FOR PURPOSE. Microchip disclaims all liability
arising from this information and its use. Use of Microchip
devices in life support and/or safety applications is entirely at
the buyer’s risk, and the buyer agrees to defend, indemnify and
hold harmless Microchip from any and all damages, claims,
suits, or expenses resulting from such use. No licenses are
conveyed, implicitly or otherwise, under any Microchip
intellectual property rights unless otherwise stated.
Microchip received ISO/TS-16949:2009 certification for its worldwide
headquarters, design and wafer fabrication facilities in Chandler and
Tempe, Arizona; Gresham, Oregon and design centers in California
and India. The Company’s quality system processes and procedures
are for its PIC
devices, Serial EEPROMs, microperipherals, nonvolatile memory and
analog products. In addition, Microchip’s quality system for the design
and manufacture of development systems is ISO 9001:2000 certified.
®
MCUs and dsPIC® DSCs, KEELOQ
®
code hopping
QUALITY MANAGEMENT S
Trademarks
The Microchip name and logo, the Microchip logo, AnyRate, AVR,
AVR logo, AVR Freaks, BitCloud, CryptoMemory, CryptoRF,
dsPIC, FlashFlex, flexPWR, Heldo, JukeBlox, KeeLoq, Kleer,
LANCheck, LINK MD, maXStylus, maXTouch, MediaLB,
megaAVR, MOST, MOST logo, MPLAB, OptoLyzer, PIC,
picoPower, PICSTART, PIC32 logo, Prochip Designer, QTouch,
SAM-BA, SpyNIC, SST, SST Logo, SuperFlash, tinyAVR, UNI/O,
and XMEGA are registered trademarks of Microchip Technology
Incorporated in the U.S.A. and other countries.
ClockWorks, The Embedded Control Solutions Company,
EtherSynch, Hyper Speed Control, HyperLight Load, IntelliMOS,
mTouch, Precision Edge, and Quiet-Wire are registered
trademarks of Microchip Technology Incorporated in the U.S.A.
Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any
Capacitor, AnyIn, AnyOut, BodyCom, chipKIT, chipKIT logo,
CodeGuard, CryptoAuthentication, CryptoAutomotive,
CryptoCompanion, CryptoController, dsPICDEM, dsPICDEM.net,
Dynamic Average Matching, DAM, ECAN, EtherGREEN, InCircuit Serial Programming, ICSP, INICnet, Inter-Chip
Connectivity, JitterBlocker, KleerNet, KleerNet logo, memBrain,
Mindi, MiWi, motorBench, MPASM, MPF, MPLAB Certified logo,
MPLIB, MPLINK, MultiTRAK, NetDetach, Omniscient Code
Generation, PICDEM, PICDEM.net, PICkit, PICtail, PowerSmart,
PureSilicon, QMatrix, REAL ICE, Ripple Blocker, SAM-ICE, Serial
Quad I/O, SMART-I.S., SQI, SuperSwitcher, SuperSwitcher II,
Total Endurance, TSHARC, USBCheck, VariSense, ViewSpan,
WiperLock, Wireless DNA, and ZENA are trademarks of
Microchip Technology Incorporated in the U.S.A. and other
countries.
SQTP is a service mark of Microchip Technology Incorporated in
the U.S.A.
Silicon Storage Technology is a registered trademark of Microchip
Technology Inc. in other countries.
GestIC is a registered trademarks of Microchip Technology
Germany II GmbH & Co. KG, a subsidiary of Microchip
Technology Inc., in other countries.
All other trademarks mentioned herein are property of their
respective companies.
All documentation becomes dated, and this manual is no exception. Microchip tools and
documentation are constantly evolving to meet customer needs, so some actual dialogs and/
or tool descriptions may differ from those in this document. Please refer to our website
(www.microchip.com) to obtain the latest documentation available.
Documents are identified with a “DS” number. This number is located on the bottom of each
page, in front of the page number. The numbering convention for the DS number is
“DSXXXXXA”, where “XXXXX” is the document number and “A” is the revision level of the
document.
For the most up-to-date information on development tools, see the MPLAB
Select the Help menu, and then Topics to open a list of available online help files.
INTRODUCTION
®
IDE online help.
This chapter contains general information that will be useful to know before using the
RN2483 module. Topics discussed in this chapter include:
• Document Layout
• Conventions Used in this Guide
• Recommended Reading
• The Microchip Website
• Development Systems Customer Change Notification Service
• Customer Support
• Revision History
DOCUMENT LAYOUT
This command reference user’s guide provides information for configuring the RN2483
low-power long-range LoRa technology transceiver module, including a description of
communication and command references. The document is organized as follows:
• Chapter 1. “Introduction” – Introduces the RN2483 module and provides a brief
overview of its features.
• Chapter 2. “Command Reference” – Provides information on the commands
used to configure the RN2483 module with examples.
• Chapter 3. “Bootloader Usage” - Gives further information on the bootloader
usage and protocol commands.
• Appendix A. “Current Firmware Features and Fixes ” – Provides information
on the release notes for each revision of the firmware.
This command reference user’s guide describes how to configure the RN2483 module.
The module-specific data sheet contains current information on the module specifications.
Other useful documents are listed below. The following documents are available and
recommended as supplemental reference resources:
RN2483 Low-Power Long-Range LoRa® Technology Transceiver Module
Data Sheet (DS50002346)
This data sheet provides detailed specifications for the RN2483 module.
LoRa® Alliance: LoRaWAN™ Specification V1.0.2
This document describes the LoRaWAN Class A protocol, which is optimized for
battery-powered end devices. This specification is available from the LoRa Alliance at
http://www.lora-alliance.org.
To obtain any of Microchip’s documents, visit the Microchip website at
www.microchip.com.
THE MICROCHIP WEBSITE
Microchip provides online support via our website at www.microchip.com. This website
is used as a means to make files and information easily available to customers. Accessible by using your favorite Internet browser, the website contains the following information:
• Product Support – Data sheets and errata, application notes and sample
programs, design resources, user’s guides and hardware support documents,
latest software releases and archived software
• General Technical Support – Frequently Asked Questions (FAQs), technical
support requests, online discussion groups, Microchip consultant program
member listing
• Business of Microchip – Product selector and ordering guides, latest Microchip
press releases, listing of seminars and events, listings of Microchip sales offices,
distributors and factory representatives
DEVELOPMENT SYSTEMS CUSTOMER CHANGE NOTIFICATION SERVICE
Microchip’s customer notification service helps keep customers current on Microchip
products. Subscribers will receive e-mail notification whenever there are changes,
updates, revisions or errata related to a specified product family or development tool of
interest.
To register, access the Microchip website at www.microchip.com, click on Customer
Change Notification and follow the registration instructions.
The Development Systems product group categories are:
• Compilers – The latest information on Microchip C compilers, assemblers, linkers
and other language tools. These include all MPLAB C compilers; all MPLAB
assemblers (including MPASM™ assembler); all MPLAB linkers (including
MPLINK™ object linker); and all MPLAB librarians (including MPLIB™ object
librarian).
• Emulators – The latest information on Microchip in-circuit emulators.This
includes the MPLAB REAL ICE™ and MPLAB ICE 2000 in-circuit emulators.
• In-Circuit Debuggers – The latest information on the Microchip in-circuit
debuggers. This includes MPLAB ICD 4 and PICkit™ 4 in-circuit debuggers.
• MPLAB
Integrated Development Environment for development systems tools. This list is
focused on the MPLAB IDE, MPLAB IDE Project Manager, MPLAB Editor and
MPLAB SIM simulator, as well as general editing and debugging features.
• Programmers – The latest information on Microchip programmers. These include
production programmers such as MPLAB REAL ICE in-circuit emulator, MPLAB
ICD 4 in-circuit debugger and MPLAB PM3 device programmers. Also included
are non-production development programmers such as the PICkit 3.
®
IDE – The latest information on Microchip MPLAB IDE, the Windows®
Preface
CUSTOMER SUPPORT
Users of Microchip products can receive assistance through several channels:
• Distributor or Representative
• Local Sales Office
• Field Application Engineer (FAE)
• Technical Support
Customers should contact their distributor, representative or field application engineer
(FAE) for support. Local sales offices are also available to help customers. A listing of
sales offices and locations is included in the back of this document.
Technical support is available through the website at:
Added 2.3.6.5, 2.3.6.6, 2.3.6.7, 2.4.8.16, 2.4.8.17 sections; Updated 2-4, 2-6, 2-8 and
2-14 Tables, Updated 2.3.5.2, 2.4.4, 2.4.9.7, 2.4.9.18, and 2.5.5.17 sections; Other
minor corrections.
Revision D (February 2016)
Added a new Note box in section 2.4.9.2, updated section 2.4.9.16 and Figure 2-1,
added A.3 section; Other minor corrections.
Revision E (February 2016)
Removed Version 1.0.2 in section A.4; Other minor corrections.
Preface
Revision F (March 2017)
Added Chapter 3 (Bootloader Usage); Other minor corrections.
Revision G (September 2018)
Updated Note in section 1.4; Updated section 2-2 and Table 2-4; Added a new Note
box in section 2.3.6.6; Updated 2.4.4 and 2.4.6; Updated Table 2-6 and added sections
2.4.8.11, 2.4.8.12, 2.4.8.13, 2.4.8.14, 2.4.8.15, and 2.4.8.16; Updated Table 2-8,
These devices deal with
plaintext application data
These entities hold secret keys
that can encrypt/decrypt
application data
These devices relay encrypted
application data without being
able to decrypt it
)))
LoRaTMGateway
(((
RN2483
Host
MCU
)
))
The Microchip RN2483 module provides LoRaWAN™ protocol connectivity using a
simple UART interface. This module handles the LoRaWAN Class A and Class C
protocols and provides an optimized text command/response interface to the host
system. This document is intended to describe an implementation of the LoRaWAN
Class A and Class C protocols. LoRaWAN protocol terms are described in more detail
in the LoRaWAN™ Specification V1.0.2 available from the LoRa Alliance
(http://www.lora-alliance.org). Thus, it is recommended to review the LoRaWAN™ Specification V1.0.2 before using the RN2483 module.
The required configuration for accessing a LoRa technology network is minimal and
can be stored in the module’s EEPROM, allowing for factory configuration of these
parameters, lowering the requirements for the host system while also increasing
system security. The module also features GPIO pins that can be configured through
the UART interface.
A simple use case is described in Figure 1-1where an end device, containing a host
MCU which reads a sensor, commands the RN2483 to transmit the sensor reading
over the LoRa network. Data are encrypted by the RN2483 and the radio packet is
received by one or multiple gateways which forward it to the network server. The
network server sends the data to the application server which has the key to decrypt
the application data. Similarly, a development platform may consist of an RN2483
directly connected over UART to a PC which becomes the host system in this case.
Users can then type commands into the module using a terminal program.
The flow of data can be followed as it gets generated by an end device and transported
on the network.
1.2FEATURES
• LoRaWAN Class A and Class C protocol compliance
• Integrated FSK, GFSK and LoRa technology transceiver allowing the user to
transmit custom packets using these protocols
• Globally unique 64-bit identifier (EUI-64™)
• Configurable GPIOs
• Intelligent Low-Power mode with programmable/on-demand wake up
• Bootloader for firmware upgrade
• All configuration and control done over UART using simple ASCII commands
Refer to the RN2483, Low-Power Long-Range LoRa
Data Sheet
(DS50002346)for details on the hardware specifications of the module.
®
T echnology Transceiver Module
1.3CONFIGURATION
The RN2483 module’s architecture is described in Figure 1-2 from the command
interface point of view. There are three types of commands that can be used, and each
allows access to different module functions:
• LoRaWAN Class A and Class C configuration and control, using the mac group of
commands
• Low-level radio configuration and control, using the radio group of commands
• Other module functions, using the sys group of commands
FIGURE 1-2:RN2483 COMMAND INTERFACE (YELLOW) AND ITS
RELATIONSHIP TO THE MODULE’S INTERNAL
COMPONENTS
The available commands can be used to configure and control the LoRaWAN protocol
layer, the radio driver and some system peripherals.
In order to communicate with a LoRa network, a specific number of parameters need
to be configured. Since two distinctive methods are offered for a device to become part
of the network, each of these requires different parameters:
• Over-the-Air Activation (OTAA), where a device negotiates network encryption
keys at the time it joins the network. For this, the device EUI, application EUI and
application key need to be configured and then the OTAA procedure can start.
• Activation by Personalization (ABP) where the device already contains the
network keys and can directly start communication with the network. Configuring
DS40001784G-page 12 2015-2018 Microchip Technology Inc.
the device address, network session key and application session key is sufficient
for this type of initialization.
For increased security, these parameters can be configured and stored in the module’s
EEPROM during manufacturing of devices requiring LoRaWAN connectivity. Thus, the
keys do not need to be sent over the UART interface by the host system every time the
device powers up.
1.4UART INTERFACE
All of the RN2483 module’s settings and commands are transmitted over UART using
the ASCII interface.
All commands need to be terminated with <CR><LF> and any replies they generate will
also be terminated by the same sequence.
The default settings for the UART interface are 57600 bps, 8 bits, no parity, 1 Stop bit,
no flow control. The baud rate can be changed by triggering the auto-baud detection
sequence of the module. To do this, the host system needs to transmit a Break
condition to the module followed by a 0x55 character at the new baud rate. The
auto-baud detection mechanism can also be triggered during sleep to wake the module
up before the predetermined time has expired.
Note:A break condition is signaled to the module by keeping the UART_RX pin
Introduction
low for longer than the time to transmit a complete character. For example,
at the default baud rate of 57600 bps, keeping the UART_RX pin low for
226 s is a valid 13-bit break condition, whereas at 9600 bps this may be
interpreted as a 0x00 character. Thus, the Break condition needs to be
long enough to still be interpreted as such at the baud rate that is currently
in use. At 9600 bps a valid 13-bit Break condition must need to be 1,350 s.
Break condition calculation is as follows:
T
= Nb/bps
b
Where:
= time required for Break condition
* T
b
* Nb = number of bits required for Break condition
* bps = current bit rate
DS40001784G-page 14 2015-2018 Microchip Technology Inc.
Chapter 2. Command Reference
The RN2483 LoRa technology module supports a variety of commands for
configuration. This section describes these commands in detail and provides
examples.
2.1COMMAND SYNTAX
To issue commands to the RN2483 module, the user sends keywords followed by
optional parameters. Commands (keywords) are case-sensitive, and spaces must not
be used in parameters. Hex input data can be uppercase or lowercase. String text data,
such as OTAA used for the join procedure, can be uppercase or lowercase.
The use of shorthand for parameters is NOT supported.
Depending on the command, the parameter may expect values in either decimal or
hexadecimal form; refer to the command description for the expected form. For
example, when configuring the frequency, the command expects a decimal value in
Hertz such as 868100000 (868.1 MHz). Alternatively, when configuring the LoRaWAN
device address, the hex value is entered into the parameter as aabbccdd. To enter a
number in hex form, use the value directly. For example, the hex value 0xFF would be
entered as FF.
RN2483 LoRa TECHNOLOGY MODULE
COMMAND REFERENCE USER’S GUIDE
2.2COMMAND ORGANIZATION
There are three general command categories, as shown in Table 2-1.
TABLE 2-1:COMMAND TYPES
Command TypeKeywordDescription
System<sys>Issues system level behavior actions, gathers status
LoRaWAN™ Class A
and Class C Protocols
Transceiver commands <radio> Issues radio specific configurations, directly accessing
information on the firmware and hardware version, or
accesses the module user EEPROM memory.
<mac>Issues LoRaWAN Class A and Class C protocols
network communication behaviors, actions and
configuration commands.
After configuring the LoRaWAN protocol settings, the user must save them to
EEPROM with the mac save command. Once the settings have been saved, they will
be retained after a reboot or Reset.
Note: Upon successful reception a command, based on the specific command,
the module will respond with one of the following:
•ok
•busy
•fram_counter_err_rejoin_needed
•invalid_class
•invalid_data_len
•invalid_param
•keys_not_init
•mac_paused
•multicast_keys_not_set
•no_free_ch
•not_joined
•silent
•err
Note:To facilitate the sharing of the radio between user custom applications and
the LoRaWAN MAC, refer to the mac pause and mac resume commands.
Since no sharing exists between sys and other types of commands, there
is no need for additional pause commands.
2.3SYSTEM COMMANDS
System commands begin with the system keyword <sys> and include the categories
shown in Ta b le 2 - 2, Ta bl e 2 - 3 and Table 2-4.
TABLE 2-2:SYSTEM COMMANDS
ParameterDescription
sleepPuts the system in sleep for a finite number of milliseconds.
resetResets and restarts the RN2483 module.
eraseFWDeletes the current RN2483 module application firmware and prepares it for
factoryRESET Resets the RN2483 module’s configuration data and user EEPROM to
(1)
set
(1)
get
Note 1:Refer to
summaries.
firmware upgrade. The RN2483 module bootloader is ready to receive new
firmware.
factory default values and restarts the RN2483 module.
Sets specified system parameter values.
Gets specified system parameter values.
Table 2-3 for system <set> and Table 2-4 for system <get> command
DS40001784G-page 16 2015-2018 Microchip Technology Inc.
Command Reference
2.3.1sys sleep <length>
<length>: decimal number representing the number of milliseconds the system is
put to sleep, from 100 to 4294967296.
Response: ok after the system gets back from Sleep mode
invalid_param if the length is not valid
This command puts the system to sleep for the specified number of milliseconds. The
module can be forced to exit from sleep by sending the UART a Break condition
followed by a 0x55 character. Forcing the module from sleep in the manner also
triggers the UART auto baud detection. The module will adjust the UART baud rate to
match the baud rate at which the 0x55 character was sent. Refer to the note box in
1.4 “UART Interface”.
Example: sys sleep 120 // Puts the system to sleep for 120 ms.
2.3.2sys reset
Response: RN2483 X.Y.Z MMM DD YYYY HH:MM:SS, where X.Y.Z is firmware
version, MMM is month, DD is day, YYYY is year, HH:MM:SS is hour,
minutes, seconds (format: [HW] [FW] [Date] [Time]). [Date] and [Time] refer
to the release of the firmware.
This command resets and restarts the RN2483 module; stored LoRaWAN protocol
settings will be loaded automatically upon reboot.
Example: sys reset// Resets and restarts the RN2483 module.
2.3.3sys eraseFW
Response: no response
This command deletes the current RN2483 module application firmware and prepares
it for firmware upgrade. The RN2483 module bootloader is ready to receive new
firmware.
Example: sys eraseFW// Deletes the current RN2483 module
application firmware.
2.3.4sys factoryRESET
Response: RN2483 X.Y.Z MMM DD YYYY HH:MM:SS, where X.Y.Z is firmware
version, MMM is month, DD is day, YYYY is year, HH:MM:SS is hour,
minutes, seconds (format: [HW] [FW] [Date] [Time]). [Date] and [Time] refer
to the release of the firmware.
This command resets the module’s configuration data and user EEPROM to factory
default values and restarts the module. After factoryRESET, the RN2483 module will
automatically reset and all configuration parameters are restored to factory default
values. All LoRaWAN protocol settings set by the user will be lost.
nvmStores <data> to a location <address> of user EEPROM.
pindigAllows user to set and clear available digital pins.
pinmodeAllows user to set the functionality of a pin to either digital input, digital output
or analog input (if available).
2.3.5.1sys set nvm <address> <data>
<address>: hexadecimal number representing user EEPROM address, from 300 to
3FF
<data>:hexadecimal number representing data, from 00 to FF
Response:ok if the parameters (address and data) are valid
invalid_param if the parameters (address and data) are not valid
This command allows the user to modify the user EEPROM at <address> with the
value supplied by <data>. Both <address> and <data> must be entered as hex
values. The user EEPROM memory is located inside the MCU on the module.
Example: sys set nvm 300 A5// Stores the value 0xA5 at user EEPROM
address 0x300.
2.3.5.2sys set pindig <pinname> <pinstate>
<pinname>:string representing the pin. Parameter can be: GPIO0 - GPIO13,
UART_CTS, UART_RTS, TEST0, TEST1
<pinstate>: decimal number representing the state. Parameter values can be: 0 or
1.
Response: ok if the parameters (<pinname>, <pinstate>) are valid
invalid_param if the parameters (<pinname>, <pinstate>) are not
valid
This command allows the user to modify the unused pins available for use by the
module. The selected <pinname> is driven high or low depending on the desired
<pinstate>.
Default: GPIO0-GPIO13, UART_CTS, UART_RTS, TEST0 and TEST1 are driven low
(value 0).
Example: sys set pindig GPIO5 1// Drives GPIO5 high 1, V
DD.
Note:In order for the pin to be driven to a value, make sure you have first
configured the pin to be a digital output using the command sys set pinmode <pinname> digout.
2.3.5.3sys set pinmode <pinname> <pinmode>
<pinname>: string representing the pin. Parameters can be: GPIO0 - GPIO13,
UART_CTS, UART_RTS, TEST0, TEST1
<pinmode>: string representing the functional mode of the pin. Parameters can be:
digout, digin or ana.
Response: ok if all the parameters are valid
invalid_param if any of the parameters are not valid
This command allows the user to configure the functional mode of a pin. A pin can be
DS40001784G-page 18 2015-2018 Microchip Technology Inc.
Command Reference
configured as digital output by using the digout parameter. A pin can be configured
as digital input by using the digin parameter. A pin can be configured as analog input
by using the ana parameter.
Note:Not all pins have analog input functionality.
Example: sys set pinmode GPIO0 ana //Configures GPIO0 as analog input
Note:This command must be called prior to reading or setting the value of a pin
in order to have correct behavior.
2.3.6System Get Commands
TABLE 2-4:SYSTEM GET COMMANDS
ParameterDescription
verReturns the information on hardware platform, firmware version, release
date.
nvmReturns data from the requested user EEPROM <address>.
vddReturns measured voltage in mV.
hweuiReturns the preprogrammed EUI node address.
pindigReturns the state of a digital input.
pinanaReturns the state of an analog input.
2.3.6.1sys get ver
Response: RN2483 X.Y.Z MMM DD YYYY HH:MM:SS, where X.Y.Z is firmware
version, MMM is month, DD is day, YYYY is year, HH:MM:SS is hour,
minutes, seconds
(format: [HW] [FW] [Date] [Time]). [Date] and [Time] refer to the release of
the firmware.
This command returns the information related to the hardware platform, firmware
version, release date and time stamp on firmware creation.
Example: sys get ver// Returns version-related information.
2.3.6.2sys get nvm <address><address>: hexadecimal number representing user EEPROM address, from 300 to
3FF
Response:00 – FF (hexadecimal value from 00 to FF) if the address is valid
invalid_param if the address is not valid
This command returns the data stored in the user EEPROM of the RN2483 module at
the requested <address> location.
Example: sys get nvm 300// Returns the 8-bit hex value stored at
300.
2.3.6.3sys get vdd
Response: 0–3600 (decimal value from 0 to 3600)
This command informs the RN2483 module to do an ADC conversion on the V
DD. The
measurement is converted and returned as a voltage (mV).
Example: sys get vdd// Returns mV measured on the V
Response: hexadecimal number representing the preprogrammed EUI node
address
This command reads the preprogrammed EUI node address from the RN2483 module.
The value returned by this command is a globally unique number provided by
Microchip.
Example: sys get hweui// Reads the preprogrammed EUI node
address.
Note:The preprogrammed EUI node address is a read-only value and cannot be
changed or erased. This value can be used to configure the device EUI
using the mac set deveui command (see Section2.4.8.8).
2.3.6.5sys get pindig <pinname>
<pinname>: string representing the pin. Parameters can be: GPIO0 - GPIO13,
UART_CTS, UART_RTS, TEST0, TEST1
Response: decimal number representing the state (either 0 or 1).
This command allows the user to read the state of a digital input. To be used as a
digital input, a pin needs to be configured using the sys set pinmode command.
Example: sys get pindig GPIO0 //Reads the state of the GPIO0 digital input
Note:The sys set pinmode <pinname> digin command must be
called to configure the function of the pin prior to reading its digital input
value.
2.3.6.6sys get pinana <pinname>
<pinname>: string representing the pin. Parameters can be: GPIO0 - GPIO3,
GPIO5 - GPIO13
Response: decimal number representing the result of the conversion, from 0 to 1023,
where 0 represents 0V and 1023 is V
DD, the supply voltage of the module.
This command allows the user to read the state of an analog input. To be used as an
analog input, a pin needs to be configured using the sys set pinmode command.
Example: sys get pinana GPIO0 //Reads the state of the GPIO0 analog input
Note:The sys set pinmode <pinname> ana command must be
called to configure the functional mode of the pin prior to reading its
analog input value.
DS40001784G-page 20 2015-2018 Microchip Technology Inc.
Loading...
+ 44 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.