Feature ID turning red while renaming

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Feature ID turning red while renaming

    Hi,
    i'm trying to inspect same linear dimension and found that the feature id is turning into red color while renaming, also when i'm trying to call output for the same it says feature doesn't exists or the feature id in output turns red.
    I have attached the snap of code.
    is anyone else getting the same error or it's just me?

    Capture1.PNG
    Code:
     MOVE/CLEARPLANE
    PNT12.44_1 =FEAT/CONTACT/VECTOR POINT/DEFAULT,POLAR
                THEO/<2.005,6,12.44>,<0,0,1>
                ACTL/<2.005,6,12.44>,<0,0,1>
                TARG/<2.005,6,12.44>,<0,0,1>
                SNAP=YES
                SHOW FEATURE PARAMETERS=NO
                SHOW CONTACT PARAMETERS=YES
                  AVOIDANCE MOVE=NO,DISTANCE=0.3937
                SHOW HITS=NO
                MOVE/CLEARPLANE
    PNT12.44_2 =FEAT/CONTACT/VECTOR POINT/DEFAULT,POLAR
                THEO/<2.005,87,12.44>,<0,0,1>
                ACTL/<2.005,87,12.44>,<0,0,1>
                TARG/<2.005,87,12.44>,<0,0,1>
                SNAP=YES
                SHOW FEATURE PARAMETERS=NO
                SHOW CONTACT PARAMETERS=YES
                  AVOIDANCE MOVE=NO,DISTANCE=0.3937
                SHOW HITS=NO
                MOVE/CLEARPLANE
    PNT12.44_3 =FEAT/CONTACT/VECTOR POINT/DEFAULT,POLAR
                THEO/<2.005,180,12.44>,<0,0,1>
                ACTL/<2.005,180,12.44>,<0,0,1>
                TARG/<2.005,180,12.44>,<0,0,1>
                SNAP=YES
                SHOW FEATURE PARAMETERS=NO
                SHOW CONTACT PARAMETERS=YES
                  AVOIDANCE MOVE=NO,DISTANCE=0.3937
                SHOW HITS=NO
                MOVE/CLEARPLANE
    PNT12.44_4 =FEAT/CONTACT/VECTOR POINT/DEFAULT,POLAR
                THEO/<2.005,273,12.44>,<0,0,1>
                ACTL/<2.005,273,12.44>,<0,0,1>
                TARG/<2.005,273,12.44>,<0,0,1>
                SNAP=YES
                SHOW FEATURE PARAMETERS=NO
                SHOW CONTACT PARAMETERS=YES
                  AVOIDANCE MOVE=NO,DISTANCE=0.3937
                SHOW HITS=NO
                WORKPLANE/XPLUS
                COMMENT/REPT,
                **************************
                IMS NO. 78
                DISTANCE 12.44 ± 0.006
                **************************
    DIM DIST97= 2D DISTANCE FROM POINT PNT12.44_1 TO POINT PNT_A1 PAR TO   ZAXIS,NO_RADIUS  UNITS=IN,$
    GRAPH=OFF  TEXT=OFF  MULT=10.00  OUTPUT=BOTH
    AX    NOMINAL       +TOL       -TOL       MEAS        DEV     OUTTOL
    M      12.4400     0.0060     0.0060    12.4400     0.0000     0.0000 --#--
    DIM DIST98= 2D DISTANCE FROM POINT PNT12.44_1 TO POINT PNT_A1 PAR TO   ZAXIS,NO_RADIUS  UNITS=IN,$
    GRAPH=OFF  TEXT=OFF  MULT=10.00  OUTPUT=BOTH
    AX    NOMINAL       +TOL       -TOL       MEAS        DEV     OUTTOL
    M      12.4400     0.0060     0.0060    12.4400     0.0000     0.0000 --#--
    DIM DIST99= 2D DISTANCE FROM POINT PNT12.44_2 TO POINT PNT_A1 PAR TO   ZAXIS,NO_RADIUS  UNITS=IN,$
    GRAPH=OFF  TEXT=OFF  MULT=10.00  OUTPUT=BOTH
    AX    NOMINAL       +TOL       -TOL       MEAS        DEV     OUTTOL
    M      12.4400     0.0060     0.0060    12.4400     0.0000     0.0000 --#--
    DIM DIST100= 2D DISTANCE FROM POINT PNT12.44_1 TO POINT PNT_A1 PAR TO   ZAXIS,NO_RADIUS  UNITS=IN,$
    GRAPH=OFF  TEXT=OFF  MULT=10.00  OUTPUT=BOTH
    AX    NOMINAL       +TOL       -TOL       MEAS        DEV     OUTTOL
    M      12.4400     0.0060     0.0060    12.4400     0.0000     0.0000 --#--

  • #2
    The problem is probably to do with your naming convention - see below

    From the PC-Dmis help files

    Feature ID Rules

    When modifying IDs, follow these rules:
    • Do not use space characters (use an underscore instead).
    • Do not duplicate feature names for different features.
    • Do not use names that are identical to PC-DMIS keywords or commands (ALIGN, PROBE, OFFSET, and many more).
    • Do not share names between ID types. For example, an alignment ID should not have the same ID as a feature ID or a label ID.
    • All IDs should be alphanumeric. You may use an underscore or a dash.
    • IDs should start with a letter.
    • Avoid using these miscellaneous characters: @ # $ % & * ( ) + = / \ [ ] { }

    While PC-DMIS does not prevent you from changing a feature ID to anything you want, ignoring these rules may cause problems with expressions, reporting, or how that ID functions with routines that use other products (like DataPage+, Microsoft Excel, and so on).
    Try replacing the . with a _

    Comment


    • #3
      Try to rename 12.44_1 as 12p44_1 or Whatever makes sense for you.

      B&S CHAMELEON/PCDMIS CAD++ V2011

      There are no bugs, only "UNDOCUMENTED ENHANCEMENTS!"

      sigpic

      Comment


      • #4
        PCDMIS thinks you are trying to do a math formula within your feature ID. Never ever ever use anything other than LETTERS_NUMB3RS_AND_UNDERSCORES within your feature ID's (unless intentional), and you will have lowered your chances of strange ghostly happenings in your code again.

        Comment


        • #5
          PC-DMIS should not have any problem with those featurenames. Might be a bug, which version is this?
          PC-DMIS CAD++ 2o19 R1 SP11

          Comment


          • jigars
            jigars commented
            Editing a comment
            Pc-dmis cad++ 2019 r1

        Related Topics

        Collapse

        Working...
        X