hey guys， who can help me to find how the project generate the .pioenvs file , espcially , there is LWIP file .and I really wonder how doer it generate. Hope some kind guys tell me.thank u. the code is there : https://github.com/dogmaphobic/mavesp8266.git
Has anyone had issues using the TX1/GPIO2 to send serial? If I use the same code on a teensy 3.1 i can successfully control the serial device, when using the esp (nodemcu or wemods d1 mini) I cannot. Unfortunately I don't have an oscilloscope
I'm wondering if maybe there is a pinmode or some setting for the ESP that I don't know about?
Got it. Let’s move this over to https://gitter.im/mavlink/qgroundcontrol. That’s where it truly belongs. You don’t need any of that. You just need to create a “transparent” mode. Let’s discuss it over there.
Realize the function is very simple , I want to learn how to build the project , how to add in the project library ，how does the project works, etc., to facilitate future doing more in-depth development
@liangzelang If you want to upload the firmware to the PX4 through the ESP8266, you need to use a separate channel (TCP) and use it to act as a simple (WiFi) TCP -> serial adapter. That’s the easy part. The hard part will be the code within QGC. You need to open a TCP connection to the ESP, tell it to stop bridging MavLink messages, reboot the flight controller, and when it boots in bootloader mode, start uploading the firmware.
I tried doing mavlink on ESPs in a slightly different manner — instead of maintaining STA-AP connection and using UDP, i abused functions to send raw 802.11 data frames.
I’ve been investigating that. The problem is on the client side. You can’t exactly do that on iOS, Mac OS, etc.