Experimental Physics and
Industrial Control System

We are having a problem when $(top) is redefined recursively for a subschematic.

What happens is that links between records in the subschematic get $(top) expanded 3 times instead of only once.

Here's a simple set of schematics/symbols to illustrate:

topschematic.sch:
--------
[schematic2]

uniq 1
[tools]
[detail]
[cell use]
use subschematic 0 0 100 0 subschematic#1
xform 0 128 96
[comments]

subschematic.sch:
--------
[schematic2]
uniq 2
[tools]
[detail]
w 258 74 -100 0 n#1 estringinval.si.FLNK 256 64 336 64 336 176 464 176 eaos.ao.SLNK
[cell use]
use estringinval 146 -32 100 0 si
xform 0 128 48
p 62 -32 100 0 -1 PV:$(top)
use eaos 607 81 100 0 ao
xform 0 592 176
p 523 81 100 0 -1 PV:$(top)
[comments]

subschematic.sym:
--------
[symbol2]
bbox -288 -40 -32 152
uniq 27
[tools]
[attributes]
p -271 -19 100 0 -1 set0:top $(top)subschematic:
[layers]
<symbol>
l 100 0 0 -232 72 SUBSCHEMATIC
r 0 -288 -40 -32 152
[comments]

The database that's generated by TDCT:

(look at the FLNK field of the first record)
--------

#= database generated by tdct V2.14.4
#= (mode: Capfast compatibility)
record(stringin,"$(top)subschematic:si") {
    field(DESC,"string input record")
    field(SCAN,"Passive")
    field(PINI,"NO")
    field(PHAS,"0")
    field(EVNT,"0")
    field(DTYP,"Soft Channel")
    field(DISV,"1")
    field(SDIS,"0.000000000000000e+00")
    field(DISS,"NO_ALARM")
    field(PRIO,"LOW")
    field(FLNK,"$(top)subschematic:subschematic:subschematic:ao.VAL")
    field(VAL,"string")
    field(INP,"0.000000000000000e+00")
    field(SIOL,"0.000000000000000e+00")
    field(SIML,"0.000000000000000e+00")
    field(SIMS,"NO_ALARM")
}
record(ao,"$(top)subschematic:ao") {
    field(DESC,"analog output record")
    field(SCAN,"Passive")
    field(PINI,"NO")
    field(PHAS,"0")
    field(EVNT,"0")
    field(DTYP,"Soft Channel")
    field(DISV,"1")
    field(SDIS,"0.000000000000000e+00")
    field(DISS,"NO_ALARM")
    field(PRIO,"LOW")
    field(FLNK,"0.000000000000000e+00")
    field(OUT,"0.000000000000000e+00")
    field(OROC,"0.0000000e+00")
    field(DOL,"0.000000000000000e+00")
    field(OMSL,"supervisory")
    field(OIF,"Full")
    field(PREC,"0")
    field(LINR,"NO CONVERSION")
    field(EGUF,"0.0000000e+00")
    field(EGUL,"0.0000000e+00")
    field(EGU,"volts")
    field(DRVH,"0.0000000e+00")
    field(DRVL,"0.0000000e+00")
    field(HOPR,"0.0000000e+00")
    field(LOPR,"0.0000000e+00")
    field(HIHI,"0.0000000e+00")
    field(LOLO,"0.0000000e+00")
    field(HIGH,"0.0000000e+00")
    field(LOW,"0.0000000e+00")
    field(HHSV,"NO_ALARM")
    field(LLSV,"NO_ALARM")
    field(HSV,"NO_ALARM")
    field(LSV,"NO_ALARM")
    field(HYST,"0.000000000000000e+00")
    field(ADEL,"0.000000000000000e+00")
    field(MDEL,"0.000000000000000e+00")
    field(SIOL,"0.000000000000000e+00")
    field(SIML,"0.000000000000000e+00")
    field(SIMS,"NO_ALARM")
    field(IVOA,"Continue normally")
    field(IVOV,"0.000000000000000e+00")
}

Is there a newer version of TDCT which fixes this?

Or might we have something configured wrong?

Thanks,

--

Mike Westfall

Control Systems Software Engineer

Navigate by Date:

Prev: Re: Asyn 4-30 Problem on Arm processor Jörn Dreyer

Next: Vxworks nfs write error? Lawson, Gregory S.

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017>  2018  2019  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: RE: AreaDetector / ADURL queries Mark Rivers

Next: Vxworks nfs write error? Lawson, Gregory S.

Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017>  2018  2019  2020  2021  2022  2023  2024