[Jason Reiss]

Network configuration and Device Provisioning information is in db.json, DevEUI and AppKeys.
Session keys are in lora-network-server.db

lora-network-server.conf is created from configuration in db.json.

[Jason Reiss]

Everything looks to be functioning.

There are no other running processes using the card.
$ ps aux | grep lora

Please open a ticket at support.multitech.com.
We may need to share a packet forwarder binary with lower level debug messages enabled.

The lgw_start function is not returning OK.
https://github.com/Lora-net/lora_gateway/blob/master/libloragw/src/loragw_hal.c

[Jason Reiss]

Can you try these gateway utilities?

cd /opt/lora/gateway-utils

./test_loragw_spi
./util_spi_stress

[Jason Reiss]

What is the result of toggling creset and reading cdone through mts-io-sysfs?

[Jason Reiss]

Try to reset the card via command line and start the packet forwarder manually.

[Jason Reiss]

The LoRaWAN > Network Settings page should display the FPGA version.
If it is showing 255 then the system was not able to read the version info from the FPGA.

See sections 5.1.4 to see that the FPGA is accessible via SPI.

Search Results

[Jason Reiss]

Best practice is to use unique keys per device on Key Management page of Conduit.

Sharing the appkey can lead to false joins if two device send requests at the same time on same channel. They will both receive a join accept with a valid MIC. Only one will have valid sessions keys unless both chose same DevNonce. If same devnonce they both have the same session keys.

[Jason Reiss]

Network ID -> AppEUI transformation?

[Jason Reiss]

Did you try the upgrade after a reboot?

[Jason Reiss]

See AEP 1.7.2 or mLinux 4.1.6 on downloads page to use gpsd for time sync and packet forwarder timestamps.

[Jason Reiss]

That looks like a lot of dependencies for installing an MQTT or HTTPS wrapper.

What is the issue using the provided MQTT or HTTPS nodes?

node-red and node.js versions cannot be updated, beyond what is already provided, on current Conduit hardware.

https://www.leverege.com/blogpost/lorawan-node-red-deployment-tips-part-ii

Even better, use fewer resources by using C/C++.
https://github.com/Azure/azure-iot-device-ecosystem/blob/master/get_started/mlinux-multiconnect-conduit-c.md

[Jason Reiss]

Looks like flash was erased.
Go to https://support.multitech.com

[Jason Reiss]

AEP 1.7.0 has improved ADR over 1.6.2.

The network server will need a minimum of 6 packets before sending an update.
The network server will assign a DR to each of the last 11 packets based on SNR. If a DR has 6 packets assigned and is higher than the current DR an LinkADRReq is sent, unless a request has been sent in the last 4 packets.

The ADR packets tracking is always occuring. So if a device as ADR bit unset and sends several uplinks. It can get a LinkADRReq on the first downlink after setting ADR bit.

Also it will send an update every four packets if lowering the power at max DR until SNR is below 3 dB or min Power is reached.

[Jason Reiss]

Profiles can be defined on the LoRaWAN > Profile page.
The LW102-* profiles are provided as examples.

If a device is set to MAC Version: 1.0.3 a DeviceTimeAns should be sent in the first downlink after join or when DeviceTimeReq is received.

mLinux and AEP use the same network server.

Looking at mqtt output on Conduit I see if a 0x0D is received a response is sent. The device profile should not matter.

admin@mtcdt:~# mosquitto_sub -v -t lora/+/+                                                                                     
...                                                                                                       
lora/00-80-00-00-00-00-c9-54/mac_recv {"appeui":"16-ea-76-f6-ab-66-3d-80","deveui":"00-80-00-00-00-00-c9-54","gweui":"00-80-00-00-a0-00-15-8e","id":13}                                                                                                         
...
lora/00-80-00-00-00-00-c9-54/mac_sent {"appeui":"16-ea-76-f6-ab-66-3d-80","deveui":"00-80-00-00-00-00-c9-54","gweui":"00-80-00-00-a0-00-15-8e","opts":"0db10cb54996"}                                                                                           

[Jason Reiss]

What version of AEP are you testing?

LoRaWAN 1.0.3
Section 1.2
The octet order for all multi-octet fields is little endian

The channel mask in LinkADRReq is sent little endian.

[Jason Reiss]

cron will not survive an upgrade
A custom app could be used to install them after upgrade.

Creating a Custom Application

OpenVPN is available on AEP
http://www.multitech.net/developer/software/aep/openvpn/

[Jason Reiss]

Details are found in mLinux documentation. AEP is built on mLinux so these low level details also apply.

A firmware upgrade will overwrite only the kernel and rootfs partitions.

Flashing mLinux Firmware

[Jason Reiss]

Using an SD card is another option if more space is needed.

[Jason Reiss]

There are two partitions that are untouched on upgrade.
/var/config
/var/oem

admin@mtcdt:/var$ sudo df -h                                                                                                    
Filesystem                Size      Used Available Use% Mounted on                                                              
/dev/root               232.0M    104.9M    127.1M  45% /                                                                       
devtmpfs                115.2M      8.0K    115.2M   0% /dev                                                                    
tmpfs                   123.3M    444.0K    122.9M   0% /run                                                                    
tmpfs                   123.3M      2.7M    120.7M   2% /var/volatile                                                           
/dev/mtdblock6            8.0M      5.9M      2.1M  74% /var/config                                                             
/dev/mtdblock7            8.0M    528.0K      7.5M   6% /var/oem

• This reply was modified 6 years, 2 months ago by Jason Reiss.

[Jason Reiss]

Power can be reduced.

[Jason Reiss]

AT Firmware does not have a setting to allow this.

Using the library it is possible to disable datarate hopping for joins.

dot->GetSettings().Test.DisableRandomJoinDatarate = lora::ON;

• This reply was modified 6 years, 2 months ago by Jason Reiss.

[Jason Reiss]

Did you register the device appkey on key mgmt page?

[Jason Reiss]

Search Results

[Jason Reiss]

The to 7 bits of the DevAddr are reserved for the NETID signature 7 least-significant-bits. The range is then limited to 0x01 – 0x01FFFFFE by the network server, Unfortunately the UI does not impose the same limitations.

The 0x20000001 value is above the maximum and only one address is available.

[Jason Reiss]

Downgrade does not keep database tables consistent. Need to factory default after downgrade or upgrade back to 1.7.0

[Jason Reiss]

Have you modified the Address Range Start or End values?

[Jason Reiss]

This will require a firmware update to reset.
Please open a case at support.multitech.com to receive the image and instructions.

[Jason Reiss]

Here is a link to the source for AT+ULC
https://os.mbed.com/teams/MultiTech/code/Dot-AT-Firmware/file/95c9eb69329a/CommandTerminal/CmdUplinkCounter.cpp/

[Jason Reiss]

Are you asking how to set uplink counter using the library?
Did you search the mDot.h header file for a function?

[Jason Reiss]

Reboot is not needed. Only to set AT+ULC=0 on the transmitter.

[Author]

Posts