Using High Speed inputs

[Garyhlucas]

I just upgraded a plastic extrusion line using a BRX36. I got rid of the Fennor M-Trim controlling the puller speed, the timers that controlled the location of slits and slicing and cutoff, and the end switch on the drop table.  Everything runs off an encoder on the puller now and the length, slice location and length, and slit location length location and quantity are all perfect now. They stay that way too as you change length or line speed.  Start up time is greatly reduced and shortly we will reduce the lengths to closer to finsihed length and reduce scrap.

I had a few issues using the high speed counters with the quad encoder, mostly a lack of experience.  I used one counter scaled for speed which runs constantly.  I used another for length which I reset at every cut.  Then I had a problem making slits where the slitter was farther away from the cutoff than the first slit.  I resolved that using the 3rd counter which resets at an offset from the length counter.  It works but I am wondering if there is a simpler way to do this?

I also had a problem getting the program to see the length which I realized was because the counter rate was much higher than the scan time of the program, so it missed when using equal.  I wound up adding a small offset value to the length value then used > length < than offset value to trigger the cutoff, slits, and slices.  Am I missing a better way to do this?

Very pleased with Do-More to do this.  Three more to do, one is almost built , and the last two getting ready to assemble.

[ADC Product Engineer]

Gary, take a look at the AXSCRIPT command.  There are a couple of ways to trigger on matches along with ladder commands such as go to stage.

[Garyhlucas]

Thanks I will take a look at that.  I was thinking maybe their were some special catch bits or words available that run off scan for stuff like this.

[BobO]

Thanks I will take a look at that.  I was thinking maybe their were some special catch bits or words available that run off scan for stuff like this.

Not sure what you are triggering, but preset tables allow you to fire outputs within 1us. You can also do interrupt match registers, and then do immediate outputs. Both are outside the scan.