Thomas10100

Hi!

How can I resolve to have checks interrupted in a program?

So:

The encoder counts from 0-180.

For example:

FC1

Undercap check Encoder position at 20.

Cap check Encoder position at 50.

FC3

Closing check Encoder position at 90

FC10

Rejecting Encoder position at 180.

Check positions are stored in recipes for products.

How can I create more interrupts for different positions?

S7-1214 the PLC

Thanks!

 What version of TIA?

What is the firmware of your PLC?

Which HSC instruction are you using?

You can setup you HSC to generate hardware interrupt when reference value equals counter value; you do that in hardware configuration. The reference value can be changed in code so you can start by setting reference value to equal 20 and when HSC current value equals 20 a hardware interrupt OB will be executed for one cycle. Then you can set reference value to 50 and the previous scenario will be repeated and so on. CTRL_HSC_EXT has two  reference values NewReference1 and NewReference2 so you can set two values at a time, NewReference1 =20 and NewReference2 = 50 and then keep changing them as you need.

Firmware 4.2V
Tia Portal V15
An HSC is used for speed measurement and one is used for the current value: ID1000. Currently, the HSC is in block FC1, where the current and control values are compared. This is a bit with SET and this bit is read during the check and if it is done then RESET.
I call FC1 before each control block.

I want to do it nicer.

Thanks!

Difficult to understand, form those snippets, what you're trying to do.

Your first post gave me the impression you are doing some kind of positioning and wanted to use interrupts which is quite common.

I also do not understand if you are using two HSC instructions with two counters or one counter.

But I understand you have everything working the way you want and just want something "nicer" and in that case I will just describe my general observations.

The use of comparison with ID1000 is fine when you have a large margin to work with because it will be affected by cycle scan and how fast the counter is counting (how fast the pulses are coming).

So going by your first post, I would do the following:

-I would use CTRL_HSC_EXT but I will describe the legacy one for you.

-In hardware configuration for HSC1 and enable "Generate interrupt for counter value equals reference value event" and setup and create and interrupt OB.

-In FC1 I call HSC instruction as you did and either in the same (FC1) or another I will have code that sets the values for NEW_RV and sets RV bit to true. The values will depend on the process and where I am positioning. First value will be starting position, then when that position is reached and the process is moving to the next stage then the value will be set to the next position.

-When the counter reaches the reference value the interrupt I set in hardware configuration will be triggered and inside the interrupt I will do something which entirely depends on the process. Let's say I have a conveyor moving and I want to stop it at that position then I will have an immediate call to reset  the output controlling the motor Q0.0:P which has an immediate effect and will insure greater positioning accuracy. In the network below it I will either set a global tag to indicate that position has been reached with the purpose of updating the status in my code or will directly call the block controlling motor execution. (this is tricky and can increase scan cycle if not executed efficiently).

-Now back in FC1 or wherever NEW_RV is and with the help of the tag that was set in the interrupt I will move on to the next phase in the process and set NEW_RV to the next position.

What is the purpose of M80.1 placed at SR.Q instruction?

The attachment is form our old and missed friend William_B

Thomas10100

The program is working now, I want a more efficient solution (in terms of PLC execution).

I mean the part that needs to be set in the Hardware config to call an interrupt. Also, I understand the part that the CTRL_HSC block can be used to set a new value for when the interrupt should be.

I don't understand the process of where to call the CTRL_HSC block, that I have to resolve that there are multiple locations within a program for control and different positions. Or to make it the most efficient code.

Thanks!

Hello.

What you have now is okay. There is no need for you to worry about the efficiency.

There is the alternative solution which uses an interrupt trigger each time the counter value equals the reference value (CV = RV). The process needs sequencing and binding interrupt with the regular processing. The CTRL_HSC (or newer CTRL_HSC_EXT) is called in the regular sequence. The process of paging through different positions is kind-of complicated and will take time to explain.

You may even find the complication not worth your time to implement.

I leave it to you to decide. It will be up to Kal.A or another helper to assist you if you reply to my message. My person opinion is to go with what you have.

BR

Thomas10100

The program is working now, I want a more efficient solution (in terms of PLC execution).

I mean the part that needs to be set in the Hardware config to call an interrupt. Also, I understand the part that the CTRL_HSC block can be used to set a new value for when the interrupt should be.

So you have the interrupt issue figured out and able to set new value and all that is working the way you want it. Excellent.

I don't understand the process of where to call the CTRL_HSC block, that I have to resolve that there are multiple locations within a program for control and different positions. Or to make it the most efficient code.

Thanks!

How many times you call CTRL_HSC instruction is entirely dependent on your code and how it is structured. Obviously you need to call it at least once and the question is should you call it again?

Calling the instruction updates the counter (actually a counter system function)  with the actual parameters that you interfaced at the instruction like NEW_CV and RV and the rest. So let's say after network 2 in FC1 and when the comparison of ID1000 is true you want the counter value to be reset to zero or any other number and the code following it will be influenced by the counter value then yes absolutely call the instruction again after the comparison to have the counter value take effect before the cycle scan is done. If your program  requires that much precision you would know it right away.

This is sometimes done in the hardware interrupt for reference value; if you want the counter to have a different value as soon as the reference value is reached you can call the instruction in the hardware interrupt OB to change NEW_CV. Or another  example that applies to your first post would be setting New_RV to 20 and then in the interrupt that is triggered when Count Value= Reference Value, you would set New_RV to 50 and RV to true followed by a call to  HSC_CTRL instruction. That would update the reference value the quickest.

ID1000 memory is read at the beginning for the scan cycle and depending on the length of the cycle and how fast the pulses are coming there may be a difference in the value. If you suffix it with a colon and the letter P like this ID1000:P you will get the current value of the counter; the :P is causes and immediate read or write.