12-11-2022, 06:56 PM
In another thread, which now I can't seem to find, you asked for feedback on whether or not the mechanism to connect or disconnect from a server was needed in Virtuino IoT. Here's my take:
I thought that the feature was the saving grace of Virtuino 6 as it allowed one to avoid overrunning the program when there were a lot of changes in topics all happening at once. I'm using 6 for a complex application, monitoring all boat wide functionality using a few Arduino MKR based systems and a vendor supplied beaglebone based power monitor. A wide range of data can be displayed ranging from water temperature to details about the nearest vessel to the amount of power being generated by a particular solar panel. Virtuino is great at this because I can configure easy to read displays, organized in ways that may sense for what you're looking at. The issue is that all this data can overwhelm the application, which is limited to about 30 updates a second. Since the user is a human, and not interested, or able, to look at all these different data points at once, it's very natural to divide things up into several "servers" (which are often the same underlying MQTT server), and selectively enabling them, the amount of data going to the application can be limited to a reasonable amount.
While IoT seems to handle being overrun by data more gracefully, keeping the UI functional, the data builds and what is displayed ends up being old data. In my testing I could see at least 10 seconds worth of delay in an update. This was with a synthetic test, not real vessel data, but the point is that the mechanism you put in 6 can avoid this and is a really good thing.
Lisa
I thought that the feature was the saving grace of Virtuino 6 as it allowed one to avoid overrunning the program when there were a lot of changes in topics all happening at once. I'm using 6 for a complex application, monitoring all boat wide functionality using a few Arduino MKR based systems and a vendor supplied beaglebone based power monitor. A wide range of data can be displayed ranging from water temperature to details about the nearest vessel to the amount of power being generated by a particular solar panel. Virtuino is great at this because I can configure easy to read displays, organized in ways that may sense for what you're looking at. The issue is that all this data can overwhelm the application, which is limited to about 30 updates a second. Since the user is a human, and not interested, or able, to look at all these different data points at once, it's very natural to divide things up into several "servers" (which are often the same underlying MQTT server), and selectively enabling them, the amount of data going to the application can be limited to a reasonable amount.
While IoT seems to handle being overrun by data more gracefully, keeping the UI functional, the data builds and what is displayed ends up being old data. In my testing I could see at least 10 seconds worth of delay in an update. This was with a synthetic test, not real vessel data, but the point is that the mechanism you put in 6 can avoid this and is a really good thing.
Lisa