Reacties geplaatst door hobo

20 Reacties

Eddy Tick
Eddy TickNieuwkomer
gevraagd in LoRa Forum

payload send twice

If I were you I would track FCntUp value (for many reasons).

7
Tim
6 jaar geleden
Eddy Tick
Eddy TickNieuwkomer
gevraagd in LoRa Forum

payload send twice

More interesting is that Lrcid values differ. So, some gateways send uplinks to one network server, and some other gateways send uplinks to another one.

7
Tim
6 jaar geleden
michieljol
KPN Moderator
michieljolProductmanager LoRa for Developers
geplaatst in LoRa Forum

Adaptive Data Rate (ADR)

[quote=rharte] I think a lot of airtime goes wasted this way on handshake on these parameters, while they are the same for every channel anyway, and all 8 frequencies can be known upfront to all devices, right?[/quote] This seems to be an example of The Art of Capacity Planning :-) [quote=rharte] However in practise, I think there are 8 channels available for uplink messages, at least my software use all 8 and messages arrive correctly, and in the messages from KPN's backend system this is indicated by the parameter [b]Channel [/b]which has values LC1.... LC8. [/quote] You're bragging that your device doesn't follow the specs, aren't you? :-)

9
rharte
6 jaar geleden
michieljol
KPN Moderator
michieljolProductmanager LoRa for Developers
geplaatst in LoRa Forum

Adaptive Data Rate (ADR)

[quote=rharte]I notice this channel mask is always 0x00 0x07.[/quote] BTW, what is the value of the Redundancy field? [quote=rharte]the device receives two NewChannelReq messages for ch3 and ch4.[/quote] Do you mean that ChIndex field values are 3 and 4? If so, these 're settings for ch4 and ch5. Actually, it shall be impossible to change ch3 settings with NewChannelReq command.

9
rharte
6 jaar geleden
S
stefanmintenNieuwkomer
gevraagd in LoRa Forum

OTAA downlink werkt niet meer (Arduino, HopeRF RFM95W)

Are you sure that your device's EUI is really unique? What DevAddr did you get after OTAA? P.S. Sorry for answering in English.

6
Jeroen10
6 jaar geleden
Tim
TimAllesweter
geplaatst in LoRa Forum

LoRa | Geolocation

[quote=rharte] However, if one gateway receives your signal quite strong, it will ask the device to tune down[/quote] Why do you think so? BTW, a gateway typically is just unable to send a MAC command to a node, as it doesn't have access to NwkSKey.

59
Rick S.
Community manager
6 jaar geleden
Tim
TimAllesweter
geplaatst in LoRa Forum

LoRa | Geolocation

[quote=Twave03] Why are moving objects not supported ? [/quote] Accuracy of the fine timestamps which are used for LoRa TDoA positioning is disappointing, and multipath propagation brings even more troubles. So you need a (huge) number of messages to feed the filter/solver with their ts and other metadata to get not-too-disasterous positioning accuracy. Actually, that's why Actility had gave up and bought Abeeway which provides assisted GPS solutions.

59
Rick S.
Community manager
6 jaar geleden
Jeroen10
Jeroen10Connaisseur
gevraagd in LoRa Forum

LoRa Geolocation Precision

[quote=Jeroen10] The question is how exactly does it improve the location with multiple messages [/quote] IIR filter is used. Not sure which one, it's their know-how. But there are not too many possibilities. And, actually, deep details don't matter for end users. [quote=Jeroen10] and with how many messages? [/quote] As many as possible. That's why moving objects aren't supported.

2
H
6 jaar geleden
B
BruininkPDeelnemer
gevraagd in LoRa Forum

Cost of LoRa

Hi Peter, do you mean that SIMPoint was unable to help you too? Thanks, Paul.

15
Rick S.
Community manager
6 jaar geleden
B
BruininkPDeelnemer
gevraagd in LoRa Forum

Cost of LoRa

Hi Peter, let us know if SIMPoint guys react better/faster, please. Thanks!

15
Rick S.
Community manager
6 jaar geleden
B
BruininkPDeelnemer
gevraagd in LoRa Forum

Cost of LoRa

[quote=Tim] At this moment, the costs of LoRa are not public yet. [/quote] http://www.simpoint.com/en/lora/ Your partners seem to think different. [quote=Tim] To give you an idea, for around 35 euro per month, you'll get 100 uplinks and 10 downlinks per day. [/quote] Your partners seem to think different :-)

15
Rick S.
Community manager
6 jaar geleden
B
basvaningenRijzende ster
gevraagd in LoRa Forum

Max uplinks per hour

[quote=salphen] 2. How many bytes will be added to the data of 51 bytes? (parity check, keys, encryption ect.) [/quote] 12 or 13 (12 bytes of LoRaWAN header + FPort, if used) [quote=salphen] 3. If I have to use SF12 with the max size message plus added information. What will the Time on Air be? [/quote] It depends on CR used. Roughly, 2.8 sec. to 4 sec.

6
Tim
7 jaar geleden
B
basvaningenRijzende ster
gevraagd in LoRa Forum

Max uplinks per hour

[quote=hobo][quote=Tim] 3384 seconds [/quote] Oops, 3386 :-)

6
Tim
7 jaar geleden
B
basvaningenRijzende ster
gevraagd in LoRa Forum

Max uplinks per hour

[quote=Tim] Example: A device just transmitted a 0.5 s long frame on one default channel. This channel is in a sub-band allowing 1% duty-cycle. Therefore this whole sub-band (868 – 868.6) will be unavailable for 49.5 s."[/quote] Please note that this is just an example. If you sent 72 frames with 0.5 s time-on-air each and then keep silence for 3384 seconds (considering that RX2 delay is 2 seconds), you still meet the duty cycle reqs.

6
Tim
7 jaar geleden
O
omartaoufikStarter
gevraagd in LoRa Forum

rn2483 rssi

Nobody can explain why, but it is impossible to get the RSSI of the last received packet using RN2483 radio get commands, althoug you can get SNR for that packet. When you use the module in LoRaWAN network, you can initiate link check and then get demod. margin for link check answer, but this feature is useless in point-to-point environment.

8
Tim
7 jaar geleden
michieljol
KPN Moderator
michieljolProductmanager LoRa for Developers
geplaatst in LoRa Forum

ISM 868 band and the duty cycle

Please see LoRaWAN™ Specification V1.0.2, chapter 21 ("Revisions") , Page 67 lines 23, 24 : "Removed explicit duty cycle limitation implementation in the EU868Mhz ISM band (chapter7.1)" You may also take a look at LoRaWAN™ Specification V1.0, article 7.1.2, EU863-870 ISM Band channel frequencies, and compare it with chapter 2.1.2 EU863-870 ISM Band channel frequencies of LoRaWAN™ Regional Parameters V1.0. You'll see that the following paragraphs (page 34, lines 20-30 in LoRaWAN™ Specification V1.0) were removed in recent versions of the spec: "The LoRaWAN enforces a per sub-band duty-cycle limitation. Each time a frame is transmitted in a given sub-band, the time of emission and the on-air duration of the frame are recorded for this sub-band. The same sub-band cannot be used again during the next Toff seconds where: ......... During the unavailable time of a given sub-band, the device may still be able to transmit on another sub-band. If all sub-bands are unavailable

4
W
6 jaar geleden
michieljol
KPN Moderator
michieljolProductmanager LoRa for Developers
geplaatst in LoRa Forum

LoRa | Frequently Asked Questions (FAQ)

[quote=michieljol][ [b]How is the SF calculated? Is see that I have very good radio conditions to a gateway, but still have a high SF?[/b] SF is calculated over messages that are received by at least three gateways. So the gateways with the lowest radio condition determines the SF. [/quote] Can you please clarify this? You meant that during ADR only the messages received by at least 3 GW count, right?

11
Tim
6 jaar geleden
michieljol
KPN Moderator
michieljolProductmanager LoRa for Developers
geplaatst in LoRa Forum

Over The Air Activation (OTAA)

As far as I see from the doc, by default that module transmits JoinRequest message with SF7. This may be the root couse of your troubles, if you're located far enough from a base station. The module's API contains a command for lowering default datarate, but I'n not sure if this will work for JoinRequest.

5
H
7 jaar geleden
michieljol
KPN Moderator
michieljolProductmanager LoRa for Developers
geplaatst in LoRa Forum

ISM 868 band and the duty cycle

[quote=michieljol] [u][b]LoRaWAN specifies that each time a message is send in one ISM subband, the device must wait the remaining time of the duty cycle in that band before resending (For time on air of 0.5s and 1% duty-cycle, this means waiting 49,5s)[/b].[/u] [/quote] Explicit duty cycle limitation implementation description for EU868Mhz was removed from LoRaWAN specification.

4
W
6 jaar geleden
michieljol
KPN Moderator
michieljolProductmanager LoRa for Developers
geplaatst in LoRa Forum

Spreading factors and Coverage

[quote=michieljol] [h3]Time on Air[/h3] ....This ranges from 50 ms for a 10 byte payload on SF7 to a ToA of 1.6 ms for the same packet on SF12.[/quote] Guess you meant 1.6 seconds, not 1.6 milliseconds.

6
Timeless
7 jaar geleden

Badges

Toon alle badges
Forumvoorwaarden