Ken Roach

MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

114 Excellent


About Ken Roach

  • Rank
    Propeller Head

Recent Profile Visitors

7742 profile views
  1. Rockwell 1756-IRT8I

    Rockwell usually forces the input data value to its maximum data type value, and sets the Over-Range bit to indicate a disconnected thermocouple. For example if a thermocouple comes disconnected from my 1734-IT2I, the Over-Range bit is set and the value goes to 32767 instead of my typical 1234 = 123.4 degrees F. I don't know if that's the case with that specific module, but it's typical.
  2. SLC 5/04 Watchdog error

    Ganpat, this  thread is seven years old and addresses a fault on a different model of controller with a different cause and solution. Please create a new thread to address your faulted MicroLogix 1200 controller. In general, "single digit" fault codes are caused by faulty hardware or by electrical noise.    When I've seen Fault 02h on MicroLogix 1200 controllers, the first place I look is for a heavy green ground wire.
  3. Devicenet error 80

    Bit 0 of Word 0 of the Output data image for the 1769-SDN slot needs to be set to "1" to put the 1769-SDN into Run mode itself.   Virtually all DeviceNet systems I've seen have an unconditional output run that sets that bit.   Some others will use a powerup timer, or a set of machine or network status conditions, to keep the DeviceNet idle until it's ready to run. I've seen a few where the programmer just poked a 1 into the data table and never otherwise addressed the issue. In general, nothing should zero out that bit if no changes have actually been made to the machine.    Get into the program and see if anything addresses that bit.
  4. Studio 5000 Logix Designer

    Neat challenge ! Can you post the EDS file itself ?    Are you using EZ-EDS, or some other verifier ? Have you tried this with any other version of Studio 5000 other than v29 ? My guess, and it's only a guess, is that A-B left themselves some looser rules when the VID=1 that allow some older or not-quite-compliant EDS files to work correctly because Studio 5000 can internally compensate for them.  But I'm reasonably confident there is a syntactic fix.
  5. RSLogix 5000 version 20

    Your username and mention of turbomachinery for which you don't have the tools suggests that you might have some Solar Turbines gear. I very strongly recommend that you go through Solar Turbines service division for the maintenance and parts for your system.   Solar Turbines has used quite a lot of hardware and firmware custom-made by Rockwell for their systems, and I never assume that ordinary Rockwell components are appropriate for use in an ST system. If not, then go ahead and use RSLogix 5000 v20.04 and whatever hardware you have. However, if you have only the old floppy-disk based "EVRSI" activation, it will not activate RSLogix 5000 v20.x software.   Version 19 was the last version that supported that old activation. If you have the modern FactoryTalk Activaiton, it will work with the same activation as your older versions.
  6. Communication between CompactLogix and RSlinx

    Older A-B platforms ran with that sort of "comms, then I/O, then logic" cycle but the modern ControlLogix/CompactLogix operating system is interrupt based and you can get situations like you describe where a communications channel can update a tag in between logic instructions or rungs/lines. It's not "configurable", in the way that you could check a box for "async/sync tag comms". When I have logic that can be affected by the change in an HMI -written tag during the process, I copy the HMI tag to an internal tag at the beginning of the routine (or before calling the routine, if it's a subroutine or AOI).   // HMI_CMD - tag that is set in HMI // CMD - tag that is used in logic CMD := HMI_CMD; if (CMD == 1) then DO_SOME_LOGIC1 ..... .... if (CMD == 2) then DO_SOME_LOGIC2 ...... ...... ..... CMD = 0 HMI_CMD := CMD;    
  7. New to PowerFlex VFD's (40).Quick question.

    The footnote isn't super clear, but in this context, "CF" means "Clear (active) Fault".    Asserting a STOP will also clear any active Fault conditions if the Stop Mode is set to a value of 0,1,2,3, or 8.
  8. How to read/write drive parameters?

    Thanks for posting that PDF !   I think we're going to be able to decode this from known values, Enigma-style. Another key phrase appears at the bottom of the DeviceNet and EtherNet/IP sections: When we look at the parameter table, there's a column that gives those values.   I think the manual is using some confusing nomenclaure, so we'll be careful with it. As an example, Parameter P1-07 is the Motor Rated Voltage.   The default value is 230, for 230 volts.   It's an unsigned 16-bit Integer value. The network object values for that parameter are listed as "A2h, 107, X". We can agree that A2 (hexadecimal) is the CIP Class value.   That's consistent both with the manual description and with general CIP protocol practice;  Class A2(hex) is commonly used as the Vendor Defined Object. An ordinary CIP protocol object description would list the Class, the Instance, and the Attribute numbers.     The manual claims to be listing the "Instance Attribute, Name, and Value (X)", which is confusing.    So let's try what makes sense from a CIP perspective.     Create a MSG instruction that you've proven works (like with the C/I/A = 1/1/1 example I gave), then set it up for Class A2 (hex), instance 107 (decimal) and Attribute 1.    Observe carefully when you type in those values;  the MSG instruction generally accepts hex for the Class, decimal for the Instance, and hex for the Attribute.   I'm reasonably confident that the Parameter number = the Instance number, but I'm less confident about the Attribute.    Some objects just put the data value in Attribute 1, while others put other data first, like the data type or the data size or the read/write setting. Because we know what value we expect for that Parameter (230 = 230V) then we can poke around an determine which Attribute is appropriate.  
  9. How to read/write drive parameters?

    How did you figure out the messaging data objects for Profinet ?   Or is it just EtherNet/IP they didn't provide documentation for ? I found a brief "user manual" for the "ETHNET-CC" EtherNet/IP module but it doesn't provide details about parameter access.   It does claim that they have a CIP Parameter Object (which often applies only to the objects contained in the adapter device itself, not the drive), but I didn't find the reference to the Vendor Specific Object you mentioned. What exact drive manual are you looking at ?
  10. How to read/write drive parameters?

    An A-B drive would  be straightforward because they either emulate a PLC/SLC data table file, or have a well defined Parameter object. Your Invertek drive with the HMS Fieldbus module will be a little more complex;   as it says, they use a vendor-specific object.    Maybe it's identical to the Rockwell Parameter object, or maybe it's a whole different beast. Which model of Invertek drive are you using ?   Can you post a link to the EtherNet/IP user manual you're referring to ? You can practice with the MSG instruction by sending a CIP Generic message to perform a "Get Attribute Single" with Class/Instance/Attribute = 1/1/1.   That will read the Vendor code from the drive's network module.    That at least should get you familiar with setting the path and triggering MSG instructions in Studio 5000.      
  11. ML1400 encoder wiring

    The Model 725 from Encoder Products Company is available with six different signalling options, so you're going to have to dig into this to figure out the appropriate wiring. What is the exact part number ?    It may include a code to describe the output circuit, like  Open Collector (OC), Pull-Up (PU), High Voltage (HV), Push-Pull (PP), etc. That's why engineers need to come hook up our own stuff frequently... to make sure we don't dump this job on somebody else ! Get one of the Quick Start documents from the website for the MicroLogix and look up which inputs are used for high-speed counter applications (hint, it's the first four) and how the High Speed Counter function files work in the controller. If I had to guess (and I hate guessing), you're correct that +24V and DC Common go to the power supply, and A, B, and C go to the first three inputs on the MicroLogix.    Since there aren't two wires per signal, this is *probably* one of the simple single-ended circuits.  
  12. how to read real time clock in RSLogix 500

    The emulator doesn't do every thing the controller does.    If you want to use all the functions of the controller, then buy and install a controller. The RTC functions work properly if you have a controller with an RTC installed and configured.  I personally don't like to use PLC controllers for time-of-day work, because their clocks drift over time like all electronic clocks.    You may find that after a few months, your shift-change logic is not correctly evaluating the correct time that your workers are coming on shift.  
  13. how to read real time clock in RSLogix 500

    No, the Emulate 500 does not implement the Real Time Clock.   It populates the RTC data files with values when you start the emulator, but the values do not increment. You will also find that the RTC in the MicroLogix controllers doesn't update every 1 second, but rather every 2 seconds.     It's OK for "timestamping" something, but it's not a good scheduler.   For that, use the timed interrupt functions or an ordinary timer function. There is a good list of some of the other functions and instructions that are hardware or OS related and are not implemented in the Emulator like they are in the physical controller:
  14. Status Bits

    Welcome to the Mr PLC forum ! Please be a little more careful with opening old posts;  the one that you posted to is nine years old, and related to a different model of CPU with a different operating system. All the information you need about MicroLogix controller operating system status data is in the MicroLogix 1400 Reference Manual, particularly in Appendix B.  
  15. I very strongly recommend against this approach.   Rockwell does not support the socket programming interface on redundant controllers and any Rockwell integrator, support office, or engineering team should recommend against this approach.    This cannot be made easy, or reliable, or cost-effective. Get a gateway device that is treated like an I/O device (like the Real Time Automation 460ESMC).