[In...] Posted May 7 Share Posted May 7 Good Day, I am currently using the T-SCAN hawk 2 via ZEISS INSPECT and it's been fantastic. However, I would like to use the trigger button (physical trigger button on the T-SCAN hawk 2) extensively. For instance: Instead of going back and forth from the T-SCAN hawk2 to the PC, I would like to use the trigger for more commands such as advancing to the next step, etc. Therefore, I was wondering how the PC/ZEISS INSPECT picks up the trigger button from the T-SCAN hawk 2. Unfortunately, the trigger button command cannot be recorded in the internal script. Is there a way to find how the trigger button signal is sent and received by the PC?ZEISS INSPECT? Does it send a .dll file? Or is it just internal code from the GOM library? Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in