Joe E.

MrPLC Member
  • Content count

  • Joined

  • Last visited

Everything posted by Joe E.

  1. firmware for compactlogix 1769-l32e version 17.004

    If Rockwell and your local distributor can't/won't help you with option 1... ...Rockwell may charge you a lot for option 2, especially if you don't have a support contract with them. I can't help you with option 2 (even if you emailed me an image of the CF card) because I don't have an -L32E at v17.004. I know we have an old, out-of-service PLC from that family, but it's at v13. Option 3 *MAY* be possible, but the fact that your photo shows a DeviceNET module makes me very cautious. If you try that, you're on your own. Be sure to make GOOD backups of the CF card image before you do anything. If you fully explained the issue and your end goal, I would be really surprised if Rockwell and/or your local distributor can't/won't help you with this. We have a very good local distributor who has gone above and beyond to help us with some really weird issues over the years.  
  2. firmware for compactlogix 1769-l32e version 17.004

    I've never done it, but I'd say it's worth a shot, especially if the controller is at a newer version than the p5k was originally. I might reach out to Rockwell or my local distributor before trying it, though. Especially if the program is doing anything "fancy", like motion control or special modules.
  3. firmware for compactlogix 1769-l32e version 17.004

    Do you need RSLogix 5000 or the firmware update file for the PLC? If you need RSLogix 5000, just download the latest minor revision of v17, which is 17.01.02 as far as I can see here. As far as I know, v17 was not sensitive to minor revision differences (unlike v20...).
  4. Alarms Display Missing

    Do you have an older copy of the project from before you deleted it? If so, restore it with a different name, then open it in a 2nd instance of View Studio. You can copy-paste between the projects. If it's the built-in default alarm display, you can also create a new project and copy-paste it from there.
  5. RSLOGIX 500

    I just learned something. I didn't know you could do that. Cool!
  6. How should I matching the impedance?

    Have you measured the signal at the AI module? You can disconnect the AI module and just use your meter in its place to rule out the AI module. If the device is too far away and the resistance of the wire is too high, the device may not be able to drive the current. The input impedance of that module is 250 Ohms, so add that to the cable resistance to see if your field device can drive through that much resistance. The 1769-IF8 technical specifications are in this manual, starting at page 24: Verify the wiring is correct and that the module is configured correctly in the Logix project. There may also be some useful information in the installation instructions:
  7. So, here's the situation. We (controls engineers) are trying very hard to get out of the password business. Folks share them with other folks who aren't supposed to have them and within a month or so they're useless, so we have to change them again. I recently added some user administration screens to a Siemens HMI (an old MP277) that allow an admin user to add and delete users and set and change their passwords. We can download an updated project to the HMI without affecting the passwords. I'd like to add the same functionality to some of our machines with PanelView Plus HMIs. We have some that are the original PV+, some PV+6 standards, some PV+6 compacts, and some PV+7 standards. Our firmware versions run all the way from 5.0 to 9.0. Our View Studio for ME is v8.20, on a 32-bit VM. I can add controls to allow a properly logged-in user to change passwords, BUT...when I later download an updated *.mer file, it overwrites the users and passwords with whatever is in the project, which almost completely defeats the purpose of this whole exercise. On a lot of the machines, the password is stored in the PLC, but there are places where "they" don't want the passwords visible to anyone, including the maintenance staff who have access to the PLC program. So.... Is there an easy way to do the password management in the PV+ HMI without the passwords being overwritten by downloading an updated *.mer file? If possible, we would like to avoid having to muck about in the Windows desktop of the HMI.
  8. PanelView+ users and passwords

    That's what their support folks came back with too. That's not ideal, but may be where we end up with if we have to implement it (we'll resist it for a while). Another option we thought of is "encrypting" the passwords in the PLC by using a know-how protected block or AOI that does "something weird" with the password string so the visible tags in the tag database are gibberish (maybe something as simple as adding an offset to the ASCII code for each character or something). That would make the HMI side easier, but the PLC side harder.
  9. Compactlogix,SLC and Prosoft

    Even if you can get the ProSoft module to work in the SLC rack, it would probably be simpler and easier to make it a local Compact I/O module. Probably simpler enough to justify the cost of replacing it.
  10. Controllogix firmware upgrade

    I would definitely get online and start a chat session for activations support. I "followed the procedure" and couldn't get it to work either until they did "something magical" on their end to make it work. Their versioning system is weird...but Siemens' system is also weird in a worse way. In their scheme, newer versions of the software can't be installed at the same time as older versions. If you open a project in a newer version, it converts it to the newer version and you can't connect online with the hardware without downloading from the project to the PLC, which opens a whole slew of cans of worms. Also, a license for an older version will not activate a newer version, so every time we got a machine with a newer version of software, we would have to buy a new set of licenses, or subscribe to their update service, which we finally had to do last year when they started releasing a new version of Portal every year.
  11. Controllogix firmware upgrade

    Hmmm, that's interesting. I'm surprised the license can't activate the older versions, that's not been our experience. We have some Logix 5k licenses that date back to v10 and have no problem activating up to v30 (the newest we've installed). Some licenses of Studio 5000 we bought at v24 also activate back to v10. There's an option in the Activation Manager when you're hosting the license to your PC where you can select how to host the license. One of the methods supports back to the old versions, the other doesn't. It doesn't work smoothly, though. The last time I had to re-host a license, I ended up having to contact their chat support (free for activation support) to get the license to activate both the older versions and the newer ones. We have machines in service right now ranging from v11 to v30, so I know it can be done.
  12. Report Button

    There's a link at the top of the post, next to the post date/time. It's grayed out until you hover on the post. I've reported some of them, but they keep posting them.

    It is a MAJOR violation of this forum's rules to ask for or discuss software piracy or any kind of password or license breaking.
  14. Master Time Source

    We have a system with a Kinetix 6500 drive controlled by a CompactLogix -L33ERM. The local CompactLogix is the system time master. It's networked to a few other Logix 5k machines, but we've never had issues with them fighting each other to be time master. On the Date/Time tab of the controller properties, there's a button labelled "Advanced..." that lets you set the priority of each machine. You might tinker with those settings to make sure that each PLC is its own time master. Hmmm.... I checked that line again and we actually have time synchronization turned off on the other Logix 5000 processors, so this reply may or may not be good information...
  15. Controllogix to PLC5 Serial Comm

    Since you're going between processors, try adding a null-modem adapter. Edited to add: a null-modem adapter reverses the Tx/Rx pins (2 and 3 on the "standard" 9-pin d-shell connector). It allows two devices that are both "masters" to talk together.
  16. Communication: PV +600 to SLC 5/03

    We have about a half dozen SLC 5/03 and 5/04 PLCs  in service right now. Unfortunately, they're pretty far down our upgrade list, behind the dozen SLC 100/150s, half-dozen PLC-2s, and dozen or so PLC-5s. We also have a handful of the SLC Fixed chassis PLCs (-L40 series). If you're in a similar predicament as we are, consider the Red Lion G3-series of HMIs to replace the PV550s. We've done that with several SLC 5/03s with good success. They can connect via either the RS-232 or the DH485 port. They're also a viable option to add/replace an HMI on a PLC-5 system. Edited to add: The G3 HMIs connect to the PLC-5 via the serial port, not DH+. One possible advantage of using a PV+ of some flavor (if you can overcome the protocol limitations) is the tool that lets you import the old PanelBuilder32 project into View Studio. We've had hit-or-miss results with that, though, and you may be better off starting over from scratch.
  17. Dashboarding Recomendation

    You can also consider the Red Lion Data Station Plus and ProducTVity Station, especially if you have multiple platforms and/or protocols.
  18. Communication: PV +600 to SLC 5/03

    Yeah, the scaling can be a pain. BTW, it's not always the fault of the conversion tool. We have in service a few 4" PV+7 HMIs that the built-in banner display that shows system faults (like communication failures) is so small it's illegible.
  19. Communication: PV +600 to SLC 5/03

    Now that I think about it, I don't remember setting up a PV+ to communicate via RS-232. All I've ever done have been DH+ or Ethernet/IP. I would think that you could set the RS-232 port on the HMI and the 5/03 to the same baud/etc. and it should work. Especially if you haven't done it before, setting up the shortcut in View Studio can be tricky.
  20. Communication: PV +600 to SLC 5/03

    You should be able to connect using the RS-232 port. How is that port configured in the 5/03? What's the catalog number of the old PV550?
  21. Error Code

    The user manual says to check: 1) ...the I/O module is in the chassis 2) ...the electronic keying requirements 3) ...the controller properties major faults tab and module properties connection tab Expand the I/O Configuration tree and look for a module with a yellow triangle icon: Open that module's properties dialog and go to the connection tab. There is a check-box there for "Major Fault on Controller If Connection Fails While in Run Mode". Evaluate whether or not that box needs to be checked. On the "General" tab, look at "Electronic Keying". For most applications, you're fine with "Compatible Keying". If it says "Exact Match" and that module has been replaced with one that's a different revision, you may get this fault. Again, evaluate your application to see which kind of keying is necessary. BEFORE changing EITHER of these settings, click the "Help" button to learn exactly what they do and evaluate the system in detail to see how changing that setting could affect your operations.
  22. Adding To Current Routine VS Creating New Routine

    I would say that using subroutines to subdivide code into easier-to-read pieces is worth any overhead hit it might cause. IMHO, if your processor is so strapped for resources that subroutines push it over the edge, you probably need a bigger processor anyway.
  23. I would think so. Your destination element will likely end up being identical to what's in the existing MSG while the source address would be your new tag name.
  24. Do you know what devices are on the other ends of the MSG instructions?
  25. There's another parameter you have to set, to make sure it uses parameters as its source for IP address, basically disabling DHCP/BOOTP. The BOOTP utility has a button you can push to disable BOOTP, but it doesn't always work.