![Lobaro wMBUS-LoRaWAN Скачать руководство пользователя страница 16](http://html.mh-extra.com/html/lobaro/wmbus-lorawan/wmbus-lorawan_user-manual_1932406016.webp)
5. LoRaWAN Data Upload Formats
10 < LoRaWAN Port < 100 (Part Number | Total Parts)
Gaps in the LoRaWAN Frame Counter are giving a hint for missing telegram parts which can
happen in LoRaWAN since it's a ALOHA based protocol, e.g. collisions and some packet
losses are accepted by principle of operation. In case the backend noticed a missing packet
the wMBUS telegram can't be assembled anymore as described before.
5.2.1. Examples
Examples (with loraMaxMsgSize = 50):
A 48 Byte wMBUS telegram will be send on LoRaWAN port 11. Port 11 says it is the
rst message of only one message (no splitting).
A 75 byte wMBUS telegram will be send in two messages on LoRaWAN ports 12 and
22. Port 12 means this part one of a wMBUS telegram that got splitted into two
LoRaWAN messages. Port 22 means that this data is the 2nd part of the original
wMBUS data. Both parts have to been concatenated in the order of receive by the
backend.
A 101 byte wMBUS telegram will be send in three messages on LoRaWAN ports 13,
23 and 33. Port 13 means this part one of a wMBUS telegram that got splitted into
three LoRaWAN messages. Port 23 means that this data is the 2nd part of the original
wMBUS data. Port 33 means that this data is the 3rd part of the original wMBUS
data. All three parts have to been concatenated in the order of receive by the backend.
5.2.2. Upload Rate
The bridge has to work in compliance with the European SRD 868 1% duty-cycle regulations.
This implies as a rule of thumb the device can upload at most wMBUS telegrams for 36
seconds every hour. The actual transmit time (`ToA: time on air') for each LoRaWAN
message depends on the byte size and the used LoRa spreading factor (SF) which denes how
redundant LoRa data is send. This means a device with good connectivity and consequently
using LoRa SF7 (ToA 0,050s) can upload much faster more data than a node using LoRa
SF11 (ToA 1s) due to a hard to reach LoRaWAN gateway. The bridge will upload in
conformity with the regulations automatically as fast as possible. When it has to wait it
enters a low power sleep mode until the next transmission is possible again.
The next data collection phase will be started only after completion of the previous upload
phase in respect to the congured cmodeCron or smodeCron, whichever is earlier. Because
of this it is advisable to dene the cron parameters with an estimation of the upload duration
in mind. This will avoid unexpected `skipping' of data collection phases.
wMBUS over LoRaWAN Bridge
16