Configure the connection of the module to the controller in the Connection tab.

Protocol

You can select either "TCP/IP" or "UDP". Note that some PLC types only support TCP/IP.

You have to enable the used protocol within the PLC parameters settings of GX works (see chapter Configuration CPU).

Encoding

You can select either "Bytes" or "ASCII", depending on the configuration of your PLC. If possible, it is recommended to use the bytes-encoding method. This way, the size of the data request message is smaller and the processing is more efficient at the PLC side.

IP address

Enter the IP address at which the network interface of the PLC is located.

Timeout

Specify a value for the timeout in seconds for establishing the connection and for read access. If the time set here is exceeded, ibaPDA declares the controller as not accessible or not responsive.

PLC type

Specify to which MELSEC series the PLC is assigned to.

Port

Specify the TCP or UDP port the PLC refers to for incoming requests.

PC number

Specify the network module station number of the access target. The default value is "FF".

Network number

Specify the network number of the access target. The default value is "00".

Request destination module I/O number

When accessing a multidrop connection station, the start input/output number of a multidrop connection source module is to be specified. The default value is "03FF".

Request destination module station number

When accessing a multidrop connection station, specify the station number of an access target module. The default value is "00".

<Test>

ibaPDA tests the connection to the CPU and displays available diagnostic data, e.g. the PLC model name and the PLC type. If this option is not supported by the PLC, a warning message is generated. However, this does not imply that requesting data will not work.