Ken Roach

MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

105 Excellent


About Ken Roach

  • Rank
    Propeller Head

Recent Profile Visitors

7371 profile views
  1. Micrologix 1500 + 1769-SND

    The 1734-PDN is basically a network isolator and power supply;  each of the POINT I/O modules appears as a DeviceNet node that goes into the 1769-SDN scanner module scanlist. "Has someone implemented something similar" is a very broad inquiry.    If you have a specific question, please post details. If you are looking for a tutorial on RSNetworx, or a guide to DeviceNet wiring, or help selecting parts, please post details or (preferably) start reading documentation on the Rockwell Automation website.
  2. Hi Ken,

    You had responded to a PLC2 topic before, I added some files to the thread hoping someone knows how to open??




  3. Fault Code 80

    If the controller memory has been cleared (it's done on purpose if the program checksum shows it's corrupted) then you'll just have to re-load the program. DeviceNet scanners hold the "Scanlist" information in their own nonvolatile memory.   If that had been cleared by a power surge, then you would have a different error code indicating an empty scanlist (I think Error 75).    If you unplug just one slave device and start getting Error 72 for that node number, you know that the Scanlist is intact and the network is intact.
  4. Retrive Password from mer file

    Can you log onto the FactoryTalk Local Directory separately from the Restore operation ?     Make sure you go through the process for configuring or resetting the Local Directory users and passwords (often the local Windows Administrator is the default user) first, so that you can at least log on to the FactoryTalk Local Directory. If the application's Runtime file (*.MER) was created with a FactoryTalk Password, and you don't have that password, there's no way to Restore the MER into a Project file.   That's the basic protection against reverse engineering/modification that is built into the software. Even if you do have a FactoryTalk password, the actual User passwords cannot be retrieved from the application. As mentioned, the discussion of password cracking is against the terms of service for this website and is generally not allowed by the Forum community.
  5. 1769-ASCII Read Issue

    If there are carriage returns and line-feeds at the end of each of those lines, then I agree that the module is simply over-writing the input buffer each time it receives a line with a delimiter, and the PLC isn't grabbing the data until after the buffer has been over-written. Maybe you could configure the card for "Ignore Delimiter" on received strings, and set the Rx Timeout to an appropriate number of milliseconds in order to deliver the whole string "****<CR><LF>0<CR><LF>OK<CR><LF>****<CR><LF>" into the input data table. In the CompactLogix, it's relatively easy to search a string for another string with the FIND command, so you could look for "OK" within that string. I remember running into a similar issue with a POINT I/O ASCII module and having the problem that when you didn't use a delimiter, the only way to declare the end of the incoming data was a fixed buffer length.   The 1769-ASCII allows you to use a delimiter, or a fixed buffer length, or a timeout.
  6. Tag description to string

    Another thing to consider;  FTView does evidently have access to a tag Description as part of the extended properties of the tag.   The user program has access to some Extended Tag Properties as read-only values (@Min and @Max, notably) but not the @Description property (again, as far as I know).
  7. Tag description to string

    I'm not aware of any way to access the documentation database from within the user program.    That documentation is saved to the controller only during a download, and is meant principally for recovery of program documents by Studio 5000.
  8. SLC 5/05 Revision Numbers Question

    Series C hardware controllers do have a new Ethernet daughtercard.    It supports 10/100 Mb/s full duplex and has better performance than the old daughtercard, and I recommend it. There is a deeply nerdy reason why the SLC-5/05 operating system and daughtercard upgrades released in 2008 or so weren't simply called "OS502", but it's impossible for even A-B engineers to explain coherently. Series A and Series B controllers will be functionally identical. You can dither around and find release notes for each revision, but I wouldn't bother.    Just get OS 501 FRN 11 for any Series A or B controller, and OS501 FRN 13 for a Series C controller, and load it using ControlFlash.   SLC-5/05 firmware used to be chargeable, but now it's a free download from the Product Compatibility and Download Center.    
  9. Newbie Screwed up AB 5/04

    The DH+ port is the 3-pin (and the DIN8 round pin) network port, considered "Channel 1" on the SLC-5/04 controller.   It will have a blue twin-axial cable connected to it. The Channel 0 serial port can be set up for ASCII or DF1 or DH485 protocol.   I was asking about that Channel 0 LED because when you disconnect it, it flashes steadily when set up for DH485,  but stays OFF if it's set up for DF1 (default ) or for ASCII and there's no outgoing commands. In general, the DH+ channel status LED will be steady green if there are devices on the network that are "passing the token", even if they aren't communicating with one another. The SLC-5/04 user program includes the DH+ node address for the SLC-5/04 controller itself.   Often the PLC is "Node 1" and the HMI is "Node 2". But if you inadvertently changed the DH+ address for the SLC, then the HMI won't see it at the expected address, which will generate error codes.   Why were you loading an old program into the machine  in the first place ?   Were you trying to overcome a communication issue ?
  10. Solved: Grace Period No Longer?

    Hey, thanks for the info !   The newest revision I'm personally running is v28, so I have not encountered this yet. As the next job I'm doing will be v30, and will involve a fairly remote jobsite, I'm glad I know this ahead of time !
  11. Newbie Screwed up AB 5/04

    Welcome to the MrPLC community !   Ready for a torrent of diagnostic questions ? What make and model is the HMI ?    Is it connected via the DH+ port, or the RS-232 port ?   If it's connected via DH+, how may other devices are on the DH+ network, and are they all working correctly ? What sort of diagnostic messages appeared on the HMI ? What is the status of the DH+ port status indicator LED ?    What is the status of the Ch.0 status LED (the serial port ?).   Disconnect from that DB9 connector and observe that status LED.   If it is blinking green slowly, then the port has been configured as DH485 protocol and you will need to work around that. Does the "Auto Configure" feature in RSLinx Classic work anymore ? The most likely outcome is that you'll re-load the controller program by clearing controller memory so that the Channel 0 serial port is set back to its default DF1 Full Duplex protocol.   That generally involves shutting down the controller, removing the CPU, unplugging the battery, then shorting out the Vdd and Common solder pads (for a minute !) on the back of the controller's circuit board so that the memory drains and the controller is set back to defaults.   There are numerous forum posts and user manuals that show you exactly where those pads are.
  12. Solved: Grace Period No Longer?

    That's not normal, in my experience.   I'm running v28 and regularly have to run without the dongle (in a sterile laboratory with air-gap security) but still have full edit capability. What is your ordinary license;  a Toolkit, or the Standard or Professional licenses ?   Does the software indicate that it's running in Grace Period (with the periodic pop-ups) or does it indicate it's running as Service Edition ? Any chance you've got a Service Edition activation resident on your PC now ?
  13. need help

    ControlLogix Redundancy requires a specific set of hardware and firmware for each Release.      While the 1756-RM2 is a successor to the 1757-SRM, you cannot mix them in the same system. The 1756-L72 controller support starts with Studio 5000 v21.    You cannot use the old v16 software with that controller. It sounds to me like you're trying to support an older ControlLogix Redundancy system.    You should look up and read the Release Notes for that specific release, and follow them closely.   If you don't have the software tools or support resources to work on that control system, please consider hiring Rockwell Automation or a qualified system integrator to do so, as control systems that use Redundancy usually have significant safety or economic consequences.
  14. The error suggests that the MCM module isn't responding to the backplane and it may be damaged or defective. Was there an event that caused you to replace the power supply which might also have damaged the MCM module ? If you are using an AC power supply, check carefully to be sure the voltage selector jumper is in the appropriate position for 240/120V .
  15. Programming Question

    Rob, The SLC-500 and MicroLogix operating system executes only LAD2 automatically.  The STI (timed interrupt) and DII (discrete interrupt) routines can also execute routines. But otherwise, every subroutine needs to be called from another routine.    Probably 90% of all MicroLogix programs include a section of LAD2 that's nothing but JSR's to run the other program routines.