[moobster]

After a probe in Mach3, I opened the .txt file in Aspire.
The 2D and 3D views came up on the screens but they were inverted.
I did a probe on a set of diagonal wire cutter jaws and what should have been a v groove was a raised prism.

I'm new to the touch probing scene and don't know if I'm supposed to correct this in Mach or correct it in Aspire.
I've used the search engines on both sites and can not find any posts on the topic.
Any help would be greatly appriecated.
moobster

[ger21]

Are you importing with the gadget?

[moobster]

Are you importing with the gadget?

Yes, I'm importing with the "Regular Grid Gadget" in Aspire 4.5.
I am using the digitizing wizard that comes in Mach3 for the probing routine.
I'm messing with Z reversed in Machs homing limits and also with the hot keys for page up and down and trying to invert the point cloud from there.
This is starting to look promising now. It appears that Mach somehow got set up on this new machine with Z+ making the axis go down.
I'm going back out to try again.

[vmax549]

IF that were the case then the wizard generated code would never had worked as it assumes that Z- is down.

Just a thought, (;-) TP

[moobster]

IF that were the case then the wizard generated code would never had worked as it assumes that Z- is down.

Just a thought, (;-) TP

Yup, it didn't work.

I'm out of ideas.

[vmax549]

IF you take teh points txt file and put a G01 F100 as teh first line then you can load it back into mach3 as Gcode and you see teh object you scanned. Does it look right ? It should.

IF it does then the problem is in Aspire or its import routine.

Just a thought, (;-) TP

[moobster]

IF you take teh points txt file and put a G01 F100 as teh first line then you can load it back into mach3 as Gcode and you see teh object you scanned. Does it look right ? It should.

IF it does then the problem is in Aspire or its import routine.

Just a thought, (;-) TP

Thanks for your help so far Vmax549
I can't get it to read in Mach
I tried to load it back into Mach with the G01 F100 first line and the status box reads "Bad character usedLine1"
The g code has no x,y,z in the coordinates, so that may be the problem.
Here is a sample of the first few lines of g code mach produced with the probe.
G01 F100
0.00000,0.00000,0.06000
0.04997,0.00000,0.06000
0.09995,0.00000,0.06000
0.14992,0.00000,0.06000
0.19990,0.00000,0.06000
0.24987,0.00000,0.06000
0.29985,0.00000,0.06000

This hasn't hit the probed surface yet, it is still on it's way over but the probe tip is .060" below the top surface of the coin.
I believe all I need to do is get a( - )in front of the z coordinate and all will be good.
x's and y's seem to be good, it's just the z that's inverted.

[victorofga]

as I remember, accutrans has function to inserting the axis letters..

shopbot producing this type output where no axis numbers outputted..

[moobster]

Attachment 307252
Canadian Nickle
I'm not sure what I did, but its working.
This is what it looks like in Aspire.
I think it was in the Z direction of Mach, cause the DRO would go more + the closer the probe got to the table,
so the deeper the probe went the higher the number. This is the only way I can explain it.

Thanks for your responses in helping me solve this issue. So, who won the game???