Problem Signature
After a disk failure removed the original network_130.lib file, replacing it with library version 1.35 caused the project to report the following compiler diagnostic:
Error 3803: Logging (35): Memory for variables exhausted.
Variable 'DLOG_RRD', 11772 bytes| Library | Observed result in the affected project |
|---|---|
network_130.lib version 1.30 |
The project did not produce Error 3803. |
| Version 1.35 | The compiler reported Error 3803 for DLOG_RRD, requiring 11772 bytes. |
Interpret the Evidence Correctly
The result establishes a project-specific difference between versions 1.30 and 1.35. It does not prove that version 1.35 is universally incompatible, because the controller model, target configuration, compiler version, and configured memory limits are not supplied.
The diagnostic identifies variable-memory exhaustion during compilation and names DLOG_RRD as the allocation being processed. Increasing the target memory partition had already been attempted without eliminating the error, but the evidence does not identify which memory field was changed or its value.
Restore the Working Library
- Search project archives and backups for the exact
network_130.libfile previously used by the application. - Remove the substituted version 1.35 reference and restore the recovered version 1.30 reference.
- Compile the project again and check whether Error 3803 and the
DLOG_RRDallocation message disappear. - Retain the recovered library with the project backup so the application can be rebuilt without depending on an unavailable download.
In the documented recovery, restoring version 1.30 from an old backup removed the compiler error.
Verification and Remaining Unknowns
Use a successful compile without Error 3803 as the immediate verification criterion. The evidence does not include a runtime download or functional test, so compile success alone does not establish controller behavior.
No active official download location, release notes, or compatibility matrix is provided. Do not assume that versions 1.30 and 1.35 are drop-in replacements; compare their declarations and memory requirements if migration to 1.35 remains necessary.
FAQ
Why does network library 1.35 cause CODESYS Error 3803?
In the affected project, version 1.35 triggered variable-memory exhaustion while allocating DLOG_RRD, reported as 11772 bytes. The available evidence does not identify the underlying library change or target-specific limit.
How can I clear Error 3803 after replacing network_130.lib?
Restore the exact version 1.30 library from a known project backup, replace the version 1.35 reference, and compile again. That procedure removed the error in the documented case.
Will increasing the CODESYS target memory allocation fix Error 3803?
It did not fix this case, although the changed memory field and values were not recorded. Verify the target settings, but do not treat memory repartitioning as a confirmed substitute for restoring the compatible library.
