[Jason Reiss]

Base code for the packet forwarder
https://github.com/Lora-net/packet_forwarder

ETSI regulations
http://www.erodocdb.dk/docs/doc98/official/pdf/rec7003e.pdf

The MTAC_LORA card has two front end radios.
Each configured for a single frequency.

The 8 demodulators are configured with an offset in “chan_multiSF_0” – “chan_multiSF_7” configuration “if” setting. These are the 8 channels.
Offsets can be up to 500k off the center channel.

[Jason Reiss]

Is lmic code in 64 channel mode?
Conduit can only receive on 8.

[Jason Reiss]

Using node-red one could use a mqtt listener subscribed to lora/+/+ to get all messages from the network server.

In the lora configuration page the network server can log to a file instead of syslog. Set log level up to trace or maximum for the most output.

Access the log through an ssh connection to the conduit or via node-red using a tail node with the file location connected to a debug node.

This code will read from mqtt and a /var/log/lns.log file.

[{"id":"833b749b.e3f0f8","type":"mqtt-broker","broker":"localhost","port":"1883","clientid":""},{"id":"6f3bd636.e3358","type":"debug","name":"","active":true,"console":"false","complete":"true","x":647,"y":208,"z":"d4e998f8.a27b","wires":[]},{"id":"726b607d.1fd1d","type":"mqtt in","name":"","topic":"lora/+/+","broker":"833b749b.e3f0f8","x":395,"y":103,"z":"d4e998f8.a27b","wires":[["6f3bd636.e3358"]]},{"id":"cee8454f.de77b8","type":"tail","name":"","split":true,"filename":"/var/log/lns.log","x":504,"y":47,"z":"d4e998f8.a27b","wires":[["6f3bd636.e3358"]]}]


[Jason Reiss]

— Suppose, i want Mdot to transmit at channel 865.2, 865.5, 865.8, 866.10, 866.40 only and receive window at frequency 866.70 or 867 only. How would i configure this ?

Changing RX would require a custom channel plan on mDot and Network Server side. There is not loraWAN defined plan to accomodate this.

Default channels cannot be changed. They can be disabled using AT+CHM

Setting AT+CHM mask will change the output from AT+TXCH which shows the enabled channels.
This will enable the 3-7 and disable 0-2
AT+CHM=0,0F80

[Jason Reiss]

A defined broadcast address and session key set would be insecure.

With class C mode all devices should be listening on RX2 Frequency/DR already.

I don’t know what nodes you are using and what support is available for multicast on them.

[Jason Reiss]

A multicast message would require a shared session between end-points.

An ABP device could be registered in the network server and used as a mulitcast address. The net address and session keys would then need to be shared with each device. The end-device would need the ability to accept alternate addresses and authenticate with session keys.

[Jason Reiss]

If you want to use Conduit in packet forwarder mode then you will need network server software on the server.

https://github.com/TheThingsNetwork/

Otherwise the lora network server in the Conduit can be used to handle the network session.

[Jason Reiss]

Also, at DR0, 50 bytes payload will take 2.5 seconds to transmit.

[Jason Reiss]

P2P uses a single channel.

869.525 can use 10% duty-cycle
869.7-870 can use 100% if erp < 7dBm Setting for 100% duty-cycle At+txf=869850000 At+txp=4 At+ant=3 http://www.erodocdb.dk/docs/doc98/official/pdf/rec7003e.pdf

[Jason Reiss]

AT+TXCH will modify the channels in the session.
You can save the session with AT+SS and restore with AT+RS after reset.
Uplink and downlink counters are also saved with the session.

[Jason Reiss]

The built-in help displayed via the ‘?’ button has answers to some of these.

https://192.168.2.1/help/index.htm#t=Configuring_your_device/LoRa_Network_Server_Configuration.htm

[Jason Reiss]

LoRa Network Server

Address on each side must match.

char DEVICE_ADDR[] = “05060708”;

lora-query -a 05060708 A …

[Jason Reiss]

https://www.google.com/search?q=aep+vs+mlinux&ie=utf-8&oe=utf-8

[Jason Reiss]

From LMIC code EU868 has the following channels defined.
If these channels are not modified there will be a mismatch causing packet loss.

// Default frequency plan for EU 868MHz ISM band
// Bands:
// g1 : 1% 14dBm
// g2 : 0.1% 14dBm
// g3 : 10% 27dBm
// freq band datarates
enum { EU868_F1 = 868100000, // g1 SF7-12
EU868_F2 = 868300000, // g1 SF7-12 FSK SF7/250
EU868_F3 = 868500000, // g1 SF7-12
EU868_F4 = 868850000, // g2 SF7-12
EU868_F5 = 869050000, // g2 SF7-12
EU868_F6 = 869525000, // g3 SF7-12
EU868_J4 = 864100000, // g2 SF7-12 used during join
EU868_J5 = 864300000, // g2 SF7-12 ditto
EU868_J6 = 864500000, // g2 SF7-12 ditto
};

[Jason Reiss]

What channels is your client set up to use? Do you use OTA join?

Conduit will listen on 868.1,868.3,868.5, 869.1,869.3,869.5,869.7,869.9 with your settings.

[Jason Reiss]

Configure the network server to log to a file.

Network Server Logging
Log Destination: FILE
Path: /var/log/lns.log
Log Level: MAXIMUM

Then see if the log shows more clues.

[Jason Reiss]

Mandatory:
msg.eui = “70-b3-d5-9b-a0-00-0f-1b” ;
msg.payload = “x”;

Optional:
msg.port = 1;
msg.ack = false ;

[Jason Reiss]

If everything has to be the same then there is no way to filter on a specific dot outside of an id in the payload.

You seem to understand the network protocol. Now you need to implement an application protocol on top.

When multiple devices are connected in peer-to-peer it is equivalent to a ring network. All devices hear every message.

However peer-to-peer was designed as point-to-point so there may be issues with counter values from each end-point matching each other.
The device will filter out (drop) packets that have the same counter as the last packet received.

AT+ULC and AT+DLC can be used to save and show the counter values.
AT+SS and AT+RS can be used to save the counters in the session to flash.

[Jason Reiss]

You have three dots addressed as 1, 2, 3

for 2 to send to 1

AT+NA=1
AT+SEND=DATA
AT+NA=2

[Jason Reiss]

Under what circumstances?
The lorawan layer may be busy with TX or RX.

[Jason Reiss]

For peer to peer mode you set the devices to the same settings.

The following settings must match:
AT+NA
AT+NSK
AT+DSK

AT+NA (Network Address) can be different on each device.
Set the AT+NSK and AT+DSK to the same values.

Then only AT+NA needs to be changed to address a specific dot.

[Jason Reiss]

npm ERR! network getaddrinfo ENOTFOUND
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.

Is the device connected to the internet?

Does this command succeed to resolve the address?
> nslookup google.com

[Jason Reiss]

Configure two dots with different addresses and change the address before sending the packet.

[Jason Reiss]

Supply an empty message

[Jason Reiss]

If ack is set the network server will hold the payload until confirmation of packet receipt from the device.

If an uplink is received without the ACK bit set then the same packet will be sent to the device again.

This behavior will continue until ACK is received or the queue is cleared.

[Jason Reiss]

Did you enable public compatibility mode?

“network”: { “public”: true, … }

[Jason Reiss]

Conduit mLinux: LoRa Use With Third-Party Devices

There is a command port

# nc -u localhost 6677
config

[Jason Reiss]

See nodeQueueSize in advanced configuration. Some have found it better to set the network server queue to one rather than manage two queues. Only the size is configurable.

Getting Started with LoRa Conduit mLinux (LoRa Configuration)

Conduit mLinux: Advanced LoRa Configuration

[Jason Reiss]

do you have ack enabled in the lora-out node?
If it is on then the network server may be waiting for ACK from the device.

[Jason Reiss]

It is a custom MTS patch that adds this.
The packet forwarder is expecting the packet to be TX’d within 200ms.
The packet may be transmitted after the 200ms wait, so this message may be a false positive.

http://git.multitech.net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-connectivity/lora
http://git.multitech.net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-connectivity/lora/lora-packet-forwarder-usb/lora-packet-forwarder-add-queue.patch

[Author]

Posts