NCPlot generates code backwards

[grweldon]

I'm using a DXF file to generate a program for a lathe. I have each segment I want to machine on a different layer. I'm using the default Fanuc control modified slightly for use with a lathe.

The DXF file shows the finished part outline, the face being 0,0 and the chuck on the left size (-Z).

After I chain the entities on each layer that make up the segments, I generate the code for each layer. The code generated seems to be backward. The pointer moves from a -Z to a +Z direction, when it should move from a +Z direction to a -Z. In English, the tool moves from the chuck to the face of the part, instead of from the face of the part toward the chuck. What causes this and how do I fix it?

Another issue is that NCPlot doesn't seem to machine the segments in the correct order. I'm assuming that NCPlot machines the segment from the first point created to the second and I didn't pay attention when I created the geometry. Is this assumption correct?

Any hints/techniques/solutions would be appreciated!

[grweldon]

OK, I figured out how to change the direction. What I still don't know how to fix is the fact that the starting point for the tool is behind the part. The first rapid move comes behind the part through the center. I don't know how to change the initial starting point of the tool.

I'm sure somebody knows how to do this and I'd appreciate it if they would share!

[MetLHead]

Hi,

After you chain the drawing you can manually generate the code in any order you want. You can also (as you discovered) reverese the direction of the chains so that they will cut in the correct direction. After chaining, click any entity that is part of the chain you want to cut. Then click "NC Sel", this will generate the code for that chain. Doing it this way you can generate the chains in any order you want.

To change the motion for approaching the part, you will need to manually edit in the approach moves. NCPlot doesn't know what kind of tool you are using, whether it's supposed to be ID/OD, etc. so you will have to handle the approach moves.

Thanks,
Scott