Advant Controller 110*2.0, AdvaSoft for Windows reports “AC 110 has no more resources”
A description of this resolution:
- Upgrade to AC 110*2.1.
To upgrade from AC 110*2.0 to AC110*2.1, the following issues need to be considered:
Application programs can be transferred by means of AMPL source code.
Addressing of I/O modules
Please note that the addressing scheme for S600 I/O modules has been changed:
In AC110 2.0 the value of the STATION terminal of module DB elements reflected the number of the S600 I/O station, with Base Station = 0 and I/O Stations ranging from 1 to 7.
In AC110 2.1 the value of STATION terminal means the AF100 station number of the module in case of S800 distributed I/O. For the AC110 base station itself and all of its local I/O stations, the STATION terminal is always set to 0.
The I/O station number is coded into the value for the POSITION terminal as follows:
POSITION = I/O_station_number * 100 + module_position
a module in the base station at position 9 has POSITION = 0 * 100 + 9 = 9
a module in I/O station 3 at position 9 has POSITION = 3 * 100 + 9 = 309
To upgrade values of STATION and POSITION from AC110 2.0 to AC110 2.1 in source code files, use the UPGRADR.EXE program delivered with the AdvaBuild Function Chart Builder.
The DB element CI626 now has 2 more terminals, BUSNO and STNNO.
BUSNO specifies which number the AF110 has in this station (in AC 110*2.0, this is the number entered in the Application Builder).
STNNO specifies the address of the AC110 station on that AF100 (in AC110*2.0, this is the address entered in the Application Builder).
Each DSP must be configured with the number of the AF100 on which it resides. This must be the same number as it is specified at the DB terminal BUSNO of the corresponding DB element CI626 or CI627.
Please note that for DSP elements that have the ACT terminal set to 0, all other terminals must be set up correctly. Otherwise the application cannot be translated.
The addressing scheme for the built-in Modbus protocol (OPT4 SW) is changed. Only PARDAT elements may be used for Modbus data exchange. The COLA file can no longer be used to calculate Modbus addresses.
Modbus addresses are specified as follows:
Bit addresses: ADDR = Mbase + n ( 32) - m
Integer addresses: ADDR = Mbase + (n-1) ( 2 + m )
Where ADDR is the Modbus address
n is the item designation of the PAM element
(example: n = 3 for PA3)
m is the offset in the PAM element, starting with 0
(example: m = 8 for bit number 9 in a PAM(B))
Mbase is the Modbus base address for the used data type
0001: input status
1001: output status
3001: input register
4001: output register
The figures are valid for the small Modbus address model only.
Event Set identities
Event set identities may not exceed 65000 in AC110*2.1
[ref SR8004 VASMASOITA0354 ]
"Advant Controller 110*2.0, AdvaSoft for Windows reports “AC 110 has no more resources”" resolves the following:
- Advant Controller 110*2.0, AdvaSoft for Windows reports “AC 110 has no more resources”
AdvaSoft for Windows reports “AC 110 has no more resources”.
This can happen if commands are sent to AC 110 too fast. The frequency that is “too fast” depends on the system load. That means, the higher the system load, the greater is the possiblity that the problem occurs.
The handler task in the AC 110 overrun and comes into a locked state. This state is left only when the processor module is initialized.
AC 110 2.0
AC 110 BASE SW*2.0/x
where x = 0, 1, 2, 3, 4, 5
Insert the URL that your highlighted text will link to.
Copy the video's "embed" tag into Embedded Video below.