How to not interfer with TTN etc on my Chirpstack test system

Im new to Lorawan.
I really like the Chirpstack project, it was pretty easy to setup on my R Pi with Ubuntu.

I am looking to build a Lorawan compliant system for a small node-count (under 25) and for an area of about 1km2 in an urban area.

I would like to design it such that it is likely to cause as little interference to other systems particularly TTN which has quite a few gateways in the location and use low-cost single-channel forwarders.

I would be very interested to learn if anyone has done this and what configs have been used:

Things I have considered so far:

  1. Use standard duty cycle rules , or lower power node <10dBm ERP
  2. Use non-TTN frequencies (868.7, 868.9 MHz) and/or not using channels 0,1,2
  3. use non-TTN spreading factors for either fixed SF or ADR
  4. RX2 use non-TTN frequency
  5. Link budget ERP plan for 1km2
  6. Use LBT for reduce collisions and time on air - if possible
  7. Use >2 single-channel “gateways” for better coverage and down-link duty-cycle limit sharing, is that possible?
  8. Careful use of class A, B C devices
  9. No confirmed uplink messages
  10. No gateway pings
  11. compressed/reduced payload design
  12. Multi-cast?
  13. activation? ABP only?

Im really trying to scope out if a lorwan-lite is a thing.


I think you may be overthinking this. There is no problem with overlapping LoRaWAN networks in the same area. As long as none of your devices are registered on TTN, transmissions like joins, uplinks, etc will go ignored and unanswered.

1 Like