Raspberry gateway RFM95 no receive

  • Raspberry RFM95 gateway

  • Mod

    Welcome to the MySensors community @Anders !

    If you haven't already checked it out, https://forum.mysensors.org/topic/666/debug-faq-and-how-ask-for-help/ has a flow chart on how to efficiently troubleshoot the most common problems, and information on what information will help to determine what is wrong.

    Clould you describe what you have done so far, what results you expected and what results you got?

  • Hello mfalkvidd

    My goal is to move my two gateways to my raspberry pi 3 so I can free up some hardware.
    I was inspired by various treads in forum to try dual radios with two separate mysensors instances on the pi .

    What I have today:
    ESP8266 with NRF24 :running for 3 years flawlessly.
    ESP32 with RFM95 :running for 3 months and works.

    I fist started with NRF24 on rpi, all okay.

    I encounter strange behaver whit RFM95 and raspberry gateway setup.

    Compiles without errors, start up as normal, init of radio is okay.
    But I can’t see any received message when running sudo ./bin/mysgw

    But my arduino nodes can see the gateway and all of data ai send with MYSController.
    And the nodes sends to gateway with no repose.

    The configure is.
    ./configure --my-gateway=ethernet --my-port=5004 --my-transport=rfm95 –my-rfm95-frequency=434

    Did also try with interrupts no difference.

    I needed answerers.
    So I did a trace with my logic analyser on SPI bus on the rpi, and trace on ESP32 to compare against.
    Trace contain:

    Mar 06 22:08:00 INFO Starting gateway...
    Mar 06 22:08:00 INFO Protocol version - 2.4.0-alpha
    Mar 06 22:08:00 DEBUG MCO:BGN:INIT GW,CP=RLNGL---,FQ=NA,REL=0,VER=2.4.0-alpha
    Mar 06 22:08:00 DEBUG TSF:LRT:OK
    Mar 06 22:08:00 DEBUG TSM:INIT
    Mar 06 22:08:00 DEBUG TSF:WUR:MS=0
    Mar 06 22:08:00 DEBUG TSM:INIT:TSP OK
    Mar 06 22:08:00 DEBUG TSM:INIT:GW MODE
    Mar 06 22:08:00 DEBUG TSM:READY:ID=0,PAR=0,DIS=0
    Mar 06 22:08:00 DEBUG MCO:REG:NOT NEEDED
    Mar 06 22:08:00 DEBUG Listening for connections on
    Mar 06 22:08:00 DEBUG MCO:BGN:STP
    Mar 06 22:08:00 DEBUG MCO:BGN:INIT OK,TSP=1
    Mar 06 22:08:00 DEBUG TSM:READY:NWD REQ
    Mar 06 22:08:07 DEBUG ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=NACK:
    Mar 06 22:23:00 DEBUG TSF:SAN:OK

    And after some time in RFM95 datasheet and a excel sheet to compare the data I did find something.

    The init of rfm95 chip on esp32 and raspberry is same,but after that things start go wrong on rpi.

    Channel activity detection (CAD) is skipped before transmit.
    Radio is not set to Receive continuous mode after transmit.

    Thise are all versions I have tried, the result was all the same.

    Fresh raspbian Buster install gives some compile warnings, does not abort.
    Old card with raspbian stretch on, no compile warnings.[0_1583533696677_ESP32 RFM95 INIT DATA 1.ods](Uploading 100%)

Log in to reply

Suggested Topics