Technical Support Notes
| Article ID: | T23 |
| Date: | 4/23/99 |
| Product: | SPEL for Windows 1.x and 2.x |
| OS: | Windows NT 4.0, Windows 98, Windows 95, Windows 3.1 |
| Problem: | Increasing memory for variables and object code in the SRC-3xx controller. |
Symptoms
After adding the expanded memory option for the
SRC-3xx controller, errors occur when running programs, indicating that there
is still not enough memory. One possible error is 84, indicating that the
object file cannot be loaded into memory. With SPEL for Windows 1.x versions,
communications timeouts can occur while sending a program during project
build.
| Causes | |
|
Remedies
MPU DIP Switch 2-2
First of all, check that DIP switch 2-2 on the MPU
board is turned on. This gives approximately 100 KB more memory for OBJ space
and still leaves 900 KB memory for file space.
PRGSIZE
Since all
programs are created in the SPEL for Windows environment on the PC and then
downloaded to the controller during project build, the memory space for
creating programs directly on the controller can be reduced to increase memory
for variables and the current object file. This memory area is known as the OBJ
space. You can check the current OBJ space by using the FREE command from the
monitor window.
Use PRGSIZE from the monitor window to set the number of bytes for the program area. The size you should use depends on whether you are using 1.x (16 bit) or 2.x (32 bit) versions of SPEL for Windows.
With SPEL for Windows 1.x versions, PRGSIZE needs to be large enough to send programs to the controller. Communications timeouts can occur if PRGSIZE is too small. PRGSIZE should be set to a value that is greater than the size of the largest PRG file in the project.
With SPEL for Windows 2.x versions, set the size to 5000. This smaller area is currently needed for creating the variable library during project build. In rare cases where the variable library has a very large number of variables, you may need to use a value larger than 5000. Error 2 will occur during project build library creation if PRGSIZE is too small.
Here is an example session from the monitor window showing the increase in OBJ space after setting PRGSIZE to 5000.
Status
This is not a bug but rather a how to bulletin. No
fix required.
