Pulsonix User Forum

Technical advice from Pulsonix engineers and the wider community.

 All Forums
 Help with using Pulsonix
 Schematic Design
 Component naming in hierarchical designs

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Format Mode:
Format: BoldItalicizedUnderlineStrikethrough Align LeftCenteredAlign Right Horizontal Rule Insert HyperlinkInsert EmailInsert Image Insert CodeInsert QuoteInsert List

* Forum Code is ON

   Upload a file

Check here to subscribe to this topic.

T O P I C    R E V I E W
Manfred Posted - 18 Jan 2018 : 10:25:05

I'm transferring a hierarchical design from Eagle to Pulsonix.
Eagle used a hierarchical naming system for the parts e.g. input.type1.R27.
Pulsonix uses a flat naming system e.g all resistors are just named Rx.

Is there a way to tell Pulsonix to use a hierarchical naming system ?

Personally I find the flat system better, but to rename all components would require a load of changes in the documentation.

Many thanks

2   L A T E S T    R E P L I E S    (Newest First)
Manfred Posted - 19 Jan 2018 : 06:07:18

a big part of the PCB has to be routed new. Therefore I decided to transfer the schematic manually, draw it new in Pulsonix to get a clean start without the Eagle inheritance.

The problem is the naming of the parts there is a big and complicated documentation for every part, so the names must stay the same in the Pulsonix schematic.
steve Posted - 18 Jan 2018 : 11:18:35
We would be interested to understand how these hierarchical references appear in the Eagle PCB.

We work our importer on what we learn about the originating systems output files, as customers highlight aspects of its format.

What is happening during/after import of your files into Pulsonix?

Can you provide the files for import to us?

You are correct in that Pulsonix uses a flat naming system.

Pulsonix Assistance