Stats

  • Locked Locked
  • Replies 10
  • Subscribers 166
  • Views 19351
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Altium to OrCAD 17.2 Translation Issues

EASiA

Hello all,

I have an issue for which I cannot find a solution.

I have translated an Altium schematic using File->Import->Altium Schematic Translator. Under the dialog box, there is a help file that explains what needs to be done in both Altium and OrCAD. I saved the files as the Advanced Schematic ascii (*.SchDoc) as directed. There is a PCB Project file (*.PrjPCB) and a valid structure file (*.PrjPCBStructure). I converted all of the Altium schematic pages to custom so the page sizes will be correct. Almost everything translated properly except the few things that is indicated that it cannot understand such as the signal harness where the signals are combined into one fancy line. That is not an issue for me at the moment. The main issue I have is the non-aliased nets reverted to an OrCAD default naming style, something like N00027 from say Q6_1. This is not necessarily a problem either. I know that OrCAD capture cannot change the names of the nets back to the Altium style.

The problem that I know I will have is when I try to link the PCB to the schematic. I know that I will have to re-run the Tools->Create Netlist... to recreate the netlists. This will be the problem. When I translated the Altium PCB to OrCAD, I followed the same instructions that were found Import->Translators->Altium PCB.... The help file under that dialog box explains that you need to save the PCBs as a PCB ASCII File (*.PcbDoc). I checked the Create Individual Symbol Definitions and Derive Connectivity check boxes as well as the Extended radio button. The board was completely translated. All of the traces/nets were translated as they are on the Altium PCB.

The issue that I have is the translated PCB nets do not match because none of the non-aliased nets changed into a default net like in the schematic. So the question is, how do I change the PCB to make the traces/nets conform to the schematic net naming so I can recreate the netlists?

Any help would be greatly appreciated.

  • Hi,

    As long as the PCB connections are the same as the netlist connections, it shouldn't be a problem, and the PCB will update to the new netnames. So if your PCB was N00001 and the new netlist called it CLKOUT (or whatever), as long as the connections (pin to pin to pin, AND!!!! the same reference designators) it will simply re-assign the net to the new netlist.

    Are you trying to do this conversion all at once (convert the schematic, pcb layout, and converge), or did you translate each on separately and then try to import the new netlist? I ALWAYS do things separately (just my mode).

    Regards.

  • in reply to CadAce2K
    CadAce2K said:
    Are you trying to do this conversion all at once (convert the schematic, pcb layout, and converge), or did you translate each on separately and then try to import the new netlist? I ALWAYS do things separately (just my mode).

    I have not actually tried to make a new netlist yet as I have not finished fixing the schematic. I assumed that when I made the netlist and imported it into the PCB that it would cause conflicts based on the nets being different.

    I also did everything separately, first the schematic and then the PCB. I have to say, the PCB translated perfectly other than a couple of silk images that did not convert.

    I will make the necessary changes to the schematic and then I will report back on whether I had success or not. Thanks for the information. Smiley

  • in reply to EASiA

    Yep. As long as your net connectons are the same, and your reference designators are the same, it should import clean (or close). We change net names all the time and it simply renames the nets in the layout. (I add a bunch more net information once I get going along so it's easier to follow in design reviews). Good luck. Be interested in seeing your successes.

  • Save them as ASCII.  Don't save the files as "Advanced Schematic binary "

     

  • in reply to RFinley

    Hi RFinley,

    I meant to type the Advanced Schematic ascii (*.SchDoc). Thank you for the advice though. I will correct the main post.

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.