Quantcast
Channel: MultiTech Developer Resources » All Posts
Viewing all articles
Browse latest Browse all 7111

MDot stuck at SF8BW500 with ADR enabled.

$
0
0

During the last weekend we have been running tests using the ADR feature. It seems like the conduit sets the MDot to run at SF8BW500 DR and after which no matter what it doesn’t change the DR. There were times the MDot couldn’t even get to the Conduit or rather transmit messages to the MDot.

Now reading thru’ the ADR spec, it seems like the conduit requires atleast 6 uplink packets before it can determine what the DR/Spread factor to set for the mdot.

My questions is in this scenario where the MDot is unable to get to the conduit after it has been connected at a given data rate, should I be implementing any changes on my end to try changing the SF/DR such that it helps with the transmission like switching it to SF10BW125?

We could have a scenario even though the mdot is static in a given place all of a sudden lets say its blocked by say a large physical obstacle or something which prevents the transmission from getting to the conduit, now the conduit has no way of directing the MDot to switch its DR right? In this case what is suggested the mdot do to get the data out to the conduit?

Thanks,
Ajay


Viewing all articles
Browse latest Browse all 7111

Trending Articles