Skip to content

Latest commit

 

History

History
64 lines (43 loc) · 2.64 KB

README.md

File metadata and controls

64 lines (43 loc) · 2.64 KB
Raw

SIGNALDuino uC v3.5.0 with cc1101 support

Development: unittest

Master: unittest

Getting started

System to receive digital signals and provide them to other systems for demodulation. Currently tested with 433 MHz, but not limited to that frequency or media.

Just clone the repo and open the project file with Visual Studio (only available for windows) or VSCode. You can also open it with the Arduino IDE. Compile it and have fun. If you are using the Arduino IDE, you have to copy all the libs into your sketch folder and modify some includes.

Using SIGNALDuino in FHEM

If you want to use the SIGNALDuino with FHEM, you can use it directly from FHEM. No need to compile any sourcode. You find more information here: http://www.fhemwiki.de/wiki/SIGNALDuino

Tested microcontrollers

  • Arduino Nano
  • Arduino Pro Mini
  • ESP32 (ESP32-WROOM-32 / ESP32-WROOM-32D)
  • ESP8266
  • RadinoCC1101
  • STM32 F103CBT6 (Maple Mini)

ESP32 Notes

If you encounter problems compiling for ESP32, sorry the code for this microcontroller is currently not finished tested with all variants from ESP32. Contributors are welcome. If you have mane errors from fastDelegate.h try adding this compiler flag: -Wno-unused-local-typedef

Signal from my device ist not detected

Implemented is a pattern detection engine, that can detect serval signal types. May not all, but most of them.

Uncomment #define debugdetect in libs/remotesensor/patterdecoder.h Search for some output which describes a pattern with serval bits received. If you find something, open an issue and provide as much as possible informations with it.

You found a bug

First, sorry. This software is not perfect.

  1. Open a issue -With helpful title - use descriptive keywords in the title and body so others can find your bug (avoiding duplicates).
  • Which branch, what microcontroller, what setup
  • Steps to reproduce the problem, with actual vs. expected results
  • If you find a bug in our code, post the files and the lines.

Contributing

  1. Open one ore more issue for your development.
  2. Ask to be added to our repository or just fork it.
  3. Make your modifications and test them.
  4. Create a branch (git checkout -b my_branch)
  5. Commit your changes (git commit -am "") 6 .Push to a developer branch (git push dev-my_branch)
  6. Open a Pull Request, put some useful informations there, what your extension does and why we should add it, reference to the open issues which are fixed whith this pull requet.