5 axis CNC Router/3d printer

[TomKerekes]

Hi George,

I disabled Master/Slave, configured to use Axis 1 for X and still see the burst of pulses with the scope. These pulses are at 600KHz quadrature (2.5 MHz step rate) so you might just be lucky that they are too fast for the drives to be always seen which may also explain all the intermittent behavior you have on what I see as a perfectly consistent bug. Please switch to 4.35h.

Also switch to 4.35h and see if that error goes away. I'm not aware of any such error message. What is the error exactly?

[George Butty]

Hi Tom ,installed 4.35h and still have the same Gcode Error pop up when trying to run a Gcode. Attached Picture.

George

[TomKerekes]

Hi George,

That error is caused when the Axis Resolution for an axis is zero which causes a divide by zero. Sorry for the poor error message where changing that. Also avoiding the issue for axes that are not used.

[George Butty]

Hi Tom, got ride of the gcode error. Tried to run The attached RTCP code but came up with attached errors.
So far no motor faults running Ch1 and no Master/Slave.
George

[George Butty]

Gcode error came after buffer error.
George

[TomKerekes]

Hi George,

Did you hit Halt when that occurred?

[George Butty]

Hi Tom, no I did not hit Halt. Just started RTCP code that I sent you and it went as far as the B45 line and then kicked out the buffer error
and after I cleared that error the Gcode error popped up.

George

[TomKerekes]

Hi George,

I believe that is a bug. I was able to re-produce. Basically the Trajectory Planner was attempting to "Round" the corner on two Pure Angle moves (without any motion).

Here is a patch for Version 4.35h. Copy to the \KMotion\Release folder.

GCodeInterpreter.dll

Here are two source files that were changed in case you re-build the Libraries. Copy to the \GCodeInterpreter folder.
TrajectoryPlanner.cpp
TrajectoryPlanner.h

Please let us know if it fixes the issue or causes any problems.

[George Butty]

Hi Tom, just tested the new files. All the axis are moving relative to each other but it seems
the H ( tool length value) is not being read. The end of the tool is sweeping in a large radius instead of around the point of the tool. I have not set the Chuck length value yet. My value would be close to that 7.875 value you have now and it was running very close to center in the 4.34 ver. with a 4.25"
offset value which I am using in this version as well.

George

[TomKerekes]

Hi George,

Are you saying RTCP was basically working with Version 4.34 but not 4.35h?

Is RTCP working at all? That is, with a pure angle move are XYZ moving at all?

What GCode are you running?