Can anyone please explain to me why...
I can happily get values out of DESCAnn - DESCEnn into a 'PLC I/O Component Connection' report,
whereas in a 'From / To' report, although the I/O block & its wiring are still there,
along with the column titles for the DESCAnn - DESCEnn fields - there are now no values in these five fields
Also, why do AE attribute names come out as something different in the available fields list for a given report type - e.g. TERMDESCnn suddenly becomes PD1 or PD2, depending on which end of the wire it's at. Does this 'feature' actually have any useful purpose ? More to the point, is there some sort of mapping list somewhere ?
All suggestions gratefully received
Keith H
Hi Keith,
For your last question, you can look under HELP contents in Reports>Generate reports>
There shows a list of available fields to select:
Available Fields
WIRENO
Wire number
LOC1
"From" device's location code (must end with "1")
CMP1
"From" device's component tag ID (must end with "1")
PIN1
"From" device's wire connection terminal number (must end with "1")
LOC2
"To" device's location code (must end with "2")
CMP2
"To" device's component tag ID (must end with "2")
PIN2
"To" device's wire connection terminal number (must end with "2")
WLAY1
Wire layer "From" device (must end with "1")
WLAY2
Wire layer "To" device (must end with "2")
REF1
Line or grid reference location for "From" device (must end with "1")
REF2
Line or grid reference location for "To" device (must end with "2")
SH1
Sheet assignment for "From" device (must end with "1")
SH2
Sheet assignment for "To" device (must end with "2")
CBL
Cable tag
CBLWC
Cable wire or cable core color
CBLLOC
Cable location attribute value
CBLMFG
Cable manufacturer attribute value
CBLCAT
Cable catalog part number
CBLASMB
Cable ASSYCODE assignment
DESC1CBL-DESC3CBL
Cable description attribute values 1 - 3
CBLP1C2
Cable parent or child (parent = 1, child = 2)
CMP:PIN1
"From" device's component tag and component terminal pin number
CMP:PIN2
"To" device's component tag and component terminal pin number
SEC1
"From" device's drawing section assignment (must end with "1")
SUB1
"From" device's drawing sub-section assignment (must end with "1")
SEC2
"To" device's drawing section assignment (must end with "2")
SUB2
"To" device's drawing sub-section assignment (must end with "2")
INST1
"From" device's installation code (must end with "1")
INST2
"To" device's installation code (must end with "2")
IECCMP1
"From" device's IEC tag name (must end with "1")
IECCMP2
"To" device's IEC tag name (must end with "2")
PD1
"From" device's wire connection TERMDESC value (must end with "1")
PD2
"To" device's wire connection TERMDESC value (must end with "2")
SEQ1
"From" device's wire connection sequence value (must end with "1")
SEQ2
"To" device's wire connection sequence value (must end with "2")
PNLWDLEV1
"From" device's panel equivalent panel (WDLEV) value (must end with "1")
PNLWDLEV2
"To" device's panel equivalent panel (WDLEV) value (must end with "2")
CMPHDL1
"From" device's entity handle value (must end with "1")
CMPHDL2
"To" device's entity handle value (must end with "2")
DWGIX1
"From" device's drawing DWGIX value as listed in FILETIME table of project scratch database (must end with "1")
DWGIX2
"To" device's drawing DWGIX value as listed in FILETIME table of project scratch database (must end with "2")
DWGNAM1
"From" device's drawing %D value (must end with "1")
DWGNAM2
"To" device's drawing %D value (must end with "2")
CBLHDL
Cable entity's handle value
CBLINST
Cable entity's installation attribute value
CBLDWGIX
Cable's drawing DWGIX value as listed in FILETIME table of project scratch database
WIREHDL1
"From" device's connected wire line entity handle value (must end with "1")
WIREHDL2
"To" device's connected wire line entity handle value (must end with "2")
XDIR1
"From" device's wire connection point direction - i.e. 4 = connects from left (must end with "1")
XDIR2
"To" device's wire connection point direction - i.e. 2 = connects from above (must end with "2")
PNLX1
"From" wire connection's physical X-coordinate value (must end with "1")
PNLY1
"From" wire connection's physical Y-coordinate value (must end with "1")
PNLZ1
"From" wire connection's physical Z-coordinate value (must end with "1")
PNLXDIR1
Panel wire "From" connection point's direction - i.e. 4 = connects from left, 1 = right, 2 = above, 8 = below (must end with "1")
PNLX2
"To" wire connection's physical X-coordinate value (must end with "2")
PNLY2
"To" wire connection's physical Y-coordinate value (must end with "2")
PNLZ2
"To" wire connection's physical Z-coordinate value (must end with "2")
PNLXDIR2
Panel wire "To" connection point's direction - i.e. 4 = connects from left, 1 = right, 2 = above, 8 = below (must end with "2")
CLEN
Panel layout calculated wire length
USER1_1 to USER20_1
"From" device's optional user field
USER1_2 to USER20_2
"To" device's optional user field
Thanks for that - got this one already. The 'mapping' question applies more to attributes not covered - especially those which change name dependent on destination, e.g. DESCAnn comes out as DESCAnn in one type of report & PLCDESCAnn in another.
Our basic problem revolves around a wish to get certain attributes out in other report types. We need some 'device terminal-related' attributes in non-PLC symbols, in addition to the normal TERMDESCnn. DESCAnn - DESCEnn would fit the bill nicely, if they weren't apparently restricted to only working in PLCIO symbols and only passing on values in PLC-related reports.
Keith H
lionSG,
Any idea if the CLEN field can be added into the Cable Markers components so the user can enter the length when the cable marker and part information is added?
Thanks.
Not sure if that is possible without customization such as adding a new length attribute to the cable marker.
But you can add the CLEN calculated length field in some schematic reports and and use edit mode to enter the lengths values which I think is not what you are looking for.