[RTD Sensoor]

When you configure an RTD, the linked MI contains the actual temperature value, scaled to tenths of a degree.  eg value 254=25.4degrees.

 

There is no need for additional linearisation.  Just make sure you use the correct coefficient value for your RTD.

Thanks Simon

 

That was helpful, i tried that and partially worked, because when temperature goes to higher values ti gets good readings, when it goes to lower values than it stuck in 85 c 

 

Good readings at 120 c and above bad readings at 85 and below in between values is ok.

I have a manometer connected in the same fistula so i can compare the readings from PLC and manometer.

 

PS the temperature in manometer goes to 55 c while in plc is stuck on 85 c

 

 

Thanks

[RTD Sensoor]

Hi

In a project that I'm working on i have a pressure sensor and and temperature (RTD) sensor connected, i went through the linearization process and for the pressure sensor everything went as a charm with the 14bit. But I'm having some serious difficulties over RTD sensor witch is a pain in the a.s. I can't get it linearized, i tried with 10, 12, 14 bit linearization with the linearization function block and no way i can get the right readings.

 

I'm not sure if it is possible to get the readings directly from the RTD assigns MI or there is no other way but linearization.

 

 

 

thanks in advance 

 

[Subroutine Problem]

My experience is that a coil remains in the state it was last in when the ladder rung stops being executed. This makes sense since the coil had no logic executed to turn it off (if it was last on, for example). This will also crop up when a subroutine is conditionally executed.

 

Any state change, whether bit, integer, or what-have-you, must be actively executed in order to occur - either off or on.

Thanks for the reply Flex727, since now I'm using drum to activate different MB which than i condition different outputs and for this project suits very well. I m not using the subroutines, but it would be interesting to fully understand how subroutines really work, and what you wrote makes sense. 

 

Thanks again for the reply. 

[Subroutine Problem]

You could just use the drum for the outputs. It is much easier and keeps the program clean. If you want different orders or times just make as many drums as you want. I also like to use one net for one logic. It makes it easier to find problems.

Thank TozoM8 for the advice, that is what i did. Now i m using drum to activate different MB whitch than i condition different outputs and it works fine. It s first time that im using Drum sequencer FB, and i think that is a very powerfull tool, i m sure in future i will use it a lot.

[Subroutine Problem]

Hello 

I used a Drum Sequencer to jump through subroutines (to energize in a  particular order), but the problem is that when the Drum energizes the certain subroutine, the outputs are energized this is the good part but when i jump to the next step meaning the next subroutine is energized and the old subroutine is de energized, power should flows only in the new subroutine and de energize the old outputs of the old subroutine, problem is that even thou it jumps to new subroutine and energizes the outputs of new subroutine it does not de energize the old subroutine outputs. 

So in the next subroutine the old and the new subroutine outputs are active, what i need to do is to stop the old subroutine outputs while I'm in new subroutine.

 

According to help file, if the subroutine is not energized the outputs should no be energized, right!!, in my case even thou the power in subroutine is not energized any more ( i can see it from the online mode) but still the output remain energized.

 

What is that I'm doing wrong. I will attach the project too, so that you guys can have a better idea of what is going on.

 

PS you can see in the drum config FB, step 1 lasts 5 sec doing nothing, step 2 activates subroutine 1 containing two outputs , step three should stop this two output in subroutine 1  and step four activates subroutine 2 activating one output...

 

 

 

Any help is much appreciated, i really have a tight deadline i need to rep it up quickly 

 

thank in advance.

Exampe for the forum.vlp

[Go to Step in Drum Sequencer]

There is a function block, Next Step, that when triggered will progress to the next step. This can be used when a step has a 0 timer and will not automatically go to the next step.

 

You can also use the function block, Go To Step (Index) which will reference an MI value for a selected drum configuration. The value within that MI is the step you will go to. So for example if you are referencing MI 0 in the Go To Step FB and the value stored in that operand is 5, then when triggered the drum will immediately jump to step 5.

 

This information can also be found in the VisiLogic help files in the contents section under Ladder\ FBs Library\ Drum.

I got it right thanks Alexander. the think was that i did not assign operand in FB Drum Config.

[Go to Step in Drum Sequencer]

Does anyone have any idea

[Go to Step in Drum Sequencer]

What model of PLC do you use?

What model of PLC do you use?

PLC that im using for my project is V350 -35-TRA 22

[Go to Step in Drum Sequencer]

Hello

 

In FB Go to Step how do i define in which step to go, I know that it's got to do with FB drum config.

Can I use a go to step for every step in my FB drum Config.

It's confusing the way to determine how to go to a particular step, example from the 1 st step (time is set to 0:0) than use fb go to 5 th step than go to 2nd step etc...

 

Thanks in advance.