STOP.G DP sub error (code = %d)

[Cause]

A DDLM function call error occurred in the DP master software on the PROFIBUS board. This alarm supplements PROF-014. The number in parentheses indicates the error code. Refer to the table below.

+-------------+--------------------------------------------------------------------------------------------+ | Code Number | Annotations | +-------------+--------------------------------------------------------------------------------------------+ | 1 | Data calibration problems have arisen. | +-------------+--------------------------------------------------------------------------------------------+ | 2 | Too many DP slaves are connected. | +-------------+--------------------------------------------------------------------------------------------+ | 3 | Incorrect slave address. | +-------------+--------------------------------------------------------------------------------------------+ | 4 | The specified address assignment mode is not supported. | +-------------+--------------------------------------------------------------------------------------------+ | 5 | Diagnosis data are too short. | +-------------+--------------------------------------------------------------------------------------------+ | 6 | The parameter data length in the slave parameters is invalid. | +-------------+--------------------------------------------------------------------------------------------+ | 7 | The configuration data length in the slave parameters is invalid. | +-------------+--------------------------------------------------------------------------------------------+ | 8 | The length of diagnostic data is illegal. | +-------------+--------------------------------------------------------------------------------------------+ | 9 | The length of the bus parameter is illegal. | +-------------+--------------------------------------------------------------------------------------------+ | 10 | The slave parameter length is invalid. | +-------------+--------------------------------------------------------------------------------------------+ | 11 | I/O data length is illegal. | +-------------+--------------------------------------------------------------------------------------------+ | 12 | The memory area on the PROFIBUS circuit board for the DP host software is inadequate. | +-------------+--------------------------------------------------------------------------------------------+ | 13 | The operating pattern of the DP host software on the PROFIBUS circuit board is incorrect. | +-------------+--------------------------------------------------------------------------------------------+ | 14 | The DP slave refuses access. | +-------------+--------------------------------------------------------------------------------------------+ | 15 | The area code for service requests from the DP host software on the PROFIBUS circuit board | | | is illegal. | +-------------+--------------------------------------------------------------------------------------------+ | 16 | The service request for the DP host software on PROFIBUS circuit boards from robotic | | | control devices is not supported. | +-------------+--------------------------------------------------------------------------------------------+ | 17 | The parameter section of the slave parameters for the DP master software on the PROFIBUS | | | board is invalid. | +-------------+--------------------------------------------------------------------------------------------+ | 18 | The configuration data section of the slave parameters for the DP master software on the | | | PROFIBUS board is invalid. | +-------------+--------------------------------------------------------------------------------------------+ | 19 | The address assignment table of the slave parameters for the DP master software on the | | | PROFIBUS board is invalid. | +-------------+--------------------------------------------------------------------------------------------+ | 20 | The slave user data section of the slave parameters for the DP master software on the | | | PROFIBUS board is invalid. | +-------------+--------------------------------------------------------------------------------------------+ | 21 | The slave parameters for the DP master software on the PROFIBUS board are invalid. | +-------------+--------------------------------------------------------------------------------------------+ | 22 | The specified area cannot be accessed. | +-------------+--------------------------------------------------------------------------------------------+ | 23 | The baud rate in the bus parameters for the DP master software on the PROFIBUS board is | | | invalid. | +-------------+--------------------------------------------------------------------------------------------+ | 24 | PROFIBUS circuit board is illegal with BP flag values for bus parameters for the DP host | | | software. | +-------------+--------------------------------------------------------------------------------------------+ | 25 | The FDL status of the robot when requesting services from the DP host software on the | | | PROFIBUS circuit board is illegal. | +-------------+--------------------------------------------------------------------------------------------+ | 26 | The activation specified when the robot sends a service request to the DP master software | | | on the PROFIBUS board is invalid. | +-------------+--------------------------------------------------------------------------------------------+ | 27 | The host site address of the bus parameter is illegal. | +-------------+--------------------------------------------------------------------------------------------+ | 28 | There was a DPRAM initialization error in the DP host software on PROFIBUS circuit board. | +-------------+--------------------------------------------------------------------------------------------+ | 29 | An error in the data size specified when the robot sends a service request to the DP host | | | software on the PROFIBUS circuit board. | +-------------+--------------------------------------------------------------------------------------------+ | 31 | The identifier (identifier) specified by the robot when sending a service request to the | | | DP host software on the PROFIBUS circuit board is illegal. | +-------------+--------------------------------------------------------------------------------------------+

[Countermeasure]

For sub-error codes other than those in the table below, contact the service department. Report the numbers in parentheses, which are needed to identify the condition.

+-------------+---------------------------------------------+ | Code Number | Annotations | +-------------+---------------------------------------------+ | 2 | Set the number of DP slaves to 32 or fewer. | +-------------+---------------------------------------------+ | 3 | Specify the correct slave address. | +-------------+---------------------------------------------+

+-------------+--------------------------------------------------------------------------------------------+ | Code Number | Annotations | +-------------+--------------------------------------------------------------------------------------------+ | 13 | Issue the correct service request in the correct operating mode. If slave parameters have | | | been downloaded to the robot controller, the operating mode can be set to CLEAR or | | | OPERATE. If slave parameters have not been downloaded, set the operating mode to STOP. | | | Note the above when issuing a service request from DP master class 2. | +-------------+--------------------------------------------------------------------------------------------+ | 14 | Check the DP slave status. | +-------------+--------------------------------------------------------------------------------------------+ | 17 | The parameter section of the slave parameters has been downloaded from DP master class 2 | | | or the robot DP master class 1. | | | 1. The parameter portion is confirmed as correct when downloaded from the DP host level 2. | | | 2. Check that the following item values on the DP master slave parameter setup screen are | | | correct. Station status | | | . Lock request | | | - Unlock the request. | | | ・Sync Request | | | ・Freezing requests | | | .WD Request | | | WD FACT1 | | | WD FACT2 | | | Minimum TSDR ID number group ID | | | ・ From group 1 to group 8. User parameter data byte count. User parameter data. | +-------------+--------------------------------------------------------------------------------------------+ | 18 | The configuration data section of the slave parameters has been downloaded from DP master | | | class 2 or the robot DP master class 1. | | | 1. The configuration data component is confirmed when downloaded from the DP host level 2. | | | 2. Check that the following item values on the DP master slave parameter setup screen are | | | correct. Configuration data byte count. Configuration data. | +-------------+--------------------------------------------------------------------------------------------+ | 19 | The address assignment table of the slave parameters has been downloaded from DP master | | | class 2 or the robot DP master class 1. | | | 1. The address distribution form is confirmed when downloaded from the DP Host Level 2. | | | 2. Check that the following item values on the DP master slave parameter setup screen are | | | correct. Input byte count. Output byte count. DPRAM input offset. DPRAM output offset. | | | 3. The input/output byte count for the PROFIBUS master and slave interface is too large. | | | Set the maximum number of DI/DO ports correctly on the PROFIBUS master setup interface. | | | Set the following system variables to the maximum allowed values. | | | $PRIMAVAR.$MAX_OUT_LEN = 32 => 128 | | | $PRIMAVAR.$MAX_IN_LEN = 32 => 128 | +-------------+--------------------------------------------------------------------------------------------+ | 20 | The slave user data section of the slave parameters has been downloaded from DP master | | | class 2 or the robot DP master class 1. | | | 1. If the slave user data section is downloaded from DP master class 2, check that it is | | | correct. | | | 2. Check that the following item values on the DP master slave parameter setup screen are | | | correct. Slave user data byte count. Slave user data. | +-------------+--------------------------------------------------------------------------------------------+ | 21 | The slave parameters have been downloaded from DP master class 2 or the robot DP master | | | class 1. | | | 1. If the slave parameters are downloaded from DP master class 2, check that they are | | | correct. | | | 2. Check that the following item values on the DP master slave parameter setup screen are | | | correct. Slave flag | | | . Activate | | | ・New parameter from station type | +-------------+--------------------------------------------------------------------------------------------+ | 23 | The bus parameter baud rate has been downloaded from DP master class 2 or the robot DP | | | master class 1. | | | 1. If the bus parameter baud rate is downloaded from DP master class 2, check that it is | | | correct. | | | 2. Check that the baud rate on the DP master bus parameter setup screen is correct. | +-------------+--------------------------------------------------------------------------------------------+

Applicable equipment

Source: Fault JSON · FANUC_R30iB_全部故障码_中英双语.json · SHA-256 3eef897f540467130587726e7a53e338980cbb19f10ad88a4eddbec837fb0f55 · PROF-015

Brand	FANUC
Updated	2026-10-26

PROF-015

STOP.G DP sub error (code = %d)

[Cause]

A DDLM function call error occurred in the DP master software on the PROFIBUS board. This alarm supplements PROF-014. The number in parentheses indicates the error code. Refer to the table below.

[Countermeasure]

For sub-error codes other than those in the table below, contact the service department. Report the numbers in parentheses, which are needed to identify the condition.

+-------------+--------------------------------------------------------------------------------------------+ | Code Number | Annotations | +-------------+--------------------------------------------------------------------------------------------+ | 13 | Issue the correct service request in the correct operating mode. If slave parameters have | | | been downloaded to the robot controller, the operating mode can be set to CLEAR or | | | OPERATE. If slave parameters have not been downloaded, set the operating mode to STOP. | | | Note the above when issuing a service request from DP master class 2. | +-------------+--------------------------------------------------------------------------------------------+ | 14 | Check the DP slave status. | +-------------+--------------------------------------------------------------------------------------------+ | 17 | The parameter section of the slave parameters has been downloaded from DP master class 2 | | | or the robot DP master class 1. | | | 1. The parameter portion is confirmed as correct when downloaded from the DP host level 2. | | | 2. Check that the following item values on the DP master slave parameter setup screen are | | | correct. Station status | | | . Lock request | | | - Unlock the request. | | | ・Sync Request | | | ・Freezing requests | | | .WD Request | | | WD FACT1 | | | WD FACT2 | | | Minimum TSDR ID number group ID | | | ・ From group 1 to group 8. User parameter data byte count. User parameter data. | +-------------+--------------------------------------------------------------------------------------------+ | 18 | The configuration data section of the slave parameters has been downloaded from DP master | | | class 2 or the robot DP master class 1. | | | 1. The configuration data component is confirmed when downloaded from the DP host level 2. | | | 2. Check that the following item values on the DP master slave parameter setup screen are | | | correct. Configuration data byte count. Configuration data. | +-------------+--------------------------------------------------------------------------------------------+ | 19 | The address assignment table of the slave parameters has been downloaded from DP master | | | class 2 or the robot DP master class 1. | | | 1. The address distribution form is confirmed when downloaded from the DP Host Level 2. | | | 2. Check that the following item values on the DP master slave parameter setup screen are | | | correct. Input byte count. Output byte count. DPRAM input offset. DPRAM output offset. | | | 3. The input/output byte count for the PROFIBUS master and slave interface is too large. | | | Set the maximum number of DI/DO ports correctly on the PROFIBUS master setup interface. | | | Set the following system variables to the maximum allowed values. | | | $PRIMAVAR.$MAX_OUT_LEN = 32 => 128 | | | $PRIMAVAR.$MAX_IN_LEN = 32 => 128 | +-------------+--------------------------------------------------------------------------------------------+ | 20 | The slave user data section of the slave parameters has been downloaded from DP master | | | class 2 or the robot DP master class 1. | | | 1. If the slave user data section is downloaded from DP master class 2, check that it is | | | correct. | | | 2. Check that the following item values on the DP master slave parameter setup screen are | | | correct. Slave user data byte count. Slave user data. | +-------------+--------------------------------------------------------------------------------------------+ | 21 | The slave parameters have been downloaded from DP master class 2 or the robot DP master | | | class 1. | | | 1. If the slave parameters are downloaded from DP master class 2, check that they are | | | correct. | | | 2. Check that the following item values on the DP master slave parameter setup screen are | | | correct. Slave flag | | | . Activate | | | ・New parameter from station type | +-------------+--------------------------------------------------------------------------------------------+ | 23 | The bus parameter baud rate has been downloaded from DP master class 2 or the robot DP | | | master class 1. | | | 1. If the bus parameter baud rate is downloaded from DP master class 2, check that it is | | | correct. | | | 2. Check that the baud rate on the DP master bus parameter setup screen is correct. | +-------------+--------------------------------------------------------------------------------------------+

Applicable equipment

Source: Fault JSON · FANUC_R30iB_全部故障码_中英双语.json · SHA-256 3eef897f540467130587726e7a53e338980cbb19f10ad88a4eddbec837fb0f55 · PROF-015

Brand	FANUC
Updated	2026-10-26