I guess it was alrady explained in another thread, but I couldnt find any Search button here, so I will ask again.
I am trying to convert schema from old orcad (.SCH) to new capture (.DSN). All goes well till the end, where it throws error:
*** Translating Page 'H:\TEMP\ELDRCP21.SCH' ***Converting 16-bit schematic 'H:\TEMP\ELDRCP21.SCH' to 32-bit schematic 'C:\USERS\SKOCH\APPDATA\LOCAL\TEMP\ELDRCP21.SCH'...INFO(ORCAP-39064): Conversion complete.Cleaning up 'C:\USERS\SKOCH\APPDATA\LOCAL\TEMP\ELDRCP21.SCH'...WARNING(ORCAP-39027): Cleanup SchematicNon-Orthogonal Wires/Buses found, need to be checked.INFO(ORCAP-39067): Cleanup complete.Could not find H:\TEMP\ELDRCP21.OLBERROR(ORCAP-21096): Cannot find part 'G' at 11.30, 8.90.ERROR(ORCAP-21102): Translation failed.ERROR(ORCAP-21103): Translation Notice.Error(s) encountered. Please check the Session Log.
Where G is not a g-spot but a symbol for GND.
What should I do to get rid of this problem?
Is there some list of those ORCAP messages?
Thanks for any valuable help
I guess that, since you don't have a load of other missing parts reported, you must have an "SDT.CFG" local to the SCHs being converted? It might be possible that you don't actually have that (G) part BUT you are getting a message that an OLB cannot be found so I expect that there is "something" in the graphical libraries that is not appreciated, like "missing vectors" for the parts.
There is a list of the ORCAP messages in the orcadmsgref, doc\orcadmsgref directory of the installation but there is probably not going to be a lot more within that source since the messages are pretty explanatory.
My advice would be to copy everything to a temporary directory on the C drive and translate the data there. Keep the path names to the 8.3 that the DOS tools would have expected. IF you can't correct whatever is preventing the OLB from being found, you are very unlikely to get the DSN file created. IF you have any current product maintenance, there is likely someone at your Cadence Channel Partner who would be familar with translating this old data and related issues.
In reply to oldmouldy: