Joe E.

MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

53 Excellent

1 Follower

About Joe E.

  • Rank

Contact Methods

  • Website URL http://

Profile Information

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

Recent Profile Visitors

4751 profile views
  1. I've used a ProSoft gateway to connect a ControlLogix to an S7-300 to get status information back and forth so the machines knew what each other was doing. Setting things up in the ProSoft module and the ControlLogix were both pretty straightforward using the support materials on ProSoft's website but the S7 side took a call to ProSoft to get sorted out because their tutorials at the time had already transitioned to TIA Portal while we were still using Simatic Manager. Once we got it initially set up, though, it's been flawless. We were able to copy-paste it pretty seamlessly to another line with the same machines but couldn't get it to work on a 3rd line that had a different S7 processor (it only supported Profibus on board and the add-on Ethernet module didn't support IO so it didn't work with the gateway). All that to say that we've had good results from the ProSoft modules but we haven't tried to do what you're proposing. The information we're transferring is not particularly high speed but seems to be transferring at much higher than a 1-second update that another poster reported. But we're also not controlling IO, just messaging between processors. My first thought is the same as Ken Roach's above: I suggest you buy a Flux-Capacitor-equipped Delorean before attempting this so you can go back and change your mind later. I'm not at all concerned with it being a CompactLogix instead of ControlLogix, but rather that you're mixing protocols in a way that they're not meant to be mixed.
  2. Starting my career

    For me, automation is a second career. I started out working offshore. When that company was bought out I had to find another job and ended up working maintenance in a factory. That was my foot in the door. Most of my automation knowledge is from learning as I went. In that first job, all I could do was learn from the other maintenance technicians (we were multi-craft so PLCs were a small part of our daily tasks). I was able to use that experience to get a more automation-specific job that also sent me to 1-week programming classes for AB (SLC500, since that's what they used) and Siemens (S7-300/400 in Simatic Manager). After a number of  years and 2 jobs later, I was able to take another class that helped me transition from SLC500 to the Logix 5000 world (it was a very easy transition).   Edited to add: I think working as a maintenance tech first is a great way to gain practical experience. It will make you a more marketable employee and will help you be a better automation technician.
  3. I agree. I don't think OP will have any issues with this arrangement at all, especially if the drives are in the same cabinet.
  4. He may be referring to the earth connections inside the drives: ETA: I circled the wrong ones. It looks like the analog (-) connection is tied to the SC connection, which is chassis ground.  
  5. Masking array in ladder logic

    Sorry, I led you wrong. I just tried what I suggested and it won't work. The COP instruction won't work on a BOOL array. It's not as elegant or simple to troubleshoot later, but you can make a loop to move the desired bits over. Or just use a series of "XIC/OTE" pairs if it doesn't change dynamically at run time.
  6. how to logic AND array of bool in studio5000

    You may have to move the BOOL array into 2 DINTs and then compare the DINTs to -1 (a DINT will be -1 if all of its bits are 1). The COP, MOV, MVM, etc. instructions work on integer type tags, not BOOL arrays.
  7. Masking array in ladder logic

    According to the help file, the MVM instruction only uses SINT, INT, and DINT data types, not a BOOL array. If the elements you want to copy are contiguous (IOW, just the first 12 elements or 12 elements in a row somewhere in the array), use a COP instruction. You will need to move the size to a DINT tag instead of SINT.  
  8. connected users

    I know it logs changes in the internal buffer that can be written to the SD card, but I didn't know it logged people connecting to it.
  9. Import/Export on 1756-L55M12 CPU Rev 16

    Or if you're not doing anything that's version-specific, change the processor to a newer version, do the export/import thing, then change the processor in the final project back to what you're actually using.
  10. Import/Export on 1756-L55M12 CPU Rev 16

    Try copy-paste first. I usually do that instead.
  11. Import/Export on 1756-L55M12 CPU Rev 16

    You might be able to find something in the release notes for v17 about it being a feature that's added with that version. I just tried to go their download site to get the release notes but it won't load for me. There have been changes over time in the RSLogix 5000 software that wouldn't seem to be a big deal. For instance, using the mouse scroll wheel in the tag database window was added at some point between v11 and v15. I don't remember which version exactly, but it caused me a lot of frustration early on when the mouse wheel would scroll when I was in some machines but not others. It took me a while to figure out that they were at different versions and the older versions didn't support scrolling.
  12. Import/Export on 1756-L55M12 CPU Rev 16

    How are you exporting? I don't have the option to export with either processor in v15 (L55 or L61). If I change it to v16, I can rt-click and export the UDT but not the routines. Changing to an L61 processor (still at v16) doesn't change that; I can still export the UDT but not the routines. Bumping the project up to a v17 L61 lets me rt-click and export the subroutines as well.
  13. Multiple branch

    If I'm reading this right, each recipe needs to store 5 cutting distances each for 4 knives? That's really just 20 numbers per recipe. What kind of PLC is it?
  14. RSView32 File Extensions

    apa is a project archive. There is a utility that comes with FT View ME that you use to archive/restore/etc. projects. You will need to use that utility to restore the archive file. I don't have access to that computer right now or I would be more exact about what it's called and how to use it. edit to add: Factory Talk View ME is the newer version of RSView 32 for Machine Edition. It should restore a View 32 project with no difficulty as long as FTView is installed on a 32-bit computer. If it's installed on a 64-bit computer, there will be complications if the archive file was created using a 32-bit machine.
  15. Panel view plus 1000

    Your subject line says it's as PV+, so you will need to use the "ME Transfer Utility" that comes with FactoryTalk View Studio for ME. Go to the Upload tab and select the source terminal in the RSLinx Enterprise window at the bottom. If your terminal isn't there, you need to open FactoryTalk View Studio, select the "Communications" tab at the bottom of the project explorer, and add the terminal to the configuration (right-click on the Ethernet driver and "Add Device").   If you have a CF card and access to the configuration menu of the PV+, that process may be simpler for you.