Like others I have ported HS3 and other applications onto a Raspberry Pi B Raspian. I am also in the middle of a similar port to Odroid Ubuntu. A couple years ago I ported mcsSprinklers onto Dockstar Debian and PogoPlug Archlinux.
On the Pi I am evaluating an environment of HS3, mcsXap, xapHub, xapTemp08, and mcsSprinklers. From a steady state CPU utilization these applications are using 12%, 1.5%,0.5%,0.5%,2% of the CPU. For control-only purposes the Pi has more than adequate horsepower. When a browser interface is used the response is sluggish, but provides an acceptable user experience.
mcsXap can have a large list of xAP devices and in this case HS3 will timeout on pageput before a user selection is completed following a Save operation. mcsXap does not use the jQuery thus needs to process the full browser setup input rather than just one item that would be typical for a standard HST page.
mcsSprinklers also exhibits the same sluggish behavior on setup Save operations, but no timeout exists. In the mcsSprinklers' case the setup can be done on a PC and then imported onto the embedded Linux. Display-only browser operations are sufficiently responsive to provide a good user experience.
The xapHub does not require any setup. Temp08 has a simple browser interface that also provides sufficient responsiveness on the Pi.
In past years operation in the field of mcsSprinklers it was learned that the flash memory does not hold up past about a year of periodic write commands. This resulted in a design change where the flash was not used for periodic updates, but data was written to a second memory device which was a USB SSD. These provisions do not exist with HS3 and I would be concerned with the long term integrity of HS3 on embedded Linux.
mcsSprinklers does contain a significant amount of expected behavior modeling that is used to monitor its operation and its interfaces. This means that unattended operation that is expected from an embedded device can be reliably achieved with mcsSprinklers. I would be concerned with mission critical applications using HS3 as expected behavior modeling is not built into the application and the best that can be expected is email or some other notification for external intervention may be warranted.
On the Pi I am evaluating an environment of HS3, mcsXap, xapHub, xapTemp08, and mcsSprinklers. From a steady state CPU utilization these applications are using 12%, 1.5%,0.5%,0.5%,2% of the CPU. For control-only purposes the Pi has more than adequate horsepower. When a browser interface is used the response is sluggish, but provides an acceptable user experience.
mcsXap can have a large list of xAP devices and in this case HS3 will timeout on pageput before a user selection is completed following a Save operation. mcsXap does not use the jQuery thus needs to process the full browser setup input rather than just one item that would be typical for a standard HST page.
mcsSprinklers also exhibits the same sluggish behavior on setup Save operations, but no timeout exists. In the mcsSprinklers' case the setup can be done on a PC and then imported onto the embedded Linux. Display-only browser operations are sufficiently responsive to provide a good user experience.
The xapHub does not require any setup. Temp08 has a simple browser interface that also provides sufficient responsiveness on the Pi.
In past years operation in the field of mcsSprinklers it was learned that the flash memory does not hold up past about a year of periodic write commands. This resulted in a design change where the flash was not used for periodic updates, but data was written to a second memory device which was a USB SSD. These provisions do not exist with HS3 and I would be concerned with the long term integrity of HS3 on embedded Linux.
mcsSprinklers does contain a significant amount of expected behavior modeling that is used to monitor its operation and its interfaces. This means that unattended operation that is expected from an embedded device can be reliably achieved with mcsSprinklers. I would be concerned with mission critical applications using HS3 as expected behavior modeling is not built into the application and the best that can be expected is email or some other notification for external intervention may be warranted.
Comment