Ken Roach

MrPLC Member
  • Content count

    2686
  • Joined

  • Last visited

Community Reputation

137 Excellent

4 Followers

About Ken Roach

  • Rank
    Propeller Head

Recent Profile Visitors

9811 profile views
  1. There is no difference between the 16K and 32K controllers in their ability to communicate via the serial port. So your problem could be in the configuration of the serial port, or with physical damage to the serial port, or with differences in the data table addresses that you are attempting to read and write.   But it's not a firmware problem.
  2. FT View Basic Error

    I don't like to directly address Inputs or Outputs;   FactoryTalk View has had some SNAFUs with the drivers, and in general I just don't like to risk the possibility that the HMI will write to something that the PLC is also trying to write to. Is your multi-state indicator configured for 2-state (which could address a Bit) or Integer state (which would have to address a whole word) ?
  3. Video Graphics Adapter (VGA) connectors are about the same size and shape but have different pins (15).    The MicroLogix 1400 has an ordinary 9-pin "DB9" RS-232 connector, which you can see is a Male (pin) connector.    The pinout is for a "Data Terminal Equipment" type port, on which Pin 2 is Receive (Rx) and Pin 3 is Transmite (Tx). This is the same pinout and style of port that you would find on a typical personal computer. The Delta HMI you posted a picture of appears to be a DOP-B07S411.    It has at least two communication ports on the back, which can be configured for RS-232 as well as for other interfaces like RS-485. The DOP Connection Guide manual I was able to find for the Delta HMI suggests that the DB9 Male plug is also a DTE style plug, where Pin 2 is Rx and Pin 3 is Tx. That means that your serial cable must be a "null modem" type that swaps Pin 2 and Pin 3.    Or, you can add a "null modem adapter" that internally swaps pins 2 and 3. There is no way to tell from a picture what type of wiring is inside an RS-232 cable.   You must either have its specification sheet or measure continuity with a meter from end-to-end.    
  4. In general, modern Ethernet systems should be allowed to use "Auto-Negotiate" to set speed and duplex.    If you have configured only the VFD to use 10 Mb/s, then the managed switch may still be set to "Auto-Negotiate". "Auto-Negotiate" is not "auto-detect".    There is a low level protocol for testing the link at 10 or 100 mb/s and at full or half duplex.    In general that's done each time the link is broken (unplugged) and re-connected. But some switches when they have an Auto-Negotiate failure (because the connected device is hard-set to 10 MB/s) will periodically attempt to re-negotiate so they can establish 100 Mb/Full Duplex. This causes drops of connections on that port, when the switch decides to do a new link negotiation cycle. So unless you have a very good reason to set the VFD to 10 Mb/s on the Ethernet port, I strongly suggest setting both the switch and the VFD to "Auto-Negotiate". A sophisticated switch like the Stratix should have some logs for you to examine, but I'm not enough of a Cisco IOS expert to tell you how.
  5. What sort of devices are the ASCII devices ?    Do they have any sort of handshaking (Xon/Xoff, or RTS/CTS) that could prevent them from transmitting at the same time ? In some applications a "code activated switch" would be appropriate.    B&B Electronics (now owned by Advantech) makes a neat device they call a "buffered smart switch" that allows you to add a prefix or even do some polling, so you could tell each port's data apart. http://www.bb-elec.com/Learning-Center/All-White-Papers/Serial/Automatic-Serial-Data-Collection.aspx  
  6. LED status on MLC1200

    Do you mean an Allen-Bradley MicroLogix 1200 controller ? In general, a flashing red Fault LED indicates a recoverable fault, often created by the user program with a math overflow or array pointer overflow, or by the diagnostic subsystem with an expansion I/O fault. Diagnostic and Troubleshooting information can be found in the MicroLogix 1200 User Manual: https://literature.rockwellautomation.com/idc/groups/literature/documents/um/1762-um001_-en-p.pdf
  7. The Net-ENI can handle up to six incoming TCP connections.    It's possible that if you are connecting to it with too many computers, you have overloaded it. I don't think the Web interface allows you to see the number of TCP connections;  I don't have a Net-ENI Series D to test on.    I do know that you can connect via Telnet to the device and send some commands to get some status data. Here's a Rockwell Knowlegebase article about how to do that (TechConnect required):  KB 27418. One common issue is that an RSLinx Classic station with an RSWho browse open will create and maintain a connection to a Net-ENI, so it's possible that in a large enterprise network that you have computers that are just running RSLinx in a background window that are taking up resources on the Net-ENI.
  8. If you're using a DF1/Ethernet interface like the 1761-NET-ENI, it's possible that there is a configuration problem with it (like the Subnet Mask or Default Gateway) or that you have exceeded its capacity to accept incoming connections. In general, both FactoryTalk Linx/RSLinx Enterprise (for FactoryTalk View) and the RSLinx Classic drivers (for RSView32) can simultaneously connect to any controller;  the memory size of the controller is not a factor. But the connection capacity or configuration of the network interface device might be an issue.
  9. ProSoft MVI46-ADMNET backup

    The MVI46-ADMNET is one of the most broadly programmable modules that ProSoft makes;  it's basically a DOS system-on-a-chip with a backplane access toolkit and an Ethernet network stack. https://www.prosoft-technology.com/Products/Rockwell-Automation-In-chassis/Platform/SLC/C-Programmable-Application-Development-Module-with-Ethernet-for-SLC The ADMNet Dev Guide includes instructions on how to interrupt the user program and get access to the filesystem via the console serial port.
  10. Comtrol looks like they've got a straightforward Web browser based configuration.    You tell it the name of tags you want it to transmit serial data into, and it does it based on the delimiter (like a CR/LF) or a timeout. DeviceMaster isn't a product I have direct personal experience with, unfortunately.
  11. MSG Error 16#0000_0311 and 16#0000_0204

    The "5370" family CompactLogix controllers support "raw socket" services, but the older CompactLogix family, including the 1769-L35E, do not. The MSG instruction on the 1769-L18ER controller points to the controller's Ethernet interface object (the 1,0 path) because that object is what handles socket creation and transmission.   If you had a ControlLogix with a 1756-EN2T or 1756-EWEB, the path would point to the 1756-EN2T module. You cannot make this connection with the 1769-L35E.    There may be another way to do it with a protocol gateway device (I would use a Red Lion DataStation) but not natively with the Ethernet port.
  12. message between L43-compactlogix and L71-Guardlogix

    That CIP Path looks OK for a message originating in a 1756-L71 ControlLogix or GuardLogix with a 1756-EN2T or other Ethernet module in Slot 1. "1,1" is "backplane, Slot 1" "2, 192.168.105.245"    is "Network port, IP address" "1,0" is the default hop to the backplane and then the CompactLogix L43 CPU If the originating controller's Ethernet module is not in Slot 1, the CIP path should be adjusted.
  13. DeviceNet devices are isolated from the PLCs, drives, and I/O block main power.     For this reason, you must provide a separate DeviceNet power supply to power the network. This can seem counter-intuitive when you are accustomed to networks like Profibus or AS-i, or when you're connecting only one Input block.   But many DeviceNet products like photoeyes or proximity sensors don't have  separate power supply, so they must receive their network power and signal from the bus cable.     And PLCs aren't always part of a DeviceNet, so we can't rely on them to be the power supplies or load up their internal power supplies (a big DeviceNet can consume several amperes).
  14. Concat Ascii to readable text

    The default STRING datatype in ControlLogix consists of a 32-bit DINT that represents the Length, and a SINT[82] array that represents the data, one character at a time. In your case it sounds like you have BCData.Data[0] that holds the Length (but it's only 8 bits), then BCData.Data[1],[2],[3],[4] that holds the letters "6 8 2 8".    The last character is shown as "$r" which is shorthand for 0x0D = 13 = Carriage Return. The easiest way to handle this would be to use a MOV instruction to move the BCData.Data[0] value to the StringTag.LEN tag.     Use the MOV because it automatically converts from SINT to DINT and it's easy to understand. Then perform a COP instruction, with the Source = BCData.Data[1] and the destination StringTag.Data[0].   Make the Length of the COPY the number of target elements (SINTs), so use StringTag.LEN as the Length.    If you don't want the carriage return on the end, subtract 1.    
  15. 1785-L40E

    Check the DIP switch settings on the backplane carefully;   they are different for PLC-5 processors vs. 1771-ASB or -ACN15 communication adapters. A solid red PROC LED generally indicates an unrecoverable hardware fault, but it can also be an empty RAM memory if there is no battery installed.    If these were not reconditioned by Rockwell, it's likely you just got damaged and untested processors.