Advanced Search

Actually I just ran gremlin/qt5_graphics.py with Axis running and other than the offsets not being used it plots, just need to figure out how to use it in my GUI.

Thanks
JT

I have looked st gremlin/qt5_graphics.py and will look closer at it.

Thanks
JT

Thank you; as always I should have read better the manual "Daughtercard specific pinouts can be specified by adding dbname3 cardname to
mesaflash’s readhmid command:" Can I ask you why it's named db3 as there is only one header ?

Not sure which paper you are referring to but I have this matrix for rotation around Z:
 

which seems to correspond to your version.

Do you know if any other control has a paradigm for this? Other than defining ad-hoc planes for each arc, which seems clumsy. 

i don't, the only way to produce arcs in arbitrary planes i know is the tilted work plane feature (ie G68.x and affiliated  gcodes).

I thought of a similar but different idea, a board with headers for stepsticks (etc) and for a Pi compute module 4.

But I didn't get any further as I don't actually need one.

By coincidence I found an example of the use of gcode.parse in a post I replied to earlier today:

forum.linuxcnc.org/38-general-linuxcnc-q...code-preview-as-json

Aciera wrote:

[edit] actually looking at the code in the commit the idea was to give the end coordinates the center and the normal so everything is defined.

You only need the normal if you want to retain the concept of CW and CCW. If you say that all arcs need to be less than 180 degrees then the start, end and centre define the plane unambiguously, and the defintion that it always chooses the shortest arc defines the direction. 

That does mean that full turn and multi-turn arcs are not supported. 

Do you know if any other control has a paradigm for this? Other than defining ad-hoc planes for each arc, which seems clumsy. 

There are some things you don't understand in your paper. The matrix rotating around the Y axis or Z axis should be like this  picture . I think these two have been reversed?

Have you looked at gremlin/qt_graphics?

I'm trying to figure out what gcode.parse and gcode.calc_extents does and how to use it. I've been grepping and searching for examples but I've not found out the syntax and what is returned.

Not much help there...

With axis running and a terminal open and running python3

grepping I find this example in src/emc/usr_intf/axis/scripts/axis.py:1589: 


So what I'm trying to do is display g code on an PyQt QtOpenGLWidget... I think I should be using the glcanon.py from lib/python/rs274... but not sure. I've been thrashing around for a couple of weeks and have not made any progress. If someone has a clue please let me know.

JT

That's great!
For the tmc2009 I think they can also be configured via the same jumpers as the a4988 but you need to change a resistor on the board (same come with it)

Worse case program it with a ch340g or an Arduino... Maybe just have the headers for an Arduino nano one could add if needed?

Alrighty will look into the source code and give that script a shot in the meantime.

What's interesting is I was able to get it working yesterday in 2.9.2. Same gcode as before. So something happened to break it in 2.10.

Have a few quality of life questions regarding the a axis

How do you increase the jog speed? I've set it in the default angular velocity in just about every location I can think of (display ,traj, kin, etc). Stuck at 1 degree per second.... Might add another slider for A.
Is there a keyboard shortcut to jog a?

Does THC work when tube cut is 1? I tried it and it just dove into the pipe. Probably needs some tuning on my end.


Finally is their a way to make the display more relevant? Right now just displays a line in the xyz and the "cone" revolves around that line for the a axis. Kinda hard to see what line it is on.

Thanks for all the help!

The micro step ratio does not affect the minimum timing
specifications, but a higher micro step ratio will require
a higher step rate to reach the same velocity.  This higher step
rate (and the minimum timing requirements) may limit  your
maximum velocity if you choose too high a micro step ratio.

In my experience, micro step ratios > 32 or so are not useful
as the magnetic aberrations in the step motor and current
control accuracy in the drive dominate the position accuracy
and torque ripple values at higher ratios.

So all this got me to digging a bit more which has lead to a few more questions. lol

In some reading i saw the same control signals when micro stepping is applied, and it appears the more micro stepping the more (chunky) the line becomes. Does micro stepping affect the step on-time and step space settings?

And kind of related, which is my current setup is set for 16 micro stepping and was set this way when I ran Mach 4 and I wound up going with that setting because my movements weren't smooth enough to maintain smooth cuts. granted I was in MACH4 but should I change to a different setting or am I fine leaving those drivers the way they are?