Jason Reiss
Forum Replies Created
-
AuthorPosts
-
Jason Reiss
KeymasterIf you want to see a source code example of a LoRaWAN client, one is available from Semtech.
https://github.com/Lora-net/LoRaMac-nodeKeymasterThe session information is maintained by the library.
If you want to read the current settings you could access a pointer to the structures through this function in the mDot class.
lora::Settings* getSettings();
KeymastergetNetworkAddress() and setNetworkAddress() access the 4-byte DevAddr sent by the Network on a join.
Source for the functions is not available. The libraries are distributed in binary form only. Only header files are visible to applications.
KeymasterJust need mLinux 3.3.x or greater for MTAC-LORA-H
KeymasterPacket forwarder is used to communicate with the lora-card just like in public network. Except the UDP end-points are local.
+20% cpu time is the process polling the card for packet through the USB-SPI library.
New MTAC-LORA-H SPI cards with packet forwarder reduce to 2-6%
KeymasterIf router has DHCP server, which is expected, then configure interface to use dhcp client to assign address and gateway.
In /etc/network/interface
Replace “iface eth0 inet static” with “iface eth0 inet dhcp”
August 2, 2017 at 2:26 pm in reply to: Understanding downlink channel used by gw/server USA 915 #20519KeymasterSee private vs public mode.
It is not lorawan protocol in private mode.
It was meant to allow 8 channel Conduits to operate in proximity without overlapping the downlink channels.KeymasterDo you have debug from the dot?
KeymasterWhat do you see in the debug?
KeymasterIs the server requesting an ack from device?
The server does not do retries yet. Perhaps it is waiting for ack.July 27, 2017 at 2:26 pm in reply to: Configuring to work with MQTT broker with user name and password #20383KeymasterSo you have enabled the MQTT broker on Conduit to use the public interface and bridge that connection using the mosquitto.conf file?
I would write an app that consumes the MQTT messages from the local broker and forwards the desired messages to the remote server using name/pass credentials.
You are probably only interested in “joined” and “up” messages.
July 27, 2017 at 1:49 pm in reply to: Configuring to work with MQTT broker with user name and password #20381KeymasterMQTT Name and password are not currently supported in network server. 🙁
KeymasterMTAC-LORA-1.5 Card is needed.
# mts-io-sysfs show lora/hardware-id
Keymastermbed mDot and xDot libraries have been updated just now.
Update to latest and use mbed-os 5.4.7.July 27, 2017 at 8:20 am in reply to: Can mLinux be installed on an AEP Model (and vice-versa)? #20367KeymasterPlease open a ticket at support.multitech.com for further assistance.
July 26, 2017 at 3:50 pm in reply to: Private Lorawan network using open-source network server #20363KeymasterThe private mode on Conduit and mDot will change the sync word to 0x12 and downlink frequencies.
The public mode should be fine to use with NetID 0 or 1
The advantage of using the private/public mode at the gateways is to filter packets based on the sync word. This way the public networks don’t bother forwarding packets over the back-haul to be rejected.
The gateways of a public network could also do this per DevAddr if NetID’s are properly used.July 26, 2017 at 8:02 am in reply to: How to change frequency from US915 to EU868 using AT commands on mDot? #20360KeymasterAT Firmware v3.0.0 is available for different regions.
https://webfiles.multitech.com/wireless/mtdot/dot-v3.0.0/Be sure to AT&F to reset to defaults and then AT&W to save new defaults.
KeymasterIncrease the log level to 6 on mdot and you will see tx and rx frequencies and datarates used for windows.
KeymasterDid you call setPublicNetwork(true) ?
KeymasterLook at main.cpp and the call to mDot::getInstance() that returns a reference to the singleton object.
KeymasterTry rx1 offset of 0.
Uplink frequency and datarate will determine the downlink response parameters. A DR Offset of 10 is outside of allowed values in LoRaWAN, range is 0-3.
KeymasterDo you mean to set the datarate used to perform the OTA join?
The OTA join datarate is handled by the library.
US915/AU915 alternates between DR0 and DR4 according to lorawan.
The regions will cycle through available datarates for each join.
This should allow a better chance of joining the network if many devices attempt to join at once.After the device is joined to the network the datarate can be adjusted according to the setTxDataRate input.
Keymaster1) The frequency band of a device is set in the firmware and cannot be changed at run-time. It was set in factory and read by firmware in v2.0.16 and before. Or next release will have separate firmware images for each regional spec.
2) It is always a good idea to check AT+TXN before sending.
3) US915 must match the channels in a single gateway deployment. EU868 has fewer channels and dynamically sets them.
4) In either 915 or 868 the tx datarate should be set using the DR0-DR7 values, these map to specific datarates (SF + BW) in LoRaWAN.
The SF_7-SF_12 values were used in the early versions and are not advised to be used.
KeymasterNo problem Frank. We’ve all been there.
KeymasterTry AT&F to reset the dot to factory configuration. The reconfigure the dot to connect.
Use AT+PN=1 to connect to public network like TTN.
KeymasterIn MANUAL join mode the session counter values need to stay in sync.
The counter on the dots must not decrease.
See AT+SS and AT+RS to save and restore the session counters.
Or from mDot.h:
/**
* Resets current network session, essentially disconnecting from the network
* has no effect for MANUAL network join mode
*/
void resetNetworkSession();/**
* Restore saved network session from flash
* has no effect for MANUAL network join mode
*/
void restoreNetworkSession();/**
* Save current network session to flash
* has no effect for MANUAL network join mode
*/
void saveNetworkSession();KeymasterSee example in AT Firmware source code
https://developer.mbed.org/teams/MultiTech/code/Dot-AT-Firmware/file/95c9eb69329a/CommandTerminal/CmdDisplayStats.cppKeymasterPerhaps first uplink is using the previous FCNT.
Was ACK received before power off?KeymasterEnable saving session over power cycle.
AT+PS=1Or AT+SS before power down and AT+RS after power up to save and restore the session manually in AT+NJM=1 OTA mode.
-
This reply was modified 7 years, 9 months ago by
Jason Reiss.
KeymasterFRAME-RX is processing something received and reported by the gateway hardware
PACKET-RX has been able to parse it as a LoRaWAN packet
PER is packet error rate, the FCNT of each packet is tracked and missed FCNT values count against the error rate of uplink packets. -
This reply was modified 7 years, 9 months ago by
-
AuthorPosts