why schematic and viva trace colors mismatched?

If you plot signals (e.g. Outputs->To be Plotted->Select on schematic) then the colors should match. If you use a calculator function (such as VT()), then the colours do not match because it is one step removed - calculator expressions could be a complicated function of multiple signals and so it makes no sense to tie them together.

How are you "loading it into VIVA"?

Andrew

As you mention, I am using  Outputs->To be Plotted->Select on schematic, then selecting the wire which then assumes a colour, Viva then assumes a colour which only coincidentally will be the same as the schematic. 9 times out of 10 it is something else.

Here's an example, the schematic wire is green, the resultant Viva colour is red.

OK, looks like I'll have to file this one with support then?

Dear kenc184,

I attempted to respond to your initial post with an example - only to realize Andrew just responded so I did not! However, one thought came to mind when I inspected the screenshot you included in your second to last post. Inpecting the net name on the ViVA plot suggests it is I0/I2/net19. On your schematic to the left of your viVA plot, the net is clearly not labeled. However, apparently you are probing a net19 two levels of hierarchy from the two - in essence net19 exists in instance I2. If this is correct, is it possible you previously selected thats ma net at an upper level of hierarchy? In otherwords, suppose the net name name signal1 at the schematic level of I0, then the net name net19 at the schematic level I2. Did you previously select net signal1 for probing at schematic level I0 and it was assigned a red color?

Did you elect it as an output to be saved in Explorer or Assembler where it was assigned a color (prior to the simulation)?

Shawn

Hi Shawn,

Something is strange. I pulled up a schematic, cleared all the "output setup" data, ran a sim then plotted two wires and the colors mismatched.

Then I created a new schematic, ran the sim, selected outputs to plot and the colors matched.

Curiouser and curiouser.

kenc184 said:

OK, looks like I'll have to file this one with support then?

Sorry, wasn't able to reply earlier in the week and then was off work for a couple of days with no access to the forums. Yes, that would be a good idea - I'm not aware of any setting that would turn off the matching with probes, so I think we need to see this (to be honest, I didn't have time to do some searching to see whether others have faced this recently). Talking to support makes sense.

Andrew

kenc184 said:

OK, looks like I'll have to file this one with support then?

Sorry, wasn't able to reply earlier in the week and then was off work for a couple of days with no access to the forums. Yes, that would be a good idea - I'm not aware of any setting that would turn off the matching with probes, so I think we need to see this (to be honest, I didn't have time to do some searching to see whether others have faced this recently). Talking to support makes sense.

Andrew

Support tells me that the colours only match for previously selected signals. Any added after simulation will not necessarily match.

I can't imagine that this would be hard to fix?

I agree, this should be fixed. I've just reproduced some behaviour that's wrong even for signals added to the output before simulation, and it's inconsistent between the tran and DC results. I'm sure this used to work but it's broken at some point.

Regards,

Andrew

Support suggested that direct plot gives matching colours. And it's true, except every one is the same colour!

With all the complicated, amazing things the Cadence tool suite does, it is strange that something so seemingly trivial can be so poor.

Andrew, perhaps you could request it being fixed?  I'm sure coming from you it would carry more weight?  I think Support believes they have done their job telling me how it works, I'm not sure that  they are going to request it to be changed.

kenc184 said:

I'm sure coming from you it would carry more weight? 

Whilst I do have some influence, having this associated with a real customer helps even more. Can you let me know the case number? Perhaps I can either take over the case or create a new one on your behalf to file the request.

Thanks,

Andrew

Here you go:

Case# 46623613

I also filed a ticket for the other "issue", I posted on here recently - the lack of a "outputs to be plotted" icon in ADE Explorer. Apparently, this has been logged as an enhancement request.

Enhancement CCR# 2666771

The AE dealing with your case filed CCR 2667707, and I filed another on behalf of a regular on these forums who asked for a duplicate - with that and an internal CCR for the same issue, I've piled on and am pushing for this to be fixed. Fingers crossed!

Andrew