This wizard allows checking for possible installation errors at the functionality level (Group Address). To perform the error diagnosis, one shall select an "item" you want to check (the functionality linked to this item will be checked). The next sections describe the various wizard steps.
How to invoke it?
Via the project menu bar 'Diagnostics' > Online Error Diagnostics
Select Group Addresses Tab
Before calling the wizard, one or more of the following elements must be selected so that the diagnostics can be carried out:
- Group Addresses (also higher-level areas)
- Group Objects
- Devices
In the wizard itself, only one Group Address can be checked at a time. Please select one single Group Address to check and proceed. Once the check is finished, you can move backwards in the wizard to the page where you can select the next Group Address to be checked.
Check Devices Tab
All devices which are connected with the selected Group Address are shown here (with extra columns for address/name, product description and building assignment).
All couplers which shall filter the Group Address are also shown. If devices from multiple lines are in the list, they are grouped by line.
You can select one device to check, or all of them (using an extra button at the bottom).
A. Button/ icon 'LED' blinking is available in the last column for every device. Only one device can be checked at a time.
B. Button 'Check Devices'
The following checks are performed for each device:
- Can the device be reached via the bus (ping)?
- Is the Application Program loaded and running (details depend on the device)?
- Reads the group communication tables to check if the Group Address has indeed been downloaded to the device (uses the same functionality as 'Device Info' for Group Addresses).
- For couplers
- If group filtering is disabled (route all): OK
- If 'block all': not OK
- If the filter table is active: read the relevant part of the filter table and check if the Group Address is included.
Whether couplers (or possibly backbone couplers) of a given Group Address are involved is determined using the following logic:
Group Address > Assignment > Group Object > Device > Line(s)
If there is only one line in this list, no couplers will be returned. If there are lines from different areas in this list, then:
- List all line couplers (a.l.0)
- List all backbone couplers (a.0.0)
Note that an area may have no backbone coupler (e.g. when there is an IP backbone). In this case, nothing is added in this step.
- List all backbone couplers (a.0.0)
- For dummy devices, the check is skipped.
Results
The results of the check are displayed as an icon with a different color in the status column:
| Icon | Description |
|
|
If all checks have been successfully executed and have been found to be in order. |
|
|
If at least one check has failed entirely. The exact error is included as text. |
|
|
If none of the checks has failed entirely, but at least one check yielded an inconclusive result (example: a device with a plug-in does not implement the intended interfaces and the standard variant of the check failed). An indication of what might be wrong is included in the text. |
The error text includes both what has been found to be inconsistent and what measures can be taken by the user.
Send/Receive Tab
This page allows sending and reading any (allowed) value via the Group Address (same function as in group monitoring).
SEND (Write)
- The selection of the (write) value itself depends on the Datapoint Type type of the Group Object to which the Group Address is assigned. It also depends on whether a Datapoint Type has been set for the Group Address.
- The reception of a group telegram from the bus via this Group Address is displayed (time, source device address + text, value formatted according to Datapoint Type).
READ (Read)
The user can also read the value of the Group Address.
Generally this will not be possible if the Group Address is not the sending Group Address of the Group Object it is assigned to and if both the Communication and the Read flags are set (devices with plug-ins can be an exception).
The Read button will be enabled in any case, but a text describing the problem will be displayed next to the button if the above situation arises.
Step 1
Any possible existing line connections in the project are checked first by ETS (for which the Group Address is in the active line) and these are then used.
Step 2 (if Step 1 is not applicable)
If the active (USB) interface is not connected to a line in which the Group Address is used (e.g. because it is blocked by couplers), the wizard will recognize this and recommend making a connection to a line in which the Group Address is used (it shows a list of all such lines).
Bus Traffic Analysis Tab
Telegram traffic is analyzed on this page. If possible, the wizard switches to bus monitoring mode. If this is not possible (another connection is open or the interface does not support bus monitoring mode), a message is displayed saying that some of the functionality is not available. During analysis, the following data is collected and displayed:
Total Bus Load (TP only)
Since the bus load is currently only specified for TP, bus load display is not possible for other media.
Note also that if the wizard is not in bus monitoring mode, telegrams with physical addresses as the target and repetitions cannot be taken into account. The bus load calculation uses a 10 second sliding integration window. The wizard window will display the current, maximum and average value for the performed measurements.
Number of BUSY/NAK and Repetitions
This is only possible in Bus Monitoring mode. The number of BUSY/NAK and repetitions is shown including information on the destination (address and name) of the telegram causing the bus load.
The resulting output is grouped according Group Address and source address (i.e. one line for each occurring combination of a Group Address and a source address) and lists the number of BUSY, NAK and repetitions.
Data is recorded permanently and the resulting list is updated every 2 seconds.
Top 5 Senders
With source address and name, number of telegrams from this address and share of this number in the total number of telegrams received.
For each source address, all telegrams which originated from this address are counted. They are then sorted according to the resulting count: the list ends after the 5th address and addresses for which the count is less than 2% of the total number of telegrams are ignored.
Data is recorded permanently and the resulting list is updated every 2 seconds.
A corresponding line connection is taken for the device check, if defined. For the monitor (send/receive), the line connection in which any one of the devices assigned to the Group Address is located is also used, if possible. If no line connection is present, the normal interfaces are applicable and the sequence is according to the priority.