[PCB_FORUM] swap functions with SPB16.01

Hello All.

 

I have a problem with SPB16.01.

I have a component AD8017 which is defined as a double operational amplifier.

So it's 2 gates.

 

in 15.7, in Allegro it is fully swappable.

In 16.01, it is not:

W- (SPMHA2-23): No functions are swappable with the selected function ... pick 
again.

 

I sent a CCR to Cadence to notify this problem.

I first have an answer of somebody that replied she can reproduce the problem 
and then send it to Cadence R&D.

 

Few weeks later, a PCR is applied in the Hotfix_SPB16.01.008_wint_1of1.exe:

README_PCR.txt:  553514    ALLEGRO_EDITOR   SCHEM_FTB            function 
swapping not working in 16.01 which was working in 15.7.

 

I install the hotfix, the problem was still there.

I check the CCR status, it says : Checked_in

According to status description in CCR status help:

Checked_In (formerly Fixed)

The requested product change has been implemented by the product development 
team and is awaiting internal verification.

 

So I wait that the CCR Status passes to another one such as validated, closed...

 

I received the Sourcelink newsletter and in the bottom I saw this:

1

41122300 
<http://sourcelink.cadence.com/en/ccscase/CaseEdit.jhtml?case=41122300&mode=notification>
 

Closed

C1 553514 : function swapping not working in 16.01 which was working in 15.7

2-Important

2008-04-15

2008-05-12

553514 
<http://sourcelink.cadence.com/en/ccscase/PcrView.jhtml?pcrListId=553514:41122300&mode=notification&SectionTitle=View+CCRs&SRPage=ViewMyPCR>
  

 

The 41122300 link returns this:

https://sourcelink.cadence.com/en/ccscase/CaseEdit.jhtml?case=41122300&mode=notification

where it is said that this is a closed Service Request.

 

But I am still not able to swap!

I tried to package again not better.

 

I cannot swap functions with any swappable component.

 

Anybody else has this with 16.01? I would be surprised if nobody swaps!

 

A guy there went on a Cadence seminar close to here and discussed the problem.

Someone told him that it can be a mouse setup problem....

I am very surprised to hear something like this, but why not...

I am quite sure that it cannot be such stupid thing.... (why Cadence did not 
reply about that in this case?)

 

May I wait more to really see the PCR implemented?

(it is formerly closed somewhere, "checked_in" in my personal information and 
planned to be corrected in 16.1 (in CCR detail) which is not planned at all in 
Cadence Review Schedule!

https://sourcelink.cadence.com/docs/files/lifecycle/Release_Schedule.html)

 

Thanks for any help.

 

William Billereau
CERN group TS / DEM
1211  Genève  23 Suisse


Tel: (+4122) 76 73403 
mail to:  william.billereau@xxxxxxx

Other related posts: