MVP Logo

Материализуя идеи

Не поднимешься в горы — не узнаешь высоты неба; не спустишься в бездну — не узнаешь толщи земли.

In memory of my mother, Gromova Margarita Ivanovna. Thank you, and rest in peace.

iconThe following is a result of more than two years of efforts, in fields of PCB and schematics software mastering, C software design, ESP8266 platform development, and struggling through quirks of Embarcadero;s Firemonkey framework in C++, all in spare time between a supper, and night sleep.
Finally, ESP8266+PZEM T004 - based WIFI PowerMetering logger is here, both, as IoT firmware, and PC client software.


steema-logoRequirements and pre-conditions:

  1. Chart series may contain different point types:
    1. First, let's call them 'automatic' - which may have been acquired by some logger process, in ordered, evenly spaced moments in time.
    2. Other type is 'manual', - meaning, that thesee may be acquired as a result of explicit user-to-device interaction during the same measurement session, as an automatic ones. These manual points usually have an arbitrary distributed x, and sometimes even y values.
  2. Chart series should draw automatic and manual points differently, while allowing these points to be iterated as a members of the same sequence.


When using boost framework, which I usually try to avoid, if possible, I further avoid using its binary libraries. Mainly because it's required to build these, and it's not as easy as it may seem.
First, you should build the boost build engine itself. My most recent attempt was with boost 1.66 + MSVC 2017. Needless to say, that I ran into quite usual showstopper. Boost could not compile b2 because it could not find a few C++ headers, and libraries. Following are necessary steps to perform to avoid these obstacles.


I started ESP8266 project, the first step was to support SDMMC over SPI. I have implemented SDMMC SPI interface years ago. The main challenge was to adapt it to new MCU core. After many attempts, it was up and running. Below are lessons learned.


Recently, I've complete my 'geshtalt' - migrate and release Windows FMX app, Ecolight-AP under MacOSX platform. And, by God, it was painful and hard, mainly due to EMB toolchain tried to fracture my butt on almost each final step.
The dehydrated knowledge here is crystallized two weeks of pain and swearing, and sweatting.
Problem starts reveling itself after all Debug stuff was successfully brushed on MAC, under PAServer session, and Release for App Store was created with Developer ID * certificates, which allow to install from signed local pkg.


Recently I've implemented lightweight header library to encapsulate interfacing with FTDI EVE chip, namely, FT800, in templated OO manner.  It should compile in modern embedded x86/ARM toolchains, like ones Keil or C++ Builder have. 

The idea is as follows - while your core framework provides standard IO bus interface, like mine esfwxe, via EseChannel templated abstract facade, the rest is done in modular manner by EVE library classes.


For the recent mobile FMX application development, I had a challenge, do not use any service from my full-featured cross-platform framework, to minimize application bloat, besides, FMX framework itself is rather big piece of cake.

One of the cornerstones is a I18N support which in my framework is based upon custom implementation of gettext. In current case, I decided to wrap I18N manager coode around FMX's TLang. As far as TLang may use, besides its binary stoarage, the plain text files as well, formatted as key=value pair.



Сейчас на сайте 50 гостей и нет пользователей

06.10.2022  ©2022 - ExactSoft - All rights reserved