RAK831: possible to use TTN LoRaWAN and LoRa-MAC(point to point) at the same time?

Hi all,

For RAK831 pi : Is it possible to use TTN LoRaWAN and LoRa-MAC(point to point, raw lora) at the same time? So one node private point to point to this gateway and other nodes pushing to TTN?
How to enable/add this with the RAK raspberry Pi image?

Rgds,
Frank

I doubt it, there are a whole host of additional chips on a gateway board that you’d have to re-configure.

It would be so so so much simpler to add a RAK811 or RAK4200 on to the serial port and just run your own C/Python/Whatever code alongside the rest of the stack. Then they’d both work at the same time.

That would only be the case if the two systems are using incompatible bands and settings. In some places that’s possible, in others there really aren’t many other legal choices for the bands.

The bigger issue is potential transmit conflicts - the gateway can only transmit one message at a time and TTN implements no mechanism to say that a given gateway’s transmitter will be busy so that a downlink can be assigned to another.

As such this would only be reasonable in very quiet circumstances, in a setting where TTN is busy doing such a thing would be detrimental to other users, especially other users who have also deployed gateways.

Huh?

The OP wants instructions on configuring his Pi + RAK831 to switch between being a LoRaWAN Gateway and P2P. Leaving aside the problem of downlinks as you mention, the single biggest barrier surely has to be writing the code to drive a SX1301 and the chips beyond it. Or hacking the packet_forwarder to see that it’s received a ‘special’ message and divert it elsewhere. And then hack it so it can take a ‘special’ downlink packet and transmit it.

You wouldn’t “switch” but rather do both at the same time

No work needed - a packet forwarder feeding two servers already exists. Each server just ignores the packets it cannot validate and decrypt. The non-LoRaWAN code simply has to be made to speak the Semtech packet forwarder protocol.

Again, no work needed, just give it a transmit request in the Semtech protocol