Additional LoRa configuration fields in /var/config/lora/lora-network-server.conf:

Use the LoRa Network Server Configuration settings for the LoRa networking configured on the Conduit. When LoRa is enabled, the Conduit acts as a network server allowing end-points to join with the correct credentials on the correct frequency and sub-band. Configured LoRa for either the 915 frequency band (NAM), or the 868 frequency band (EU). For NAM, the 915 band allows 8 sub-bands. For the EU, the 868 band has three default channels and five configurable channels.

Use the TX Power setting to control the gateway’s transmission power. The Rx 1 DR Offset and RX 2 Datarate are sent with a join response to configure the data rates used for receive windows. The offset is applied to the upstream data rate for reception on the first window.

For more information about setting up a LoRa network on a Conduit AEP, go to Getting Started with LoRa Conduit AEP (LoRa Configuration)

LoRa Configuration

The LoRa Configuration pane contains the configuration values for the LoRa network server that acts as a gateway for the LoRa endpoint devices.

Server Ports

The server ports communicate via UDP with other processes running on the
Conduit.

Payload Broker

The payload broker is an MQTT broker that facilitates communication between an application and the network server.

Links

Intro to LoRa

Basic Configuration

Advanced Configuration

MQTT Messages

Methods for end-devices to join the Conduit LoRaWAN network

Order of network server join authentication

The first one to succeed will provide the appkey and configuration used for creating the session keys.

1. Network ID and Network Key are checked if the JoinEUI/AppEUI in the Join Request matches the NetworkID
2. If Join Server Location is set to Local Keys, or in mLinux whitelist is enabled
   • The whitelist is searched for the DevEUI and the AppKey and Class setting are used for the device
3. If Join Server Location is set to Cloud Key Store, or in mLinux whitelist is disabled and Lens settings are correct
   • The Join Request is sent to the Join Server to be authenticated, the Lens end-device configuration is returned to the Conduit including the Class setting.

LoRa Query Utility

The LoRa Query Utility provides an easy to use interface to the command port for most operations as an alternative to directly accessing the UDP command port.

lora-query
Version: 1.0.4

Usage: lora-query [-t timeout] [-s] [-n]
        Simple UDP client utility to pull info from LoRa Network server
        --timeout (t)     : UDP recv timeout, default: 100 (msecs)
        --stats (s)       : get LoRa Network server statistics
        --stats-reset (r) : reset LoRa Network server statistics
        --node-list (n)   : get Node List
        --command (x) : send command string to network server
                usage: --command   ...
                ex:    --command device list json
                ex:    -x help
        --json (j)        : data in json format
        --help (?)        : returns this message
        --version (v)     : print version

Examples

End-Device List

> lora-query -x devices

Add End-device
Add a node for ABP or MANUAL network joining

> lora-query -x device add '{"deveui":"00-80-00-00-00-00-e1-9c","class":"C"}'

> lora-query -x session add '{"deveui":"00-80-00-00-00-00-e1-9c","dev_addr":"00112233","appeui":"00-88-88-88-00-00-e1-9c","joineui":"00-99-99-99-00-00-e1-9c","net_id":"000017","app_senc_key":"531bd9c5ec5d8ba5ef3b262cebfb3e66","fnwk_sint_key":"531bd9c5ec5d8ba5ef3b262cebfb3e66"}'

Add a node for OTA join with unique APPKEY

AEP use LoRaWAN > Key Management page in GUI or this curl command, restart of network server is needed after adding

> curl 127.0.0.1/api/loraNetwork/whitelist/devices -X POST --data '{"deveui":"16ea76f6ab663d80","appeui":"0001020304050607","class":"C","appkey":"4c194e20d396b5f7d3e1551e4cd320de"}' -H "Content-Type: application/json"
> curl 127.0.0.1/api/command/save -X POST --data ""
> /etc/init.d/lora-network-server restart

mLinux

> vi /var/config/lora/lora-network-server.conf
...,
"whitelist": {
 "enabled": true,
 "devices": [
     {"deveui":"16ea76f6ab663d80","appeui":"0001020304050607","class":"C","appkey":"4c194e20d396b5f7d3e1551e4cd320de"}
  ]
},
...

Remove an end-device

> lora-query -x device delete 008000df30011a6c

Change node class

> curl 127.0.0.1/api/loraNetwork/whitelist/devices/0 -X PUT --data '{"class":"A"}' -H "Content-Type: application/json"

Command Interface

Connect using netcat

nc -u localhost 6677

or

echo "$x" > /dev/udp/localhost/6677

Where $x is the command to execute.

LoRa Network Server Commands 2.0.19

admin@mtcdt:/opt/lora# lora-query -x help
MTS Lora Server Command Help

Commands:
stats - list current stats
  reset - reset stats for network, gateways and end-devices
gateway - gateway commands
  list - list connected gateways
      format: gateway list [json]
  delete - remove a gateway from the list
      format: device gateway 
device - end-device commands
  add - add a new end-device record
      format: device add 
      example: device add '{"deveui":"00-80-00-00-00-00-e1-9c","class":"C"}'
  stats - show end-device statistics
  update - update end-device configuration or session info
      format: device update   
      example: device update 00-80-00-00-00-00-e1-9c class C
      fields: class, nskey, dskey, ulc, dlc
      format: device update 
      example: device update '{"deveui":"00-80-00-00-00-00-e1-9c","class":"C"}'
      fields: class, name, serial_number, product_id, hardware_version, firmware_version, lorawan_version
  delete - delete an end-device configuration, session and packet records
      format: device delete 
  config - show configuration for a specific device
  reset - reset end-device session counters
      format: device reset 
  list - list end-devices configured in the network server
      format: device list [json | json file ]
      example: device list json
      example: device list json file /tmp/devices.json
  keygen - generate a unique end-device key using zero-touch settings
      format: device keygen  [APP-EUI]
session - session commands
  add - add a session for a device
      format: session add 
      example: session add '{"deveui":"00-80-00-00-00-00-e1-9c","dev_addr":"00112233","appeui":"00-88-88-88-00-00-e1-9c","joineui":"00-99-99-99-00-00-e1-9c","net_id":"0
00017","app_senc_key":"531bd9c5ec5d8ba5ef3b262cebfb3e66","fnwk_sint_key":"531bd9c5ec5d8ba5ef3b262cebfb3e66"}'
      fields: deveui, appeui, joineui, dev_addr, net_id, app_senc_key, fnwk_sint_key
  delete - remove a device session
      format: session delete 
  reset - reset session counters
      format: session reset 
  list - show current device sessions
      format: session list [json | json file  ]
      example: session list jsonvi /
      example: session list json file /tmp/sessions.json
packet - packet commands
  join - list all validated join packets
      format: packet join [json]
  recent - list all recently received packets (unauthenticated)
      format: packet recent [json]
      join - list all recently received join requests
            format: packet recent join [json]
  up - list all validated uplink packets
      format: packet up [json]
  down - list all downlink packets
      format: packet down [json]
  list - list all packets: join, up and down
      format: packet list [json]
  queue - list downlink queue packets to be sent to end-device
      format: packet queue [json]
    add - add a packet to the downlink queue
      format: packet queue add 
      fields: deveui, data, ack, ack_retries, rx_wnd
    delete - delete all downlinks for a specific device
      format: packet queue delete 
    delete - delete one downlink for a specific device
      format: packet queue delete  
database - database commands
  backup - backup database to flash memory
config - show network server configuration
debug - change debug level
ping - ping the network server command port
help - display this help
quit - command network server process to stop

- add 'json' modifier to request output in json

LoRa Network Server Commands 1.0.32

• database backup

LoRa Network Server Commands 1.0.26

• node keygen <DEV-EUI> [APP-EUI] – zero touch key generation

LoRa Network Server Commands 1.0.8

• config – display config
• stats – display stats
• stats reset – reset network server stats
• print error|warning|info|debug|trace – change debug output level
• node list – list nodes
• node add <NET-ADDR> [CLASS] <APP-EUI> <DEV-EUI> { [APP-KEY] | [NET-SKEY] [APP-SKEY] }
  • ABP

    node add <NET-ADDR> [CLASS] <APP-EUI> <DEV-EUI> [NET-SKEY] [APP-SKEY]
    node add 00000001 A 0011223344556677 7766554433221100 00112233445566777766554433221100 77665544332211007766554433221100

  • OTAA with unique APP-KEY

    node add <NET-ADDR> [CLASS] <APP-EUI> <DEV-EUI> [APP-KEY]
    node add 00000001 A 0011223344556677 7766554433221100 00112233445566777766554433221100

• node delete <NET-ADDR> – delete a node
• node config <NET-ADDR> – show node config
• node update <NET-ADDR> (class | appkey | nskey | dskey) <VALUE> – update a config setting
  • change existing node to class C

    node update 00000001 class c

  • change existing node APP-KEY

    node update 00000001 appkey 00112233445566777766554433221100

• node reset <NET-ADDR> – reset node counters
• ping – print alive message
• include <FILENAME> – Read commands from file

LoRa Network Server Commands 0.9.2

• config – display config
• stats – display stats
• stats reset – reset network server stats
• print error|warning|info|debug|trace – change debug output level
• node list – list nodes
• node add <NET-ADDR> <APP-EUI> <DEV-EUI> [NET-SKEY] [APP-SKEY]
• node delete <NET-ADDR> – delete a node
• node reset <NET-ADDR> – reset node stats
• ping – print alive message
• include <FILENAME> – Read commands from file

For Conduit^® MTCDT and MTCAP models

Setting up the Conduit

Prior to starting LoRa, make sure you have properly installed and cabled your LoRa hardware.

1. Power up  your device and wait for it to boot up.
2. Login to the console. Refer to Getting Started with mLinux if needed.
3. Issue these commands on the Conduit:

   $ mkdir /var/config/lora
   $ cp /opt/lora/lora-network-server.conf.sample /var/config/lora/lora-network-server.conf

4. Edit /var/config/lora/lora-network-server.conf and modify these settings as needed (use vi or nano). For advanced LoRa settings, go to Conduit mLinux: Advanced LoRa Configuration

   Field	LORA-915, 923, 920 (NA, AU, JP, KR)	LORA-868, 865 (EU, IN)
   lora[“frequencyBand”]:	“915”	“868”
   lora[“channelPlan”]:	“US915”, “AU915”, “AS923”, “KR920”	“EU868”, “IN865”
   lora[“frequencySubBand”]:	(integer: 1 to 8)	Not applicable
   lora[“frequencyEU”]:	Not applicable	default: 869500000 range: [863500000 – 867500000] and [869100000 – 869500000]
   network[“name”]:	Name of your LoRa network (string, 8-char min, case sensitive)
   network[“passphrase”]:	Security passphrase for your LoRa network (string, 8-char min, case sensitive)
   network[“public”]:	Choose from 0: Private MTS, 1: Public LoRaWAN or 2: Private LoRaWAN, Private Options use SyncWord 0x12 vs Public SyncWord 0x34
   network[“joinDelay”]:	Set to desired Join Delay, default 5 seconds

5. Restart the network server.
   $ /etc/init.d/lora-network-server restart
6. Start mosquitto client:
   $ mosquitto_sub -t lora/+/+ -v

Setting Up the mDot

1. Establish a serial connection to the mDot^™
   1. Connect your PC to the DB9 serial connector on the UDK
   2. Open a terminal session using an application such as TeraTerm with baud rate 115,200
2. Issue these commands with the same values you set for the Conduit:
   • AT+PN=value (Match Public Network setting)
   • AT+JD=value (Match Join Delay setting)
   • AT+FSB=value (915 NA only | value = frequencySubBand from your Conduit)
   • AT+NI=1,value (value = Network Name for your Conduit)
   • AT+NK=1,value (value = Network Passphrase for your Conduit)
   • AT&W (save settings)
   • ATZ (restart)
3. Join the network: AT+JOIN
4. Send data with ACK requested:
   • AT+ACK=1
   • AT+SEND=hello world

Next Steps

• Conduit mLinux: LoRa Communication
• Troubleshooting LoRa Communication

This section only applies to devices with mPower^™ and LoRa. For the Conduit^®, LoRa cards are typically sold separately.

https://www.youtube.com/watch?v=Q_25lZWcSWI&t=6s

Before setting up LoRa, your device should be connected and powered up. If not refer to installation information for your device.

• For Conduit installation, see the Conduit Quick Start Guide.
• For Conduit Access Point installation, refer to the Quick Starts or User Guides available through Conduit AP
• For Conduit IP67 Base Station, refer to the Installation Guide for your model, available through Conduit IP67 Base Station

Getting Started with LoRa

1. Login to the web management interface. Refer to the software guide if needed.
2. Access the LoRaWAN Network Settings by going to LoRaWAN > Network Settings on the left sidebar. See LoRaWAN Network Settings in the software guide for details.
3. To modify advanced settings, click Show Advanced Settings. For more details, see LoRaWAN Network Settings in the software guide.
4. For configuring as a Packet Forwarder, select Packet Forwarder from Mode under LoRa Mode. For more details, see LoRaWAN Network Settings in the software guide.

Setting Up an mDot

1. Establish a serial connection to the mDot^™
   1. Connect your PC to the DB9 serial connector on the UDK
   2. Open a terminal session using an application such as TeraTerm with baud rate 115,200
2. Issue these commands with the same values you set for the gateway:
   • AT+FSB=value (915 NA only | value = frequencySubBand from your LoRa gateway)
   • AT+NI=1,value (value = Network Name for your LoRa gateway)
   • AT+NK=1,value (value = Network Passphrase for your LoRa gateway)
   • AT&W (save settings)
   • ATZ (restart)
3. Join the network: AT+JOIN
4. Send data with ACK requested:
   • AT+ACK=1
   • AT+SEND=hello world

Next Steps

• Conduit mPower: LoRa Communication and Node-RED
• Troubleshooting LoRa Communication
• Troubleshooting Guide

Server/Gateway Deployments using Multiple Conduits

A network of Conduits or Conduit 300s can be created with several setup as packet forwarders (Gateway) and one as a central network server (Server). This Server/Gateway deployment allows a basic limit of 10 gateways as 10 external packet forwarders. Local forwarders for LoRa cards installed on the network server unit do not count against this limit.

This configuration can be used to increase the area of the network or the number of channels supported. The capacity of the network will still be limited to a single instance of the network server, 2000 end-devices in default configuration.

NOTE: If you are using LENS®, there is no limit on the number of gateways or devices. But we recommend no more than 2000 end-devices for MTCDT/MTCAP in most circumstances.

The /var/config directory is limited to 8 MB. Custom applications may also be installed in the /var/config directory reducing the space available for the database. To reach 2000 connected end-devices it may be necessary to install an SD card to hold the custom application or network server database.

AEP Configuration

On Network Server Conduit

The central network server will handle all end-device session information, authenticate uplinks and author downlink packets.

Configure Network Server to accept connections from remote packet forwarders

1. Go to LoRaWAN > Network Settings on Conduit
2. Set Public LoRaWAN under Network section, if a private setting is selected all packet forwarders should also be set to private
3. Click Show Advanced Settings
4. Under Server Ports verify Local Only is unchecked to allow incoming connections from the packet forwarder Conduits.
5. Click Submit
6. Go to Firewall > Settings
7. Enable Allow Inbound Input Filter Rule, change allowed ports to 1780 and 1782
8. Save and Restart Conduit

Configure Forwarding Conduit to send packets to the Network Server

1. Go to LoRaWAN > Network Settings
2. Enable Packet Forwarder mode
3. Set Public under Basics section, or match setting selected on Network Server config above.
4. In Server section, settings must match those of Master Conduit
   1. Set Server Address to IP address
   2. Set Upstream Port to 1780
   3. Set Downstream Port to 1782
5. Click Submit
6. Save and Restart Conduit

After the Conduits have rebooted, navigate to the LoRaWAN > Gateways page on the first Conduit. The Forwarding Gateway should now be shown in the list. The IP address of the forwarding Conduit will be listed. Packet forwarders running on the same Conduit as the Network Server will have a local address (127.0.0.1).

Extending Supported Channels for US915 and AU915 Channel Plans

Additional channels can be supported by the network by enabled different Frequency Sub-Band settings on each forwarding Gateway. The supported channels must be relayed to the Network Server using the Channel Mask setting. This will allow the full set of channels to be enabled on the end-device following that OTAA join.

On a Forwarding Conduit

1. Go to LoRaWAN > Network Settings
2. Set the Frequency Sub-Band to the desired setting
3. Click Submit
4. Save and Restart the Conduit
5. Configure the other forwarding Conduits likewise

Configure Network Server to support additional channels

1. 1. Go to LoRaWAN > Network Settings on Conduit
2. Set channel mask to enable the additional channels
   • FSB 1, 2 and 3 – 00070000000000FFFFFF
   • FSB 1, 2, 3 and 4 – 000F00000000FFFFFFFF
   • FSB 5, 6, 7 and 8 – 00F0FFFFFFFF00000000
   • FSB 1 and 8 – 0081FF000000000000FF
3. Click Submit
4. Save and Restart the Conduit

mLinux Configuration

mLinux installations running the Network Server can be configured as well. Note: The mLinux images do not have a firewall enabled by default.

Allow the Network Server to accept incoming connections

1. Edit the configuration page

   # vi /var/config/lora/lora-network-server.conf

2. Configure “udp” => “allowPublic” to true
3. Save the file, enter ‘:x’
4. Restart the network server,

   # /etc/init.d/lora-network-server restart

Now the UDP ports are set to listen on the external IP interfaces.

Configure the packet forwarding Conduits

1. Setup the packet fowarder to send packets to the Network Server Conduit IP address and Ports
2. See Convert to Basic Packet Forwarder

• ABP – Activation by Personalization
• ADR – Adaptive Datarate
• AES-128 – Advanced Encryption Standard 128-bit wikipedia
• AppEUI – Application EUI, an 8-byte unique identifier for a LoRaWAN application
• AppKey – Application Key, a 16-byte AES-128 key used in LoRaWAN to authenticate an end-device and derive session keys
• Application Network – A set of gateways and end-devices configured to support a LoRaWAN application
• Application Server – Entity in a LoRaWAN network tasked with managing the Application Session Key to decrypt uplink payloads and encrypt downlink payloads in packets
• Application Session Key – A 16-byte AES-128 session key used in LoRaWAN to encrypt payloads between an application and end-device, derived from AppKey during OTAA
• Bandwidth – Width of a LoRa transmission at 20 dB
• Channel – Combination of LoRa datarate and frequency used for concurrent communications
• Channel Plan – Set of supported datarates and frequencies for use in a LoRaWAN network according to regional regulations
• Confirmed Packet – Packet requesting an ACK from the receiver
• Custom Application – An application installed on a Conduit, can be used to receive LoRaWAN packets from the network server then process and/or forward to a remote server
• Datarate – Combination of Spreading Factor and Bandwidth that determines the bit-rate of transmissions. Datarates can be used on the same frequency without interference. This creates virtual channels to reduce collisions.
• DevEUI – Device EUI, an 8-byte unique identifier for a LoRaWAN device
• Downlink – Packet sent from the gateway to an end-device
• Downlink Counter – Session counter for downlink packets, 32-bit unsigned integer, 16-bits are sent with each packet
• End-device – LoRa radio device expected to connect to the network and report
• ERP – Effective Radiated Power wikipedia
• EIRP – Effective Isotropic Radiated Power
• EUI – Extended Unique Indentifier wikipedia
• Frame Port – Optional 1-byte port value attached to packets, port 0 is used for sending mac commands in a payload, 1-223 can be used for application used. Values above 223 are reserved.
• Frame Counter – 16-bit value attached to each packet as the least significant bits of the 32-bit uplink or downlink counter
• Gateway – Component in a LoRaWAN network that receives packets from end-devices and forwards them to a network server
• Hybrid Operation – US915 channel plan operating in an 8-channel mode
• JoinEUI – Join EUI, an 8-byte identifier for LoRaWAN OTAA join requests
• Join Accept – Message to end-device containing network information for an end-device, encrypted with AppKey, aka join response
• Join Request – Message from end-device requesting to join a network, signed with AppKey
• Join Server – Component in a LoRaWAN network that authenticates join requests and authors join responses using a unique end-device AppKey
• LoRa – Low Power / Long Range, Digital spread-spectrum modulation technique used in Semtech SDR chips
• Network Server – Component in a LoRaWAN network that maintains session information for communications with end-devices
• Network Session Key – A 16-byte AES-128 session key used in LoRaWAN to authenticate uplink and downlink packets, derived from AppKey during OTAA
• OTAA – Over-the-air Activation
• OUI – Organizationally Unique Indentifer wikipedia
• Spreading Factor – Amount of redundancy used in transmissions to extend the range of end-
  devices
• Unconfirmed Packet – Packet not requesting ACK from the receiver
• Uplink – Packet sent from an end-device to a gateway
• Uplink Counter – Session counter for uplink packets, 32-bit unsigned integer, 16-bits are sent with each packet

Collections are groups of related elements used to configure a service or capability. You can perform four main actions on a collection: get, edit, add, and delete. These actions align with RESTful calls: GET, PUT, POST, and DELETE.

5.3.5 (10/19/2021)

• Release Notes

5.3.4

Known Issues

• Packet forwarder can stop transmitting after several days, work-around using CRON job to killall -9 lora_pkt_fwd – mPower 5.3.5 has this fixed

5.3.3 (3/29/2021)

• Release Notes

5.2.1 (6/10/2020)

• Release Notes

Known Issues

• Repeated valid join requests can cause the lora-network-server.db to fill the /var/config partition
• Packet forwarder can stop transmitting after several days when LBT is enabled

5.1.6 (3/08/2020)

Bug Fixes

• Web-UI clears local storage on signin to fix browser issues after upgrading

Known Issues

• LoRaWAN FOTA should use non-default Rx2 datarate, US/AU DR10 and other plans DR2 or above. The session may expire and the end-device will return to Class A mode before the firmware has finished broadcasting over multicast.

5.1.5 (3/08/2020)

Bug Fixes

• Fix logrotate issues when configured in packet forwarder mode

Known Issues

• LoRaWAN FOTA should use non-default Rx2 datarate, US/AU DR10 and other plans DR2 or above. The session may expire and the end-device will return to Class A mode before the firmware has finished broadcasting over multicast.

5.1.2 (12/06/2019)

Changes

• See Release Notes

Known Issues

• Packet forwarder logs not being rotated
  • FIX: Update lora-logging IPK to 1.0-r3
• LoRaWAN FOTA should use non-default Rx2 datarate, US/AU DR10 and other plans DR2 or above. The session may expire and the end-device will return to Class A mode before the firmware has finished broadcasting over multicast.

5.0.1(09/04/2019)

Changes since 5.0.0

• Add support for the L4E1 and L4N1 models

Bug Fixes since 5.0.0

• Allow access to SD card, access was lost in 5.0.0.
• Fix for LoRa Network Settings defaulted on upgrade from version <=1.7.4
• Fix two race conditions in LoRa Network Server, one blocked MQTT output, the other would cause a crash on uplink
• Disable node-red logging to /var/log/app/node-red.log, log was not rotating correctly causing RAM to be filled

Known Differences since 5.0.0

• No Known Differences.

Known Behavior in 5.0.1

• User must be at version 1.6.4 (or newer) before upgrading to 5.0.1.
• Although not recommended, downgrading to a version before 5.0.0 will require a
  hard reset back to factory default settings.
• A Hard Reset (or Factory Default) will force 5.0.1 firmware into Commissioning
  Mode to create a new Administrative Username and Password.
• On LVW2, certain newer Verizon SIM’s do not support SMS. Contact Verizon.
• On LVW2, received SMS’s greater than 140 characters may be truncated to 140.
• Command AT+WS46 reverts to default after a power cycle which may affect a user
  that sets a non-default value.
• SMS Command API ignores 6 character password limit, does not fail if SMS is
  longer than 160 characters, has issues depending on location of spaces and can
  not view/delete inbox/outbox.
• Notifications API can delete existing alerts, add new alerts, modify with
  non-existing group, add two groups with same name and generate email with
  bad characters.
• DHCP API can set invalid Gateway.
• With SMS Commands, the Whitelisted numbers may need to be updated to include a +,
  a 1, or full phone number. Send a test SMS to the device to confirm.
• Version 1 API call (/api/v1/whoami) does not respond.
• Connecting OpenVPN Tunnels, user is unable to open WebUI of remote device.
• If using Remote Management and you perform a manual check in to Device HQ, your
  device may show two check in’s based on your Check In Interval.
• The lora-network-server should be updated to from v2.2.30 to v2.2.41 to address a possible deadlock issue

5.0.0 (07/03/2019)

Changes since 1.7.4

• Migration of Web UI to vueJS. Look and Layout has changed.
• Added RADIUS support.
• DHCP Lease Time displays expiration date and time.
• Firewall display/layout aligns more with Linux layout.
• Implement X.509 Certificate support.
• Eliminate Default Username and Password. User prompted to set up a Username and secure Password upon Factory Default/Hard Reset, Commissioning Mode.
• The Logout option has changed to Door Exit icon.
• The browser tab name references page name.
• Changed LogIn screen to sign-in.
• Page links have removed the .html extension.
• Add IPSec certificate based authentication support.
• Updated supported ciphers in multiple features (SSH, HTTPS, etc…).
• Implement Trusted IP feature.
• Implement Self-Diagnostics beta feature to check Resource Overuse and Security Violations.
• Incorporated Signed Firmware support.
• SNMPv3 advanced security settings enhancements and support for multiple trap destinations. Extended SNMP read parameters.
• Usage Policy implementation in the Web UI.
• Display Notifications sent via Email, SMS, or SNMP.
• RADIUS Message Authenticator Attribute was added to all PAP requests.
• Implement tunnel features.
• Implementation of more Network Interface capabilities under Setup > Network Interfaces.
• Updated Global DNS Configuration under Setup > Global DNS.
• Added Bootloader password configuration to the Initial Setup Wizard.
• LoRa Network Server updated to v2.2.27.
• LoRa Packet Forwarder: Added duplicate packet filter, fix for GPS lock and time synchronization and increased radio lead time for better downlink success.
• Updated Help Content.

Bug Fixes since 1.7.4

• Add Statistics page for OpenVPN tunnel.
• Populated leading 0’s in SMS #cellular Command, Uptime now reads 00:00:00 not 0:0:0.
• Fixed “Invalid Date” issue when viewing Remote Management with Firefox 47.
• Fixed SMS Command #cellular eliminating Uptime leading 0’s.
• Fixed device position on GPS page map to not depend on NMEA configuration settings.
• Fixed Generate Certificate so that the City value is not lost and set to empty when generating a new Web server certificate.
• SMS Commands should work again for International numbers.

Known Differences from 1.7.4

• A hard reset/factory default of the 5.0.0 will force Commissioning mode.
• Security modifications may require “sudo” usage if using SSH or debug console.
• Security modifications require a “sudo su” to log into root and adding the following “–unix-socket /var/run/api/http.sock” to existing curl commands.
• Although not recommended, downgrading from 5.0.0 to a previous version will require a hard reset back to default settings. Very important to not downgrade when remote to the device or when using DeviceHQ (Remote Management) because access will be lost.
• On WiFi models, the Dashboard WiFi MAC address now matches the WiFi hardware instead of matching the Ethernet MAC Address. This was improper reporting on the Dashboard only, the WiFi hardware was correct.
• Because of additional GPS options, GPS may take longer to acquire satellites.
• IP Defense options, DoS Prevention, Ping Limit and Brute Force Prevention are Enabled by default.
• Under Adminstration > Access Configuration, SSH via LAN is disabled by default.
• For security, Telnet Radio Access and Telnet have been removed.
• The Clear History buttons have moved from Administration > Debug Options to the Ethernet, WiFi and Cellular tabs under Status & Logs > Statistics.
• GPS NMEA options default with GGA, GSA, GSV and RMC enabled and GLL and VTG are disabled.
• The code version has been removed from the log in screen, it is replaced with the new mPower^™ Edge branding.
• Dashboard banner and Firmware version includes “-AEP”, i.e. 5.0.0-AEP.

Known Behavior in 5.0.0

• User must be at version 1.6.4 (or newer) before upgrading to 5.0.0.
• Although not recommended, downgrading to a version before 5.0.0 will require a hard reset back to factory default settings.
• A Hard Reset (or Factory Default) will force 5.0.0 firmware into Commissioning Mode to create a new Administrative Username and Password.
• On LVW2, certain newer Verizon SIM’s do not support SMS. Contact Verizon.
• On LVW2, received SMS’s greater than 140 characters may be truncated to 140.
• Command AT+WS46 reverts to default after a power cycle which may affect a user that sets a non-default value.
• SMS Command API ignores 6 character password limit, does not fail if SMS is longer than 160 characters, has issues depending on location of spaces and can not view view/delete inbox/outbox.
• Nofications API can delete existing alerts, add new alerts, modify with non-existing group, add two groups with same name and generate email with bad characters.
• DHCP API can set invalid Gateway.
• With SMS Commands, the Whitelisted numbers may need to be updated to include a +, a 1, or full phone number. Send a test SMS to the device to confirm.
• Version 1 API call (/api/v1/whoami) does not respond.
• Connecting OpenVPN Tunnels, user is unable to open WebUI of remote device.
• Firmware upgrade may revert LoRa Network settings to default. Network Mode set to Private LoRAWAN may change to Public LoRaWAN. Rx2 Datarate to 8 for 915 cards and 0 for 868 cards. Rx1 Delay to 1. Join Delay to 1 for Private MTS or 5 for Public LoRaWAN. Additional Channels setting for KR920 and AS923 to 922.9 or 922.6, respectively. MaxEIRP and DwellTime Up/Down for AS923 to 0. WorkAround is to modify /var/config/db.json “__v”: 1 setting in “loraNetwork” collection to “__v”: 18 before the upgrade to avoid reverting. Otherwise modify the above settings after the upgrade.
• If using Remote Management and you perform a manual check in to Device HQ, your device may show two check in’s based on your Check In Interval.

1.7.4 (05/14/2019)

Bug Fixes

• In MTCDT AEP 1.7.3, it was identified that when the Ethernet cable was unplugged and plugged back in, the IP address would revert to the factory default setting (192.168.2.1) instead of the customer-defined IP address. This issue has been corrected.
• In MTCDT AEP 1.7.3, gpsctl occasionally fails to initialize the GPS module, so GPS information is not consistently sent. This has been corrected by downgrading gspd to an earlier and more reliable version (3.16) while continuing to use 3.18.1 libraries.

1.7.3 (04/18/2019)

Changes

• Changes were made to reduce noise during bootstrap, bootloader (u-boot), and kernel device tree on pins connected to the usb hub and GNNS module.

1.7.2 (03/15/2019)

Changes

• The LoRa Network Server has been updated to version 2.2.18.
• The LoRa v2.1 AES key is set by network server for accessing fine-timestamps for geolocation

Bug Fixes

• Fix: LoRaWAN Network Server – Send correct Channel Mask in first downlink for AU/US

1.7.0 (02/27/2019)

Changes

• The LoRa Network Server has been updated to version 2.2.6.
• The GPS functionality has been re-architected for better performance and consistency.
• Configurations downloaded from the device now no longer contain the AppManager.json file. That behavior was found to be problematic, causing App versions to possibly be incorrect.
• A radio reboot feature has been added to reboot the radio when ppp has been unable to connect after all backoff timers have been exercised or ping/tcp connect has failed for ~2 hrs.
• Custom Apps install was enhanced: back up the current app if one exists, and restore it if the new app install fails.
• Support for the MTAC-XDOT card has been added.
• LoRa: Dual Card Support has been added.
• LoRa: RU864 (864- 870 MHz)
• LoRa: Class B support
• LoRa: Class C Multicast

Bug Fixes

• The ICCID on the Radio Status Page has been added back in.
• Radio switching between AT&T and Verizon on the MTCAP models with the LNA3 radio has been fixed.
• A number of help links in the Web UI have been fixed including SMS Configuration.
• Custom Apps: Fixed a race condition between restoring Custom Applications and reboot in User-Defined-Defaults restore.
• SMS issues with international numbers have been fixed.
• LoRa Packet forwarder logs are disabled, the forwarder logging did not work well with logrotate

Known Issues

• LoRaWAN Network Server – US/AU channel plan sends ADR MAC command in first downlink after join that disables all channels. Devices that do not reject it will be silenced. mDot/xDot 3.1.0 with ADR disabled accepts the channel mask and is affected. (Update is pending to repair)

1.6.4 (11/29/2018)

Bug Fixes

• Fix remote management but related to GPS interval that prevents configuration of remote management on devices with no GPS capability

1.6.2 (08/29/2018)

Changes

• Built with Yocto 2.2 (Morty) and mLinux 4.0
• Radio FOTA for H5 and LTE radios
• Enable/Disable call home feature
• Monit added for custom application monitoring
• Back-up custom applications with user-defined-defaults
• Python support for MODBUS and SSL
• LDC3 Radio support
• Netfilter NFLOG, TRPROXY, XT_MATCH_IPRANGE and XT_MATCH_TIME in kernel
• Added libnetnfnetlink and libnetfilter-log to the mPower Conduit^® image to support applications
• Increased RSA cert length to 2048-bits
• SMS Commands
• Firewall – user chanins processed first
• DeviceHQ config upload controls
• OpenVPN Upgrade to v2.4.2
• Certificate upload support
• Bootloader login support
• LoRa Network Server v2.1.5
• Support for LoRaWAN Multicast
• Support for LoRaWAN FUOTA
• Combined LoRaWAN > Devices Configuration and Device Sessions
• Added LoRaWAN menu items
  • Devices
  • Device Groups
  • Profiles
  • Operations

Bug Fixes

• WAN fail-over dnsmasq now updates resolv.conf correctly
• LoRa Network Server downlink queue allows delete through UI, lora-query and MQTT
• Node-RED logs are not rotated
• Packet forwarder manual mode maintained on upgrade from 1.4.3

Known Issues

• GPS error when trying to enable Remote Management on non-GPS units. Workaround using API: https://192.168.2.1/api/remoteManagement?method=PUT&data={"accountKey":"<ACCOUNT-KEY>","enabled":true}

1.4.17 (07/16/2018)

Bug Fixes

• Fix for watchdog when restarted by update from DeviceHQ – it should not monitor api, ppp, or lora
• Fix for WAN manager to setup DNS resolve paths when interface changes are detected
• Firewall – Apply custom user rules first

Known Issues

• Packet forwarder manual mode is not maintained on upgrade from 1.4.3
• IN865: Rx2 frequency for downlink is not set by network server.
  • Workaround by fixing the Rx2 Frequency through the API
    • curl 127.0.0.1/api/loraNetwork -X PUT –data ‘{“lora”:{“rx2Frequency”:866550000}}’
    • curl 127.0.0.1/api/command/save_restart -X POST –data ”
  • If the channel plan is changed the Rx2 frequency setting should be unset
    • curl 127.0.0.1/api/loraNetwork -X PUT –data ‘{“lora”:{“rx2Frequency”:0}}’
    • curl 127.0.0.1/api/command/save_restart -X POST –data ”

1.4.16 (03/29/2018)

Bug Fixes

• Fix for some JoinEUI values creating invalid Join Accept messages to be transmitted
• Fix db migration from AEP 1.4.3/1.4.14 for lora database path

Known Issues

• IN865: Rx2 frequency for downlink is not set by network server.
  • Workaround by fixing the Rx2 Frequency through the API
    • curl 127.0.0.1/api/loraNetwork -X PUT –data ‘{“lora”:{“rx2Frequency”:866550000}}’
    • curl 127.0.0.1/api/command/save_restart -X POST –data ”
  • If the channel plan is changed the Rx2 frequency setting should be unset
    • curl 127.0.0.1/api/loraNetwork -X PUT –data ‘{“lora”:{“rx2Frequency”:0}}’
    • curl 127.0.0.1/api/command/save_restart -X POST –data ”

1.4.14 (03/21/2018)

Changes

• Increase the RSA key length in server.pem (the default self-signed certificate) to 2048 bits.
• Upgrade to wpa_supplicant 2.6
• Upgrade pyserial to version 3.4
• Display LoRa Server and Packet Forwarder versions in web UI.
• Be able to use the lora network server without a mtac-lora card installed
• Update Node-RED to version 0.15.3
• Add support for LDC3 radio
• Custom Apps: Update user defined defaults to backup and restore custom apps installed in /var/config/app. Custom Apps are not uploaded with configuration to Device HQ.
• Add libnfnetlink and libnetfilter-log to AEP 1.4.x and turn on CONFIG_NETFILTER_XT_TARGET TPROXY and NFLOG in kernel
• lora-network-server now version 2.0.18
• Add LoRaWAN Private mode for LoRaWAN compatible network using 0x12 syncword
• Restart lora services if a packet forwarder has not been seen in 10 minutes
• Class C scheduling up to 5 seconds out, instead of failing schedule call multiple times
• Set default join delay to 5 seconds, if null was provided OTA join was not possible
• Fix sample config file JSON error comma at end of list
• Add app port to application MQTT topic for up and packet_sent events
• Allow for application specific filtering such as Multicast or Multipart
  • mosquitto_sub -v -t lora/+/+/+/+
  • mosquitto_sub -v -t lora/<APP-EUI>/<DEV-EUI>/<APP-PORT>/<EVENT>
• PUT update to LENS cloud for end-device class, name, hardware or firmware version if changed on Conduit
• Add some time randomization for class C downlink rescheduling
• Fix for US/AU private mode Rx2, frequency was not correct
• Emit queue_full message if no room left, check of queue size was added before making a call to add the packet
• Lora:
  • show join request result description in hover over
  • statistics for dropped packets has changed
  • add gateway card info to packet forwarder config section
  • do not hide Command to restart lora services based on capabilities.
• LoRaWAN Changes
  • Removed Setup > Lora menu item
  • Added LoRaWAN menu group
  • Added LoRaWAN menu items
  • hide menu items if network server is not enabled.
  • Network Settings
  • Key Management
  • Gateways
  • Device Configuration
  • Device Sessions
  • Packets
  • Downlink Queue
  • Added restart lora services command to commands menu
  • Backup lora database before creating config download
  • Added Packet Forwarder mode configuration UI
  • Updated to Network Server to v2.0.11
  • Added multiple gateway support
  • Added LENS cloud join server support
  • Added LENS cloud statistics support
  • Command API updates to add devices, sessions and downlink packets
  • Added json output options
  • lora-query interface changed to pass commands to network server
  • MQTT event updates for applications

Bug Fixes

• lora-in node fix to reconnect if disconnected from MQTT broker
• Disabled logging on LoRa Packet Forwarder in forwarder only mode to prevent filling up /var/log
• Node-RED LoRa node fixes [IN002602] lora-out node UI cannot be overridden.
• Node-RED mCard and lora node fixes handling lora nodes and new rev of LoRa network server
• Support Portal Case #5084641: Device GPS position data not displaying
• dnsmasq: Starting too early causes it to point to stale empty resolv.conf file
• SNTP: SNTP server settings don’t transfer after device firmware upgrade
• WAN priority defaults after upgrade
• Logging: Setting Debug Options syslog level to INFO doesn’t allow INFO
• Make firmware upgrade error message stay displayed on mPower web UI
• Support #5085601: Lora networking disables if device config from template is used for device config upgrading
• lora packet forwarder does not run after clicking submit button
• ntp_sync: update to call ntpdate with both the -u and -b options
• Radio Firmware upgrade using mPower web UI fails
• Turn off Server Cert Validation in URLopener call for Node-RED app download
• network configuration: Cannot configure the eth0 interface with very restrictive subnet mask
• PPP up and down Verizon (ppp-check process was trying to use ppp0 before it was up – race condition)
• Help link broken for OpenVPN

Known Issues

• Some JoinEUI values sent in the OTA Join Request can cause an invalid Join Accept response, this is fixed in lora-network-server v2.0.19 which is available for download
  • 12-00-00-01-00-00-00-00 is an example value
  • If the last half of 4th byte is greater than zero and the first byte is less than 0x14 an invalid Join Accept may be created
  • If the last half of 4th byte is zero there is no issue with the remaining bytes of any value like this example
  • 12-FF-FF-F0-FF-FF-FF-FF
• Lora end-devices will not be saved over reboot for some configurations. See LoRaWAN > Network Settings > Database > Database Path set to /var/config/lora/lora-network-server.conf or click Reset To Default and reconfigure.

1.4.4 (09/29/2017, released for Conduit IP67 only)

Changes

• LoRa Network Server updated to 1.0.41
• Updates to radio-query and radio-cmd for support of new radios
• Upgrade from mLinux 3.3.6 to mLinux 3.3.12, including MTCDTIP support (mLinux Changelog)

Bug Fixes

• See mLinux fixes from mLinux 3.3.6 to 3.3.12 (mLinux Changelog)

1.4.3 (06/09/2017)

Changes

• Update OpenSSL to be in sync with the mLinux version of OpenSSL for backwards compatibility of applications.
• Update LoRa Network Server to version 1.0.31.  The latest version is available on multitech.net.

Bug Fixes

• Fixed SNTP feature upgrade to preserve non-default configurations.  This bug was introduced in AEP-1.4.1.
• Fixed eglibc memory leak with gethostbyname

Known Issues

• When upgrading to AEP 1.4.3 from a firmware level older than AEP 1.3.2 it is necessary to upgrade to AEP 1.3.3 first and then to AEP 1.4.3 in order to retain the LoRa configuration settings. If it does not matter whether the LoRa configuration settings are retained or not, then it is possible to upgrade from any firmware older than AEP 1.3.2 to AEP 1.4.3.
• Node-Red lora-in node may become disconnected from the broker and not connect again. Edit /opt/node-red/nodes/core/lora/lora.js and move the following code.

  client.subscribe(mqttTopic);

  To the inside of the ‘connect’ handler function.

      }).on('connect', function() {      
        node.log("Connected to MQTT for LoRa in node.");
        setStatus(node, "connected");                                  
        client.subscribe(mqttTopic);                                           
      })

1.4.1 (04/20/2017)

Changes

• WiFi AP and Client support
• Bluetooth IP and BLE support
• Custom Application installation in flash (SD Card no longer required)
• GNSS support (GPS NMEA support)
• WAN failover
• Ethernet Card support
• LoRa support for US915, AU915, and EU915 channel plans
• LoRa network server upgraded to version 1.0.26

Bug Fixes

• The app-manager utility now sets the environment variables correctly for the “Start reload” command after a config file install from Device HQ.
• The size of the fields for the rx_bytes and tx_bytes sent to Device HQ for Cellular stats has been increased and should support far larger values.
• A bug preventing disabling of the LoRa Network Server after it was enabled has been fixed.
• The Multi-Serial Node in Node-RED has been fixed so that RS-485 Half Duplex works and no longer continuously displays “disconnected”.
• The level of OpenSSL has been upgraded to 1.0.2k to address multiple CVE’s.
• An issue has been fixed where the DHCP client would not renew the lease on an Ethernet interface when cable was unplugged for a time and then plugged back in.
• The DHCP server gateway address now gets updated when the IP on the Conduit interface is changed.
• A bug when resetting to User Defined Defaults not working with non-default IP address has been fixed.
• Installing a custom application from Device HQ, deleting it on Device HQ, adding the app back on Device HQ, and then re-installing the app to the Conduit no longer shows two of the same application in the app-manager DB.
• A bug in the Inbound Forwarding Rule menu’s Input Filter Rule not showing the External IP address has been fixed.
• A bug has been fixed involving mPower set for 868, LoRa setting Rx 1 DR Offset drop down menu adds values after changes are submitted.
• A bug has been fixed involving LNS not sending LoRa downlinks with CRC disabled.
• A bug has been fixed involving AS923, join on Rx2 NS uses DR0.

Known Issues

• When upgrading to AEP 1.4.1 from a firmware level older than AEP 1.3.2 it is necessary to upgrade to AEP 1.3.3 first and then to AEP 1.4.1 in order to retain the LoRa configuration settings. If it does not matter whether the LoRa configuration settings are retained or not, then it is possible to upgrade from any firmware older than AEP 1.3.2 to AEP 1.4.1.
• There is limited support fro running Wi-Fi Access Point and Client Mode concurrently at 2.4GHz. When concurrent mode is configured, the channel is not configurable because the channel is restricted to be the same as the channel the Wi-Fi client mode gets. To perform a Wi-Fi scan for access points when Wi-Fi client is connected, all “Saved Wi-Fi Networks” must be disabled.
• It is not recommended to use Wi-Fi 5GHz in concurrent mode with Access Point and Client modes both enabled.
• The version of mLinux stated on the mPower Conduit firmware 1.4.1 is 3.3.5. The mLinux version contains every commit for mLinux 3.3.6 except the commit that updates the revision and got tagged. So, in essence it is the same as mLinux 3.3.6.

1.3.3 (11/17/2016)

Changes

Bug Fixes

• Leave Node-RED enabled on upgrade

1.3.2  (9/15/2016)

Changes

• Custom Application Support
• Configuration File Management for Custom Applications
• Partial Configuration Download
• LoRa network server upgraded to version 1.0.13
• LoRa Web UI changes adding ADR support
• Updated and new help content

Bug Fixes

• Fix: Add support for decoding GSM PDU encoding characters
• Do not set or allow setting LVW2 APN -> provider automatically sets APN
• ppp doesn’t connect after the SIM card is ejected and inserted again
• LEU1: Ping feature not working, increase ping data size due to provider/SIM limitation on minimum ICMP data size
• Diversity gets disabled on LTE models – Initial Setup Wizard was defaulting diversity to false for LTE models
• lora: query MTAC-LORA card frequency band on set defaults.
• lora_pkt_fwd logging is disabled, process can be run manually to debug issues

Known Issues

• Node-RED will be disabled after upgrading to 1.3.2, but you can re-enable it in the UI or through DeviceHQ (this will be fixed in the next release)
• With 868 MTAC_LORA card installed, LoRa Network Server configuration must be set to EU868 channel plan after update.

1.2.2  (6/8/2016)

Changes

• Upload LoRa stats to DeviceHQ
• Upload system logs to DeviceHQ
• Upload Node-RED application status to DeviceHQ
• Make Node-RED settings.js modifiable. You can now modify this file without it being overwritten each time node-red restarts.
• Add LoRa support for ADR (Adaptive Data Rate)
• Improve Node-RED serial card performance by 10x
• Added support for LTE radios
• Improve LoRa config UI
• Upgrade help content framework and theme
• Upgrade lora network server to 1.0.8

Bug Fixes

• Fix IE11 save & restart
• Fix LTE radio RSSI isn’t updated after removing antenna
• Fix only update system time in initial setup wizard if user is changing it
• Fix sms send truncation on C2 radio SMS messages
• Fix C2 receive SMS being truncated.
• Fix for sms: characters like @ $ not working on CDMA & LVW2 multi-part sms
• Fix Issue where “broken” tar files for apps were still “installing” the app though it could not run and was effectively broken.
• Fix for updating time in the initial setup wizard -> only updates time when user has changed it in the wizard.
• Fixed a bug in the jsparser that should resolve the DHCP lease expiration time issue.
• Add npm utility back in, got removed because openEmbedded moved npm utility to a different package than nodejs.
• Fingerprint assets (js/css) to fix caching issues
• Fix restart page to redirect to login.html instead of dashboard.html
• Remove password from lighttpd & api logging
• Fix don’t validate DHCP form if not enabled
• Fix app upload input fields too narrow
• Fix LTE PPP doesn’t work when SIM requires PIN
• Fix lora address range can’t be lowercase
• Fix redirect to login page after factory default goes to wrong IP
• Fix firewall rule description hover help not working
• Fix initial setup wizard: change to LAN lost when backing through wizard
• Fix sms characters = + and ` (but ` doesn’t work with all carrier combinations)
• Fix Remote Management – device not consistently checking into DHQ at scheduled interval
• Fix LoRa stats and nodes to DeviceHQ: reset appears to cause API to not return anything for node list on the Conduit.
• Fix when Node-RED restarted, serial streamer instances not getting killed
• Fix cases where firmware upgrade would fail
• Fix LoRa logging: lora-pkt-fwd-1.log not getting rolled and keeps on growing.

Known Issues

• lora-pkt-fwd-1.log still not being rotated. Will consume all RAM if unchecked.

1.1.2  (1/27/2016)

Changes

• Add LoRa Packet Forwarder Mode
• Upgrade Nodejs to 0.10.40
• Upgrade Node-RED to 0.11.1
• Make LoRa logging level configurable through the UI.
• Update Node-RED SMS node to use only HTTP instead of HTTPS to conserve memory.
• Change Node-RED log to always be /var/log/app/node-red.log
• Improve Time Configuration UI
• Improve Initial Setup Wizard
• Feature: On Install Apps page, change “options” to “actions” and use better icon.
• Add support for no-radio and LTE models.
• Add Node-RED LoRa out support for requesting ACKs and setting the LoRaWAN FPort
• Add Node-RED M2X node.
• Improve stability & UI of multi-serial card nodes in Node-RED. Remove option for DTR/DSR flow control and 5 and 6 data bit options.
• Add popup prompt if configuring lora network server without enabling it
• Update LoRa Network Server to 0.0.9-2
• Update LoRa packet forwarder to 1.4.1-r9

Bug Fixes

• Fix Node-RED gpio node error message
• Fix Node-RED sms UTF8 support.
• Fix can’t browse to Node-RED via WAN port.
• Fix sms to correctly handle characters like @ $ etc.
• Fix firewall – lost access to box after enabling NAT Loopback on Prerouting Rule
• Make default LoRa log level to be 30 instead of 100
• Fix “SIM card is locked. Requires SIM Pin” message after enabling Dial-on-Demand
• Fix can’t save default lora configuration
• Fix Save & Restart not red after adding fixed DHCP address
• Fix can’t add DHCP fixed address when using non-default subnet
• Fix can’t configure DHCP infinite lease time
• Fix can’t login to web interface with password containing ‘&’

Known Issues

• npm is no longer in this version (unintended), but will be added back in the next release.
• DHCP Server does not respond to requests if lease time is set to 11-13-47 or higher. Will be fixed in next release

1.0.33  (9/2/2015)

• First official release!

Default Console Login Credentials

• Username: root
• Password: root

Serial Debug Port

This section applies to MTCDT-xx-210L only.

The micro USB connector on the front of the device behind the removable panel provides a USB serial debug port. The debug port provides access to the bootloader (U-boot) and the Linux system console.

• Baud rate: 115,200
• Data: 8 bit
• Parity: none
• Stop: 1 bit
• Flow control: none

If the USB port isn’t recognized on your computer, download and install this driver: https://www.exar.com/content/document.ashx?id=1596

Ethernet

The built-in ethernet port is a 10/100 Mbps interface. Network configuration is defined in
/etc/network/interfaces.

Defaults:

• IP address: 192.168.2.1
• Subnet mask: 255.255.255.0

To change the static IP, change the address and netmask fields in /etc/network/interfaces (use vi or nano). To apply changes, either reboot the device or issue: ifdown eth0; ifup eth0.

To enable the DHCP server with default settings, issue: mlinux-dhcpd start. Configure the dhcp server by editing /etc/udhcpd.conf. You can also issue mlinux-dhcpd stop or mlinux-dhcpd restart.

Cellular

Cellular data/Internet access is provided by the PPP software.

To set up an H5 radio cellular data connection using default options:

# Set "APN" to the APN for your cellular provider
$ mlinux-set-apn APN

# Dial the connection (using /etc/ppp/peers/gsm config)
$ pppd call gsm

# Verify ppp0 is up
$ ifconfig ppp0
ppp0      Link encap:Point-to-Point Protocol  
          inet addr:33.140.12.18  P-t-P:33.140.12.18  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3 
          RX bytes:106 (106.0 B)  TX bytes:145 (145.0 B)

PPP daemon options are configurable in /etc/ppp/options and in peers files: /etc/ppp/peers/gsm

To reset the cellular radio in the case that the radio is unresponsive to AT commands:
$ mts-io-sysfs store radio-reset 0

The radio-query and radio-cmd scripts can be used to communicate with the radio using these soft links to the radio’s USB ports: /dev/modem_at0 and /dev/modem_at1.

LEDs

MTCDT

There are five software-controlled LEDs on the MTCDT hardware:

• led-status – default: status (solid during boot, flashes while running)
• led-a  – default: always off
• led-b  – default: always off
• led-c – default: always off
• led-d  – default: always off

MTCAP

• STATUS – default: blinks when operating system is fully loaded.
• LORA  – default: lights when LoRa software is active.
• CELL  – default: lights when there is power to the cellular radio. Cellular models only.
• WIFI – default: always off Wi-Fi models only.
• Ethernet Link  – default: always off

MTCDT and MTCAP

LED control using mts-io provides simple on/off functionality and gives the convenience of using the mts-io-sysfs script.

Examples

• Turn led-a on:

  $ mts-io-sysfs store led-a 1

• Turn led-a off:

  $ mts-io-sysfs store led-a 0

LED control using the linux leds-gpio driver gives advanced functionality in the form of triggers. Options:

• none: disable trigger (in order to use mts-io)
• nand-disk: NAND flash activity
• timer: custom LED flash timing
• heartbeat: default for led-status
• default-on: always on
• mmc0: SD card activity

Examples

• Show current led-status trigger:

  $ cat /sys/class/leds/led-status/trigger

• Change led-status to NAND flash activity:

  $ echo "nand-disk" > /sys/class/leds/led-status/trigger

USB ports

This section applies to MTCDT-xx-210L only.

Host port

This port is a USB 2.0 high speed port that functions as a host to any USB device, such as a flash drive, printer, etc. Linux driver support is required for any device attached to this port.

Device port

This port functions as a device connected to a host, such as your development PC. The USB gadget set of Linux drivers provides functionality for connected devices.

By default, this port is configured as a USB serial port (g_serial driver) with a serial login console that functions like the debug port.

This port’s functions can be customized as needed. For example, you can have the Conduit^® show up as a mass storage device on your PC. To change the gadget driver loaded on boot, edit /etc/default/usb-gadget-mode and change the USB_MODE variable. For USB_MODE available options, see /usr/bin/usb-gadget contents. To disable the serial console, edit /etc/inittab and comment out or delete the line starting getty on ttyGS0.

Reset button

The reset button on the MTCDT hardware interfaces to the mts-io utility. A reset button handler named reset-handler installs and starts on boot.

Default reset-handler behavior:

• Short button press (< 5 seconds): perform soft reboot
• Long button press (>= 5 seconds): reboot and restore default settings

mts-io attributes

• reset: show current state of reset button

  $ mts-io-sysfs show reset

• reset-monitor: show/set configuration of PID to signal on button press

  $ mts-io-sysfs show reset-monitor

  $ mts-io-sysfs store reset-monitor �500 10 12 1�

  PID=500, send SIGUSR1 (signal 10) on short press, send SIGHUP (signal 1) on extra long press

• reset-monitor-intervals: show/set the button press durations used by reset-monitor

  $ mts-io-sysfs store reset-monitor-intervals �5 30�

  Short press: < 5 seconds, long press: < 30 seconds, extra long press: >= 30 seconds

• Reset-handler uses the reset-monitor and reset-monitor-intervals attributes to configure mts-io and then waits for signals generated by a button press.

To customize reset button behavior, provide a custom version of reset-handler or disable it and install your own handler. See /usr/sbin/reset-handler for reference. To disable reset-handler from starting on boot, modify /etc/default/reset-handler and set ENABLED=�no�.

Micro-SD Card

This section applies to MTCDT-xx-210L only.

Cards inserted into the micro-SD slot are auto mounted at /media/card using device /dev/mmcblk0p1 (first partition on the device). Linux Ext2/3/4 and MSFAT file systems are supported by default. To change the mounting behavior, see /etc/fstab.

• By default, mLinux^™ mounts the SD card using the sync mount option. This flushes all writes to the physical card immediately. This can increase write times, but allows the writing application to know that the data is on the card when it is done writing. It also reduces the chances for filesystem corruption if the SD card is removed from the slot without unmounting it.
• To improve write performance, the SD card may be mounted with the async option instead. The performance cost of the sync mount option varies from card to card. Some cards gain a very large increase in throughput by using async instead of sync when mounting.
• To use the async mount option, modify the following line in /etc/fstab and remove ‘, sync ‘

  /dev/mmcblk0p1 /media/card auto defaults,sync,noauto 0 0

• After modification, the line should read:

  /dev/mmcblk0p1 /media/card auto defaults,noauto 0 0

Temperature Sensor

The MTCDT hardware includes an on-board TMP102 temperature sensor, which is accessed via the hwmon sysfs interface. Units are in millidegrees Celsius

Read current temperature:

cat /sys/class/hwmon/hwmon0/temp1_input