SLC500: Free reommended memory?

RSLinx, RSLogix, RSView, LogixPro ...
Post Reply
asteroidehk
Posts: 106
Joined: Sun Dec 30, 2007 8:03 am
Location: Mexico

SLC500: Free reommended memory?

Post by asteroidehk » Thu Dec 18, 2014 12:40 am

Hello friends

I have a machine with an 1747-L541C 5/04 CPU - 16K Mem. and it is using the DH+ port to communicate with a PanelView 2711-B5A8 PV550

The machine works fine, but suddenly happens strange things and I think that could be the free memory.

The actual values are:

Memory Used: 9699 Instruction Words Used - 4143 Data Table
Memory Left: 735 Instructions Words left


Which is the recommended free memory capacity?

Another question: 9699+4143+735=14577 where is the missing memory if the CPU is 16K?

In case that I need to increase the memory, should I change the cpu for an 1747-L542C 5/04 CPU - 32K Mem. o what else do you recommend? (I need DH+ for PanelView)



Image



Thanks in advance :mrgreen:

Cts349
Posts: 12
Joined: Fri Dec 05, 2014 3:28 am
Location: Asia

Re: SLC500: Free reommended memory?

Post by Cts349 » Sun Dec 28, 2014 9:15 am

What do you mean " suddenly happens strange things" ? please explain clearly what error or message you got.
So far what i know panelview550 it did not take up or occupy PLC memory.

asteroidehk
Posts: 106
Joined: Sun Dec 30, 2007 8:03 am
Location: Mexico

Re: SLC500: Free reommended memory?

Post by asteroidehk » Thu Jan 15, 2015 4:13 pm

Sorry for the time, I was on vacations

I know that the panelview is not the problem.

Strange thins like:

the machine has all the conditions to start a cycle but, it doesn´t start

A timer exceed its preset (EX. PRES 500 ACCU 4758938)

when monitoring online, sometime refresh of some inputs is too slow.

This strange situations happens maybe 1 in week, o sometimes 2 o 3 weeks doesn´t appears, this is why we think that could be the memory.

which is the recommended free memory?

best regards

LarsKBH
Posts: 23
Joined: Mon Jan 03, 2011 12:24 pm

Re: SLC500: Free reommended memory?

Post by LarsKBH » Fri Jan 16, 2015 1:58 pm

This is not a memory issue but a scan time issue.

Post Reply