ParaffinPower

Hello Herewith my comments: 1. I don't know what the ADD instruction on the ENO is supposed to be doing 2.The DistanceBetweenPulses is a REAL, so needs to be entered in the format +1.0 3. The Pulse and Running parameters need to be something other than Always Off 4. The other addresses are all 0; the inputs need populating, the outputs are optional (but the result will appear in one, or both, of them 5. Bare in mind, this was an example rolling average FB; it won't produce wotsits/hour 6. The 'Tweak' parameter was intended to give a bit of calibration; +1.0 yields no calibration will be applied, +1.1 will give 10% over. Hope this helps point you in the right direction. Pp

The oneshot fb is nested; don't worry about it. The idea of a fb is to encapsulate some code so you would rarely (never) address its internal memory. Anything you need from, or presenting to the outside world would be presented as an input or output parameter. This is the case on the example fb provided. Clear as mud? Pp

Invoking the FB in your ladder will allow you to attach the 'real-world' addresses to the FB via the Input and Output parameters. Have you got the FB in your ladder yet? It's fairly self-evident once you have. Pp

Hello The FB maintains a stack of the 10 most recent timings internally, and averages them each time a new entry is made. There's no need to do anything externally. Pp

Attachments here need to be zipped. Use winzip (or similar) and extract the .cxf file. This can be imported into a cxp project by right clicking on the function block section of the project tree, and then select 'from file'. This will make the fb available for invocation in your standard ladder. Pp

Winzip. Think it's native in windows (speculation). If not, there must be freeware available Pp

Hello again This uses the plc's internal clock (ie if fairly oblivious to scan time), and updates the rate each clock pulse. The DistanceBetweenPulses input parameter was so it would give you m/min or inches/min or whatever you want. If you just want pulses/min then make this +1.0 A oneshot FB is nested. It pulls this in automatically, so don't worry about that. Pp RateCalculation.zip

Fifo = first in first out. Each minute, move the latest minute's data in, and the oldest data out. This gives a rolling total, rather than just counting how many pulses there have been in the last hour. There are ladder instructions for stack control, but I'd roll my own in an ST FB. Pp

Hello denise01 The PRV2 instruction only relates to plc's with built-in high speed IO (CP1, CJ1MCPU2x) so is not appropriate if you have a CPU11. If you want to display rotations per hour, then I'd count pulses in a minute and perform a rolling average of these over 60 minutes FIFO-ing the array of readings. The problems of inaccuracy due to timings won't be relevant if you're averaging an hour's worth of pulses I don't think. If you want rpm, then scan time becomes an issue, or should I say or striking a balance between precision, stability and responsiveness of the readout. I have an FB that looks at the plc's internal clock which does a pretty good job of this. However, it's on another pc. Next time I'm on that, I can post it, if it'd be useful. Pp

Can you use the drive programming to copy the analog input to P100, then use explicit messaging to read from there. Alternatively, try the polled I/o flexible format then you don't need the explicit messaging. Pp

Hello If you use a timer within your ST, then you can do the maths in there too. Much easier than fannying aobut with maths in ladder imho. TIMHX(StartCondition,MyTimer,TimerValue)

Automatic

No, you don't need to do anything to the screen. If you've not connected before then you will need to install the driver.

I think Jay wanted to say that you need CX-Designer (part of CX-One). With this, you'll be able to upload the application (USB is easiest and fastest) then download this to the new screen. Contact your local Omron office to get CX-One. Pp

I agree; you'd need two pt100's, and two separate loops on the tc101. To use Geir's idea, you'd need a standard pt100 input card ( not a tc101 controller) and write the temperature contol bit yourself. The PID instruction works beautifully. Pp

Hello guys I'm working on a project at the minute where the customer values a slick recipe system above all else. The NS recipes have alway been lacking IMHO. However, I'd like to use its recipe 'base', ie writing to the CF. I'd really like a tailored recipe entry screen, rather than the datablock table it provides. I want to dynamically show/hide entry fields depending on other entries, eg if temperature loop 1 is not enabled, I don't want to show the setpoint for loop 1. I can pretty much do everything external from the table (with Command buttons)except enter the recipe name. Has anyone rolled their own recipe handling that I could have a look at ? Cheers, Pp

I was

Hi FLTL converts directly from ASCII to REAL. Works for scientific notation, too. Pp

Hello I'd check each of the addresses used on screen 29 to start with. Cx-Designer can display addresses to make this easier... Pp

Yep, you'll need to upgrade to open that. From memory, v2.1 to the current version (3.4) isn't covered by the autoupdate, and you'll need to buy CX-One V4 Pp

A stab in the dark, but was his version created in a later version of CX-D than you're using to try and open it? Pp

Thanks, fellas As I'm using CP1H, and I need the recipes on a CF, I'm obliged to use the NS. James - you mentioned saving data to CF (from not within the recipe environment?). Can't find this posted on here anywhere. Don't suppose you have a link? thanks again. Pp

Hello I don't have any documents, but the process is pretty straightforward, providing Cognex have provided a valid eds. If you post your confif, and the eds, I'l lhave a look. Pp

NT Link is best. Pp

In Europe, this servo*R88D-GT..." is G-series. I guess it's G3 over there? I've just found reference to it in the G-series ML2 manual (very similar) and it's just described as "the load ratio as a percentage of the rated load" Yours is cruising at 25%