mecs UTX1700PTFE Servo speed governor

   Communication Overload has appeared for at least one sending DSP, the rest of the sending DSPs in the same list also fails in configuration. No indication of the error is given except that no data is received in the receiving end.The system messages, generated in the Advant Controller 400 Series, are displayed on the connected Advant Station 100 Series engineering station.All DataSet Peripheral related system messages have message type 39. The tasks that generate DataSet Peripheral related system messages are: • CXPIOP0, the init task. Advant Controller 410/Advant Controller 450 *1.1: • CXAP000, DSP task Advant Controller 410/Advant Controller 450 *1.2 and later: • CXAP000, DSP scan task • CXAPC0x, DSP supervision tasks. x is a number between 1 and 4 for Advant Controller 410 and between 1 and 8 for Advant Controller 450.

The sequence number in the DSP system messages contains code specific information. Data1 with a few exceptions consists of the concept number and the logical record number of the first DSP for which the error has occurred or the first DSP in a group of up to 100 for which the error has occurred. Below follows a short description of an extract of the possible code values:1 Configuration error due to module busy or module hardware error Data2: Internal information. 3 Configuration error in configuring a group of up to 100 DSPs. Data2: Internal information 4 Basic cycle time used. One or several DSPs defined for a faster cycletime than the DSP scan time. Data2: The DSP scan time.

DataSet Peripheral not Configured

 This indicates that the DSP in question cannot be configured, as this would result in a bus overload. The error persists until the DSP is re-configured (for example with a larger cycle time or fewer DAT Elements, thus reducing the bus load). The only way to resolve problems due to too high bus load is to reduce the number (or size) of the DSPs, or to make the cycle times larger. DataSet Peripheral not Addressed This indicates that no bus master function for the DSP in question is detected. Either there are no bus masters, or the sending DSP has not (yet) been configured. The error persists until the DSP in question is being addressed by the bus master. To repair the error, make sure that the corresponding sending DSP is configured, and that the associated communication interface is operational. When this is the case, the DSP will sooner or later be configured in the network, and the error will disappear