Joe E.

MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

95 Excellent


About Joe E.

  • Rank

Contact Methods

  • Website URL http://

Profile Information

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

Recent Profile Visitors

5717 profile views
  1. Finding the max values in an Array

    I haven't worked with the Micro800s, but other AB processors have a sort (SRT) instruction that will sort the array in ascending order so the largest value ends up in the bottom (highest index) register. Does the Micro800 have a sort instruction?
  2. RS5000-Firmware Not correct

    Another piece of advice: max out your PC's RAM as well, especially if you plan to use Virtual Machines. I have mine at 32GB and can run 3 VMs easily.
  3. RS5000-Firmware Not correct

    I concur. I have 8 active virtual machines on my PC right now with backups on an external HDD. The total of all of these VMs is about 390GB. My 4 AB VMs range in size from 25GB to 78GB each. My 4 Siemens VMs vary from 17GB up to 62GB each. On my external drive, I also keep 3 VMs with clean OSs (fully updated, but no software installed) that are 3.4GB (WinXP), 15GB (Win7 32 bit), and 27GB (Win7 64 bit). I hear you about hard drive space. We had to bite the bullet and get good hard drives for our PCs. When my second internal hard drive failed, I replaced my main drive with a 2TB SSD, which cost about $350 a few months ago. It's down to $290 now. It was a big step up in performance and boot time. I still maintain the backups on the external drive. As end users, we use the same VMs repeatedly, so it made sense to not try to run them from external drives. An integrator who works with more platforms would need a more sophisticated system than we're using, or just move them back and forth as needed.
  4. RS5000-Firmware Not correct

    I have the following versions installed: 10.07 11.16 12.06 13.04 15.01 16.04 19.01 20.04 24.00 30.01 And I need all of them to support the machines in our plant. I've rarely had any issues installing additional versions. It's usual to install older versions first, but I've had to install an older version after installing newer ones and it went fine. You don't need to download the PLC firmware, but you do need to get the right version of Studio 5000. Go to the download center: Select "Software Downloads by Serial Number" and enter the information for your Logix 5000 license registration. Then choose version 30.xx.xx in the drop-down and download it. The minor revisions don't have to match, just the major revision. Except for v20 and one other version (19, I think) that the minors had to match too. Note: just in case you don't know (or anyone else doesn't know), changing the firmware of a PLC will stop the processor and completely wipe out its memory. Your program will be gone beyond recovery if you don't have an offline backup. In general, I don't make firmware changes to a running machine unless it's necessary.
  5. Awesome, I'm glad you're back up and running! These problems can be very random and frustrating to fix.
  6. Wire Color Requirements

    ...except when the O/L is tripped. Then we have a white wire with line voltage on it. I've always wondered why we put the O/L contact on the neutral side of the coil. Why not put it on the high side of the coil? ETA: I guess to do what I described above, where a lot of contactors are dropped when any one is tripped... I've always seen it in the neutral side of the coil, even when it's a standalone starter, though.
  7. Perhaps we should also consider eliminating the offensive Master/Slave terminology.
  8. I found a KnowledgeBase article (access level: Everyone) that appears to cover your symptoms: It's saying to install the EDS files for the chassis. Since you can see the chassis through the EN2T, I'm not sure this is the issue, but it may be worth a try. If that doesn't work, it says there's a deeper problem with your EDS files and to try the remedies listed in another KB article (access level: TechConnect): Summary: 1) If you're using RSNetWorx v10 or 11, there's a patch: 2) Make sure  your version of RSLinx matches your version of Studio 5000 (RSLinx v2.59.02 with v20.01 for example) 3) Make sure the "Compatibility mode" checkbox in the RSLinx Classic shortcut is un-checked 4) Go to your "Programs and Features" list in Control Panel and make sure the "Microsoft SQL server Compact 4.0 X64 ENU" is installed. If not, it tells you to run a particular msi file. I found another article that *almost* describes your problem, but they say the "+" isn't there in the tree view. They say to remove the EDS file and re-install the correct one. This may be worth a try before digging into some of the deeper fixes listed above. Remove the existing -ENBT EDS file and upload it from the module. If you can then browse the backplane, try re-installing the newer EDS. Here's the tech note (access level: TechConnect):  
  9.  I admit that I've never worked with DeviceNet. Are the outputs in a DeviceNet card updated asynchronously? Wouldn't O:1/28 be written every scan by the OTE instruction independent of the OTU?
  10. Here's how RSLogix 500 processors work with OTU, OTL, and OTE instructions: If the logic leading up to an OTU instruction is false, it does nothing. If the logic leading up to an OTU instruction is true, it writes a 0 to the indicated memory location. If the logic leading up to an OTL instruction is false, it does nothing. If the logic leading up to an OTL instruction is true, it writes a 1 to the indicated memory location. If the logic leading up to an OTE instruction is false, it writes a 0 to the indicated memory location. If the logic leading up to an OTE instruction is true, it writes a 1 to the indicated memory location. The big difference is that OTU/OTL instructions only write to the memory location when their preceding logic is true. An OTE instruction always writes to the memory location. So, after rung 69 executes, O:1/28 will be on if and only if N15:101 is equal to 3 or 4. If N15:101 is equal to anything other than 3 or 4, O:1/28 will be off. Has this been running fine? Rung 68 is redundant with rung 69 right after it.  
  11. Unless there's a jump or something, the OTE instruction is probably in control. Can you post a screenshot of the 2 rungs in question?
  12. You might be surprised... You could also pull the ENBT out of the chassis for 20 seconds or so and pop it back in.
  13. Ultrasonic Flow Meter noise

    That does seem to isolate the problem to the field. It's possible that the noise exists on all of the flowmeter channels but that there's something unique about the Daniels meter and its internal isolation that cancels it out or keeps it from affecting the reading. Is there a Flexim flowmeter near the Daniels flowmeter? I'd be strongly tempted to swap the cabling at the flowmeter end to see if the problem stays or moves. Are the cable runs the same between the Flexim and Daniels meters? Any additional terminations in one or the other where a shield didn't make it through continuously?
  14. Depending on your version of RSLinx and the version of the module, you may be able to right-click on it and have RSLinx upload the EDS directly from the module. That way you're sure you have the right one. I haven't seen this particular issue, but I've seen other weird RSLinx issues resolved by rebooting the PC. We use VMWare for all of our automation software, so rebooting the VM is usually enough but we occasionally have to reboot the host too.
  15. Ultrasonic Flow Meter noise

    Disclaimer: I'm by no means a grounding/bonding/noise expert... Noise and grounding can be tough. Like you, I would expect the HSC to read the same frequency as the Fluke, so noise may be getting into the HSC module from somewhere else. I can also see there being some noise in the system that the HSC would see since it has a common ground that the Fluke may not since it's power supply is isolated. You said that the frequency reading from the Daniels meter is dead on. Is it wired to an HSC module in the same chassis as the one that's acting weird? If so, have you tried to swap the leads at the chassis so the signal from the Daniels meter is wired to the HSC module that's acting up and the meter that's giving weird readings is connected to the HSC for the Daniels meter? That would help you isolate the problem to the field or to the chassis. If the weird reading stays with the HSC module, then the field wiring is ok. If it moves, however, you can rule out the chassis and investigate in detail the shielding and grounding of the field wiring. Not all field devices are the same, and your different flow meters may be bonded differently internally. Is the ControlLogix chassis with the HSC module grounded properly? Can you add or change the routing of the ground connection for the chassis frame to the system ground? Look at the installation and user manuals for the ControlLogix system and the VFDs to find the right way to bond their frames. Both have a lot of details on it. Do you have an oscilloscope you can use to look at the incoming power to the chassis power supply while the VFDs are stopped and running to compare readings? I think this would be less likely, but worth checking. These are all very speculative on my part. We get machines built to European standards and they always come in with both line and load filters on VFDs, so tech support isn't completely out of line here. In the long run, it may be better to go ahead and put in the filters on the VFDs, to avoid future issues, even if they don't completely fix this issue.