Ken Roach

MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

94 Excellent

1 Follower

About Ken Roach

  • Rank
    Propeller Head

Recent Profile Visitors

6241 profile views
  1. 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.
  2. 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 ?  
  3. 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.
  4. 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.  
  5. 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.
  6. micrologix1100 explict message for power flex 525

    What are the exact addresses and formats for the message ? The PowerFlex 525 contains quite a few CIP objects and emulates some PCCC registers (SLC-500/MicroLogix style data tables). If you requested the value of a parameter or object that doesn't exist, error code e6 is what you would get.  
  7. RS Linx Installation Issue

    The old 1747-PIC/AIC+ driver is very limited in its ability to run on any operating system newer than Windows XP SP2.    It shouldn't even be available when you install on Windows 7 or Windows 10, and was removed from some earlier versions of RSLinx for this very reason. The only supported modern way to connect to DH485 networks is the 1747-UIC, a USB to DH485 converter. Ideally, you will install the current version of RSLinx Classic, or at least one of the most recent ones that is compatible with your operating system.   Version 2.51 is at least ten years out of date and it's foolish to install it on Windows 8, the least stable and supported of modern Microsoft operating systems. If you aren't going to install RSLinx Classic version 3.90, at least install the last of the 2.x revisions, which was 2.59.02.    
  8. Are those two green lights just the Module Status and Network Status up at the top ?   Those confirm that your IO connection and configuration are all OK. But you should see "flickering" on the Input A and Input B LED when you spin the encoder.   If not, then there's something wrong with your wiring. Can you describe the encoder make and model and how it's connected to the VHSC24 ?     In general the VHSC24 gives you an update on its counts every RPI.    The really fast reactions of the module are on its onboard outputs, when they're set to turn on and off within a count window or at a count threshold. How are you using the VHSC24 ?   It is for position detection, or velocity measurement, or something else ?  
  9. Connecting FactoryTalk VS to Emulated PLC

    With the RSLogix emulators this is difficult, because they don't emulate Ethernet comms to outside devices. The only way I know of to do this is to set up RSLinx Classic on the host PC as an OPC Server, and configure FactoryTalk View Studio to communicate with RSLinx Classic's OPC Topic instead of the RSLinx Enterprise Shortcut.    You need to add RSLinx Classic to your FactoryTalk project to get it available as a server. Because the programs are on different computers, you need RSLinx Classic to be a "Remote OPC Server", which I think requires the "Gateway" license.   If you have the RA Toolkit, then your RSLinx OPC should activate as Gateway and make this feature available.    
  10. Isolation and intrusion prevention are a really excellent reason for doing this.   Thanks for posting that !
  11. You've got the right basic idea.    Data is written to the MVI module internal "database" by the .WriteData tags, and read out of it by the .ReadData tags. I find it helpful to draw myself a simply diagram of the flat-file "database" inside the MVI module.   It's really just one big data table and you have to be clear about which section of the table is being used for which purpose (writing or reading). Because you are using two Allen-Bradley products, can I ask why you are using Modbus/TCP instead of one of the built-in Allen-Bradley protocols ?  
  12. Implement IEC 61499 Micrologix 1500

    It's just the wrong platform for it.   The MicroLogix 1500 runs ONLY a cyclic relay ladder logic language that is mostly compliant with IEC 6-1131. For an IEC61499 event-driven function block system, you're looking for something else meant for distributed control in your industry.
  13. 1747-SDN Firmware update

    I found RA Knowledgebase Article ID # 461211 that confirms that 1747-SDN firmware is no longer on the download server and must be obtained from a distributor or RA office. I agree that for a Series B module, you want version 6.002.   It's very stable and hasn't been touched for maybe eight years. I would be very surprised if you could update the firmware in the 1747-SDN by passing through the module itself;  it's sort of like trying to tickle yourself.   I always did it with a 1770-KFD and a hot cup of coffee that I carried someplace else while I let the upgrade run.
  14. Strictly speaking, Modbus/TCP is a peer to peer protocol, so it's a "Unit Identifier", not a "Modbus Slave address".   And yet the MVI56-MNET module makes no mention of the proper name, calling them all "Modbus Slaves". Here's an excellent technical discussion of Modbus/TCP from a different vendor, Real Time Automation.   John Rinaldi is super-smart: When your MVI module is acting as a "Modbus Slave", it's really being a "Modbus/TCP Server". When your MVI module is acting as a "Modbus Master", it's really being a "Modbus/TCP Client". In general, I think the MVI56 and MVI46 modules behave as Unit Identifier 1 at their IP address, so you'll always make the module you're reading from or writing to "Modbus Slave 1" in the Command List.

    MicroLogix 1500 or CompactLogix controller ? The RSLogix 500 and Studio 5000 syntax for hex characters is a little different, I think.  RSLogix 500 liked to use old conventions for some control characters. In the Studio 5000 string browser, a dollar sign is done by doubling, i.e.   $$   means a single dollar sign character. If you're concatenating or creating strings right in the SINT[x] elements, just use 16#24 to designate ASCII character 24, the dollar sign. I'd first take a bit of a step back and be sure that the mass flow controller is really looking for hex characters, or if it is looking for ASCII representations of hex characters. As pure hex, $02$21$AD is three bytes.    But as an ASCII representation of hex characters, it's nine bytes.