Joe E.

MrPLC Member
  • Content count

    1312
  • Joined

  • Last visited

Community Reputation

193 Excellent

3 Followers

About Joe E.

  • Rank
    Propeller Head

Contact Methods

  • Website URL http://

Profile Information

  • Gender Male
  • Location Harrisonburg, VA
  • Country United States

Recent Profile Visitors

9058 profile views
  1. Rockwell Files to PDF Request

    Here's the third part CNV9451_2019_01_31_C.pdf
  2. Rockwell Files to PDF Request

    Here's the second part CNV9451_2019_01_31_B.pdf
  3. Rockwell Files to PDF Request

    The CNV... file is in v29, which I don't have installed. I bumped it to v30 while opening it, so be aware that some things may not be an exact match. Here's the first part CNV9451_2019_01_31_A.pdf
  4. Rockwell Files to PDF Request

    Here's the second part of the Tea Line File TeaLine_Filler_02_18_19_B.pdf
  5. Rockwell Files to PDF Request

    Here's the first part of the Tea Line file TeaLine_Filler_02_18_19_A.pdf
  6. Momentary PB does not work

    Thank you for following up with the solution. That may help the next person!
  7. Compact Logix run without I/O Cards

    In CompactLogix and ControlLogix PLCs, double-click on each I/O module (whether local or remote) to open the properties. On the "Connection" tab, check the box next to "Inhibit Module". The code will run like normal but the I/O will be ignored.   Edited to add: You can also inhibit/un-inhibit modules via SSV instructions, but I've only had to do that once. One cool thing you can do while the input modules are inhibited is write to their tags. I've often written simulation programs to run alongside the main program to test my logic. So, for example, when an output turns on to move a cylinder, there's a time delay in the simulation program that will then turn on the input associated with that cylinder's position. It makes it a lot easier to commission a system when you've already simulated the logic. When I can simulate it ahead of time, I can typically just do an I/O check (make sure they're wired correctly and physically work) and it runs with little difficulty.
  8. Whatever you do, RAM is your friend. Figure out how much you need...and get more. I run all of my automation software inside VMWare virtual machines. The 32 bit VMs (WinXP, Win7) have 4GB of RAM each, the 64 bit Win7 and Win10 ones have 8GB. The host is running Win10 and has 32GB, which I wouldn't mind expanding some. It can run 2-3 VMs without issue but does still bog down occasionally, especially when I'm running a couple of VMs, Excel, Outlook, and AutoCAD all at the same time.
  9. Alternative Servo Drives

    We have an OEM building a new line for us using Beckhoff controls (PLC, servos, etc.) and they're having some supply chain issues with some of the Beckhoff drives/motors. They suggested replacing the problematic drive/motor with Festo, but we pushed back, preferring to stick with a single vendor for support in the future. I have some experience with "mixed" systems (AB PLC with Anorad/Kollmorgan drive, Siemens PLC with Festo drive) and the best/easiest systems to support are the ones that are single-vendor. They tend to work well together and there isn't an opportunity for the vendors to point fingers at each other when there's an issue. The supply issues I've seen aren't vendor-specific but are component-specific. Within one vendor's offerings, we've found some components are fine while others have longer lead times. You might be able to choose a different size drive or a drive with slightly different features that would also work to get a shorter lead time.
  10. Only thing I can think of would be an OS update of some kind that only just now got installed. It's a real long shot since XP has been out of support for so long, but it may be possible. I know our IT department manages all Windows Updates, so it may be an update thing that was delayed or something rather than a policy or patch specifically. Does the Windows system log show any updates? It *shouldn't*, but we all know better than to trust that, right? Could possibly also be a secret update to a firewall or something. Maybe I'm overly cynical, but I've seen problems traced back to IT updates that IT swore never happened...but did.
  11. Firmware Update

    Also, for future reference, v20 is one of a couple (I think 19 or 21 is the other) that had some issues with minor revisions of the software. Normally, with all other major revisions, as long as the major rev matches between the software and PLC, you're ok and can go online with no issues. Version 20 is one of the exceptions where the minor revision has to match as well. It's been a while, but as I recall, there was a major security vulnerability with the earlier minor rev of v20 that they fixed with a newer minor rev. Upgrading to the newer minor rev required flashing and downloading to the PLC, which is a pain. They then released another minor rev of v20 that could connect to either of the previous minor revs even though they couldn't connect to each other. I may have some of the details wrong (it's been a while), but I clearly remember how much of a pain in the neck it was when we had several PLCs at different incompatible minor revs of v20. With RSLogix 5000, which became Studio 5000, you can have any number of major revs installed, but only one minor rev of each major.
  12. Upload S7-1200 Siemen PLC with TIA Portal v14

    If you change the language, even while online and matching, it will make it not match the next time you open the project. To change language, you would have to re-download the program to the PLC. ***That's from my memory of v13-14 from a couple of years ago. I matched the project with online while the project was set to French and then changed the project language to English. It still matched. Then I went offline and tried to go back online and it told me that it didn't match any more. What I would do is set your project language to whatever the PLC seems to be set to and then upload. If you want to change it to another language, then, once you get online and verify that everything matches, change the project language while online, then download. This will stop the PLC and the machine. I don't know if you'll lose any online values stored in DBs or not. With Simatic Manager you would, but I didn't have that issue with that one machine in Portal. Good luck...
  13. Micrologix 1500 Apu step 4 watchdog fail.

    It would be best if you start a new post for your issue. What is the error code in register S2:6 of the status file?
  14. Factory talk text"output"

    Two options come to mind: 1) Multistate Indicator 2) Simple string display The first would look at the integer you have and will display a message based on its value. It's fully self contained within the HMI. For the second option, you would just have a string display on the HMI that would show the text from a string tag in the PLC. You would store the strings in the PLC and have the PLC copy the correct string to the display tag based on the value of the INT tag. The advantage to the first is that you can use existing PLC code and add it to the HMI without messing with the PLC at all. The multistate indicator also lets you easily change background and text colors and text size on a state-by-state basis so each step could be easily color coded. The disadvantage is that any changes to the text, whether correcting a typo or adding a message would require modifying the HMI project, recompiling a runtime file, and transferring the runtime file to the HMI. I find this more cumbersome than editing the PLC file. The advantage to the second is that you can quickly and easily update the string files from within the PLC program. You could even add a screen to the HMI to let you edit the string values at runtime without needing a laptop at all. The biggest disadvantage is that it's harder to control the text and background attributes (color, font size, etc.).
  15. Dynamic Arrays and Data Entry Studio 5000

    I think you're on the right track. You would have to set up a static array big enough to handle the biggest test (plus a little, because you know they'll want more later....). Basically, you're talking about recipes. My first thought would be to store the recipes in the PLC, because that's what I've seen done the most often. Maybe create a UDT called Recipe_Type (or whatever you want) and inside it create tags, like Temp_Setpoint, Humidity_Setpoint, Time_Setpoint, Part_Name, Num_Of_Steps, etc. The setpoints that change per step would need to be arrays, of type REAL[250] (a 250-element array of floating point numbers). The others can be whatever is appropriate. Then you can create an array to store the data in the PLC called Recipe_Storage (or whatever) of type Recipe_Type[xx], where xx is the number of part numbers they'll have to run. In other words, if they're asking for the capability to store 100 different sequences, you'd need the data type to be Recipe_Type[100] for what they want now, but you'll want to make it bigger to allow room for more later. When the operator selects a recipe, say recipe #50, the system would copy the data in Recipe_Storage[50] to Active_Recipe. Then the HMI could base visibility of the settings for individual steps on whether that step number was less than or equal to the number stored in Active_Recipe.Num_Of_Steps. Importing from Excel will be tricky and will take some software external to the PLC to write the data from the PC to the PLC and back. If you use the PV+'s recipe functionality, you MAY be able to export/import the recipe data from the HMI to a flash drive that you could then edit. I've never done that, so I don't know how easy/hard that would be. I do know that the PV+ can do datalogging to internal memory, flash drive, or FTP site, so the recipe may be able to be imported/exported the same way. I poked around a little in FT View Studio and didn't see it, but that doesn't mean it can't be done.