[John C]

Ok i have raised a support case 5065580.

Meanwhile, are we sure that the LoRa mtdot card is not defective? Since every data sent from device seems to reach the gateway ( as per node-red debug message), its the ACK that is not received by the end device. Is there a known defect in the transmit side on MTAC-LORA?

Is there a different way I can have a chat, send a private message or email?

Thanks,
John

[John C]

The serial number is 18253567 and got it around first week of Oct. Can this be replaced if its one of the early production ones?

Thanks,
John

[John C]

AT+JOIN
Successfully joined network

OK
AT+PING
-119,-5.5

OK
AT+RSSI
-124, -125, -124, -125

[John C]

Using mdot library:

Total Payload sent : 10
Payload sent failed: 7
Average: 30%
Ping status: 0, RSSI= -115, SNR= -28
RSSI info (dB): last= -112, min= -114, max= -112, avg= -114
SNR info (dB): last= 17, min= 16, max= 18, avg= 16
TX power (dB): 20
UP = 12, Down= 5, Joins= 1, JoinFails= 0, MissedAcks= 8
Channels used: 868 MHz 868 MHz 868 MHz 869 MHz 869 MHz 869 MHz 869 MHz 869 MHz 869 MHz

Using
ATI
MultiTech mDot
Firmware: 0.1.4
Library : 0.0.9

AT+RSSI
-112, -112, -112, -112

OK
AT+PING
-118,-3.0

[John C]

Also another point regarding JOIN message. I have the following code (removed the check for errrors).

dot->setJoinRetries(255);

// attempt to join the network
pc.printf(“joining network\r\n”);

while ((ret = dot->joinNetwork()) != mDot::MDOT_OK) {
// in the 868 (EU) frequency band, we need to wait until another channel is available before transmitting again
wait_ms(dot->getNextTxMs() + 1);
}

Do we need the while loop here when we setJoinRetries. Also when I see that JOIN fails with “-4: Join Error” it is never able to JOIN back with the delay using while loop .

Thanks,
John

[John C]

I am using the mdot library? Is it ok if I call the API exposed by this lib?

Thanks,
John

[John C]

Hi Brandon,

I have a mdot and conduit gateway. I am able to
1. I am able to get mdot sending data to Conduit gateway
2. The data i sent from mdot device is visible on node-red

What I am facing:
1. I have only 26% success rate of sending data from mdot to conduit. The rest I get an error “-5: Operation Timed Out”.
I see almost all the time the remaining 74% data on node-red but the device is unable to receive the ACK.
2. I used to see a higher percentage 60% success rate but now its in late 20 or early 30%. Dont know what has changed here.

To help you i have dumped the stats here:
Total Payload sent : 50
Payload sent failed: 37
Average: 26%
RSSI info (dB): last= -82, min= -83, max= -73, avg= -80
SNR info (dB): last= 26, min= 24, max= 31, avg= 26
TX power (dB): 20
UP = 52, Down= 14, Joins= 1, JoinFails= 0, MissedAcks= 38
Channels used: 868 MHz 868 MHz 868 MHz 869 MHz 869 MHz 869 MHz 869 MHz 869 MHz 869 MHz

Let me know if you need any further info.

Thanks,
John

[John C]

Any update on this? I see a similar issue here.

[John C]

Resolved this issue since the Windows machine I use is a company laptop which prevents writing to a USB storage.

Using a VM to short circuit this issue 🙂

[Author]

Posts