Tool Plunges to Z0 at start of job

Tool Plunges to Z0 at start of job

martysletterbox
Observer Observer
789 Views
7 Replies
Message 1 of 8

Tool Plunges to Z0 at start of job

martysletterbox
Observer
Observer

Hello,

 

At the start of each job my CNC plunges to the set bottom hieght, retracts to clearance height then moves into the correct starting position and runs the job fine.  This only started happening after I re-installed Fusion 360 on my computer. Is there some setting in Fusion that is causing this or a particular line of code?

  I have tried comparing earlier codes that were fine but cannot see where the problem would be.

I have also tried running earlier codes (before reinstallation) through my toolpath program again and even these ones now incorporate the same starting plunge problem.

I have a multicam CNC using an old Toolpath software to load the the code onto the machine.

Does anyone have a solution to this problem?  Is it a Fusion or Toolpath issue?

 

0 Likes
790 Views
7 Replies
Replies (7)
Message 2 of 8

seth.madore
Community Manager
Community Manager

Could you share a legacy NC program, along with something new from Fusion?

Has there been any non-Fusion hardware/software changes?


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 3 of 8

martysletterbox
Observer
Observer

Hi Seth,

 

Yes. The "2 Centre Sash Arch" code is from before I reinstalled Fusion and Toolpath and the "Side" code is after I reinstalled it. 

No non-Fusion hardware changes that I know of. 

 

Thanks,

 

Marty

0 Likes
Message 4 of 8

martysletterbox
Observer
Observer

Also,

 

If I make a code directly from Toolpath and run it on the machine it does not plunge.  So it only plunges from code coming from fusion. Fusion does not show the plunge in the simulation so it must be something added in when I create the NC program in Fusion and then load it onto Toolpath.

 

Any ideas?

 

Marty 

0 Likes
Message 5 of 8

freviWX56W
Contributor
Contributor

In case this is not some goofy thing in the post processing engine....

Depending on what machining strategy it is, there may be a checkbox for "order by depth"; if that's checked the toolpath should start shallow and go deeper with each pass. I've had situations where the toolpath tries to start at the bottom of the cut and work its way out, until I checked that box.

 

0 Likes
Message 6 of 8

seth.madore
Community Manager
Community Manager

It looks like with "2 Center Sash" you have your origin set to the bottom of the part, but with the "SIDE", you have it set to the top. Does your machine expect one or the other, or does it not matter?

By chance, is this one of those machines/controls that are flipped around in the Z axis, with a positive direction of travel being deeper into the part, and negative direction moving away from it?


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 7 of 8

martysletterbox
Observer
Observer

Hi Seth,

 

No It does not matter which height I set the origin in the programming stage, as long as I set the top and bottom limits the same on the machine. I had set it to the bottom in "2 centre Sash" as I was was milling stock which was attached to a template board and that template board was the only constant location I had (stock were all slightly different shapes). 

What seems to happen is that the tool will plunge to whatever I set my bottom limit too when I press start. If  I set the bottom limit to 1mm below the bottom of job (whether the origin is at the top or bottom of piece) it will then it will plunge to that point, come back up and run the program.

 I have only, in the last few days, figured out that this manoeuvre is inputted as "shape 1" in the program list and if I pause the machine as soon as I press start, I can then tell it to move to the position of "shape 2" and it runs the job as per normal.

 

Also, no the machine is not flipped, positive is up, negative is down.

 

Regards,

Marty 

0 Likes
Message 8 of 8

programming2C78B
Mentor
Mentor

This just sounds like you used an edited processor that was re-set upon an update. 

Please click "Accept Solution" if what I wrote solved your issue!
0 Likes