Ken Roach

MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

105 Excellent


About Ken Roach

  • Rank
    Propeller Head

Recent Profile Visitors

7085 profile views
  1. Flex I/O

    EDIT:  I'm not going to lecture you on this.   I'm just irritated that you seem to blame A-B for a basic features/functions issue that is very widely understood. MicroLogix are built to be standalone small machine controllers.   They're the little brothers to the SLC-500 family and they've been using the RSLogix 500 software since 1995. It's well known that the MicroLogix 1100 and 1400 controllers with built-in Ethernet use that network for messaging and for online monitoring and editing, but not for I/O. The only "remote I/O" for MicroLogix family controllers is the ability to add a 1769-SDN DeviceNet scanner to the MicroLogix 1500.   While it was a neat little controller in its time, the MicroLogix 1500 (and to a degree, DeviceNet networking) have largely been superceded by higher-capacity, more highly-featured controllers and devices. If you have a system that needs Ethernet I/O, the minimum controller you need is a CompactLogix.     If you haven't used CompactLogix or ControlLogix controllers before, you're in for a toolset (Studio 5000 Logix Designer, the Mini version at least) and a bit of a learning curve for the tag-based architecture. Get a CompactLogix selection guide and look at what each controller will do.   The little 1769-L16 and -L18 controllers can run a limited number of EtherNet/IP nodes, like your Flex I/O.  
  2. 1734-VHSC Rate, and Counts

    I use a Periodic Task, with a program that uses a GSV to grab the CST timestamp from the controller. I don't even have to rely on the Periodic Task's accuracy:  because I copy the CST timestamp in microseconds, I have a very accurate value for the time elapsed since I grabbed the last number of counts.    If you have elapsed time and increment in counts, then you can calculate a counts/time value.
  3. Auto Download FactoryTalk mer File

    It's really pretty easy, but the file paths change with the version of Windows CE and with the external device you're using. This is the Knowledgebase article you want: If it's a modern PV+6 or PV+7, this is the syntax for a USB drive.   Be sure the drive is formatted for FAT16.   @echo offecho  Copying MER File...copy "\USB Storage\Rockwell Software\RSViewME\Runtime\<name_of_the_MER_file>" "\application data\rockwell software\rsviewme\Runtime\<name_of_the_MER_file>"echo  The process is complete.exit  
  4. Replacing compactLogix analog cards

    In general, Compact I/O modules have been widely compatible with regard to firmware.    Some government-regulated industries require that you use precisely the same firmware revisions in your application, and Compact I/O modules are (in general ) not field upgradeable.     Examine the "Electronic keying" tab in Studio 5000 to be sure that your new module will work when it goes into the installation. All of the configuration for scaling and range and signal type is done in software, automatically by the CompactLogix CPU. One physical setting you will want to check is the 1769-OF8C has an internal/external power selector switch on the circuit board.   Be sure that is set to match the module you replace.
  5. MonitoringServoMotorTemperature

    Two excellent Knowledgebase articles (TechConnect required for both) regarding the various heatsink and embedded temperature sensors in various Kinetix motors and drives: The Motion Axis parameters should have the motor stator temperature as an available feedback parameter. Your motors are also equipped with a high-resolution absolute encoder.   The second Knowledgebase article I linked to tells you how to use a message instruction to get the value being read by the temperature sensor embedded in that encoder. I like your idea.    A short trend object that shows the temperature would be even more useful to show the operator if the motor has been running hot all the time and just eased over the threshold, or if it was heating up quickly because of an abnormal condition.  
  6. GPS time synchronisation with AB PLC

    The usual way to synchronize controllers to a networked time clock is to use the Clock Update Tool utility on an ordinary Windows workstation that gets its time from a domain server or from an Internet source.    The Clock Update Tool utility is a free download or is included in every Studio 5000 installation.
  7. GPS time synchronisation with AB PLC

    There's no easy way to synch with a time server directly from the controller.   There is not built-in Network Time Protocol (NTP) client in the controller, nor is there a good one in the PV+. If you have a serial GPS, you could write code to parse the incoming string using the controller's serial port. If you want very high accuracy position and time, you can use a 1756 module from HIPROM in South Africa.
  8. PLC hardware

    Switch the Run/Prog toggle switch all the way to RUN mode and secure the cabinet.   When the keyswitch is in RUN mode (not Remote Run), the controller will not accept a download or edit. There is no way to prevent a new program from being downloaded to a controller if someone has physical access to the controller.
  9. RsLogix 5000 Motion with third party

    Logix integrated motion is only native to Rockwell products.    They haven't licensed the technology and protocols for CIP motion over Ethernet to third parties (that I know about). It's theoretically possible to run third party drives over SERCOS with Rockwell, but it's a very, very involved process.    As noted, some A-B drives can run third party motors if the physical and electrical characteristics of the motors are well understood and a "motor database" is created.   That's how the linear motors from Anorad worked when RA first bought them, and I've worked with a tiny handful of specialty motors in this way. Drives and motors that don't integrate with the Motion instruction set are easier to integrate with ControlLogix, because they behave like an ordinary I/O module.    An example that I use frequently are JVL integrated servo motors.    They just look like an I/O block and I fill in the target position, velocity, and acceleration and turn on the GO bit.  
  10. Copy data from/to a 5069 digital module

    Wow, this is a great question !    I too have not used the 5069 IO platform yet, but creating a project in Logix Designer shows that the discrete modules have a Data and a Packed Data format, and that the points are all individual BOOL datatypes, with fault and Uncertain BOOLs mixed in there as well. I would approach this by using a subroutine (or eventuall an AOI) to use a CPS (Copy Synchronous) instruction to copy the whole 68-byte datatype into an INT array and then parse out the bits I'm interested in.  It might take some experimentation to figure out which bits are which;  overlays inside Module-defined datatypes aren't always obvious.
  11. AB Ethernet Port Problem.

    Your screenshot of RSLinx shows all the DataMan and PV+ and CompactLogix devices coming up in the RSLinx browse, and your screenshot of RSLogix 5000 shows all the I/O objects in their normal state with no faults. Explain what the symptoms are of your controller not being able to communicate "with any device".    It looks like it's communicating fine.
  12. What is the destination device, exactly ? These error messages are consistent with you having inserted only a communications module and not a CPU, or some other similar issue where the actual device associated with the shortcut isn't a controller.
  13. CompactLogix slot numbers

    The slot numbering for Compact I/O modules always goes left-to-right, no matter if you're using a R/L or R/R expansion cable. 1769-L32E Slot 0 1769-IQ16 Slot 1 1769-IQ16 Slot 2 1769-IQ16 Slot 3 1769-PA4  (no slot number) 1769-IQ16 Slot 4 1769-OW16 Slot 5 1769-OW16 Slot 6 1769-OW16 Slot 7 1769-Expansion cable (no slot number) 1769-IF8  Slot 8 1769-IF8  Slot 9 1769-IF8  Slot 10 1769-PA4 (no slot number) 1769-OF8C Slot 11 1769-OF8C Slot 12
  14. Saving Tag Values to SD card of AB processors

    It's not as simple as checking a "retentive to SD" box for the tag and having it auto-loaded when you reboot. But you can write logic that saves tag data to the removable media, and reads it back out. This logic has a rocky history from back in v16 with CompactFlash cards (about 10 years ago) but it's pretty solid now, especially because modern controllers use SD cards, which have data integrity features built in. There's a Application Profile manual for this feature:
  15. Will MVM work for this

    Yes, it is ! Always add a good rung comment when you're doing Masked Moves to explain what they're doing and why.