12/31/2014 9:40 AM | |
Posts: 3 Rating:
|
Hello all. Regarding the problem with OB30,with its cycle time set to 1ms, I realized that the particular OB, brings the CPU to STOP only if I use "%M" memory adresses in it. If I use DB-memories, then the OB is working better. Nevertheless, if I interrupt the PLC's power supply and I re-supply it, then the CPUcannot go to RUN automatically, due to this OB30. I need to set it to run from the PC. ------------ New subject after splitting from Cyclic interrupt stop CPU. |
Last edited by: Min_Moderator at: 12/31/2014 2:33 PMSplitted |
|
12/31/2014 4:02 PM | |
Posts: 3 Rating:
|
Hello all. Regarding the problem with OB30,with its cycle time set to 1ms, I realized that the particular OB, brings the CPU to STOP only if I use "%M" memory adresses in it. If I use DB-memories, then the OB30 is working better. Nevertheless, if I interrupt the PLC's power supply and I re-supply it, then the CPUcannot go to RUN automatically, due to this OB30. I need to set it to run from the PC. ... AND THE SOLUTION IS... Delay the first execution of the OB30, after the CPU goes to RUN, do not use "%M" memories in the OB30. Use only DB memories in the OB30,which by the way, have to be NON retentitive (if you check their "Retain" box, then the CPU stops). I tested all above mentioned on a CPU 1211C, with firmware version 2.0 and it works fine. If you take a look inmy attached pdf, you will see that the program inside OB30 is not small. So all the advices already written by some colleagues, that the program inside OB30 has to be small, are rather excessive. To my humble opinion all this OB30-thing appears to be one of the huge or small firmware issues,that other manufacturers have already solved since ages... ------------ New subject after splitting from Cyclic interrupt stop CPU. AttachmentCyclic interrupt OB30.pdf (127 Downloads) |
Follow us on