Note: Reference is made below to the MMi202 LCD display. It is not essential to have an LCD on the MMi202, but it helps.

At startup there is a 10-second delay before ModBus communications start.

The MMi202 LCD reads '10 seconds to connect to SPLat/PC'
During this time the Kaspro will display an empty text box on the Operation screens and zero values on the configuration screen and elsewhere.

Pretend configuration data for the demo system is stored in the MMi202 permanent memory. After startup this must be sent to the Kaspro, so the user will see correct information in the configuration screen. An initial ModBus script in the MMi202 program transfers this data to the Kaspro and also reads it back from the Kaspro to a separate area of MMi202 RAM. The MMi202 program compares the data sent to the Kaspro with the data received back, and waits until there is a match.

If it is a virgin board the MMi202 will load default configuration values.

The MMi202 LCD reads 'Waiting for HMI to respond'
During this time the Kaspro will still display an empty text box on the Operation screens and zero values on the configuration screen and elsewhere.

When MMi202 receives confirmation that the configuration values have been successfully restored the temporary ModBus script is terminated and the ModBus Master Script is invoked. This runs forever.

The MMi202 LCD reads 'Configuration data restored'
The Kaspro will now show actual data from the MMi202.

ModBus Master script loop

After initialization is complete, the MMi202 starts running its “master script” and you can start to explore the various functions. The Kaspro displays 3 buttons at the top of the display that let you switch between different screens. The four screens are Maintenance, Configure and two Operation screens. Pressing the Operation button multiple times will cycle between the two Operation screens.