Hi!
The units join via OTA. Most traffic is uplink, but once a week there is significant traffic downlink.
We have several different installations. Nodes range from 30 items to 400 items (and up to 1000 units are planned).
The nodes report back (uplink) every 15 minutes sending a short status of aproximately 10 bytes.
Once a week aprox 300 bytes of data is transmitted to each unit. data is splitted into packages of size 50 bytes.
if something goes wrong with the 300 bytes of data (it is not all received) a new attempt is done at every 15 minutes when the node sends its status. We then resend the 300 bytes (as 6 packets).
We are using a STM lora chip and your gateway. The lora stack beeing used is obtained from STM.
1. “It may be possible work around by incrementing the uplink counter to 1″ – how can this be done?
4. “Cannot increase duration mean a packet was scheduled but the payload cannot be added in the available downlink slot. The payload will wait in the queue until a downlink slot is found.”
This is very interesting, but would need some more explanation. We just noticed that the limitation of payload is different between Europe and US.
11 – 242 bytes US
51 – 242 bytes EU
Does this mean that we have a packet of 50 bytes that we try to send to a unit that transmits on a very low datarate so that the data does not fit in the 400ms window?
Or what do you mean with a downlink slot? What is regulating the downlink slots? Will many uplink data packages make it harder to find a downlink slot?
Please elaborate more as I think I might miss some vital part here. 
5 b.) “Scheduling conflict means two transmissions want to use the same time. Only one can be transmitted. Some guard time is added in scheduling, we will have this timing tightened in a coming release. It should reduce conflicts.”
If our serverprogram sends lots of packets (6 packets of 50 bytes) for each node instantly to the mqtt server. Will the network server not just transmit them one by one in the same order as we transmitted them to mqtt?
I am very greatful for your help.
Thanks
Thomas Hermansson
ÅF Technology
Sweden.