[Jason Reiss]

It would be “possible” to repeat the packet with one conduit, however there is no software available to support this.

This will only work with upstream packets. Downlink packets would arrive late.

[Jason Reiss]

The MTAC-LORA radio can send and receive lora packets. With the correct settings the they can communicate.

The “ipol” setting is enabled when communicating with the end points.
The “ipol” setting is not enabled when end points are communicating with the gateway.
https://github.com/Lora-net/packet_forwarder/blob/master/PROTOCOL.TXT

Two cards can be installed and used and two packet forwarder processes can be started. The network server will only use one card by default.

[Jason Reiss]

Please see the following documentation:

LoRa

AEP:

Conduit mPower: LoRa Communication and Node-RED

mLinux:

Conduit mLinux: LoRa Communication

[Jason Reiss]

If you want to add a channel at 869.5 the use the addChannel function.

This channel will then be added to the list of available channels for the device to choose. The device will choose randomly from the available channels with each send. 869.5 is in the 10% band so it will be available most often.

Peer to peer mode in EU is fixed at 869.85 and 7dBm output to allow 100% duty cycle. Peer-to-Peer mode will not join a network.

[Jason Reiss]

If you have followed the things network install guide the installed packet forwarder (global_conf.json) can be configured to pass uplink packets to the local network server and the things network server.

https://thethingsnetwork.org/wiki/Installing-your-Multitech-mLinux-Conduit

You may see downlink issues with two network servers are scheduling packets for one gateway.

[Jason Reiss]

Rafael,

The global_conf.json file should be created in this directory

/var/run/lora/1/

It will contain the json that has been entered into the packet forwarder configuration text area when configured for packet forwarder mode.

Can you provide more details one what you have done or what you are trying to do?

[Jason Reiss]

The ST Micro STANDBY is the lowest power mode. All RAM is lost and peripherals are off. Backup registers can be used to retain state over sleep. The libmDot will keep running state in the backup registers to be reloaded automatically so the session will be maintained. Execution begin at the start of the program as it would from power-up.

With ST Micro STOP RAM is maintained and peripherals are on. Execution resumes from the call to sleep.

Waking up from Stop mode takes 13-14 μsec.
Waking up from Standby mode takes 314-407 μsec.
RTC time period is 30.5 μsec.

These values have to be taken into account if you need to wake-up on a specific 1 msec timehack.

[Jason Reiss]

Page 93 of the linked manual above shows an AT Command example.

An application would setLinkCheckThreshold and setLinkCheckCount then monitor the getNetworkJoinStatus between sends to detect when the network may be down.

The AT Command firmware code on mbed provides an example too.
In CommandTerminal.cpp
bool CommandTerminal::autoJoinCheck()

[Jason Reiss]

Could be an old session file. Try AT+SS to see if it goes away.

[Jason Reiss]

Do you have any messages being generated by the device?

What is the message from this command:
> /etc/init.d/lora-network-server restart

Is the MTAC-LORA card seated properly and being read? MTAC-LORA info should show on the dashboard in the bottom right corner.

[Jason Reiss]

The libloragw v1.7.0 is built into mLinux.

Is there specific functionality from v2.0.0 that you need?

We use version 1.7.0-mts branch from http://git.multitech.net/cgi-bin/cgit.cgi/lora_gateway.git/

[Jason Reiss]

See AT+ACK, AT+LCT and AT+LCC
http://www.multitech.com/manuals/s000643_1_1.pdf

The network server has a lease time setting to configure the amount of time to keep a session without activity.

[Jason Reiss]

The DataRates enum also has DR0-DR15

DR2 – SF8BW125
DR4 – SF8BW500

[Jason Reiss]

I believe you will find your answers in our updated documentation.

Here is the updated AT Command Guide for 1.0.8
http://www.multitech.com/manuals/s000643_1_1.pdf

Here is the updated Developer Guide for 1.0.8
http://www.multitech.com/manuals/s000612_2_0_7.pdf

Thanks,

Jason

[Jason Reiss]

The public network setting is documented on these pages.

Conduit mLinux: LoRa Use With Third-Party Devices

Introduction to LoRa

[Jason Reiss]

The session should be reloaded when you wake from sleep.

You could try to enable this setting.
AT+PS – Preserve session

The 1.0.8 firmware has session management functionality that can also be used in OTA mode. After a join you can save and restore the session info.
Be sure to save the session before going into deep-sleep mode.

AT+SS – save session
AT+RS – restore session

[Jason Reiss]

Currently our products are available for sale online through distributors.
http://products.avnet.com/shop/en/ema/3074457345626399590/?CMP=KNC-SupplyFrame_VSE-T11

[Jason Reiss]

When building strings stringstream is also very helpful
http://www.cplusplus.com/reference/sstream/stringstream/

Using DR0 the max payload is 11 bytes.

Introduction to LoRa

Sending JSON maybe overkill for data being sent from a known endpoint. It would be best to pack it as small as possible.

“t:32,h:57” -> 9 bytes

A binary format with predefined types for each data item
temp: 0x01
value: 0x20 -> 32
humidity: 0x02
value: 0x39 -> 57

0x01200239 -> 4 bytes

If you know this sensor is only sending temp and humidity then you could just send the values in two bytes.

Here is a binary format we use for the EVB:

Data Packet Format

[Jason Reiss]

The dash is the EUI canonical format separator. It was a mistake to use the colon originally. Sorry for the inconvenience.

[Jason Reiss]

You can issue an http request to the local api.

127.0.0.1/api/stats/ppp/rssi

[Jason Reiss]

The conduit will send only one message downlink per uplink.
Otherwise there would be some format needed in order to concatenate two packets.

AT+DP (data pending) will tell the end-point if there are more messages available on the server.

AT+RECV shows the last packet received, which was also displayed after AT+SEND

AT+RECVC is used to for testing receive functionality of the radio outside of LoRaWAN when doing compliance testing

More info can be found in our AT Command Guide
http://www.multitech.com/manuals/s000643_1_1.pdf

[Jason Reiss]

The app won’t start, there should be debug message

“pinmap not found for peripheral”

[Jason Reiss]

Have you tried:

Serial gps(PA_2, PA_3);

The TX pin should be first.

Also you could see if any debug comes out at the mbed default 9600 if there are issues before the application is loaded.

[Jason Reiss]

I do not see why that would not be possible.

[Jason Reiss]

This sample nodejs app shows how to connect to the local mqtt.

Conduit mLinux: LoRa Communication

[Jason Reiss]

Differences are shown in this document

Introduction to LoRa

In a nutshell, if the settings don’t match it don’t work.

Details, the gateway will be listening for lora packets starting with a different sync word signifying the beginning of a packet. It will start to receive bytes at the wrong time or not at all.

Also join accept messages will be sent to hit rx windows at different delays.

[Jason Reiss]

The bin file will disappear in normal operations. The USB drive is a staging ground to flash the processor on the mDot, it is not the mDot flash memory.

The problem is the USB driver in linux thinking the memory is full.

I use the eject command in Debian to reset the USB driver without unplugging the device:

> eject /dev/sdd; sleep 1; eject -t /dev/sdd

Use df to find which drive to use:

> df
...
/dev/sdd       528        16       512   4% /media/MULTITECH

[Jason Reiss]

You can use update-rc.d to install a script to run at startup.

https://www.debian-administration.org/article/28/Making_scripts_run_at_boot_time_with_Debian

[Jason Reiss]

Our current MTAC-LORA card has a USB interface.

Here is the gateway branch used for the gateway library in mLinux, it will show how to access the card
http://git.multitech.net/cgi-bin/cgit.cgi/lora_gateway.git/log/?h=1.7.0-mts

Otherwise the built in packet forwarder can be used accessed through UDP, lorawan is not required to receive and send packets through the radio.

Recipes for building the packet forwarder:
http://git.multitech.net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-connectivity/lora

Documentation for communicating with packet forwarder:
https://github.com/Lora-net/packet_forwarder/blob/master/PROTOCOL.TXT

[Jason Reiss]

On the Conduit in lora-network-server version 1.0.8 and above the ADRStep setting will allow configuration of the sensitivity of the ADR algorithm. The default setting of 30 cB will allow 3dB per spreading factor setting determined by the received SNR of the last set of packets. The minimum setting is 25 cB (2.5 dB) which is the theoretical difference in link budget between each spreading factor.
Increasing the ADRStep above 30 will require a greater signal quality to reach the highest datarate.

The configuration setting should be:

"lora": {
...
    "ADRStep": 30 /* Step in cB between SNR based datarate assignment for ADR */
...

[Author]

Posts