Error after adding another label

[Darrell]

after adding another label to look at the .acc of a timer I get this error , I'm not sure what it actually means , the page is polling over 75 different addresses and seem to work fine to this point.
I'm assuming this error has something to do with timers , as I look at 15 different presets or accumulated values , have I possibly reached a limit for one SlcMicro driver

Darrell

[Archie]

There is nothing that I can think of that would limit the driver except maybe the older SLC 5/01 and 5/02 which had a limited packet length.

Try this to see what happens:

- Add another driver instance with the sane settings
- On the BasicLabel that caused the problem, change the ComComponent to the new driver instance

[Darrell]

I can add more labels and it,s not a problem only if I use a another timer address , I thought that maybe there is a limit on how many timer addresses can be used to a single driver.
If I add another driver , works fine ,  Micrologix 1400 ,

thanks Darrell

[Archie]

It sounds like there is a problem with the communication optimizer with timers. When you first got the problem, what was the lowest timer address used on the form and what is the address of the timer that created the problem?

[Darrell]

Timers used  In this order - NumericSevenSegment T4:35.ACC
Labels
 T4:35.ACC - T4:35.PRE  - T4:40.ACC - T4:41.ACC  - T4:43.ACC  - T4:44.ACC - T4:45.ACC  - T4:47.ACC  - T4:61.ACC - T4:62.ACC  - T4:64.ACC  - T4:65.ACC - T4:67.ACC  - T4:68.ACC  and then when I added T4:20.ACC I got the error , If I add a second driver it's works ok

[Darrell]

Timers used  In this order - NumericSevenSegment T4:35.ACC
Labels
 T4:35.ACC - T4:35.PRE  - T4:40.ACC - T4:41.ACC  - T4:43.ACC  - T4:44.ACC - T4:45.ACC  - T4:47.ACC  - T4:61.ACC - T4:62.ACC  - T4:64.ACC  - T4:65.ACC - T4:67.ACC  - T4:68.ACC  and then when I added T4:20.ACC I got the error , If I add a second driver it's works ok

aslo seen to get the same error on a working HMI , when I did a download while the HMI was running.

[Archie]

I will check this, but I think what is happening is that it is trying to read T4:20-T4:68 all in one read. with 3 integers for each timer that comes out to 49*3*2=294 bytes in one read, which is probably over the protocol limit.