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

Offset Force Issue

nooners4
Hi,

I am having an issue with changing our offset force. We run an offset force of 0.1N. Hexagon settings run it at 0.25N. When I change it in parameter settings and try to calibrate a probe, the Offset force reverts back to 0.25N and excess probe deflection occurs. Is there any reason why it would change back to the original Offset force?

Running PC DMIS 2010 MR3.
  • In every program, before every LOADPROBE statement, you should insert an Opt Probe statement.
    F10, Option Probe, enter the values there.

    You should never have to edit the registry for daily machine operation.
  • This is the first that I have heard that you need the probeoptions command before each loadprobe command. Are you sure this is necessary? I can see how it might be needed for DC800 controllers since the probing parameters are treated as non-modal and revert to controller defaults when runtime terminates. Perhaps a probe change also triggers a reset to controller default unless otherwise specified?

    On a B3C, or similar controller, probing parameters are modal and will not change unless explicitly changed in the program. With this type of controller I doubt you need the optionprobe statement if you aren't explicitly trying to change a parameter.

    Edit: I completely agree that you should have the optionprobe statement at the beginning of every program. I'm just not sure you need it multiple times in a single program unless you are trying to change the valued of these parameters.if you want to use the same parameters throughout the program I think you only need the command once.
  • In every program, before every LOADPROBE statement, you should insert an Opt Probe statement.
    F10, Option Probe, enter the values there.

    You should never have to edit the registry for daily machine operation.

    +1.09
  • This is the first that I have heard that you need the probeoptions command before each loadprobe command. Are you sure this is necessary? I can see how it might be needed for DC800 controllers since the probing parameters are treated as non-modal and revert to controller defaults when runtime terminates. Perhaps a probe change also triggers a reset to controller default unless otherwise specified?

    On a B3C, or similar controller, probing parameters are modal and will not change unless explicitly changed in the program. With this type of controller I doubt you need the optionprobe statement if you aren't explicitly trying to change a parameter.

    Edit: I completely agree that you should have the optionprobe statement at the beginning of every program. I'm just not sure you need it multiple times in a single program unless you are trying to change the valued of these parameters.if you want to use the same parameters throughout the program I think you only need the command once.

    You can certainly have a single Opt Probe and the beginning of the program - if every probe uses the same Offset force and every Nullfilter scan uses the same Point Density.

    But we have found it very useful to tweak Offset force per probe (heavier longer ones need more) and tweak Density per scan.

    ~~~

    On the subject of Opt Probe parameters and Controllers: the older Common Controllers, B3C, FBII, etc, stored these parameters as per the Registry.
    However the new generation of FDC controllers do not and therefore the Opt Probe parameters are absolutely required in PC-DMIS programs to send the parameters to the controller during each execution.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement