Size and number of robot programs
By default, there are 20 SRL program slots available per robot that can be used freely. The size of these 20 programs cannot be adjusted. These 20 programs are sufficient for common handling and simple processing applications. Programs 1-20, for example, can contain 166 typical program lines consisting of a LIN command and 4 coordinates.
In addition, the entire RAM of the MOVI-C® CONTROLLER (minus the memory used by the software module, axes, and user codes) can be used for SRL programs. The memory can be used for a few very large programs, or numerous additional small programs can be created. For more information, refer to chapter Large G-code files.
INFORMATION
To determine the available memory on the MOVI-C® CONTROLLER, the memory usage of the MOVI-C® CONTROLLER can be read in the IEC Editor after the code has been created.
MOVI-C® CONTROLLER UHX25A/45A/85A (64 MB RAM):
Minus the memory used by the software module, the axes, and by any user code, a maximum of approx. 58 MB is available for additional SRL programs, e.g. one program requiring 50 MB, or two programs each requiring 25 MB, etc.
When using typical program lines consisting of a LIN command and 4 coordinates, the program could thus have approx. 1 million lines. In comparison: Programs 1-20 can each contain 166 typical program lines consisting of a LIN command and 4 coordinates.
MOVI-C® CONTROLLER UHX65A (96 MB RAM):
Minus the memory used by the software module, the axes, and by any user code, a maximum of approx. 90 MB is available for additional SRL programs, e.g. one program requiring 80 MB, or two programs each requiring 40 MB, etc.
When using typical program lines consisting of a LIN command and 4 coordinates, the program could then have approx. 1.7 million lines.
MOVI-C® CONTROLLER UHX86A (256 MB RAM):
The same limit as for the MOVI-C® CONTROLLER UHX65A (max. 90 MB) currently applies.
Significance for the size of the G-code to be imported
It is not possible to establish a direct relationship between the size of a G-code file to be imported and the size of the SRL program that is generated by the import. This is because G-code programs and SRL programs are stored differently: A G-code program is a readable text file, while the SRL program is stored in the form of variables (image file).
The following aspects influence the relationship between the size of the G-code file and the size of the resulting SRL program:
- Type of commands contained in the G-code
- Number of decimal places in the G-code
- Use of "G1" at the start of each line
- Are all coordinates in each line or are coordinates retained modally?
- Number of comments
The following table shows examples of program size:
| Size of | Size of SRL | Ratio of |
|---|---|---|---|
"N10 G1 X100 Y2000 Z30" | 21 bytes | 40 bytes | ~2 |
"N10 G1 X100.111 Y2000.222 Z30.333" | 33 bytes | 40 bytes | ~1.2 |
"X1000.11" | 8 bytes | 16 bytes | 2 |
"M4" | 2 bytes | 16 bytes (mapped as call function) 56 bytes (mapped as path event + call function) | 8 28 |
"N360 G2 X566.4883739999999 Y916.4174720000000 I-42.9742430000000 J4899.8115229999994 F=VG_2 $AC_PATHACC=AG_2 $AC_PATHDEC=DG_2" | 125 bytes | 112 bytes | ~0.9 |
";this is a comment" | 18 bytes | 0 bytes | Comments are not counted as part of the program memory in the SRL |
In typical real G-code programs, the ratio of "SRL to G-code" is between 0.9 and 1.5. The exact required size of the SRL program is output at the end of the G-code import. This can also be performed offline (without a MOVI-C® CONTROLLER).
