Browsed by
Category: Uncategorized

Desktop Capture to Node Red via MQTT

Desktop Capture to Node Red via MQTT

This post uses a similar process to an earlier post (https://www.cloudacm.com/?p=3974) where images are piped through a MQTT broker. This post will not be using FFMpeg or images captured with a camera. Instead it will use a native application to capture the desktop screen. PowerShell is a Windows native application that will be used to capture the desktop. PowerShell will call a MQTT publish process to forward the base64 data to a broker. Although the MQTT application is not native,…

Read More Read More

Nextion Integration

Nextion Integration

This post will expand on the CYD post here, (https://www.cloudacm.com/?p=5386). Instead of using the all encompassing CYD platform, a Nextion display will be used. Much of the code used in the CYD will be used here with some minor adjustments. The hardware used here is the Nextion HSD035383B4 which connects to a ESP32-C3 module. In addition, a SPI micro-SD module was attached to provide data logging. The code for the ESP32 module can be found here, https://github.com/cloudacm/ESP32-C3-Nextion-microSD The Nextion display…

Read More Read More

The CYD – (C)areful who (Y)ou invite for (D)inner

The CYD – (C)areful who (Y)ou invite for (D)inner

This post will cover the ESP32 based CYD, commonly know as the Cheap Yellow Display. The earlier post wireless network health scanner code will be repurposed here, (https://www.cloudacm.com/?p=5130). The hardware platform here is the ESP32-2432S028. It is an ESP32 based development board with an integrated 240 x 320 2.8 TFT display and microSD slot. The board typically ships with a stylus, USB C cable, and 4 pin jumper cable to serial connections. The code at the bottom of this post…

Read More Read More

AI Considerations on Command Acknowledgment and Workload Management

AI Considerations on Command Acknowledgment and Workload Management

MQTT is not stateless, publishers and subscribers maintain a connection state with the broker.  There are 2 types of connection states.  Persistent connections use a keep alive which is mainly used for subscriptions.  Session states can be persistent which allow offline messages to be queued on the broker and delivered once a subscriber re-connects, for non-persistent the broker clears its queue and resumes delivery of new messages when a subscriber re-connects.  Although the broker maintains a connection state between itself…

Read More Read More