Modicon State RAM Layout

jseroka

Member
Join Date
May 2009
Location
Canonsburg
Posts
3
The Modicon compact 984 says:

Each 0x or 1x value implemented in user logic is represented by one bit in a word in
state RAM, by a bit in a word in the history table, and by a bit in a word in the
DISABLE table. In other words, for every discrete word in the state RAM table there
is one corresponding word in the history table and one corresponding word in the
DISABLE table.Counter input states for the previous scan are represented on page
F in an up-counter/down-counter history table. Each counter register is represented
by a single bit in a word in the table; a value of 1 indicates that the top input was ON​
in the last scan, and a value of 0 indicates that the top input was OFF in the last scan.

Does anyone know the specifics of how the SRAM history/disable tables are set up? It says they start from the end of the SRAM and work forward.

We are using Proworx to program the PLC. And I think it is allowing us to have the 0x,1x,3x,4x registers overlap with the enable/history registers. And I am trying to determine where the conflict is.

 
In Proworx32 go to Configuration/Controller Properties to see what the register ranges have been set up as.
For example the one I am looking at has 0xxxx 1536, 1xxxx 0512, 3xxxx 0048, 4xxxx 1872. If you try to use addresses outside of these preselected ranges you will have trouble.

Brian.
 
Our address limits are:

0xxxx - 1600 (Memory Addresses 1 through 100)
1xxxx - 256 (Memory Addresses 101 through 116)
3xxxx - 99 (Memory Addresses 129 through 227)
4xxxx - 1800 (Memory Addresses 241 through 2040)

So this uses 2040 registers(Since the 3x,4x must start on a 16 word boundary). But then I think there is a history word and a disable word for each of the 0xxxx and 1xxxx starting from the back of the 2k state ram and moving forward.

I am trying to figure out which history/disable words are conflicting with the 4xxxx registers that are used in the overlap range.

Is it:

Disable 0xxx1
.
.
Disable 0xxxN
Disable 1xxx1
.
.
Disable 1xxxN
History 0xxx1
.
.
History 0xxxN
History 1xxx1
.
.
History 1xxxN

OR is it:

Disable 0xxxN
.
.
Disable 0xxx1
Disable 1xxxN
.
.
Disable 1xxx1
History 0xxxN
.
.
History 0xxx1
History 1xxxN
.
.
History 1xxx1

I am not the programmer of the PLC, I only have a PDF of the ladder logic and a screen print of the register usage.

The History/Disable words do not show in the register usage.

Any help is appreciated.
 
Why do you think the State/history/disable etc bits are accessible to you as the plc programmer?

I have never seen them. The book only mentions them for information. Do not worry where they are as you cannot access them. Modicon does not let you screw up things like other plcs.
 
The Modicon Software 984 LL Manualy shows a table like the following:

0x Word 0001
.
.
0x+n
1x
.
.
1x+n
3x
.
.
3x+n
.
.
4x
.
.
4x+n
coil history
.
.
.
.
Discrete Disable Word 2048

To me this shows that the coil history and the discrete disable table are in the same 2048 words of state RAM. So I am trying to figure out if there are 2040 words of registers defined, does the history and discrete table overlap and cause conflicts.

The documentaion is very confusing regarding this.

 

Similar Topics

Can someone tell me what state the outputs are in when a stop command is issued to a Modicon 584. Do they remain in their last state or do they...
Replies
9
Views
2,903
Hello All, Was hoping I could get a little help with Modicon ladder logic. This is the first time I have seen Modicon logic and currently trying...
Replies
6
Views
257
I have a 170AAO92100 card that I am interested in using as a 10 volt output. Is there setup that I have to do in order to change output or simply...
Replies
0
Views
86
Hi, Seeking consultation on an implementation matter, and have a question about Modicon Compact 984 communication through RS485: Three Modicon...
Replies
4
Views
211
After updating a panel, I inherited another PLC for my "learning lab". It's a Modicon TSX Micro. I've not worked with a Modicon PLC yet, so I...
Replies
1
Views
129
Back
Top Bottom