RFM69 new driver delay

[gohan]

RPI gw uses new driver only. I am sticking to 2.2 for now as I had some timing issues with the RPI3, if you make a gw with an arduino it would probably work better with 2.3

[pepson]

@gohan
I want use gateway on RPI because i use special project PCB for gateway on RPI3.
But on MySensors 2.2.0 i also use NEW DRIVER and all works ok. But why not works on 2.3.0 ?

[gohan]

If I got it right it is related to RPI3, on RPI2 it should work

[pepson]

@gohan
From where you have this information?
Is any chance to fix this problem?

[gohan]

I was talking to @tekka some time ago about the issues I had on 2.3 alpha, I don't know what he did after that.

[pepson]

@gohan
And where we can send issue with this?

[gohan]

github and if you attach the rfm69 verbose output both for gw and node

[pepson]

@gohan
But how I can download info from gateway and node?

On github created issue but nothing replay from developers...

[mfalkvidd]

@pepson all core members are helping MySensors when they have free time. Quick replies can happen, but don't count on it. We have as many projects and as little time as you.

[pepson]

@mfalkvidd
OK thanks

[mickecarlsson]

I run mysgw 2.30 on a RPi 3 Model B and all nodes on 2.20 with RFM69:

cat /proc/cpuinfo
.
.
Hardware	: BCM2835
Revision	: a02082

I did a git pull then configured:

./configure --my-transport=rfm69 --my-is-rfm69hw --my-rfm69-frequency=868
make
sudo make install

Note that I don't use LED's or specify gateway. My Controller is Domoticz

I then started the gateway with debug (note missing -d) (and the log is from today):

pi@mysensors-gw:~ $ sudo /usr/local/bin/mysgw 
Jun 21 06:36:58 INFO  Starting gateway...
Jun 21 06:36:58 INFO  Protocol version - 2.3.0
Jun 21 06:36:58 DEBUG MCO:BGN:INIT GW,CP=RPNGL---,VER=2.3.0
Jun 21 06:36:58 DEBUG TSF:LRT:OK
Jun 21 06:36:58 DEBUG TSM:INIT
Jun 21 06:36:58 DEBUG TSF:WUR:MS=0
Jun 21 06:36:58 DEBUG TSM:INIT:TSP OK
Jun 21 06:36:58 DEBUG TSM:INIT:GW MODE
Jun 21 06:36:58 DEBUG TSM:READY:ID=0,PAR=0,DIS=0
Jun 21 06:36:58 DEBUG MCO:REG:NOT NEEDED
Jun 21 06:36:58 DEBUG Listening for connections on 0.0.0.0:5003
Jun 21 06:36:58 DEBUG MCO:BGN:STP
Jun 21 06:36:58 DEBUG MCO:BGN:INIT OK,TSP=1
Jun 21 06:37:18 DEBUG GWT:RFC:C=0,MSG=0;0;3;0;2;
Jun 21 06:37:18 DEBUG GWT:RFC:C=0,MSG=0;0;3;0;2;Get Version
Jun 21 06:37:20 DEBUG GWT:RFC:C=0,MSG=0;0;3;0;18;PING
Jun 21 06:37:30 DEBUG GWT:RFC:C=0,MSG=0;0;3;0;18;PING
Jun 21 06:37:37 DEBUG TSF:MSG:READ,22-22-0,s=1,c=1,t=0,pt=7,l=5,sg=0:23.3
Jun 21 06:37:37 DEBUG TSF:MSG:READ,22-22-0,s=2,c=1,t=1,pt=7,l=5,sg=0:48.0

After the debug check I pressed ctrl-c and started mysgw as a service

sudo systemctl start mysgw.service

System has been running without any hickup since then.

If you check the commit 2175c993ef81b78527c85649f5bdc3585d2f41b2 you will notice that -d is removed and some other features has been added.

git log 2175c993ef81b78527c85649f5bdc3585d2f41b2
commit 2175c993ef81b78527c85649f5bdc3585d2f41b2
Author: Marcelo Aquino <marceloaqno@users.noreply.github.com>
Date:   Fri Mar 23 07:00:34 2018 -0300

    Linux: Use config file for gateway settings (#1061)
    
    - The following settings can be use on the config file:
      - verbose=[debug,info,notice,warn,err] - Logging verbosity.
      - log_file[0|1] - Enable logging to a file.
      - log_filepath=(FILE) - Log file path.
      - log_pipe=[0|1] - Enable logging to a named pipe(aka fifo).
        Use this option to view your gateway's log messages from the
        log_pipe_file (defined below).
        To do so, run the following command on another terminal:
        - $ cat "log_pipe_file"
      - log_pipe_file=(FILE)
      - syslog=[0|1] - Enable logging to syslog.
      - eeprom_file=[/etc/mysensors.eeprom]
      - eeprom_size=[1024]
    - Change some mysgw parameters:
      - Added:
        - -q, --quiet:  for quiet mode, disable log messages written to the
        terminal.
      - Removed:
        - -d, --debug: removed, log messages are now enabled by default.
      - Replaced:
        - -b, --background: replaced by --daemon
    - isatty() is no longer used, log messages by default are printed to
      stderr unless the gateway is started with --quiet (#1022)
    - MY_LINUX_CONFIG_FILE: no longer holds the path to the eeprom file,
      but to the configuration file

My nodes has these definitions (I don't use New Driver):

#define   MY_SPLASH_SCREEN_DISABLED
// Enable and select radio type attached
#define   MY_RADIO_RFM69
#define   MY_IS_RFM69HW
#define   MY_RFM69_FREQUENCY RFM69_868MHZ

[pepson]

@mickecarlsson

Hi
But you run gateway on 2.3.0 and node on 2.2.0 without NEW DRIVER and it was working ?
Even though the gateway has a different version and nodes have a different ?
All people tell that gateway and nodes must have the same version ?

[gohan]

There have been versions in the past that were not backward compatible, but usually it is not necessary to have same version on gw and nodes

[pepson]

@gohan

Ok thanks

[mickecarlsson]

@pepson
Yes, I run gateway 2.30 and nodes on 2.20 without new driver. No probems.

[pepson]

Today i installed Gateway on RPI3 with version 2.3.0 but node has 2.2.0 with NEW_DRIVER and still is problem with communication.

After come back to home i test it with change version on node to 2.2.0 without NEW_DRIVER.

I give you and info...

But tell me on what RPI you have run gateway version 2.3.0 ?
I have RPI3 version B.

[mickecarlsson]

@mickecarlsson said in RFM69 new driver delay:

> cat /proc/cpuinfo
> .
> .
> Hardware	: BCM2835
> Revision	: a02082

Type as above and check the last entries, my RPi is revision a02082
Se here for more info:
Raspberry Pi revision codes

[pepson]

@mickecarlsson
It is the same hardware and rev.
Ok i done test...
On Gateway on RPI3 i have installed MySensors 2.3.0

On node i installed version 2.2.0
One with NEW_DRIVER. Communication with gateway sometimes is ok but still with problem lost communication.

Second test installed on node 2.2.0 without NEW_DRIVER and it no working. No communicate with gateway.
Not working NODE. Any reaction to control relay.

For me only all working when i have MySensors 2.2.0 also on Gateway and also on node with NEW DRIVER option.

// Enable and select radio type attached
#define MY_RADIO_RFM69
#define MY_IS_RFM69HW
#define RFM69_868MH
#define MY_RFM69_NEW_DRIVER


other 


// Enable and select radio type attached
#define MY_RADIO_RFM69
#define MY_IS_RFM69HW
#define MY_RFM69_FREQUENCY RFM69_868MHZ

[mickecarlsson]

What kind of antenna do you have on the RPi for the radio? And what kind of antenna do you have on the node?

[pepson]

@mickecarlsson

I have a wire length if I remember 82mm.