DDCSV1.1 4 Axis controller

The Shop > CNC

<< < (165/202) > >>

Will_D:
Looking at the code the ParserGGroupnn procedure names are based on the Grouping of gcodes. This was defined by Fanuc a long time ago!

Group 1 are the movement commands G00 .. G3
Group 2 is the Plane selection group G17, 18, 19
Group 3 is the Dimension mode G90, 91
Group 4 is the units group G20, 21

Group 7 is the Cutter Radius Offset group (G40, 41 and 42) and so these may be implemented.
Group 8 is the tool length compensation set (G43, 44, 49) and so may these.

Group 10 is the Return Mode group G98, 99
Group 12 is the coorddinate system G54 ,, 59 and it looks like G53 is oresent (technically in Group 0 the non modal commands)

Will

Benedikt:

--- Quote from: Will_D on January 08, 2018, 10:23:34 AM ---Looking at the code the ParserGGroupnn procedure names are based on the Grouping of gcodes. This was defined by Fanuc a long time ago!

Group 1 are the movement commands G00 .. G3
Group 2 is the Plane selection group G17, 18, 19
Group 3 is the Dimension mode G90, 91
Group 4 is the units group G20, 21

Group 7 is the Cutter Radius Offset group (G40, 41 and 42) and so these may be implemented.
Group 8 is the tool length compensation set (G43, 44, 49) and so may these.

Group 10 is the Return Mode group G98, 99
Group 12 is the coorddinate system G54 ,, 59 and it looks like G53 is oresent (technically in Group 0 the non modal commands)

Will

--- End quote ---
Thats interesting. I was not aware of that.
Thanks for sharing! :thumbup:

WeldingRod:
Progress! :thumbup: It turns out that the parameter:
5 Min. log. radius in 4-axis mode
Translates to: divide maximum feed rate (and probably acceleration) by 360 * pi* this number to get degrees per minute on the rotary axis. FYI, I'm guessing on the constants. What I actually did is test at a log radius of 5mm, 55mm, and 555mm. 5mm was so fast the motor lost steps unless I set FRO down to 20%. 55mm was slow enough that 100% FRO didn't lose steps. 555mm was even slower.

HOWEVER, I'm pretty sure it doesn't pay any attention to the F command WRT the rotary axis, at least alone. I need to play with some coordinated motions more.

WeldingRod:

--- Quote from: Will_D on December 01, 2017, 09:57:42 AM ---Back to Backlash Basics.

Has anyone used this on the version 1.1 controller and the 16-04-17 software?

I know I have about 0.1 mm backlash in X and Y

If I run this code

G17 G21 G90 G94 G54
(^Safe Block^)
F 2.
S 10.
G1 X-1. Y-1.
G1 X0.
Y0.
G1 X10.
Y10.
G1 X0.
Y0.
M30

--- End quote ---

A quick question on the Gcode above: is the F 2 line the correct syntax? Or should it be G1 F2, or G1 F 2? :scratch:

lordprimoz:
Hi Guys,

when running gcode on my machine I have this really werid issue where there is a significant deviation in the actual position(as well as the position it shows on the display) and the position it should be according to the gcode.

im trying to mill a vacuumtable, which is basically a milling grid pattern where i step down 0.1mm for each level.
Fusion360 generated the gcode for this project.

I noticed that (it seems to be in all axes) the z-axis has this weird difference. for example: the gcode tells the machine it should go to -0.8mm on the Z-axis, but it actually only goes down 0.774mm. After moving up and to a new spot it moves moves down again. This time its also different from the previous value. This might be something i would expect from (failing?)backlash settings, but these are all disabled and set to 0.

So essentially the machine starts and moves to a xy coordinate, then it moves down (gcode Z-0.8) to -0.7xx. When it moves up again to its safe position and comes back down the z-depth is no longer the same as previous, even though this depth was already wrong.

When telling the controller to move to a certain z-heigth from the display itsself it does indeed move to exactly that position....

Anyone got any ideas what is causing this?

Navigation

 Message Index

Go to full version