[andrew@bitfinder.co]

Does this knock out one of the other LoRa mode channels, or is there already spare capacity for the EU868 setup?

Is there already another LoRa channel set up on that center?

The planning of the network seems to be very … opaque.
I am hitting network capacity limits with EU868 due to the 1% airtime.

Given that the EU868 spec does not mandate the channel plan directly in the way that the US915 plan does, it would be good to know the actual, exact channel plan that the Conduit it set up to offer when in EU868 mode, so I can compare that (and any additions/modifications) to the EU868 bands, airtime limits, and plan for the capacity that is needed.

I would like to be able to be able to know, see, and modify exactly which centers, BW’s, DR’s, and modes (LoRa vs FSK) are being offered. By either the UI setup or by editing of a config file.

[andrew@bitfinder.co]

We are not using packet forwarder mode. We are running some application code on the Conduit that connects to our own cloud services.

Is there a config file that sets the radio channel plan in general for each region setting?

[andrew@bitfinder.co]

Just to close this out, for anyone else who comes looking for this same information:
Extensive RF testing reveals that the receive sensitivity of the Conduit AP model is -110dBm, and for US915 DR3 and DR4, packets cannot be received below this level.

[andrew@bitfinder.co]

It would be great to have an answer to this.

[andrew@bitfinder.co]

Is there a tabulation of which channels belong to which frequency sub-band? A specific version of the standard or of the regional parameters?

I assume it is something like:
Band 1 = upstream 125Khz channels [0-7] and downstream 500Khz channel 0
Band 2 = upstream 125Khz channels [8-5] and downstream 500Khz channel 1
and so on …

But I am having some difficulty getting things to work properly, using an end-node where “frequency sub-band” is not defined.

[andrew@bitfinder.co]

I am doing a similar-ish thing now-ish. But not with parking sensors.

If you are running your python script on the gateway, then you need to get python pip installed, then paho_mqtt and requests python modules.

paho_mqtt will connect to the local mqtt broker, get the “data” key from the message, do a base64 decode on it to get bytes, then (the hardest part) will be using struct unpack on the byte data to recover the values you are looking for.
Then formulate your HTTP request and send via requests module.

[andrew@bitfinder.co]

Ah, apparently this forum doesn’t support emoji (cricket emoji, specifically …)

[andrew@bitfinder.co]

[andrew@bitfinder.co]

Ah, great, that makes it much clearer.

I had a few follow-up questions, then:

Does the conduit listen on all of those 8+1 channels simultaneously? So if an end node transmits, assuming the channel mask is set correctly and there is no collision and no TxTimeout, then the Conduit should receive it?

And I assume that the Conduit will set the matching 8+1 channel mask for the selected sub-band to the end nodes?

And lastly: If there is only one 500Khz uplink channel available, and my end node is only sending long payloads, does that imply that it will always be on a single 500KHz width uplink channel?

[Author]

Posts