💬 Connecting the Radio

[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]

:bread: :bread: