APOGEE Troubleshooting

Select a topic to continue:

APOGEE Cross Trunk Troubleshooting

This section provides solutions to the problems you are most likely to encounter using Cross Trunk.

PPCL Issues

For issues that are related to PPCL statements and commands, check the following table for possible solutions.

Symptom	Investigation Steps	Possible Solutions
Referenced point not found	Is the point underlined?	If the point is not underlined in the PPCL, the point is either misspelled, is a BACnet point, or does not exist.
Unresolved lines in the PPCL program	Is the PPCL Editor up-to-date?	Press the Refresh button to update the PPCL Editor.
	Are there any spelling errors?	If you have more than one point referenced on a line, make sure all local points are correctly spelled. Dragging-and-dropping can reduce spelling errors.
	Is it a BACnet point? If so, is the name qualified enough to be uniquely located?	BACnet points must be unambiguously specified.
	Is the display between PPCL and panel consistent?	Telnet to panel with PPCL and verify that the panel and Desigo CC are online, READY, and the display between the two is consistent.
	Is there a problem with the point in System Browser?	Check the System Browser to see if unresolved points display without errors in the Contextual pane.
	Is there a problem with the point in the panel?	Telnet to the panel and check the status of the unresolved point.

Diagnostics and Tracing Issues

Panel ready/Desigo CC ready
Node name table address
Hosts file
Diagnostics, diagnostic tracing

APOGEE P2 Devices and Networks Troubleshooting

This section provides solutions to the problems you are most likely to encounter with APOGEE P2 devices and networks.

Symptom	Investigation Steps	Possible Solutions
Not receiving Alarms.	Check Destination 0 at the MMI. Is the Desigo CC computer name in the list of recipients?	Add Desigo CC to Destination 0.
Not receiving Alarms or COVs.	Does the panel see Desigo CC as failed? Perform a panel log at the MMI.	Make sure the APOGEE P2 Driver is in the allowed applications of the Windows Firewall. Make sure the BLN name in the panel IP Settings report is identical to the BLN name in the APOGEE P2 Network application.
Ethernet BLN will not connect.	Can the panel be pinged by a name from a command prompt?	Make sure the name of panel can be resolved by the DNS or host table entry. Make sure the APOGEE P2 Driver is in the allowed applications of the Windows Firewall. Make sure the BLN name in the panel IP Settings report is identical to the BLN name in the APOGEE Network snapin.
AEM BLN will not connect.	Is the AEM defined on the network? The Has AEM property will be True. Can the AEM be pinged by the name or IP address? Make sure Insight is not using the same AEM. You will need two AEMs; one for each management station. Has the AEM been configured in the panel? In the HMI/Modem settings, the BLN name must be set and the modem disabled.	Make sure the name of AEM panel can be resolved by the DNS or host table entry. Make sure the AEM is defined on the network. Make sure the APOGEE P2 Driver is in the allowed applications of the Windows firewall. Make sure the BLN name in the panel IP Settings report is identical to the BLN name in the APOGEE P2 Network application. Make sure the Modem is disabled in the panel HMI/Modem port settings.
Objects added at the MMI are not showing up in Desigo CC .	Is Desigo CC defined as the primary or backup mass storage device? Is the panel ready?	Desigo CC must be one of the mass storage devices. Make the panel ready.
Pressing Discovery Shows failure error.	Is the panel ready?	Make the panel ready.

Handling Import Error Conditions

The following table lists the most common import errors and what you can do to remedy the problems.

Message

Situation

Do the following...

Invalid XML file format

The selected file is not a valid database file from the Desigo CC Export Tool.

Retry using a new file.

Import failed – Unable to create a new data point.
Abort, Continue, Continue All

The import did not recognize one of the objects to import.

If you do not know the reason for the missing object type, click Abort to stop the import procedure.

Alternatively, you can choose to Continue and skip the missing object or click Continue All to ignore the error.