Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. romeo01
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    romeo01

    @romeo01

    1
    Reputation
    22
    Posts
    439
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    romeo01 Follow

    Best posts made by romeo01

    • RE: MYSBootloader 1.3 pre-release & MYSController 1.0.0beta

      Nice job, the last bootloader seems to run in good conditions.

      I use MySensors 2.2.0 beta, MYSController 1.0.0 (3314) and the last version MYSbootloader 1.3.0-beta.4 (https://github.com/mysensors/MySensorsBootloaderRF24)

      Update, flash, firmware via OTA is ok.

      But 1 problem occurs when a node reboot.
      I tried to isolate the problem, so I think that's arround the presentation request.

      When I click on "request presentation", I got it

      http://hpics.li/93e8861

      and below the debug output (via serial) of the node

      70437 TSF:MSG:READ,0-0-1,s=0,c=3,t=19,pt=0,l=1,sg=0:0
      70445 TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
      70453 TSF:MSG:READ,0-0-1,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
      70460 TSF:MSG:SEND,1-1-0-0,s=255,c=0,t=17,pt=0,l=10,sg=0,ft=0,st=OK:2.2.0-beta
      70469 TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=OK:0
      70497 TSF:MSG:READ,0-0-1,s=255,c=3,t=6,pt=0,l=1,sg=0:M
      70504 TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=11,pt=0,l=8,sg=0,ft=0,st=OK:OTA Test
      70512 TSF:MSG:SEND,1-1-0-0,s=255,c=3,t=12,pt=0,l=1,sg=0,ft=0,st=OK:1
      70521 TSF:MSG:SEND,1-1-0-0,s=1,c=0,t=3,pt=0,l=8,sg=0,ft=0,st=OK:Sensor 1
      

      Maybe a bug or where is the mistake ?

      Thanks in advance foryour help

      Edit: After a couple of test, the problem is related to the gateway with MySensor Library version 2.2.0 beta.
      All nodes (2.1.1 & 2.2.0 libs) from my network present the same error.
      Probably a vartype unexpected by the Gateway (2.2.0 lib).

      The serial Gateway (2.1.1) is ok

      posted in Development
      romeo01
      romeo01

    Latest posts made by romeo01

    • RE: Consumption & idle Loop

      Hi Yveaux, many thanks for your effort to my case.

      I didn't knew that after a wakeup, nrf24 is in stby before the next restart loop.
      Indeed, I tried a new sketch and confirm this particularity.

      So, a workaround should be to put a "sleep()" at start of the "loop"

      void loop()
      {
      
        // => At this point NRF is in RX mode
      
        sleep(xxx ms); // Put NRF24 in stby
      
       // ******
       //
       // All job here without NRF consumption !!
       //
       // *****
      
      } // End of loop
      
      

      I will do something like that !!

      Maybe, a new definition should be interresting, like MY_NRF24_RXMODE_DISABLED

      I'm sure many nodes never need the RX mode.

      PS: Hum.. !! I didn't tried if after the send command, NRF24 come back in RX mode or not.

      posted in Development
      romeo01
      romeo01
    • RE: Consumption & idle Loop

      In my case, node is awake every 5 minutes for a couple of measure (no data sent).
      An average from previous measure is only sent once by hour.
      Sometimes, awake by interrups or for monitoring some sensors.
      Most of time, no need to sent data.

      In summary, in some case, a node can be awake and doesn't send anything.
      NRF24 is still there in RX for pumping some power.

      posted in Development
      romeo01
      romeo01
    • RE: Consumption & idle Loop

      @Nca78
      Tnx fer your suggestion.

      @Yveaux
      Many low power node (running on batteries) don't need to be in RX mode.
      Like temp, door contact sensor, .....
      These simplest node only send datas.

      Is this idea could be related to a passive node ? with the RX disabled ?
      MY_PASSIVE_NODE

      posted in Development
      romeo01
      romeo01
    • RE: Consumption & idle Loop

      @yveaux Tnx fer fast reply.

      Is there there any way to put the radio in standby (no TX, no RX) when node is active ?

      posted in Development
      romeo01
      romeo01
    • RE: Consumption & idle Loop

      @mfalkvidd The problem is not here.
      In deep sleep mode, the consumption is arround 4, 5 Ua. That's perfect !

      When the node does not sleep, the NRF24 is always in RX mode.
      According to the datasheet, this one consumes +/- 12mA.

      The right question is: How to prevent the NRF24 to be in RX mode when nodes wakes up ??

      void loop{
      
      /*
       *
       *consumption here +/- 15mA
       *
       */
      
      sleep(100000) ;  // when performed , consumption +/- 4uA
      
      /*
       *
       *Immediately after wake up, consumption +/-15mA
        because NRF24 come back to RX mode.
       *
       */
      
      }
      

      I reminder, I'm looking for ultra low power node.
      My node needs only to test some input data and then send it to the Gateway.
      It never needs to RX anything from Gateway.

      I would like that NRF24 consumes only when the "send" command is performed

      send(MyMessage.set(anyData));
      

      How to put the NRF24 in sleep mode immediately after the "send command ?

      posted in Development
      romeo01
      romeo01
    • Consumption & idle Loop

      HI,

      I use a arduino pro mini 3.3v as a low power node (without power regulator and led) with a NRF24 and the lib v2.3.0-alpha

      In deep sleep mode, the consumption is arround 4, 5 Ua. That's perfect !

      Why the consumption is arround 15mA, with the sketch below. ??

      #define MY_RADIO_RF24                     // Enable and select radio type attached
      
      #define MY_RF24_PA_LEVEL RF24_PA_MAX
      
      #define MY_NODE_ID 250
      #define MY_PARENT_NODE_ID 0       
      #define MY_PARENT_NODE_IS_STATIC
      
      #define MY_BAUD_RATE 9600
                  
      #include <MySensors.h>
      
      void setup() { }
      
      void presentation(){ 
      
            sendSketchInfo("Dummy Node", "1.0");
      
      }
      
      void loop() { }
      

      This sketch does nothing as you can see, the Loop{} is empty BUT consumes 15mA at full time.
      That's just for test purpose.

      When it's running, if I unplug the NRF24, the consumption go down to few mA ( 2, 3 mA)

      So, I could say that every time the node wake up, NRF24 pumps the power for nothing.

      Why such consumption for a NRF24 in RX (I suppose) ?

      Afterwards, I tried to use the IRQ feature with MY_RX_MESSAGE_BUFFER_FEATURE and
      MY_RF24_IRQ_PIN

      but same consumption, not less than 15mA with an empty Loop.

      In my case, I don't need to receive anything from the gateway after the registration. Can I stop the "receive mode" for a NRF24 ??
      I just need to send a couple of data and then go to sleep.
      The RX period is a waste of energy.

      Any idea ?? Thanks

      posted in Development
      romeo01
      romeo01
    • RE: 💬 Building a Raspberry Pi Gateway

      @mfalkvidd Thanks fer info, now I can see the serial protocol as well in the syslog. Next step should be to have a logfile dedicated to mysgw.

      posted in Announcements
      romeo01
      romeo01
    • RE: 💬 Building a Raspberry Pi Gateway

      How can I monitor the traffic data between the raspberry and RF module (NRF24L01) on a Ethernet gateway ??

      My gateway is built for Ethernet. I start the gateway with "service mysgw start"
      Now, I would like to get the same data output than output debug (./bin/mysgw -d) but without stop mysgw service.
      I need to use MYSController as Ethernet client at the same time.

      Thanks

      posted in Announcements
      romeo01
      romeo01
    • I_LOG_MESSAGE & OTALogPrint()

      I try to send a C_INTERNAL / I_LOG_MESSAGE via MYSController.

      According to the documentation, that's the same output format that the OTALog() function https://www.mysensors.org/apidocs-beta/group__MyOTALogginggrp.html

      That's what I send "100;255;3;0;9;Hello"
      from MYSController via a raspberry Gateway (2.2.0-rc.2) to NodeID: 100

      On the node receiver: (ID #100) VER=2.2.0-rc.2
      // Enable OTA log display
      #define MY_OTA_LOG_RECEIVER_FEATURE

      I got the message below on the serial output

      157866 TSF:MSG:READ,0-0-100,s=0,c=3,t=9,pt=0,l=5,sg=0:Hello
      ⸮⸮⸮WvqA⸮⸮⸮⸮⸮⸮⸮⸮;⸮⸮In⸮⸮r⸮⸮i⸮Og⸮⸮Hello...
      

      The message is unreadable as you can see.
      What's wrong ??

      I have the same issue with LogOTANode & LogOTAGateway sketch examples. That doesn't work.
      Something seems to be wrong arround OTALogPrint() function
      https://www.mysensors.org/apidocs-beta/group__MyOTALogginggrp.html#gacda87d62975a29d2a379ce2ac64bab26

      My goal is to send some debug messages from a node to another one. I need to check and see what's happening in my sketch in development version. The node is inaccessible.

      posted in Development
      romeo01
      romeo01
    • LogOTANode & LogOTAGateway

      Hi All,

      Someone could confirm me that LogOTANode & LogOTAGateway sketch example work correctly.

      I'm unable to test the OTA degug feature because all characters sent by the node are unreadeable.

      In fact, I do not try with the logOTAGateway sketch, because I aready have a gateway running. But I use a new node with unique ID to receive all debug messages from the fist node (LogOTANode).

      TX_LogOTANode.ino (TX OTA)

      /**
       * The MySensors Arduino library handles the wireless radio link and protocol
       * between your home built sensors/actuators and HA controller of choice.
       * The sensors forms a self healing radio network with optional repeaters. Each
       * repeater and gateway builds a routing tables in EEPROM which keeps track of the
       * network topology allowing messages to be routed to nodes.
       *
       * Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
       * Copyright (C) 2013-2015 Sensnology AB
       * Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
       *
       * Documentation: http://www.mysensors.org
       * Support Forum: http://forum.mysensors.org
       *
       * This program is free software; you can redistribute it and/or
       * modify it under the terms of the GNU General Public License
       * version 2 as published by the Free Software Foundation.
       *
       *******************************
       *
       * DESCRIPTION
       *
       * Example for sending debug messages over the air (OTA).
       *
       */
      
      
      
      // Enable debug
      #define MY_DEBUG
      
      // Enable OTA debugging to Node 100
      #define MY_DEBUG_OTA (100)
      
      // Allow sending logs without MY_DEBUG_OTA enabled
      #define MY_OTA_LOG_SENDER_FEATURE
      
      #define MY_NODE_ID 50
      
      
      // Disable ACK for debug messages
      //#define MY_DEBUG_OTA_DISABLE_ACK
      
      // Enable and select radio type attached
      #define MY_RADIO_NRF24
      
      #include <MySensors.h>
      
      void setup()
      {
      }
      
      void presentation()
      {
        // Send the sketch version information to the gateway and Controller
        sendSketchInfo("TX DebugSensor", "1.0");
      }
      
      // Arduino loop
      int c=0;
      void loop()
      {
        // Wait some time
        if (sleep(3000)==MY_SLEEP_NOT_POSSIBLE) {
          delay(3000);
        }
      
        // Count loops
        c++;
      
        // A debug message
        DEBUG_OUTPUT(PSTR("DEBUG\nc=%" PRId16 "\nmillis=%" PRId32 "\n"), c, hwMillis());
      
        // Send a log message with ACK to a node
        OTALog(100, true, PSTR("LOG\nc=%" PRId16 "\nmillis=%" PRId32 "\n"), c, hwMillis() );
      
      
        
      }
      

      RX_LogOTANode.ino (RX OTA)

      /**
      * The MySensors Arduino library handles the wireless radio link and protocol
      * between your home built sensors/actuators and HA controller of choice.
      * The sensors forms a self healing radio network with optional repeaters. Each
      * repeater and gateway builds a routing tables in EEPROM which keeps track of the
      * network topology allowing messages to be routed to nodes.
      *
      * Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
      * Copyright (C) 2013-2015 Sensnology AB
      * Full contributor list: https://github.com/mysensors/Arduino/graphs/contributors
      *
      * Documentation: http://www.mysensors.org
      * Support Forum: http://forum.mysensors.org
      *
      * This program is free software; you can redistribute it and/or
      * modify it under the terms of the GNU General Public License
      * version 2 as published by the Free Software Foundation.
      *
      */
      
      // Enable debug prints to serial monitor
      #define MY_DEBUG
      
      // Enable OTA log display
      #define MY_OTA_LOG_RECEIVER_FEATURE
      
      #define MY_NODE_ID 100
      
      
      // Enable and select radio type attached
      #define MY_RADIO_NRF24
      
      #define MY_BAUD_RATE 115200
      
      #include <MySensors.h>
      
      void setup()
      {
        // Setup locally attached sensors
      }
      
      void presentation()
      {
          sendSketchInfo("RX DEBUG Display", "1.0");
      
      }
      
      void loop()
      {
        // Send locally attached sensor data here
      }
      
      
      
      // Traite les messages provenant de la Gateway
      void receive(const MyMessage &message){
      
        OTALogPrint(message);
        
      }
      
      

      Pse confirm if the sketchs above are OK and run on your side.
      Thanks in advance.

      posted in Development
      romeo01
      romeo01