Ken Roach

MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

124 Excellent


About Ken Roach

  • Rank
    Propeller Head

Recent Profile Visitors

8169 profile views
  1. RS232(DB9)

    Most small logic controllers have a serial port of some kind.    Many modern ones have USB and Ethernet as well. DB9 is a common form factor for RS-232 ports, but I have seen them implemented in DIN-8 (round) connectors (like on the MicroLogix), and in RJ45 and RJ11 modular connectors, and in mini-USB style connectors.
  2. Panel view plu 600

    When the terminal powers up, it checks to be sure that none of the cells on the touchscreen are ON.    If they are, it assumes the touchscreen is damaged and this error message appears. Try cleaning the screen with rubbing alcohol and examining it for damage. Otherwise, your only option is to replace it or have it repaired by Rockwell Automation.
  3. AB PV 800 compatible with Micrologix 1100?

    The PanelView 800 is specifically intended to work with Micro 800 and MicroLogix controllers. This Knowledgebase document (1023307, access level Everyone) shows that you designate the protocol as Ethernet | MicroLogix/ENI and then designate the type of MicroLogix in the Controller Settings entry.
  4. FTView SE (Local Station) - Offline .ACD Connection

    Be sure that there is a valid Shortcut pointed to a controller object, and then you should be able to also designate a *.ACD file for offline browsing.
  5. Interlaced MOV Instruction

    MOV, COP, and CPS are all completed before the ladder routine (or structured text routine) moves on to the next branch or next rung. The issue that I suspect you're working on is that COP is an array instruction, and the operating system moves data in 32-bit chunks from the source to the destination.    While the RLL or ST routine execution does not move on to the next instruction, rung, branch, or line until the COP is complete, the OS can interrupt the copying of data to service another higher-priority feature. Usually the problem appears when that interrupt is an I/O update.    The Input data might be written over in the middle of the COP, or the Output data might be grabbed and sent out to the network subsystem before all the data was copied into it. That's why the Copy Synchronous (CPS) instruction was created (it wasn't part of the original ControlLogix OS).   It locks the source and destination from being affected by interrupts until all the data gets copied.    Doing that lock and unlock process in memory takes a few microseconds, so I only use CPS when I'm handling I/O data. Because MOV doesn't operate on arrays or on data types that are bigger than 32 bits, it doesn't have the same vulnerability to interrupts as COP does.
  6. conveyor speed

    While the MicroLogix timers are not extremely accurate (because they depend on the scan rate for evaluation), the MicroLogix does have a Selectable Timed Interrupt (STI) feature that triggers off the controller's internal clock pulse and executes a subroutine at that rate.  You can set the rate in 1 ms increments.    Look in the "Function Files" section of the controller organizer and in the User Manual for details about how the STI feature works. The RA Knowledgebase includes a document (19445, Access Level = TechConnect) that describes using the STI and a High-Speed Counter to simply count the accumulated pulses between executions of the STI and calculate a rate in Hz or kHz, from which you could calculate your conveyor speed. The only HSC-related instruction you really have to use is the Reset Accumulated Value (RAC).    Run it once at the first scan of the processor in your normal PLC program, and then run it at the end of the Program File that is jumped to by the STI interrupt.     That way the Accumulated Value in HSC:0.ACC will always be just the number of counts accumulated during the STI period (set in HSC:0.SPM).
  7. 22-Com-E Card Mess

    I am very surprised that the module accepted that address ! I think the only way to reset the 22-COMM-E is going to be to install it in a drive and use a 22-HIM keypad module, or plug in with a 1203-USB and DriveTools/CCW to access the menus and return it to defaults. There's no other return-to-defaults mechanism for the 22-COMM-E like a jumper or switch.    Its big brother (the 20-COMM-E) has rotary switches you can set to put it on the subnet, but the 22-COMM-E does not. Your Rockwell distributor ought to have these sorts of devices available to help you recover the module.
  8. Micrologix 1100

    Check the ribbon cable connections very carefully to be sure you haven't bent a pin or torn a cable. In general, you just enter the expansion modules in the I/O configuration and the controller recognizes them.    You might have a bad expansion port on the controller itself.     Talk to your distributor to see if you can test your I/O modules with one of their demos.
  9. Rswho not showing

    Those Microsoft updates were an emergency patch for the Intel processor-related "Spectre" and "Meltdown" security vulnerabilities.    They affected more than RSLinx;  I am carefully working through problems with CoDeSys that are probably related. RA has a discussion of the issues here: And information on the symptoms driven by those updates here:   I carefully managed my "I told you so" discussions with my colleagues who consider my insistence on running all automation software under VMWare to be unnecessary;  my virtual machines don't update automatically and almost never connect to the Internet, and can be rolled back easily (when I remember to make snapshots).
  10. Rockwell CompactLogix PLC

    This sounds like a damaged 1768-L45 controller or damaged 1769 backplane connector, or a conflict between the 1769-SDN firmware and the rest of the components. You absolutely should be able to "see" the 1769 I/O modules when you browse the backplane with RSLinx Classic, and your screenshot suggests that you do.   But shortly thereafter the communications with those modules fails and you get a red X over the modules. I would delete all the modules from the RSWho browse and try to browse again, just to establish if you have basic connectivity with the 1769-SDN removed from the assembly. The firmware compatibility is described in the Rockwell Knowledgebase as article 462381 (Access Level: Everyone) Because you have a 1768-L45 controller you will be limited to v20 firmware, which means you should not try to upgrade the 1769-SDN over the backplane.    Borrow a 1784-U2DN to do this upgrade over the DeviceNet network port, or have your local Rockwell distributor or sales office help you upgrade the 1769-SDN if it is not already at version 4.004.

    That is a broad request.     What do you want the encoder to do in your automation system ? The MicroLogix 1400 has High Speed Counter features that can be used with encoders for some automation tasks. Start with the User Manual and the Reference Manual for the MicroLogix 1400. There are also some technotes about wiring, configuration, and applications of encoders with the MicroLogix and its High-Speed Counters in the Rockwell Automation Knowledgebase.
  12. Messages between CompactLogix and SLC 5/03

    Is the SLC-5/03 Channel 0 serial port available ? The Allen-Bradley 1761-NET-ENI module allowed this kind of connection;  the CompactLogix could send a message to the Net-ENI as though it was an SLC-5/05, and the device would translate that to RS-232/DF1 protocol and get the reply from the SLC/PLC/MicroLogix attached to the serial port side. It's slower than a native Ethernet port, but it works. A-B stopped making the Net-ENI last year, but a company called Real Time Automation in Wisconsin makes a very good replacement device: I would even say that the RTA-ENI is better than the original because it has some extra features (like the web interface) and more capacity (10 TCP connections instead of 4).   They were so intent on drop-in replacement that you can use the old A-B configuration software if you want.  
  13. HAI SIR



  14. Redundancy

    Rockwell has a limited-scope "hot backup" technique using CompactLogix and some special inter-controller communication and inhibit/un-inhibit logic to switch ownership of field I/O between controllers.    It is not a fully featured Redundancy system like ControlLogix Redundancy. It is ONLY available by direct agreement and supervision between a Rockwell field sales office and a customer.      Nobody should be giving it to an unauthorized customer or to a customer who is unwilling or unable to work with their local Rockwell Automation field office.
  15. If the Configuration screen is access-protected, the only way to overcome that is to download new firmware or to download an application that does not have the "Configuration Screen Secured" box checked in the application configuration.