New in working with H0-CTRIO2

[Evilbeard]

I've been tasked with an upgrade on a piece of equipment. I'm beginning my project and I had a few questions.

Basically, I'm removing all the old pushbuttons, switches, and knobs on the machine and replacing it with a 12" HMI, a DL06, and a H0-CTRIO2. I currently have the H0-CTRIO2 configured with a quadrature encoder on Inputs 1 and 2. I don't need the outputs on the CTRIO. The information I need from the CTRIO is speed, footage of material ran, and a totalizer count. This machine is a rewinder, and will be turning larger rolls of material into smaller rolls. I set up the scaled units as the footage. Is there a way to also make the CTRIO calculate the speed for me, or will I have to do that with the ladder logic of my program? Would it be easier to setup the CTRIO as a rate, have it calculate the speed, and then extrapolate the position (footage) with math in the ladder logic using the raw data (pulses)?

When the machine runs to its programmed setpoint the operator will reset the footage (and therefore the CTRIO). I'm assuming there is no way to maintain a "totalizer" without having to do some moving/adding in the ladder logic?

Thanks in advance for helping a DirectLogic and CTRIO newbie.

[BobO]

First...if I were doing any significant CTRIO2 work, I would try hard to talk whoever is buying the hardware into using an H2-DM1E and H2-CTRIO2. The time saved will cover the additional cost of the hardware. Yeah...it's that much easier.

But either way, lemme answer your questions:

Is there a way to also make the CTRIO calculate the speed for me, or will I have to do that with the ladder logic of my program?

Yes. Rate Scale or Interval Scale either one will covert from edges to speed. For faster things use a Counter with a Rate Scale, for slower things use a Timer and an Interval Scale.

Would it be easier to setup the CTRIO as a rate, have it calculate the speed, and then extrapolate the position (footage) with math in the ladder logic using the raw data (pulses)?

You can wire to more than one input and have the counter do both...or...for Counters (vs Timers) the Rate can be calculated, and the raw counts are returned in a different register.

I'm assuming there is no way to maintain a "totalizer" without having to do some moving/adding in the ladder logic?

Use a second counter channel. There are up to four.

[Evilbeard]

But either way, lemme answer your questions:

Use a second counter channel. There are up to four.

Using the H0-CTRIO2 and a quadrature counter uses 3 inputs of 1 channel right? (A, B slaves to A, C becomes Reset, and then I can make D an edge timer to calculate speed). Are you suggesting I just use one set of pulses from the encoder or am I setting up the CTRIO improperly?

[BobO]

Duh...H0...single channel.

If you don't need the bidirectional ability of the encoder, then yes, you could run two functions from the same source. But a counter can do rate out and still give you raw counts off one function.

[Evilbeard]

This was more in reference to the totalizer. I think my best course of action with this will probably be to calculate rate, use the raw data to calculate footage using math, and then use the second counter to be a totalizer.

Thanks for the help, but don't run away, I'm sure I'll need more in the future. I've mainly worked with AB and RSLogix, and done some work with AD's Click line. The language is still a bit new.

[BobO]

If you don't need bidirectional, then yes, rate on A and totalizer on B.

Pretty sure I'll still be close by.

[BobO]

And I'll toss in a plug for the new platform we're developing...it can do everything you want, and much more, for less than the cost of the DL06 and CTRIO. Doesn't help you now, but would slam dunk this.

[Evilbeard]

And I'll toss in a plug for the new platform we're developing...it can do everything you want, and much more, for less than the cost of the DL06 and CTRIO. Doesn't help you now, but would slam dunk this.

I will definitely look into that in the future, but my superiors kinda dumped this on me, so I'm working with what I have.

[BobO]

Not available yet. I just mention because this app would be really easy on it. Always good when your design choices are confirmed by real world apps.