dmargineau

It is an issue caused by the using of the same tag (name-> memory location) within more than one ACTION or TRANSITION. Refer to https://rockwellautomation.custhelp.com/app/answers/detail/a_id/45745 The reason is probably related to the RSL5K FBD editor Order of Execution Rules; if "duplicate" names are encountered, the processor will not be able to "decide" which one of them should be executed first hence not being able to "resolve the logic loop". If you have a TechConnect contract, refer to https://rockwellautomation.custhelp.com/app/answers/detail/a_id/50324/related/1

http://en.wikipedia.org/wiki/Voltage_divider http://en.wikipedia.org/wiki/Potentiometer

Welcome to the Forum! Within your FTVS application, right-click on an empty area of the respective Display and choose Display Properties...; choose the Size (in pixels),give it a Number and decide which way it's going to show up (Replacing or On-Top of the previous display); move over to the Display Properties interface Behavior Tab and you will find the "placeholders" for the display's Startup and Shutdown macros. Within the Project Tree Logic and Control folder, create two macros containing the tags and relating expressions required for the Startup and Shutdown of the newly configured display and then, point the Display Properties/Behavior configurator to the configured macros. Don't forget to add Display Navigation buttons and to Save when done.

Use the Configuration Mode/Application Settings -File Menu (Copy Applications) from Internal Storage to External Storage (present USB media). The only way you could create a different revision Runtime (matching the FTV Machine Edition Station running on the Machine revision!) is by using the FactoryTalk View Studo ME software.

Is it a local application or it is distributed? If it is local, you will need FactoryTalk View Machine Edition Station. You could transfer the Runtime application via USB media, however, the existing Runtime application might not be compatible with the newer terminal firmware. if you want to retrieve and eventually Restore/Archive/Backup the application file you will need FactoryTalk View Studio ME. http://www.rockwellautomation.com/rockwellsoftware/performance/view/orderinginfo.html If it is a distributed application, your customer's FactoryTalk View SE system is "serving" the application file hence there is no need for a "terminal" backup.

The bad news is that you will need RSLogix 5000 Rev.19 to connect to the CPU.... The good ones: once connected to the CPU using RSL5K Rev.19.xy, you should be able to "downgrade" the controller firmware to Rev.17 using the ControlFlash utility and the Firmware package included with RSL5K Rev.17. Install RSL5K Rev.19.xy concurrently to Rev.17; on Logix Class platforms, user software major revisions must match the controller major firmware revisions.

It is an .EDS (Electronic Data Sheet) issue. Probably your copy of RSLinx is older than the CPU's "age". You could freely download RSLinx Lite (I'd suggest at least Rev. 2.59 for a 32-bit OS or Rev. 3.60 for a 64-bit one) at http://compatibility.rockwellautomation.com/Pages/MultiProductDownload.aspx?Keyword=Free&crumb=112

Your best bet if intending to have all the listed software running within one "machine" is Virtual; VMware Workstation is the recommended platform. I'd suggest WinXP Pro SP3 32-bit as the Guest OS, mainly because the older RSL5K revisions. In order to run Rockwell Automation software on a 64-bit OS you will have to install and run only the latest available revisions (if available for 64-bit OSs!). Refer to: https://rockwellautomation.custhelp.com/app/answers/detail/a_id/42682/related/1

Please post your application...someone will need to take a look at it...you might not have the proper CPU type or you are using software not compatible with the controller at hand.

Have you tried to delete the Harmony files? https://rockwellautomation.custhelp.com/app/answers/detail/a_id/48241

You will find a couple of examples at http://search.rockwellautomation.com/search?q=Micro800+ASCII&filter=0&num=20&getfields=*&btnG=Search&client=samplecode&output=xml_no_dtd&proxystylesheet=samplecode&ulang=en&sort=date%3AD%3AL%3Ad1&entqrm=2&oe=UTF-8&ie=UTF-8&ud=1&exclude_apps=1&site=sample_code

Get yourself a 1203-USB ($380.00 List) USB-to-DPI/DSI/SCANport Converter; it comes with a cable kit and will allow you to connect to the PF40 DSI communications port. http://literature.rockwellautomation.com/idc/groups/literature/documents/um/drives-um001_-en-p.pdf

Modifying the IP Address of any device while "connected" to it via the very protocol which's settings you are editing is never a good idea. Forget BOOTP if the 22-COMM-E had a configured static IP Address; most likely it has been disabled at the time of the original configuration. What drive are we talking about? You will need to connect to the drive via different communications means (DriveExplorer/Executive or CCW via DF1 USB-to-DSI) and modify the comms module settings or, if there is an installed HIM module, use this peripheral device to enter the proper 22-COMM-E module settings. http://literature.rockwellautomation.com/idc/groups/literature/documents/um/drives-um001_-en-p.pdf or Chapter 3 of http://literature.rockwellautomation.com/idc/groups/literature/documents/um/22comm-um004_-en-p.pdf

I'd use a differential encoder (digital) in order to avoid "electrical" issues. Dynapar HA25 or HR25 series http://www.dynapar.com/Products_and_Solutions/Series_HA25_Shafted_Encoder/ Allen-Bradley 845H Series http://ab.rockwellautomation.com/Motion-Control/High-Performance-Incremental-Optical-Encoder#/tab5 This is your HSC module's User Manual: http://literature.rockwellautomation.com/idc/groups/literature/documents/in/1769-in030_-en-p.pdf

Presuming that the ML1500 is an LRP Series B or C, you could use the 1747-UIC only if the CPU's Comm. Port 0 is set to DH485; unfortunately the Default setting is DF1 and chances are it is still set there; in order to modify the Channel 0 port settings you will need to connect to the CPU Serially(RS232) using Channel 1 and, obviously, an USB-to-Serial adapter. http://literature.rockwellautomation.com/idc/groups/literature/documents/in/1747-in063_-en-p.pdf

Usually device specific AB/RA literature manuals come in two "flavors", The User Manual and the Reference Manual. User Manuals address the installation, setup and troubleshooting while the Reference Manuals explain in detail the actual functionality of the devices.

Page 272 of http://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1763-rm001_-en-p.pdf

What is the expected RPM range to be "detected"?

Forget RSLogix 5000...Your ML1400 is not a Logix class CPU... Your approach (using RSLogix 500) is the proper way to retrieve the ML 1400 CPU Status. The 0x08 Fault Code is caused by an ASCII Write instruction which cannot be performed due to an already ongoing ASCII command. Find all the ASCII commands within your application file, disable their scan, redownload to the controller in order to eliminate the Hard Fault condition and then re-examine the way the ASCII commands are implemented; there should be only one active ASCII Read/Write command at any time; trigger the next ASCII command based on the completion of the previous one.

I believe this is the only way you could accomplish your goal, especially on a forty years old platform. I really don't see why would you consider this inefficient or "out-of-style"; this is what CPUs are built for afterall....

Either use the PowerFlex Datalinks feature (expanding the implicit I/O communications buffer with the additional needed parameters) or explicit messaging (MSG) via application code. Depending of the installed EtherNet/IP communications interface (20-COMM-E, 20-755-ENETR or embedded Ethernet port) refer to : http://literature.rockwellautomation.com/idc/groups/literature/documents/um/20comm-um010_-en-p.pdf http://literature.rockwellautomation.com/idc/groups/literature/documents/at/750com-at001_-en-p.pdf http://literature.rockwellautomation.com/idc/groups/literature/documents/um/750com-um008_-en-p.pdf Search for "Datalinks" and "Explicit Messaging"

There are many ways of "rigging" the VFD in order to operate encoderless, however, this should never be attempted after the crane has been fully comissioned and especially when a load is present! There are specifically designed holding brakes or holding brakes built-in provisions for safely lowering the load in case of emergency or electrical malfunctions.

http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1747-um655_-en-p.pdf http://literature.rockwellautomation.com/idc/groups/literature/documents/gr/dnet-gr001_-en-e.pdf

Yes, you will need RSLogix 500 (at least the Standard Edition) for the SLC CPU application file (http://www.rockwellautomation.com/rockwellsoftware/design/rslogix500/orderinginfo.html) and RSNetWorx for Devicenet for configuring the 1747-SDN Scanlist and the network's slave devices' configuration(http://www.rockwellautomation.com/rockwellsoftware/design/rsnetworx/orderinginfo.html).

Chuck, You will need RSLogix 500 for the MicroLogix CPUs- http://www.rockwellautomation.com/rockwellsoftware/design/rslogix500/orderinginfo.html If you are sure you will never use any SLC CPUs and depending of your budget, you could get away with RSLogix 500 Starter Edition, however, if you wish to get most of the available features, I would recommend the Standard Edition. For the CompactLogix CPUs carrying Firmware Revision 20 or lower you will need RSLogix 5000- http://www.rockwellautomation.com/rockwellsoftware/design/rslogix5000/orderinginfo.html Again, if you are sure you will never acquire any ControlLogix CPUs you could get away with the Mini Edition, however, I would recommend the Lite Edition in order to explore most of the available features of the CompactLogix family. For CompactLogix CPUs Firmware Revision 21 (the latest) you will need Studio 5000 Logix Designer- http://www.rockwellautomation.com/rockwellsoftware/design/studio5000/orderinginfo.html; use the same logic as for the RSL5K when it comes to Studio 5000 editions. For the PanelView Plus terminals you will need FactoryTalk View Studio for Machine Edition (ME)- http://www.rockwellautomation.com/rockwellsoftware/performance/view/orderinginfo.html RSLinx Classic (Lite) is pre-packaged with all the above and needs to be installed only once per machine. I would first install RSLogix 5000/Studio 5000, then RSLogix 500 and at the very end FTVS ME. Install the FactoryTalk Services Platform, FactoryTalk Activation Services and RSLinx Classic only once when first prompted.