In this way you are emulating an attached MCU. For a very simple experiment with the ESP firmware loaded and the ESP connected to a terminal (I use CoolTerm as it has a very nice popup screen for sending messages) you can send a commands like info: and time: the ESP should respond with this info. These commands could easily be expanded to allow many more ESP specific functions. There are also a selection of commands from the uMite that tell the ESP what to do with the data or are direct commands like time: (gets NTP time from Internet) info: (gets basic system info from ESP, eg IP,Flash,Ram etc)įrom the PC end you can Read and Set the time on the uMite, Command the uMite or ESP or Both to reset. The protocol structure allows for commands/data meant for the ESP or the uMite in the ESP/uMite device to be received and acted upon.īasically the format is IP:Port|from|to|cmd|data however the IP:Port is fairly transparent and handled in the ESPbasic firmware. I have developed a "protocol" that allows messages to be sent to/from ESP/uMites and or PC. What ever the uMite project the parts are always the same.ġ, ESP8266-MCU is the ESP firmware, sends/receives UDP messages between network and attached MCU, in my case a uMiteģ, uMite "Hook" code into the user program running on the uMite. The code I have developed consists of 3 parts. Anyway this prompted some improvements to identify the ESP/uMite device and have it use unicast when returning data. Further testing determined that messages from the PC to the uMite were being received and processed but the returned data was being sent but could not be received by Win 7 machine, the broadcast packets were being blocked. This worked fine on XP but when we came to real world testing he was using Win 7 and it didn't work. I designed the program originally as part of a project for a colleague where a uMite had to respond to a network request from a PC and send a file from an attached SD card. Original development was done on XP and I was using broadcast generally but with each ESP named in the data packet. I found this early on in the development of the PC app. In file included from C:\Documents and Settings\ijadi\Desktop\New Folder (4)\arduino-1.6.13\portable\packages\esp8266\hardware\esp8266\2.3.0\libraries\ESP8266WiFi\src/ESP8266WiFiGeneric.h:27:0, from C: \Documents and Settings \ijadi \Desktop \New Folder (4) \arduino-1.6.13 \portable \packages \esp8266 \hardware \esp8266\2.3.0 \libraries \ESP8266WiFi \src/ESP8266WiFiSTA.h:28,įrom C: \Documents and Settings \ijadi \Desktop \New Folder (4) \arduino-1.6.13 \portable \packages \esp8266 \hardware \esp8266\2.3.0 \libraries \ESP8266WiFi \src/ESP8266WiFi.h:34,įrom C: \Documents and Settings \ijadi \Desktop \New Folder (4) \arduino-1.6.13 \portable \packages \esp8266 \hardware \esp8266\2.3.0 \libraries \ESP8266WiFi \examples \WiFiWebServer \WiFiWebServer.ino:10:Ĭ:\documents and settings\ijadi\desktop\new folder (4)\arduino-1.6.13\portable\packages\esp8266\tools\xtensa-lx106-elf-gcc\1.20.0-26-gb404fb9-2\xtensa-lx106-elf\include\c \4.8.2\functional:48:28: fatal error: bits/c config.h: No such file or directory include ^Įrror compiling for board WeMos D1 R2
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |