MikeGuerard
Member
Thanks very much for the simplified background info George. I found this thread really useful. Appreciate the detail!
Mike
Mike
Wrong. You can keep io in controllogix. When changing from CpLX to emulate it's not a choice, it will remove io for you.
Keep IO in ControLogix?!...What are you talking about?!...ControlLogix is a PLC!...The Emulator is a PLC!...How do you 'use an Emulator in ControlLogix'?!..Or CompactLogix?!...
Replace the CPU in the software application?...Software...S o f t w a r e...There is only one software...RSLogix 5000 or Studio5000/Logix Designer...
So, again, what are you talking about?!...RSL5K 'Lite'?...That is not 'CompactLogix'!...That is a cheaper license of RSL5K software which works only with the CompactLogix processor family...
Either way, RSL5K Standard Edition (or 'higher') or Lite Edition (or 'lower'), there is no 'real' IO in any Emulator application...Just 'simulated' (1789-SIM-) modules in the Emulator chassis and 'virtual' 1756-Generic in the RSL5K/Logix Designer software application...
If using CLX, you don't have to delete IO to download.
CpLX is different. After you change the processor the software will delete all IO for you.
You are not using ControlLogix anymore!...You just replaced it with an Emulator!...The software application is RSLogix 5000 no matter the CPU type...The predefined I/O is different...
CompactLogix is not 'different'...There is no CompactLogix anymore!... It doesn't matter what CPU you were initially using; replacing it with an Emulator or any other CPU will require deleting of the predefined IO which did not get deleted by simply changing the processor type.
The point I was making was the limited functionality of an Emulator when testing real systems...You cannot use the original I/O at all...Whether automatically or manually deleted is a moot point...It is not the original controller type what matters but the I/O type...The 'real' kind...
If you are trying to make a point please learn how to quote the statements you disagree with in your replies rather than claiming the entire post is wrong...And that RSLogix 5000 does not care what CPU you put at the top of the project...It will just let you know what you could or cannot do in your user application...
Working with ControlLogix appplications, I don't delete the IO, just inhibit each module to avoid "connection request time out" errors. That way I can use the memory tables declared for the modules (toogling inputs or writing analog values).... you will have to delete all 'real' IO prior to downloading to the Emulator CPU.
An I would leave it at:
There is no ControlLogix Emulator or CompactLogix Emulator; only a Logix5000 Emulator...
http://literature.rockwellautomation.com/idc/groups/literature/documents/gr/lgem5k-gr016_-en-p.pdf
Working with ControlLogix appplications, I don't delete the IO, just inhibit each module to avoid "connection request time out" errors. That way I can use the memory tables declared for the modules (toogling inputs or writing analog values).
You seem fixated on semantics and manuals.
Semantics are very important when professionally conveying information and manuals are fundamental for acquiring of said professional information...'Monkey-see-Monkey-do' (YouTube style) will get you only so far...
You are very correct, however you also have to be correct in your comments, which in this thread, you haven't.
you will have to delete all 'real' IO prior to downloading to the Emulator CPU.
Still not correct, you don't need to delete or inhibit. It's no different than downloading to a real processor. You will get errors, but for most IO, nothing is preventing you from downloading. I say most, because I do realize there are some exceptions."...you need to delete or inhibit all 'real' IO (if not already gone) prior to downloading to the Emulator CPU..."
How 'bout that CompactLogx Emulator vs. ControlLogix Emulator thing?......Any comments?