2026-08-19, 12:15 AM
(This post was last modified: 2026-10-02, 12:52 AM by saltwaterone.)
*** EDIT: Since posting this, I added audible alerting functionality to the code and the displays (by wiring a cheap, 3-5v piezoelectric buzzer to an open GPiO pin on the same ESP32 controlling the display). It's kinda cool, since 1. the alerting and display functionality are totally separate (an alert can be sent to any display no matter what it is displaying at the time), and 2. I added the ability to "shape" the alert tone (vary volume, frequency, and tone pattern, ie, duration, pausing, and repeating, etc. in the GUI), so, for example, critical alerts can be loud and long duration, whereas "gentle reminders", such as watch changes, etc., can be low volume and relatively sonorous, lol). To me, that beats the heck out of Raymarine one-size-fits-all heart-attack inducing alert tones!
Anyhow, I hope this is of value to some folks!
END EDiT ****
I am probably "reinventing the wheel" with a recent tft MFD (multi-function display) project I'm working on, but I figured I'd share some details in the event that others may want an easy way to display any data from signalk on cheap but good quality digital tft displays, dynamically, based on pre-configured conditions/logic set up in node red. In my case, I had a few of these displays in the parts drawer from other projects and I wanted to mount them in convenient spots on the boat to display different data via wifi on a single display conveniently mounted on the boat, dynamically and automatically when conditions arise where said data might be useful. This way, I don't need to boot up a laptop or the nav system, or toggle between a bunch of dashboards or web objects, to get critical (or just helpful) data on the fly on a single display. Again, I have seen similar tft display examples on-line using production MFDs or displays like the Waveshare ESP32 versions, but surprisingly (to me) there doesn’t seem to be many of them. Also, I didn't feel like dealing with the learning curve of ESPsence and platformIO (most seem to use these packages), so I wrote a simple but pretty flexible approach using just standard ESP32 libraries, Node Red, and MQTT (using Mosquitto broker). Each display with the ESP32 controller can be bought for around $25 and I 3D printed the enclosures, or so, so the price is really hard to beat, especially with larger tft displays (there is no real limit on size or shape of the display, the way the code is written, but I admittedly have some additional work to do to pretty up display options).
The way I did this is to write simple C++ classes for the the specific displays I have, which specifies the display size and pinouts, instantiated using standard aft calls (so the class works with existing tft code with no real change except adding the display class. I am using the LovyanGFX library, just cuz which works great, but other libraries could be used. For node red to ESP32/display comms I am using MQTT with the data output in json structured essentially the same as signalk’s data model and using the same path conventions (it would be easy to convert this to NMEA0183 or NMEA2000, but json is human readable and I like the idea of essentially extending the SK data model in json end to end). I then wrote a function in node red to convert signalk data, which is pulled into node red using the "on delta" node, as per the above, which is sent to the display using an MQTT out node, with the topic set as the signalk path and payload as json display 'instructions' and data. I am going to add some other display specific json fields later, such as brightness control, font-size/color (eg., change font red if the news is bad, lol), layout options, etc., all from a node red dashboard UI, which can be surfaced on any web browser.
In other words, taking data in from signalk and sending to the display requires just three nodes, but what (for me) is cool is that literally any logic or trigger conditions can then be easily configured, without code between those I/O nodes (For example, if wind pipes up while outside temp cools, grap anchor alarm drift and show that on the display. Or if the motor is running hot, show engine temp vs RPM vs SOG automatically. Stuff like that).
Anyhow, so far the display is just text based, no graphic gauges, but those could be pretty easily added. For me, though, it's the numbers that matter, not the look and feel of those numbers, so all in all, it is really an easy, quick, and cheap, yet for me highly functional approach way to display stuff on the boat.
I can share or post all the code (for the node red function and the ESP32 firmware), plus .stl files to 3D print (preferably using ASA filament) some waterproof enclosures for several tft displays, if anyone wants this. I am still working on a node red UI to parse the certain signalk data paths and do things like adjust brightness and font size on the displays (it's currently hard coded in the firmware), but I think I have the basics covered to get this up and running pretty easily.
Here is the first version, which includes the firmware (which is reusable for other displays, just change the class code for your display, if different), and the related node red funtions. I'm working on graphical instrument display objects (which will be selectable from the node red GUI), similar to the KIP), but it works great as is for basic numerical/text data. I welcome suggestions on this: https://github.com/sv-enkidu/easyMFD
Anyhow, I hope this is of value to some folks!
END EDiT ****
I am probably "reinventing the wheel" with a recent tft MFD (multi-function display) project I'm working on, but I figured I'd share some details in the event that others may want an easy way to display any data from signalk on cheap but good quality digital tft displays, dynamically, based on pre-configured conditions/logic set up in node red. In my case, I had a few of these displays in the parts drawer from other projects and I wanted to mount them in convenient spots on the boat to display different data via wifi on a single display conveniently mounted on the boat, dynamically and automatically when conditions arise where said data might be useful. This way, I don't need to boot up a laptop or the nav system, or toggle between a bunch of dashboards or web objects, to get critical (or just helpful) data on the fly on a single display. Again, I have seen similar tft display examples on-line using production MFDs or displays like the Waveshare ESP32 versions, but surprisingly (to me) there doesn’t seem to be many of them. Also, I didn't feel like dealing with the learning curve of ESPsence and platformIO (most seem to use these packages), so I wrote a simple but pretty flexible approach using just standard ESP32 libraries, Node Red, and MQTT (using Mosquitto broker). Each display with the ESP32 controller can be bought for around $25 and I 3D printed the enclosures, or so, so the price is really hard to beat, especially with larger tft displays (there is no real limit on size or shape of the display, the way the code is written, but I admittedly have some additional work to do to pretty up display options).
The way I did this is to write simple C++ classes for the the specific displays I have, which specifies the display size and pinouts, instantiated using standard aft calls (so the class works with existing tft code with no real change except adding the display class. I am using the LovyanGFX library, just cuz which works great, but other libraries could be used. For node red to ESP32/display comms I am using MQTT with the data output in json structured essentially the same as signalk’s data model and using the same path conventions (it would be easy to convert this to NMEA0183 or NMEA2000, but json is human readable and I like the idea of essentially extending the SK data model in json end to end). I then wrote a function in node red to convert signalk data, which is pulled into node red using the "on delta" node, as per the above, which is sent to the display using an MQTT out node, with the topic set as the signalk path and payload as json display 'instructions' and data. I am going to add some other display specific json fields later, such as brightness control, font-size/color (eg., change font red if the news is bad, lol), layout options, etc., all from a node red dashboard UI, which can be surfaced on any web browser.
In other words, taking data in from signalk and sending to the display requires just three nodes, but what (for me) is cool is that literally any logic or trigger conditions can then be easily configured, without code between those I/O nodes (For example, if wind pipes up while outside temp cools, grap anchor alarm drift and show that on the display. Or if the motor is running hot, show engine temp vs RPM vs SOG automatically. Stuff like that).
Anyhow, so far the display is just text based, no graphic gauges, but those could be pretty easily added. For me, though, it's the numbers that matter, not the look and feel of those numbers, so all in all, it is really an easy, quick, and cheap, yet for me highly functional approach way to display stuff on the boat.
I can share or post all the code (for the node red function and the ESP32 firmware), plus .stl files to 3D print (preferably using ASA filament) some waterproof enclosures for several tft displays, if anyone wants this. I am still working on a node red UI to parse the certain signalk data paths and do things like adjust brightness and font size on the displays (it's currently hard coded in the firmware), but I think I have the basics covered to get this up and running pretty easily.
Here is the first version, which includes the firmware (which is reusable for other displays, just change the class code for your display, if different), and the related node red funtions. I'm working on graphical instrument display objects (which will be selectable from the node red GUI), similar to the KIP), but it works great as is for basic numerical/text data. I welcome suggestions on this: https://github.com/sv-enkidu/easyMFD

