simulate multiple LoRa transmitters...

[Bastlerstube]

I use a TTGO LoRa32-OLED V1.0 ESP32 ( EU868 ) to which other ESP32s without LoRa are connected via Modbus RS485.

Is there a way to modify the LMIC to simulate multiple LoRa transmitters transmitting in sequence with different APPEUI, DEVEUI and APPKEY ?

I would start several LMIC instances that go through one after the other and send and receive the data received from the Modbus via LoRa.

In principle I see no problems with Class A devices, there, I just need to understand how the LMIC works with the timing when "os_runloop_once();" is called to make the necessary modifications there at the point.

You as experts of the library can you please tell me if I imagine it too easy or if it is relatively easy to implement after all?

Background is an apiary with several hives, which should be kept largely free of any radio pollution. That is why modbus and power supply are transmitted via a fixed cable and the hope for less problems, if not several Lora transmitters in a confined space interfere with each other.

[terrillmoore]

I would keep things simple, and let the library get idle after a given transmission. (Don't try to interleave Class A uplinks from different virtual devices.) Remember that your radio must comply with uplink limitations; the LMIC doesn't separate that kind of data from other data, so you can't swap everything out. Would be nice if it did, but...

However, if you ignore those phy-level details, and keep a copy of LMIC for each virtual device, and only swap when the LMIC is idle (has no pending jobs), it should work. A pure swap would give you n different virtual radios, but no guarantee that the physical radio is complying. Handling this properly would require an enhanced phy radio driver that enforces duty cycle regs. (This might simplify the LMIC, but ...)

Barring that -- it looks like you could keep LMIC.band[] as a "common" item for EU868, along with LMIC.globalDutyAvail, and you'd get pretty close. But all bets are off if you're using multiple networks, etc. (I've thought about this for redundancy; use a commercial network as a fallback to a free network, for example.)