[Jason Reiss]

Doc for mbed 5 can be found here.

https://os.mbed.com/docs/latest/reference/ticker.html
https://os.mbed.com/docs/latest/reference/timeout.html

[Jason Reiss]

Yes that is correct.

[Jason Reiss]

The DETAILS.TXT file is in the flash of the programming module on the developer board. The mDot software does not have access to it.

The boot loader can be used to send a file from the flash to a PC over serial. The file name will have ‘u_’ prepended to the name you have assigned through code.

The bootloader is accessed through the debug port.
https://os.mbed.com/teams/MultiTech/wiki/updating-firmware-using-MTS-bootloader

Available commands:
help: display this message
boot: start user application
upgrade : upgrade to new firmware transferred over serial
transfer : transfer new firmware over serial, but don’t flash it
recv simple : read file into the filesystem over serial
recv ymodem [filename]: read file into the filesystem over serial
send : send file from the filesystem over serial
flash: flash new firmware that has already been transferred
reset: perform a soft reset of the system
delete : delete the specififed file from the filesystem
erase: erase entire 2MB external flash – BE SURE YOU WANT TO DO THIS!

[Jason Reiss]

You could implement a blacklist using an application

In node-red use MQTT in and out nodes with a function node between.
This code will clear the join accept packet out of the downlink queue.

if (msg.topic.search("<BLACK-LISTED-EUI>")) {
    msg.topic = msg.topic.replace("joined", "clear");
    return msg;
} else {
    return null;
}

[Jason Reiss]

I suggest you go back to start.

Download the aep upgrade file

Downloads

Go to Admin > Firmware Upgrade

This will reset the file system.

[Jason Reiss]

Do you use unique keys per device in the whitelist or the same key?
Both Conduits are configured for same NetworkEUI/AppEUI and NetworkKey/AppKey?
End-devices are configured same NetworkEUI/AppEUI and NetworkKey/AppKey?
Can end-devices use different AppEUI or AppKey?

[Jason Reiss]

When a duplicate is detected the FCNT value is not reporting correctly in this version of network server. It is an uninitialized value.

In the next release of network server, the value is initialized to FFFFFFFF which may show in the FCNT if the packet cannot be authenticated.

In the server update when a duplicate is received the FCNT will be set correctly.
|CHECK-PKT|FCNT: 00000002 LAST-FCNT: 00000002 Duplicate: yes

Although the enableStrictCounterValidation is set to false, the network server will still filter out duplicate messages from being reported to the application. So if the end-device is sending 0 repeatedly the payloads are not forwarded to the application.

[Jason Reiss]

Looks like that state is temporary.

INFO: Disabling GPS mode for concentrator’s counter…
INFO: host/sx1301 time offset=(1518963007s:43415µs) – drift=-622µs
INFO: Enabling GPS mode for concentrator’s counter.

[Jason Reiss]

FCC regulation allows a hybrid mode for FHSS devices using DTS for 8 channel operation. It is discussed how FCC Part 15.247 includes this mode of operation in this manual.
https://www.semtech.com/uploads/documents/an1200.26.pdf

Below is an excerpt from the LoRaWAN Regional Parameters.

— LoRaWAN Regional Parameters 1.0.2 Section 2.2.2
Hybrid mode, which requires that the device transmit over multiple channels (this
may be less than the 50 channels required for FHSS mode, but is recommended to
be at least 4) while complying with the Power Spectral Density requirements of DTS
mode and the 400 msec dwell time of FHSS mode. In practice this limits the
measured conducted power of the end-device to 21 dBm.

For the issue of Radiated Emission tests and Field Strength tests please open a ticket at support.multitech.com to discuss with our certifications team.

[Jason Reiss]

https://github.com/Lora-net/packet_forwarder

If you are still having issues getting time from all gatways through ttn you may want to setup a UDP server to recieve directly from packet fowarders.

[Jason Reiss]

looks like you have it configured correctly and get gps data

what sort of logging happens when you run manually, as described in the above 12:41 pm post.

$ ./lora_pkt_fwd

you can also forward the packets locally to “127.0.0.1” and listen with netcat

$ nc -u -l -p 1700

See what info is in packets going to TTN. After that it is up to TTN to handle the time info once it is forwarded.

[Jason Reiss]

Do you have a USB or SPI MTAC-LORA card?

For USB the gps_pkt_fwd-usb must be used.

$ cd /var/run/lora/1/
$ ls -lah
$ /etc/init.d/lora-network-server stop
$ ./lora_pkt_fwd

A work around could be to modify the /etc/init.d/lora-network-server script.
Change basic_pkt_fwd-usb to gps_pkt_fwd-usb near line 56

ln -sf /opt/lora/basic_pkt_fwd-usb $pkt_fwd
to
ln -sf /opt/lora/gps_pkt_fwd-usb $pkt_fwd

[Jason Reiss]

Without the packet forwarder running can you get data out of the /dev/ttyXRUSB2

Try to read the GPS device
> cat /dev/ttyXRUSB2

Depending on the TTN packet forwarder installed you will have to reach out the maintainer of the code to get support for issues.

Perhaps you are using this version?
https://github.com/kersing/packet_forwarder

[Jason Reiss]

Disable ACK
AT+ACK=0

Disable waiting after Tx for Rx Windows
AT+TXW=0

This will allow sending faster than normal.

To enable waiting for Rx windows
AT+TXW=1

Set on a single frequency, this setting will not be sticky when saved with AT&W and AT+NJM is not peer to peer, if the device is reset then AT+TXF will need to be issued again.
AT+TXF=902300000

Reset to frequency hopping
AT+TXF=0

AT+CHM can also be used to reduce channel usage by modifying the enabled channels mask.

[Jason Reiss]

LoRa Network Server

[Jason Reiss]

When you upload either binary?

[Jason Reiss]

Did you compile the example project as is or try to integrate with your own project?

Can you get the example project to work without modifications?

[Jason Reiss]

Here is another example.

https://os.mbed.com/users/jreiss/code/mDotFilesExample/

[Jason Reiss]

Yes that is the risk of using the same AppKey configured on end-devices.
It allows convenience of configuration at the expense of some security.

Our next AEP version will bring out the configuration of unique keys for end-devices to the UI.

[Jason Reiss]

Glad to help Pete.
If you ever need more timely support, our support portal is also available to customers. support.multitech.com

[Jason Reiss]

Can you compile and try this example on your mDot?

https://os.mbed.com/users/jreiss/code/BackupRegisterExample/

[Jason Reiss]

I think it is working although your check fails because it is expecting MDOT_OK to be returned.

MDOT_OK is defined as 0 and is equivalent to false.
The check is printing failed if 0 is NOT returned.
In the success case true will be returned which is definitely not 0.

From mDot.h the backup register functions are declared to return a true or false value
https://os.mbed.com/teams/MultiTech/code/libmDot-mbed5/file/mDot.h/

bool writeUserBackupRegister(uint32_t reg, uint32_t data);
bool readUserBackupRegister(uint32_t reg, uint32_t& data);

• This reply was modified 7 years, 4 months ago by Jason Reiss.

[Jason Reiss]

See these projects on mbed

https://os.mbed.com/users/dudmuck/code/?page=3

https://os.mbed.com/users/dudmuck/code/sx127x_simple_TX_mDot/
https://os.mbed.com/users/dudmuck/code/sx127x_simple_RX_mDot/

[Jason Reiss]

Sorry, there is not a command to send raw LoRa packets in the AT firmware or libmDot libraries.

Closest thing would be to set in MANUAL mode
AT+NJM=0

The ADDR can be set with
AT+NA=00112233

Uplink counter can be adjusted with
AT+ULC=1

And disable encryption of the payload
AT+ENC=0

The header and MIC will still be in the packet

[Jason Reiss]

Here are the end-points for the REST API

Conduit mPower API

Here are some curl examples, these are easier to show than a node-red flow. Should not be too much work to port node-red.

# curl 127.0.0.1/api/ni/nis/0 -X PUT --data '{"MAC":"00:08:00:4A:1E:AF","available":true,"bridge":"--","ipv4":{"dns1":"172.16.0.20","dns2":"", "gateway":"172.16.0.1", "ip":"172.16.0.182","mask":"255.255.255.0","mode":"STATIC"}, "name":"eth0","nitype":"ETHER","type":"LAN"}' -H "Content-Type: application/json"

# curl 127.0.0.1/api/loraNetwork -X PUT --data '{"network":{"name":"NEW-NAME"}}' -H "Content-Type: application/json"

# curl 127.0.0.1/api/command/save_restart -X POST --data '' -H "Content-Type: application/json"

• This reply was modified 7 years, 4 months ago by Jason Reiss.

[Jason Reiss]

What is not working?

sleeptime != sleep_time

[Jason Reiss]

There is no message in the protocol for an end-device to send to the network server to change class.

This will need to be an application level message.

An application can listen for Joined messages and change new devices to class C as the records are created.

[Jason Reiss]

We have no plans in the near term. This would be a lower level change that we can look into for a future release.

Thanks for the feedback.

[Jason Reiss]

There is a setting in the packet forwarder that can be enabled to quit the packet forwarder if the network server cannot be reached after a series of “keepalive_interval” checks.

Add this setting to the “gateway_conf” section to enable the autoquit
“autoquit_threshold”: 30

On AEP the angel process will restart the packet forwarder after it quits.

We are updating our examples to include this setting.

[Jason Reiss]

When a network name is provided, the AppEUI is created by preforming crc64 to get a 64-bit EUI.

Otherwise the 64-bit value can be used directly in mDot and Conduit as AppEUI.

[Author]

Posts