Ken Roach

MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

156 Excellent


About Ken Roach

  • Rank
    Propeller Head

Recent Profile Visitors

13110 profile views
  1. DF1 Protocol For Bit Read

    I'm not a protocol driver author, but in general I'd initialize to zero when you open a connection or restart the driver, then roll over at 65535.
  2. DF1 Protocol For Bit Read

    Thanks for the followup ! Most A-B devices can be set for BCC or CRC, but SLC/MicroLogix default to CRC.   As you've found, it's a fairly ordinary CRC-16 checksum, so it's 2 bytes instead of 1. Remember also that the Transaction Sequence Number should increase by one every time you send a command;  the reply for that specific command event should have a matching TSN. The sequence numbers are one of the things that distinguishes DF1 from Modbus and allows true full duplex communication. Some A-B devices can be configured to ignore duplicate packets, so sequences of the same command with the same TSN will ignore all but the first one.
  3. how to change Panelview300 from DF1 to DH485

    There is a link in the thread above that tells you exactly how to load the DH485 or DF1 firmware into one of those terminals. If your question is really "I don't have the firmware, will someone please provide it for me", then ask THAT question.  
  4. Powerflex 755 Net I/O Timeout

    "Auto-Negotiate" is not the same as "Auto-Detect". A port that's set for auto-negotiation, depending on the exact implementation in the low-level firmware, will periodically drop the link and try to re-negotiate a link speed and duplex, even if it's already running at the highest link speed and full-duplex supported by the device.     With most ordinary IT gear, that's not a problem.   Your e-mail and web browsing and even YouTube won't notice a 100 ms drop in the link. But a cyclic I/O connection generally will. Let us know your outcomes, if you get an opportunity.  
  5. Powerflex 755 Net I/O Timeout

    Why ?   Unless you have also set the switch to 100/full and disabled auto-negotiate, you might be getting link drops in order to attempt auto-negotiation periodically. I do not recommend disabling auto-negotiation unless you have hardware (like some fiber/copper converters) that requires it. Your Class A subnet suggests these drives are on an enterprise network.   Are they isolated, or seeing a lot of other broadcast / multicast traffic ? Have you set up a port on the 708TX to mirror the CompactLogix traffic to ?   That will be where you connect and use Wireshark.   Generally the 708TX is a battle tank of a switch, well suited to ordinary automation projects. With the faults being so frequent, you should be able to get some diagnostics just from the link status LEDs on the switch ports to which the PowerFlex are connected. Are there any other I/O adapters or devices that also show faults/disconnections in the I/O tree of the controller ?  You may need to monitor those with GSV instructions or just watch the status indicators in the I/O tree while online.  
  6. Redundancy Processor Online Modifications

    If this is true "ControlLogix Redundancy", then you don't have to do anything to the Secondary because it automatically transfers all the edits from the Primary. This includes changes to the ControlNet configuration, if you're using ControlNet. I recently revisited a Redundant system running v19.52 and the hardest part was disabling redundancy so I could save to the CF card on both controllers.    And convincing the customer that there was no such thing as "running on secondary";    they simply couldn't comprehend that Chassis A and B were not "primary and secondary".   Bit of a language gap.  
  7. 1756 ControlLogix connect with 1734-ib8s

    You cannot use POINT Guard modules as though they were ordinary I/O modules, or with a non-GuardLogix CPU.  
  8. Devicenet to RS232 re-formatting

    Disclosure:  This is the sort of thing I do for a living, but obviously it's a pretty expensive thing to contract out.   I'm happy to discuss it directly.
  9. Devicenet to RS232 re-formatting

    Followup:   I got out my Hilscher configuration software and created a new project for a NetTap NT100-DN-RS, which is a DeviceNet Slave on one side and a programmable serial device on the other. The Configuration screen does let you change the default ID object Vendor, Type, Code, and Revision from representing a Hilscher NT100 gateway to anything you wish.  So that would let you get around the electronic keying issue.    You can set the I/O connection size to anything you like, so you could emulate the data size of the existing pressure controller. I have never used Hilscher's NetSCRIPT engine to program a serial interface.   That might or might not be a way for you to use the NT100 as a gateway for this application.  
  10. Devicenet to RS232 re-formatting

    Unfortunately, without access to the DeviceNet master configuration, what you want to do is either impossible or very difficult. While that MKS device is very useful (and a classic;  I wrote some of the first A-B technotes using it in 1999) it has a slave data layout that's built for ASCII string transfers and almost certainly doesn't match the pressure controller's data layout.     Imagine you're exchanging eight 16-bit words of data.   The "group 2 only slave" standard just means that the data gets from Point A to Point B every X milliseconds.   It doesn't say anything about what each word means or does. There's also the issue of electronic keying;  most master devices check the Identity Object and won't connect to a device that doesn't match what they expect.  If I was going to take this on, I would need a DeviceNet slave whose ID object could be modified, and which is custom programmable on the serial slave side.   The Hilscher NT100-DN-RS might do the job, or a Red Lion DSPSX with a DeviceNet slave.    I have used both of those devices but never tried to change their Identity Object. To analyze the network, you would need either a raw CANBus analyzer (and a very strong DeviceNet background) or a more sophisticated tool like Frontline Test Equipment's NetDecoder. Compared to paying the OEM to modify their program to work with a different pressure controller, how much effort and time can you put into this ?
  11. Ethernet Information

    Check the sticker on the side of your MicroLogix 1100 to see if it has Series B firmware, and check the Processor Type in RSLogix 500 under Controller Properties to be sure it's set for "Bulletin 1763 MicroLogix 1100 Series B". As far as I know, the original MicroLogix 1100 Series A firmware did not support CIP Generic messages, while Series B does.   I think Series B is defined as FRN 5 or later.   You can indavertently select a "Series A" controller in RSLogix 500 and still download and run the program on a new controller. While the MicroLogix 1400 controllers had a hardware change to support Series B firmware, all MicroLogix 1100's can be upgraded.   
  12. Ethernet Information

    Ethernet transports hundreds of different protocols, and there are dozens of common ones in industrial use. So please, post some details about the device. Unless it supports the "PCCC" command set and the Rockwell Automation specific "CIP" transport protocol, it very probably cannot communicate directly with a MicroLogix 1100 controller. The bigger MicroLogix 1400 controllers (Series B and later) do support an "open sockets" feature that lets you connect to more devices, especially those with simple text or binary data protocols, but it's still not super-easy to use. A gateway or protocol converter device might be appropriate for you.     Post more about the air pressure sensor and folks can provide more advice.
  13. allen bradley kinetics 300 user units

    There are three related parameters in the drive:   Encoder Counts, User Units, and Measure Units.     Encoder Counts of course is the number of counts per revolution of the encoder.   I think the Kinetix knows this value (often 128 or 1024 PPR) based on the motor part number. User Units (parameter 181) is the number of motor Revolutions per "User Unit".   This is typically a floating point number that expresses the ratios in the physical drivetrain. Since your slide moves 5.890 inches per 1 motor revolution, then the User Unit is 1/5.890 = 0.16977 revolutions per inch. Measure Units are the number of User Units in a Measure Unit (parameter 676, an integer multiplier and parameter 678, a selector for micro-meters, meters, or inches). When you command the drive to move 10.0 inches, it calculates 10.0  inches x 0.16977 revolutions /inch = 1.6977 revolutions.   It calculates the number of encoder pulses it needs to travel based on the Encoder Counts per Revolution.  
  14. Disqualified Redundancy Partner IO Issue?

    Obviously that's a light load of details to work on, but you've got what you've got. First, please verify that when you say "RIO" you mean I/O on EtherNet/IP, through a 1756-EN2T module.     The term "RIO" is a bit of legacy vernacular in the A-B world, referring to the old "blue hose" Universal Remote I/O network that the PLC-2/3/5 used for decades. Do you think that the comms problem on the Slot 1 Ethernet module was the reason that the Secondary was disqualified ? Did the disqualification and the failure to function as expected occur at the same time, or close together in time ?   Do the loads connected to the 1756-OW16I have inductive suppression or other circuit protection on them ?   Obviously "a relay failed to open as expected" suggests a stuck or welded contact in the relay. How was the system "stop" eventually accomplished ?   Did it happen later than expected, or not until another mechanism like E-Stop was used ? What version of the Redundancy firmware bundle does this system run ?   Have you verified that all the modules in the system are correctly loaded with firmware that is compatible with that bundle ?

    What, precisely, do you mean by "loses its parameters" ? My guess is that you mean that parameters that you have recently adjusted or modified are set back to their default values, or to the values from before you set them. The PowerFlex 525 does support a feature called "Auto Device Configuration" that stores the parameters in the ControlLogix program.    Every time the drive is power cycled, the ControlLogix will check to see if the parameter set is consistent with the configuration, and download the configuration to the drive. If your saved set of parameters is the default set, then that's what the ControlLogix will download. The first thing to check is the "Automatic Device Configuration" tab in the vertical menu for the PowerFlex 525 in your Studio 5000 Logix Designer I/O tree.