hexagon logo
Register Sign in
  • Replies 14 replies
  • Subscribers 9 subscribers
  • Views 199 views
  • Users 0 members are here
Options
Related

Size Feature and DataPage

bfire85
FYI

The new size feature in PC-DMIS 2017 R1 does not import into DataPage+ 5.2 SP1. I use an external command to call up the DataPageStats.exe file. I have submitted a ticket about this into Tech Support.

UPDATE from Tech Support: The external command to DataPageStats.exe does not work, however the STATS/ON does work. He will be submitting a ticket to the software development group to fix this issue.
  • A temporary workaround is to GETTEXT the two values, create generic features from them and dimension that.
    (Sorry, in Swedish, but I think you get it...) 

    
The feature

CYL1       =ELEMENT/CYLINDER,REKTANGULÄRA,INRE,GAUSS,NEJ
            TEOR/<124,50,-6>,<0,0,-1>,60.493,10
            MÄTT/<124,50,-6>,<0,0,-1>,60.493,10
            KONSTR/CYLINDER,BA,CIR1,CIR2,CIR3,,

Dimension size

SIZE4      =STORLEK/
            UTSKRIFT=BÅDA, ENHETER=MM, STANDARD: ISO 14405-1
            LÄGE FÖR TOLERANSSPECIFIKATION: NOMINELL_MED_AVVIKELSER
            NOMINELL STORLEK: 60.493
            ÖVRE TOLERANS: 0.05,__
            LOWER TOLERANCE: -0.05,LP,__
            ÖVRE STORLEK: 60.5
            UNDRE STORLEK: 60.48
            ELEMENT: CYL1

Get the UPPER and LOWER values

            TILLDELA/UPPER_SIZE=GETTEXT(1049, 0, {SIZE4})
            TILLDELA/LOWER_SIZE=GETTEXT(1050, 0, {SIZE4})

Construct two generic feature

SIZE4__UPPER=ALLMÄN/CYLINDER,BEROENDE,REKTANGULÄRA,YTTRE,$
            NOM/XYZ,<CYL1.TX,CYL1.TY,CYL1.TZ>,$
            MÄTT/XYZ,<CYL1.X,CYL1.Y,CYL1.Z>,$
            NOM/IJK,<CYL1.TI,CYL1.TJ,CYL1.TK>,$
            MÄTT/IJK,<CYL1.I,CYL1.J,CYL1.K>,$
            DIAMETER/CYL1.TDIAM,UPPER_SIZE,$
            AVSTÅND/CYL1.TLENGTH,CYL1.LENGTH

SIZE4_LOWER=ALLMÄN/CYLINDER,BEROENDE,REKTANGULÄRA,YTTRE,$
            NOM/XYZ,<CYL1.TX,CYL1.TY,CYL1.TZ>,$
            MÄTT/XYZ,<CYL1.X,CYL1.Y,CYL1.Z>,$
            NOM/IJK,<CYL1.TI,CYL1.TJ,CYL1.TK>,$
            MÄTT/IJK,<CYL1.I,CYL1.J,CYL1.K>,$
            DIAMETER/CYL1.TDIAM,LOWER_SIZE,$
            AVSTÅND/CYL1.TLENGTH,CYL1.LENGTH

Dimension

UTV LOC1= ELEMENTEGENSKAPER FÖR CYLINDER SIZE4__UPPER  ENHETER=MM ,$
GRAF=AV  TEXT=AV  MULT=10.00  UTSKRIFT=BÅDA  HALV VINKEL=NEJ
AX  NOMINELLT       +TOL       -TOL       MÄTT          AVV    UTOMTOL
X      124.000      0.050     -0.050    124.000      0.000        0.000
Y       50.000      0.050     -0.050     50.000      0.000        0.000
Z       -6.000      0.050     -0.050     -6.000      0.000        0.000
D       60.493      0.050     -0.050     60.500      0.007        0.000
SLUT PÅ UTVÄRDERING LOC1

UTV LOC2= ELEMENTEGENSKAPER FÖR CYLINDER SIZE4_LOWER  ENHETER=MM ,$
GRAF=AV  TEXT=AV  MULT=10.00  UTSKRIFT=BÅDA  HALV VINKEL=NEJ
AX  NOMINELLT       +TOL       -TOL       MÄTT          AVV    UTOMTOL
D       60.493      0.050     -0.050     60.480     -0.013        0.000
SLUT PÅ UTVÄRDERING LOC2
  • FYI

    The new size feature in PC-DMIS 2017 R1 does not import into DataPage+ 5.2 SP1. I use an external command to call up the DataPageStats.exe file. I have submitted a ticket about this into Tech Support.

    UPDATE from Tech Support: The external command to DataPageStats.exe does not work, however the STATS/ON does work. He will be submitting a ticket to the software development group to fix this issue.

    There are quite a few issues with DataPage when you use DataPageStats.exe and then DataImporter, that somehow work perfectly fine when you use STATS/ON and Operation>Send Current Stats to File... (which creates an XML that gets uploaded via DataImporter). Two exact same files, somehow get imported differently...
  • A temporary workaround is to GETTEXT the two values, create generic features from them and dimension that.
    (Sorry, in Swedish, but I think you get it...) 

    
The feature

CYL1 =ELEMENT/CYLINDER,REKTANGULÄRA,INRE,GAUSS,NEJ
TEOR/<124,50,-6>,<0,0,-1>,60.493,10
MÄTT/<124,50,-6>,<0,0,-1>,60.493,10
KONSTR/CYLINDER,BA,CIR1,CIR2,CIR3,,

Dimension size

SIZE4 =STORLEK/
UTSKRIFT=BÅDA, ENHETER=MM, STANDARD: ISO 14405-1
LÄGE FÖR TOLERANSSPECIFIKATION: NOMINELL_MED_AVVIKELSER
NOMINELL STORLEK: 60.493
ÖVRE TOLERANS: 0.05,__
LOWER TOLERANCE: -0.05,LP,__
ÖVRE STORLEK: 60.5
UNDRE STORLEK: 60.48
ELEMENT: CYL1

Get the UPPER and LOWER values

TILLDELA/UPPER_SIZE=GETTEXT(1049, 0, {SIZE4})
TILLDELA/LOWER_SIZE=GETTEXT(1050, 0, {SIZE4})

Construct two generic feature

SIZE4__UPPER=ALLMÄN/CYLINDER,BEROENDE,REKTANGULÄRA,YTTRE,$
NOM/XYZ,<CYL1.TX,CYL1.TY,CYL1.TZ>,$
MÄTT/XYZ,<CYL1.X,CYL1.Y,CYL1.Z>,$
NOM/IJK,<CYL1.TI,CYL1.TJ,CYL1.TK>,$
MÄTT/IJK,<CYL1.I,CYL1.J,CYL1.K>,$
DIAMETER/CYL1.TDIAM,UPPER_SIZE,$
AVSTÅND/CYL1.TLENGTH,CYL1.LENGTH

SIZE4_LOWER=ALLMÄN/CYLINDER,BEROENDE,REKTANGULÄRA,YTTRE,$
NOM/XYZ,<CYL1.TX,CYL1.TY,CYL1.TZ>,$
MÄTT/XYZ,<CYL1.X,CYL1.Y,CYL1.Z>,$
NOM/IJK,<CYL1.TI,CYL1.TJ,CYL1.TK>,$
MÄTT/IJK,<CYL1.I,CYL1.J,CYL1.K>,$
DIAMETER/CYL1.TDIAM,LOWER_SIZE,$
AVSTÅND/CYL1.TLENGTH,CYL1.LENGTH

Dimension

UTV LOC1= ELEMENTEGENSKAPER FÖR CYLINDER SIZE4__UPPER ENHETER=MM ,$
GRAF=AV TEXT=AV MULT=10.00 UTSKRIFT=BÅDA HALV VINKEL=NEJ
AX NOMINELLT +TOL -TOL MÄTT AVV UTOMTOL
X 124.000 0.050 -0.050 124.000 0.000 0.000
Y 50.000 0.050 -0.050 50.000 0.000 0.000
Z -6.000 0.050 -0.050 -6.000 0.000 0.000
D 60.493 0.050 -0.050 60.500 0.007 0.000
**** PÅ UTVÄRDERING LOC1

UTV LOC2= ELEMENTEGENSKAPER FÖR CYLINDER SIZE4_LOWER ENHETER=MM ,$
GRAF=AV TEXT=AV MULT=10.00 UTSKRIFT=BÅDA HALV VINKEL=NEJ
AX NOMINELLT +TOL -TOL MÄTT AVV UTOMTOL
D 60.493 0.050 -0.050 60.480 -0.013 0.000
**** PÅ UTVÄRDERING LOC2


    @Andersl I am aware of the work around, however this then defeats the purpose of the new feature. Lol. I could do this without the new size feature too. Haha. Apparently they will be working on a fix.


  • There are quite a few issues with DataPage when you use DataPageStats.exe and then DataImporter, that somehow work perfectly fine when you use STATS/ON and Operation>Send Current Stats to File... (which creates an XML that gets uploaded via DataImporter). Two exact same files, somehow get imported differently...

    We are working on that too. Currently our STATS/ON isn't setup correctly for some reason. That's going to get worked on as well.
  • in reply to bfire85
    Oh, I only use STATS/ON to create the master in the database, then I switch back to DataPageStats.exe. It doesn't surprise me at all that it doesn't work like it's supposed to either. DataPage has a lot of problems.
  • in reply to AndersI
    Just a FYI, in v2017 R2 we have added "proper" expression support for SIZE rather then using GETTEXT (which also works well as seen here).

    ASSIGN/UPPER_SIZE=SIZE4.UPPER.MEAS
    ASSIGN/LOWER_SIZE = SIZE4.LOWER.MEAS

    The other typical expressions (.DEV / .TOL / .OUTOL) are there as well. Expression builder has the full list if interested.
  • I'm curious for those using the external command method to create the .XML stats file. How are you dealing with updates to Datapage+ with that file path embedded in your programs? Do you edit the path when you update? I know you can install / overwrite to a neutral directory, or perhaps embedd the external command call in a subroutine so it's only a single change, but it seems using STATS/ON would be much easier to maintain.


  • At the beginning of my program, I have PCD read a text file with the location of DataPageStats.exe with a -listening tag at the end.

    At the end of my program, I have PCD read a text file with the location of DataPageStats.exe with a -end tag at the end.

    So all I have to do is change the location in the text file. But yes, we will be migrating towards the STATS/ON command.

  • in reply to bfire85
    Clever! Do you lose the ability to cancel / restart execution at cursor using this method?
  • in reply to bfire85
    If I cancel early, DataPageStats.exe cancels and doesn't store the data. Executing from cursor, I am not sure on that one.
  • in reply to bfire85
    I'm not sure I follow the your problem here , I use the external command on all of my programs and everything is transferred into Datapage 5.2. What is not going in there?, cause everything goes in there just fine for me
  • in reply to mkopesky_
    DataPage has updates? Slight smile

    J/k... DP+ doesn't update so frequently that this even really presents a problem. I was told, during one of my tech support calls, that DataPageStats isn't "really" a DataPage thing. If DataPageStats is just a file that spits out an XML, then why would it matter if DP+ is updated, and an old DPS.exe is used? Does that file ever get changed? Is it listed in the changelog?
  • in reply to mkopesky_
    It does need to be updated occasionally (as found by bfire here with SIZE) to support new commands, or changes to existing commands. My concern was that when these changes occur it would potential force me to update hundreds of programs with a new file path, a small edit, but still.

    bfire has a really elegant solution below, but I'm still concerned about users who weren't thinking ahead. The Stats/On option is tied to the PC-DMIS version (rather then the Datapage version) so I've always recommended that direction when asked. I was using this thread as a bit of a sounding board to see what I was missing.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement