PL/i Simulator - Page 2

Model Specific Features

The product model drop list allows you to select your particular model so that the compiler can check for errors that may be model specific. If you select "generic", no special checks will be made. Otherwise applicable checks are made.

Here is an example of the types of model specific checks that are made: The Modbus slave devices (e.g. AM3-SM) cannot act as a Modbus master at the same time. Therefore, calls to the Modbus master functions that are normally legal will be flagged as errors for this specific device. In addition, some resource limited models do not include trig functions such as sine, cosine, etc.

Error Messages

Runtime errors such as divide by zero will cause a break point if not single stepping. The offending source line will have its icon temporarily replaced by a red "X". The green arrow will still point to the next line to be executed, and may not necessarily be near the red X. Error messages are displayed in the upper right corner of the screen.

Variable Inspect & Change with Expanded View

You change values of variables by double (left) clicking on the data in the variable display window, lower left. In the top level view, arrays and records are simply shown as hex bytes somewhat like a memory dump. To view the interpretation of that data, double RIGHT click on the variable name. If there is no expanded view, nothing will happen; however, if an expanded view is available, a new window will pop up showing the elements or record fields. You may now double (left) click on the data fields to change data. If there is yet a deeper level, such as a record of records, you may double RIGHT click on the name to get yet another new window. The example below shows the view of an array nested several levels deep in a structured variable.