Ken Roach

MrPLC Member
  • Content count

    2526
  • Joined

  • Last visited

Community Reputation

96 Excellent

1 Follower

About Ken Roach

  • Rank
    Propeller Head

Recent Profile Visitors

6367 profile views
  1. 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.
  2. 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.  
  3. 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.    
  4. 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.
  5. 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.
  6. 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 ?  
  7. 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

  8. 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.
  9. 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.
  10. Controllogix and Ramsey Micro-Tech 9101

    Do you have experience with Wireshark, and/or the ability to connect a "mirror" port on an Ethernet switch to capture Ethernet traffic ? The ControlLogix and the slave device are actually negotiating the data connection size, but only the "wrong size" error is shown to the user. 
  11. AB PLC 1400, RS LOGIX 500 WITH ABB ACS 850

    I can't think of an easy way to do that.    The MicroLogix 1400 controller has no Profibus DP scanner or master module available.   It's a MicroLogix, meant to control only I/O devices that are physically connected to it, not networked ones. Ideally, you'll connect the VFDs to the controller with digital I/O for start/stop/jog and with an analog channel for speed reference.
  12. Davii, While the general error code is the same, that's a different network, a different device, and very likely a different problem. What type of marquee module is it ?     Does it have a well-known interface module (like HMS, or Hilscher) ?   Is this a new installation or one that's been working for a while ?  
  13. That encoder says it's software-selectable for TTL or HTL output.   The 1734-VHSC24 is built for 24V encoder signals, so you want the High Threshold Logic (HTL) setting.   You'll want to book up both A and A- so that the module can detect the differential voltage between those two terminals.
  14. micrologix1100 explict message for power flex 525

    Please show the Multi-Hop tab, and compare it to the other message. While I realize that A-B and various integrators have illustrated how to do this sort of control with a MicroLogix 1100 controller, I still strongly recommend against it.    The MicroLogix does not and will never really do I/O control over Ethernet.  
  15. RS Linx Installation Issue

    The 1747-PIC/AIC+ driver will not work in Windows 7, Windows 8, Windows 8.1, or Windows 10. For this reason, it is not available in the drop-down list of drivers. If you manage to install a version of RSLinx Classic that is old enough that it doesn't recognize the modern Windows and remove that driver from the list, it does not mean that the driver is supported.   It still won't work. If you want to connect to a DH485 network, you need a 1747-UIC.