Jason Reiss
Forum Replies Created
-
AuthorPosts
-
Jason Reiss
KeymastermLinux configuration info
AEP see Setup > Lora page
The test setting disableRxWindow1 maybe useful to force the network server to always use Rx2.
KeymasterIn EU the Rx2 downlink channel 869.525 can use a higher power (27 dBm EIRP) than the 14 dBm EIRP limit of the rest of the 863-870 band.
The Rx2 Datarate is configurable in Conduit. The Join response will be sent in Rx2 at the LoRaWAN default.
The Rx2 window is a specific frequency and datarate and must be configured on the device, the datarate is sent to the device in OTA join response.
Rx2 settings are not configurable for a single device or downlink.
The best resources are the LoRaWAN specification directly from the lora-alliance or the Semtech reference implementation https://github.com/Lora-net/LoRaMac-node.
KeymasterThere is no fragmentation.
A packet that is too big will have to wait until an time it can fit in the downlink.Downlink payloads of 51 bytes for EU and 66 bytes for US can be sent at any datarate.
The Rx2 Datarate can be set to ensure a specific datarate.
Although there is then a trade-off of larger size for maximum range.KeymasterThere is no need to specify a datr field to a message sent to the network server. This field is provided by the network server on uplink packets received and downlink packets sent. The datarate used is determined by the LoRaWAN protocol and configuration of Rx1 and Rx2 settings.
KeymasterAny AppEUI/DevEUI can be used for ABP.
The DevEUI must be unique per device.KeymasterUnfortunately, I don’t see this issue getting resources in the near term.
KeymasterThe end-device should initiate a join once the 16-bit counter reaches 0xFFFF. Rolling the counter back to 0 would be reuse of counter values with same session keys.
Also in 4.3.1.5
The end-device shall not reuse the same FCntUp value, except for retransmission, with the same application and network session keys.
KeymasterIt appears that the lora-in node is lacking any “connectionlost” handling code.
The MQTT in/out nodes appear to be more robust in handling reconnects.
KeymasterYou can also attach a USB cable to the device port on the back to get a terminal.
Use minicom, teraterm or putty to connect with the serial interface.
http://www.multitech.net/developer/products/multiconnect-conduit-platform/conduit/connecting-to-the-debug-interface/
There is also a port behind the Multitech logo on the front, remove the screw slide the plate off.KeymasterSee definition of RadioEvent in Dot Examples.
https://os.mbed.com/teams/MultiTech/code/Dot-Examples/file/d80afce304c6/examples/inc/RadioEvent.h
KeymasterDid you follow this guide?
See Using the MQTT protocol directly
https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-mqtt-support
KeymasterThe system will use the id programmed into the MTAC_LORA card. To override the behavior the init script must be modified.
Edit /etc/init.d/lora-network-server
Replace line 132 with either of the following curl lines.
We will consider implementing the second option for future AEP release.# Remove the replacement out-right curl -m 5 -s "127.0.0.1/api/loraNetwork/lora/packetForwarderConfig" | jsparser -p /result > /var/run/lora/1/global_conf.jsonOR
# Replace only if a placeholder is found with angled brackets in gateway_ID field. Added <.*> between quotes \")[^\" curl -m 5 -s "127.0.0.1/api/loraNetwork/lora/packetForwarderConfig" | jsparser -p /result | sed "s/\(.*gateway_ID\"\s*\:\s*\"\)<.*>[^\"]*\(.*\)/\1${lora_eui_raw}\2/g" > /var/run/lora/1/global_conf.jsonKeymasterNot yet. It is on todo list.
KeymasterLooks like some of my message was filtered as HTML.
That is correct, each device queue must be cleared.
KeymasterThe lora-in and lora-out nodes are just wrappers around MQTT.
There are other message end-points available for control of the network server.
Send MQTT empty message to “lora/<DEV-EUI>/clear” to remove all queued packets. There is currently no command to remove or replace a single item.
There is also a UDP command port 6677 interface available
-
This reply was modified 7 years, 7 months ago by
Jason Reiss.
KeymasterUse the Rx2 Datarate setting.
This setting will be sent to the dot in OTA join response.
KeymasterYour latest example does not show a step of 2.
What is the AT+RSSI of received packet?
Perhaps a packet was missed.
You could test with RX2 datarate to 5 or 6, FSK is not as robust as LoRa.KeymasterThe lora-out node communicates to end-devices through network server over lora rf. The port field is application specific.
Ipv6 would be used to communicate with outside world via ethernet. An application (node-red) in conduit should be used to setup the external connection and forward packets to and fro.
No changes to lora config should be necessary as lora communication to application is local.
KeymasterThe latest version seems to be OK, no missed frames.
admin@mtcdt:/var/log# /opt/lora/lora-network-server –version
MTS Network Server – Version 1.0.37Have a look at the DOT logs too it will show all received frame counters.
[INFO] Packet Received : Port: 1 FCnt: 00000002 Size: 1 ACK: 0 DUP: 0KeymasterWhat versions are you running for xdot and lora-network-server?
Do you see the missing frame counter being sent in Conduit logs?
The counter will be sent from the network server, the dot will just display what was received.
KeymasterIn lora-network-server v1.0.32 the “database backup” command to the network server can be used to write the node database to flash. This database holds the node key information.
This backup will automatically happen hourly and on a soft reboot (shutdown -r now).
KeymasterWe are still working on a 3.x DOT BOX release.
The 2.0.x DOT BOX firmware would need the unit reconfigured.
Contact support.multitech.com to get the unit reconfigured for AU.
KeymasterReceived packets will not appear on command port unless in serial data mode.
A custom application on mDot may be needed to handle Class C received packets depending on your use-case.The following are commands to be used to see that Class C packets are received.
Enable logging to see packet being received in debug output
AT+LOG=6To show last packet received
AT+RECVTo show counter of last packet received
AT+DLCTo enter serial data mode
AT+SDTo exit issue +++
KeymasterUDP or MQTT can be used to receive and send lora messages through the network server.
A sample app using node.js is available here:
KeymasterSerial data mode in at firmware might meet your requirements.
KeymastermLinux lora recipes
http://git.multitech.net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-connectivity/loraSee lora-packet-forwarder-usb
Pre-built packages, match your mLinux version.
http://www.multitech.net/mlinux/feeds/3.3.7/arm926ejste/lora-packet-forwarder-usb_1.4.1-r10.0_arm926ejste.ipkKeymaster$ mts-io-sysfs show lora/product-id
MTAC-LORA-868
$ mts-io-sysfs show lora/hw-version
MTAC-LORA-1.0This card is a USB card and must use the /opt/lora/basic_pkt_fwd or gps_pkt_fwd binaries.
v3.x packet forwarder with V2 protocol is not available for USB cards.
V1 protocol is used in basic/gps pkt_fwdsKeymasterThe unique encryption keys referred to are the Session keys used after the join.
Best practice for overall security is unique AppKeys per device as you are trying to configure.
lora-query is the current way to configure unique appkeys per dev-eui.
Be sure that the app-eui configured with the dev-eui does NOT match the NetworkID assigned to the Conduit. Otherwise it will validate the join against the Network Key.If you need more help with lora-query please provide more detail of what you have tried and what is not working for you.
KeymasterAt+MAC=CMD
Send a mac command from server or inject mac command to change sessio n rx param per lorawan.
KeymasterDo save of configuration on original Conduit.
Administration > Save/Restore
Restore on new Conduit.
Or be sure the NetworkName/EUI and NetworkKey/Passphrase match on old and new boxesOn old conduit do
# /etc/init.d/lora-network-server stop
Then copy /var/config/lora/lora-network-server.db off the boxOn new conduit do
# /etc/init.d/lora-network-server stop
Then copy saved db file to /var/config/lora/lora-network-server.db
# /etc/init.d/lora-network server start -
This reply was modified 7 years, 7 months ago by
-
AuthorPosts