MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

26 Excellent


About ElectronGuru

  • Rank

Profile Information

  • Gender
  • Location Missouri
  • Country United States
  • Interests ones and zeros.
  1. AB Studio 5000 Lite

    In addition to @VFD Guy's suggestion, I would look up the release notes for the specific version of Studio5000 Lite you have and see if there's anything in there that might answer the question. 
  2. Communication

    @VFD Guy This would have to be done offline and then downloaded, or in the program mode. Of course the process would have to be stopped; about 1/2 the drives out there will not let you change the speed reference while the drive is running. I've never figured out how they go about deciding which drives they'll allow a speed reference change while running, but there it is. There are at least a dozen different ways this can be done. But whichever method is used, I would never want to make a major change like this to a running process. You'd want to have the time to safely and thoroughly test the changes before releasing the process back to production.  Yes, speed reference data can be sent from the Micro to the Compact but if done over a network, it would almost certainly have to be via a MSG instruction, and that's time and scan consuming. I don't know how responsive the OP's system has to be, but that might make for sluggish performance, depending on how much network traffic they already have. He could also hardwire the analog output from Micro to Compact and go from there, but he stated earlier he wants the analog input direct to the drive from the Micro.   
  3. 1756-IF8 rev 1.5 Input tags freeze

    @der0492 Thanks for sharing the Tech note because though we're always on the lookout for EMI, I didn't know that was a possible anomaly for the IF8. And we use quite a few of them. To add to @BobLfoot's comments, when you have to hotswap, (Allen Bradley calls it RIUP, for Removal and Insert Under Power) I'm a big fan of placing the controller in the program mode, if possible. If the process is dependent on these inputs for control, and you remove the card in the run mode...... well, use your imagination, lol. Bad things could happen to your process. In any case, the card's configuration is held in the controller and written to the new card so yes, all your scaling, etc, will immediately be written to the new I/O card when it powers up. But there's a catch or two: The new card must be a direct replacement card for the one coming out. If the "Electronic Keying" setting in the card's properties is the default "Compatible", the firmware on the new card must be the same or higher than what's saved in the controller. If the keying is set to "Exact Match", the firmware and everything else on the new card must match exactly what the old card was. Hope this helps, even though you hopefully were able to locate and remove an EMI issue and not have to replace parts. Let us know how it goes, please.
  4. Fault Reset on powerflex

    @PaulKim1003 which specific model of PowerFlex are you using? As you've seen from the previous responses, the answer to your question may vary from drive to drive. The physical Stop button on the front of all PF drives can also be used to clear drive faults. However, within the logic of the drives, some PowerFlex drives' Stop and Clear Fault are always the same input (PF70), and on other PF drives they can be separate inputs (PF755). As @Dev Shrivastav showed above, when they can be on the same digital input, you will almost certainly have to program separate logic instructions. 
  5. Communication

    So reading through the thread again, are these the desired operating conditions? The CompactLogix starts and stops the drive. Never control that from anywhere else. The MicroLogix controls the speed of the drive. Never control that from anywhere else. If so, this is what I would do: Check to see if the PF drive has been added to Compact's I/O configuration. (If it's currently receiving instruction via Ethernet, I guarantee it has).  Go into that configuration (within the CompactLogix controller, NOT in the drive) and change the speed reference (parameter 38) from "Comm Port" to either "0-10V Input" or "4-20mA Input", whichever you have available on the Micro. This step will ensure that the PF drive is always looking at the analog input for speed reference. It shouldn't care that start/stop and other commands come over eNet.  Hardwire an analog output from the Micro to the appropriate input on the PF drive. Write the code in the Micro to scale and control the analog output for speed.  If you have to make any other adjustments to the PF drive parameters (such as Min/Max frequency, etc) do so in the CompactLogix, not the drive itself.  This should work for you and minimize system complexity for this unusual control situation you're in. I would also add rung comments in both controllers, and parameter descriptions on the PF (again, within the CompactLogix I/O tree Device Definition) to explain the setup to anyone else working on the system.
  6. FactoryTalk View Studio Runtime issue

    That sounds pretty bad. If it's working from the FT application, I'd just open and test/run projects from there, and not launch directly from the .mer icon. Otherwise, the only thing coming to my mind is re-installing FT Studio. Were there any recent changes to your laptop? Any updates or installs that a system restore might take care of? 
  7. PanelView Windows screen

    The original post was keeping me up at night, because I knew there was a way to reset that password without flashing the PanelView. I just tested this procedure and it works on my PanelView 7+. -          Plug a keyboard into a USB port and hold F1 while the HMI is rebooting, and this will bring up the Maintenance Mode. -          Use the touch screen (arrow keys, if on keyboard) to select “Special BOOT Action”. -          Use Right/Left arrows to select “Clear All Data”. o   This will clear everything except the firmware. -          Select “Continue booting with selected options” -          During the rest of the BOOT process you will be prompted to create a Windows CE access password. Using this procedure, you will lose any applications within the PanelView, but not have to flash the firmware.
  8. FactoryTalk View Studio Runtime issue

    Since the .mer can only be run in the PanelView, I assume you're running the test mode from your laptop, where FT sets up a temporary .mer-like runtime on the laptop, and mimics the PanelView while being connected to the controller. If so, are you using a shutdown or goto configure button within the FT project, or typing "X" to stop running the test mode? Or is this a problem with shutting down the FT Studio application, itself?
  9. CompactLogixL24ER

    I checked catalog numbers and found only these three Compact L24 controllers:  1769-L24ER-QB1B 1769-L24ER-QBFC1B 1769-L24ER-QBFC1BK All will take Studio5000 Versions 19 through 32.  
  10. RSLogix5000 CDM

    As far as I know, the CDM only exists in RS5 and RS500. RS5000 and Studio5000 use tags, and therefore have the tag monitor, the Watch and Quick Watch window, and the Data Monitor. To view a custom list of tags, open the Watch window and create a Quick Watch list.  If you can build a trend in an emulator, I would that the emulator can trend. However, I could be wrong, as I don't really use emulators. Assuming you can trend in S5K Emulate, make sure you hit the start button to get the thing going after you've created it. Then it's usually a matter of adjusting all the trend settings (sample rate, time span, scale, etc) to get it dialed in and displaying usable data.
  11. After replacing PowerFlex 70, the HIM is blind???

    So the HIM works on an existing drive, but not the new one, and doesn't even appear to have power when installed on the new one? I can't seem to match either of those drive catalog numbers exactly but in this string,  20A E 2P7 A 0 AYNNNCO, that 0 means "Blank face".   That could mean this drive is not equipped to support a HIM.  The HIM cradle has a small four to six conductor cable that plugs directly into the drive, usually at the main control board. Remove the HIM and take the front cover off the drive to see that the HIM cradle is properly plugged into the drive. The cable is likely unplugged, damaged, or non-existent.  
  12. @Michael Lloyd I came up through relays and didn't start learning logic until the mid 90s. I started in ControlLogix with version 16 and the first time I saw OTEs in series, I though my head was going to explode. I programmed for another few years using only parallel until I got to a power plant, where scan time was everything. I find that since leaving that job I'm still putting OTEs in series, and still looking for anything that'll reduce scan time, even when it's not all that necessary. @Joe E. If you take it a step further (and know your tags that well) you can type the whole thing out in ASCII. To use your example:     BST XIC Tag1 NXB XIC Tag2 BND XIO Tag3 OTE Tag4   
  13. A quick note about placing outputs in series. Some programmers don't like putting outputs in series but if you have a large project, you can reduce scan time by avoiding branch rungs whenever possible. The best way I've found to demonstrate this is by viewing the code in ASCII, by double clicking on a rung number. When ladder logic is shown in ASCII it uses the format:     instruction tag instruction tag So if a rung of code consists of an examine-if-on instruction with the tag IN1, followed by an output-energized instruction with the tag PUMP2, shown in ASCII it would look like this:     XIC IN1 OTE PUMP2 Where you have branch (parallel) rungs, in ASCII they are shown as:     BST = branch start, NXB = next branch, and BND = branch end. Now check out the attached pdf. The same code is shown twice, once using outputs on branch rungs, once putting all outputs in series. In both images I've opened the ASCII editor to get a better idea of the steps the controller takes when scanning the code. At a glance, it's easy to see that if the same three outputs in the first example are placed in series instead of on branches, the controller gets to take four fewer steps when scanning the code, but the outcome is the same. You can place instructions on a rung in an input-output-input-output format, which is called "interlacing", so long as the last instruction on the rung is an output.  PLCs were invented in the late 1960s, and ladder logic was specifically developed to have a computer programming language that resembled relay logic schematics. And for the next several decades, we kept following the hardwired rule that outputs must be placed in parallel. In fact, in older software like RS500 for SLC500 controllers, placing outputs in series is not possible. But somewhere along the way it occurred to someone that these are not physical outputs, they're 0s and 1s in a processor. And with the Logix generation of controllers, they finally gave us the option of putting outputs in series and interlacing. When you're working with code that has hundreds of tags and thousands of rungs of logic, scan time is everything. And placing outputs in series is just one of the many tricks to help reduce scan time.  Hope this hasn't been overwhelming and welcome to world of Studio5000 programming! ascii.pdf ascii.pdf
  14. Communication

    @akashleo if you're wanting to alternate a single PowerFlex40's speed control between the existing CopmactLogix and a newly installed Micrologix 1400 (or any other system), you will have to change the value of drive parameter 38 (Speed Reference) any time you want to change form one controller to the other. While some PF drives can have alternate speed reference inputs (usually referred to as "Speed Ref A" and "-B"), that can be switched back and forth with something as simple as a digital input, the PF40 can only have a single speed reference programmed.  What is the reason you might have this singe drive change speed control from Compact to Micro and back?
  15. Communication

    So you're taking a PF40 away from the CompactLogix and installing it on a Micro 1400? If so, your Micro should have a analog output channels on it. You'll want to use either a 0-10VDC or 4-20mA. Wire the analog output on the PLC to the analog input on the drive. You'll program the PF40 to use the analog input as the primary speed reference (parameter 38), set the minimum frequency (parameter 34) to 0Hz, and the max frequency (parameter 35) to 60Hz.To scale the speed in the drive, you'll need to use parameters 110 through 113. You will then need to write code for the Micro to look at the input condition that causes the drive to speed up and slow down, and adjust the analog output accordingly.