I joined your two posts because they appear to be asking the same thing. Note that the Spectre model for a level 3 MOS is "mos3" (see "spectre -h mos3") Andrew
↧
Forum Post: RE: Issue with Level=3 MOS model in Spectre
↧
Forum Post: RE: Spectre error: parameter range violation
I'm not sure if this is possible (I didn't find a way from a quick check). Please contact customer support (submit a support case after logging in). Andrew
↧
↧
Forum Post: WARNING(SPMHNI-297): Component instance property overwrite detected
I am getting this following error " WARNING(SPMHNI-297): Component instance property overwrite detected " after importing the netlist to the PCB layout. After importing the netlist, all the components are getting unplaced. Does anyone know why this is occurring, if yes can anyone send me the solution for the above.
↧
Forum Post: RE: Need Help Exporting ODB++ from OrCAD 16.2 Layout – GW2ODB Executable or Alternatives?
Hi Robert, The latest legacy version we're entitled to use is 16.2. However, we also have licenses from 17.4 up to 24.1. One of the first ideas I had was to try converting to a newer version, and I did try using the "Translator" tool in both 17.4 and 22.1 under "OrCAD Layout...". But since we work in millimeters and use precision up to four decimal places, the resulting design had many nets that weren’t properly connected — not to mention severe issues with shapes. You just can't expect to convert a .MAX file and get a clean .BRD file. There are also netlist issues due to formatting differences: characters like . and / aren’t allowed, which adds even more complications. At this point, I haven’t found an effective way to generate ODB++ files that include both trace and netlist information. Given all these limitations, I decided to abandon that conversion path.
↧
Forum Post: RE: Need Help Exporting ODB++ from OrCAD 16.2 Layout – GW2ODB Executable or Alternatives?
I strongly suspect any license that runs 17.4 and above also runs 16. 6 and below. 16.6 needs windows 10. 16.3 doesn’t run on windows 10(a requirement to get translator help from MGC.) I have 16.2 squirreled away somewhere just in case. Just think 16.2 to 16.6 should be easy. Currently using the same odb plugin from 16.6 to current release. to read 16.x after 22.1 we have to use DBdoctor.
↧
↧
Forum Post: RE: Need Help Exporting ODB++ from OrCAD 16.2 Layout – GW2ODB Executable or Alternatives?
Thanks for the insights. The main issue on my side is that the starting file is a .MAX file. Do you happen to know if .MAX files are still supported in version 16.6? I also keep version 16.2 always ready and operational on an XP VM, just in case.
↧
Forum Post: RE: How to get pin position and location?
KD202502275710 whish part you didn't understand?
↧
Forum Post: RE: Optimization on Fine/turbo
You can go through the Fine/Design3D tutorial, specifically Tutorial 1: "AXIAL COMPRESSOR ROTOR37." This tutorial provides more information on how to perform optimization.
↧
Forum Post: CDF: Not able to modify the choices of Cyclic type cdf for a specific instance of the PCell
Hi Team, I am creating a PCell, which has a cyclic type cdf. There's a requirement based on some other cdf parameter, I need to modify the cyclic cdf choice dynamically. I have written a call-back for that. But the problem is, when I change the choice in one instance, it gets updated in rest of the instances of the PCell. I read a similar discussion in the forum (sorry for creating a duplicate), but the post discussed only on the work around rather than why it actually happens. Usually, when the choices can be changed dynamically, the change must be applied only to a particular instance (for which I am changing the cdf) and not to other instances of the same PCell. If we take the case of changing the cdf values, it's being changed only to the particular instance (not all). Likewise, it should happen with cyclic cdf choices, but it didn't. Could any one please let me know why it's not happening? Thanks, Naveen
↧
↧
Forum Post: RE: CDF: Modifying the cyclic type cdf choices for a specific instance of the PCell changes the choices for all the instances
Naveen, When you update the CDF, you're actually updating the effective cell CDF. This is shared amongst all instances using that cell - and as you perform edit properties or create instance it updates the effective cell CDF with the current instance's values. If you are updating the choices only in the callback, then that will be retained too. The general way to solve this is to also update the choices in the formInitProc for the CDF. That way as each instance is edited, the choices are updated for the settings on that instance (you'd need to also do it in the callbacks so that the choices change as you edit the values on the form). Doing this in the formInitProc means that the choices are updated per instance in the same way that the values are updated in the cell CDF per instance too (that's done by the system). Andrew
↧
Forum Post: RE: Allegro skills
what is "output generator"?
↧
Forum Post: RE: Need Help Exporting ODB++ from OrCAD 16.2 Layout – GW2ODB Executable or Alternatives?
I can confirm that Allegro 16.6 sp 115 >File >import >Orcad Layout Max file. And, it shares the ODB exporter with 24.1
↧
Forum Post: RE: Problem Running dxf2a Command via Skill Form – Invalid Program Arguments
All the data I am attempting to import is mapped to the 'DRAWING FORMAT' class, so the '-p' option fails The -f option appears to work, however nothing is saved to disk:( D:\D:\XXX\YYY>tail allegro.jrl \i (00:01:18) close \i (00:01:20) setwindow pcb \i (00:01:20) open \i (00:01:44) fillin "menu_cancel" \i (00:01:44) generaledit \i (00:03:25) skill '`'axlRunBatchDBProgram("dxf2a" sprintf(nil "dxf2a -$ -u MILS -v MM -a 2 -f MULTIPACK_l.cnv MULTIPACK.dxf %%s" ?reloadDB t ?logfile "dxf2a.log"))`'' \t (00:03:25) Starting dxf2a... (00:03:27) t \i (00:03:32) exit \t (00:03:33) Journal end - Wed May 14 11:16:53 2025 D:\D:\XXX\YYY>cat dxf2a.log Reading Layer Conversion File Reading DXF file... done. Layer conversion file: MULTIPACK_l.cnv DXF file: MULTIPACK.dxf BRD file: D:/D:/XXX/YYY/#Taaaaau00244.dra Update existing design?: NO Use default text?: NO DXF units: MILLIMETERS Design units: MILS Design precision: 2 dxf2a complete. D:\D:\XXX\YYY>dir *dra Volume in drive D is New Volume Volume Serial Number is 902D-8197 Directory of D:\D:\XXX\YYYP 05/05/2025 09:57 AM 201,016 mp.dra 1 File(s) 201,016 bytes 0 Dir(s) 40,886,636,544 bytes free D:\D:\XXX\YYY>dir *log Volume in drive D is New Volume Volume Serial Number is 902D-8197 Directory of D:\XXX\YYY 05/14/2025 11:16 AM 713 downrev.log 05/14/2025 11:16 AM 323 dxf2a.log 2 File(s) 1,036 bytes 0 Dir(s) 40,886,636,544 bytes free Any new suggestions?
↧
↧
Forum Post: RE: Issue with Level=3 MOS model in Spectre
Using Spectre version: Version 15.1.0.803.isr18 64bit -- 21 Jun 2017 The SPICE model I am using is of PSMN8R5-40MSD from the nexperia website It did work after changing B11 to I11 but the MOS characteristics are order of magnitude off. So somehow the model is not being interpreted correctly. Note that I also had to change the E12 definition from TABLE to PWL to make it work.
↧
Forum Post: RE: Issue with Level=3 MOS model in Spectre
It did simulate after I converted the whole model to Spectre but the characteristic of the MOS is very off. My converted model to Spectre looks like this: subckt PSMN8R5_40MSD D G S B * Package impedance LD (D 5) inductor l=20.00p RLD2 (D 5) resistor r=25.13m RLD1 (5 4) resistor r=5.000u LG (G 1) inductor l=1.509n RLG (G 1) resistor r=1.896 LS (S 8) inductor l=440.0p RLS2 (S 8) resistor r=552.9m RLS1 (8 7) resistor r=450.0u * Drain,gate and source resistances RD (3 4) resistor r=5.913m TC1= 6.580m TC2= 1.004n RG (1 2) resistor r=805.9m RS (6 7) resistor r=1.000u RBULK (S B) resistor r=1.000u * Body Diode RBD (9 4) resistor r=1.911m TC1= 4.000m TC2= 23.00u DBD (7 9) D_DBD RDS (7 4) resistor r=40.00M TC1= -5.000m * Internal MOS M1 (3 2 6 6) MINT * Gate leakage and gate capacitance RGS (2 6) resistor r=200.0M CGS (2 6) capacitor c=927.5p * CGD C11 (11 12) capacitor c=1E-12 V11 (11 0) vsource dc=0 type=dc B11 (3 2) bsource I=V(13)*I(V11) E11 (12 0 3 2) vcvs gain=1 E12 13 0 vsource v = table(v(12), -20.0, 287.92, -16.0, 287.86, -15.0, 287.87, -12.0, 287.87, -10.0, 287.85, -8.0, 287.88, -6.0, 287.86, -5.0, 287.87, -4.0, 287.86, -3.0, 287.69, -2.0, 286.80, -1.0, 275.62, -0.5, 236.32, -0.2, 220.97, -0.1, 220.76, 0.0, 200.6204, 0.1, 180.444, 0.2, 180.7272, 0.5, 164.752, 1.0, 142.2876, 2.0, 108.7704, 3.0, 85.0832, 4.0, 67.9872, 5.0, 57.4872, 6.0, 51.7236, 8.0, 47.49, 10.0, 46.824, 12.0, 46.364, 15.0, 45.4972, 16.0, 45.2384, 20.0, 44.1484, 25.0, 43.1592, 30.0, 42.5252, 32.0, 42.3004) * E12 (13 0) TABLE {V(12)} * + (-20.0,287.92) (-16.0,287.86) (-15.0,287.87) (-12.0,287.87) (-10.0,287.84999999999997) (-8.0,287.88) (-6.0,287.86) (-5.0,287.87) (-4.0,287.86) (-3.0,287.69) (-2.0,286.79999999999995) (-1.0,275.61999999999995) (-0.5,236.31999999999996) (-0.2,220.97) (-0.1,220.76) (0.0,200.6204) (0.1,180.444) (0.2,180.72719999999995) (0.5,164.75200000000004) (1.0,142.2876) (2.0,108.7704) (3.0,85.08319999999999) (4.0,67.98720000000002) (5.0,57.4872) (6.0,51.72359999999999) (8.0,47.49) (10.0,46.824) (12.0,46.364000000000004) (15.0,45.4972) (16.0,45.23840000000001) (20.0,44.1484) (25.0,43.1592) (30.0,42.525199999999984) (32.0,42.300399999999996) model MINT mos3 Vto= 4.100 Kp= 167.8 Nfs= 1.062T Eta= 0.000 + Level= 3 Gamma= 0.000 Phi= 600.0m Is= 1.000E-24 UO= 600.0 + Js= 0.000 Pb= 800.0m Cj= 0.000 Cjsw= 0.000 Cgso= 0.000 Cgdo= 0.000 Cgbo= 0.000 + Tox= 100.0n Xj= 0.000 + Vmax= 403.3 model D_DBD diode Bv= 44.00 Ibv= 250.0u Rs= 1.000u Is= 385.9f + N= 1.000 M= 392.5m VJ= 621.9m Fc= 500.0m Cjo= 1.592n Tt= 13.61n ends PSMN8R5_40MSD
↧
Forum Post: RE: Presto Bugs Report
This would be a great feature. I can measure all sorts of things in Altium. All I can measure in Presto are gaps between objects.
↧
Forum Post: RE: Issue with Level=3 MOS model in Spectre
Sorry for the incomplete information. I am using quite an old version of Spectre: Version 15.1.0.803.isr18 64bit After I change it to I11 it does simulate but the MOS characteristic is totally off. The drain current is orders of magnitude lower so it may be something related to the model. The model I am using is this: https://assets.nexperia.com/documents/spice-model/PSMN8R5-40MSD.lib Note however I did have to change the E12 definition from: E12 13 0 TABLE {V(12)} + (-20.0,287.92) ..... to E12 13 0 VCVS PWL(1) 12 0 -20.0,287.92 ..... to make it work.
↧
↧
Forum Post: RE: Issue with Level=3 MOS model in Spectre
I am simulating in an old version of spectre: Version 15.1.0.803.isr18 64bit -- 21 Jun 2017 I am simulating the following model: https://assets.nexperia.com/documents/spice-model/PSMN8R5-40MSD.lib After running it as a Spectre model the MOS characteristic does not look right, i.e. the MOS Ids-Vds characteristic is orders of magnitude different. My translated spectre model is pasted below: subckt PSMN8R5_40MSD D G S B * Package impedance LD (D 5) inductor l=20.00p RLD2 (D 5) resistor r=25.13m RLD1 (5 4) resistor r=5.000u LG (G 1) inductor l=1.509n RLG (G 1) resistor r=1.896 LS (S 8) inductor l=440.0p RLS2 (S 8) resistor r=552.9m RLS1 (8 7) resistor r=450.0u * Drain,gate and source resistances RD (3 4) resistor r=5.913m TC1= 6.580m TC2= 1.004n RG (1 2) resistor r=805.9m RS (6 7) resistor r=1.000u RBULK (S B) resistor r=1.000u * Body Diode RBD (9 4) resistor r=1.911m TC1= 4.000m TC2= 23.00u DBD (7 9) D_DBD RDS (7 4) resistor r=40.00M TC1= -5.000m * Internal MOS M1 (3 2 6 6) MINT * Gate leakage and gate capacitance RGS (2 6) resistor r=200.0M CGS (2 6) capacitor c=927.5p * CGD C11 (11 12) capacitor c=1E-12 V11 (11 0) vsource dc=0 type=dc B11 (3 2) bsource I=V(13)*I(V11) E11 (12 0 3 2) vcvs gain=1 E12 13 0 vsource v = table(v(12), -20.0, 287.92, -16.0, 287.86, -15.0, 287.87, -12.0, 287.87, -10.0, 287.85, -8.0, 287.88, -6.0, 287.86, -5.0, 287.87, -4.0, 287.86, -3.0, 287.69, -2.0, 286.80, -1.0, 275.62, -0.5, 236.32, -0.2, 220.97, -0.1, 220.76, 0.0, 200.6204, 0.1, 180.444, 0.2, 180.7272, 0.5, 164.752, 1.0, 142.2876, 2.0, 108.7704, 3.0, 85.0832, 4.0, 67.9872, 5.0, 57.4872, 6.0, 51.7236, 8.0, 47.49, 10.0, 46.824, 12.0, 46.364, 15.0, 45.4972, 16.0, 45.2384, 20.0, 44.1484, 25.0, 43.1592, 30.0, 42.5252, 32.0, 42.3004) * E12 (13 0) TABLE {V(12)} * + (-20.0,287.92) (-16.0,287.86) (-15.0,287.87) (-12.0,287.87) (-10.0,287.84999999999997) (-8.0,287.88) (-6.0,287.86) (-5.0,287.87) (-4.0,287.86) (-3.0,287.69) (-2.0,286.79999999999995) (-1.0,275.61999999999995) (-0.5,236.31999999999996) (-0.2,220.97) (-0.1,220.76) (0.0,200.6204) (0.1,180.444) (0.2,180.72719999999995) (0.5,164.75200000000004) (1.0,142.2876) (2.0,108.7704) (3.0,85.08319999999999) (4.0,67.98720000000002) (5.0,57.4872) (6.0,51.72359999999999) (8.0,47.49) (10.0,46.824) (12.0,46.364000000000004) (15.0,45.4972) (16.0,45.23840000000001) (20.0,44.1484) (25.0,43.1592) (30.0,42.525199999999984) (32.0,42.300399999999996) model MINT mos3 Vto= 4.100 Kp= 167.8 Nfs= 1.062T Eta= 0.000 + Level= 3 Gamma= 0.000 Phi= 600.0m Is= 1.000E-24 UO= 600.0 + Js= 0.000 Pb= 800.0m Cj= 0.000 Cjsw= 0.000 Cgso= 0.000 Cgdo= 0.000 Cgbo= 0.000 + Tox= 100.0n Xj= 0.000 + Vmax= 403.3 model D_DBD diode Bv= 44.00 Ibv= 250.0u Rs= 1.000u Is= 385.9f + N= 1.000 M= 392.5m VJ= 621.9m Fc= 500.0m Cjo= 1.592n Tt= 13.61n ends PSMN8R5_40MSD
↧
Forum Post: RE: report file
thank u, david, for creating the skill code. unfortunately i do not know how to use it. i created a report file and ran the skill code. it give me an error. maybe i should save it in a different format. regards masa
↧
Forum Post: RE: report file
thank u, david, for creating the skill code. unfortunately i do not know how to use it. i created a report file and ran the skill code. it give me an error as shown below. DataLine = " www.w3.org/.../loose.dtd\">\n" maybe i should save it in a different format. regards masa
↧