导致 SINAUT ST7 中 CPU 出现错误信息的原因以及决方法是什么？

Description:
The TD7 typical with the instance DB [Info1] has discovered a parameter error on the parameter “PartnerNo”. The specified value is not within the permitted range of values.n

Reactions:
This message is entered once into the diagnostics buffer when the CPU is restarted or when the typical is reinitialized (e.g. after loading the instance DB).
The bit “OrgIndex_2_PF” is set in the instance DB and so the processing of the typical is blocked and the typical stops communicating.n

Possible causes and remedies:
Correct the parameter “PartnerNo” so that it has a value within the permitted range of values (see Online Help for the relevant typical).
The typical restarts online communication once the error has been cleared so that a restart of the CPU is not necessary.

Description:
The TD7 typical with the instance DB [Info1] has discovered a parameter error on the parameter “PartnerNo”. The specified partner node number is not known in the local CPU.n

Reactions:
This message is entered once into the diagnostics buffer when the CPU is restarted or when the typical is reinitialized (e.g. after loading the instance DB).
The bit “OrgIndex_2_PF” is set in the instance DB and so processing of the object is blocked. The affected object no longer communicates.n

Possible causes and remedies:

• Check if the specified node no. exists in the node management of the SINAUT ST7 configuration tool.n
• Check if a coection is configured between the specified node no. and the local node in the coection configuration of the SINAUT ST7 configuration tool.n
• Check if the SINAUT configuration data was correctly generated:
  In the “DBBasicData” (offline) there must be an entry “SubscriberObject[serial no.].SubscriberNo” with the initial value the same as the specified node no.n
• Check if the generated coection data was loaded into the CPU.
  In “DBBasicData” (online) there must be an entry “SubscriberObject[serial no.].SubscriberNo” with the actual value the same as the specified node no.

The object restarts online communication once the error has been cleared so that a restart of the CPU is not necessary.

Description:
the TD7 typical with the instance DB [Info1] has discovered a parameter error on the parameter “PartnerObjectNo”. The specified Partner Object number is invalid.n

Reaction:
This message is entered once into the diagnostics buffer when the CPU is restarted or when the typical is reinitialized (e.g. after loading the instance DB).
The bit “OrgIndex_2_PF” is set in the instance DB and so processing of the object is blocked. The affected object no longer communicates.n

Possible causes and remedies:
The parameter “PartnerObjectNo” of a communication object with the instance DB [Info1] was parameterized with a wrong value. The value range 1 – 32000 is always permitted. In some cases the value 0 is permitted.
You find the permitted value ranges in the Online Help for the communication object or in the SINAUT ST7 manual.
The object restarts online communication once the error has been cleared so that a restart of the CPU is not necessary.

Description:
The ST1 message block with the instance DB [Info1] has discovered a parameter error on the parameter “ST1_MessageNo”. The specified message number is invalid.n

Reaction:
This message is entered once into the diagnostics buffer when the CPU is restarted or when the object is reinitialized (e.g. after loading the instance DB).
The bit “OrgIndex_2_PF” is set in the instance DB and so processing of the object is blocked. The affected object no longer communicates.n

Possible causes and remedies:
An invalid value was parameterized on the parameter “ST1_MessageNo” of the ST1 message block with the instance DB [Info1]. ST1 message numbers can have values between 2 and 250.
The object restarts online communication once the error has been cleared so that a restart of the CPU is not necessary.

Description:
The ST1 message block with the instance DB [Info1] has discovered a parameter error on the parameter “ST1_MessageNo”. The specified message number is invalid.n

Reaction:
This message is entered once into the diagnostics buffer when the CPU is restarted or when the object is reinitialized (e.g. after loading the instance DB).
The bit “OrgIndex_2_PF” is set in the instance DB and so processing of the object is blocked. The affected object no longer communicates.n

Possible causes and remedies:
An invalid value was parameterized on the parameter “ST1_MessageNo” of the ST1 message block with the instance DB [Info1]. Check if the affected ST1 message block was correctly parameterized.
The object restarts online communication once the error has been cleared so that a restart of the CPU is not necessary.

Description:
The ST1 message block with the instance DB [Info1] has discovered a parameter error on the parameter “ST1_IndexNo”. The specified index number is invalid.n

Reactions:
This message is entered once into the diagnostics buffer when the CPU is restarted or when the typical is reinitialized (e.g. after loading the instance DB).
The bit “OrgIndex_2_PF” is set in the instance DB and so processing of the object is blocked. The affected object no longer communicates.n

Possible causes and remedies:
An invalid value was parameterized on the parameter “ST1_IndexNo” of the ST1 message block with the instance DB [Info1]. Check if the affected ST1 message block was correctly parameterized.
The object restarts online communication once the error has been cleared so that a restart of the CPU is not necessary.

Description:
The ST1 message block with the instance DB [Info1] has discovered a parameter error on the parameter “ST1_PACK_Value”. The specified value is invalid.n

Reactions:
This message is entered once into the diagnostics buffer when the CPU is restarted or when the typical is reinitialized (e.g. after loading the instance DB).
The bit “OrgIndex_2_PF” is set in the instance DB and so processing of the object is blocked. The affected object no longer communicates.n

Possible causes and remedies:
An invalid value was parameterized on the parameter “ST1_PACK_Value” of the ST1 message block with the instance DB [Info1]. Check if the affected ST1 message block was correctly parameterized.
The object restarts online communication once the error has been cleared so that a restart of the CPU is not necessary.

Description:
The data blocks could not be generated for object reference list 1 or 2.

The object reference list 1 is required so that received objects (messages) with incomplete target address can be processed correctly. Incomplete addressing takes place when objects are sent to target node no. 0 (send objects with PartnerNo = 0) or if the CPU is to receive ST1 messages.
Object reference list 2 is only generated if the CPU is to send ST1 messages.
However, object reference list 2 is not currently in use!n

Reaction:
With missing object reference list 1: using incomplete target addressing:
Received objects (messages) caot be evaluated; no data can be received.
With missing object reference list 1: using ST1 messages:
Received ST1 messages caot be evaluated, this means it looks as if no ST1 messages would be received.
With missing object reference list 2: no reactions; object reference list 2 is currently not required. Possible causes and remedies:
The following error code provides the causes in [Info2/3]:

Description:
The object reference list could not be completely created because the addressing of the objects/messages is not clear.
[Info1] specifies which nodes are involved.
[Info2] specifies which objects/messages are involved.

With ST7 communication objects, [Info2/3] displays the affected object number.

With ST1 messages [Info2/3] displays the affected message number “ST1_MessageNo” as well as the ST1 object number “ST1_ObjectNo” (the high byte of Info2/3 corresponds to the ST1 message number; the low byte corresponds to the ST1 object number)n

Reaction:
To a certain extent received objects/messages caot be evaluated.
It appears that not all messages are transferred.
This affects objects/messages with incomplete addressing (ST1 messages or ST7 objects/messages that are sent with the target address = 0).n

Possible causes and remedies:
The receive blocks for the ST1 messages or ST7 communication objects/messages are not clearly addressed.
There is multiple addressing.
The additional information Info1 and Info2/3 give you an idea which objects have multiple addressing.

Check if the addressing of the receive blocks is clear.
With ST7 communication objects:
A particular object may only occur once per node, that means all objects with the same partner number (“PartnerNo”) must be different in the parameter “PartnerObjectNo”.
With ST1 messages:
The same message number with the same ST1 object number may only occur once per node. That means all ST1 messages with the same partner number (“PartnerNo”) must be clearly different in the parameters “ST1_MessageNo” and “ST1_ObjectNo”.n

Warning: You caot differentiate using the parameter “ST1_IndexNo”.

Description:
The object reference list could not be found online.
Reference is made to the node no. [Info1] and the object no. [Info2/3] in the received message.n

Reaction:
The received object/message caot be supplied.
This affects objects/messages with incomplete addressing (ST1 messages or ST7 objects/messages that are sent with the target address = 0).n

Possible causes and remedies:
The block “ListGenerator” is missing or is not called in the cyclical program.
For B109: Online the data block with the data block address = “BasicData.DB_ObjectList1” is missing in the CPU
For B10A: Online the data block with the data block address = “BasicData.DB_ObjectList2” is missing in the CPU

Description:
The reference to the information on the source node is missing in the object reference list.
[Info1] specifies which nodes are involved
[Info2/3] specifies which objects/messages are involved

With ST7 communication objects, [Info2] displays the affected object number

With ST1 messages, [Info2] displays the affected message number “ST1_MessageNo” as well as the ST1 object number “ST1_ObjectNo”.
The high byte from Info2 corresponds to the ST1 message number, the low byte corresponds to the ST1 object number.n

Reaction:
The received object/message caot be evaluated.
This affects objects/messages with incomplete addressing (ST1 messages or ST7 objects/messages that are sent with the target address = 0).n

Possible causes and remedies:
The addressing of the receive blocks for the ST1 messages or ST7 communication objects/messages is not consistent.
The additional information Info1 and Info2/3 gives you an idea of which objects are incorrectly addressed.n

Check if the addressing of the receive blocks is consistent.
With ST7 communication objects:
An object (PartnerObjectNo= [Info2/3]) must occur at least once for the node (PartnerNo= [Info1]).
With ST1 messages:
The message number (ST1_MessageNo= [Info2]) must occur at least once for the node (PartnerNo= [Info1]).n

Warning: You caot differentiate using the parameter “ST1_IndexNo”.

Description:
The ST7 identification (A5h) is missing on the byte with the symbol name “ST7_ID” in the data block with the DB no.= [Info1].n

Reaction:
A received message is stored in the target object data block by FC distribute.
If the data block does not exist, then the CPU changes into the operating state “STOP”.
If the data block exists, but the ST7 identification is not A5h, then the received message alone is discarded.n

Possible causes and remedies:

• Incorrect addressing at the send block.n
• The instance DB does not exist online in the CPU. It has to be reloaded.n
• The ST7 identification in the data block was overwritten.n
• The data block is not an ST7 block.

Description:
There is no entry of a node object (“SubscriberObject[?]”) in the data block “DB-BasicData” with the DB no.= [Info1].n

Reaction:
The SINAUT program is aborted. No communication is possible.n

Possible causes and remedies:
No coection was configured between two SINAUT nodes in the SINAUT configuration tool.
A coection was configured between two SINAUT nodes in the SINAUT configuration tool, but it was not generated via node management.
The DB BasicData may have been copied from the SINAUT library into the current project.

Description:
The source node no. [Info2/3] specified in the receive message for the TD7 typical with the instance DB no. [Info1] is not known in the local CPU.n

Reaction:
The receive message is discarded.n

Possible causes and remedies:

• Check if the specified node no. exists in the node management of the SINAUT ST7 configuration tool.n
• Check if a coection is configured between the specified node no. and the local node in the coection configuration of the SINAUT ST7 configuration tool.n
• Check if the SINAUT configuration data was generated:
  In “DBBasicData” (offline) there must be an entry “SubscriberObject[serial no.].SubscriberNo” with the initial value the same as the specified node no.n
• Check if the generated coection data was loaded into the CPU.
  In “DBBasicData” (online) there must be an entry “SubscriberObject[serial no.].SubscriberNo” with the actual value the same as the specified node no.

Description:
The source node no. [Info2/3] specified in the receive message does not conform to the value of the parameter “PartnerNo” on the TD7 receive typical with the instance DB = [Info1].n

Reaction:
The receive message is discarded.n

Possible causes and remedies:
Check the parameterizing of both send and receive typicals, looking at the consistency of the current node no.
Also note the TD7 typicals of other nodes contained in the project.
Note:
– The TD7 send typical was perhaps copied to another node and the parameters “PartnerNo” and “PartnerObjectNo” were not changed.
– The node number of the send object has perhaps changed and the parameter “PartnerNo” was not updated on the receive object.

Description:
The source object no.[Info2/3] specified in the receive message does not conform to the value of the parameter “PartnerObjectNo” on the TD7 receive typical with the instance DB = [Info1].n

Reaction:
The receive message is discarded.n

Possible causes and remedies:
Check the parameterizing of both send and receive typicals, looking at the consistency of the current node no.
Also note the TD7 typicals of further nodes contained in the project.

Description:
The command/setpoint value message of the TD7 typical with the instance DB [Info1] to the target node no. [Info2/3] could not be entered in the communication DB.n

Reaction:
The message is discarded in the CPU.n

Possible causes and remedies:
The target node no. [Info2/3] is listed in the CPU as defective (not available).
Note:
The availability on the CPU can be checked via the ST7 block “PartnerMonitor” or “PartnerStatus”.

Description:
The MPI coection between the CPU and the local node no. [Info1] is defective.n

Reaction:
If it is a local node to a TIM module, the configured coections to the other nodes that communicate across this module are likewise disrupted. If no other (alternative) path is configured and able to function, then the affected nodes are likewise reported as defective.
If an alternative path was configured via another TIM module and if it hasn’t failed, then the data is sent via this path.

Command (Cmd01B_S) and setpoint value messages (Set01W_S) that are to be sent to a defective node are not entered into the send buffer of the CPU. These messages are lost.
The further data messages (e.g. Bin04B_S, Ana04W_S) are entered into the relevant send buffer (ComDB) of the CPU depending on the active data path and if the coection is error-free they are sent to the local TIM.
The further message handling depends on the individual subcomponents of the entire path.

The local node no. [Info1] is reported as defective in the status of the FC PartnerMonitor and the FC PartnerStatus.
Depending on the configured coections and their status, the affected nodes are reported as defective or OK in the status of the FC PartnerMonitor and FC PartnerStatus.
The status of the FC PartnerMonitor also displays if a node is available across all coections or not.n

Possible causes and remedies:
Check the MPI coection between the CPU and the node no. [Info1].
Check if the node no. [Info1] is functional.

Description:
The coection between the CPU and node no. [Info1] is defective.n

Reaction:
Command (Cmd01B_S) and setpoint value messages (Set01W_S) that are to be sent to a defective node are not entered into the send buffer of the CPU. These messages are lost.
The further data messages (e.g. Bin04B_S, Ana04W_S) are entered into the send buffer of the CPU and if the coection is error-free they are sent to the local TIM.
The further message handling depends on the individual subcomponents of the entire path.n

The local node no. [Info1] is reported as defective in the status of the FC PartnerMonitor and the FC PartnerStatus.n

Possible causes and remedies:
Check the coection between the CPU and the terminal nodes.
Check if the node no. [Info1] is functional.

Description:
An error was discovered in the general query of the node [Info1]. The general query is incomplete, that means either not all the objects expected as part of the general query were received or the monitoring time has run out.

As part of a general query, the CPU expects that the queried node will send all objects within a certain time. This monitoring time is currently fixed at 900 seconds for a ST7 CPU (parameter “SubscriberObject[x].SupervisionTime” in the DB BasicData).
Unless all objects are received during this monitoring time, the general query is regarded as defective.n

Reaction:
If a complete general query is recognized, then the message is entered once into the diagnostics buffer of the CPU.
The FC PartnerMonitor displays the status “General query defective” (see Online Help for FC PartnerMonitor).n

Possible causes and remedies:

• Receive objects were configured, but no send objects exists for these in the partner CPU.
  Every send object (e.g. “Bin04B_S”) must have a corresponding receive object (e.g. “Bin04B_R”).
  Every missing object also results in a diagnostics message entry into the diagnostics buffer of the CPU. (see event ID 16#B162)n
• After triggering the general query, the coection to the queried node was interrupted for a prolonged period.n
• The addressing of the communication object is wrong. Check the address parameters “PartnerNo” and “PartnerObjectNo”.n
• The object addressing used is incomplete (objects with PartnerNo = 0) whereby the FC ListGenerator was not called in the cyclical program.

Description:
The object no. [Info1] was not transferred as part of a general query of the node no. [Info2/3].n

Reaction:
The general query is incomplete. This results in the entry of a diagnostics message with the event ID 16#B160 in the CPU.n

Possible causes and remedies:

• No send object was parameterized for the object no. [Info1] in the partner CPU with the no. [Info2/3].
  Every send object (e.g. “Bin04B_S”) must have a corresponding receive object (e.g. “Bin04B_R”).n
• The addressing of the communication object no. [Info1] is wrong. Check the address parameters “PartnerNo” and “PartnerObjectNo” of the appropriate object.n
• The object addressing used is incomplete (objects with PartnerNo = 0) whereby the FC ListGenerator was not called in the cyclical program.

Description:
There was a change within the same cycle to the typical input parameters “CommandInputByte_HW” and “CommandInputByte_SW” on TD7 typical with the instance DB [Info1].n

Reaction:
The input is rejected.
The error status is displayed via the output “InputError” of the FC Safe and appropriate error bits are set in the central data block “DB-BasicData” that can be queried by the software (see SINAUT ST7 manual: FC Safe)n

Possible causes and remedies:
You must ensure that always only one of the two typical input parameters (“CommandInputByte_HW” or “CommandInputByte_SW”) gets an input within the same cycle.
Note:
If the exact same value is entered on both typical input parameters (“CommandInputByte_HW” and “CommandInputByte_SW”) then this is accepted; the hardware input is processed further.

Description:
There was a 1-from-8 error on the parameter “CommandInputByte_HW” or “CommandInputByte_SW” on TD7 command typical (“Cmd01B_S”) with the instance DB [Info1].n

Reaction:
The input is not processed.
A new input is only read in again if no hardware or software command was previously recorded in the PLC for an OB1 cycle.
Appropriate error bits are set in the central data block “DB-BasicData” that can be queried by the software (see SINAUT ST7 manual: FC Safe)n

Possible causes and remedies:
More than 1 bit has changed within an OB1 cycle in the command input byte (“CommandInputByte_HW” or “CommandInputByte_SW” ).

Description:
There was a 1-from-N error on the CPU due to an input on the parameter “CommandInputByte_HW” or “CommandInputByte_SW” of the TD7 typical with the instance DB [Info1].
Additional info: [Info2/3]
0 = command (“Cmd01B_S”) or setpoint value (“Set01W_S”)
1 = command (“Cmd01B_S”)
2 = setpoint value (“Set01W_S”)n

Reaction:
The input is not processed.
A new input is only read in again when no new value was previously recorded for an OB1 cycle in the PLC on the parameter “CommandInputByte_HW” or “CommandInputByte_SW” for all command and setpoint values.
Appropriate error bits are set in the central data block “DB-BasicData” that can be queried by the software (see SINAUT ST7 manual: FC Safe)n

Possible causes and remedies:
There were command or setpoint value inputs on the CPU from more than one TD7 object (TD7 typical) within the same OB1 cycle.
The FC Safe was perhaps not integrated into the CPU’s cyclical program.

Description:
A received command object contains incorrect net data. This message is created by the command evaluation object “Cmd01B_R” or “BTA01”.n

Reaction:
In the received command message, the command and control bytes are not identical. The received command is discarded and not issued by the block “Cmd01B_R” or “BTA01”.n

Possible causes and remedies:
The data content of the messages is falsified by sources of interference on the transmission route.
The falsification of the message is so severe that the normal security mechanisms for recognizing transmission errors no longer work (hamming distance = 4 is no longer sufficient).n

Explanation of command transmission
So that there can be no falsification of the sent commands on the WAN transmission route, command bytes are transmitted with increased security.
Mirrored transmission is used here whereby the original command byte and a copy of it are sent.
On receipt of a command message, the receive block “Cmd01B_S” compares if the command information and a copy are still identical. This helps you to recognize falsifications of the command bytes on the WAN transmission route.

Description:
A received command object contains incorrect net data. More than one bit is simultaneously set in the received command byte.
This message is created by the command evaluation object “Cmd01B_R” or “BTA01”.

Reaction:
More than one bit is set in the received command message. The received command is discarded and not issued by the block “Cmd01B_R” or “BTA01”.

Possible causes and remedies:
Check if the rules from the 1-from-8 control were observed when sending commands. You must set only 1 bit in a command byte.

If the rules were observed, serious interruptions on the transmission route might be the cause. Serious sources of interference might falsify the content of the command message. The falsification of the message is however so severe that the normal security mechanisms for recognizing transmission errors no longer work (hamming distance = 4 is no longer sufficient).