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

rising edge interrupt at I0.0 of 1212C PLC

Created by: HydroPLC at: 4/16/2012 7:54 AM (32 Replies)

Rating (2)

Thanks 3

Result pages:: |; 1 | 2 | 3 | 4; |

33 Entries

Entries per page: 10 | 20 | all

4/16/2012 7:54 AM	Rate (0)
HydroPLC Posts: 13 Rating: (0)	Hello, I have been trying to use rising edge interrupt at I0.0 of 1212C PLC, but without any success. I am not sure if it is the hardware issues. I am using the following: Windows XP pro sp3 TIA portal v10.5 sp2 S7-1212 AC/DC/RLY., Firmware v1.0, Module version 1.0.0.0 I configured the device properties for I0.0 for rising edge hardware interrupt. I put a UP counter in the interrupt OB (OB200) but no counting is seen with I0.0 as the signal for the input to the count. If I use an ATTACH function in the main OB for the OB200 with the I0.0 risisng edge event, then the RET_VAL at the ATTACH has a value of -32621, which is not listed in the manual as a possible error output. I did not see much information on hardware interrupt in the forum. Can anyone please explain this behavior of the PLC? Thanks in advance.
HydroPLC Posts: 13 Rating: (0)	Last edited by: O_Moderator at: 4/17/2012 12:28 PM new subject after splitting from /tf/WW/en/Posts/67366#top
Suggestion To thank Quote Answer

4/16/2012 2:30 PM	Rate (0)
Gorp Posts: 89 Rating: (16)	You can not use an up-counter in your interruptroutine since an up-counter uses a flank detection. This means it needs to see the count input going from low to high. Since you call your interrupt wheninput 0.0 goes high, the interrupt routine never sees input 0.0 as low, it's sees it high all the time. You should use an increment instruction instead.
Gorp Posts: 89 Rating: (16)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Tomy Master

4/16/2012 9:54 PM	Rate (0)
HydroPLC Posts: 13 Rating: (0)	Thanks Corp, I tried to use increment "INC" instruction in the hardware interrupt OB with the triggering bit as I0.0. (without the \|P\| ). However, the interrupt does not seem to triggered at all when I change the staet of I0.0 from 0 to 1.. When I try a Normally open contact at the Main OB with an INC instruction there, y=the count keeps on increasing so ,ong as I0.o is ON. If I change the I0.0 into a \|P\| type in the Main OB, it increments by 1 at a time. Tis means that the interrupt is not working. Am I correct to assume that the interrupt need not be called or attached. It only need to be configured in the device digital input at I0.0. Thanks for your help.
HydroPLC Posts: 13 Rating: (0)
Suggestion To thank Quote Answer

4/16/2012 11:02 PM	Rate (0)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 3/21/2025 Posts: 15745 Rating: (2489)	HydroPLC Thanks Corp, I tried to use increment "INC" instruction in the hardware interrupt OB with the triggering bit as I0.0. (without the \|P\| ). However, the interrupt does not seem to triggered at all when I change the staet of I0.0 from 0 to 1.. When I try a Normally open contact at the Main OB with an INC instruction there, y=the count keeps on increasing so ,ong as I0.o is ON. If I change the I0.0 into a \|P\| type in the Main OB, it increments by 1 at a time. Tis means that the interrupt is not working. Am I correct to assume that the interrupt need not be called or attached. It only need to be configured in the device digital input at I0.0. Thanks for your help. If you have enabled a HSC on that input, the hardware interrupt will not function. Not saying you did, but if your project configuration somehow managed to enable the HSC, disable it. Now that the HSC is verified disabled (which I believe it already was disabled...), the documentation for my TIA Portal V11 (SP2 update 2) states the OB # for Hard Int >= 123 and you can have up to 50 of them. I created one and it started them off at OB 40. OB200 and up will definitely not work. Maybe in your digital input 0.0 configuration, you can do a screenshot of the OB being called (it should be named Hardware_Interrupt, or Hardware_Interrupt_1 and so on with the name being automatically assigned. In your Hard Int OB, do you assume the input is HI and process that way? I prove my OB runs by putting a simple ADD block in there and have it simply increment each time it is called. I then put the add value into a watch table, toggle the input from low to hi, and observe the counter. If the counter counts multiple times, increase the debounce time. Test a few times until everything works, then disable the timer with some test bit you can toggle to perform the test again in the future should it be necessary (optional but it does help as you do not need to recompile, just toggle a bit and it starts counting again).
	science guy
Suggestion To thank Quote Answer

4/16/2012 11:05 PM	Rate (0)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 3/21/2025 Posts: 15745 Rating: (2489)	You can not use the -\|p\|- or P_TRIG type of instructions inside hardware & diagnostic interrupts as they run one scan and have no 'memory' of the prior state. That is why I use the simple add block. I'm sure there is a better way, but it is easy to understand and explain and the same technique works on multiple plc platforms :)
	science guy
Suggestion To thank Quote Answer

4/17/2012 2:08 AM	Rate (0)
Gorp Posts: 89 Rating: (16)	Ok, I am not going to argueso here is a sample program. Just set up I0.0(channel 0) in your device configuration and one network in OB 200 will do the job. There is no need to ATTACH or DETACH any interrupt. I have added the network in OB1 so you can monitorthe counter value when you go online. Attachment increment on interrupt.zip (817 Downloads)
Gorp Posts: 89 Rating: (16)
Suggestion To thank Quote Answer

4/17/2012 3:40 AM	Rate (0)
HydroPLC Posts: 13 Rating: (0)	Thanks. I checked and found that no HSC is enabled. Vesion 10.5 of TIA allows only OB #200 to #32767 for Hardware Interrupt at creation of New HW Interrupt OB. I wonder why OB number is different for TIA vesion VII? Is there any way to find that the action of hardware interrupt itself happens on arising edge? Watch table does not seem to show any info to indicate that it is happening. I have a version V11 of TIA portal, but I am concerned whether it will work with the WinCC Flrxible 2008 Advanced sp2 I am using with a MP377, 15" touch with old Windowes CE 5.0? I do not wish to upgrade the firmware on the MP377 because it is being used curently and concerned about trouble if the firmware is upgraded!Anyone knows about the comptibility of these two software- TIA v11 and wincc 2008? Thanks in advance.
HydroPLC Posts: 13 Rating: (0)
Suggestion To thank Quote Answer

4/17/2012 2:41 PM	Rate (0)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 3/21/2025 Posts: 15745 Rating: (2489)	HydroPLC Thanks. I checked and found that no HSC is enabled. Vesion 10.5 of TIA allows only OB #200 to #32767 for Hardware Interrupt at creation of New HW Interrupt OB. I wonder why OB number is different for TIA vesion VII? Is there any way to find that the action of hardware interrupt itself happens on arising edge? Watch table does not seem to show any info to indicate that it is happening. I have a version V11 of TIA portal, but I am concerned whether it will work with the WinCC Flrxible 2008 Advanced sp2 I am using with a MP377, 15" touch with old Windowes CE 5.0? I do not wish to upgrade the firmware on the MP377 because it is being used curently and concerned about trouble if the firmware is upgraded!Anyone knows about the comptibility of these two software- TIA v11 and wincc 2008? Thanks in advance. Understand on the OB# for the hard int OBs. Maybe V11 is the first time Portal is integrating with S7-300/400 and trying to be more standard between basic/pro versions? I do not have the pro version so cannot be sure. I too have a couple of those MP377 screens in use with V10.5SP2. Since the PLC program is written with all standard DB access, it should migrate well. Later this year I will test the theory, but until then, I do not know. If you have a spare MP377, update the firmware in that one, load the program, run it on the current system for a quick test to verify it works with new firmware. Then you can use that for developing the migrated V11 project. If you do not have a spare MP377, I found the lead times to be fairly long, so it would be good to have one on hand - despite the high cost. As for the config, I think you can choose rising or trailing edge detection and as the prior poster suggests, one network can handle all the interrupt logic necessary to handle the state change.
	science guy
Suggestion To thank Quote Answer

4/18/2012 6:38 AM	Rate (0)
HydroPLC Posts: 13 Rating: (0)	Thanks Gorp. I ran the application on two PLCs. (S71212C-AC/DC/Rly). Both did not work. I wonder has it anything to do with any vesion or firmware number. Attached is a screen shot of the running application. The Main and the Interrupt OB200 are seen along with a watch table which shows the Input I0.0 as "TRUE", but no count update on MW100 or MW102. The interrupt configured on channel 0 (for rising edge) is also seen at the screen shot. Can anyone else also join with testing the program from Gorp? Attachment Screen_Shot_of_running_HWINterrupt_Counter.pdf (809 Downloads)
HydroPLC Posts: 13 Rating: (0)
Suggestion To thank Quote Answer

4/18/2012 3:44 PM	Rate (1)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 3/21/2025 Posts: 15745 Rating: (2489)	It appears you have rediscovered a bug in older firmware. If the PLC FW is not the latest for the software you are using, I say update it. For now, you can of course simulate the interrupt function putting the interrupt code in an FB and call that FB from the HW interrupt (OB200) as you have it set up, PLUS have a P_TRIG on I0.0 call FB to increment MW100. If you are using 10.5 SP2, FW 1.2.x is advisable. V11+, FW 2.2 is best. Be sure and match the plc configuration FW level to the installed firmware level. Portal generally seems to allows you to have higher firmware installed than configured in the project.
	science guy
Suggestion To thank Quote Answer

Result pages:: |; 1 | 2 | 3 | 4; |

33 Entries

Entries per page: 10 | 20 | all

|

Share this page:

Share this page on...

Follow us on