-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operating on 433MHz #24
Comments
I've never tried. The sx1276 I use should be programmed just like the sx1278, it is the same datasheet... Do you see the text "Unknown radio:' in the logging? If you don't, communicating with your SX1278 is working correctly. It is a check of the chip type, and according to the datasheet it should return 0x12 for SX1276/77/78/79. I would expect that it should just work... |
I just did a quick test: I configured a gateway to listen on 433.175Mhz and hacked a node to use 433.175Mhz for channel 0 too. It seems to work for my SX1276 based gateway... Even with 868Mhz antennas on my gateway and node...
|
I've looked into it: TTN does not support 433Mhz (yet). I guess you have to use another network, or run your own, to use a 433Mhz gateway and nodes. |
Hi @JaapBraam , Thanks for your reply. Glad you quickly tested yourself, that software wise it should work. I was on the same impression. When I misconfigured the NSS setting in the Config.lua, yes I saw the Unrecognized transceiver = 255 message, but after finding out the correct naming convention, this has disappeared. You are right, I am not using it on TTN, but on the openlora backend, which supports the 433 MHz frequency band networks also. But at this stage this is not relevant, since first I should see the above rxpk packets on the gateway, which would state radio wise I am ok. In the gateway I see timeouts, but nothing more:
I suspect my node module (RN2483) is sending messages, beacuse on 868 MHz it did (with an another gateway on the other end), just reconfigured it to use the 433MHz band, and enabled only one channel, channel 0 for 433.175 MHz operation. Do you have an idea, how more intensive logging can be enabled, so maybe I can find the reason of not seeing the packets? |
Strange... now I set the gw to listen on a single SF, SF7, and I can see the packets...
|
Have you changed the antenna on your node for a 433Mhz one? What antenna are you using on your gateway? On the gateway, there is not much extra logging you can enable, because it already works on the limit timing-wise. A good test to do is to try listening only to a single SF (CONFIG.GW_SF='SF7'). This mode is much less critical timing wise. |
The packet I received on 433Mhz was on a gateway in 'ALL' SF mode. So it can work... The rx timeouts in the logging indicate that LoRa signals were detected, but too late. Maybe the frequency you configured is also used for other transmissions in your area. The allSF mode depends on RSSI measurements and thus will react to any signal present. In single SF mode the SX chip will only look for LoRa signals... If you use another frequency you might have more luck... |
Or you can make your gateway less sensitive by increasing the RSSI threshold used for signal detection. https://github.com/JaapBraam/LoRaWanGateway/blob/master/src/SX1276.lua#L366 This will probably decrease the range of your gateway on higher SF's, but will also make it more tolerant for interfering signals. |
Well the antenna is the one shipped with the module. This is a non well known and used, chinese module. Bought it cause it has SMA connector on the module and they shipped with antenna for a bit less than 10 USD. For the first trial I will make expriments on single SF, since that seems to work for now. After modifying the backend to use in the downstream RX1 windows I could successfully join. :-)
And sending packets also works solid rock. So you're saying that when in allSF mode, the receiver is configured to listen to any kind of radio modulation, not only LoRa modulation on the configured frequency? Can't we configure the LoRa module to listen to only LoRa modulated packets and trigger to the DIO handlers? |
One more thing. I mentioned that I am using an ESP12E, but this is a plain ESP8266 board, not an nodemcu built development board. Maybe this is causing issues deep in the nodemcu firmware? |
In allSF mode, it uses RSSI detection to decide if trying a higher SF is useful. If there are other signals above this threshold present it will make the gateway try the higher SF's increasing the chance to miss the preamble of a lora message... When the preamble is missed, it usually results in a rx timeout... |
I've worked with 'bare' esp8266's too, and have never experienced differences from the Wemos d1 mini's I'm using now... |
Indeed, following your suggestion to increase sensitivity, as advised, I have modified the SX1276 lua script to a lower RSSI (38). Now in allSF mode the gateway is able to catch the LoRa modulation radio signals, and gateway forwards packet. |
Hi. I also have a problem with 433 MHz using my SX1276MB1MAS. The maximum node-to-node communication range that I can reach for 868, 915 and 433 MHz are 500 m, 500 m, and 20 m respectively. |
Dear @JaapBraam ,
I am trying your code on an ESP12E, so far so good, nodemcu firmware installed, files uploaded.
Since I have an SX1278 module (only low band ie. 433), I've modified the freq setting to 433175000.
Connections:
DIO0-ESP12E GPIO5 - Definition in code - 1
DIO1-ESP12E GPIO4 - Definition in code - 2
SCK - ESP12E GPIO14
MISO - ESP12E GPIO12
MOSI - ESP12E GPIO13
NSS-ESP12E GPIO16 - Definition in code - 0
Gateway registers with backend, and can see the regular stats messages.
But I don't see packets arriving from the node (RN2483, also configured for 433 band) to the gateway. Is this something that should work, or am I trying something that is not implemented? - yet :-)
Thanks. Cheers.
Tamás
The text was updated successfully, but these errors were encountered: