Jason Reiss
Forum Replies Created
-
AuthorPosts
-
October 31, 2017 at 8:49 am in reply to: Invalid MIC in mdot when the conduit is reset. Manual mode and Class C #21405
Jason Reiss
KeymasterSame issue as Conduit. Need to reset the downlink counter on the dot.
AT+DLC=0
Reusing/resetting counters is not best practice. OTA join is suggested.
KeymasterTry mosquitto_sub -v -t lora/+/joined
The message is blank, only a topic will be sent.
KeymasterThis is not a feature of the AEP LoRa software. The DevEUI is used to uniquely identify the end-devices.
To send packets with a specific DevAddr a device must be registered in the system with a DevEUI that maps to the DevAddr. Then queue packets using the DevEUI.
See ABP node registration commands.
KeymasterThe gateway can receive any lora packets sent on the configured frequencies.
If the lora packets employ the LoRaWAN protocol the payload will be encrypted, no information can be retrieved.
Only the payload header is available un-encrypted, it contains the network DevAddr, frame control and counter bytes, and optional mac commands.
Have a look at the protocol specification for more details.
You can request a copy at https://www.lora-alliance.org/lorawan-for-developersKeymasterI meant any firewall in-between. This is a regular fix for AEP models that configure a firewall to not allow in-bound traffic. Since you are running mLinux there is not firewall enabled by default.
KeymasterPacket forwarder will send lora packets as received.
A node will not be able to join or use encrypted data unless there is a network server between the packet forwarder and application, such as node-red.If you want the lorawan network server to handle the join and encryption of packets then you will want a service on the Conduit that forwards data to your remote Node-RED instance. Using Node-RED on the Conduit with Lora-in node connected to an HTTP/UDP/TCP out node to a HTTP/UDP/TCP in node on your remote machine would be a quick proof of concept.
The lora nodes on Conduit cannot be used off the Conduit. They are a wrapper over an MQTT client to pass messages to/from the network server. They do no lora packet processing on their own. The format MQTT messages to/from Base64 into strings or byte buffers for an application.
Later you may decide to create a custom app to handle the message passing.
Keymaster1. Rx1 should use DR0 only if the end device uplink was DR0. Since the end-device may not know the dwell-time setting until after an uplink it may be possible of the end-device to not receive a packet.
When you say you need to set the Rx1 window to DR0, what is the uplink DR?
2. The AS923 plan has 2 default channels. The Join Accept message sends down 5 additional channels. These are added to channel indexes 2-6.
Two more channels for DR6 and DR7 are send in the first downlink.
The channel 2 you are missing is 923.6 and the gateway is configured to listen on the is channel. The network server is not sending this channel at the moment, an additional MAC command will be needed.AT+TXCH
0 923200000 5 0 1
1 923400000 5 0 1
2 922200000 5 0 1
3 922400000 5 0 1
4 922600000 5 0 1
5 922800000 5 0 1
6 923000000 5 0 1
7 923400000 6 6 1
8 923900000 7 7 1KeymasterDid you open the port through the firewall?
KeymasterLooks like your settings will keep the device awake to Rx packets and output to serial. The device will keep waiting for data on serial. The only thing that breaks the loop is serial data.
If interested have a look at the implementation.
Line 486 for serial mode function.
Line 1308 for Packet Rx event.
https://os.mbed.com/teams/MultiTech/code/Dot-AT-Firmware/file/95c9eb69329a/CommandTerminal/CommandTerminal.cppKeymasterIf you want a simple behavior, mbed could be used to create a custom firmware.
KeymasterYour wake delay setting appears out
of range. I would expect 200-2000, is is measure of ms between wake up and start of data on serial port.-
This reply was modified 7 years, 6 months ago by
Jason Reiss.
KeymasterIf interested in raw packets, the Conduit uses Semtech packet forwarder.
Protocol of Packet Forwarder to Network Server is detailed here:
https://github.com/Lora-net/packet_forwarder/blob/master/PROTOCOL.TXTSource is found here:
https://github.com/Lora-net/packet_forwarderYou can run just the packet forwarder from the /var/run/lora/1 directory.
# /etc/init.d/lora-network-server stop
# cd /var/run/lora/1/
# ./lora_pkt_fwdKeymastermin/maxDatarate: null settings is the issue.
Set min to 0.
Set max to 3 or 4 for DR3 or DR4.Ignore the US and EU min/max settings.
KeymasterBesure to use the network server in public mode.
I would debug the rx in the end device.
Look at mqtt output from network server to see response packet freq and datr. Be sure end device settings and timings match.
KeymasterLooks like mqtts is not available on Conduit.
Have you looked at using the REST API?
https://docs.microsoft.com/en-us/rest/api/iothub/KeymasterFILE* fd = popen(“mts-io-sysfs show device-id”, “r”);
// Read the command result from the FILE pointer
pclose(fd);
KeymasterFirst read the AT Command Guide, this will give you an overview of capabilities in software.
https://www.multitech.com/documents/publications/manuals/s000643.pdfYou will should be able to get xDot and mDot to communicate with AT Firmware.
Source for AT Command Firmware will provide implementation for each command using the libmDot library.
https://os.mbed.com/teams/MultiTech/code/Dot-AT-Firmware/Then when you are ready to code your solution, use the provided libraries.
https://os.mbed.com/teams/MultiTech/code/libxDot-mbed5/
https://os.mbed.com/teams/MultiTech/code/libmDot-mbed5/KeymasterConfigure the conduit for packet forwarder mode, this will send lora packets to a remote server or local UDP ports. The source project for the packet forwarder has good documentation on LoRaWAN network architecture.
https://github.com/Lora-net/packet_forwarder
https://github.com/Lora-net/packet_forwarder/blob/master/PROTOCOL.TXTAEP setup for packet forwarder.
Setup packet forwarder to send to uplink packet so a UDP port on localhost. This local port can be setup in Node-RED with a UDP in node.
KeymastergetTxDataRate() is the one stored in configuration in NVM
Check getSessionDatarate() for the datarate in use.
KeymasterPlease open a case at support.multitech.com. Our support engineers will walk you through the setup to flash your Conduit.
KeymasterNot all npm nodes are able to be installed directly on Conduit using npm.
Only nodes that are pure js, any c/c++ dependencies need to be cross-compiled into the system using mLinux.
Even then they must have support for node.js installed on Conduit, the current hardware is limited to supporting up to node.js v0.10.40.I still think using MQTT to connect to the IOT hub will be your best option.
What issues are you having with connecting with MQTT?
Can you get it to work first with a PC install of node-red through MQTT?KeymasterPre-built mLinux images are found on the downloads page.
The factory image will have all the pieces you need.Network setup info can be found here.
October 9, 2017 at 8:58 am in reply to: Can Fearther RFM9x LoRa module be used as an end node with conduit gateway #21140KeymasterThey both employ LoRa modulation in hardware communication between them should not be impossible.
October 9, 2017 at 8:46 am in reply to: Can Fearther RFM9x LoRa module be used as an end node with conduit gateway #21138KeymasterThe link you provide seems to provide the information you are looking for. Sounds like the feather has a steep learning curve.
LMIC has a base LoRaWAN implementation, it is not full featured it should work for some things. The LMIC project does not appear active in adding features either.
Multitech mDot and xDot are also programmable modules with a LoRaWAN certified stack available.
October 9, 2017 at 7:41 am in reply to: Connecting external gateway / packet forwarders to the AEP #21136KeymasterIt is experimental feature in current software.
Also connecting a gateway to multiple network servers may run into problems.
A device cannot join both via OTA and only one should be used for downlink.October 9, 2017 at 7:33 am in reply to: Can Fearther RFM9x LoRa module be used as an end node with conduit gateway #21135KeymastermDot and xDot are LoRaWAN certified. Conduit will work with other certified devices, Public mode on Conduit may need to be enabled to work with some.
October 8, 2017 at 5:30 pm in reply to: Connecting external gateway / packet forwarders to the AEP #21127KeymasterKeymasterLook for conduit mlinux convert to packet forwarder article in lora software.
KeymasterYou’re right. 66 is the maximum packet size with header info for DR8.
This is the N value (53) plus 13 bytes for header and MIC.Just to clarify the EU info too. 51 bytes is payload size without header and MIC. 64 bytes is max packet size for DR0-SF12BW125.
Keymaster51 is at SF12BW125
66 is at SF12BW500NA downlinks use 500kHz.
-
This reply was modified 7 years, 6 months ago by
-
AuthorPosts