medm screens

modbus provides example medm .adl files in the modbusApp/op/adl directory.

modbusDataTypes.adl

The following is a screen shot from an IOC running the testDataTypes.cmd and testDataTypes.substitutions files, communicating with a Modbus Slave Simulator. These are the ao/ai records using the asynFloat64 interface. It shows that the output and input (readback) records agree.

_images/testDataTypes.png

The following is a screen shot from the Modbus Slave Simulator communicating with the ao/ai records shown above. The values shown in this screen agree with this in the medm screen, showing that each Modbus data type is being communicated correctly.

_images/testDataTypesSimulator.png

The following are screen shots of these screens from an IOC controlling a Koyo DL205 PLC.

Koyo1.adl

Top level medm screen for the Koyo1 example application.

_images/Koyo1.png

Koyo_8inputs.adl

Inputs X0-X7 read as discrete inputs (function code 1).

_images/K1_Xn_Bit.png

Inputs C200-C207 read as register inputs (function code 6).

_images/K1_C20n_In_Word.png

Koyo_8outputs.adl

Outputs Y0-Y7 written using register access (function code 6).

_images/K1_Yn_Out_Word.png

Outputs Outputs C200-C207 written using bit access (function code 5).

_images/K1_C20n_Out_Bit.png

modbusArray.adl

Inputs C0-C377 read using a waveform record and coil access (function code 1).

_images/K1_Cn_In_Bit_Array.png

Inputs C0-C377 read using a waveform record and register access (function code 3).

_images/K1_Cn_In_Word_Array.png

modbusStatistics.adl

I/O statistics for the Modbus driver that is reading inputs X0-X37 using register access (function code 3). The histogram is the number of events versus TCP/IP write/read cycle time in msec.

_images/K1_Xn_Bit_Statistics.png

Koyo2.adl

Top level medm screen for the Koyo2 example application.

_images/Koyo2.png

Koyo_4ADC.adl

4 ADC inputs from a 13-bit bipolar ADC.

_images/K2_ADCs.png