Code development

[tcsaba101]

I am thinking of the code development stages for the future.

As a lot of ESP32 based services still missing on the ESP platform (LCD, button, SD, network) I still have some code what I would develop in the Atmel environment and release for the OS community:
some more kind of log records
brushing SensorGroup code
LCD messages on sensor data and alams

Most of those can be migrated later to ESP32

The cloud module and network needs absolute different implementation.
I will implement the cloud module on the Atmel platform what Paolo launced.
I will do the further testing on Atmel platform, till the ESP network handling will get alive.

I think till the ESP services are not functional enough it is better if I develop on Atmel platform and we migrate those parts to ESP.

It will help me to get understood the ESP coding while I can brush the code.

How you think?

[pbecchi]

I agree it is a good idea that you keep developing on Atmel!
In a couple of months I will catch up with Esp32 , at that time you can decide what to do!
Regarding cloud I think that we should do the development together to avoid problem for the porting to Esp32. Just give me couple of week and I can start working on it!
I need to make a pull request to your site to split main.cpp and create cloud.cpp so that we have same code configuration .

[tcstmarkt]

I will keep on Atmel.
But I start with ESP32 too, I would like to test „blinking” and also get JTAG to work.
Do you think I should use as a step the coding of ESP8266, or there is a total different environment?
I agree that finally we should work on the same code, but we need some more steps to start.

I finished to commit on Cloud_testing branch, it looks to work what I has intended to accomplish.

I have launched with my cloud developer the mobile UI server development on the cloud.
I will open a new branch now for developing the cloud. But still I waiting for your split of cloud functions in a separate module. Or should I do it?

[pbecchi]

You can start working on Esp8266 and then go to Esp32 the 2 environment are similar and my code on Esp8266 is working since a long time while the one on Esp32 it compile and run but few limitations but has not been debugged.
Regarding Cloud we should talk a little bit more:
It will have an significant impact on all firmware operations and need to be clearly planned
It will be dependent on type of cloud , protocol and type of application you want to use.
Let's start defining a specification for this work and we will see how to do it.
I will make a pull request to your Cloud testing branch where a split main.cpp in cloud.cpp so that you can check it out and merge it!

[tcstmarkt]

Answer relocated to Cloud messaging Issue.

[pbecchi]

I have uploaded SG21 branch to my Esp8266 OpenSprinkler repo.
This is first compilation , I believe it is still full of bugs but it compile ok on Esp8266, if you want you can try it!
I will Port it now to Esp32 it should be easy!