After the configuration has been accepted, the following data are displayed:

Message counter
Messages received that cannot be mapped
When receiving messages of a new connection, this value is incremented in case all available connection entries are already in use.Cause: ibaPDA receives more connections than the license supports
Connection table
Display variants
|
Green background/ bold text |
The connection is ok and there is a module assigned to it. |
|
Green background/ standard text |
The connection is ok, but there is no module assigned to it. |
|
Gray background/ bold text |
A module is defined, but no connection has been established with these parameters. |
Connection data
-
Source IP address
-
Destination port
-
Connection mode
-
Receive message counter
-
Data length of the received telegrams
Possible errors
If the connections are not displayed or only partially, this may have the following causes:
-
The controller is not sending.
-
No Ethernet connection between ibaPDA PC and the controller
-
Error in the controller configuration:
-
Incorrect remote IP address
-
The port number does not match the ibaPDA settings.
-
The port number is blocked by the firewall.
-
Other errors:
-
If the telegram counters do not increment continuously, the messages are not sent cyclically on the controller side.
-
In case the values for the data length change, this is an indication of the following error:
-
Different messages with different layout are sent over the same connection.
-
The "delayed acknowledge" problem occurs, see TCP performance problems caused by Delayed Acknowledge.
-