Joe E.

MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

159 Excellent


About Joe E.

  • Rank
    Propeller Head

Contact Methods

  • Website URL http://

Profile Information

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

Recent Profile Visitors

8022 profile views
  1. I created an empty project for a MicroLogix 1100. I wonder how hard it would be to build your own FIFO stack.... How much precision do you need your flow numbers to have? Can you round it to the nearest gallon? Or to the nearest 1000 gallons?
  2. PLCMentor is right. To get greater than 256 elements, you'll need to use more than one file. The PLC5 could have larger files, but the SLC and MicroLogix only go up to 256 elements, even the newer ML1400.
  3. Studio 5000 Logix Designer

    In the PLC2 and SLC150 worlds (both using old DOS software), I would often use the laptop and printout at the same time. With the printout, you can see the comments and descriptions of all of the addresses on the rung at once instead of one instruction at a time in the software. The search function in the software was pretty painful to use, too. With the PLC5 and newer, I only used the printout when there wasn't a PC available.
  4. The newer families of AB CompactLogix (5370-series and newer) and ControlLogix (1756-L7x and newer) have super capacitors and non-volatile memory to retain programs instead of batteries. You need Studio 5000 to program them. If you're at v24 or newer, symbols and comments can be stored in the PLC (memory space permitting) so you can walk up to the machine cold and upload everything you need from the machine. The Siemens S7-300 PLCs that I used to work with also don't use a battery. They have a special (and EXPENSIVE) SD card that you can swap in when replacing the CPU as long as the CPU is the same model. You do NOT, however, get symbols and comments when you upload without a project file. Those are programmed with Step 7 for Simatic Manager (older) or Step 7 for TIA Portal (newer). Only some (maybe most, but definitely not all) S7-300s can be programmed in Portal. I haven't done much with other brands yet, so I can't speak to other options.
  5. HMI user

    There are macros that run when a user logs in or logs out. You could use one of those to write the user name to a string tag in the PLC. Or do something similar. I *think* that will work, but I've never done it before.
  6. Panelview Plus 1250 Discrete Output?

    I'm not aware of any way for a PV+ to control I/O itself. If you're using Ethernet to connect the HMI to the PLC, you can add a block I/O of some kind in the HMI enclosure. Something like an Armor Block for Rockwell, or similar from Turck or another vendor. There are a bunch out there. I remember prototyping one from Turck that was fairly easy to integrate and not too expensive.
  7. We all understand long, multi-day Mondays.... My old laptop has two connections for external monitors: VGA and HDMI. My new one only has a single HDMI but I have a docking station for it that offers a few more options. I believe that my older laptop actually has more than one video card in it and I've had weird things happen on one connection but not the other. You may have ruled that out by using internal and external screens. About all I can suggest is uninstall/reinstall the software. Which version of Studio 5000 do you have? I have up to v32 installed and only have view designer 6.
  8. What's with my font???

    I'm generally a big fan of AB stuff, especially PLCs and drives. Their old PanelView Standard HMIs were solid...but I've never liked the PV+ line. The Micro 800 series PLCs and PV Component HMIs are also on the "avoid" list.
  9. What's with my font???

    Here are my standard steps for weirdnesses in FT View Studio, especially with the communications shortcut. It's worth a shot here too. Delete-recreate the object, then make a new MER. If that doesn't work, close VIew Studio and re-open it, then make a new MER. If that doesn't work, reboot the PC, then make a new MER. Is that the only object that uses that font? With the PV+ being a Windows device, that may be doing weird things. I'd try another font as a test. If it works with the new font, try changing it back.
  10. To maybe help isolate it, do you have an external monitor you can plug in? Try it both mirrored and extended.
  11. We have a mess here. Before I started last February, they didn't have anyone really specifying stuff. On our older AB machines with SLC500s, we have PanelView Standard HMIs. The newer machines with Logix 5000 PLCs have PanelView+, PanelView+6 (compact and standard), PanelView+7 (standard and performance), Red Lion Kadet, Maple Systems, and Schneider HMIs. Those are the ones I've found so far; there may be more. The ones with the higher end PV+6/7 HMIs don't need them at all but they're using them anyway.
  12. Knowing length of time PLC was powered down

    panic mode's description is a more elegant version of what I had stewing in my head. It just wouldn't come out as coherently for some reason...
  13. Like Bob, I haven't used it except to open a test project to see if I could figure out how awful it was (sorry, FT View Studio and CCW may have me a bit biased against AB's newer HMI software...). I don't have that same issue in my test program. I'm using View Designer v6.01 in a virtual machine running 64-bit Windows 7 Professional, SP1. My first thought, honestly, is video drivers. I've had weird things happen video-wise that had nothing directly to do with the software in question.
  14. Knowing length of time PLC was powered down

    My rough draft that I mentioned above did something similar except all of the PLCs were in machines on the line. IOW, one machine served as the data concentrator and gathered all of the information from the other PLCs on the line. The first word of data that was transferred was binary flags and the first flag was a heartbeat that the data generator flashed. The recipient then monitored its status to see if it stopped blinking. If your data collection PLC is always on and your network is reliable enough (ours wasn't down there), you can use the heartbeat to track when the machine is powered off. Of course, you're going to need an "extra" PLC which was another expense we didn't have the budget for. When I did it, all I could use was hardware we already had.
  15. RS5000 question/ Help understanding arrays

    Wow, that thing has 41 programs in the continuous task...that seems like a lot. It's also a SoftLogix processor (running on a PC instead of a dedicated PLC). So, the UDT "In" tag is controller-scoped, which makes sense since it's holding Input data. As an entire tag, it's used destructively (written to) about 20 times by external routines. These are only available in SoftLogix and I have no idea what they're doing since they're not part of the ACD file. All of the other destructive instructions refer to individual bits except one place in one program where an array of all 0s is written to UDT member In.D when INPUTS_BYPASS is active. Short're past my experience now. I've only ever worked with SoftLogix once, in my first automation-type job when I was a multi-craft maintenance and all we could do was go online to look at the ladder code for troubleshooting (not change anything). And that was about 15 years ago. The online help refers to DLLs and to the SoftLogix5800 System User Manual (1789-UM002) for more information. As an example, the first JXR is in the program FirstRoutine, subroutine CallScheduledJxrs and calls the routine ValveGFileStatus. That shows up in the controller organizer as a routine under the FirstRoutine program. Double-clicking on it gives you the configuration dialog which shows the path and filename of the DLL file. A quick look in the user manual shows that the DLLs are standard Windows DLLs that are developed using any standard software development software like Visual Studio. I don't know how much access you'll have to the actual DLL from within RSLogix without having a source code version of it. I'm afraid I'm going to have to hand you off to someone else at this point.