Multisim and Ultiboard

cancel
Showing results for 
Search instead for 
Did you mean: 

wrong pinout after copying a schematic symbol to the database

Hi,

 

I had a very odd problem on a recent board.

A customer made a schematic symbol, which I would use afterwards.

 

So, I copied the symbol in my database and attached it to a 28 pin footprint.

When placing the footprint in the layout all pins were reversed...

 

I have added a Jpg to make thing clear:

U8 is the original schematic symbol made by my customer.

As you can see, it is flipped horizontally in the schematic.

 

When I copy this to my user database, and place it: I get the result as in U2:

-the texts are in the corrct location, but all footprint pins are wrong...

 

Next I flipped the original U8, so it becomes U3.

And next I copied it to my database and placed it back into the schematic: U4

As you can see U4 is exactlty the same as U3.

 

 

Obviously the difference betwee U8 and U2 is a bug.

Also the pin texts are quite messy... but the footprint is the worse

Is this a known issue?

 

By the way, I'm using version 10.0.

 

Johan

 

 

 

0 Kudos
Message 1 of 7
(5,352 Views)

Hello stressed_user,

 

Can you share a design with this custom component in there?

This will allow me to do some tests and perhaps might allow me to find a work-around.

Kind Regards,
Thierry C - CLA, CTA - Senior R&D Engineer (Former Support Engineer) - National Instruments
If someone helped you, let them know. Mark as solved and/or give a kudo. 😉
0 Kudos
Message 2 of 7
(5,339 Views)

This has happened to me in the past, I had to rebuild it from scratch....it seems like an object parsing issue since it reverses the pins as it moves around to in its database. Its been a while, but I do recall see the same behavior.



Signature: Looking for a footprint, component, model? Might be here > http://ni.kittmaster.com
0 Kudos
Message 3 of 7
(5,319 Views)

Hi Thierry,

 

In attachment the file I used to do the tests.

As described, I have found a workaround, but it should not happen in the first place!

 

In the schematic:

U8: the schematic symbol as received, it was flipped horizontally in the schematic.

U2: that flipped part(U8) was added to the data base, and U2 is as it looked when placed.

 

U3: then I copied flipped the original U8 in the schematic: that is U3

This part (U3) was the added to the database and when placed as U4, all was correct.

 

So, I found the workaround, but what should not have happened:

the difference between U8 and U2!

the footprint pin numbers (even without footprint attached to it (black symbol)) have switched from left to right!

while the pins and texts have stayed where they should be..

(and the texts are mesy too)

 

 

Thanks for having a clos look at this...

 

 

 

0 Kudos
Message 4 of 7
(5,314 Views)

Hello Stressed_user,

 

I'm here working with Multisim 12 and saw the following:

- Opening the ms10 schematic gave me the same view as you had (even after saving to ms12).

- Saving U8 to the database an then dropping that component (withouyt any extra flipping)  to the schematic gave me U4.

So it seems like the issue is fixed in Multisim 12.

 

Have you tried it also in version 12?

Kind Regards,
Thierry C - CLA, CTA - Senior R&D Engineer (Former Support Engineer) - National Instruments
If someone helped you, let them know. Mark as solved and/or give a kudo. 😉
0 Kudos
Message 5 of 7
(5,307 Views)

Thierry,

 

Thanks for checking that out.

 

unfortunately, I can' just switch over to v12...

1) I'll have to ask for some budget... (and it's crisis, so there isn't any)

2) the ms12/ms10 schematics are not compatible

The last would mean that both me and my customer would have to upgrade....

 

we only using multisim for its schematics, not for simulation...

It would be great if one could make a schematic in v12 and 'save as ms10....

but that isn't possible I believe....

 

Thanks for the help

 

Johan

 

 

 

 

 

 

 

 

0 Kudos
Message 6 of 7
(5,301 Views)

Hello Johan,

 

One thing that we first could try is check if you and the customer are using both the same version of Multisim v10.

I'm asking this because there were patches for that version that might fix the issue:

http://joule.ni.com/nidu/cds/view/p/id/899/lang/nl

Kind Regards,
Thierry C - CLA, CTA - Senior R&D Engineer (Former Support Engineer) - National Instruments
If someone helped you, let them know. Mark as solved and/or give a kudo. 😉
0 Kudos
Message 7 of 7
(5,297 Views)