Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

S7-1200 and hardware interrupt OBs

Created by: attis at: 4/22/2013 1:03 PM (5 Replies)

Rating (2)

Thanks 2

6 Entries

4/22/2013 1:03 PM	Rate (0)
attis Posts: 4 Rating: (0)	Hello! I am using: S7-1214C 6ES7 214-1HG31-0XB0 V3.0 SB1221 6ES7 221-3AD30-0XB0 V1.0 and some other modules ... TIA Portal V11 SP2 I've enabled rising edge events at 2 digital inputs (I0.4 and I0.5) and added 2 hardware interrupt OBs, one for I0.4 and another for I0.5. During the testings I had to realise that the second OB does not execute, so I deleted it and tried to detect the source of the event within a single OB using I0.4:P and I0.5:P. Now the rung with I0.5:P was not executed. Eventually I had to realise that the rising event at the second input is not "handled". When I moved the second input line from I0.5 to I 0.6, the rising event worked and the rung with I0.6:P was executed. I did a last test and connected my first input line from I0.4 to I0.7. Now the rung with I0.7:P was not executed. Does that mean that I can use only every second input for interrupt handling? I could not find anything about this in the S7-1200 system manual (04/2012). Did I miss something. Some other questions regarding the hardware interrupt OBs regarding S7-1200: 1.According to the S7-1200 system manual I should use interrupt OBs from number 200 and up, however in the TIA Portal when I add the OB, I can choose from 40-47 and 132-32767? OB40 works fine, too. 2.Aren't there local variables in the OB likeOB40_POINT_ADDR(as in the case of S7-300)? Thanks!
attis Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

4/23/2013 10:01 AM	Rate (0)
attis Posts: 4 Rating: (0)	Hi there! Nobody had the same problem with the interrupts? Any explanation? BR Attila
attis Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

4/23/2013 3:30 PM	Rate (0)
0_Einstein Grandmaster-Expert Joined: 7/7/2010 Last visit: 12/23/2025 Posts: 16325 Rating: (2520)	attis Hi there! Nobody had the same problem with the interrupts? Any explanation? BR Attila Maybe we are confused by the question? I know I am still not quite sure what question is asked. It felt more like a comment without screenshots to let us see what you saw. I am unclear whether in your interrupt OBs whether you used the :P or just assumed the input was in the state necessary to actually execute the OB. Seems like a waste to look at the input again, and possible even incorrect results could occur. If you put counters in your interrupt OBs, do they count up (an easy way to see the OB was triggered)? That is the simplest way I know to count interrupt event handling and it can be seen in the watch table while inputs are switched to trigger the edge OBs.
	Last edited by: huggy_d1 at: 4/23/2013 3:31 PM [For counter, I mean, just add 1 to some tag every scan. Since the OB is only active for a single scan per trigger, your add block is a counter.] science guy
Suggestion To thank Quote Answer

4/24/2013 9:33 AM	Rate (0)
attis Posts: 4 Rating: (0)	Hello! Sorry for the fuzzyness! I attached a screenshot about the inside of my HW interrupt OB, the version which works. When I change input I0.6:P to I0.5:P then that rung is not executed (1 is not moved into that tag MW26) I also tried to use a counter before, as you mentioned (add 1 to a tag), that is how I saw that something is wrong. Also, if I use inputs I0.6:P and I0.7:P, than the rung with I0.7:P is not executed. (When I changed the inputs, I set the trigger event and OB in the hardware config, too.) It looks like I cannot use two inputs next to each other. BR Attachment this works.JPG (2874 Downloads)
attis Posts: 4 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users JEYAPRAKASH SP

4/24/2013 4:10 PM	Rate (2)
0_Einstein Grandmaster-Expert Joined: 7/7/2010 Last visit: 12/23/2025 Posts: 16325 Rating: (2520)	Have you tried a single hardware interrupt for each unique hardware trigger? For example: OB200, HW_Interrupt_0, assigned to rising edge of I0.0. OB201, HW_Interrupt_1, assigned to rising edge of I0.1. It certainly sounds like a hardware problem. Thanks for the screenshot. It really helped.
	science guy
Suggestion To thank Quote Answer

4/25/2013 8:09 AM	Rate (0)
attis Posts: 4 Rating: (0)	I did as you said. Two separate OBs, no inputs in them, only the MOVE blocks. Now it works fine! Thanks a lot!
attis Posts: 4 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users 0_Einstein

|

Share this page:

Share this page on...

Follow us on