Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates for functions like CGNX_RunVGRPicked. #7

Open
clope031 opened this issue May 1, 2018 · 1 comment
Open

Updates for functions like CGNX_RunVGRPicked. #7

clope031 opened this issue May 1, 2018 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@clope031
Copy link
Member

clope031 commented May 1, 2018

It seems that the current implementation hasn’t provided code to adjust tools to re-establish the relationship between tool and runtime target. We would love to know how that could be accomplished in Denso’s programming environment.

@clope031 clope031 added the enhancement New feature or request label May 1, 2018
@clope031 clope031 self-assigned this May 31, 2018
clope031 added a commit that referenced this issue May 31, 2018
@clope031
Copy link
Member Author

One issue with this implementation is that when using the Tool command the new offset will get wiped after reboot (its only set on RAM). Only when you setup a tool offset via TP or Wincaps then the offset get really saved into the storage memory

Possible Solutions:

  • Have the user confirm the new tool offset using the TP.
  • Find a way to save the Tool offset into the Storage memory via PACScript.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant