433 MHz ESP 32 MQTT Gateway with proper antenna
Thanks for taking a look Mikeal,.
Here's my update:
I added a 47uF cap to the 3.3V input to the RA-01 Lora radios on both Node and Gateway, now the SF 12 long payload messages pass!
I tested various SF and BW and coding rates, I decided on the following for the "long-range mode". Typical use will be point-point mode, or gateway to 2 or 3 nodes max, no repeaters. Horizontal polarised yagi antennas.
MY_RFM95_FREQUENCY 433237500ul (its 1MHz away from my co-located standard mode gateway frequency and other local ISM users).
RFM95_MODEM_CONFIGRUATION RFM95_BW62_5CR45SF4096 (Typical time-on-air is around 4000ms.
MY_RFM95_ATC_MODE_DISABLED (to reduce traffic).
Passive mode = off.
MY_REPEATER_FEATURE = off.
CAD = Default settings.
Encrypton = Off
Signing = Off
Sleep = Off.
Further test planned:
I have been testing out the RA-02 433MHz Lora modules with the Mysensors implementation.
I setup a GPS node, reporting through the RFM95-MQTT gateway to Hassio.. All good it works well.
I hope to eventually run two Mysensors LoRa gateways, 1 local, high speed and with multiple nodes, and another, so-called long-range mode gateway for remote sensors or GPS tracking.
So I thought I would try some other Lora Phy settings in the hope to get better range between the mobile GPS node in my car and the gateway at home.
I am using BW 62.5KHz, CRC Coding 4/5, Spreading factor 2048CPS (SF11).
Messages can take up to 4 seconds long time on air.
I tried SF12 (4096CPS) and it doesn't completely work, for some reason some presentation messages fail (NACK) such as the internal presentation version message: (2.3.2).
I tried increasing the time-out setting, but It didnt really work, Im wondering is these long time-on-air messages are causing other time-out issues somewhere or perhaps certain payloads is causing issues.??
#define MY_TRANSPORT_STATE_TIMEOUT_MS (4*1000ul)
I would be very interested in your comments
MQTT Gateway Client - Last Will topic and feature.
It would be really nice if our controllers can know if the gateway disconnects.
I think this can be implemented in MyGatewayTransportMQTTClient.cpp
// Attempt to connect
if (_MQTT_client.connect(MY_MQTT_CLIENT_ID, MY_MQTT_USER, MY_MQTT_PASSWORD))
A theroetcical capacity using RFM 95 LoRa radios in 433 MHz ISM band:
Lora Config bandwith: 125 KHz.
ISM band 433.050 - 434.790 MHz.
Allows for these 5 "channels";
Each GW can handle 254 RF Nodes
254 x 5 RF channels = 1270 sensor nodes in any one geographical location. (including repeated nodes)?
Thanks for your reply.
Is there a document which describes the tree radio network transport design in detail?
I have taken look at the API and the mysensors Radio page.
I am keen to know if this is an CSMA or Aloha system and how the network can respond to higher traffics loads, channel occupancy and collisions etc.
Its a great project, I really like that the LoRa Phy has been leveraged to this.
Im a noobie as of this week.
I have a Mysenors MQTT gateway on ESP32 with a AI Thinker RA-02 (433 MHz) Lora modulation radio.
Its working well so far, I'm interested to know if anyone has created a multi-node network covering , say a town using this protocol on LoRa or RFM69 Phyisical layer?
I am wondering if I setup an Mosquitto MQTT broker on a VM instance on Google Cloud, link my gateway to it and mount the thing on a high site with a decent co-linear antenna (I have a Ham Radio License). How big of a coverage area could I build?
Perhaps I make a mobile Node reporting GPS RSSI and drive around?
Solar-powered repeater nodes in the trees?