Ken Roach

MrPLC Member
  • Content count

    2532
  • Joined

  • Last visited

Community Reputation

98 Excellent

2 Followers

About Ken Roach

  • Rank
    Propeller Head

Recent Profile Visitors

6575 profile views
  1. 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.
  2. RSLogix Micro License

    Yes, you may only use the Internet-based "re-host" a limited number of times per year.    Because "re-host" opens up the possibility of unauthorized duplication of license files, Rockwell restricts its use. If you need to run your software on multiple computers frequently, buy a USB dongle and use that as your Host ID.    For RSLogix 500 Micro, I don't even know if they offer concurrent server-based licensing.
  3. [Newbie] Using AdvancedHMI for rslogix 5000 emulate

    RSLogix 5000 Emulate does not communicate over TCP/IP like true controllers do.    It can only communicate with the RSLinx Classic and RSLinx Enterprise communication drivers via its virtual backplane. If you have RSLinx Classic with a licensed activation that provides OPC DA Server functionality, you may be able to use the OPC DA Client driver in AdvancedHMI.
  4. Point I/O compared to Flex I/O

    Joe, I just took over a machine project where there are symmetrical North and South sides, with identical I/O count and signal types. The North side is where the CompactLogix is installed, so they used an L36 and local Compact I/O because they needed a PLC that could handle 4 axes of CIP motion. The South side got POINT I/O to save a few bucks and a few centimeters over a 1769-AENTR and Compact I/O. So I've got Input and Output handling routines that include little stories about the differences in resolution, scaling, and data packing between the two platforms.   I've edited out all my lines about "For reasons that are lost to antiquity...."
  5. Panelview 1000 (2711 T10C9

    You never needed freshly-killed chickens for PanelView or PanelMate;  it's about the bird as food, not about the death rite.    As long as it's warm and you're hungry but don't get to eat because you're fixing the machine, the mojo is suitable.  The DH485 PanelViews that were equipped with Printer serial ports can use those ports ONLY for printing (or have them disabled).   Those ports don't support upload and download.   This includes the 2711-xxxx3 and 2711-xxxx9 models. The 1747-UIC and a straight-through RS-232 cable should do the job if the UIC's switch is set to RS-232.   Use the RSLinx driver;  I don't think the direct driver (it dates from the mid-90's) will work with the UIC. If the terminal has v3 or v4 firmware (virtually all of the 10" ones will) it should support ATA Flash memory cards, including a CompactFlash in a Type II carrier, as long as it's under 2 GB and formatted for FAT16 and not NTFS or FAT32.      That would be my choice for loading a *.PVA application file.
  6. Arduino to Compactlogix communications

    I'm not aware of an EtherNet/IP adapter library for Arduino.    The TCP/IP stack is a huge amount of work for the Arduino all by itself and there are really only some basic libraries that can be used with Ethernet shields. Since you're using an L33ER controller, which does support raw Ethernet sockets, you could implement something simple without the connections and objects and error checking and tagnames of EtherNet/IP, just using ASCII. Which Arduino platform and Ethernet shield are you using ? Another approach you might take is the GridConnect / LanTronix "XPort" device, which implements an EtherNet/IP to Modbus RTU serial slave bridge inside the footprint of an RJ45 jack.   http://gridconnect.com/industrial-protocols/ethernet-ip/ethernet-ip-interface.html   Modbus/RTU is reasonable straightforward on an Arduino.
  7. L3 Serial Communication

    :rolleyes: Don't go throwing a handful of acronyms out and ask how to implement a system.    If you've got a manufacturing execution system of any kind and it doesn't have drivers to communicate directly with Allen-Bradley controllers, I don't think it's much of a software system. It's practically professional malpractice to use ASCII serial when high-speed Ethernet communications is available.
  8. L3 Serial Communication

    Can you expand on what you're talking about ? "L3" might refer to the 1769-L3x family of controllers, either the older -L32E and -L35E or the modern L30, L33, L36.    The older ones had RS-232 serial ports, while the modern ones do not. And, of course, please provide some details on what you mean about "WMS";   are you referring to warehouse management software, or something else ?     Warehouse management is obviously a huge topic and there are dozens of different vendors and technologies and methods for communicating.  
  9. 1769-ASCII

    They're just listed as "Device Control" bytes in some ASCII charts (like the one above). XON is hexadecimal 0x11 = decimal 17. XOFF is hexadecimal 0x13 = decimal 19.    
  10. Message from 1761 net-eni to 1756 enbt

    Welcome to the Forum !     Ideally, set up a new thread for this new topic;   the existing thread involves different devices and different commands, and it's nearly eight years old. I'm not sure you'll be able to send an ASCII string from a Micro 820 to an SLC-5/03 via a Net-ENI;  that's an unusual requirement.   Go ahead and create a new thread, and point to that example code in the Micro 820.
  11. 1769-ASCII

    The description is a little difficult to read, I agree. XON/XOFF is basically a software based handshaking scheme, rather than using the RTS/CTS or DSR/DTR handshaking signal pins.   Instead of asserting a "Clear to Send" pin, the printer sends a periodic XON (0x11) byte, then sends an XOFF (0x13) byte to say "I've received my data and am not going to listen again for a bit while I do my printing thing". I agree that the printer should be sending XON bytes every half-second after it turns on, then it will send and XOFF byte once it's received a command and is ready to process it. But I don't think the 1769-ASCII supports automatic XON and XOFF handshaking.   There's no mention of it in the user manual. How do you have the Start Delimiter and Stop Delimiter set up for receiving data on the 1769-ASCII ? You might try setting up the 1769-ASCII so that XOFF is the Start delimiter and XON is the Stop delimiter. That's logically backwards, but what it would do is give you an increment on the incoming data Record ID each time that XON arrived, which would tell you that the printer is ready to receive a print command. I don't know how the 1769-ASCII would behave if it gets End Delimiter values without getting Start delimiter values first.   You should be able to experiment to find out.
  12. Prosoft PLX31-EIP-MBTCP Configuration with Control Logix

    Welcome to the Forum !   Modbus is a very common industrial protocol but because it's been around for many years (since the late 1970's) there are many different ways to implement it.   You really do need to learn the basics of the terminology, and www.modbus.org is a good place to start. Your screenshot in green shows what looks like a configuration for a Modbus/TCP device in a Yokogawa CS3000 DCS system. What is the second part a screenshot of ? Will your DCS be using this Prosoft device to communicate with your ControlLogix ?     Will the same Prosoft device also be used to allow the ControlLogix to communicate with smaller devices like power meters ?  
  13. 1747-KE to 1761-NET-ENI.

    Can I do that, or do I have to use RS232 port (DF1) on my SLC 5/04?  I think this will be my cheap answer getting the PLC accessible from our Ethernet/IP network.  The RS232 port is already in use by a barcode scanner, using ASCII read/write instructions.  I would just assume not touch any code I don't have to, so that would let me connect over the KE card instead.  If necessary, I could move the scanner to the KE card and use the PLC port for the 1761-NET-ENI...I think.

    Just a word of validation will suffice...I am out of my element with this old stuff!

    1. herkaderka

      herkaderka

      By Ken Roach on 6 April, 2001 - 3:52 pm

      I'll say about Lynn Linse what somebody once said about George Stephanopalous; "If IQ were Fahrenheit you could boil water with the guy". I'm eager to test out a 1747-KE with the 1761-NET-ENI; I'm not certain if those two devices together would effectively bridge Ethernet to DH485. It's moot in this case because there are no spare slots. The SLC-5/03 does not pass through data from DF1 to DH485. The SLC-5/04 and SLC-5/05 have this function when Channel 0 is in DF1 or DH485 mode (and the function is enabled in the status file), but the SLC-5/03 does not. If one of these controllers was replaced with a 1747-L531 processor, then Channel 0 of that processor could connect through a 1761-NET-AIC isolator to the DH485, and the other controllers (and probably the PanelView, this depends on PanelBuilder) would be accessible via Ethernet and ENet/DH485 passthrough function. >>We have two AB slc 503 and 4 panelviews connected togheter on a rs 485 >>network using dh-485. There are not empty slots on the plc and they don't >>have a ethernet connector. We want to connect [the DH485] to our ethernet network. Ken Roach Tech Specialist A-B Seattle

  14. PLC5/15 Changes its address on power-up

    Smart, McNasty !   My guess is that there's condensation or corrosion on the first DIP switch, causing a short that makes the binary number go up by 1 when the PLC-5 restarts.   The apparent time-of-shutdown difference might have to do with the temperature of the enclosure.  If the machine owner can't shell out for PLC-5 software, they should at least pay a local integrator who does have the tools to come in and do some disaster-recovery backup.   They can then run the control system to failure if they want.
  15. Controllogix and Ramsey Micro-Tech 9101

    First go ahead and figure out if your switch supports port mirroring;  most managed switches do.    It's always a little disappointing when third parties put weak support for EtherNet/IP into their product.    Documenting and troubleshooting that stuff used to be most of my job, and the differences between company attitudes was striking, whether enthusiasm (HMS Fieldbus), apathy (Atlas-Copco), or conflict (Emerson). If the size is the only problem, we can probably sniff out the issue.