LabView accessing ESP8266 TCP/IP server

[julio.cesar.melo]

Ola Enio, gostei do seu trabalho e gostaria de saber se é possível você compartilhar seus arquivos .ino e .vi pois estou realizando um estudo sobre telemetria. caso seja possível, por favor me envie os arquivos no email julio.cesar.melo@live.com, ou compartilhe novamente sua pasta no google drive. Desde já agradeço sua atenção.

[Enio]

Obrigado por ajudar! Infelizmente não consegui resolver o meu problema mesmo com suas orientações. No final eu acabei usando dois módulos de rádio frequência NRF24L01 (um transmissor e o outro como receptor) junto com dois arduinos. Assim consegui replicar meu sinal usando a saída PWM do arduino e mandar esse sinal para a entrada analógica de um módulo DAQ mx da NI passando por um filtro passa baixa passivo para tirar as altas frequências do sinal PWM.

Att.

Ênio Vieira Soares.

[bestecf]

I work on same problem, can you share your solutions? How to arrange HTTP GET block connections for exapmle client handle, headers, body etc. ?

[Big77]

Hello! Greetings to everyone.

I’m having some difficulties creating a .vi using the TCP/IP protocol. I need to create a program where LabVIEW acts as the server and the ESP32 as the client. In this setup, LabVIEW will use two virtual buttons: when I click one of the buttons in LabVIEW, it should send a command such as “turn on” or “turn off” to a physical output on the ESP32, for example, to control an LED or a pump. The ESP32 should interpret this command and execute the corresponding action.

The other button in LabVIEW is for triggering an emergency state. When I click it, LabVIEW sends a command, and the ESP32 interprets it and puts the system into an emergency state. In this state, a physical LED should start blinking with a delay of 300 milliseconds and keep blinking while the system remains in the emergency state.

[altenbach]

---

@Big77 wrote:

I’m having some difficulties creating a .vi using the TCP/IP protocol. I need to create a program where LabVIEW acts as the server and the ESP32 as the client. In this setup, LabVIEW will use two virtual buttons: when I click one of the buttons in LabVIEW, it should send a command such as “turn on” or “turn off” to a physical output on the ESP32, for example, to control an LED or a pump. The ESP32 should interpret this command and execute the corresponding action.

.

---

You seem to have this backwards. In TCP/IP the server is listening for connections and the client connects to the server. In your case, it seems that your LabVIEW program is the client, right? What is running on the ESP32?

Do you really need TCP? Maybe UDP would be sufficient.

(You also seem to have different hardware compared to the topic of this thread and probably should have started a new thread instead of adding to something that has not been active in a ling time and already has a marked solution from 2016!)