You can try to change "total number of channels" from 3 to 1 in Seasim Gui main
window.
SI Lurker
Best Regards
________________________________
From: Filip, Cristian <Cristian_Filip@xxxxxxxxxx>
Sent: Tuesday, July 25, 2017 9:55:00 AM
To: Sanjeev Gupta
Cc: Lurker Li; si-list@xxxxxxxxxxxxx
Subject: RE: [SI-LIST] Re: Seasim - port definition for s4p files
Thanks for suggestion, but this means that Seasim cant handle the s4p file for
victim channel only? Does it work only with s12p s-paramters?
Cristian
From: Sanjeev Gupta [mailto:sanjeev@xxxxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Monday, July 24, 2017 9:50 PM
To: Filip, Cristian
Cc: Lurker Li; si-list@xxxxxxxxxxxxx
Subject: Re: [SI-LIST] Re: Seasim - port definition for s4p files
Better way is to feed step response rather than using s-parameters in seasim.
Since you have only s4p victim channel. Get the step response of victim by
simulation and create zero response aggressor file as per seasim format. Use
all these files in seasim config file as per specified rules. This should
work..
On Jul 25, 2017 7:12 AM, "Filip, Cristian"
<Cristian_Filip@xxxxxxxxxx<mailto:Cristian_Filip@xxxxxxxxxx>> wrote:
I don't want/need to use multiple s4p files, just one for the victim (there are
no aggressors in this channel). And the question is about Seasim not ADS...
Thank you,
Cristian
From: Lurker Li [mailto:Lurker_Li@xxxxxxxxx<mailto:Lurker_Li@xxxxxxxxx>]
Sent: Monday, July 24, 2017 8:24 PM
To: si-list@xxxxxxxxxxxxx<mailto:si-list@xxxxxxxxxxxxx>; Filip, Cristian
Subject: Re: Seasim - port definition for s4p files
Hello,
If no Seasim code, maybe change three s4p to one s12p can fix this issue. ADS
can do it.
SI Lurker
Best Regards
________________________________
From:
si-list-bounce@xxxxxxxxxxxxx<mailto:si-list-bounce@xxxxxxxxxxxxx><mailto:si-list-bounce@xxxxxxxxxxxxx<mailto:si-list-bounce@xxxxxxxxxxxxx>>
<si-list-bounce@xxxxxxxxxxxxx<mailto:si-list-bounce@xxxxxxxxxxxxx><mailto:si-list-bounce@xxxxxxxxxxxxx<mailto:si-list-bounce@xxxxxxxxxxxxx>>>
on behalf of Filip, Cristian
<Cristian_Filip@xxxxxxxxxx<mailto:Cristian_Filip@xxxxxxxxxx><mailto:Cristian_Filip@xxxxxxxxxx<mailto:Cristian_Filip@xxxxxxxxxx>>>
Sent: Tuesday, July 25, 2017 4:48:13 AM
To:
si-list@xxxxxxxxxxxxx<mailto:si-list@xxxxxxxxxxxxx><mailto:si-list@xxxxxxxxxxxxx<mailto:si-list@xxxxxxxxxxxxx>>
Subject: [SI-LIST] Seasim - port definition for s4p files
Hello,
I would appreciate if someone could explain how the port definition works in
Seasim, or at least how the configuration file should look like for an s4p file.
The test_example.sea, which works with s12p s-parameters as input, contains the
following rows:
.
.
.
step_portout (9,10) # Differential Rx port
step_portsin (3,4),(1,2),(5,6) # Differential Tx ports
.
.
.
tstone_ports [\
['0', '', 'Gen3 package model'],\
['1', '1', 's12p_Txpkg_642010_b.s12p', '[1,3,5,7,9,11]', '[2,4,6,8,10,12]'],\
['1', '1', 's12p_pin2pin_642010_b.s12p', '[1,3,5,7,9,11]', '[2,4,6,8,10,12]'],\
['1', '1', 's12p_Rx_pkg_642010_b.s12p', '[1,3,5,7,9,11]', '[2,4,6,8,10,12]'],\
]
.
.
.
After reducing the number of ports of the original s-parameters from 12 to 4, I
modified this file as shown below and re-run the simulation:
.
.
.
step_portout (2,4) # Differential Rx port
step_portsin (1,3) # Differential Tx ports
.
.
.
tstone_ports [\
['0', '', 'Gen3 package model'],\
['1', '1', 's12p_Txpkg_642010_b.s4p', '[1,3]', '[2,4]'],\
['1', '1', 's12p_pin2pin_642010_b.s4p', '[1,3]', '[2,4]'],\
['1', '1', 's12p_Rx_pkg_642010_b.s4p', '[1,3]', '[2,4]'],\
]
.
.
.
Seasim fails simulating and generates the error message: "Unknown port
identifiers: (2, 4) 1". The s4p files have ports 1, 2 and 3, 4 strongly
connected or in other words input ports are 1, 3 and output ports are 2, 4.
Thank you in advance,
Cristian
------------------------------------------------------------------
To unsubscribe from si-list:
si-list-request@xxxxxxxxxxxxx<mailto:si-list-request@xxxxxxxxxxxxx><mailto:si-list-request@xxxxxxxxxxxxx<mailto:si-list-request@xxxxxxxxxxxxx>>
with 'unsubscribe' in the Subject field
or to administer your membership from a web page, go to:
//www.freelists.org/webpage/si-list
For help:
si-list-request@xxxxxxxxxxxxx<mailto:si-list-request@xxxxxxxxxxxxx><mailto:si-list-request@xxxxxxxxxxxxx<mailto:si-list-request@xxxxxxxxxxxxx>>
with 'help' in the Subject field
List forum is accessible at:
http://tech.groups.yahoo.com/group/si-list
List archives are viewable at:
//www.freelists.org/archives/si-list
Old (prior to June 6, 2001) list archives are viewable at:
http://www.qsl.net/wb6tpu
------------------------------------------------------------------
To unsubscribe from si-list:
si-list-request@xxxxxxxxxxxxx<mailto:si-list-request@xxxxxxxxxxxxx> with
'unsubscribe' in the Subject field
or to administer your membership from a web page, go to:
//www.freelists.org/webpage/si-list
For help:
si-list-request@xxxxxxxxxxxxx<mailto:si-list-request@xxxxxxxxxxxxx> with 'help'
in the Subject field
List forum is accessible at:
http://tech.groups.yahoo.com/group/si-list
List archives are viewable at:
//www.freelists.org/archives/si-list
Old (prior to June 6, 2001) list archives are viewable at:
http://www.qsl.net/wb6tpu
------------------------------------------------------------------
To unsubscribe from si-list:
si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field
or to administer your membership from a web page, go to:
//www.freelists.org/webpage/si-list
For help:
si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field
List forum is accessible at:
http://tech.groups.yahoo.com/group/si-list
List archives are viewable at:
//www.freelists.org/archives/si-list
Old (prior to June 6, 2001) list archives are viewable at:
http://www.qsl.net/wb6tpu
