9/2/2021 11:52 AM | |
Joined: 3/5/2014 Last visit: 8/5/2022 Posts: 5521 Rating: (1054)
|
hi, for diagnostic interrupt you can use this application sample: With diagnostics-compatible modules how do you evaluate a change of the diagnostics status in the user program of the S7-300?You can do the same in OB40. The difference is that OB40 is not called because of an error, it is called because of another event. If you just want to have shown something on your HMI, you only need to evaluate the address and channel from the OB40 header and set a bit if it is the rigth channel. this bit triggers a message on the HMI. hope this helps. P.S: If this information doesn´t helps you, you should consider to visit a professional training for automation. no offense, but if programming isn´t done in the rigth way, yours and others health may be in danger! |
FCK WAR! |
|
9/3/2021 3:25 AM | |
Joined: 3/16/2015 Last visit: 10/10/2021 Posts: 1250 Rating: (173) |
OB 82
OB 40 has nothing to do with Diagnostics. It can be configured only for violation of high or low limits and will have no effect at all on whether the CPU stops or not. I just saw your first thread and you are doing fine. All you were missing was OB 82. Now that you added OB 82 all you have to do is compile the hardware and download it; it should work fine then. Here's a manual that may be helpful. |
Last edited by: Kal.A at: 09/03/2021 03:36:13Last edited by: The Helping Hand at: 09/03/2021 08:36:23Optimized link. |
|
Follow us on