💬 Building a Orange Pi Gateway

[pansen]

@marceloaqno: ok so here are my conclusions:
After going through the schematics of the OPi Plus2e I realized that the H3 has dedicated pins for NAND/eMMC, which is probably not the case for the H2+ in the OPi zero. They used the pins of SPI1 for a status LED and a "MUTE" net, which is not connected anywhere so at first I was like "wtf?"...
So, the SPI0 is free for usage out of the box and the .fex does not need to be modified. Summed up:

If the OPi to be used has "SPI0" in the GPIO header, no .fex modifications are necessary. CE and CN/CS/CSN pin can be chosen freely (?), I picked it like this:
ce - gray - pa13 - PHYSICAL pin8 - LOGICAL pin13 (1-1)*32 + 13
cn - blue - pa14 - PHYSICAL pin10 - LOGICAL pin14 (1-1)*32 + 14
If another pin is chosen, the pin number can be calculated with that formula: (position of letter in alphabet - 1) * 32 + pin number (from: https://linux-sunxi.org/GPIO)
The pinout of the connector can be found here: https://linux-sunxi.org/Xunlong_Orange_Pi_Plus_2E#Expansion_Port (SPI0 pins are PC0-PC2 or 19,21,23)
After connecting the physical pins 8,10,19,21 and 23 to the nrf24 (and pin 1 for 3.3v), following command was sufficient to set up mysgw and get the nrf24 to respond:
./configure --spi-spidev-device=/dev/spidev0.0 --my-transport=nrf24 --my-rf24-ce-pin=13 --my-rf24-cs-pin=14

[lecintre]

hello
I build this and work great for my OrangePI PC+ but I do not know how to integrate it in domoticz???
Can you help me please
thank's for you good work

[pansen]

@lecintre: I just installed domoticz and I could enable my gateway by clicking on "please setup your Hardware" in the start screen, then selecting "mysensors gateway with lan interface" with the lan ip of my orange pi (but i guess 127.0.0.1 would also work) and port 5003.
this should appear then:
mysensors_lan_gw Yes MySensors Gateway with LAN interface
Version: 2.2.0-beta Setup 0.0.0.0 5003 Disabled

clicking on "Setup" then leads to a menu where i see my first test node:

NodeID
Name
Sketch Name
Version
Children
Last Seen
0 Unknown Unknown 1.0 1 2017-01-29 20:27:28
1 Unknown nrf24LEDtest 1.0 2 2017-01-29 20:28:27

let me know if that works out for you

[lecintre]

@pansen: Thank you very much it works very well.
Cool for your help
thank you so much
For you which is the best domoticz or jeedom ?? With mysensors protocol

[pansen]

@lecintre: avec plaisir :) I only compared OpenHAB and domoticz so far. Domoticz worked out of the box with the nrf24 but does not have support for my 5.1 receiver (which OpenHAB does). Jeedom looks to commercial (for example no free app+controller) for my taste and there seems to be no community. A good starting point for me was the popularity of each controller in this forum: https://forum.mysensors.org/category/3/controllers

I guess it really depends on your application, if you only have DYI sensors and actuators, domoticz is probably enough.

[Yveaux]

@marceloaqno Great job man!
Looking at the radio connection, there is a 5V -> 3V3 conversion layed out.
The Pi Zero Schematics sheet 7-D1, 7-B5 and 11-D4 indicate VCC3V3-EXT is present on pin 1 of the IO connector and internally connected to VCC-IO, which can supply 1A @ 3V3.
Don't you think there is enough margin to supply the nRF24 directly from VCC3V3-EXT?

[marceloaqno]

@Yveaux Yes, more than enough :smile: . Thanks and thanks for pointing that out.

[scalz]

i've not checked yet, i miss time for trying the linux port :blush: but i'm curious to know if this power supply would be noisy..which may need a ferrite and capas, else radio could have a bad snr and less range/sensitiviy. Maybe i'm wrong.. i'll try to scope when i'll have some time, or if i remember about it lol!

[SdeWeb]

@pansen Hi, Please could you confirm your pin connection beetween NRF24L01 and the Opi Plus2E, il followed your setup inctruction (no .fex modification and your specific ./configure), but mine don't work, i got this error "mysgw: Could not open /sys/class/gpio/gpio13/direction".

I connected my NRF24L01 on OPI P2E like this :

• NRF Port Name / (N°) ------- OPI Port (N°) / Name
  • GND (1) <------------> (6) GND
  • VCC (2) <------------> (17) 3.3V PWR
  • CE (3) <---------------> (8)
  • CSN (4) <------------> (10)
  • SCK (5) <-------------> (23)
  • MOSI (6) <-----------> (19) MOSI
  • MISO (7) <-----------> (21) MISO
  • IRQ (8) <---------------> NC

Thanks.
Seb.

[pansen]

Hi @SdeWeb header pins 8 and 10 are used by some other hardware (SPI1, UART3) which might need to be deactivated in the .fex in your system, for me it worked straight away so that would be weird..just check the .fex if SPI1 and UART3 are indeed disabled.

It looks like the definitions for the GPIO are faulty, you could try a LED test to see if they work at all. If the problem persists rather open a topic in the Development sub forum 8) Or, pick another GPIO, for example header pins 14 and 16.

[Wascht'l]

Hello,
would it be possible to add the wiring for the RS485-Modules, please?
will it be similar to the Raspberry Pi?
Thank you. Waschtl.

[SdeWeb]

Hi,
Well done finally i used the dedicated .fex file for Orange Pi Plus 2E here :
https://linux-sunxi.org/Xunlong_Orange_Pi_Plus_2E#Expansion_Port

at this point :
https://github.com/igorpecovnik/lib/blob/master/config/fex/orangepiplus2e.fex

Read the .fex file in a text editor, u'll see important things about "gpio_config" for H3 cpu :

; NOTE: This section is necessary only for "gpio_sunxi" driver
; which is obsolete for H3 boards
[gpio_para]
gpio_used = 0
gpio_num = 0

I connected my NRF24L01 on OPI P2E like this :

NRF24L01 Port Name / (Pin N°) ----- OPI Port (Pin N°) / Name
                      GND (1)  <-----------> (20) / GND
                      VCC (2)  <-----------> (17) / 3.3V PWR
                      CE (3)   <-----------> (22) / (PA2 / GPIO2)
                      CSN (4)  <-----------> (24) / (PC3 / GPIO67)
                      SCK (5)  <-----------> (23)
                      MOSI (6) <-----------> (19) MOSI
                      MISO (7) <-----------> (21) MISO
                      IRQ (8)  <-----------> NC

So "MySensors" setup is :

./configure --spi-spidev-device=/dev/spidev0.0 --my-transport=nrf24 --my-rf24-ce-pin=2 --my-rf24-cs-pin=67

Then

./bin/mysgw -d

Return :

root@orangepiplus2e:~/MySensors# ./bin/mysgw -d
mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0-beta
mysgw: MCO:BGN:INIT GW,CP=RNNG---,VER=2.2.0-beta
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: MCO:REG:NOT NEEDED
mysgw: Listening for connections on 0.0.0.0:5003
mysgw: MCO:BGN:STP
mysgw: MCO:BGN:INIT OK,TSP=1

Best.
Seb.

[SdeWeb]

@Wascht'l Hi,
Take a look here, to get some idea :

https://fr.pinout.xyz/pinout/rs485_pi#

Regards.

[Reza]

i have problem :/
what about this :

root@orangepione:~/MySensors# ./configure --spi-spidev-device=/dev/spidev0.0 --my-transport=nrf24 --my-rf24-ce-pin=2 --my-rf24-cs-pin=13                       
 -bash: ./configure: Permission denied
root@orangepione:~/MySensors#

[Tag]

@Reza
Seems your ./configure script is not executable... try:

chmod 755 ./configure

[Reza]

@Tag

root@orangepione:~/MySensors# chmod 755 ./configure
root@orangepione:~/MySensors# chmod 755 ./configure --spi-spidev-device=/dev/spidev1.0 --my-transport=nrf24 --my-rf24-ce-pin=2 --my-rf24-cs-pin=13
chmod: unrecognized option '--spi-spidev-device=/dev/spidev1.0'
Try 'chmod --help' for more information.
root@orangepione:~/MySensors#

[SdeWeb]

@Reza
after "chmoded" the file you don't need anymore chmod command, run directly ./configure .

Regards

[Reza]

@SdeWeb thank you . this is ok

[Reza]

can i add this lines ? for orangepi ?

#define MY_RF24_PA_LEVEL RF24_PA_MAX
#define MY_RF24_CHANNEL 0

but after add i have problem :

root@orangepione:~/MySensors# make
gcc -MT build/drivers/Linux/log.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_IS_SERIAL_PTY  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -c drivers/Linux/log.c -o build/drivers/Linux/log.o
g++ -MT build/drivers/Linux/noniso.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_IS_SERIAL_PTY  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -c drivers/Linux/noniso.cpp -o build/drivers/Linux/noniso.o
g++ -MT build/drivers/Linux/Print.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_IS_SERIAL_PTY  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -c drivers/Linux/Print.cpp -o build/drivers/Linux/Print.o
g++ -MT build/drivers/Linux/EthernetClient.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_IS_SERIAL_PTY  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -c drivers/Linux/EthernetClient.cpp -o build/drivers/Linux/EthernetClient.o
g++ -MT build/drivers/Linux/SerialPort.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_IS_SERIAL_PTY  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -c drivers/Linux/SerialPort.cpp -o build/drivers/Linux/SerialPort.o
g++ -MT build/drivers/Linux/Stream.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_IS_SERIAL_PTY  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -c drivers/Linux/Stream.cpp -o build/drivers/Linux/Stream.o
g++ -MT build/drivers/Linux/IPAddress.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_IS_SERIAL_PTY  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -c drivers/Linux/IPAddress.cpp -o build/drivers/Linux/IPAddress.o
g++ -MT build/drivers/Linux/compatibility.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_IS_SERIAL_PTY  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -c drivers/Linux/compatibility.cpp -o build/drivers/Linux/compatibility.o
g++ -MT build/drivers/Linux/SoftEeprom.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_IS_SERIAL_PTY  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -c drivers/Linux/SoftEeprom.cpp -o build/drivers/Linux/SoftEeprom.o
g++ -MT build/drivers/Linux/EthernetServer.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_IS_SERIAL_PTY  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -c drivers/Linux/EthernetServer.cpp -o build/drivers/Linux/EthernetServer.o
g++ -MT build/examples_linux/mysgw.o -MMD -MP -march=armv8-a -mtune=cortex-a53 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_IS_SERIAL_PTY  -Ofast -g -Wall -Wextra  -I. -I./core -I./drivers/Linux -c examples_linux/mysgw.cpp -o build/examples_linux/mysgw.o
In file included from examples_linux/mysgw.cpp:73:0:
./MySensors.h:258:2: error: #error No support for nRF24 radio on this platform
 #error No support for nRF24 radio on this platform
  ^
In file included from ./drivers/RF24/RF24.cpp:23:0,
                 from ./MySensors.h:294,
                 from examples_linux/mysgw.cpp:73:
./drivers/RF24/RF24.h:52:17: fatal error: SPI.h: No such file or directory
compilation terminated.
Makefile:98: recipe for target 'build/examples_linux/mysgw.o' failed
make: *** [build/examples_linux/mysgw.o] Error 1

[Tag]

@Reza

Are you sure your git environment is okay?
Maybe do a fresh git pull for mysensors?
See the howto on the orangePI page just follow from the start.... I have serious questions that your env is correct since configure was not executable....