5/03 with PV 550 touscreen project

I'm not terribly familiar with AB, as I primarily use the AutomationDirect line of PLCs. I think the last time I touched an AB PLC was about 7 years ago. However, I've got an upcoming project that will require the 5/03 CPU and a 550 touchscreen panelview.

Needless to say I'm a little rusty on the addressing scheme they use. Looking it over, I've got the discrete inputs/outputs figured out again, but i'm new to their analog inputs/outputs so I'll have to figure those out. Also, I've never used the PanelView touchscreens before, and that looks extremely complicated.

Can anyone point me at some texts or sites that might cover these 2 units working together? It's going to be a heating application using an RTD as an input and analog output to a steam valve. The panel will need the operator to punch in various heating temps and how long to hold them. It'll have about 12 steps and need to display which step it's on, elapsed time, and total time left. There's several other things I'll need the panel to do, but it isn't important.

I was hoping to find some example PV550 screens to use to figure out how its communicating with certain addresses, but I've come up empty.

I'm pretty good at figuring out how it all works when I see a few examples, but the trouble is I'm not finding any examples of anything I'm trying to do. Maybe I'm not using the right search terms here on in google, but I figured as a last resort I could ask here and see if anyone can nudge me in the right direction.

http://forum.mrplc.com/index.php?act=Downloads&CODE=01&cat=3

http://www.thelearningpit.com/


These might help

BrianF said:

Needless to say I'm a little rusty on the addressing scheme they use. Looking it over, I've got the discrete inputs/outputs figured out again, but i'm new to their analog inputs/outputs so I'll have to figure those out. Also, I've never used the PanelView touchscreens before, and that looks extremely complicated.

Can anyone point me at some texts or sites that might cover these 2 units working together?

Click to expand...

Actually - it depends on the style of the 550 that you use. If you use the RIO version 2711-K5A1), you'll have to look at block transfers (I think the 5/03 supports BTR/BTW). More likely though, you'll be using a different style PV550, and for most of those, you use the same processor and PV address (so it isn't too complicated after all . . .).

Check out the AB literature library and look for the PV550 documentation (Operator Interface/Graphic Terminals/Panel View Standard), and the SLC 5/03 (Programmable Controllers/Programmable Logic Conrollers/SLC 500 System) documentation (especially the Instruction Set Reference, the Addressing Manual, and the SLC 500 Modular Hardware Style User Manual).

Good luck,

Marc

When you install PanelBuilder software you can choose to install sample applications. I think those sample apps include the PanelBuilder files and SLC500 logic.

I don't believe the option is selected for a normal install so you have to make sure to select it.

OG

Thanks for the replies. Starting at the link in the first reply and a little more digging, I got it all figured out. Already created a panel file with numeric input calling the onscreen scratchpad, momentary buttons that operate PLC outputs, etc. My last hurdle now is trying to figure out how to connect an RTD to the RTD module. I think my only problem there is lack of documentation of the RTDs, so I'm not sure what bits to dump into the module to configure it properly.

Thanks for the help! I'll toss the Panelbuilder CD back in and look for the examples, but the only 2 I had found the first time were 2 casino game panel files, which weren't any help.

Brian,

I think most people use 3 wire RTD's. 2 of the wires should be the same color, 1 should be different color. On the module it may show what appears to look like a resistor but one end showing 2 leads, the 2 same color wires would go on those terminals. If you let us know what module you are using may be easier. Also most RTD's I have used are 100 ohm Platinum. The other "common" one is 1000 ohm - seems to be used more in the HVAC area.

George

The module is a 1746-NR4. There's 2 red wires and 1 white wire but they're unlabeled. Talking with the manufacturer of the RTD, I connected the red wires to RTD and RETURN and the white wire to SENSE. Supposedly it's a 100 ohm platinum 3-wire RTD. I go into the DataTable into the 0:2.0 section and drop a "1" into bit 11, which is the Channel 0 enable. I save the project and dump it to the PLC. The channel light illuminates, but then starts blinking, meaning an error of some kind. Is there a bit storage location that holds the error trap of the actual fault that I can lookup?

Could the problem be I don't have the shield wire connected (as a test I'm just running some very short twisted 3-wire set). I see no place to actually connect the shielding at the RTD so I don't know what good it would do me.

Brian,

Be sure to do THE ENTIRE CONFIGURATION!!!

Check out the manual at:

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1746-um008_-en-p.pdf#xml=http://127.0.0.1/texis/search/pdfhi.txt?query=1746-NR4&pr=literature.rockwellautomation.com&prox=page&rorder=500&rprox=750&rdfreq=0&rwfreq=0&rlead=250&sufs=1&order=r&cq=&id=42d9c5b2a

Hope this helps and good luck. It's really not so bad. Except the first time I went crazy trying to understand this same type of thing, only with thermocouples...

Brian,

The 2 Red colored wires are tied together at the tip end of the RTD. They should show a direct short if you only have a few inches of wire. Measure between the white and either one, then go to a RTD table http://www.thermometricscorp.com/plat100ohmat4.html
This will tell you the temperature. The 3 wire RTD is so that it will ignor the length of wire run. Note: this assumes that you are using 100 ohm Platinum, .00385 temp. coefficient. There are more tables on that web site.
George

That is the RTD it is (finally got the specs nailed down). 100 ohm plat, 0.00385.


As for doing the whole configuration, the default state ("0") should work in all of the bits, shouldn't it?

Input is fine with 0's, data format shouldn't matter as far as it reading something, broken input set to zero, temp units set for C, filter freq 10hz (00), channel enable set to 1, excitation set to 0 (2.0 mA), and scaling set to default (00).

The RTD module is in slot 2, so I'm messing with the bits in O:2.0. Checking the Input data monitor when it faults, I see that I:2.4 bit 13 is set. Looking at the book, that seems to be a short circuit error, if I'm reading the Input data table correctly.

EDIT: Simple user error (me). I had the RTD wired wrong after getting some misinformation from the manufacturer. Once I knew it was a short, I double checked the wiring diagram in the book and found the resistance on the return lead. I had it connected to the Sense lead. The RTD is staying alive now with no faults. Now I just have to continue reading and figure out how to pull the readings and I'll have all the info I need to write the program. Thanks for the help!

Ok, I've got most of the previous stuff figured out, but now I'm stumped by the PID block. I've read numerous threads on it, so I'm beginning to grasp it, but I still haven't gotten to the "Ah-HA!" part...

I've got the RTD module (1746-NR4) that I'm pulling in a scaled (through the module logic) value of the current degrees in F. It's currently reading a value of 84 right now in open air. It's currently 80-something degrees F here in the room, so it seems right on.

The problem is, I think I'm confusing myself with the scaling I think... and I'm not even sure I need scaling in this case for the output module.

For the PID block, the Control block is N103:0. I'm pulling in the PV using the address of the RTD input on the module directly (I:2.0). Should I be doing this? Or dumping it to an N value and scale it to some value?

I've got the CV set to N102:3. Reading some of the threads here, I thought I needed to scale the output and dump it to the output module (1746-NIO4I), which was O:4.0. I was using 6242-31208 & 3277-16384 as the min/max input/scaled.

I think I might be confused, though, since I believe the thread was bringing in a scaled value instead of a direct value like I'm doing.

I've got the Panelview figured out, and have a screen to edit the setpoint. That's dumping fine into the setpoint field. In this case I just temporarily dump the value "125" in there.

My loop update is 0.01 (just because I'm not sure what to put there yet... I'm using a SLC5/03 CPU). The other settings are left at the default. I'm not sure what to use for the Setpoint min/max. I'm confused because I think it depends on the scaling.

When I activate the PID block in the ladder, and pop up the PID setup during an online edit, I get no action going on in the CV values.
I'm not sure if I've got something funny going on with the output module, or if it's something dumb like I don't have the PID block configured properly (which is highly likely, since it's confusing me greatly).

Not sure if I'm explaining things properly, but I guess part of that might be my confusion right now.