ScottC

I don't know for sure, personally, but check the Compatibility Matrix in tech note 58963. It shows that the 1770-KFD is supported on Win7 Pro and Win2008 64-bit OSs for RSLinx Classic versions 3.51 and above.

I remember having the same problem when I first used FTV Studio. I fixed it by resizing one of the panes in the Communication Setup window, but I can't remember which one. I believe I had to drag the horizontal bar above the Browse button down. If that's not it, try maximizing the Communication Setup window. If that doesn't work, post a screen shot of the window and maybe it will trigger my memory.

I would look at the CPT instruction in Rung 51 of the PDF file you attached earlier. Since the destination register is an integer, all intermediate steps in the CPT are limited to values ranging from -32768 to 32767. So, if the sum of N7:90 + N7:91 ... + N7:104 is ever greater than 32767, you will get a math overflow error.

Check TConnolly's totalizer solution in post #9 of topic 109702.

Have you seen the CompactLogix 5370 L1 series of processors? They sound like what you're describing.

The node address switches are factory set to 999 and DHCP (BootP) is enabled. You can reset to the factory defaults by setting the thumbwheel switches to 888 and cycling power to the adapter. Set the thumbwheel switches back to 999 (or anything except 000-255 or 888) and cycle power again. You should now see DHCP (BootP) requests on the network. Don't forget to disable DHCP (BootP) or else the address will be lost on the next power cycle.

For practical purposes, TTL is a count, not milliseconds. When you ping a device, it sets the TTL of the reply packet to some integer value, like 64, 128, or 255. As the reply packet makes its way back to the requester, the TTL value is decremented by one each time it passes through a router. If the TTL reaches 0, the packet dies. This countdown prevents packets from floating around the Internet indefinitely. The host device that is being pinged determines what the starting TTL will be. Apparently, the Eaton touchscreen starts at 128 and the ControlLogix starts at 64, and neither has to pass through a router to reach the requesting PC. The different TTLs between the two devices has nothing to do with their speeds and will not affect the network performance.

Look at TechNote 35690 (The difference between EVMOVE.EXE and EVMOVEW.EXE) in the RA Knowledgebase and see if it helps.

I've done something similar using macros. First, create a memory tag in RSView32 to hold a pending value, say Pending\Tag1. Create a display, i.e. EditPopUp, with an input field for the data to be edited, a "Save and Close" button, and a "Cancel and Close" button. For the "Save and Close" button, make the action "SaveEdit" and for the "Cancel and Close" button, make the action "AbortMe". Create two macros like the following and call them OpenEdit and SaveEdit. OpenEdit Pending\Tag1 = RealTag Display EditPopUp SaveEdit RealTag = Pending\Tag1 AbortMe Now, create your "Edit" button on one of your displays. For the "Edit" button's action, enter OpenEdit. The pop-up window will open with a copy of the data you want to edit. After you edit it, you can click the "Save and Close" button to move the edited data to the Real tag or click the "Cancel and Close" button to keep the old data.

Take a look at this datasheet. It may be what you're looking for. Good luck finding one, though. Digi-Key shows them as a 2000 minimum order with 0 in stock and Arrow Electronics shows 0 in stock. They are the only two big players that lists them. You may be able to cross-reference to another part number or brand.

9324-RL0100ENE: RSLogix 500 Starter Offline/Online Programming 9324-RL0100ENF: RSLogix 500 Starter Offline/Online Programming (Concurrent) My understanding is that the ENE version is for a single license that you load on a single PC or dongle that can be moved to different PCs. With the ENF version, you load the license on a network drive and "check it out" on a PC as needed. It sounds like the 9324-RL0100ENE package and dongle are what you need. If you have knowledgebase access, check answer 21640 - RSLogix 5/500 Comparison Matrix. It looks like the starter package will do what you want. According to the comparison matrix, all SLC and MicroLogix controllers are supported by the starter package. I think you will lose some functionality like the ability to make online edits, cross-referencing, and diagnostics that the standard package has. I'm not an expert, but I hope this info helps.

I did a forum search for "sammy" and I think your initial interpretation of his reply was correct. He seems to have issues.

Use a 10-turn pot.

I'm not familiar with the 1762 modules, but have you considered using the A-B Bulletin 1492 wiring system. They don't list cables for the 1762 modules specifically, but the 1492-CABLE***N3 may work. It is intended for the 1769-IQ32T, but it seems to use the same connector and have the same pinout as the 1762-IQ32T.

In the second picture, take a closer look at the processor types you have highlighted. All the SLC modular processor catalog numbers are formatted as 1747-L5xy. The x denotes the processor type, i.e. 1 = SLC5/01, 4 = SLC5/04, 5 = SLC5/05. The y denotes the memory size, i.e. 1 = 16K, 2 = 32K, 3 = 64K, for the 5/04s and 5/05s. So, since you have a 1747-L553, it has 64K of memory.

The firmware upgrade is not available for download. You have to order it - catalog number 1747-DU501. Scott

Is VESSEL_alarm_value a new tag? If so, I think the Tag Server has to be restarted before it will go on-scan. I guess the easiest way to do that is to close the project and restart it. The expression you have should work.

Are you starting the derived tags file that contains VESSEL_alarm_value? There needs to be a command DerivedOn <filename> somewhere that executes when the project starts.

Am I missing something? Aren't the 1762-OW8 (NO) and OX6I (NO-NC Type C) just dry contact modules that will work with AC or DC?

It looks like it depends on the exact model number of the PanelView. Check chapter 12 of the PanelView Standard Operator Terminals User Manual available at http://literature.rockwellautomation.com/i...um014_-en-p.pdf.

Active X controls are not "portable" with the project. They are installed on the PC the project is running on. Which Active X are you trying to use?

The NT4 only reads thermocouple and mV signals. If you want to use it with PID loops, the PIDs are set up in your ladder program. The BTM reads thermocouples and does the PID loops within the module, not in ladder logic. It also does autotuning, which is not the same as autocalibration. Programming for the BTM is very advanced - definitely not recommended for someone just starting out. As you mentioned, there are some good documents and programming examples available from AB. Scott

Mickey, You can configure any channel of the NT4 to read the CJC temperature. You don't physically connect the CJC to the input terminals. It is done internally. When configured to read the CJC, the physical terminals are ignored for that channel. It's just a way to read the ambient temperature at the module. Usually it is done dynamically in the ladder program (switching back and forth between the CJC and physical input) so that you don't "waste" an input. Scott

If you have Ch. 3 configured for CJC and Eng. Units 1, then it should be reading from 0 to 850 in 0.1 degree C increments. There is no need to scale the value.

Device type (I/O) tags are counted towards the limit. Checking the tag count may depend on the revision level. For revision 7.40, open the tag database. Select Help>Tag Statistics... from the menu bar. Under Tag Limits you will find the actual and limit values for I/O tags.