Ken Roach

MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

139 Excellent


About Ken Roach

Recent Profile Visitors

9919 profile views
  1. The "remote" 1756-ENxT, the chassis that contains it, and the "Producing" 1756-L73 controller must all be in the I/O tree. The 1756-L73 is definitely supported by Studio 5000 v30.
  2. Studio 5000 and different PLC versions

    Take a look at what's in the contents of those "DVD images";   for better or for worse it's every support file in every language. When I download a Rockwell software product, I put the .RAR or .ISO or .ZIP files onto our big file server once I'm done with my installation;  no reason to keep them on my relatively small SSD.
  3. SLC500 Chassis

    Yes.    The very oldest Series A chassis had some MOV's under the processor slot that were notorious for getting bent and damaged, and Series B improved that design. 1746 chassis of any Series are 100% compatible with all controllers, modules, and power supplies.
  4. ML1000 MSG Instruction

    OK, that's a different set of conditions and devices. Is your communications over serial, or over TCP/IP ? What revision of firmware is the CompactLogix 1769-L32E running ?  What protocol are you using;  DF1 full duplex, or half-duplex, or half-duplex Radio-Modem ? Telemetry can be hard to troubleshoot, and the tools and techniques aren't as commonplace as ordinary automation electronics.  I used to make my living hooking up protocol analyzers and hunting for the correlation between communication failures and weather/temperature/vibration/traffic/time.
  5. ML1000 MSG Instruction

    What is your master controller ?   When you say "some of the messages do get through", do you mean that of the three to that site two of them always get through, or some of each of the three sometimes get through ?    Does your system do any statistical collection on error rates or counts ? Have any changes been made to the system lately ?   Do your radios have any independent diagnostics ? In general, Error code 0x37 really does mean "timeout";   the local controller sent a query to the remote controller, and never got a reply. This is different from the sort of error that you would get if the data table was unavailable, or there was a corrupted value like a CRC error.   With a MicroLogix 1000, the data tables are fixed in size and type, so the risk of mis-addressing is mostly limited to typos at the master side.  
  6. Yes, that is definitely possible.    FactoryTalk View's diagnostic log will generally indicate the data table addresses it cannot read or write.
  7. 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.
  8. 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) ?
  9. 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.    
  10. 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.
  11. 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.  
  12. 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:
  13. 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.
  14. 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.
  15. 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. The ADMNet Dev Guide includes instructions on how to interrupt the user program and get access to the filesystem via the console serial port.