Place of Origin: | GERMANY |
Brand Name: | LENZE |
Certification: | CE |
Model Number: | E82ZAFIC010 |
Minimum Order Quantity: | 1pcs |
---|---|
Packaging Details: | carton |
Delivery Time: | in stock |
Payment Terms: | T/T, Western Union, MoneyGram |
Supply Ability: | 100pcs/week |
LENZE: | LENZE | E82ZAFIC010: | E82ZAFIC010 |
---|---|---|---|
Material: | Iron | Color: | Black |
Temperature: | 20-90 | Wire: | Wire |
Dimension: | 80mm | Germany: | Germany |
Procedure 1. Open the Main[OB35] program block and insert the MOVE instruction into network 10. |
nsert a reset coil after the MOVE instruction. |
. Expand the instruction to a total of four outputs. | Interconnect the inputs and outputs of the MOVE instructionThe EN/ENO mechanism is interconnected for this block. If there are no errors during |
Insert a normally open contact before the MOVE instruction. | execution, the ENO enable output has the signal state "1". If there are errors during |
execution, the ENO enable output has the signal state "0".The MOVE and Reset instructions should be expanded with detailed commentary.
Procedure
1. Insert a comment using the shortcut menu.
2. Enter the comment text.
Result
The comments for the instruction and the coil are entered. Unlike the CPUs of the S7-300/400, CPUs of the go to STOP with errors much less
often. If an error occurs, it is entered in the diagnostics buffer of the CPU. You avoid the
CPU STOP by using local error handling at each block. You should preferably enable local
error handling during development of the user program.You can precisely evaluate the information and, for example, program the error handling in
the block with STL/FBD/LAD and SCL programs. The block generates an error ID that is
evaluated by the "GET_ERROR_ID" instruction. You can call the "GET_ERROR_ID"
instruction in both the MAIN block and in the function blocks. The CPU remains in RUN
mode.To illustrate the local error handling, load the blocks of the "ProgLib_LEH" library in the
project. The blocks are used only to demonstrate the local error handling and are otherwise
not used in the project.
Procedure
1. Open the global library, "ProgLib_LEH".
2. Copy the blocks from the master copies into the project.Call the "LAD_Local_Error_Handling" function block in an empty network of the "Main"
blockUse the "LEH_INDEX" tag at the "INDEX[0..100]" input parameter to trigger a programming
error in the following. For example, if you set the input parameter to "101", an error at the
output parameters is reported.Perform the following steps to trigger a programming error without using the local error
handling or creating a corresponding OB.
Procedure
1. Activate the "Monitor" function.
2. Set the value of the "LEH_INDEX" tag to an invalid value, for example, "101". In the
Testing dialog, the ERROR LED flashes briefly and the CPU goes from RUN to STOP3. Switch to the diagnostics buffer. The error and the error response is displayed in the
diagnostics buffer.
4. Set the CPU back to RUN.
Result
The transition from STOP in RUN resets the "LEH_INDEX" tag to the start value "0". This
automatically solves the problem.Perform the following steps to use "GET_ERR_ID" instruction and its ENO bit for the local
error handling to respond to the error with an error message. This means the CPU remains
in RUN mode.
Procedure
1. Open the "LAD_Local_Error_Handling" function block.
2. Insert the "GET_ERR_ID" instruction in the second network and interconnect the "ID"
output.3. Call the "ErrorID_to_ErrorText" function from the project tree.
4. Interconnect the parameters of the "ErrorID_to_ErrorText" function so that they can
convert the error code into an error message.
5. Load the changes to the CPU.
6. Trigger an error in the "Main" organization block by entering an invalid value, for example,
"101". An error message is output at the "ERROR_MESSAGE" parameter.