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

QDAS converter - Can I include K0004 date and time?

constadin
Hello guys,

I am currently in version 2017 and in this version, having the seperate PCDMIS to QDAS converter program provided by hexagon, is the only option for a .dfq output. I do not have much experience with it but I was able to integrate it to my core program and I am getting automatically my measurments in .dfq format. Also I was able with trackfield commands to add information such as machine name, work order, batch number etc... For the love of me although, I could not find a way to add the K0004 field which is data for the current date and time.

After a long day, I ended up believing that this is possible with later versions of pcdmis that do not need the converter program only. AFAIK, I can only add the K0004 after the program execution with pcdmis appending the exported file, but this is bypassing and I want to look into it as a final solution.

Do you guys have any idea or experience for that matter? Thanks in advance!
  • Did you go into the Setup K-Field Configurator and ensure that the boxes are checked for K0004?

  • Yes I did and there is no option for said K field unfortunately. I am using the latest version of the converter by the way.

  • Coming directly from the manual, there is no K0004 unfortunately. Also I do not seem to understand the following table...

  • Oh this is a different configurator than what is used commonly. Let me see if I can get you some additional assistance.
  • Hello guys,

    this converter is still an active product, developed at Hexagon in Germany (also available for the latest PC-DMIS Versions). The K0004 is automatically generated from the converter. Based on a lot of customer request we will take a time stamp for all characteristics if the measurement routine is executed. There is in the moment no possibility to overwrite this value. If this is a request, please let me know and we can do this in a future version.

    The latest Version you can find here:
    ftp://ftp.hexmet.de/PC-DMIS/PC-DMIS_...6.2020.212.zip

    The tool requires a valid license from Hexagon Metrology GmbH in Germany.

    Best regards
    Frank Herr
    Director Application Technology & Support EMEA
  • Hello thanks for the input. In fact I was using the final 5.xxx.xxx version that exists found here - https://ftp.hexmet.de/PC-DMIS/PC-DMIS_Q-DAS_Converter/PC-DMIS_Q-DAS_Converter_Version_5/

    Thing is that I read somewhere that this would be the final version of the converter which apparently is not the case since there is a version 6. I will download it and try to see if the K0004 is indeed automatically generated unlike the latest version 5.

    Based on a lot of customer request we will take a time stamp for all characteristics if the measurement routine is executed. There is in the moment no possibility to overwrite this value. If this is a request, please let me know and we can do this in a future version.

    I do not think I understand what you mean here! In any case, I hope this update will solve this issue!
  • K0004 is included in the DFX information section of the file. The date and time stamp is describing when the individual part was measured. By this reason the converter is using the system time at the moment when the measurment routine will be executed. There is no change between Version 5 and 6.
  • Here I send you 2 examples how the fille will look like:

    K0001/1 150.00000
    K0002/1 0
    K0004/1 08.06.2021/11:06:29
    K0001/2 180.00000
    K0002/2 0
    K0004/2 08.06.2021/11:06:29
    K0001/3 30.01000
    K0002/3 0
    K0004/3 08.06.2021/11:06:29

    or

    124.000000 16.09.2021/07:56:3250.000000 16.09.2021/07:56:3260.500000 16.09.2021/07:56:32
  • Version requires PC-DMIS Version 2020.2 or higher. It will support also the GeoTol, Size and Temperature commands.
  • In the update notes and in the user manual, I found these info:


    Version 5.xxxx.y29 - Added support for lower acceptance limit (K2116 and K2117). The value will be defined in a tracefield using the name K2116_K2117. The value is defined in percent (e.g. value 70 = 70% of the tolerance). TRACEFIELD/DISPLAY=NO,DISPLAY MESSAGE=K2116_K2117 ; K2116_K2117 : 70 The tracefiled can be repeated in the measuring routine if the value will be changed for different dimension commands. - Fix for K2991 - for legacy form dimensions the axis letter was missing - K2005: New Q-DAS Flags HI=5 and OS=6 was added for Ford rules. - K0004, K0006, K0007, K0008, K0010, K0012 and K0053 will be only written ones using /0 if Ford rules are active. - Independend of the character in the Feat1 ID X,Y and Z will be written in the Q-DAS ASCII files (valid only for Ford naming rules). - Change of QDAS E Tracefield handling to timer function to protect against Server busy error message - Check if PCDLRN process exist before GetObject. - Fix in ftp upload protocol

    I have no idea what does this mean and maybe is the solution to the k0004 showing in the exported file. Anyone have any idea?
    Attached Files
  • K0004 is included in the DFX information section of the file. The date and time stamp is describing when the individual part was measured. By this reason the converter is using the system time at the moment when the measurment routine will be executed. There is no change between Version 5 and 6.

    Hello Franck, thanks for the reply! So is it possible to have a DFQ K0004 field like the example that follows?

    K0001 6.241015.357010.43205.44205.4380
    K0004/0 02.10.20/08:51:19
    K0006/0 1
    K0014/0 5
    K0054/0 18.8000 °C

    This is a DFQ file example not generated or having naything to do with pc dmis from a different branch of our company. The request is having similar. I could only get date and time info in the DFQ file in the following format

    K2991/34 10.5.M
    K2001/34 10.5.M
    K2002/34 10.5.M.REF_C.PLN105
    K2003/34 REF_C
    K2005/34 3
    K2009/34 200
    K2022/34 3
    K2101/34 10.50000
    K2110/34 10.35
    K2111/34 10.65
    K2112/34 -0.15000
    K2113/34 0.15000
    K2120/34 1
    K2121/34 1
    K2130/34 9.75
    K2131/34 11.25
    K2142/34 MM
    24.652710 31.08.2021/15:32:3912.86000031.08.2021/15:32:3912.86000031.08.2021/15:32:390.00000031.08.2021/15:32:390.00000031.08.2021/15:32:397.02000031.08.2021/15:32:393.00000031.08.2021/15:32:390.00000031.08.2021/15:32:398.50000031.08.2021/15:32:39-0.00083031.08.2021/15:32:393.00000031.08.2021/15:32:390.00000031.08.2021/15:32:3912.86000031.08.2021/15:32:390.00166031.08.2021/15:32:393.00000031.08.2021/15:32:390.00000031.08.2021/15:32:398.50000031.08.2021/15:32:390.00083031.08.2021/15:32:393.00000031.08.2021/15:32:390.00000031.08.2021/15:32:3912.86000031.08.2021/15:32:390.00166031.08.2021/15:32:3911.00000031.08.2021/15:32:3910.00000031.08.2021/15:32:390.00000031.08.2021/15:32:3912.86000031.08.2021/15:32:390.00000031.08.2021/15:32:3910.00000031.08.2021/15:32:390.00000031.08.2021/15:32:3912.86000031.08.2021/15:32:390.00000031.08.2021/15:32:399.45000031.08.2021/15:32:399.45000031.08.2021/15:32:3910.50000031.08.2021/15:32:39
  • in reply to Frank Herr
    Is there a setting to have the results as displayed in the first example rather than the second?
  • Ok this is stupid but I will report it for future reference in case of need by somebody. The solution is a tickbox in preferences, setup - Using line notation. I could swear that I tested this... In any case, not ticking the box provides results in the form of K0004/0 date and time for each measurement. Finally I got the solution. Thanks everybody for the support!
  • Hello Constadin, this is correct. Q-DAS ASCII supports 2 different formats. Both are supported by the converter.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement