cmcgrath5035

Can you describe what this does to your Gcode file?

My guess is that with “allowedCircularPlanes = 1 << PLANE_XY;" early in the Gcode file is a G17 command, which sets XY as the arc plane. So then, does "allowedCircularPlanes = (0 << PLANE_XY) | (0 << PLANE_ZX) | (0 << PLANE_YZ);" result in a Gcode file with all G1 moves, no G2 or G3?

I have no hands on experience but have considered these to be interesting

Have a browse over at https://plus.google.com/communities/110852928951643236736
Many Ox builders use external drivers.
You should see many likes over there.

You seem to be aiming for high power stepper performance, therefore suggest you investigate 48V supply for the drivers (but not tinyG). Or 36V.

Good lists as a summary.

I assume you realize that may of the items listing are really different ways to say the same thing. Helical plunging is a special case of G2/G3 moves, in three dimensions, Slight arcs result in large I,J values.

Manipulating large numbers will result in the loss of fine precision

I’ll assume you are running tinyG FW 440.20, that is the most tested version.

There is no complete ‘fix’.
First I would suggest you run an experiment to verify this is the root cause.

The only known full(?) fix is to tell Fusion to not use G2 or G3 arc commands, which causes it to generate very short G2 linear moves.
This slows down the milling process and can result in very large Gcode files, but does work.
I am not sure how you set Fusion to do this.

If an all-linear-move file is way too big, perhaps you can generate a sub set of your complete job to test, first with G2/G3, then with just G2 moves.

• This reply was modified 6 years, 1 month ago by cmcgrath5035.

My read (moderate, not deep dive) of the info on the Amazon listing finds no mention of a PWM compatible input.
From comments made by reviewers, it is hard to determine what documentation you get with the unit. That said, some of the reviewers seem to have figured it out and are please with the results.

tinyG has three spindle control outputs, On/Off, CW/CCW and SpinPWM, a variable duty cycle pulse train that varies the torque generated by the spindle and therefore its RPM.

The typical(default) VFD controller interface is an analog voltage in the range of 0-10V, I believe.
It is my understanding that Machx interfaces provided an output for VFD control, so I am confused by the comment that MACH3 is not compatible with this unit.

It is possible to convert the tinyG SpinPWM signal to an analog voltage using an external filter circuit and perhaps an amplifier. The tinyG output is 3volt logic.

I figured out my issue. It was the Travel per Revolution ($4tr in my case). It was set to 360000.

That is why I suggested a $$ listing.

Good to hear your are up and running.
Interesting looking machine, Happy Milling

Can you disconnect the Z motor from the load and check that you get same result unloaded?

$$ listing would help maybe

Create a Parameter list ($$ command, copy to a text file) which will answer a few questions. Add that to your dropbox.
When you say Z axis mechanically moves smoothly, do you have a way of manually rotating the Z Stepper ?

One possibility is obviously a bad stepper.
Did you check A and B winding continuity with voltmeter?
So lets say the X stepper is working properly.
You could swap wires from the Z motor and the X motor at tinyG end, just to see if perhaps a driver is not functioning correctly on tinyG.

How many steppers are there, 3 or 4?
I can only see what looks like a stepper at end of gantry.