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
Bogusz JagodaB

Bogusz Jagoda

@Bogusz Jagoda
About
Posts
11
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • 💬 Building a WiFi Gateway using ESP8266
    Bogusz JagodaB Bogusz Jagoda

    Worth noting - use MY_RFM69_NEW_DRIVER define... (2.3.2+)

    #ifdef ESP8266
        // For RFM69
        #define MY_RADIO_RFM69
    	#define MY_RFM69_NEW_DRIVER
        #define MY_RFM69_FREQUENCY  RFM69_868MHZ // Set your frequency here
        #define MY_IS_RFM69HW                    // Omit if your RFM is not "H"
        #define MY_RFM69_IRQ_PIN    D1
        #define MY_RFM69_IRQ_NUM    digitalPinToInterrupt(MY_RFM69_IRQ_PIN)
        #define MY_RFM69_CS_PIN     D8           // NSS. Use MY_RFM69_SPI_CS for older versions (before 2.2.0)
    #endif
    
    Announcements

  • Increasing range of 8MHz ATMEGA328P with NRF24L01
    Bogusz JagodaB Bogusz Jagoda

    @monte True, eByte’s are legit, afaik. But still you’re encountering some problems. 2.4Ghz band is pretty messy. 315/433/868 are still better solution (more obsolete now)… requiring larger antenna, though.

    Hardware

  • Increasing range of 8MHz ATMEGA328P with NRF24L01
    Bogusz JagodaB Bogusz Jagoda

    You know what I did? Switched to RFM69. You know why? Because I couldn’t get the shit done with nRF24s. You don’t even know if you have real nRF or some counterfeits - that’s the real problem. You can buy HackRF One to sniff on 2.4GHz band, but that won’t tell you if your module is receiving anything.
    Really, to spare you some time - give up on these.

    Hardware

  • New Attiny1614 /3224 /3226 Support?
    Bogusz JagodaB Bogusz Jagoda

    Main problem (already "quickfix" solved) is completely new and incompatibile interrupt system implemented in new (post-2016) ATtinys. More flexible, but also coming with some problems when using Arduino-like code and few libraries. Other than that, due to completely new power management these features I don't tested yet, may not work properly...

    Hardware

  • New Attiny1614 /3224 /3226 Support?
    Bogusz JagodaB Bogusz Jagoda

    Ok.
    Some progress.
    I've ATtiny 3227, so tested on it, with RFM69, works in IRQ mode ok.

    How to use:

    • download library from github & replace in-place in arduino user lib folder
    • use SpenceKonde megaTinyCore for newest ATtiny support
    • required define (non-standard) goes into main sketch file (.ino) before <include "MySensors.h> :
    #define MY_RFM69_IRQ_PIN PIN_PA5
    #ifdef MY_RFM69_IRQ_PIN
    	#define MY_RFM69_IRQ_PORT_vect        PORTA_PORT_vect
    #endif
    

    https://github.com/Gobol/MySensors

    Hardware

  • New Attiny1614 /3224 /3226 Support?
    Bogusz JagodaB Bogusz Jagoda

    Some advances made.

    Library is compilable @ 3227, but stripped from IRQ functionality.

    DevEnv: Microchip Studio & vMicro w/ Arduino 1.8.16

    Tests ongoing...

    Hardware

  • New Attiny1614 /3224 /3226 Support?
    Bogusz JagodaB Bogusz Jagoda

    Trying to adapt MyS to tiny3227.

    • selfmade devbrd done.
    • pickit4 as a programmer (UPDI) works from newest Arduino 1.8.16 with megaTinyCore added to board manager
    • churning datasheets for HAL part adaptation.

    It is still quite amount of work to be done, even before first successful compilation...

    Hardware

  • Gateway using Odroid-N2 via 40pin->SPI
    Bogusz JagodaB Bogusz Jagoda

    My repo depends on hardkernel's linux kernel, esp. 4.9.277. It won't work with kernels >4.9 for Odroid N2, because the developers left GPIO subsystem down (no IRQs, no /dev/gpiomem), and it only works partially...

    My Project

  • Gateway using Odroid-N2 via 40pin->SPI
    Bogusz JagodaB Bogusz Jagoda

    @Norton yep, it works in polling mode (~1% of cpu).

    My Project

  • Gateway using Odroid-N2 via 40pin->SPI
    Bogusz JagodaB Bogusz Jagoda

    Hello,

    I've made necessary changes to MySensors 2.4.0-alpha in order to work on Odroid-N2 SBC running Ubuntu 21.04 with 5.13.0 kernel
    Library would have worked if every reference to pin number was at least uint16_t (not uint8_t, like it is). That's because Odroid-N2 have >2^8 pin numbering, and GPIO ranges in 460-490 decimal.

    I've made my fork@github and pushed odroid-n2 required changes version.
    Using polling (non-IRQ) mysgw drains 1.0% cpu time.
    Still waiting for interrupt issues to resolve with HK team - hopefully soon.

    Github repo @ https://github.com/Gobol/MySensors

    My Project

  • How to compile MySensors on Platformio for Blue Pill
    Bogusz JagodaB Bogusz Jagoda

    Maybe diggin a topic a bit, but as for June 2021 :

    In library file MyHwSTM32.h one line seems to be lost :

    
    #ifndef MyHwSTM32_h
    #define MyHwSTM32_h
    
    #include <IWatchdog.h>
    #include <itoa.h>
    #include <SPI.h>
    #include <EEPROM.h>   <<--- this is necessary to compile agains BluePill
    
    

    and something like this in platformio.ini

    [env:bluepill_f103c8]
    platform = ststm32
    board = bluepill_f103c8
    framework = arduino
    
    upload_protocol = stlink
    debug_port = stlink
    debug_tool = stlink
    monitor_speed = 115200
    monitor_filters = time, default
    
    

    Just to keep you entertained.
    Cheerz.

    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