Saturday, August 12, 2017

Thermostat based on Arduino

This time we are going to build a Thermostat based on Arduino, temperature sensor and relay.
You can find on github

That gives you possibility to drive multiple devices in order to control temperature. In my case I have installed two fans on my attic in order to cool it down in summer. There are no windows, so I had to force airflow. First fan gets started when temperature reaches 30 degrees, second over 35.

You can control any reasonable amount of units, it's all configurable. You have also access to basic statistics:
Runtime of whole system

ON time for each relay

Statistics for 14 days

Statistics for 7th day

Configuration

Whole configuration is stored in Config.h. You can change PINs controlling relays, reading temperature, thresholds or timings.

Hardware

Configuring Relays

Let's assume that we would like to have 3 relays:

  • ID:0, PIN: 1, Temperature setpoint: 20
  • ID:1, PIN: 10, Temperature setpoint: 30
  • ID:2, PIN: 11, Temperature setpoint: 40
  • First you have to make sure that PIN of your choice is not already taken. All pins can be find in Config.h, they are defined by variables starting with DIG_PIN.

    You have to edit Config.h and configure PINs, thresholds and amount of relays. Obviously some properties already exists, so you have to just edit them.

    const static uint8_t DIG_PIN_RELAY_0 = 1;
    const static uint8_t DIG_PIN_RELAY_1 = 10;
    const static uint8_t DIG_PIN_RELAY_2 = 11;
    
    const static uint8_t RELAYS_AMOUNT = 3;
    
    const static int16_t RELAY_TEMP_SET_POINT_0 = 20;
    const static int16_t RELAY_TEMP_SET_POINT_1 = 30;
    const static int16_t RELAY_TEMP_SET_POINT_2 = 40;
    

    Now we have to setup relays and controller, this happens in RelayDriver.cpp


        initRelayHysteresisController(0, DIG_PIN_RELAY_0, RELAY_TEMP_SET_POINT_0);
        initRelayHysteresisController(1, DIG_PIN_RELAY_1, RELAY_TEMP_SET_POINT_1);
        initRelayHysteresisController(2, DIG_PIN_RELAY_2, RELAY_TEMP_SET_POINT_2);


    Choosing Controller

    There two controllers available Hysteresis and PID

    Hysteresis Controller

    It's the one chosen in example above, it has few additional configurations:

    const static uint32_t RELAY_DELAY_AFTER_SWITCH_MS = 300000; // 5 minutes
    const static uint32_t RHC_RELAY_MIN_SWITCH_MS = 3600000;
    

    RELAY_DELAY_AFTER_SWITCH_MS gives wait time for switching next relay. Imagine that configuration from our example would start working in 40 degrees environment. This would result in enabling of all three relays at the same time. This could eventually lead to high power consumption - depending on what you are controlling, electric engine for example consumes more power during start. In our case switching relays has following flow: first relay goes, wait 5 minutes, second goes on, wait 5 minutes, third goes on.

    RHC_RELAY_MIN_SWITCH_MS defines hysteresis, it's the minimum frequency for particular relay to change it's state. Once its on, it will remain on for alt least this period of time, ignoring temperature changes. This is quiet useful it you are controlling electric motors, since each switch has negative impact on live time.

    PID Controller

    This is advanced topic. Implementing such controller is simple task, finding right amplitude settings is a different story. 

    In order to use PID controller you have to change initRelayHysteresisController(.....) to initRelayPiDController(....) and you need to find right settings for it. As usual you will find them in Config.h 

    I've implemented simple simulator in Java, so that it's possible to visualize the results. It can be found in folder: pidsimulator.
    Below you can see simulations for two controllers PID a P. PID is not perfectly stable because I did not apply any sophisticated algorithm to find right values.

    On both plots required temperature is set to 30 (blue). Current temperature indicates read line. Relay has two states ON and OFF. When it's enabled temperature drops by 1.5, when it's disabled it rises by 0.5.

    Software Design

    Message Bus

    Different software modules have to communicate with each other, hopefully not both ways ;) 

    For example: 
    • statistics module has to know when particular relay goes on and off,
    • pressing a button has to change display content and it also has to suspend services that would consume many CPU cycles, for example temperature reading from sensor,
    • after some time temperature reading has to be renewed, 
    • and so on....
    Every module is connected to Message Bus and can register for particular events, and can produce any events.

    For example pressing Next button results in following flow:
    Some components have some tasks than needs to be executed periodically. We could call their corresponding methods from main loop, since we have Message Bus it's only necessary to propagate right event:

    LIBS

    Following libs are required to compile Thermostat:
    • https://github.com/maciejmiklas/Thermostat
    • https://github.com/milesburton/Arduino-Temperature-Control-Library
    • https://github.com/maciejmiklas/ArdLog.git

    Wednesday, March 22, 2017

    Weather Station based on Arduino and NodeMCU

    We are about to build a weather station with forecast for three days, it will also include clock with local time and date.
    The whole project is based on Arduino, NodeMCU provides access to the Internet over WiFi. The display is built from single LEDs. Since they can be really bright it adopts illumination based on light conditions.


    Let's start from the beginning ;)
    I've found those 8x8 LED modules:

    so I've decided to combine few to build a display. In my case there are 3 lines, each consists of 8 modules, 24 it total, this give us 1532 single LEDs! 
    To drive single module I've chosen MAX72xx, I also wanted to improve my soldering skills, so I've decided to go for 24 PIN DIP chips and solder them to prototype boards:

    Well that worked out pretty well when it comes to those skills, but I would recommend to use LED modules combined with MAX Chip, this will save you at least few hours, not mentioning time spent afterwards when single cable gets loose ;) Such combo-module has only 3 wires instead of 16.

    So we have hardware part for our display: 24 led modules with drivers. Now it's time to light them up! I've decided to go for Arduino Mega, because it has two serial ports, so it's easier to debug things (one port will be used for communication with EPS8266). You could also use Uno, in this case you would have to daisy chain MAX chips and change addressing in software. I've used separate line for each Max chip, but Uno just does not have enough digital output pins.

    I was looking for API that will join all led modules into one canvas, so that you can print sprites on it without bothering with transitions between LED modules. I did not find anything that would make me happy so I've decided to implement one by myself. It provides not only simple canvas, but fonts and few animations. Basically everything that will be needed to display time and weather.

    So ... we have display and API to control it. Now we need to get date and weather. Arduino does not support Internet connectivity and it definitely does not have enough resources to process incoming data. So I've decided to use NodeMCU. With few Lua scripts I was able to implement simple API that is accessible over serial port. Arduino connects over it with NodeMCU, obtains time, date, weather and displays it.

    In order to provide date NodeMCU connects with NTP server and receives UTC time, afterwards it calculates local date from it. I could use one of Internet services to grab the local date, but I was looking for solution that will remain stable for long time. Those services can change their API or just go offline, but NTP protocol will remain unchanged. In worst case you will have to change server name. Current implementation supports also failover trough many different servers, so probably you will not have to bother with it soon ;)

    Getting the weather was a bit tricky, because I had to find API that will return response small enough so it could be parsed by NodeMCU. I've decided to use yahoo weather. They provide nice REST API with small and simple response. Hopefully they will keep interfaces stable for long time.....


    Putting things together

    Hardware

    First you have to build the display, I've already described it in this post: Arduino LED Display .You can use the same pin numbers on Mega, so that you will not have to alter software.

    After the display is ready, you should connect ESP8266 and photoresistor. Schematic below contains all hardware elements together:

    The area on right top corner is the display itself - 8x3 LED modules. Each single module exposes 3 PINs, those are MAX 72xxx PINs responsible for communication over SPI.
    Here you will find exact schematic of single module including SPI PINs:


    Next one is just another representation:
    Those last two schematics can be found here: https://github.com/maciejmiklas/LEDDisplay/tree/master/doc/fritzing

    Now it's time to build a software.

    Software for Arduino Mega

    You need to compile this project https://github.com/maciejmiklas/LEDClock and upload into Arduino.
    In order to compile it, you will need to include SPI module and two other libraries: https://github.com/maciejmiklas/LEDDisplay and https://github.com/maciejmiklas/LEDDisplay

    Here is a compiled software for those with the same hardware setup.

    You can use Sloeber for compilation, just follow those steps:
    1. Install Sloeber from http://eclipse.baeyens.it
    2. Create new Arduino sketch and name it: LEDClock 
    3. Confirm next screens until it will ask you about code, select cpp
    4. Finish it, and you should get something like that:
    5. Clone LEDClock project from https://github.com/maciejmiklas/LEDDisplay and move its content into Sloeber project folder. This operation should replace two files: LEDClock.h and LEDClock.cpp. Now we have Sloeber cpp project with right main files. Those wired steps were necessary, because I did not want to check in into github IDE specific files. This is our structure now:
    6. There are still compilation errors, we will now add missing libraries
    7. Clone LED Display API: https://github.com/maciejmiklas/LEDDisplay and import into the project:
    8. Repeat this procedure for Logger: https://github.com/maciejmiklas/ArdLog
    9. Imported project LEDDisplay has subfolder: examples. We have to exclude it from compilation, because it contains files with main-loop and this will disturb Sloeber. Select Properties on folder examples and check: Exclude resource from build:
    10. Now you should have following structure:
    11. You can upload it !

    Software for NodeMCU/ESP8266

    I am using EPS8266 with Lua interpreter, this combination is called NodeMCU.

    In order to provide weather and time to Arduino you will have to clone NodeMCUUtil, modify few scripts and finally upload those into NodeMCU. Below you will find exact instruction: 
    1. Compile firmware for NodeMCU so that it has all required modules. Here you will find instructions on it, and those are required modules: file, gpio, net, node, tmr, uart, wifi and cjson.
    2. Clone project containing Lua scripts: https://github.com/maciejmiklas/NodeMCUUtils
    3. Edit serialAPIClock.lua and set UTC offset for your location. This will be required to calculate local date from UTC time. For most European countries it's already set to correct value. For US you will have to replace require "dateformatEurope" with require "dateformatAmerica" and rename all method calls from setEuropeTime to setAmericaTime
    4. Edit yahooWeather.lua and provide city and country that you would like to have weather for.
    5. Create new file called: credentials.lua and specify login data for WiFi connection, it's just one line, for example: cred = {ssid = 'openwifi', password = '123456789'}
    6. Upload all Lua scirpts from main project's folder into NodeMCU:
      • credentials.lua
      • dateformat.lua
      • dateformatAmerica.lua
      • dateformatEurope.lua
      • ntp.lua
      • ntpClock.lua
      • serialAPI.lua
      • serialAPIClock.lua
      • serialAPIYahooWeather.lua
      • wlan.lua
      • yahooWeather.lua
    7. Now for the final touch we need the init-file that will be executed right after NodeMCU boots up. In our case we are using the only Serial Port in order to expose weather and clock API. This also means, that once our API is registered, it's impossible to execute standard NodeMCU commands, like file upload. For this reason init-script has two seconds delay, during this time you can still upload files, or just remove current init.lua file. Init-files are there: NodeMCUUtils/init/serialInit
      • init.lua
      • serialInit.lua

    Github repos used in this project

    Friday, November 18, 2016

    NodeMCU (ESP8266) as provider of Yahoo Weather

    I've developed small library that can be used to access Yahoo Weather over NodeMCU and than provide it over serial port. This can be connected to anything with serial port with - for example Arduino.  In such case you have simple way of accessing weather for your Arduino projects :)

    When connecting ESP8266 to Arduino you will need voltage divider to convert 5v from arduino to 3.3v.


    yahooWeather.lua

    yahooWeather.lua script provides access to Yahoo weather.
    yaw.start() will obtain weather immediately and keep refreshing it every yaw.syncPeriodSec seconds. Weather data itself is stored in yahooWeather.lua -> yaw.weather, you will find there further documentation. 

    In the example below you can see how to get wether for Munich and update it periodically:

    require "yahooWeather"
    require "wlan"
    
    yaw.city = "munich"
    yaw.country = "de"   
    wlan.setup("free wlan", "12345678")
    
    -- update weather every 17 minutes
    yaw.syncPeriodSec = 1020
    
    yaw.responseCallback = function()
        print("Weather for today:", yaw.weather[1].date) 
        print(yaw.weather[1].low, yaw.weather[1].high, yaw.weather[1].text)
    
        print("Weather for tomorrow:", yaw.weather[2].date) 
        print(yaw.weather[2].low, yaw.weather[2].high, yaw.weather[2].text)
    end
    
    -- start weather update timer
    yaw.start()
    

    Weather for today:  01 Sep 2016
    18  25  Partly Cloudy
       
    Weather for tomorrow:   02 Sep 2016
    16  25  Partly Cloudy
    
    

    Serial API

    Script below registers Serial API Interface providing access to weather. Weather itself will get updated every 17 minutes.

    require "serialAPI"
    require "serialAPIYahooWeather"
    
    yaw.city = "munich"
    yaw.country = "de"
    yaw.syncPeriodSec = 1020 -- 17 min
    -- setup wlan required by NTP clokc wlan.setup("fred", "1234567890") -- start serial API by enabling gpio and uart sapi.start() -- start yahoo weather with serial API yaw.start()

    Now you can execute few simple commands over serial:
    # weather description for today
    >YF1 text
    Rain And Snow
    
    # weather description for tomorrow
    >YF2 text
    Showers
    
    # not existing command
    >YF1 min
    ERR:serialAPIYahooWeather.lua:6: attempt to concatenate field '?' (a nil value)
    
    # max temp for tomorrow 
    >YF2 low
    1
    
    # weather date for today
    >YF1 date
    09 Nov 2016
    

    You can find full API description in serialAPIYahooWeather.lua

    Monday, September 19, 2016

    NodeMCU(ESP8266) as provider of NTP date and time over serial port

    I've boon looking for possibility to have current date and time on my Arduino projects. Arduino itself has limited resources and I would like to use them for the actual work. So I've decided to take NodeMCU with Lua language and use it to access date and time form the internet, format it in the way that meets my requirements and provide such result over serial port.

    There are many different ways to access local date and time from the internet, but mostly those interfaces change over time and code using them has to be adopted. I was looking for something that would last for years without interaction form my side. That's why I've decided to use Network Time Protocol. There is only one catch: it's UTC time without date. It was not such a big deal, because there are lot of algorithms out there so I've just adopted one of them.

    Now it's possible to obtain local date and time from NodeMCU over serial port and the whole thing is reliable and will last for many years without touching it :)

    Here is the source code: https://github.com/maciejmiklas/NodeMCUUtils

    The whole implementation is dividend into small building blocks, putting them together will give you desired serial API. This is just short overview:

    • Date Format - calculates local date and time based on timestamp
    • WiFi Access  - simple facade for connecting to WiFi
    • NTP Time - obtains UTC timestamp form give NTP server
    • NTP Clock - keeps actual UTC timestamp and synchronizes it periodically with NTP server
    • Serial API - finally this one provides API for date and time


    Date Format

    Provides functionality to get local date and time from timestamp given in seconds since 1970.01.01

    For such code:
    collectgarbage() print("heap before", node.heap())
    
    require "dateformat"
    require "dateformatEurope"
    local ts = 1463145687
    df.setEuropeTime(ts, 3600) -- function requires GMT offset for your city
    
    print(string.format("%04u-%02u-%02u %02u:%02u:%02d", 
        df.year, df.month, df.day, df.hour, df.min, df.sec))
    print("DayOfWeek: ", df.dayOfWeek)
    
    collectgarbage() print("heap after", node.heap())
    

    you will get this output:
    heap before 44704
    2016-05-13 15:21:27
    DayOfWeek:  6
    heap after  39280
    

    In order to format date for USA you have to replace require "dateformatEurope" with require "dateformatAmerica" and call setAmericaTime instead of setEuropeTime. Functionality is divided into small scripts in order to save some RAM.


    WiFi Access

    It's simple facade for connecting to WiFi. You have to provide connection credentials and function that will be executed after the connection has been established.

    execute(...) connects to WiFi and this can take some time. You can still call this method multiple times. In such case callbacks will be stored in the queue and executed after WiFi connection has been established.

    require "wlan"
    
    wlan.debug = true
    
    local function printAbc() 
        print("ABC")
    end
    
    wlan.setup("free wlan", "12345678")
    wlan.execute(printAbc)
    

    Configuring WiFi on:   free wlan
    status  1
    status  1
    status  5
    Got WiFi connection:   172.20.10.6 255.255.255.240 172.20.10.1
    ABC
    


    NTP Time

    This simple facade connects to given NTP server, request UTC time from it and once response has been received it calls given callback function. 

    Example below executes following chain: WiFi -> NTP -> Date Format. 
    So in the fist step we are creating WLAN connection and registering callback function that will be executed after connection has been established. This callback function requests time from NTP server (ntp.requestTime). 
    On the ntp object we are registering another function that will get called after NTP response has been received: printTime(ts).

    collectgarbage() print("RAM init", node.heap())
    
    require "wlan"
    require "ntp"
    require "dateformatEurope";
    
    collectgarbage() print("RAM after require", node.heap())
    
    ntp = NtpFactory:fromDefaultServer():withDebug()
    wlan.debug = true
    
    local function printTime(ts) 
        collectgarbage() print("RAM before printTime", node.heap())
        
        df.setEuropeTime(ts, 3600)
        
        print("NTP Local Time:", string.format("%04u-%02u-%02u %02u:%02u:%02d", 
            df.year, df.month, df.day, df.hour, df.min, df.sec))
        print("Summer Time:", df.summerTime)
        print("Day of Week:", df.dayOfWeek)
        
        collectgarbage() print("RAM after printTime", node.heap())
    end
    
    ntp:registerResponseCallback(printTime)
    
    wlan.setup("free wlan", "12345678")
    wlan.execute(function() ntp:requestTime() end)
    
    collectgarbage() print("RAM callbacks", node.heap())
    

    and console output:
    RAM init    43328
    RAM after require   30920
    Configuring WiFi on:   free wlan
    RAM callbacks   30688
    status  1
    status  1
    status  5
    Got WiFi connection:   172.20.10.6 255.255.255.240 172.20.10.1
    NTP request:    pool.ntp.org
    NTP request:    194.29.130.252
    NTP response:   11:59:34
    RAM before printTime    31120
    NTP Local Time: 2016-07-12 13:59:34
    Summer Time: 
    Day of Week:    3
    RAM after printTime 30928
    


    NTP Clock

    This script provides functionality to run a clock with precision of one second and to synchronise this clock every few hours with NTP server. 

    In the code below we first configure WiFi access. Once the WiFi access has been established it will call ntpc.start(). This function will start clock that will get synchronized with given NTP server every minute. Now you can access actual UTC time in seconds over ntpc.current. In order to show that it's working we have registered timer that will call printTime() every second. This function reads current time as ntpc.current and prints it as local time. 

    collectgarbage() print("RAM init", node.heap())
    
    require "dateformatEurope";
    require "ntpClock";
    require "wlan";
    
    collectgarbage() print("RAM after require", node.heap())
    
    ntpc.debug = true
    wlan.debug = true
    
    wlan.setup("free wlan", "12345678")
    wlan.execute(function() ntpc.start("pool.ntp.org", 60) end)
    
    local function printTime() 
        collectgarbage() print("RAM in printTime", node.heap())
        
        df.setEuropeTime(ntpc.current, 3600)
        
        print("Time:", string.format("%04u-%02u-%02u %02u:%02u:%02d", 
            df.year, df.month, df.day, df.hour, df.min, df.sec))
        print("Summer Time:", df.summerTime)
        print("Day of Week:", df.dayOfWeek)
    end
    
    tmr.alarm(2, 30000, tmr.ALARM_AUTO, printTime)
    

    so this is the output:
    RAM init    43784
    RAM after require   29408
    Configuring WiFi on:    free wlan
    status  1
    status  5
    Got WiFi connection:    192.168.2.113   255.255.255.0   192.168.2.1
    
    NTP request:    pool.ntp.org
    NTP request:    195.50.171.101
    NTP response:   17:09:46
    
    RAM in printTime    29664
    Time:   2016-08-08 19:10:08
    Summer Time:    true
    Day of Week:    2
    
    RAM in printTime    29808
    Time:   2016-08-08 19:10:38
    Summer Time:    true
    Day of Week:    2
    
    NTP request:    pool.ntp.org
    NTP request:    195.50.171.101
    NTP response:   17:10:46
    
    RAM in printTime    29680
    Time:   2016-08-08 19:11:08
    Summer Time:    true
    Day of Week:    2
    
    RAM in printTime    29808
    Time:   2016-08-08 19:11:38
    Summer Time:    true
    Day of Week:    2
    
    NTP request:    pool.ntp.org
    NTP request:    131.188.3.221
    NTP response:   17:11:46
    
    RAM in printTime    29680
    Time:   2016-08-08 19:12:08
    Summer Time:    true
    Day of Week:    2
    
    RAM in printTime    29808
    Time:   2016-08-08 19:12:38
    Summer Time:    true
    Day of Week:    2
    


    Serial API

    Serial API exposes simple interface that provides access to diagnostic info and date so that it can be accessed outside NodeMCU - for example by Arduino.

    Serial API is divided into few Lua scripts. Loading of each script will automatically add new API commands:
    - serialAPI.lua - has to be always loaded. It initializes serial interface with few diagnostics commands.
    - serialAPIClock.lua - access to clock including date formatter.

    Each script above registers set of commands as keys of scmd table - inside of each script you will find further documentation.

    Example below provides date access over serial port:

    require "credentials"
    require "serialAPI"
    require "serialAPIClock"
    
    ntpc.syncPeriodSec = 900 -- 15 min
    sapi.baud = 115200
    
    -- setup wlan required by NTP clock
    wlan.setup("free wlan", "12345678")
    
    -- start serial API by enabling gpio and uart
    sapi.start()
    
    -- start NTP synchronization
    ntpc.start("pool.ntp.org")
    

    Here are few Serial API commands and their responses:
    # free ram
    >GFR
    10664
    
    # WiFi status
    >GWS
    5
    
    # date and time (24h) in format: yyyy-mm-dd HHLmm:ss
    >CF1
    2016-09-16 10:45:25
    
    # date in format: yyyy-mm-dd
    >CH2
    10:45:59
    

    Firmware

    Executing multiple scripts can lead to out of memory issues on NodeMCU. One possibility to solve it is to build custom firmware containing only minimal set of node-mcu modules: cjson, file, gpio, net, node, tmr, uart, wifi. This blog provides detailed upgrade procedure: http://maciej-miklas.blogspot.de/2016/08/installing-nodemcu-v15-on-eps8266-esp.html

    Wednesday, August 17, 2016

    Upgrading NodeMCU Firmware to v1.5 on EPS8266 (ESP-12E)

    I've been updating firmware on my NodeMCU few times without issues - at least up to 0.9
    The installation procedure has changed with SDK 1.5 - I've spent few hours before I got it right, so maybe this post will help you to save some time.

    Here you will find all required information, but depending on your chip manufacturer you will need different combination of some options, and this is exactly the part when it's getting a bit tricky.

    Since things are changing rapidly, I will point out exact versions in this tutorial, so that it's clear what was working with what at time of this writing.

    Installing esptool

    Download esptool v1.1 https://github.com/themadinventor/esptool/releases/tag/v1.1 and unzip it.
    This will give you possibility to execute esptool.py form command line - we will use it below.

    Determining version of your ESP8266 chip

    As usual there are different versions, and probably you will have to modify flashing commands if you have different one.
    sudo python esptool.py -p /dev/tty.wchusbserial1410 flash_id
    
    esptool.py v1.2-dev
    Connecting...
    Manufacturer: e0
    Device: 4016
    

    Well it's obviously ESP-12E with 4MB flash:

    How do you tell? I've no idea - just google for "Manufacturer: e0 Device: 4016" and check what people are thinking.


    Building custom firmware 

    Now we have to obtain firmware containing Lua interpreter for our chip - it's everything that you will need in order to upload Lua scripts over serial. 

    Basically you will need two binary files: 
    • custom firmware - something like: nodemcu-dev-7-modules-2016-08-10-10-43-59-integer.bin
    • initial-data-block (esp_init_data_default.bin)
    Obviously you will need matching versions. 

    There are two options to get those files: 
    • you can download it from my github repo - this will give you SDK 1.5.4.1
    • you can also use cloud service to build latest release. The link to latest initial-data-block can be found here - just search for esp_init_data_default.bin
    I would prefer a latest version - as usual. But in case of some problems you can try using version provided on my github repo. At least this one was working in my case with ESP-12E, this might help you to locale a problem.

    Erase flash

    Put your chip into flash mode as described here. If you have development board it should have two buttons: flash and reset. In such case press flash and without releasing it press reset, after that release reset.

    Now you have to determine com port, and change it in all commands in this tutorial. In my case it's: /dev/tty.wchusbserial1410

    Let's finally erase flash!
    sudo python esptool.py -p /dev/tty.wchusbserial1410 erase_flash
    esptool.py v1.1
    Connecting...
    Erasing flash (this may take a while)...
    

    Now disconnect ESP from usb port, so that it can fully reset - pressing reset button does not have the same effect !

    Flashing new firmware

    Put your chip again into flash mode.
    I am assuming that you have in you current directory two binary files: one with firmware (nodemcu-dev-7-modules-2016-08-10-10-43-59-integer.bin) and second with init-stuff (esp_init_data_default.bin).
    sudo python esptool.py -p /dev/tty.wchusbserial1410 write_flash -fm dio -fs 32m 0x000000 nodemcu-master-7-modules-2016-08-10-10-45-03-integer.bin 0x3fc000  esp_init_data_default.bin

    esptool.py v1.1
    Connecting...
    Running Cesanta flasher stub...
    Flash params set to 0x0240
    Writing 385024 @ 0x0... 385024 (100 %)
    Wrote 385024 bytes at 0x0 in 33.4 seconds (92.2 kbit/s)...
    Writing 4096 @ 0x3fc000... 4096 (100 %)
    Wrote 4096 bytes at 0x3fc000 in 0.4 seconds (80.0 kbit/s)...
    Leaving...


    Testing....

    I've used ESPlorer, and it looks just fine.



    Thursday, May 12, 2016

    TS 555 timer with trigger network

    I wanted to pimp my son's bobby car by installing few lights, they should go on for a few minutes once he starts moving the car. For this I've installed few LEDs and an micro switch attached to rear axle. So that the micro switch will get triggered from time to time.

    Connecting LEDs was quiet simple, but I had some difficulties to build circuit that will enable the lights for few minutes. I've decided to use 555 timer - there are plenty of examples out there how to assemble it. I just wanted one, that will be energy efficient on stand by, and the lights should always go off after few minutes. This was not so easy, because you have to trigger the 555 by short impulse, otherwise it will never go off. My solution with micro switch has this one catch, that it can remain shorted for very long time. I've could ask my son to keep pushing the car until he hears the second click..... instead I've used a trigger network.

    On the end I had to find right values for all components in the way that it will guarantee the functionality and ensure low power consumption to not to drain batteries over few days. Actually I did not calculate those values, I've just used oscilloscope to make sure that timing on 555 pins is right. Probably I've got not a perfect values, but on the other hand side it does what is suppose to be doing and it runs on single battery for months :)



    Here is the Fritzing drawing.


    Thursday, February 4, 2016

    Arduino LED Display

    My latest project (https://github.com/maciejmiklas/LEDDisplay) contains driver for 8x8 LED Modules controlled via MAX722xx. It allows you to build display of custom size that is only limited by the hardware itself. Vertical and horizontal size can contain up to 256 modules, but before reaching this limit you would run out of Slave Select lines for controlling MAX chips, or you would be limited by amount of RAM. The fact is: you can control reasonable amount of MAX chips and build display of custom size ;)

    I've tested the whole idea on display that consist of 8 LED Modules in horizontal and 3 in vertical position. This gives us 24 modules which are containing 1536 LEDs (88 * 38).

    Hardware

    First let's start with the controller, actually any Arduino will work, I've used Mega due to large number of digital output pins. You could also use Nano with shift register and alter way of addressing Select Slave lines in Display::send(...).

    You will need extra power supply for driving LEDs - assuming that you are going to use more than one LED Matrix.

    Driving single LED Matrix Module

    I've used the MAX7219 and 788BS LED Matrix, this is the one with common anode. The schematic below illustrates wiring of LEDs, MAX and Arduino:

     This one is equivalent, but instead of single LEDs we have PIN layout of LED Module:
    It might happen, that your LED Module has common cathode, in this case you have to rewire connection to MAX chip. You just have to keep in mind, that MAX hat two sets of pins, that are relevant here: Dig0-Dig7 are supposed to be connected to cathodes (-) and SegA-SegG to anodes(+). Additionally such change will swap rows with columns within sine LED module.

    Connecting all LED Matrix together

    In the previous chapter we've seen how to connect single LED Module with MAX chip. Now we will connect multiple LED Modules together into one large display. Below is the physical display that I've used for testing and examples. Each LED Module has label indicating its position and Select Slave line.
    Here is the wiring (and image below in original size https://github.com/maciejmiklas/LEDDisplay/blob/master/doc/fritzing/LED_Display_schem.png):

    Each 3-PIN connector on schematic above symbolizes one module described in previous chapter (LED Matrix + MAX72xx), now we've connected all those modules together.

    All MAX722xx chips share common MOSI and SCK lines, MISO is not used, each chip occupies separate Slave Select line.

    The position of LED Matrix on the schematic above directly corresponds to their location on the physical display that I've used for testing. Additionally each module has description indicating it's position and Select Slave line, so for example: (2,1) SS: 35 gives us second module on third row (counting from zero) and PIN:35 on Arduino for Select Slave line.

     

    Software

     

    Compiling

    We are using standard Arduino libraries, so they are already available, the only exception is ArdLog. You have to import this LIB into your IDE. This basically means, that you have to download right release: https://github.com/maciejmiklas/ArdLog/releases/tag/v1.0.0 and unzip it into folder, where you usually place external libraries. In case of standard Arduino IDE on Mac it's ~/Documents/Arduino/libraries. On the end you should have following structure:

    $ pwd
    ~/Documents/Arduino/libraries/ArdLog
    
    $ ls
    ArdLog.cpp ArdLog.h   LICENSE    README.md
    

     

    Communication with MAX72xxx

    We are using standard SPI library and Select Slave line on MAX chip for addressing. MAX is configured in LED Matrix mode - so there is nothing special. The setup method can be found in: Display::setup()

     

    Setting things up

    The main class of our interest will be the Display - it's responsible for setup of MAX chips and provides API for painting.
    Before we start painting it's necessary to set thing up. Code below creates 2D array containing Select Slave lines and initializes display. The display itself consist of 3 rows, each one has 8 LED Modules. Obviously you can choose any responsible size, but I will stick to this one.

    The layout of mentioned 2D array corresponds to physical display: each LED Module has dedicated MAX chip, and each chip has dedicated Select Slave line. First dimension of our array indicates physical row on display, second dimension indicates LED Module within this row, and the value itself contains PIN number for Select Slave line.

    #include <Display.h>
    
    Display *disp;
    
    /**
     * Orientation of LED Kits (8x8 LED matrix) on display that I've used for testing.
     * The numbers are indicating Select Slave line of MAX7219.
     * 48, 46, 49, 47, 45, 43, 41, 39
     * 36, 34, 32, 30, 28, 26, 24, 22
     * 37, 35, 33, 31, 29, 27, 25, 23
     */
    ss_t **ss;
    
    ss_t** createSS() {
      ss_t **ss = alloc2DArray8(3, 8);
    
      // first row
      ss[0][0] = 48;
      ss[0][1] = 46;
      ss[0][2] = 49;
      ss[0][3] = 47;
      ss[0][4] = 45;
      ss[0][5] = 43;
      ss[0][6] = 41;
      ss[0][7] = 39;
    
      // second row
      ss[1][0] = 36;
      ss[1][1] = 34;
      ss[1][2] = 32;
      ss[1][3] = 30;
      ss[1][4] = 28;
      ss[1][5] = 26;
      ss[1][6] = 24;
      ss[1][7] = 22;
    
      // third row
      ss[2][0] = 37;
      ss[2][1] = 35;
      ss[2][2] = 33;
      ss[2][3] = 31;
      ss[2][4] = 29;
      ss[2][5] = 27;
      ss[2][6] = 25;
      ss[2][7] = 23;
    
      return ss;
    }
    
    void setup() {
      util_setup();
      log_setup();
    
      ss = createSS();
    
    
      // Test display consist of 8x3 LED Modules (3 rows, each one 8 Modules)
      disp = new Display(8, 3, ss);
      disp->setup();
    }
    

    There is one more method worth mentioning: log_setup(). Whole project has quiet precise logger - so that you can see what is actually happening. By default it's disabled, in order to enable it check out its documentation: https://github.com/maciejmiklas/ArdLog

     

    Painting on the display 

    Display consists of a few LED Modules, but form API perspective they are connected together into one continuous canvas. You can place on this canvas bitmap on any position given by such coordinates:

     (0,0) -----------------------------> (x)
          |
          |
          |
          |
          |
          |
          |                            (x max, y max)
          v (y)
    

    The paint method has following syntax: paint(pixel_t x, pixel_t y, pixel_t width, pixel_t height, uint8_t data).

    It allows you to paint a bitmap on given coordinates with limited width and height. So you can for example paint a bitmap on (3,4) that has 25x3 pixels. It might be larger than a actual display size - in this case it will get trimmed.

    This is obvious and simple, but there is one catch - you have to provide right data. This is 2D array, where first dimension indicates vertical and second horizontal position on the display. Technically speaking data is flat array of pointers and each pointer points to array that represents one horizontal line on the display.

    Moving over first dimension of data traverses over lines of the display. The second dimension of data represents horizontal pixels within single line, where each byte represents 8 pixels. Since our display consist of simple LEDs they can be either in on or off state, so each pixel is not being represented by one byte, but by one bit. In order to cover 16 pixels in horizontal position we need two bytes, 24 pixels require 3 bytes, and so on.
    For example to fully cover display consisting of 8x3 LED kits (one used in our examples) we would need data[3][8]. Usually you will take array small enough to fit your bitmap and not one that will cover up whole display.

    The paint(...) method updates internal buffer, in order to send content of this buffer to MAX chips you have to call flush(). The idea behind is to give you possibility to display few bitmaps on the display and after that paint the result. You can program few independent routines, that will update different part of the display and flush all changes at once.

    Communication with MAX chips is not very fast and sending content of the whole display with every flush() is time consuming. You might be able to speed up this process by enabling double buffering (set DEOUBLE_BUFFER in Display.h to true). In this case flush() method will send only bytes that have changed, so you can call flush() with every loop and do not have to worry about loosing performance. The only drawback is increased usage of RAM: we are creating 2D array that allocates 8 bytes per each LED Kit plus few pointers that are usually required to maintain arrays.

    2D arrays in this project have reduced memory footprint, because in order to create dynamic 2D array, we are creating actually 2 arrays with calculated offset (see: alloc2DArray8(....) in Util.h).

    Examples

    Requires Libs

    Examples are using ArdLog, so you have to import this lib into Arduino IDE. Here are instructions: https://github.com/maciejmiklas/ArdLog

     

    Simple Bitmap 

    In this example we will display simple static bitmap with 8x8 pixels:
    Here is the Arduino sketch: SimpleBitmap, now lest go over it:

    First we have to initialize display, as we have done in above in chapter Setting things up. Next we have to create data that can hold our bitmap - it will have 8x2 bytes. This gives us up to 8 lines and 16 horizontal pixels. But the size of our bitmap is 9x8 pixels (width x height) and this will be also the size of the painted rectangle. It should be as small as possible, so that you could place another bitmap right next to it.

    The display will obviously only paint the rectangle given by width/height and not whole data array. This is normal, that data array can hold more pixels than accrual size of out bitmap, because size of data is a multiplication o 8 and bitmap not necessary.

    void setup() {
      util_setup();
      log_setup();
    
      ss = createSS();
    
      disp = new Display(8, 3, ss);
      disp->setup();
    
      data = alloc2DArray8(8, 2);
      data[0][0] = B01100001; data[0][1] = B10000000;
      data[1][0] = B01100001; data[1][1] = B10000000;
      data[2][0] = B01100001; data[2][1] = B10000000;
      data[3][0] = B01100001; data[3][1] = B10000000;
      data[4][0] = B01100001; data[4][1] = B10000000;
      data[5][0] = B00110011; data[5][1] = B00000000;
      data[6][0] = B00011110; data[6][1] = B00000000;
      data[7][0] = B00001100; data[7][1] = B00000000;
    
      disp->paint(27, 9, 9, 8, data);
    }
    
    void loop() {
      util_cycle();
      log_cycle();
    
      // Paint method updates only internal buffer, in order to send data to 
      // MAX chips you have to flush display. 
      disp->flush();
    
      delay(100000);
    }
    

     

    Static Text 

    Now we will display static text, actually those are going to be two independent lines.

    Here you can find Arduino sketch containing whole example: StaticText.

    Your sketch needs setup method as we've already seen above (chapter: Setting things up), so we will not discus it again.

    In order to display text you should use StaticText8x8.

    Font is defined in: Font8x8, each character has 8x8 pixels.

    Your code could look like this one (plus initialization stuff from Setting things up):

    StaticText8x8 *sta1;
    StaticText8x8 *sta2;
    
    void setup() {
      util_setup();
      log_setup();
    
      ss = createSS();
    
      disp = new Display(8, 3, ss);
      disp->setup();
    
      sta1 = new StaticText8x8(disp, 64);
      sta1->box(14, 2, "Hello");
    
      sta2 = new StaticText8x8(disp, 64);
      sta2->box(5, 15, "World !");
    }
    
    void loop() {
      util_cycle();
      log_cycle();
      disp->flush();
    
      delay(100000);
    }
    

    We have created two text areas, each one containing different text and being display one under another.

     

    Single Scrolling Text

    This time we are going to display area containing text that will scroll from left to right. Link below contains youtube video - you can start it by clicking on it.
    Lest analyze code (Arduino sketch):

    Display *disp;
    
    ScrollingText8x8 *message;
    const char *textMessage;
    
    void setup() {
      util_setup();
      log_setup();
    
      ss = createSS();
    
      disp = new Display(8, 3, ss);
      disp->setup();
    
      message = new ScrollingText8x8(disp, 48, 50, 5);
      message->init();
      textMessage = "This is an example of multiple scorlling areas ;)";
      message->scroll(8, 8, ScrollingText8x8::LOOP, textMessage);
    }
    
    void loop() {
      util_cycle();
      log_cycle();
    
      message->cycle();
    
      disp->flush();
    }
    

    The initialization of the display is the same as in examples above, so it's omitted here.

    In order to display scrolling text we are using ScrollingText8x8. In setup() we are creating instance of this class and calling method scroll(...). This part only initializes scrolling, but does not play the animation itself. In order to play the animation you have to call cycle() and flush() in main loop and you must not have any additional delays there, otherwise you might get jagged animation.

    During creation of ScrollingText8x8 we have provided speed of animation - actually it's a delay of 50ms per frame. Now calling cycle() in main loop will produce frames of animation according to provided delay. When the time comes the method cycle() will update display and finally method flush() will send updated content to MAX chips.

    The whole implementation of ScrollingText8x8 is non blocking and it consumes CPU only when there is something to be done. Internally it's using simple State Machine.

    There is one last thing: you have to keep text used for animation in global variable in order to avoid garbage collection. It's not being copied in scroll() to avoid memory fragmentation.

     

    Scrolling Text Mixed 

    This example is similar to one above, but this time we will display several scrolling areas:

    Here is the sketch.
    This code is similar to one with one scrolling area, but this time we have a few:

    void setup() {
      util_setup();
      log_setup();
    
      ss = createSS();
    
      disp = new Display(8, 3, ss);
      disp->setup();
    
      uint8_t borderSpeed = 20;
      textUpDown = "* * * * * ";
      up = new ScrollingText8x8(disp, 64, borderSpeed, 1);
      up->init();
      up->scroll(0, 0, ScrollingText8x8::CONTINOUS_LOOP, textUpDown);
    
      down = new ScrollingText8x8(disp, 64, borderSpeed, 2);
      down->init();
      down->scroll(0, 16, ScrollingText8x8::CONTINOUS_LOOP, textUpDown);
    
      textLeftRight = "* ";
      left = new ScrollingText8x8(disp, 8, borderSpeed, 3);
      left->init();
      left->scroll(0, 8, ScrollingText8x8::CONTINOUS_LOOP, textLeftRight);
    
      right = new ScrollingText8x8(disp, 8, borderSpeed, 4);
      right->init();
      right->scroll(56, 8, ScrollingText8x8::CONTINOUS_LOOP, textLeftRight);
    
      message = new ScrollingText8x8(disp, 48, 50, 5);
      message->init();
      textMessage = "This is an example of multiple scrolling areas ;)";
      message->scroll(8, 8, ScrollingText8x8::LOOP, textMessage);
    }
    
    void loop() {
      util_cycle();
      log_cycle();
    
      up->cycle();
      down->cycle();
      right->cycle();
      message->cycle();
      left->cycle();
    
    
      disp->flush();
    }
    

    We have created few instances of ScrollingText8x8, each one containing different text and position on the display. In order to play animation you have to call cycle() on each instance, but you have to call only once flush(). Each call on cycle() will update it's part of the display and flush will send changed display to MAX chips.