The default input for your I0.0/0.1/0.2/0.3 is 6ms if I recall correctly.

Change the input filter time to the small possible time value to perform high speed counting.

I *KNOW* Siemens should do this for us, but they do not. 

cody_master

Hi. Please help me.

I have the hardware:

1. MOTOR 0-30 RPM

2. CPU 1214C DC/DC/DC

3. INCREMENTAL ENCODER 720 RPM

I connected:

A with I0.0

B with I0.1

Z with I0.3

A- B- and Z- no connection

I configured the hardware in TIA PORTAL V13 as:

Enable HSC_1 as counter A/B

Enable external reset and create the hardware interrupt OB 40.

I configured the software in TIA PORTAL V13 as:

I MOVE ID1000 to Dint variable to monitoring on OB1.

Well....

I can read the speed counter when this is slow but its missing when the speed is little fast (18 RPM).

This counter value is to enable some outputs. But when its slow no problem (<6 RPM) but the ouputs is lost when the speed is upper.

Please help me.

You are so right! 

cody_master

This information should be in the manual 

Thanks so much...

cody_master

I connected:

A with I0.0

B with I0.1

Z with I0.3

One more  fly in the soup...
If you wish to get a continuous count for continuous rotation,
then disconnect the Z-phase.
The Z-phase will restart the counter at each rotation.

cody_master

Hi. this no problem dear William_B.


I need reset the value for this reason i have to connect the z-phase.

I need activate some outputs around 0 -360 °. one and other time.

But, when the speed is little upper the counter value is lost inclusive the z-phase.

Good!  So then <huggy_d1> has given already the answer.

Just one more concern... how do you check if the axis is in position?
Do you use the "double integer input" variable (example "myHSC")
or do you use HSC interrupts?

If you use "myHSC" (example) variable, be careful for..
* do not use equal compare
* measurements around 360°

Recommendation: Use cam concept - define a window of trigger points.
Still be careful on handling around around 360°.

cody_master

 Ok. i did this.

1. I have one button on HMI to define ZERO POINT.

2. In OB40 once z-phase launch capture. this value when cross exactly for this wherever point.

3. In OB40 second time and forever z-phase launch charge the value CV to HSC_Ctrl to ever same value in same cross time.

What the user sees does not need to be "myHSC".

A better solution would be to include z-phase in the hardware configuration of the HSC. In that way the HSC will be exact all the time... program interrupt and calling HSC_Ctrl will not give as accurate.

Then capture the position where the <ZERO POINT> is as measured by the HSC. So what the user sees and uses as a value is...

_{... I hope I copied the right coding ....}

#PositionNormalized :=
     DINT_TO_REAL(#RawPosition - #RawReference) / #PulsePerRev;
IF #PositionNormalized < 0 THEN
  #PositionNormalized := 1 + #PositionNormalized;
END_IF;
#PositionView := FRAC(#PositionNormalize) * 360.0;

But the above does not solve the issue on when the outputs are triggered.