Neues Projekt Hilfe?
  • Projekte
  • Zeitraum
  • Badge
Neueste Kommentare
EcoKees vor 9 Stunden
DoorbellButton.c is the doorbell-client. The software is a modification of an example I found on the web. I use Eclipse for software development. A hell of a job to install, set-up and create a new project. But after that it is a marvellous development system. One big problem is that you don't have version control. After a few modifications I forgot to save my source code. At the end I had to start again from the beginning. You really need an automagically save of all your previous versions. This program will send a telnet-message to a dingdongserver and then go into deep sleep. The dingdongserver will ding the dong three times. That is something I can't miss in my room. The program awakens from deep sleep when the doorbellbutton has been pressed by a visitor. It will draw about 140 mA current at 5 V during about 6 seconds. In deep sleep the current is only 3.5 mA. In a later version of this program all events will be logged and made available using a website.
Remote dingdong-server
fuso vor 19 Stunden
I checked the time library readme.txt file at row 21 it says "day of the week, Sunday is day 0" while in dcf 77 time format monday=1 sunday=7 so you are right ! thear's a bug ! I didn't noticed it because of my clock implementation which don't use dayOfWeek so I didn't care about it I will fix it asap and send new version bye  
DCF77 emulator with ESP8266
eike vor 22 Stunden
It's been some time since my last update. I've been pretty busy with work and since it was pretty cold outside work on my car was not an option anyway.  But here is the next update. It will mostly concern the software again, as this was the main focus of my latest work.  First of all, whoever feels like plunging into my work, here you get the chance. I put my software into my gitlab repo, feel free to go through it (it's a little messy and some things aren't really smart, like my event distribution, but it was a nightly first shot, I will rework it. Maybe.). So, what's happening there?  1. The ESPAsyncWifiManager connects to my network or starts an AP so I can configure the WiFi.  2. Worker instances will be created (WifiControl, JsonWebSocket,GPSLogger) 3. OTA and and simple FTP will be set up 4. Entering main Loop. 5. Cycle through all worker and call ->run()WifiControl The WifiControl mainly manages the HTTP Server. I designed it for another project, where is used to do some UDP Broadcasting to announce it's presence but here it's mostly an HTTP Server. Not sure if I will merge it with the JsonWebSocket worker. JsonWebSocket So far not doing too much, will be the receiver and decoder for Json Documents. I plan some dynamic Index.html setup to see the last X log entrys (pushed via websocket maybe), basically mirroring Serial.println(...) while a websocket is connected. A dynamically created Json document will be part of this.GPSLogger The actual logger and hardware representation of the Neo-6M Module. Does all the processing and logging onto the SD card / SPIFFS.  The generated Webpage is currently a mix of some easy JS, charts.js and some css thrown together with gulp to reduce it's size. It's also a bit messy but works for me. 
ESP32 GPS Car Logger
mwick83 vor 1 Tag
Sadly, the reservoir fill level sensor has proven to be unreliable. I was planning to use a voltage measurement over a voltage divider, which is influenced by the number of gold contacts covered in water. It's starting to go crazy when the pump is turned on. That's the reason why I implemented configuration options to disable battery monitoring and/or reservoir fill level monitoring. If one is disabled, it will not take part in the decision if an irrigation should take place or not. This not only allows continuing with the development regardless of the fill level sensor, but it also adds more flexibility in the hardware setup. One other missing piece in the software is proper SNTP handling. The control logic requires to be notified of changes in the system time to work properly. Manually setting the time through the debug console is no problem at all, because I have all the software under my control. But the SNTP implementation is part of the lwIP stack used in the ESP-IDF. It doesn't signalize any state changes at all. According to a discussion on Github, I'm not the only one needing such a feature and it looks like it's already in development. I hope it will go public soon. Otherwise, I would have to patch the ESP-IDF sources, which would not be publicly available.
Irrigation Controller
mwick83 vor 1 Tag
Each control loop run will publish a state info via MQTT to a configured MQTT broker. The info is published in JSON format and currently looks like that: { "batteryVoltage": 12958, "batteryState": 1, "batteryStateStr": "OK", "reservoirFillLevel": -2, "reservoirState": 3, "reservoirStateStr": "DISABLED", "activeOutputs": [], "activeOutputsStr": [], "nextIrrigationEvent": "2018-01-01 07:00:00" } The state info contains internal and external sensor data as well as system state data: The battery voltage in mV and a state representation (as an integer value and a string, i.e. CRITICAL, LOW, OK, FULL and DISABLED) The reservoir fill level in percent multiplied by 10 and a state representation (as an integer value and string, i.e. CRITICAL, LOW, OK and DISABLED). Information about currently active outputs (as integer values and strings). Date and time of the next occurring irrigation event based on the currently set date and time. I have chosen to publish the voltage and reservoir fill level in mV and "percent multiplied 10" to prevent the usage of floating point variables as much as possible.
Irrigation Controller