💬 Connecting the Radio

[LaMB95]

I m getting symbols when I send Hello World message from Arduino Uno to an Arduino Pro Mini (5V).
Yes I have put an input of 3.3V to the pro mini.
Baud rate used is 9600.
Any clue why this is happening? I can provide the code.

[mfalkvidd]

@LaMB95 are you using a Pro Mini 5V 16MHz or Pro Mini 3.3V 8MHz?

If the wrong variant is selected in the Arduino IDE, all timings will be off, including the timings for serial communication.

[LaMB95]

@mfalkvidd

I have an arduino pro mini 5V. But I have attached a breakout CP2102 usb connection to it. On the board there is a 3.3V point which I have plugged in as Vcc to the NRF24L01+ module.

To upload the code I have selected the 5V 16Mhz as processor.

[mfalkvidd]

@LaMB95 Interesting. I have never seen a 5V Pro Mini with 3.3V output. Where did you get it?

Try different serial speeds in the serial monitor and see if you get something readable.

[flopp]

This post is deleted!

[mfalkvidd]

This post is deleted!

[tboha]

@flopp :
No, it isn't that easy.
To improve your NRF, please have a look at https://forum.mysensors.org/topic/1851/extending-range-of-regular-nrf24l01.

I tried solution Nr. 2. It is easy to do and cheap. Improvements are noticeable but not dramatically.

In regard to effort it is worth trying.

If you aimed at changing NRF's frequency - no this is not possible at all. Base frequencies are selected within the chip itself and antenna resonant frequency has to match oscillator frequency.

[LaMB95]

@mfalkvidd Haha not really a 3.3 output I changed its input voltge to 3.3 hoping it would work.

But nevertheless I managed to solve the issue.
It seems to be an error in the Hardware serial.

Refer: http://forum.arduino.cc/index.php?topic=46458.0

The code bhagman has posted worked !

[LaMB95]

@mfalkvidd

It worked yesterday now I am back to the same problem.
What a wonder !

[napo7]

Hi !

It seems that the FRM69 library set the IRQ pin as optionnal. Can someone confirm that the IRQ pin is mandatory ?

[tekka]

@napo7 yes, it is mandatory since the driver is IRQ-dependent

[napo7]

Well, I had a look in RFM69 driver, and it seems that the interrupts handlers are never sets ?
Am I wrong ?

Edit : In facts, DIO0 is not used as an Interrupt source in RFM69 driver : it's a pin that informs the library that, either, a packet has been received, or , the frame we try to send has been sent.

So, the code doesn't use interrupts, but this pin is more a "Data available" pin.

[scalz]

@napo7
so, if data available or data sent, this can be an interrupt source for an mcu
It's enabled in the init there https://github.com/mysensors/MySensors/blob/development/drivers/RFM69/RFM69.cpp#L123

[napo7]

Yes I noticed it !
Since it didn't mention IRQ pin, I didn't seen it at first !

What misleaded me, is that on LowPowerLab forums, some users says that you can absolutely discard this interrupt and poll the radio frequently to ask if a packet is available.

[adamp237]

I had this working perfectly on my Arduino Uno. I soldered it up to my Arduino Nano and it seems to work ok, but I'm not getting any data sent. The serial says it's connected OK but never sends any motion 1s or 0s. My MQTT server shows the following: Client mosqsub/3449-raspberryp received PUBLISH (d0, q0, r0, m0, 'mygateway1-out/255/255/3/0/3', ... (0 bytes))

Any idea what is going on? I've tested the motion sensor separately and that is sending a high value to pin 3 no worries.

[gohan]

@adamp237
Enable debug on the node and add some more serial prints in order to see better in detail where the code runs and where not

[siddmon]

where can I find the picture for connecting NRF to arduino uno?

[mfalkvidd]

@siddmon to my knowledge, Arduino Uno the same pins as on Arduino Nano, Arduino Pro Mini and all other atmega328-based Arduino boards.

[siddmon]

@mfalkvidd Thanks and yes, they have the same pins, I didn't see Uno in the table so I google it and got incorrect instructions.
Now that I used the same as nano my node seems work

[mfalkvidd]

@siddmon great! Thanks for reporting back.

[nitroburn]

Little mistake in the text, I don't think dupont cables are made of bread.
"the antenna need to be single core inside, only one wire, not multi-wire breaded like you can find in common dupont cable (not good for antenna.)"
should be
"The antenna need to be single core inside, only one wire, not multi-wire braided like you can find in common dupont cable (not good for antenna)"

[mfalkvidd]

@nitroburn thanks! I've updated the page.

[nitroburn]

@mfalkvidd No problem, did make me a little hungry though.

[mfalkvidd]

[Grave]

Can anyone change the text for "Configuring MySensors for RFM69". When you want to use another pin for cs it´s not this code:

// #define RF69_SPI_CS 15 // If using a different CS pin for the SPI bus

but this

// #define My_RF69_SPI_CS 15 // If using a different CS pin for the SPI bus

[mfalkvidd]

@Grave thanks for pointing this out. From looking at the source code, it looks like it should be MY_RFM69_CS_PIN. I have updated the text. Could you check if I got it right?

[Grave]

Thanks, you are right.

[joseyapor]

which one is better RFM69 or NRF24L01+

[gohan]

The problem is that nrf24 have many crappy clones that have limited range and it is difficult to find the original ones. Rfm69 is slower but have better wall penetration and modules come in 3 frequencies.

[sundberg84]

Nrf24l01+ also drains less current when sleeping vs RFM69

[mfalkvidd]

@joseyapor neither is better. They are good at different things. See https://forum.mysensors.org/topic/3993/nordic-or-hoperf-radio/2 for an earlier discussion.

[RAD-X]

@mfalkvidd said in Connecting the Radio:

@Grave thanks for pointing this out. From looking at the source code, it looks like it should be MY_RFM69_CS_PIN. I have updated the text. Could you check if I got it right?

It looks like that MY_RFM69_CS_PIN is used only in develop branch.
Stable brach still using MY_RF69_SPI_CS.

[mfalkvidd]

@RAD-X both will work in the stable branch. See https://github.com/mysensors/MySensors/blob/28c4f3f19e7026f56fd9bbc61d566f770fd7a9d2/MyConfig.h#L935

[RAD-X]

@mfalkvidd
Hmm.... Is not that a reference to the development branch?
I think that right content for stable branch is: https://github.com/mysensors/MySensors/blob/master/MyConfig.h
If you don´t believe it, try to download a stable branch, unpack and search for string "MY_RFM69_CS_PIN".

[mfalkvidd]

@RAD-X yes, you are correct. Thanks for noticing.

I thought that if I selected the master branch on github and used the search function, the search results would only show hits from the selected branch. But it seems like this is not the case.

Linking to a specific line in a file doesn't work very well, because that line might move by later commits. That's why I select a specific commit to link to. But as you point out, my link points to a commit in the development branch.

The correct link is https://github.com/mysensors/MySensors/blob/8bb3cfb2e14214ae19e8531c989d1e81c9660614/MyConfig.h#L663 and there is indeed no support for MY_RFM69_CS_PIN.

I'll update the documentation again. The documentation is meant to reflect the current stable branch.

EDIT: Found this in the Github documentation:

Only the default branch is considered.

So there is no way to search in the stable branch.

[manutremo]

I have one question regarding the length of the 868MHz antenna. According to the theory, a the wavelength of a 868Mhz signal is 300/868 = 34.6 mm, so a quarter wave antenna should be 8.6mm long. The table above indicates 8.2mm. May someone confirm the correct figure, and also indicate how critical is that difference in terms of range?

[mfalkvidd]

@manutremo the speed of electromagnetic waves is slower in metal than in vacuum, that's why the length is shorter.

My experience is that the length doesn't need to be exact, but antenna theory is way too complicated for me to understand the details.

[manutremo]

Many thanks @mfalkvidd . That explains it.

While waiting for an answer I also found some sites which mention that the speed of electromagnetic waves is even slower if the conductor has an isolation layer around, which would further justify the difference.

Many thanks!

[mfalkvidd]

@manutremo I think that part is due to skin effect.

[manutremo]

@mfalkvidd Many thanks again... I learn new things every day.

[gvorster]

@manutremo said in Connecting the Radio:

I have one question regarding the length of the 868MHz antenna. According to the theory, a the wavelength of a 868Mhz signal is 300/868 = 34.6 mm, so a quarter wave antenna should be 8.6mm long. The table above indicates 8.2mm. May someone confirm the correct figure, and also indicate how critical is that difference in terms of range?

I tried 3 types of antennas with RFM69HCW 868mhz.

1. Just a 8.6 cm wire

2. helical antenna

1. sma antenna

Indoor in my appartement (one floor) it doesn't matter which one I use. All is working fine.
I tried 2 nodes in my metal mailbox 10 meters below which has 2 tiny holes.
One with helical antenna, one with sma antenna.

Gateway (using sma antenna) receives no data.

Testing two repeater nodes (1 helical, 1 sma antenna) near a window I receive data via both repeaters. Sometimes the repeater with sma antenna is not relaying messages for the node with the sma antenna.

In my situation, the helical antenna works better for me. I just buy them on ebay.

[gohan]

Maybe the sma antenna is for the wrong frequency and it's giving poor results.

[krisha]

There is a mini module of the NRF 24L01+. Unfortunately some pinouts on the web were not correct. Not sure if many people use that, but here is a pinout that worked for me: http://s2.electrodragon.com/wp-content/uploads/2014/12/NRF24-Mini-02.jpg

[manul]

Hi Team,

First of all, thank you for your amazing work! It does help a lot to sea a dream become true

I was wondering, it seems that I can't receive messages from NRF24 radio while arduino node is sleeping... I've read several testimonies in this way as well on forums. I did connect the IRQ of the transceiver to the PIN 2 of my arduino, and took this as event for exiting sleep mode, but it seems not to work.

Is there anything in the roadmap regarding this? It could be really amazing to be able to sleep the battery-powered arduino, and wake it up as soon a message is received by the radio.
Or maybe there is something I did not correctly. Is there a feature for this?

[mfalkvidd]

@manul it would indeed be amazing, but the radios consume so much power when listening that it is no use to sleep the mcu.

The smartsleep feature is the best alternative so far. documentation: https://www.mysensors.org/download/sensor_api_20#sleeping

[ricorico94]

Hi,
I'm interested in using long range sensors based on LoRa and I saw on this forum that LORA radios should be supported with the RFM95. But I did not see any explanation or advice on hardware, pins, etc.
Could anyone confirm that the type of radio to attach on the gateway and the sensor is like:
link to aliexpress RFM95 radio

I see the chip mentioned is "RF96", but I did not see that name on the forum..(it was SX1276 I think), so I don't know.
Regarding frequency, I uderstood from other websites that in France, the frequency should be 868MHz, correct ? No risk to interfere with EnOcean/Zwave devices ?

I see also that these RFM95 radios have many more pins than the NRF24L01 : should I use the same pins than for NRF24 and leave the others unused ?
and then in the sketch, use the #define RFM95 statement ? Is it all that simple ?

And then I install the RFM95 as a second MySensors gateway on my network (for instance as an ethernet gateway) ?

br,
Ricorico94

[peerv]

Hi ricorico94,
If you are interested in LoRa and how to connect the radio have a look at www.thethingsnetwork.org

[MattiMan]

Hello!
I would like to use NRF24+PA radio, but when I try to use it instead normal NRF24 radio in MQTT-gateway it just dont work. I cant make connection between sensors and gateway.

Normal radio works just fine, but the range is a bit short for me.

I tried the low power setting also, but no help.

What should I do to make it work?

I use Domoticz as my controller.

[mfalkvidd]

Welcome to the MySensors community @mattiman !
Could you post the debug logs of the node and the gateway? That's usually the quickest way to get a hint on what is wrong.

If you haven't already, you can also look at https://forum.mysensors.org/topic/666/debug-faq-and-how-ask-for-help/ which has recommendations on the most common problems and how to troubleshoot them.

People have also been helped by this: http://blog.blackoise.de/2016/02/fixing-your-cheap-nrf24l01-palna-module/

[pepson]

Hi
I use Arduino Pro Mini 5V and i want user radio RFM69HW. I must use logic level converter from 5V to 3.3V to connect radio or i can only reduce power from 5V to 3.3V to VCC ?
On this page is nothing describe that i must use logic level converter,...but some users on this page write that i must use:
https://www.openhardware.io/view/268/RFM69HW-interstitial-board-for-Arduino-Pro-Mini#tabs-comments

Now i have connected only with reduce power to 3.3V but my Arduino not working still time. Only some minutes to test...

[gohan]

It was already answered to you in another topic and if you read in the openhardware project it is clearly stated that it is meant for pro mini 3.3v. If you connected it to a 5v pro mini you most likely fried the RFM69 module.

[pepson]

I connect to 5V Arduino but i use AMS1117 to step down power 5v to 3.3V and radio still working.

[manutremo]

I have two of my nodes using rfm69hw and mini pro 5v 17mhz. I only step down the power line to 3.3v, the comms lines work just fine with 5v. I also remember reading somewhere that this is actually the case, even though the datasheet says the opposite.

[gohan]

I'd follow the datasheet and don't take the risk of frying the radio.

[manutremo]

They've been working for more than 6 months now as part of a test run and are not yet fried.

There is other people around reporting the same with at least the rfm69HW. I remember someone stating that the new models are more robust in this regard than older models, in spite of the manufacturer not yet stating 5v tolerance in the data pins.

In fact the datasheet never mentions 5v intolerance, and it does never actually mention a max voltage for the data pins, only for Vdd.

It seems like the board does something with the voltages in the data pins anyways, since if it was using the definitions of the logic levels (as a percent of Vdd) as they appear in the datasheet, it should not be able to communicate at all with a 5v arduino when powered at 3.3v and no logic level shifter on the data pins - but it does.

This doesn't mean this is good practice, directions in the datasheet are there for some reason and my nodes will eventually get a logic level shifter when they finally go into their final case. But reality is it seems at least RFM69HW can tolerate 5v for months without being fried.

[gohan]

still I would not advise someone to go ahead and use them without a level shifter as I would not take responsibility to damage someone else hardware 3.3V is still able to talk to 5V, depends on how large is the tolerance zone around the 2.5V grey zone of the arduino

[manutremo]

I would not expect anyone to put or take responsability on anyone for a piece of advice. I think we are here to help each other by sharing information and our own experiences.

The full picture should be more than clear at this point for anyone reading this and other threads, but I will clarify once more. Best practice is using the rfm69 family with a logic level converter when connected with a 5v arduino, given that as of today the manufacturer's datasheet is not 100% clear on this area. From a problem solving perspective, keep in mind, however, that should a converter not be in place for any reason, the setup might or might not work, so if it doesn't don't discard it as a cause but don't take it for granted at 100%. And even if it works, do plan for adding a converter.

[jkandasa]

@hek @mfalkvidd RFM95 radio part connection details are missing.

[maghac]

Is it possible to change any of the radio pins 9, 10, 11 to something else? The reason is that I'd like to use 4 PWM pins and currently I only have pins 3,5,6 available on my Pro Mini.

[mfalkvidd]

@maghac yes. Redefining for example the nss/cs pin is possible as described on the connecting the radio page.

For more exact i structions we'd need to know which radio you are using.

[maghac]

Thanks - I use NRF24 radios.

I found MY_RF24_CE_PIN which I redefined to pin 8 which worked absolutely fine.

The problem I have now is that now cannot use the Newbie PCB anymore

[mfalkvidd]

@maghac doh!
How about using a software pwm library instead? I have not tried any, but I have seen this before: https://github.com/Palatis/arduino-softpwm

[sundberg84]

@maghac cut the trace with a small knife and re-attach it with a wire.

[maghac]

@mfalkvidd Maybe I'll give that a try.

I think FOTA will fail as the bootloader will try to initialise the radio with the default pin, right? Then I'll need software pwm or recompile my own bootloader.

[gohan]

@maghac or go for dual optiboot

[maghac]

@gohan But then I would need additional hardware to use DualOptiBoot?

Anyone have any quick instructions on how to build a new custom version of MySensorsBootLoader using MY_RF24_CE_PIN = 8

I have access to ArduinoIDE on Windows or a Ubuntu 16.04 box.

[gohan]

@maghac yes, an spi flash chip. It is not a bad solution since the firmware is transferred during normal node operation and if it fails nothing bad happens.

[sundberg84]

@maghac - EasyPCB rev 10 will probably include spi flash

[alowhum]

It might be an idea for the "connecting the radio" page on MySensors to point to these handy boards:
https://www.aliexpress.com/item/Free-shipping-Nano-328P-IO-wireless-sensor-expansion-board-for-XBEE-and-NRF24L01-Socket-for-arduino/32298692903.html

Then people have to just plug in the NRF24 boards. And it also makes it much easier to connect lots of sensors. I wish I had known about these boards earlier, it would have saved me a lot of time.

[gohan]

It depends if you want to go with the nano or the pro mini like many nodes use

[KimmoHop]

Just noticed, that MySensors 2.2 changed default RF24 CS pin on Mega2560 from pin 10 to pin 53 (SS) I could not find any reference to the change from 2.2 change log nor from pull request (722)... No wonder RF24 worked with 2.1.1 but not with 2.2 on M2560.
Contrary to instruction above, I wanted to continue with old pins (same as on Uno) and set the pins explicitly to MY_RF24_CE_PIN=9 & MY_RF24_CS_PIN=10. Now transport seems quite good (with combined HW and SW ack, static GW address, no routers)

[mfalkvidd]

@kimmohop thanks for reporting. Looks like the change was introduced in commit b132a8a81e2ba6c81bcc6e2afce7513cdddbe193. I have added a message to the release notes.

[alowhum]

@gohan perhaps it can be added to the buying advice page? There the Nano is advised.

[mfalkvidd]

@alowhum which of the buing pages are you referring to? https://www.mysensors.org/store/buying_guide has the pro mini.

[alowhum]

@mfalkvidd: Yes that's the page I'm referring to.

[mfalkvidd]

@alowhum I'm confused. Could you clarify what you want us to change on that page?

[alowhum]

Add a link to: https://www.aliexpress.com/item/Free-shipping-Nano-328P-IO-wireless-sensor-expansion-board-for-XBEE-and-NRF24L01-Socket-for-arduino/32298692903.html

[alowhum]

While you're at it: maybe tell people about the NRF52 option?

[mfalkvidd]

@alowhum thanks. That does indeed look lika nifty solution. I'll add it.

For the nrf5x, I don't know which boards are user-friendly, and I haven't understood if MySensors nrf5x support is "production ready" yet or if it requires people to tweak or otherwise do special stuff to get a node working. I don't think I have seen anyone building nrf5x MySensors nodes yet.

[alowhum]

Lots of people have I think, check the NRF5 thread. I built my own first one this week (BME280 sensor). It rocks.

• Arduino with built in NRF24 for $3.
• The size of a postage stamp.
• Powerful enough to use the simple encryption functionality.
• Antenna socket: just plug in antenna for more range.

[skywatch]

Maybe it's just me, but in the first image of a pro mini the top row of pins seem to be reversed to what I normally see.....

[42isjustanumber]

My first post at mysensors.org. Sounds like a great tool. Tried to set up an MQTT Gateway with Hardware as described above, ESP8266 and RFM69W with 868 MHz, to connect some Technoline TX29DTH-IT temperature and humidity sensors, without success. ES8266 is working , connects with my wifi network and also connects to my mosquitto server. But I do not get any connection from RFM to technoline. Is there anyone out there who was able to get this running?

[Yveaux]

@42isjustanumber welcome to the forum!
MySensors uses its own protocol and is therefore not compatible with the TX29DTH-IT.
You can however build your own temperature and humidity sensors from examples on this website and start expanding your network from there!

[42isjustanumber]

@Yveaux: thanks for the information. I thought it's much easier. I heard about LaCrosse Gateway which seems to be able to connect to Technoline temperature and humidity sensors with Nodemcu and RFM69 hardware and connect it to FHEM. I wanted to have a more general approach and just forward data from technoline sensors via MQTT. But if this is a totally different protocol I'll have to look for another solution.

[gohan]

Mysensors is just taking care of transporting the data, if you have a sketch that can read data from any sensors, you can then send those values via mysensors to any controller supported.

[42isjustanumber]

That was my misunderstanding. I thought with the hardware and settings mentioned above, I would be able to read the data from any Technoline sensor. There's a YouTube video from Miika Kurkela explaining how to interpret the data from these sensors. But to be honest, I only unterstand half of it.

[gohan]

If you have a working code that works on esp8266, you can use it as a node or as a gateway with sensors and no radio module.

[joaoabs]

Hi, just to warn navigation that the above code for RFM69 seems to have a glitch:

#define MY_RFM69_FREQUENCY RF69_433MHZ doesn't compile but changing it to #define MY_RFM69_FREQUENCY RFM69_433MHZ it does. (missing the "M" in RF69_433MHZ).

[mfalkvidd]

@joaoabs thanks for noticing. I have updated the page.

[dmonty]

After running NRF24L01+ for a few years I recently decided to upgrade to several NRF24L01+PA+LNA (Antenna version) using the link from this page. Initially the performance was worse. Fail to find gateway, fail to send data and lots of NACKs. However eventually I was able to get them working. Below is a summary of tweaks and suggestions from various Mysensor Forum posts that helped stabilize my sensor network.

1. Add 47uf capacitor between 3v and ground pin on the transceiver.

2. Add plastic-wrap then a tinfoil shield as per other threads. Tinfoil needs to to touch the base of the antenna (ground).

3. My 5V switching power supply to the Arduino Nano was causing problems. Some sort of noise on the wire? When I disconnected the transformer and powered the arduino by laptop usb, the signal was much more reliable. So I added a 1000uf capacitor between ground and 5V coming from the transformer which filtered out the noise coming from the power supply. This is probably not applicable to battery powered devices.

4. Use static node addressing for each node - automatic addressing sometimes randomly make bad routing decisions bypassing repeater nodes and choosing far away nodes.
   // Far-from-gateway sensor node
   #define MY_NODE_ID 2
   // Parent is a repeater node
   #define MY_PARENT_NODE_ID 1
   #define MY_PARENT_NODE_IS_STATIC

5. Lower the power on the transceiver. Try each power level reboot the node and pay attention to: Setup speed, how many NACKs.
   // RF24_PA_MIN = -18dBm;
   // RF24_PA_LOW = -12dBm;
   // RF24_PA_HIGH = -6dBm;
   // RF24_PA_MAX = 0dBm
   #define MY_RF24_PA_LEVEL (RF24_PA_LOW)

6. Run the RF24 scanner example for a long time to find a channel that is free from noise. I ran it for a day to pick up neighbourhood noise and loaded the results into a spreadsheet to graph. Set the clearest channel on all my nodes. e.g.
   #define MY_RF24_CHANNEL (105)

7. In domoticz I lowered the ACK time from 1200 to 400 to avoid broadcast storms/collisions. On the nodes after each send or receive add a "wait(LONG_WAIT);" to allow ACKs to settle between transmissions ( e.g. 500ms).

8. Run a ping-pong test between two battery powered mobile nodes to find optimal locations for your gateway, repeaters and sensors. Find the outer limits and keep the nodes well within those limits. Try not to place a node at the outer range limit, add repeaters. Sometimes moving a few feet in one direction can have a big difference.

[alowhum]

@dmonty which hardware did you use? It sounds like you tried the old cheap model without shielding.

There are way better modules out there now which will give you far less trouble.

[gohan]

Agreed, the shielded modules can run at full power without any problem

[dmonty]

@alowhum @gohan - I used the non-shielded module found in the "Shopping Guide" on this page: https://www.mysensors.org/build/connect_radio. Used bought from the seller that the link took me to.

The Connecting the Radio page get's you up and running. Would be nice if the "Shopping Guide" - grouped optimal matching components into a plug-n-play style "Shopping Cart". e.g. Optimal recommended component groups for:

1. Gateway node.
2. Repeater node.
3. Sensor node.

a) usb powered.
b) transformer powered.
c) battery powered.
d) solar powered.

I think my next experiment may be to pick up the 3v regulated power sockets to see if they will help in increasing the power and range as I've read the 3.3v regulator on the Arduino Nano is not very good at powering the radio.

[alowhum]

That shopping guide (heck, most examples on the site) is often out of date.

I'd recommend checking out this thread:
https://forum.mysensors.org/topic/9668/cdebyte-s-new-nrf24-modules-are-great-and-cheap/26

For your nodes I'd highly recommend getting the "nano wireless board" from places like aliexpress. The radios just plug right into it.

For the Raspberry Pi there is also a really easy to use 'hat' that allows you to plug the NRF24 directly into it:
https://forum.mysensors.org/topic/9696/i-got-a-plug-and-play-nrf24-shield-for-the-pi-on-aliexpress

[FlyingDomotic]

Concerning RF24 Plus datasheet, it seems that a more recent version is available at https://infocenter.nordicsemi.com/pdf/nRF24L01P_PS_v1.0.pdf?cp=8_4_0_0

[mfalkvidd]

Thanks @FlyingDomotic
I have updated the page.

[dmonty]

A journal update on NRF24L01+PA+LNA (Antenna version). After 4-5 months two of them stopped transmitting. I had also purchase and installed the 3.3v regulator base socket to help improve overall transmission reliability.

Loaded the RF24 library GettingStarted example onto two arduinos connected to laptop and a desktop. Changed the code to match MySensors pinout and data-rate, along with a free channel found by the RF24 scanner example.

RF24 radio(9,10);

...snip...

  radio.begin();
  radio.setDataRate(RF24_250KBPS); 
  radio.setChannel(120);
  //radio.setPALevel(RF24_PA_MIN);
  radio.setPALevel(RF24_PA_LOW);
  //radio.setPALevel(RF24_PA_HIGH);
  //radio.setPALevel(RF24_PA_MAX);

I Moved laptop to far edges of the range and tried various power levels for NRF2L01 as well as the PA+LNA. Sketch default is RF24_PA_LOW which turns out to have the farthest range with the least packet loss and fastest turn around time packet time. I also cycled through the various radios to weed out the ones that were week. Even with the 3.3v base socket, a capacitor helps as well as cellophane+tinfoil on the PA LNA modules.

I then put one of the arduinos onto a battery pack and placed it next to each of my sensors. Then used the laptop to see packet loss next to repeater nodes and gateway. When near the edge of the range moving the antenna a few feet in different directions will cause packet loss. When a sensor is at the edge it is better to move radios closer to each other or a add a repeater. I thought PA LNA would be better in all locations but it turns out that the cheaper base radios sometimes perform better.

[gohan]

@dmonty did you use the shielded radio module?

[dmonty]

@gohan said in Connecting the Radio:

@dmonty did you use the shielded radio module?

Yes they are shielded.

I found another way to find optimal sensor location using an on/off loop script as a ping. Start the ping running then move the antenna to find best mount point location.

To find the strongest location it helps to find the weak-signal boundaries where packets are lost, then make sure the antenna is on the inside of the boundary. Move the antenna:

• X+, X-
• Y+, Y-
• Z+, Z-

#!/bin/sh
# Desc: Domoticz ping script to help find optimal location for sensor antenna.
# Auth: Dean Montgomery
# Date: April 21, 2020

# Url of domoticz server.
HOST="http://192.168.0.1:8080"
# ID=14 is device idx of a light switch found on the Divices page of domoticz.
ID=14

while true; do
  CMD="${HOST}/json.htm?type=command&param=switchlight&idx=${ID}&switchcmd="
  echo "=== ON ==="
  wget -q -O - "${CMD}On"
  sleep 1
  echo "=== OFF ==="
  wget -q -O - "${CMD}Off"
  sleep 1
done

It may help to include a dummy ping light switch in all sensor nodes dedicated for this purpose.

[cloolalang]

Tips for connecting the LoRa Radios:

1. Use de-coupling capacitor on power supplies (as per above other radios).
2. Carefully select: MY_RFM95_TX_POWER_DBM and MY_RFM95_MAX_POWER_LEVEL_DBM as Semtech spec states +20dBm output power is only for 1% duty cycle operations, and some modules (AI-Thinker RA-02) are only rated as +18dbm.
3. If you build a LoRa radio gateway using an ESP32 (for example), take care to provide a separate, low-noise 3.3V power supply to the radio as the on-board voltage regulator may not be able to supply enough current at the higher RF output power levels.