Problem: Object does
not match target type.
Possible solution:
This topic contains some error messages or conditions you might see and some ideas that might help resolve them. Click on the link for each problem below to see possible solutions. If this topic does not provide a solution, visit Hexagon Technical Support here:
http://support.hexagonmetrology.us/ics/support/default.asp
Problem: Object does
not match target type.
Possible solution:
Problem: Object reference
not set to an instance of an object.
Possible solution:
Problem: You receive
a "No such interface supported" message when you try to
execute a measurement routine.
Possible solution:
Problem: You receive
an "Emergency Error" when Inspect
tries to establish a connection with PC-DMIS or during execution.
Possible solution:
Problem: Inspect has a configuration error
with its adapters and you want to reset it back to its factory settings.
Possible
solution:
Problem: Your Settings.xml
file is corrupt, and you cannot use Inspect
at all.
Possible
solution:
Problem: Inspect does not generate a report
when you execute a PC-DMIS measurement routine.
Possible
solution:
Problem: When you execute,
Inspect does not
show your version of PC-DMIS.
Possible
solution:
Problem: When you execute,
Inspect gives an
Execution Option Error. The error says it cannot set an execution
option, and that an execution option can only be set on a loaded temporary
measurement routine.
Possible
solution:
Problem: When you execute
a playlist, Inspect
gives an execution error message about invalid routines in the playlist.
Possible
solution:
Problem: When you execute
a routine or playlist, Inspect
gives an execution error message about a task being expired.
Possible
solution:
Problem: Pallet, Barcode,
and some probe-related capabilities, such as calibration, Probes Refresh,
etc. no longer function.
Possible
solution:
Problem: Inspect
does not work if the PC-DMIS report output folder is shared by other
CMMs. When this happens, Inspect confuses the origin of the reports.
Possible
solution:
Problem: In
very rare cases, during execution, Inspect gives a "System call
failed" error message that stops execution.
Possible
solution:
