[Tutorial] Raspberry Pi NRF24l01 direct connection

fets

Hi everybody,
I'm new in mysensors world and I would like to use my pi2 with direct connection to nrf24l01.
There is a new release of the arduino library but I can't find the raspberry one.
Somebody knows if it exists and where to find it ?

I also tried to find an example of using raspberry as mqtt gateway without success, any ideabut was not able to find an example

hek

You could probably run the old one.

Ideally I would like to have the same code-base for RPi but someone needs to help implement the HW-implementation-class.

fets

Thanks hek, i'll try to use old code but I didn't find anything about raspberry as mqtt client gateway.
If I succeed, and if not too late, i'll try to implement the new library

hek

If you do want to help out, have a look at the gateway-refactoring-branch. Opening up for different protocols over there (where MQTT should be one of them).

https://github.com/mysensors/Arduino/tree/gateway-refactoring

Fernando Arconada

hi everybody
@hek are you going to support Rpi + rf24 direct connection? I were playing with https://github.com/mysensors/Raspberry a bit and works (I opened a pair of tickets) but needs to be updated.
I also think that PiGateway should support MQTT I have created PiGatewayMQTT (It's just a prototype).
What will be the future of https://github.com/mysensors/Raspberry repo? abandoned in favor of any kind of gateway-refactoring-branch ?

thanks

jelluz

(solved)
Hi. Thanks a lot for this implentation and the helpful posts here!

I've got the gateway working with a tmp75 temperature sensor on an arduino. The nrf24 is sitting on the raspberry directly (CE pin 22), as a controller i'm using PiMatic. It works very nicely!

There is one small problem however. The PiGatewaySerial will only work if i have called PiGateway before (and closed it again). With working I mean picking up radio transmissions from my sensor node. Everything else seems normal (/dev/ttyPiGatewaySerial and radio details printout).

The details of both configurations might give a clue:

pi@raspberrypi ~/mysensors_rpi $ sudo ./PiGateway
Starting Gateway...
================ SPI Configuration ================
CSN Pin          = CE0 (PI Hardware Driven)
CE Pin           = Custom GPIO25
Clock Speed      = 8 Mhz
================ NRF Configuration ================
STATUS           = 0x0e RX_DR=0 TX_DS=0 MAX_RT=0 RX_P_NO=7 TX_FULL=0
RX_ADDR_P0-1     = 0xa8a8e1fc00 0xa8a8e1fc00
RX_ADDR_P2-5     = 0xff 0xc4 0xc5 0xc6
TX_ADDR          = 0xe7e7e7e7e7
RX_PW_P0-6       = 0x20 0x20 0x20 0x00 0x00 0x00
EN_AA            = 0x3b
EN_RXADDR        = 0x06
RF_CH            = 0x4c
RF_SETUP         = 0x23
CONFIG           = 0x0e
DYNPD/FEATURE    = 0x3f 0x06
Data Rate        = 250KBPS
Model            = nRF24L01+
CRC Length       = 16 bits
PA Power         = PA_LOW
[CALLBACK]0;0;3;0;14;Gateway startup complete.
read: 4-4-0 s=0,c=1,t=0,pt=7,l=5:22.9
[CALLBACK]4;0;1;0;0;22.9
read: 4-4-0 s=0,c=1,t=0,pt=7,l=5:22.9

after closing PiGateway and opening PiGatewaySerial i get this:

pi@raspberrypi ~/mysensors_rpi $ sudo ./PiGatewaySerial
Starting PiGatewaySerial...
Protocol version - 1.4
Created PTY '/dev/pts/3'
Gateway tty: /dev/ttyMySensorsGateway
================ SPI Configuration ================
CSN Pin          = CE0 (PI Hardware Driven)
CE Pin           = Custom GPIO22
Clock Speed      = 8 Mhz
================ NRF Configuration ================
STATUS           = 0x0e RX_DR=0 TX_DS=0 MAX_RT=0 RX_P_NO=7 TX_FULL=0
RX_ADDR_P0-1     = 0xa8a8e1fc00 0xa8a8e1fc00
RX_ADDR_P2-5     = 0xff 0xc4 0xc5 0xc6
TX_ADDR          = 0xe7e7e7e7e7
RX_PW_P0-6       = 0x20 0x20 0x20 0x00 0x00 0x00
EN_AA            = 0x3b
EN_RXADDR        = 0x06
RF_CH            = 0x4c
RF_SETUP         = 0x23
CONFIG           = 0x0e
DYNPD/FEATURE    = 0x3f 0x06
Data Rate        = 250KBPS
Model            = nRF24L01+
CRC Length       = 16 bits
PA Power         = PA_LOW
read: 4-4-0 s=0,c=1,t=0,pt=7,l=5:22.9
read: 4-4-0 s=0,c=1,t=0,pt=7,l=5:22.9
read: 4-4-0 s=0,c=1,t=0,pt=7,l=5:22.9
read: 4-4-0 s=0,c=1,t=0,pt=7,l=5:22.9
read: 4-4-0 s=0,c=1,t=0,pt=7,l=5:22.9
read: 4-4-0 s=0,c=1,t=0,pt=7,l=5:22.9
read: 4-4-0 s=0,c=1,t=0,pt=7,l=5:22.9
read: 4-4-0 s=0,c=1,t=0,pt=7,l=5:22.8

Notice how the CE pins of both SPI configurations are different!

I'm at the point that i want to daemonize the gateway. Which in fact i did, but the same problem persists. Before i hack the startup script to first run and close PiGateway before PiGatewaySerial, i was hoping that someone has an idea what i'm doing wrong.

Thanks in advance!

solved!
I have two RPIs (a Pi 2 B and a Pi B+), which both worked with the pyRF24 lib of TMRh20, so when i had a look in the source of the radio initialization of PiGatewaySerial and found this:

#ifdef __PI_BPLUS
	gw = new MyGateway(RPI_BPLUS_GPIO_J8_15, RPI_BPLUS_GPIO_J8_24, BCM2835_SPI_SPEED_8MHZ, 1);
#else
	gw = new MyGateway(RPI_V2_GPIO_P1_22, BCM2835_SPI_CS0, BCM2835_SPI_SPEED_8MHZ, 1);
#endif

When i changed it to:

#ifdef __PI_BPLUS
	gw = new MyGateway(RPI_V2_GPIO_P1_22, BCM2835_SPI_CS0, BCM2835_SPI_SPEED_8MHZ, 1);
#else
	gw = new MyGateway(RPI_V2_GPIO_P1_22, BCM2835_SPI_CS0, BCM2835_SPI_SPEED_8MHZ, 1);
#endif

and recompiled the gateways,it all started to work. After powerup everything runs :).

The Rpi that is connected now is the Pi 2 B. So i guess either i have my nrf25 wired differently then defined in this lib, or the precompiler was thinking i have a B+ connected. Or both.
I will find out when i get this also working on my B+.

ericvdb

Hi all,

I just followed the guide in the 1ste post, but i'm not able to compile this correctly.
Here's the output:

g++ -Wall -fPIC -Ofast -mfpu=vfp -mfloat-abi=hard -mtune=arm1176jzf-s -march=arm                                                                  v6zk -D BCM2835_PERI_BASE=0x -c RF24.cpp
gcc -Wall -fPIC -Ofast -mfpu=vfp -mfloat-abi=hard -mtune=arm1176jzf-s -march=arm                                                                  v6zk -D BCM2835_PERI_BASE=0x -c bcm2835.c
bcm2835.c: In function ‘bcm2835_init’:
bcm2835.c:1207:28: error: invalid suffix "x" on integer constant
bcm2835.c:1208:28: error: invalid suffix "x" on integer constant
bcm2835.c:1209:28: error: invalid suffix "x" on integer constant
bcm2835.c:1210:28: error: invalid suffix "x" on integer constant
bcm2835.c:1211:28: error: invalid suffix "x" on integer constant
bcm2835.c:1212:28: error: invalid suffix "x" on integer constant
bcm2835.c:1213:28: error: invalid suffix "x" on integer constant
bcm2835.c:1214:28: error: invalid suffix "x" on integer constant
bcm2835.c:1228:83: error: invalid suffix "x" on integer constant
bcm2835.c:1232:81: error: invalid suffix "x" on integer constant
bcm2835.c:1236:81: error: invalid suffix "x" on integer constant
bcm2835.c:1239:83: error: invalid suffix "x" on integer constant
bcm2835.c:1242:83: error: invalid suffix "x" on integer constant
bcm2835.c:1246:83: error: invalid suffix "x" on integer constant
bcm2835.c:1249:83: error: invalid suffix "x" on integer constant
bcm2835.c:1253:79: error: invalid suffix "x" on integer constant
Makefile:52: recept voor doel 'bcm2835.o' is mislukt
make: *** [bcm2835.o] Fout 1
g++ -c -o MyGateway.o MyGateway.cpp -Wall -Ofast -mfpu=vfp -lpthread -g -D__Raspberry_Pi -mfloat-abi=hard -mtune=arm1176jzf-s -D_TTY_NAME=\"/dev/ttyMySensorsGateway\" -D_TTY_GROUPNAME=\"tty\" -march=armv6zk -I. -Ilibrf24-bcm/
g++ -c -o MySensor.o MySensor.cpp -Wall -Ofast -mfpu=vfp -lpthread -g -D__Raspberry_Pi -mfloat-abi=hard -mtune=arm1176jzf-s -D_TTY_NAME=\"/dev/ttyMySensorsGateway\" -D_TTY_GROUPNAME=\"tty\" -march=armv6zk -I. -Ilibrf24-bcm/
g++ -c -o MyMessage.o MyMessage.cpp -Wall -Ofast -mfpu=vfp -lpthread -g -D__Raspberry_Pi -mfloat-abi=hard -mtune=arm1176jzf-s -D_TTY_NAME=\"/dev/ttyMySensorsGateway\" -D_TTY_GROUPNAME=\"tty\" -march=armv6zk -I. -Ilibrf24-bcm/
g++ -c -o PiEEPROM.o PiEEPROM.cpp -Wall -Ofast -mfpu=vfp -lpthread -g -D__Raspberry_Pi -mfloat-abi=hard -mtune=arm1176jzf-s -D_TTY_NAME=\"/dev/ttyMySensorsGateway\" -D_TTY_GROUPNAME=\"tty\" -march=armv6zk -I. -Ilibrf24-bcm/
g++ -c -o PiGateway.o PiGateway.cpp -Wall -Ofast -mfpu=vfp -lpthread -g -D__Raspberry_Pi -mfloat-abi=hard -mtune=arm1176jzf-s -D_TTY_NAME=\"/dev/ttyMySensorsGateway\" -D_TTY_GROUPNAME=\"tty\" -march=armv6zk -I. -Ilibrf24-bcm/
g++ -o PiGateway MyGateway.o MySensor.o MyMessage.o PiEEPROM.o PiGateway.o -Wall -Ofast -mfpu=vfp -lpthread -g -D__Raspberry_Pi -mfloat-abi=hard -mtune=arm1176jzf-s -D_TTY_NAME=\"/dev/ttyMySensorsGateway\" -D_TTY_GROUPNAME=\"tty\" -march=ar                                                                  mv6zk -I. -Ilibrf24-bcm/ -lrf24-bcm
/usr/bin/ld: cannot find -lrf24-bcm
collect2: ld returned 1 exit status
Makefile:60: recept voor doel 'PiGateway' is mislukt
make: *** [PiGateway] Fout 1

Done!

I'm using the 2015-05-05-raspbian-wheezy version complete with:

rpi-update
apt-get update
apt-get upgrade

Can anyone tell me what is going wrong.

Thx in advance.

ericvdb

I got it working, and by adding ser2net in the mix, you have a MySensors raspberry pi ethernet gateway.
The trick is not to update the RPi, just use the latest image.

Does anyone know if it is possible to connect the status LEDs to the RPi?

Anduril

Hi @ericvdb ,
could you please post your config for ser2net? I also tried to use my NRF24L01 connected to my RPi as ethernet gateway for MYSController, but all I got was an 'unable to bind port'.

ericvdb

in /etc/ser2net.conf i used:

9003:raw:600:/dev/ttyMySensorsGateway

where 9003 is the tcp port your controller needs to connect to.

Remember, this allows only 1 connection, so if you want to play with multiple controllers, you can, however 1 at a time.

Anduril

Don't see any difference to my old entry... but pasted yours and now it works. Thank you very much @ericvdb

ericvdb

you're welcome ;)

GrantsPi

@Vladut-Grecu - Thanks very much for the tutorial!! After a bit of trial and error I was able to get the Pi reading my two nodes with very good reliability.

I'm now trying to merge this RPi Direct Connection with the openHab With Serial Gateway that TimO was kind enough to post (http://forum.mysensors.org/topic/1194/tutorial-openhab-with-serial-gateway). I had openHab working well on the RPi using an Arduino nano serial gateway using that tutorial.

Running PiGatewaySerial in a terminal window yields the proper readings from the Arduino nodes but when I try to have openHab recognize the serial port "/dev/ttyMySensorsGateway" instead of the "/dev/ttyUSB99@115200" used in the openHab tutorial I get messages from openHab saying it could not open serial port '/dev/ttyMySensorsGateway'...

Just wondering if anyone else has tried to marry the two projects or has any suggestions. (Perhaps I should also post this in TimO's openHab thread...)

revoltec112

upload-3f496795-4ae3-4ed2-b533-3f5e9fd6283e

Hi I am a beginner
If I have something that's ok , I plugged in humidity and temperature sensor , and for what I have in front of ./PiGatewaySerial enter sudo ? ,
how to make the data visible in Domoticz please help

revoltec112

whether in the / dev file must be named ttyMySensorsGeteway ? if so how it developed and what it should contain

Daniel Oliveira

Hi @hek

I know that a lot if going on regarding the MySensors 1.6 but I would like to know the plans for the repo mysensors/Raspberry?

Is there any plans to keep developing it of merging it with the main libraries?

I would like to be able to run the latest version on my Pi and I'm more than willing to help making it possible :)

Cheers

hek

Hi @Daniel-Oliveira,

I've talked with @Anticimex and @thozza about it... We think it would be best to move the RPi build file and any eventual support libs into the main MySensors repo to keep it in sync with the rest .

Not sure if @thozza has begun working on some autoconf script or not (did you?). But I imagine he'd appreciate any help you can contribute with.

jpbabou

@jelluz
I have got he sme configuration between Arduiono et a PIGATEWAYSERIAL ?
How do you declare it into a controler like Pimatic (you says that it works fine)
Tkd for your advice

Mediacj

I'am trying to get this working on my Raspberry Pi 2 B with Raspbian but when using the setup.sh command I get this error:

bcm2835.c: In function ‘bcm2835_init’:
bcm2835.c:1207:28: error: invalid suffix "x" on integer constant
bcm2835.c:1208:28: error: invalid suffix "x" on integer constant
bcm2835.c:1209:28: error: invalid suffix "x" on integer constant
bcm2835.c:1210:28: error: invalid suffix "x" on integer constant
bcm2835.c:1211:28: error: invalid suffix "x" on integer constant
bcm2835.c:1212:28: error: invalid suffix "x" on integer constant
bcm2835.c:1213:28: error: invalid suffix "x" on integer constant
bcm2835.c:1214:28: error: invalid suffix "x" on integer constant
bcm2835.c:1228:83: error: invalid suffix "x" on integer constant
bcm2835.c:1232:81: error: invalid suffix "x" on integer constant
bcm2835.c:1236:81: error: invalid suffix "x" on integer constant
bcm2835.c:1239:83: error: invalid suffix "x" on integer constant
bcm2835.c:1242:83: error: invalid suffix "x" on integer constant
bcm2835.c:1246:83: error: invalid suffix "x" on integer constant
bcm2835.c:1249:83: error: invalid suffix "x" on integer constant
bcm2835.c:1253:79: error: invalid suffix "x" on integer constant
Makefile:52: recipe for target 'bcm2835.o' failed
make: *** [bcm2835.o] Error 1

Any idea what is going wrong? Thanks in advance!

wergeld

@Mediacj I too had this error. The only way I was ever to solve this was to take a fresh image of Wheezy and start from scratch there. No sudo apt-get updated/upgrade until after I built the lib.

[Tutorial] Raspberry Pi NRF24l01 direct connection

15

11.7k

11.2k

113.0k