Skiroy said:
Well I would need all A/C inputs and Output cards.
I talked to my nemesis today. And now he is talking about bringing in a contractor to upgrade evrything to Micrologix 1400 after they told him everything I have been telling him about staying with PLC-2 or going PLC-5. He knows I have knowledge of RS LOGIX 500 so he is going to try everything he can to keep me from it.
Wait a minute, the ML1400 is programmed with RSLogix500, so he may have done you a favor.
Skiroy said:
So I need to start making a Address conversion spreadsheet and begin programing with my free version of RS LOGIX 500.
---
My questions are the following:
1. I how would I write in RS LOGIX 500 the equalvilent to how they used ---(MCR)--- and -----(ZCL)---- commands and can you give a brief explanation of each in lamens terms just so I fully understand them?
Get rid of them all where possible.
Skiroy said:
2. What is with all the numbers in Parrenthesis on the input side and all the lists of numbers on the output sides? Is this just for rung refernces of where that input or output is being used throuhout the rest of the program?
Yes, if the report has cross referencing turned on, and, if it works like RSLogix5, this would indicate address cross refernce.
Skiroy said:
3.Why is address terminal 9 always missing? Not relevant to the uograde just curious.
Octal addressing for 1771 i/o modules (at least for a PLC-5). "8" should be missing, too. You should see addressing like EDIT: (In a PLC-5, the PLC-2 may be similar) "O:01/00" through "O:01/07" then "O:01/10" through "O:01/17" in the data table for a 16 point card.
Skiroy said:
4. On all AC I/O modules. Is L2 for inputs usually the common terminal for the Input modules and L1 is the common for the Outputs? Im used to DC and the option of Sink vs Source option. So Im trying to compare this to a AC system.
Please specify part numbers as there are numerous AC input and output modules available. The most common AC input module is 1771-IAD which has 16 input points. You attach the common (four?) terminals that should be lettered rather than numbered IIRC, and assuming the correct wiring arms which also have a few options. I am assuming that you are using 1771 I/O and chassis, correct me if I am wrong.
Skiroy said:
5. If I write the program on my free version will there be any problem opening it up in the Start edition they are going to purchase?
No, but the reverse is not true. The Free version only opens files with the controller type set to ML1100 or ML1000 unless it has very recently changed. Look up the specs for the loads you are driving. I have some 1771 I/O with 12 outputs...12 2 amp triacs per card with onboard fuses...they bang big Nema coils (up to size 4) in and out with somewhat frequent cycling for condenser fans...they are virtually bulletproof. Your little legologix can't handle that type of load.
Ken's solution is perfect, but your situation is not all that bad. The 1771 I/O is extremely repairable extremely rugged and extremely common. It will be around for fifty more years. I am not nearly as confident in the reliability and power of the Micrologix I/O in comparison to a beast. 1771 I/O chassis give me a semi. Big thick steel frames with locking levers made of thick-azs metal. But the Micrologix should run circles around the PLC-2 as far as scan time if the PLC-2 is comparable to the -5. This may alleviate the need for JMP/LBL/MCR and the like.
I believe the OS between the ML1400 and ML1100 is very similar so you could get a head start with the free version.
Write generic code with an I/O map, and just leave out the I/O map (map the bits to themselves to mark them, and ease of toggling for testing). You can fill in the blanks in the input map with the real I/O when you get ahold of the real software license.
Filling in the blanks means: offline, find and replace the XIC addresses in the input map with the actual device addresses, and in the output map, you do the same for the OTE instructions.
Everywhere else in the code, you program using those mapped bits. I normally use B11 for inputs and B10 for outputs sorta like file 0 and 1.
As for your license: I would also recommend that you look into a concurrent activation, and use the FTA server/client arrangement if you do a lot of work from a desk in a network environment where it would be handy to a) share the license b) access it from multiple devices for your own purposes. If you want to hog it on one PC for longer than the FTA borrowing limit, I think you can set it up to serve it to yourself quite easily and still more or less node lock a concurrent license on one machine.