Release v1.2.2

The major enhancement is on the format of “remote logging”.

  • Add PUT method
  • Use printf-like format
  • Data Type.(Content-type)

The printf-like format and specification of content type provides maximum flexibility. You can use any format with your own “field name” or “variable name”.┬áSo far, form type (thingspeak.com) and JSON format (ubidots.com) have been tested and verified. I hope to test XML format if I can find one.

You can find the example in readme.md at GitHub.

 

5 thoughts on “Release v1.2.2

  1. Hi, is it using a PID logic for controlling the temp? Or there is hysteresis? How accurate can be temperature controlled? Is there a PWM signal for heater and cooler or it is just 1/0 ?

  2. The temperature is controlled by PID algorithm when the temperature reading is less than a specified range, default to 3 degree Celsius.
    In boiling stage of automatic mode, PID is not applied, and the power is full-on before the temperature is greater than BOILING temperature and SETTING temperature.
    For example, let mash temperature be 64C, the heating is full on before the temperature reaches 61C if the range is set to 3.
    After 61C, PID takes control.
    If the the BOILING temperature is set to 99C and SETTING temperature is set to 100C, the power is full on before 100C. After it reaches 100C, PWM will be applied.
    If PWM cycle is one of the settings, ranging from 4000ms to 7500ms. If you set it to 5000ms, and PWM to 50%, the heating will be on for 2.5 seconds and then off for 2.5 seconds.

  3. Wait I think you replied me not about BrewPiLess but Brewmaniac? But I got it now from the forum. Although there are still few questions because I wanted to design my own PCB with circuits for your 2 projects (of course open source so everyone can use it).
    1. For BrewPiLess is it necessary to have LCD and keypad or it is useless?
    2. For Brewmaniac can I skip PCF8574 and directly attach buttons and LCD via I2C? Like you did here => http://vito.tw/wp-content/uploads/2016/08/BrewManiacAtESP8266.jpg
    3. Maybe it would be nice to have those 2 unified and choose a system when ESP starts? TO choose if you want fermentation mode (BrewPi) or mashing mode (Brewmaniac)? This is maybe for future reference and just an idea.

    If you are interested in cooperation in this please get in touch via email so we can talk details

  4. 1a. For BrewPiLess, LCD is not mandatory, but I won’t say its useless. You can check and operate it on your computer or phone, so it works fine without a display itself. However, I like to have a look at it when I walk by.

    1b. BrewPi(Less) uses Rotary Encoder, not buttons or keypad. I’ve thought of replacing the rotary encoder by a keypad, but I don’t really need the input. I don’t use rotary encoder, either. It’s far more easy and convenient to operate on browsers. Thorrax at hombrewtalk.com seems to have interest doing this. If he does it, I might save my time and just merge that code.

    2. The reason to use a PCF8574 is lack of available PINs. Please study the ESP8266 and think about PIN assignment.

    3. I don’t really think it’s a good idea unless you want to build a all-in-on system, like BrewHa.
    https://brewhaequipment.com/products/3-in-1-jacketed-conical-fermenter
    Even though, you might need to switch the connection of RELAYs from heater and pump to heating and cooling. The BrewPiLess build can be very cheap for a minimum setup: a NodeMcu(under $5), a relay module($2), and two DS18B20($3). I don’t see much benefit to merge fermentation and wort-making controllers.

  5. Sorry,

    My bad. I though that you were asking BrewManiacEx.
    BrewPiLess is comprised of web related portion and the porting of BrewPi which uses a designated PID algorithm to control fridge/freezer as a fermentation chamber. I don’t really trace all the source code of BrewPi. You can find the information by googling BrewPi.

    The temperature control is handled by the BrewPi “core” which originally runs on Arduino. My work is to eliminate Raspberry Pi.

Leave a Reply

Your email address will not be published. Required fields are marked *