hexagon logo

QDAS converter - Can I include K0004 date and time?

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!
Parents
  • 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
Reply
  • 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
Children
No Data