Using a Clean-Tec (Lang) Propeller with Fusion360 ramping up the spindle speed

[alex.neretin]

Hello,

I'm using a clean-tec probeller after my machining cycle, to clean up my part from chips and coolant.

According to the manual, I should start the spindle with 2000 1/min (to unfold the propeller blades) then ramp up to max. 12000 1/min. It's to reduce the wear of the propeller part.

Is there a posibility to program this in fusion.

Best regards,

[mathew.hutton]

Hi @alex.neretin 

You could potentially do this by specifying the ramp spindle speed as 2,000RPM, and the spindle speed as 12,000RPM. In your toolpath you would need to specify it to do a  helix lead in move which would use the ramp spindle speed. 

Let me know if this helps. If you require further assistance, you could attach your project and i could take a look for you

Cheers

Mat

[alex.neretin]

Hello Mat,

I  tried this approach.

This dosn't help, because the tool ramps up to it's normal speed after tool change and then slowes down to the ramping speed accelerating then to the normal speed again.

N22 (Reinigung)
N23 M9
N24 G7 L1=1 (Tisch in Grundstellung vor Werkzeugwechsel)
N25 G00 B0 C0 (Tisch in Grundstellung vor Werkzeugwechsel)
N26 S250 M3 (Drehzahlbegrenzung vor Werkzeugwechsel)
N27 T22 M6 <- Tool Clean-Tec Propellor
N28 S12000 M3 <- spindle speed
N29 G54 I1
N30 G0 X118.422 Y53
N31 G0 Z166.942
N32 E3=5000 (Schlichtvorschub)
N33 E4=5000 (Einfahrvorschub)
N34 E5=5000 (Ausfahrvorschub)
N35 E8=3000 (Ramping)
N36 G2 Y37 Z150.942 J37 K166.942 F=E4
N37 G1 X118.422 Y21
N38 G3 X134.422 Y5 Z150.942 I134.422 J21
N39 S2000 <- ramping speed
N40 G1 X134.51 Z148.442 F=E8
N41 G2 X150.5 Z133 I150.5 K149
N42 S12000 <-back to normal speed
N43 G1 X216 Y5 F=E3
N44 G2 X306 Y-85 Z133 I216 J-85
N45 G1 Y-187

In Fusion there is a option to input a manual g-code.

Could this be an option?

Best regards,

[mathew.hutton]

Hi @alex.neretin 

I've not actually used that option as of yet so i'm unsure as o whether it would work but it's worth a try. Alternatively, at this point you could just edit that single line so it does the tool change and spind up to 3,000RPM instead of 12,000RPM. I think if the manual G-code option doesn't work for you then i can submit a ticket to development so that we can incorporate this functionality somehow, like a tick box so that it starts off with ramp spindle speed etc. 

Let me know how you get on and i can submit a ticket in any case 

Cheers

Mat

[rhdfmail]

I solved this by by dividing it into two operations.
One "startup" Wich is a simple drill-op with 2000rpm and then another for the actual cleaning on full speed.
Saved them as a template 

A future improvement in fusion would be that the speed is set to that of the first cutting-move
Its annoying that the spindle revs up to 12000 rpm, rapid down and then goes down to say 5000

[Laurens-3DTechDraw · Accepted solution]

What @mathew.hutton suggested indeed doesn't work.

Because the post processor does not know if the normal or the ramp spindle speed will be needed for the first cut. And therefore it just defaults to the normal spindle speed.

What I have done in our post is use the turret number 2 to trigger the ramping behavior in the post.

It now looks like this:

if(tool.turret == 2){
	writeBlock(
      sOutput.format(tool.rampingSpindleRPM), mFormat.format(tool.clockwise ? 3 : 4)
    );
    writeBlock("G4 X2");
  writeBlock(
      sOutput.format(tool.spindleRPM), mFormat.format(tool.clockwise ? 3 : 4)
    );
    forceAny();
    } else {
    writeBlock(
      sOutput.format(tool.spindleRPM), mFormat.format(tool.clockwise ? 3 : 4)
    ); }

What was this:

    writeBlock(
      sOutput.format(tool.spindleRPM), mFormat.format(tool.clockwise ? 3 : 4)
    );

So I just give the lang fan turret number 2 in the tool library and it works like a charm.

[alex.neretin]

Hello Mat,

Changing my code afterwards is not a permanent solution. It's just a source for errors.

It would be great, if you'd open a ticket for this issue.

I think other machinist would also be thankfull for this option, if this sort of clean up cycle becomes more popular in the future.

Please keep me informed.

Best regards,

[alex.neretin]

Hello,

I'll give that a try.

Thanks,

[rhdfmail]

Brilliant!

I had some idea of tinkering with the post to solve it.

[alex.neretin]

Hello Laurens,
it works perfect.
Thanks alot

[gtprototype]

Hello Laurens,

It really would be nice to be able to have a chip clearing fan in the tool library that already does this however, your contribution looks to be a good work around.  I'm trying to duplicate your solution with the latest Haas Next Gen post here:

https://cam.autodesk.com/hsmposts?p=haas_next_generation

I'm getting stuck because I can't identify the same variables.  Can you point me in the right direction?  Thank you.

Regards

Dale

[Laurens-3DTechDraw]

Yeah, posts have changed a bit since then. The edited version of that post is attached, along with some pictures as an explanation.

   

[gtprototype]

Thank you Laurens!