hexagon logo

Extracting directional vector of position deviation of elements in FCF...

I'm currently working on extracting additional information from FCF:s using Automation. What I am interested in is the deviation vectors of elements in positional tolerances.

I do seem get the vector components I need from the summery table when all relevant axis and current alignmen is selected. Only problem is I can´t assume that the right axis will always be selected. I can change the alignment used, but I am having difficulty changing the selected axis.

Changing USE_AXIS(139) fields using puttext returns true but does not actually change the value nor the output.

The axis fields (132) can change the axis reported, but I haven´t found a comprehensible pattern to how it responds to input. Just rewriting with the wanted values does not seem to work. Have anybody gotten that to work?

I looked into using Devang, no luck since it uses the workplane instead of anything sensible(seriously, what is up with that?).

I looked into using the datum shift, however it seems to me it only gives half the answer as it works from the reference coordinate system basis. I would then first have to build the base from the reference set and the add the datumshift to get out anything useful. That feels like serious work as the different elements will lock different aspects of translation/rotation. (There do seem to be such a matrix in the exported XML-file.)
Parents
  • I'm currently working on extracting additional information from FCF:s using Automation. What I am interested in is the deviation vectors of elements in positional tolerances.

    I do seem get the vector components I need from the summery table when all relevant axis and current alignmen is selected. Only problem is I can´t assume that the right axis will always be selected. I can change the alignment used, but I am having difficulty changing the selected axis.

    Changing USE_AXIS(139) fields using puttext returns true but does not actually change the value nor the output.

    The axis fields (132) can change the axis reported, but I haven´t found a comprehensible pattern to how it responds to input. Just rewriting with the wanted values does not seem to work. Have anybody gotten that to work?

    I looked into using Devang, no luck since it uses the workplane instead of anything sensible(seriously, what is up with that?).

    I looked into using the datum shift, however it seems to me it only gives half the answer as it works from the reference coordinate system basis. I would then first have to build the base from the reference set and the add the datumshift to get out anything useful. That feels like serious work as the different elements will lock different aspects of translation/rotation. (There do seem to be such a matrix in the exported XML-file.)


    Post some code
Reply
  • I'm currently working on extracting additional information from FCF:s using Automation. What I am interested in is the deviation vectors of elements in positional tolerances.

    I do seem get the vector components I need from the summery table when all relevant axis and current alignmen is selected. Only problem is I can´t assume that the right axis will always be selected. I can change the alignment used, but I am having difficulty changing the selected axis.

    Changing USE_AXIS(139) fields using puttext returns true but does not actually change the value nor the output.

    The axis fields (132) can change the axis reported, but I haven´t found a comprehensible pattern to how it responds to input. Just rewriting with the wanted values does not seem to work. Have anybody gotten that to work?

    I looked into using Devang, no luck since it uses the workplane instead of anything sensible(seriously, what is up with that?).

    I looked into using the datum shift, however it seems to me it only gives half the answer as it works from the reference coordinate system basis. I would then first have to build the base from the reference set and the add the datumshift to get out anything useful. That feels like serious work as the different elements will lock different aspects of translation/rotation. (There do seem to be such a matrix in the exported XML-file.)


    Post some code
Children
No Data