gSender not honouring toolpath speed

@jepho As @NeilFerreri has observed, every instance of Speed being set in the .nc file is a F1181. This translates to a ‘modest lilt’ but nothing like ‘fast’ for the machine to be moving. There is a pre-positioning move that readies Z, which is F590

G1Z-0.0382F590.6
G1X1.5259Y1.4278F1181.1

Although the co-ordinates vary as the .nc file progresses, these speeds are consistent throughout the file. So this is what Carveco’s post-processor is outputting. If your SO3 is not behaving like this, then it suggests the fault is within the machine/controller/config, it is is behaving like this, then the fault is in your Carveco design file, Carveco setup/units/machine config/etc, and/or its post-processor.

You could manually construct a .nc file to move from A to B and back with specified speeds, vary those speeds and confirm that the machine is complying… Taking the preamble from your example .nc files, this could be something like the following - please, any experts who know Grbl better, please chime in/correct.

Copy the following into a text file, and save it with .nc extension:

%
(Searough)
(STOCK/BLOCK) (X=7.283, Y=7.165, Z=1.969)
G90 G94
G17
G20
(Tool Number:510 6.350 mm dia. slot drill)
G28 G91 Z0
G90
T510 M6
G54
G0X0.0000Y0.0000

(move left and right 50mm from X0Y0Z0 at various speeds)
G0X50F500
G0X-50F500
G0X50F1000
G0X-50F1000
G0X50F1500
G0X-50F1500

(ending begins)
G17
G28 G91 Z0
G90
G28 G91 X0 Y0
G90
M30
%
(END)

Hi Neil. I must have explained this poorly. I don’t mind how fast the rapid moves are. Once my zero point is established and the correct X & Y starting positions found via the goto buttons. I usually will work from the centre of the workpiece. I jog the Z into its previously found Z zero height position then hit run. Immediately the speed of the cutter for the roughing path is too fast. I am using a new material as stock (Ash) and I had no idea how it would machine. I was roughing with a two flute 6.35mm x 32mm cutter with a 1mm stepdown, 500mm/min feed speed and 40% stepover with a 250mm/min plunge speed. This should have produced a reasonable feed speed so that I could increase it to the point just below tearout occurring.

My initial move after homing will be at that speed and it does not seem unreasonable. I have a standard sized SO3 which is unmodified apart from the fixture tooling plate, stiffener rods and modular vices and the belt tensioners. It is running Makita 00700CX4 trim router. I keep the belt tension adjust weekly to 135Hz (C3) for all three belts.

OK… Carveco Maker phones home monthly and any adjustments to the software are carried out by the company. I have not been notified of a major adjustment in recent weeks. I will contact them to try and understand why the software is not specifying the speed, I am entering at the toolpath creation stage.

I suppose the only thing that the developers here can address/resolve is why the buttons on the GUI do not adjust the speed.

Yes, exactly that. I was hoping that the latest gSender version would appreciate a clean prefs file.

Jeff

I’ll have another go , from what I see

your seafinish.nc file is “imperial” and your feed rate is 19.7 inches/min. which equates to 500 mm / min which agrees with what you have said.

However

your searough.nc file is “imperial” and your feed rate is 1181.1 inches/min. which equates to 30000 mm / min

I believe you have some conversion issues. 1181.1 mm yields 46 inches per minute.

Andy

2 Likes

Ha!

I saw 1181 and didn’t even consider that was in/min.
I’d call this solved by @Andy1

I will go back and redo the toolpaths for my design file. If this is a setting I have missed or Carveco has in someway started to decide its own variables, I will be a bit nearer to an answer. 1181.1, while consistent throughout the file is not something I have knowingly set. It is also an odd value for anyone to select. I usually stick with multiples of 100 for feed speeds. 500 doubled is 1000 not 1181.1.

Agreed!

This is a good idea so as to test what is actually happening. I will do this after I have had a quick bite to eat.

Yes, thank you. I will do this in a while.

Jeebus! Thank you @Andy1. I don’t know what has happened there but this has the ring of the solution. I am obliged to you. :smile:

1 Like

Yes, I feel truly dumb. :blush: Thank you for your efforts, Neil.

1 Like

Ok, just shoot me now!
I had measured and calculated everything in millimetres. When I was experimenting with inlays, I was using some imperial measurements initially because that was what most of the tutorial material worked with. My post processor was still set to imperial (:face_with_raised_eyebrow:) when my work was being completed in millimetres. Please forgive me and thank you all very much for the help. It was very much appreciated. :+1:

:roll_eyes:
:grin:

2 Likes

I believe grbl, by default, only lets you reduce the feedrate to 10% of your programmed rate. You’d have to get down to 30% or so to see a difference as anything over 10000mm/min would default to your 10000 max feed.
How’d the cut go?

1 Like

Cut in progress:inexplicably fast so I used Textmate to find and replace all instances of F15000 and F30000 with F500. Only the roughing path had this error.The finishing path had f250 and F500 throughout. This is a very fine bit ball end bit with a 4.9 degree cutter angle and a ball end of .25mm radius so I do not want to break it.

Roughing first few lines…
%
(SLrepairedrough)
(STOCK/BLOCK) (X=185.000, Y=182.000, Z=50.000)
G90 G94
G17
G21
(Tool Number:510 6.350 mm dia. slot drill)
G28 G91 Z0
G90
T510 M6
S10000 M3
G54
G0X0.000Y0.000Z5.000
(SLrepairedrough)
G0X38.142Y37.059Z5.000
G1Z-0.979F15000.0. <------------------
G1X38.451Y36.754F30000.0 <---------------
X38.758Y36.447
X39.160Y36.042
Y37.660
X37.515

I will check with Carveco support to see how that is caused.

It all appears to be fixed now! Thank you gents. This is the completed roughed piece and tomorrow I will machine the finishing touches. This is almost a 7 inch square x 2 inch deep block of Ash. It is a really lovely wood to work and is tolerant of quite a wide speed range. I was feeding from 3000mm/min down to 500mm/min. . I set the base speed to 1500mm/min so that I could increase or decrease it over a wide speed range. The GUI buttons worked correctly.

1 Like

As the original issue has been addressed, I’m closing this topic. If anyone else has a similar concern, feel free to start a new topic, which will ensure that it is addressed promptly.