C-More Micro Message Databases support up to 255 messages per project. If a project appears unable to use the full capacity, first confirm that the limit is the actual issue rather than a mismatch between the project’s message count and the message being displayed.
Check the project’s message count against the 255-message limit
Read the number of messages included in the project’s Message Database. The stated capacity is up to 255 messages; it is a maximum, not a requirement to populate all 255 entries.
- Count is below 255: The stated database limit does not explain a message failing to appear. Continue by checking whether the project is selecting or referencing the intended message.
- Count is 255: The database is at its stated capacity. If another message must be added, identify an existing entry that can be removed or replaced before editing.
- Count is above 255: The project exceeds the stated capacity. Reduce the database to no more than 255 messages, then retest.
Use the project’s own message count as the first decision point. Do not infer that a display problem means the database has reached its limit.
Check whether the symptom is actually a capacity problem
Record the observed symptom and the message the project is expected to show. Compare that expectation with the database entry and the project’s current message count. A message that is absent or incorrect when the count is below 255 calls for a reference or project-logic check, not deletion of unrelated messages.
If the symptom began after adding entries and the count reached 255, treat capacity as a plausible branch: the panel’s published maximum has been reached. If the count remains below 255, keep the entries and inspect how the project identifies the intended message. The capacity figure alone does not identify a bad reference or explain display behavior.
Check the entry and its selection path
For a project below the limit, inspect the expected message entry and the part of the project that selects it. Confirm that the intended entry is present and that the project’s selection logic points to that entry. If the entry is missing, restore or add the required message only if the resulting total stays within 255.
If the entry exists but the display still shows something else, follow the selection path through the project rather than deleting database content. Verify the result with the normal operating condition that requests the message. If the selection path is unclear or the project’s count cannot be established, preserve the working project and stop making speculative edits.
Free capacity without losing required messages
When the count is 255 and the project needs an additional message, the resolving branch is to make room while staying at or below the limit. Decide which current entry is obsolete or can be replaced before changing the database. Do not remove an entry merely because it seems unused; first confirm that the project no longer requires it.
- Save a recoverable copy of the current project using the site’s normal project-control method.
- Identify the message entry to remove or replace, and check that its function is not still required by the project.
- Remove or replace that entry, then confirm that the resulting database contains no more than 255 messages.
- Add the required message if replacing an entry did not already do so.
- Retest the project condition that selects the changed message and any operating conditions that previously used the removed or replaced entry.
This is a capacity correction, not a remedy for a wrong selection reference. If the project is under the limit, freeing space does not address the cause.
Verify the corrected database before returning it to service
After editing, check the database count again and confirm it is no greater than 255. Then trigger the intended message through its normal project selection path and confirm that the expected text appears. If an entry was removed or replaced, also test the project conditions that depended on it.
If the count is within capacity but the expected message still does not appear, return to the selection-path check rather than repeatedly changing database entries. Preserve the known-good project copy so the edit can be reversed if the change causes another message to fail.
FAQ
How many messages can a C-More Micro database contain?
A C-More Micro project’s Message Database supports up to 255 messages.
Can I add more than 255 messages to one project?
No. The stated maximum is 255. Remove or replace an entry before adding another message when the database is already at capacity.
Does a missing message mean the database is full?
Not by itself. Check the project’s message count; below 255, inspect whether the intended entry exists and whether the project selects it.
Can I delete a message to make room?
Only after confirming the project no longer needs that entry. Save a recoverable project copy, make the change, verify the count remains at or below 255, and test affected message selections. Stop and contact AutomationDirect official support if you cannot establish the count, selection path, or impact of removing an entry; provide the project and the observed symptom.