HMI Messages

For communication between the board and a remote device, the following messages are available:

HMI Pi3 debugger

HMI Pi3 debugger (experimental) Like the debugger made on Windows 10 with Visual studio VBA, a debugger is now also made for Raspberry Pi3, raspian OS. Programmed in Phyton and the GUI in tkinter. See also the article about the VBA I/O debugger in

Data acquisition

Data acquisition It is possible to save the raw data to an access database via the VB GUI. Every I/O type can be saved by opening the context menu of an I/O control by means of a right mouse click. When data

HMI DIY-scada

HMI DIY-Scada As explained in prior sections of the website, it is possible to make your own HMI forms with all the benefits of the standard debugger. An example of a very detailed DIY form, is the fishtank project (under the

HMI debugger

HMI Debugger When concentrating on the FSM functions on the board it is often useful to have some sort of monitor available for testing/debugging. The standard contains (as documented) a help function in the serial monitor (channel 0). Like the serial monitor help function,

Executable startup parameters

There are two different VBA executables available in Visual Studio. See also the article about the VBA-debug app for more information.  (for the following information knowledge of Visual studio is needed) The two executables are different in the way of communication with

HMI Functionality

HMI Functionality When using the Visual Studio application going with the toolbox, the following functions are available: The described functionality is a typical method of dynamic updating of data on a form. To perform dynamical updates, the “VBA backgroundworker” is developed to perform

Auto- and Handmode

Auto- and Handmode With the available commands for HMI, it is not only possible to read data from the board, but it is also possible to control the board. For example; it is possible to set a digital output pin

HMI

It is possible to communicate with more than 1 serial line from the 2560 board to other devices, so why not communicate to a second device for sending and receiving commands for supervisory control and data acquisition of the board