determining a program's size

merlin00724

Member
Join Date
Oct 2007
Location
cincy, OH
Posts
45
ive been tasked, due to a restructure of our inventory, to find out how big our SLC programs are. specifically, we have several dozen 5/05s at our plant and we stock 16k, 32k, and 64k processors. I need to find out if 32k is big enough for everything and we will just stock a single 32.

I looked in controller properties and memory used and memory left doesn't add up. I think I am going at this wrong. How can I find out the "k" size of a given program?

thanks
 
I think its just straight conversion... double click on the controller properties and you will see 'words used' and memory left, so memory left is 12xxx then you have 12k left

They are 16k 32k and 64k
 
There is some overhead that you can't count. I have a 32k SLC 5/05 and when I add up the "Instruction words used" "Data Table" and "Instruction Words Left" I get 29920.

I don't think there is a limit in the SLC on how you allocate available memory whether to data table or instructions like there is with some Micrologix models where you can only use a certain amount for data tables.

For your situation then, take the "fattest" SLC program you have and change processor types to the 32K, uncheck "Resize Data tables", verify program files, then check the controller properties. If you leave "Resize Data Files" it will shrink them for you to the last element used in each file which often can create a problem. If your verify fails due to a lack of space, manually shrink them as you choose, or do it again and let the software pare them down for you.

Be sure to leave at least 1k free at a bare minimum. Doing online edits can be a problem if you don't have enough unused edits.
 
Last edited:
For your situation then, take the "fattest" SLC program you have and change processor types to the 32K, uncheck "Resize Data tables", verify program files, then check the controller properties. If you leave "Resize Data Files" it will shrink them for you to the last element used in each file which often can create a problem.

Don't understand why AB allows "Resize Data Files" if it can create a problem. On several occasions we had to substitute processors with different memory sizes and had to decide whether to resize or not. I asked several Engineers over the years about this issue and know one could give me an answer. Just told me not to use unless absolutely necessary or verify program manually, can anyone elaborate.

Regards,
Sydney
 

Similar Topics

Hello, I need to determine analog and digital I/O for a new ladder logic program I am going to be creating. Are there guidelines? How does one go...
Replies
8
Views
2,451
We are in the process of installing a new DC drive to replace a 1373 series Speedpak drive. There are 8 leads coming out of the motor -- Two for...
Replies
5
Views
810
Good morning! I am looking for a clever method to determine the number of occurrences in a series using ladder logic. What I need to determine is...
Replies
6
Views
1,236
I have my PLC and HMI connected to my local network over DHCP just like my laptop. I can upload and download including VNC to the HMI over wifi...
Replies
2
Views
1,129
We have a DC Drive (ABB DCS800) which is running a load (initially) at a fixed speed. For testing purposes, we want to simulate a different...
Replies
20
Views
6,157
Back
Top Bottom