6/7/2024 11:47 AM | |
Joined: 1/21/2013 Last visit: 9/12/2024 Posts: 3093 Rating:
|
Hi Fabi, According to your previous posts, you are using an ET 200SP CPU. If so, you should take a closer look at your diagnostic buffer, as the PLC should not stop in this case. STOP is only the default response to a programming error or a cycle monitor time violation. Regarding your task to send some information via MQTT, please be aware that the OBs are only executed once. So you should put all required data into one data block and set some bit to trigger the message. The message itself should be sent in a cyclic OB. Kind regards |
6/10/2024 5:23 AM | |
Joined: 4/26/2024 Last visit: 8/22/2024 Posts: 11 Rating:
|
Hi Stefan, First of all , thanks for your reply and help. Yes I have an ET200SP, sorry for not mentioning it. In my understanding I thought the OBs prevent the CPU from going into stop mode, I also see it in the Diagnostics that the IM Module gets unplugged and the code I have inside the OB also is executed but after the OBs code is executed the PLC goes into stop mode and the MQTT message gets send once it is back into run (i.e. after I plugged the IM Module back into the CPU). The message itself is sent in a cyclic OB (Main OB1) so this should not be the problem I'd assume. I have attached a file of the diagnosticsbuffer, sorry it's in german. Thanks in advance again. Fabi AttachmentDiagnose.txt (75 Downloads) |
Last edited by: AutoGen_7524768 at: 06/10/2024 07:04:59Last edited by: AutoGen_7524768 at: 06/10/2024 07:34:50Last edited by: AutoGen_7524768 at: 06/10/2024 07:41:31 |
|
Follow us on