Jason Reiss
Forum Replies Created
-
AuthorPosts
-
Jason Reiss
KeymasterThe AT+TXP and AT+ANT effects will be changed for the US915 in the next release. The current release will subtract the gain from the output power
Under FCC the maximium conducted output allowed is 1 W (30 dBm)
Depending on the number of channels enabled and the datarate used this limit may be 21 or 24 dBm
Antenna gain up to +6 dBi is allowed with 1 W.
Higher than +6 dBi must dial back the conducted power the amount of gain over 6 dBiThe mDot library will use the antenna gain and tx power settings to stay below.
KeymasterEnabling the network server on conduit will replace the Loriot functionality.
You can configure the mDot box as a node on Loriot if you want.
OTA MODE
——–
AT+NJM=1
AT+NI=0,
AT+NK=0,
AT&WABP MODE
——–
AT+NJM=0
AT+NA=
AT+NSK=
AT+DSK=
AT&W
KeymasterSet the network.eui and network.key fields for the network server and configure each node with the same. Then issue OTA join.
Keymaster256 is the maximum physical LoRa packet size. It is not the max payload size, 242 bytes. That is the maximum allowed in the LoRaWAN protocol and a limitation of the SxRadio chips.
There are also regional regulations to consider. Regions may restrict dwell time or duty-cycle. EU restrict by duty cycle and US by 400 ms dwell time.
See https://www.lora-alliance.org/portals/0/specs/LoRaWAN%20Specification%201R0.pdf for limits according to datarate per region.
KeymasterKeymasterKeymasterAs Leon said the timing is tight.
I usually just hold the ‘+’ key down and press the reset button on the device a few times when resetting manually.If it is automated I would reset, wait 0.2 sec, reset, wait 0.8 sec, and send +++
KeymasterYes, +++ will escape the join sequence.
Keymaster1) it will stay in the queue until network server is reset or empty command is sent to queue
2) the downlink seq no should be in the packet_sent event
3) it does not handle the event
4) it contains all information sent to the radio via the packet forwarder i.e. freq, datr, modu, …
See
https://github.com/Lora-net/packet_forwarder/blob/master/PROTOCOL.TXTKeymasterIf you require ACK on the lora-out node then the network server will hold the packet in the queue until ACK is received from the device. If the ACK is not received on the next uplink then the same packet will be sent down to the device, include the same sequence number.
This is separate from the ACK required for an uplink sent to the server where the server will send the ACK in a downlink if the device has ACK enabled.
@Lawrence uplink/downlink ACK is a LoRaWAN feature
KeymasterYou will need an MQTT node
KeymasterKeymasterSame as if it were powered on from outside of sleep.
KeymasterYes, the TX windows will be opened at 1 and 2 seconds after end of TX.
RX timeout will fire after a symbol timeout at the of each window. The longest symbol timeout is ~200 msYou may find interesting info in these high level overviews as well.
https://www.lora-alliance.org/portals/0/documents/whitepapers/LoRaWAN101.pdfhttps://www.thethingsnetwork.org/wiki/LoRaWAN/Overview
http://www.link-labs.com/what-is-lorawan/
Or you can also read directly from the spec.
https://www.lora-alliance.org/portals/0/specs/LoRaWAN%20Specification%201R0.pdfOr you could dig into the reference implementation
https://github.com/Lora-net/LoRaMac-nodeKeymasterThis will handle the lora side. of communication
It should be easy to find an example for the REST side of the node.js.
KeymasterDeepsleep is standby mode.
The flag will be set when the application creates the mDot object if the device was in deepsleep/standby mode. If unthe reset button is pressed while in sleep the flag will also be set. Two reset presses will reset the flag before the mDot object creation. Otherwise the value is read and the flag is reset by mDot.
KeymasterThe Pinout Diagram shows the Pin mapping from mDot to the arduino header on the UDK
https://developer.mbed.org/platforms/MTS-mDot-F411/Mbed I2C show the programming side.
https://developer.mbed.org/handbook/I2CKeymasterNode-Red lora settings
MQTT: localhost:1883
Topic: lora/+/+http://www.ibm.com/developerworks/cloud/library/cl-mqtt-bluemix-iot-node-red-app/
July 27, 2016 at 7:22 am in reply to: using mDot Lib's writeUserFile not saving data to flash. #14334KeymasterThe bootloader is part of the mDot platform and can be accessed by sending to the debug serial port just after reseting the device.
User files in the flash memory are saved with a ‘u_’ prefix prepended to the supplied name through libmDot api. Also if a file is uploaded with the prefix it should show in the libmDot file list.
bootloader :>
bootloader :> help
Available commands:
help: display this message
boot: start user application
upgrade
transfer
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!
KeymasterThe bootloader is part of the mDot platform and can be accessed by sending to the debug serial port just after reseting the device.
User files in the flash memory are saved with a ‘u_’ prefix prepended to the supplied name through libmDot api. Also if a file is uploaded with the prefix it should show in the libmDot file list.
bootloader :>
bootloader :> help
Available commands:
help: display this message
boot: start user application
upgrade
transfer
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!
KeymasterTime between messages will depend on the duty-cycle of the frequencies used and length of packet sent. Typically a 1% duty-cycle is imposed, so take the time-on-air for your packet length and datarate and multiply by 100.
It is possible to configure to use the 10% duty-cycle band centered at 869.525. Set Conduit additional frequencies to 869.5.
100% duty-cycle can be used at 869.9 if power is limited to EIRP 7dBm
July 26, 2016 at 11:20 am in reply to: using mDot Lib's writeUserFile not saving data to flash. #14320KeymasterThe file should be opened for writing.
mDot::mdot_file file = dot->openUserFile(“test.dat”, mDot::FM_CREAT | mDot::FM_WRONLY);
July 26, 2016 at 10:48 am in reply to: using mDot Lib's writeUserFile not saving data to flash. #14316KeymasterCan you provide debug output?
July 26, 2016 at 10:46 am in reply to: Public/Private messages coming through when they shouldn't… #14315KeymasterIt does it’s best at making it invisible. But as you see there may be a packet error to allow a few through.
Increasing distance from mDot to gateway may reduce this occurance.
KeymasterConduit is a gateway/packet forwarder when operating with Loriot network server.
lora-network-server.conf is not used in that setup.
Depends on the LoRaWAN stack implementation?
July 26, 2016 at 10:08 am in reply to: Public/Private messages coming through when they shouldn't… #14311KeymasterQ1: The goal is just reduction?
A1: What other goal could be made?
Q2: 3rd party + remote server?
A2: mDot can be used with Public or Private. 3rd party device may not be able to be configured to operate with the Private mode on Conduit.
Private vs Public and remote server is a matter of packet forwarder sync word setting, mDot can also function in this mode.July 26, 2016 at 8:36 am in reply to: Public/Private messages coming through when they shouldn't… #14307KeymasterThe Public/Private feature?
Using Private mode will filter out the number of packets that need to be processed if there are public network mDot’s in the area.
Also since the network server resides at the gateway a shorter join delay of 1 second is used. And the private mode allows multiple networks in the same area by segmenting the frequencies used with the Frequency Sub Band setting. This mode is applies Multitech devices as it departs slightly from LoRaWAN in the downlink frequencies used.
Using private mode also helps the public network from having to examine and filter out packets if there is a gateway receiving the private packets.
The Public mode is included in the gateway to allow 3rd party LoRaWAN devices to function with the on-board network server.
July 26, 2016 at 7:35 am in reply to: Public/Private messages coming through when they shouldn't… #14305KeymasterCRC is applied to the packet data, so if bits are flipped past the sync word then the packet can be filtered.
What is the concern of a private message being forwarded?
A 3rd party will not have the encryption keys needed to decrypt the packets.
A 3rd party network server will drop the packet as the seqno and MIC will not match, if there is a corresponding record for the packet address. -
AuthorPosts