| Applies to:
PcVue version 7.00d and earlier. |
| Summary:
This article specifies limits of connectivity for communications in previous versions of PcVue. |
| Details:
If too many frames are generated in PcVue, a breakdown occurs without any error message. A correction was applied in PcVue version 7.00f. If any parameter’s limit is reached, the following message will appear in the Event Viewer: “CIMWAY, starting communication error: CwReadConfiguration(): 103 Start Cimway: not enough memory (103)” Limits These are the limits in PcVue :
After PcVue 7.00, if you see this error, there is a bad configuration into your COMM.dat file. |
Communication object limits in CimWay for PcVue 16:
In CimWay, there is no hard-coded limit to the number of communication objects. However, this does not mean that there are no constraints. Each communication object consumes memory, so the real limit depends on the capabilities of the machine used.
With version 7.00, the figures achieved were already considerable, highlighting the importance of taking available hardware resources into account when adding communication objects. It is therefore essential to evaluate memory capacity and system performance before increasing the number of objects.
Created on: 22 Oct 2010 Last update: 19 Mar 2025