Hp-s-x1h failing?

[Cumofo]

I doing scans today, all day, nothing is coming up good. Is this an indication of a broken scanning head?HP-S-X1H FAILURE.JPG
It also pulls away from cylinders and scans the air....


I think i'm smoked, or is this a registry fixable issue?


Thanks for the help. I know i cant do this alone.

[KIRBSTER269]

can you post your settings in your scan, maybe you just have a setting wrong, one with Execution Tab, one with Graphics, one with Path Definitions

[Schrocknroll]

can you post your settings in your scan, maybe you just have a setting wrong, one with Execution Tab, one with Graphics, one with Path Definitions

Also the F10 probe options tab might be helpful to post.

[Cumofo]

Yes I agree. I think I'm going to do a factory reset, update to 2019 R3, and go re-input Miim line by line. I've had some very strange things happening with this 20-40-20 Global MN: like it became totally disconnected from the report. I could change alignments above, but the dimensions below would not respond. I showed a few 10ths deviation in two axii, but the true PO-output was over . 009
Iive been manning this machine for just two months and it's been a total nightmare. It's just three years old on the install, and all the dip switches for the Tesastar - e were for an micro series controller.
Thank you for the support gentlemen.

[Cumofo]

Dear Friends and colleges,

I have installed the latest rev 2019 R2 SP3, reloaded all defaults from the resident controller file, validated all registry entries to the MIIM and Scanning Parameters to H006908 PRB.

Nonetheless, i am unsuccessful in returning a useful scan output. I am bent into a complete pretzel, and I am ineffectual now at solving even the most remedial challenges. I have included many screenshots of my technique and parameters that you may correct my deficits please, that I may return to producing data for final part acceptance as customary for our profession. Thank you!

SCAN EXE MENU.JPGgraphics menu.JPGpath definition menu.JPGsettings menu.JPGparameter settings.JPG THIS IS THE GARBAGE I GET!
Here are the associated errors:
ACTUALLY I ADJUSTED THE FIND NOMS TOLERANCE TO THE SIZE OF THE 8MM SPHERE PLUS .030.




What should I do next?


Thank You
Gabriel Ortiz
949-573-4833

[JEFMAN]

I would try measuring a vector point with the cad where the scan goes up.
Maybe it's only a bad definition.
You could also export the hits in a xyz file (as a cop), then change all the z values, and import the file in a free form scan.

[KIRBSTER269]

maybe also try setting your offset force 0.120 N this seems to be a good setting for me, may not for you, but I would try that first. Also maybe set your offset edge to 0.0000 maybe your to close to those holes. This is the rule from the help file.

Edge offset box
The Edge offset option defines the minimum distance away from a boundary/edge where scan points are considered valid. Scan points that are closer to the boundary that the specified offset distance are not allowed. For example, if you set your offset distance to .5 mm, any scan point located within .5 mm of the boundary/edge is not allowed. This is used with the Jump holes option.

Oh and maybe change this to FIND Nominals

Capture.JPG

[louisd]

It looks as if the data points are patterned in alignment with those bosses? Maybe KIRBSTER269 is right with the edge offset. Defining it as a perimeter scan is likely considering the CAD of that pattern of bosses, even with a safe edge offset.

Is it simply a planar scan, in a circular pattern? If so, try autoplane with the "Adaptive plane circle scan" strategy.

[KIRBSTER269]

One other thing I was curious about was that Inner Bound is checked. I really don't use Perimeter scans, but will add this bit of info.

Capture.JPG

[Cumofo]

Any other modification to the input parameters produces the error: "Bad Surface Etc."

deselecting the surface in the graphics dialog box allows the path generation to proceed.

it produces the expected path and either crashes to desktop or begins the scan and produces these errors:

Power Circuit Failure.JPG

or:
error2.jpg


YIKES!

[Cumofo]

NO luck with the auto plane adaptive circle scan, it begins to scan normally, then gradually picks up off the part and ends up probing the air about an inch above the surface. Then bombs out: CRASH TO DESKTOP.
HARDWARE DRIVER LEVEL 8 ERROR.JPGOVER CURRENT ERROR 3.JPG

[Cumofo]

I broke my toy!!

[KIRBSTER269]

reboot everything

[louisd]

Do you have the "PROBE ENABLE" button on the jogbox turned on (far top-left button on the NJB Jogbox)?
--For the HP-S-X1H sensor, this is not a "probe enable" toggle, but a probe balance/re-balance toggle. If you have this turned off, it's like using a scale that is showing +30lbs before stepping on it... With the light on, it 'tares' the scales on the sensor, in the machine's current orientation (gravity affects each probe/angle differently).

Another note that might be helpful: We had Hexagon apps engineer on-site here in March of 2019, she installed new firmware for our Global S Chrome, which has the same HP-S-X1H sensor. I had similar ridiculous crashes and hardware faults when i attempted to conduct a scan, before this firmware update was implemented.

[Cumofo]

Do you have the "PROBE ENABLE" button on the jogbox turned on (far top-left button on the NJB Jogbox)?
--For the HP-S-X1H sensor, this is not a "probe enable" toggle, but a probe balance/re-balance toggle. If you have this turned off, it's like using a scale that is showing +30lbs before stepping on it... With the light on, it 'tares' the scales on the sensor, in the machine's current orientation (gravity affects each probe/angle differently).

Another note that might be helpful: We had Hexagon apps engineer on-site here in March of 2019, she installed new firmware for our Global S Chrome, which has the same HP-S-X1H sensor. I had similar ridiculous crashes and hardware faults when i attempted to conduct a scan, before this firmware update was implemented.

YESS! Excellent! Hexagon spent 3 hours remotely experiencing these anomalies, completely stumped as how to proceed. The scanning head was rigorously tested with a simple script that produced only submicron deviations, allowing us to look elsewhere.

Thank you soo much for your input and comrade-re!


Gabriel