JRoss

As far as I know, those are the only three options.

Unless you're talking a really slow pulse train, you will either need to get a transistor base unit, or an FX3U-1PG special function module. Only the first three outputs of a transistor base unit will work with the high-speed commands like PLSY, DRVI, and DRVA. The FX3U-1PG uses standard FROM/TO commands to set up and execute the motion. Using the built-in commands with the base unit is much easier, so I would highly recommend replacing the base unit.

Take a look at the help file. When you select the type and temp units on the configuration tab of the module properties, it scales to the published range of the thermocouple, and the value you get is the temperature. The 0-7000 you see is grayed out and doesn't apply unless you choose "custom range" instead of Celsius or Farenheit. So if you have the thermocouple in ice water, you should see 32F or 0C depending on the units. If you don't, then there is a problem with the thermocouple, the card, or the wiring. Either that or you have a different type than you think.

Yes, configure your card as Joe E states, then you'll get the actual temp reading in your input data. Then you can just use comparison intructions (LES, GRT, LEQ, GEQ) for off-on control of your heaters.

Not without knowing what you are trying to accomplish. What is the process? Give as much detail as you are legally allowed!

Well... An RTD and a thermocouple are both temperature sensors. Choosing one versus the other is a factor of the temperature range, accuracy, and the characteristics of what you are monitoring. But both give you the same piece of information. So you can change the type, but the PLC won't do anything differently. Next, an SCP isn't a control algorithm, it's a scaling instruction. It's for taking one linear range of numbers (like 4-20mA) and converting to another (like 0-1000 degrees). It sounds like you want a PID instruction.

Once you install the AOI, you can use it in the ladder logic as if it were a regular instruction. In ladder, add an instruction and type in the name of the AOI, in this case it should be "SCP". You'll see the block appear with 7 arguments. The first is for a tag with a custom data type to match the AOI. I usually type in a name like "DeviceID_SCP", then right-click and create a tag on the spot. You shouldn't need to do anything in the create tag dialog except click OK. Then back in the ladder, you can enter the tags or constants for the rest of the arguments, just like in RS Logix 500.

I got the AOI from a colleague, but I suspect he got it from Rockwell. I've tweaked it a little, but the guts are essentially the same. I modified it so that I don't have to assign separate tags for the min/max parameters and added an "In Range" bit. I'm also planning to add a clamping feature in a week or so.

Maybe try to download it to a PLC, then create a new project without labels and upload the PLC.

There isn't a built-in scaling instruction in Logix 5000. You can use the CPT (compute) function and put the computation in that way. I use an SCP add-on instruction (AOI) that I got from a colleague years ago and have modified slightly. It mimics the operation of the SCP in Logix 500 and is much easier to use. It's basically the CPT function hidden inside an AOI with a couple of other features, but I like it. PM me your email address and I'll send it to you.

I think the only difference is that in jog mode you don't have control over the speed using digital inputs or analog input. I would use speed control mode in your application for that reason.

GT Works 3 (of which GT Designer is the main piece) is for programming HMIs. GX Works is for programming PLCs. The two packages are complementary, but serve completely different purposes.

That's excellent, glad to hear it.

<rant> Why do we have to do this? Why can't Mitsubishi either (a) Put the GS Installer in an obvious location and publish big notices that it needs to be installed or (b) simply add it to the installer script so nobody has to do anything? This seems like an idiotic oversight. I went through this the first time I tried to use a GS21, and have gotten a call from every one of my customers that gets GT Works 3 and tries to open a program file I've sent them. There's nothing in the software to alert you, no inserts in the HMI box, no notices on the website, and nothing in the manuals. Is tech support so bored they need people to call about things like this? </rant>

Just to be pedantic, and perhaps avoid some future confusion... The Q3xx racks are main racks, and require a power supply and at least one CPU. The Q6xx racks (as you have in the first setup) are powered extension racks, and require a power supply (not a CPU). The Q5xx racks (your final selection) are un-powered extension racks, and don't require a power supply. In any configuration, you need to make sure that you have enough 5V backplane power to power the modules. The tool makes this easy, of course, though you can always calculate it using the specs for each module. You had enough power left for your additional modules, so you were fine to use an unpowered extension rack. If that had not been the case, you could have used a powered extension rack (with a power supply) to add more power into the system. CPUs can only go on the main racks. You can have up to four, but they must be all the way to the left on the rack, with no other modules between them. Incidentally, the third character in the part number indicates the number of I/O slots, and does not include the power supply slot or the first CPU slot. For example: Q35B - 1 power supply slot, 1 CPU slot, 5 module slots Q65B - 1 power supply slot, 5 module slots Q55B - 5 modules slots