[Jason Reiss]

Could you use the default firmware AT commands?

[Jason Reiss]

How long is the Dot configured to sleep?
I may be possible to sleep between ping slots.
Application may need to track time to be sure the device is awake for beacons and ping slots.

Automatic low-power Class B will be a future feature.

[Jason Reiss]

The value is a us timestamp internal to the radio hardware. It is used to schedule downlink packets with precise offsets.

1791585540 – 1790585540 = 1000000 us = 1 s

[Jason Reiss]

Is the network server configured and running?

[Jason Reiss]

Looks like your join delay is set to 1 second. The tmst is a value in microseconds of the Rx and Tx packets.

Change the join delay of the network server to 5 seconds and it should succeed.

lora/00-25-ca-0a-00-00-85-2f/join_request {…, “tmst”:1790585540,”chan”:0,”rfch”:0,”freq”:8
lora/00-25-ca-0a-00-00-85-2f/packet_sent {…, ”tmst”:1791585540,”twnd”:1}

[Jason Reiss]

The ack field means that the packet is an ACK and has the ACK bit set in the FCtrl field of the LoRaWAN header. Other fields are ADR, FPending, AdrAckReq, ClassB, etc. Details can be found in the protocol reference documentation (https://lora-alliance.org/resource-hub/lorawanr-specification-v103)

The confirmed/unconfirmed bits are in the MType field in the first byte of the LoRaWAN header. In this case 0x80 seen in the “mhdr” field which is a Confirmed Uplink packet.

I would only expect a packet to have an empty data field if mac commands needed to be sent and could not fit in the packet with the requested payload. The MAC commands would be sent and seen in the “opts” field which is empty.

You will need to look at the end-device application to see how an empty packet could be sent. The Confirmed Uplink request will not be overridden by the library in any case to answer your question.

This packet decoder maybe useful, this fake packet shows each field of the packet with an incremented set of numbers. A full LoRaWAN packet from the packet_recv topic would need to be used as input if you wanted to decode a real message.
https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=80111111112233334444556666666677777777&nwkskey=&appskey=

Field definitions found in the MQTT messages are defined.

MQTT Messages

[Jason Reiss]

The device is commissioned correctly as the JoinAcc is being sent.

Perhaps the device is not receiving the downlink as another join request is sent?

[Jason Reiss]

I am able to reproduce this if the downlink on port 0 is in the queue when the first uplink after join is received.

If there is a packet for any port other than 0 then both will be sent.

The first downlink after join will contain a Confirmed downlink with ADR commands to set the channel mask. There is an issue in scheduling this automatic downlink where the application downlink is lost.

[Jason Reiss]

The python mqtt packet should be in v1.6.4 and greater.

admin@mtcdt:~$ opkg list | grep mqtt
python-paho-mqtt – 1.1-r0.0

[Jason Reiss]

The hardware cannot support node.js past the provided version. The processor does not support hardware floating point operations.

v0.10.48 was the last version to maintain support for software floating point operations.

[Jason Reiss]

What packages are you looking to update?

On AEP normally an update image is applied.
They are available here.

Downloads

[Jason Reiss]

Try to see if the DNS is being resolved?
The links look to be working.

# nslookup multitech.net

[Jason Reiss]

Sorry, there is no hot-swap for the whitelist, is device provisioning expected o be a frequent occurrence in your use case?

We have a cloud Join Server service for end-device provisioning without changing the gateway configuration. Ask a sales representative about our Lens service (sales@multitech.com).

POST https://192.168.2.1/api/loraNetwork/whitelist/devices to add a single device.

{"deveui":"1122334455667789","appeui":"1122334455667788","appkey":"11223344556677881122334455667788","class":"A","device_profile_id":"","network_profile_id":""}

• This reply was modified 5 years, 6 months ago by Jason Reiss.

[Jason Reiss]

An updated version is available here.
https://github.com/MultiTechSystems/Dot-AT-Firmware-beta?files=1

[Jason Reiss]

Did you set join delay to 5?
AT+JD=5

[Jason Reiss]

msg.payload.result is an array.

https://jsonlint.com/

[Jason Reiss]

The API is available to node-red to access any information you may see in the GUI.

Make an HTTP request to 127.0.0.1/api/lora/devices for a list of end-devices.

MTR, Conduit, and Conduit 300 API Reference

Collection Endpoints

[Jason Reiss]

The firmware posted for beta has an updated mbed-os version 5.13.4 and do not appear to have this issue. Our next release will use an updated mbed-os.

https://github.com/MultiTechSystems/Dot-AT-Firmware-beta

[Jason Reiss]

This is a known issue since 3.1.0
https://os.mbed.com/teams/MultiTech/wiki/Dot-firmware-change-log

Reset is the only way to recover the device.

Do you have the debug pins wired to the host MCU?

A serial break on the debug port should reset the device.

[Jason Reiss]

If you did the 30s reset then it should have returned to factory settings.
It is now in commissioning mode and the WEB UI should be available at 192.168.2.1.
You should be prompted to create a user and password.

After commissioning the USB login should work again. SSH would need to be enabled.

[Jason Reiss]

Try using sudo if on mPower 5.0.x or higher.

admin@mtcdt:/opt/lora/gateway-utils$ sudo ./util_spi_stress

[Jason Reiss]

Firmware upgrade will install a full image. Only /var/config and /var/oem directories are left intact.

[Jason Reiss]

From Web UI console the URL provides the DevEUI and ID like this.

https://172.16.0.244/api/lora/packets/queue/00-80-00-00-00-00-fe-54/38

[Jason Reiss]

Using the gateway bridge I would expect the packet forwarder to connect to 127.0.0.1 or localhost.

> Network is unreachable

With this error it appears the remote server may not be accessible to the bridge anyway.

You will need to setup the network correctly.

These commands should work when the network is setup correctly

$ ping 8.8.8.8
$ nslookup google.com

[Jason Reiss]

lora-network-server init script is used for both network server and packet forwarder modes

Try to run the packet forwarder manually to see if you are receiving packets

$ sudo /etc/init.d/lora-network-server stop
$ cd /var/run/lora/1
$ sudo ./lora_pkt_fwd

Is there any gateway bridge logging?

[Jason Reiss]

Have you tried to use sudo with your commands?

[Jason Reiss]

Eu868 duty cycle is same for device and gw. It is limited by frequency.

[Jason Reiss]

The broker is attached to the loopback interface and is not available externally. There is no security to allow local applications to communicate without the overhead via MQTT.

The firewall will block incoming connections by default. So this will also need to be opened.

It would be better to run an MQTT client on the Conduit to connect to an external broker with connection security and forward messages through it.

[Jason Reiss]

AEP 1.7.4 and 5.0.1 can be installed on the geolocation gateways.

Search Results

Flashing mLinux Firmware

See Using Auto-Flash During Reboot with image upgrade.bin

[Jason Reiss]

All incoming connections are blocked by the firewall with default settings.

[Author]

Posts