Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
M

melwinek

@melwinek
About
Posts
22
Topics
3
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • STM32 signing problem
    M melwinek

    When I define MY_SIGNING_SIMPLE_PASSWD
    Then my sketch not compile.
    Latest mysensors lib from git and arduino 1.8.4 and STM32F103C.

    \libraries\MySensors-development/drivers/AES/AES.cpp: In member function 'void AES::printArray(byte*, bool)':
    
    \libraries\MySensors-development/drivers/AES/AES.cpp:559:45: error: 'printf_P' was not declared in this scope
    
        printf_P(PSTR("%c"),output[j*N_BLOCK + i]);
    
                                                 ^
    
    \libraries\MySensors-development/drivers/AES/AES.cpp:562:21: error: 'printf_P' was not declared in this scope
    
      printf_P(PSTR("\n"));
    
                         ^
    
    \libraries\MySensors-development/drivers/AES/AES.cpp: In member function 'void AES::printArray(byte*, int)':
    
    \libraries\MySensors-development/drivers/AES/AES.cpp:570:32: error: 'printf_P' was not declared in this scope
    
       printf_P(PSTR("%x"),output[i]);
    
                                    ^
    
    \libraries\MySensors-development/drivers/AES/AES.cpp:572:21: error: 'printf_P' was not declared in this scope
    
      printf_P(PSTR("\n"));
    
                         ^
    
    Troubleshooting

  • OTA FW update using I2C EEPROM
    M melwinek

    @kisse66
    This is not urgent.
    Nice holiday :)

    Development

  • HELP !! cannot make Sensor work with RFM69
    M melwinek

    I also have a problem with rfm69. NRF24 always works. RFM69 can operate for hours and then disconnect and can not connect to the gateway for a long time.

    Troubleshooting

  • OTA FW update using I2C EEPROM
    M melwinek

    kisse66: Bootloader hang only when i disconnect pullup.

    1. Pullup and EEPROM - OK
    2. Pullup without EEPROM - OK
    3. Only EEPROM - Hang
    4. Free I2C pins - Hang
    Development

  • OTA FW update using I2C EEPROM
    M melwinek

    kisse66: Arduino with this bootloader without connected EEPROM hang in bootloader with DEBUG: SSF2

    Development

  • Problem with a small amount of RAM
    M melwinek

    After some changes in MySensorsCore.cpp and MySensorsCore.h I used code:

      present(10, S_CUSTOM, F("RSSI Sending"),true);
      present(11, S_CUSTOM, F("RSSI Receiving"),true);
      present(12, S_CUSTOM, F("Power dbm"),true);
      present(13, S_CUSTOM, F("Power Percent"),true);
      present(14, S_TEMP, F("DHT Temperature"),true);
      present(15, S_HUM, F("DHT Humidity"),true);
      present(16, S_TEMP, F("BMP Temperature"),true);
      present(17, S_BARO, F("BMP Pressure hPa"),true);  
      present(18, S_BARO, F("BMP Pressure Sea hPa"),true); 
    

    Compilation result:
    1582 bytes (77%) of dynamic memory

    This is still too much.
    It seems to me that signing up consumes a lot of memory.
    Can it be improved?

    Troubleshooting

  • Problem with a small amount of RAM
    M melwinek

    Am i doing something wrong?
    Are two sensors too much for Atmega328?
    library: today from git.

    #include <Adafruit_BMP085.h>
    #include "DHT.h"
    
    #define MY_TRANSPORT_WAIT_READY_MS 100
    //#define MY_DEBUG
    #define MY_DISABLED_SERIAL
    #define MY_SIGNING_SIMPLE_PASSWD "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
    #define MY_RADIO_RFM69
    #define MY_RFM69_NEW_DRIVER
    #define MY_RFM69_MAX_POWER_LEVEL_DBM 13
    #define MY_NODE_ID 1
    #include <MySensors.h>
    
    MyMessage msgRSSIS(10, V_VAR1);
    MyMessage msgRSSIR(11, V_VAR1);
    MyMessage msgPowerd(12, V_VAR1);
    MyMessage msgPowerp(13, V_VAR1);
    MyMessage msgTempDHT(14, V_TEMP);
    MyMessage msgHumDHT(15, V_HUM);
    MyMessage msgTempBMP(16, V_TEMP);
    MyMessage msgPresBMP(17, V_PRESSURE);
    MyMessage msgPresSeaBMP(18, V_PRESSURE);
    
    Adafruit_BMP085 bmp;
    DHT dht(3, DHT22); //PIN, TYPE
    
    void setup()  
    { 
    }
    
    void presentation() 
    {
      sendSketchInfo("Zewnetrzny", "1.0");
      present(10, S_CUSTOM, "RSSI Sending",true);
      present(11, S_CUSTOM, "RSSI Receiving",true);
      present(12, S_CUSTOM, "Power dbm",true);
      present(13, S_CUSTOM, "Power Percent",true);
      present(14, S_TEMP, "DHT Temperature",true);
      present(15, S_HUM, "DHT Humidity",true);
      present(16, S_TEMP, "BMP Temperature",true);
      present(17, S_BARO, "BMP Pressure hPa",true);  
      present(18, S_BARO, "BMP Pressure Sea hPa",true);  
    }
    
    void loop()      
    {
      send(msgRSSIS.set(RFM69_getSendingRSSI(),1));
      wait(200); 
    
      send(msgRSSIR.set(RFM69_getReceivingRSSI(),1));
      wait(200); 
    
      send(msgPowerd.set(RFM69_getTxPowerLevel(),1));
      wait(200); 
    
      send(msgPowerp.set(RFM69_getTxPowerPercent(),1));
      wait(200); 
      
      dht.begin();
      send(msgTempDHT.set(dht.readTemperature(),1));
      wait(200); 
      send(msgHumDHT.set(dht.readHumidity(),1));
      wait(200); 
    
      bmp.begin();
      send(msgTempBMP.set(bmp.readTemperature(),1));
      wait(200);
      send(msgPresBMP.set(bmp.readPressure()/100,1));
      wait(200); 
      send(msgPresSeaBMP.set(bmp.readSealevelPressure(164)/100,1));
    
      wait(10000);   
    }
    
    void receive(const MyMessage &message) 
    {
    }
    
    

    Compilation result:

    Sketch uses 20196 bytes (65%) of program memory. The maximum is 30720 bytes.
    Global variables use 1694 bytes (82%) of dynamic memory, leaving 354 bytes for local variables. The maximum is 2048 bytes.
    Low level of available memory, stability problems may occur.
    
    Troubleshooting

  • OTA FW update using I2C EEPROM
    M melwinek

    I wish it was so long. You did a great job.

    Development

  • OTA FW update using I2C EEPROM
    M melwinek

    kisse66: Can you refresh your sources? Official Mysensors has now added a very cool option: MY_SIGNING_SIMPLE_PASSWD.
    What determines the moment to add your changes to the official distribution?

    Development

  • OTA FW update using I2C EEPROM
    M melwinek

    When eeprom ota will be attached to official development branch ?

    Development

  • OTA FW update using I2C EEPROM
    M melwinek

    I changed to 0x7a00
    FUSE: L:FF H:DA E:05 this is 1024 words bootloader.

    And beautifully everything works.
    With little attention, I do not know why MYSCOntroller has been sending firmware several times.

    Development

  • OTA FW update using I2C EEPROM
    M melwinek

    kisse66: i have error while writing bootloader:
    avrdude: ERROR: address 0x8010 out of range at line 65 of ...optiboot_atmega328_e8.hex
    I compile it with Arduino-1.0.x
    Can you share a compiled file?

    Development

  • OTA FW update using I2C EEPROM
    M melwinek

    Please correct the warnings at https://github.com/mysensors/MySensors/pull/834
    I really want to see support for eeprom in official mysensors.

    Development

  • ESP8266 with RFM69HW - missing packets
    M melwinek

    NodeMCU is much bigger. It also costs a lot more. I do not need a USB port or any other features that have these modules.

    Troubleshooting

  • 💬 Security & Signing
    M melwinek

    @Anticimex, @mfalkvidd But with the use of encryption so easily no one will take control, must break the code.
    So it is best to simultaneously encrypt (eg RFID tag serial number when opening the gate) and sign (eg gate open message)?

    Announcements

  • 💬 Security & Signing
    M melwinek

    Is SIGNING a RFM69_ENABLE_ENCRYPTION replacement? If so is it a better or worse solution? Maybe RFM69_ENABLE_ENCRYPTION is enough?

    Announcements

  • ESP8266 with RFM69HW - missing packets
    M melwinek

    Controller: fhem
    Sketch: GatewayESP8266OTA with my changes:

    #define MY_RADIO_RFM69
    #define MY_RFM69_NEW_DRIVER
    #define MY_RFM69_MAX_POWER_LEVEL_DBM 13
    #define MY_RF69_IRQ_PIN 15
    #define MY_RF69_IRQ_NUM MY_RF69_IRQ_PIN
    #define MY_RF69_SPI_CS 16
    

    Hardware is very simple :)
    0_1494437968070_1.jpg
    0_1494437986271_2.jpg

    Troubleshooting

  • ESP8266 with RFM69HW - missing packets
    M melwinek

    MY_RFM69_NEW_DRIVER uses unique transmission power control, if the distance is less, transmission power is also reduced.

    Troubleshooting

  • ESP8266 with RFM69HW - missing packets
    M melwinek

    In 2.1.1 wait 200ms, did not help
    In development, everything is okay. All messages is received by gateway once.
    Tomorrow I will check the range, maybe I do not need RFM69HCW just RFM69CW. Thanks for help.

    One observation:
    Global variables in development version use a lot of dynamic memory. Its normal ?

    Troubleshooting

  • ESP8266 with RFM69HW - missing packets
    M melwinek

    In loop:
    V_VAR1
    V_VAR1
    V_VAR1
    Wait 5sec.

    Between 3 VAR messages no wait.

    Troubleshooting
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular