I inserted a Dcc program into a Romer data base, then added a probe change for the HP-L-20.8 Scanner and edited out he codes that were not needed "move points, tip changes etc... Then went to edit the perimeters in the existing code (f9) and the software pops up an error stating that the surface point is not supported by the current laser. It will allow me to create a new surface point just not edit the older code????
I inserted a Dcc program into a Romer data base, then added a probe change for the HP-L-20.8 Scanner and edited out he codes that were not needed "move points, tip changes etc... Then went to edit the perimeters in the existing code (f9) and the software pops up an error stating that the surface point is not supported by the current laser. It will allow me to create a new surface point just not edit the older code????
When it comes to different sensors, making PC-DMIS support them often requires handling features differently.
The more complicated optical sensors require far more parameters than a touch sensor, so the measurement feature has to be created with an upgraded dialog tailored to the special sensor to get all those parameters in place.
The feature created for a touch sensor won't have those fields, so the optical sensor cannot use it.
It would be a nice luxury for PC-DMIS to "up-convert" the features as soon as you change the active probe, but from what I gather there are too many parameters that can't be automated.
I inserted a Dcc program into a Romer data base, then added a probe change for the HP-L-20.8 Scanner and edited out he codes that were not needed "move points, tip changes etc... Then went to edit the perimeters in the existing code (f9) and the software pops up an error stating that the surface point is not supported by the current laser. It will allow me to create a new surface point just not edit the older code????
When it comes to different sensors, making PC-DMIS support them often requires handling features differently.
The more complicated optical sensors require far more parameters than a touch sensor, so the measurement feature has to be created with an upgraded dialog tailored to the special sensor to get all those parameters in place.
The feature created for a touch sensor won't have those fields, so the optical sensor cannot use it.
It would be a nice luxury for PC-DMIS to "up-convert" the features as soon as you change the active probe, but from what I gather there are too many parameters that can't be automated.
