[Jason Reiss]

Are you connecting through a grove shield or directly to the mdot pins?

Here is an mbed library and example for the sensor:
https://developer.mbed.org/cookbook/Grove-temperature–humidity-sensors

[Jason Reiss]

This page describes the options available in the lora-network-server configuration. The “allowPublic” will open UDP ports on the external interfaces.

Conduit mLinux: Advanced LoRa Configuration

[Jason Reiss]

Rx2 will be used if Rx1 is not available when queuing a downstream packet.

This would happen if packets are received from two or more motes at the same time. Since the downstream packets for Rx1 overlap, Rx2 will be used.

[Jason Reiss]

You can use the virtual serial port but you will lose the debug output.

To change the ports you can build a modified AT Command firmware.

https://developer.mbed.org/teams/MultiTech/code/mDot_AT_firmware/?platform=MTS-mDot-F411

Change main.cpp as follows

Serial debug(XBEE_DOUT, XBEE_DIN);
 
mts::MTSSerial serial(USBTX, USBRX, 512, 512);

• This reply was modified 9 years, 2 months ago by Jason Reiss.
• This reply was modified 9 years, 2 months ago by Jason Reiss.

[Jason Reiss]

Thanks for the heads up.

The altitude would be in the units as read by the network server.
The Things Network I guess would read as meters.

Semtech demo site shows meters as alt of gateways.

[Jason Reiss]

It would be best to buy the AEP version.

mLinux can be installed on it later if you wish. It is much easier to move from AEP to mLinux and back than if you started with an mLinux setup and wanted AEP.

[Jason Reiss]

Currently there is no white-list feature.

Any device that is configured with the network eui/key will be able to join.

[Jason Reiss]

It is the Datarate used for the second receive window.

A LoRa “Class A” device will open two receive windows after each uplink to receive possible a downlink packet from the server. The server will respond in one of the windows.

The configuration accepts the Spreading Factor to use, US will use 500 kHz channels and EU will use 125 kHz.

[Jason Reiss]

The files will be saved in the 2MB external flash and will persist across firmware updates.

[Jason Reiss]

The ON_SLEEP pin is used to signal a host that the dot is awake. It is used in the AT Command firmware in serial data mode. It has no defined function within libmDot.

More details can be found at the bottom of this page:

AT Command Getting Started Guide

[Jason Reiss]

What browser are you using?
Safari has a known issue with creating ssl web sockets to some web servers.

[Jason Reiss]

The duty-cycle for join requests is 0.1% for deployed modules you would want to wait until AT+TXN returns 0.
For development purposes a reset with clear the duty-cycle timers.

[Jason Reiss]

On AEP the default creds are not root/root. Follow this link to the correct creds.

http://www.multitech.net/developer/software/aep/getting-started-aep/

[Jason Reiss]

The linux kernel ip-stack may have a fifo buffer before the NIC.
There is nothing in software to buffer received packets.

The packet forwarder code is open source.
https://github.com/Lora-net/packet_forwarder

[Jason Reiss]

Do you see consistency with the “rfch” value to each set of values?

There are two radios each setup to listen on 4 frequencies.
The node will randomly choose a frequency out of the eight.

[Jason Reiss]

When is data_str being filled?
I don’t believe data_str.length() will ever be > 0.

Shouldn’t you check ‘data.length()’ and iterate over ‘data’ calling push_back on ‘data_str’?

[Jason Reiss]

The packets sent down to mDot are during two receive windows at 1 and 2 seconds after end of transmission.

[Jason Reiss]

Please open a case at https://support.multitech.com/ to share more info of your ‘no tx’ issue and see about getting dev build.

[Jason Reiss]

The downloads page has been updated.

Downloads

[Jason Reiss]

We can pass the full value from the packet forwarder in a future version. Not sure on a time table at the moment however.

[Jason Reiss]

Howard,

Did you send a packet to the Conduit?

The mDot will only be able to receive a packet after a successful send.

[Jason Reiss]

WAN access must be enabled Admin > Remote Access
Under HTTPS check the WAN box then save & restart.

The will of course expose the GUI interface to the internet increasing the security footprint. Be sure your uname & pwd have been changed.

[Jason Reiss]

The mDot will print debug on the mbed debug pins on the back of the module. This is available through the USB of the UDK.

AT+LOG=6 will set the log level to max.

If you are using 5/6 s join windows set AT+PN=1
Since you received the JoinRequest I assume you have done this, unless you gateway is set for Private Network sync word 0x12.
In that case the AT+PN=0 would match the sync word by the expected JoinAccept message will be at 1/2s on the mDot.

[Jason Reiss]

Yes, the network server must follow the ETSI duty-cycle limitations per transmitter. We will be working on the ability to add second AC-LORA card.

[Jason Reiss]

There is not a way through the interface. You can enter a URL manually.

Login as normal and use the following:
https://[AEP-IP]/api/loraNetwork?method=PUT&data={"lora":{"nodeQueueSize":1}}

You can check that the change is complete with:
https://[AEP-IP]/api/loraNetwork

Now restart the network-server by disable and save then enable and save.

• This reply was modified 9 years, 3 months ago by Jason Reiss.

[Jason Reiss]

Yes that will work for now. I plan on added a way to flush the queue as well.

[Jason Reiss]

The default Rx2Channel datarate per LoRaWAN is DR8 SF12BW500 in US and DR0 SF12BW125 in EU. The network server uses these datarates for the 2nd window on the join accept message. With the join accept message are instructions to change the second window datarate to the one specified in the AEP configuration.

If the server used the configured datarate for the 2nd window on join accept message this information would have to be communicated to the mote ahead of time.

[Jason Reiss]

It is in micro-seconds.

[Jason Reiss]

I found this topic on the openlora forum regarding the RN2483.

https://openlora.com/forum/viewtopic.php?f=5&t=6

[Jason Reiss]

We will be adding more mqtt message events to the lora-network-server.

I am not sure you would want all these events routed off box and possibly over a cellular connection.

It would be better to proxy with a filter for a specific mqtt topic.

Plus changing the config will cause the lora nodes to not function without being configured with username and password.

[Author]

Posts