MrPLC Member
  • Content count

  • Joined

  • Last visited

Community Reputation

45 Excellent

About pcmccartney1

  • Rank

Profile Information

  • Gender Male
  • Location Colorado
  • Country United States
  • Interests Family, Golf, Lacrosse
  1. CompactLogix L35E

    Post a picture of you RSLinx Driver setup. You should try using Ethernet devices and then type to station 0 - Or using the EtherNet/IP Driver, browse the local subnet. The unrecognized device is more than likely the lack of the proper EDS file installed and registered.
  2. Compact Logix Tag Address for Omron NS5 HMI

    Hard to answer your question, as I don't know the structure of your program.  Personally, I have a Main routine who's only function is to JSR to the subroutines.  The each subroutine has an END instruction to return to the routine or subroutine that called it.  Short answer is yes, if you create a new subroutine, then you need to JSR to it.
  3. Compact Logix Tag Address for Omron NS5 HMI

    Thor, Interestingly, the AutomationDirect document is the best I've seen on the subject. I suggest that you have two N type files and map them both.  Use the N7Array (File 7) for PLC (Statuses) to HMI and then maybe N17Array (File 17) for HMI (Setpoints, collection of bits for operations) to PLC.  You can then either "alias" the tags in the PLC or write rungs of code to MOV or transfer the data from the NxArrays into and out of your normal tagging scheme.  In this way, you can ensure that neither the PLC nor the HMI are overwritting each others data.  If you need reals consider F8Array and F18Array
  4. Compact Logix Tag Address for Omron NS5 HMI

    Thanks Jay!
  5. Compact Logix Tag Address for Omron NS5 HMI

    Thor, Any chance you could post a picture of the Host PLC settings for the serial port?  I'm goofing around in CX-Designer and can't find a driver type that would be similar to Allen-Bradley DF1. Also, I did a quick search in the Omron forum and found exactly this topic and Joe is spot on.  You would need to map all the data needed for the HMI into the B*, N*, F*, L* files in the L32E then build your symbol table to reference them in the NS 
  6. message between L43-compactlogix and L71-Guardlogix

    Wondering why you aren't trying to do this with Produce/Consume.  Seems like it might be easier.
  7. Try using a Generic EtherNet Module with the same setup. If I'm not mistaken, you also have to configure the Ethernet module in the Kuka with another software.  At least that's how it was done in the KRC2 days.
  8. CompactLogix 1769-L30ER VS. YASKAWA MP3300 Communication

    In your PLC project, under the the IO Tree and ethernet, you will need to configure a Generic EtherNet Module. The following are settings for the Generic EtherNet Module for connection to an MP2300 but should be similar. Comm Format: Data-INT Connection Parameters: Input Assembly Instance : 102, Size: 128 (16-Bit) Output Assembly Instance: 112, Size: 128 (16-Bit) Configuration Assembly Instance: 1, Size: 1 (16-Bit)   You should download and read the manuals for the MP3300 (specifically the one for the EtherNet/IP) from the Yaskawa website.
  9. Ken is right.  You must supply power to the V+ and V- terminals on the DeviceNet Terminal block.  Generally, to be compliant, you need to supply an ODVA certified +24VDC Power Supply.  Almost everyone has something to offer.  I've used Phoenix Contact QUINT Power Supply for hundreds of control panels with DeviceNet.  Be aware that there are limitation to the available amperage that can or should be supplied to the DeviceNet network.  It needs to be less than 8 Amps.  If you exceeding this limit, you need to consider supplying an additional DNet Scanner and ODVA Power Supply.
  10. CompactLogix Communication

    Having never been a big fan of BOOTP Utility.  I always attached the serial cable, configured the DF1 driver in RSLinx.  be sure to use Auto-Config to set the baud rate.  At that point, you should be able to expand the DF1 tree and set the L35E and it's ethernet port.  Right click and select port configuration.  From this dialog, you'll be able to see it's configuration and changing if you need to.  Then go back and configure an EtherNet driver with that IP address, at which point, you should be able to go online with RSLogix 5000. Granted with today's PCs lack of a serial port, you'll also need a USB/Serial adapter.  Tripp-Lite Keyspan Model: USA-19HS is still around and very cheap.
  11. Logix Compare Tool v4.1 & Win XP

    To Joe's point, with the ACDs, I watched it open both projects, convert to L5K, then start analysing through the controller, etc...When it gets to the module comparison, it would fail.  Still doesn't lend it self to thinking that if the files are already in the L5K format when the analysis begins, as to why it fails. The Event Viewer complains about a stack overflow with regards to CLR.DLL within the .NET (v4) Framework.
  12. Logix Compare Tool v4.1 & Win XP

    Dillo!  It worked! Just for giggles, I saved the compare of the L5Ks, then went back to a compare on the ACDs and it is now working. Now tell me, what made you think of that as a workaround to comparing the ACDs?
  13. RSlogix 5000 service edition

    There are differing options for each and every processor platform type as well as version of software.  The solution above is not "locked down".  Someone could still select a different ethernet drive and point to another processor.  The basic need is for training of the personnel.  Within RSLinx, make sure you name the individual ethernet driver as either the machine name or ID.  We as an integrator, use project numbers AAANNN with AAA is a three letter acronym for the customer and NNN is the specific project.   An RSLinx Drive name is limited to 15 characters, so we also add characters concerning plant location to help differentiate. Looking further into CompactLogix, specifically the 1769-L35E, you have the option of tying the program to the serial number of the processor.  ControlLogix differs and seems to be more dependant on FactoryTalk Security.
  14. Logix Compare Tool v4.1 & Win XP

    Update First of all thanks to Joe for his help. Still no success. Deleted, Re-Installed, viewed Microsoft Event Viewer and it's complaining about a possible corrupt CLR.DLL file and stack overflow issue causing the application to die.  Worked with Joe to get a copy of the DLL, managed to get it copied into the correct folder.    An attempt to register the DLL through RegSvr32 is met with an acknowledgement that it can be loaded but can not be registered.  More than likely it's PEBKAC (Problem Exists Between Keyboard and Chair). About the only thing remaining is to attempt rebooting in safe mode and attempting to register the DLL. BTW RA Chat was of almost no help.  They did get me a copy of the original install executable for v4.1.  Otherwise says it's a Microsoft issue and of course XP isn't supported anymore. Any other ideas out there?
  15. Logix Compare Tool v4.1 & Win XP

    Have a VM in Win XP and maintained it for more than a decade.  Attempting to run the Compare Tool v4.1.  Getting an error crashing the application, part way through compare of two projects.  Chasing the error down through Event Viewer indicates a stackover flow error in .NET4 and specifically the CLR.DLL.  Yes, it has worked for the entire decade.  Just won't run properly now.  Actually got RA to send me the original installer for 4.1, but that didn't help either. There is a technote 59154 that talks about reconnecting to a drive or deleting the UserPreferences.xml.  Did this and still getting the same crash.  The note goes on to say check the Event Viewer repair the problem and retry the application. The issue is, I'm to dumb to figure out how to repair the CLR.DLL file.  Any ideas would be helpful.   RSLCompare Dialog.bmp