After the project symbol library is replaced with the program’s working library, the four-connection current-transformer symbol becomes available for insertion again. The key distinction is between a symbol that the editor can open and a symbol that the active project can place: those operations may read from different library copies.
Project-library scope
The term program library here means the symbol collection installed with the application. The project library means the symbol collection stored in the project’s simbols folder. The reported condition affects the project copy: the basic symbol editor can open the four-connection current-transformer symbol lsw1-A, while the transformer group does not offer that symbol for insertion.
| Observation | Engineering meaning | Next check |
|---|---|---|
lsw1-A opens in the basic symbol editor |
A readable definition exists in at least one accessible library. | Confirm whether the editor and project use different copies. |
| The transformer group omits the four-connection symbol | The active project library or its group data is incomplete, stale, or internally inconsistent. | Inspect the project’s simbols folder. |
| Repeated reinstallations do not restore the symbol | Reinstalling the application does not necessarily replace project-local data. | Repair the project library directly. |
Check 1: Open lsw1-A in the basic symbol editor. Expect the four-connection current-transformer graphic and its four connection points to be visible. This proves that a usable source definition exists before changing the project.
Library divergence check
A project-local library can diverge from the installed library after a symbol already used by the project is edited, particularly when its connections are changed. Symbol placement depends on more than the drawing: connection definitions and group membership must agree with the project’s stored symbol data. A mismatch can leave the definition editable but prevent it from appearing in the expected insertion group.
- Close any symbol-editing window so it cannot save another copy during diagnosis.
- Locate the active project’s
simbolsfolder. - Locate the corresponding
simbolsfolder used by the program. - Confirm that these are separate locations. Do not treat the visible definition in the editor as proof that the project copy matches it.
Check 2: Compare the two folder locations and their contents. Expect the project folder to be distinct from the program folder; a missing or differing project-side entry provides the repair path. If both locations resolve to the same folder, stop and re-identify which library the active project actually uses before deleting or copying files.
Recoverable project preparation
The working fix replaces all contents of the project’s simbols folder with the contents of the program’s folder. Because this operation removes project-local symbol data, first preserve a recoverable copy. A backup also protects intentionally customized symbols that would otherwise be lost.
- Close the project and, preferably, the application. This prevents open files or cached library data from interfering with the replacement.
- Copy the complete project
simbolsfolder to a backup location outside the folder being repaired. - Record whether the project contains customized symbols. Those definitions may need controlled reintroduction after the standard library works.
- Verify that the program’s source
simbolsfolder contains the definition that opens aslsw1-A.
Check 3: Open the backup location independently. Expect a complete copy of the original project library and a readable lsw1-A definition in the program library. Do not proceed with a partial backup or an unverified source folder.
Project-library replacement
Replace the library as a complete set rather than copying only the visible symbol file. A placement group may depend on related catalog, indexing, connection, or grouping data stored alongside the drawing definition. Mixing selected files from two library states can preserve the inconsistency.
- With the application closed, remove all contents from the active project’s
simbolsfolder. Keep the folder itself if the project expects that directory structure. - Copy all contents from the program’s
simbolsfolder into the now-empty project folder. - Confirm that the copy completed without skipped, locked, or access-denied files.
- Reopen the application and then open the repaired project.
- Navigate to the transformer symbol group and locate the four-connection current-transformer symbol.
Check 4: Expect lsw1-A to appear in the transformer group and be selectable for placement. If the editor can still open it but the group still omits it, verify that the repaired folder belongs to the active project rather than another project or template.
Placement and connection validation
Library visibility alone is not sufficient. The inserted instance must retain all four defined connection points and behave as a project symbol rather than as an unconnected graphic. Test in a disposable drawing area or project copy before changing a production sheet.
- Select
lsw1-Afrom the transformer group. - Insert one instance on a test sheet.
- Confirm that the placed symbol displays the expected current-transformer graphic.
- Inspect or connect each of its four connection points using the normal project workflow.
- Save the project, close it, reopen it, and inspect the same instance again.
Check 5: Expect the symbol to remain present after reopening and all four connections to remain available. A symbol that disappears, loses connections, or returns to the editor-only state indicates that project data is being rewritten from another library location or by an incompatible customized definition.
Recurring repair pitfalls
| Wrong practice | Result | Corrective action |
|---|---|---|
| Repeatedly reinstalling the program | The project-local simbols folder can remain unchanged. |
Replace the project library from the verified program library. |
Copying only lsw1-A
|
Related grouping or connection data may remain mismatched. | Copy the complete library contents as one set. |
| Deleting project symbols without a backup | Customized definitions may be unrecoverable. | Preserve the entire original folder first. |
| Editing connections on an inserted symbol without controlling library scope | The project copy and program copy can diverge. | Determine which library is being edited and validate placement afterward. |
| Checking only the symbol editor | Editability is mistaken for project availability. | Verify group visibility, placement, four connections, save, and reopen. |
Check 6: After any later symbol edit, expect the edited definition to remain visible in its intended group and newly inserted instances to expose the intended connections. If either check fails, restore the backed-up state or repeat the controlled full-library replacement.
FAQ
Can I fix TOP B1 missing symbols by reinstalling?
Not when the fault is in the project’s simbols folder. Repeated reinstalls did not correct this condition; replacing the project library with the program library did.
Does opening lsw1-A prove the project can use it?
No. Opening lsw1-A proves that the editor can read a definition, while insertion depends on the active project library and its transformer-group data.
Can I copy only the missing current-transformer symbol?
Replace the complete contents of the project simbols folder. Copying the library as a set avoids retaining mismatched grouping or connection data.
Does the repair preserve custom project symbols?
Only if they are backed up before replacement and reintroduced carefully afterward. Final verification is to insert lsw1-A, confirm all four connections, save the project, reopen it, and confirm the instance and connections remain intact.