MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

6 Neutral

1 Follower

About dmargineau

  • Rank

Profile Information

  • Country United States
  1. Good morning! I am wondering if you have ever had to exchange data between a Micro 850 and an L18? I am having problems getting them to talk using the MSG. Do you have any info on these CIP modules? and how to configure them?

  2. memory overlap problem

    It is an issue caused by the using of the same tag (name-> memory location) within more than one ACTION or TRANSITION. Refer to 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
  4. Display Visibility

    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.
  5. 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.
  6. 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. 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.
  7. 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.
  8. 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
  9. 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:
  10. FAULT with Micrologix 1000

    Please post your application...someone will need to take a look at might not have the proper CPU type or you are using software not compatible with the controller at hand.
  11. Have you tried to delete the Harmony files?
  12. You will find a couple of examples at*&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
  13. 22-Comm-E

    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.
  14. 22-Comm-E

    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. or Chapter 3 of
  15. Encoder for use with 1769-HSC

    I'd use a differential encoder (digital) in order to avoid "electrical" issues. Dynapar HA25 or HR25 series Allen-Bradley 845H Series This is your HSC module's User Manual: