Advanced Search

Note, for the gcode to reload you need to switch to the 'AUTO' mode screen in gmoccapy.

 



I used the latest I could find
 

Seems likeI lost the hashbang in the first line of the python code in my last post.
I just fixed that, so copy/paste the fixtd python code above and try again.

The kinematic compensates for tool length.

Are you sure you have connected the required pins:

Hello,
I think I'm making a mistake somewhere
The file.txt file is in the config folder, but I think it cannot find this file.

./python/file-check.py: 1: import: not found
./python/file-check.py: 2: import: not found
./python/file-check.py: 3: import: not found
./python/file-check.py: 4: import: not found
./python/file-check.py: 6: Syntax error: "(" unexpected
<commandline>:0: waitpid failed ./python/file-check.py file-check
<commandline>:0: ./python/file-check.py exited without becoming ready

wow, that looks really professional, you can tell it's not the first time you've done it.

I wouldn't know what to say about it either, you're doing really well!

There are easier ways to start playing around with kinematics. I would suggest to have a look at 'millturn', also have a look at the linked paper:

forum.linuxcnc.org/38-general-linuxcnc-q...atic-mechanis#306700

[edit]
Just for completness, 'trivkins.c' uses functions in 'kins_util.c':

 

But again, unless you know your way around with C I would strongly recommend using the .comp method with 'halcompile --install  your_path/your_kinematic.comp' as in the 'millturn' example pointed out in the link above.

Hello, I am a beginner trying to learn LinuxCNC. Please note that not only that I am totally new to LinuxCNC, but I am also totally new to working with CNC machine, G code, and the C programming language, so please forgive me if I ask stupid questions. Since I don't have any lathe or mill that I can experiment with (without messing things up), I am playing with LinuxCNC on a virtual machine (Debian inside VirtualBox). I have successfully managed to build LinuxCNC using run-in-place method as instructed in this guide linuxcnc.org/docs/master/html/code/building-linuxcnc.html .

Right now, I want to understand how .c kinematics files work in LinuxCNC. So, as a first step, I did a little experiment by modifying the inverse kinematics function in trivkins.c (located at src/emc/kinematics/) as shown.

My understanding is that the inverse kinematics translates the position of the tool into joints variables, so by putting a negative sign in front of pos -> tran.x before passing that to identityKinematicsInverse function, I expect the machine to move in -x direction whenever I command the machine with G code to move in +x direction (like G0 X10). 

After I have modified trivkins.c, I compiled the file and rebuild LinuxCNC by going into /src and use  ./autogen.sh, then ./configure, and then make. 
However, as you can see in the photo attached   , when I open axis.ini config (which I believe it uses trivkins.c), the machine still do engraving in the +x direction. Nor did it go to X-10 when I command it with G X10.

I tried modifying trivkins.c in different ways, such as setting some directions to a constant, but I still experience the same result. So what did I do wrong here? Why I see no changes in AXIS after I modified the kinematics files. I am pretty sure the trivkins.c was compiled because when I deliberately put syntax error line in there, make threw an error

This is looking amazing!   I am impressed with how smooth that boomerang video looked!  Absolutely fantastic work my friend!  Thank you very very much for your hard work! 

Chris

Hi all,

This is my first time playing with electronics. I had almost zero knowledge but during the last 3 months I understand quite a bit now. I was quite afraid of it (especially Linuxcnc, I was keeping Acorn ahead because of the ease) but I am quite enjoying it now. I have wired my lathe previously with a printer BOB and it ran successfully. Now I am getting it hooked with a mesa 7i96s card with nema 23 motors and a spindle encoder. Getting a mesa board here in India is quite hectic so I will ask some questions frequently so that I dont mess anything up. 

1. What are the 5V, GND pins on each stepper axis of the Mesa card used for?

2. I heard that you need shielded wires for steppers. So do I need to shield the pulse and direction wires from the mesa card to the drivers along with the wires from the drivers to the motor or just the latter is enough?

3. Even though I searched quite a bit about the enable signal of the drivers, I couldn't land on a decision on how to wire it. I understand that leaving it unconnected or having the pins low enables them and having them high disables them. I really dont want the steppers to be enabled all the time, maybe F1, F2 from Linuxcnc will disable-enable them. Any wiring suggestions?

4. There is a Frame GND on the Mesa card. Do I need to ground it?

Thanks in advance..


EDIT: I now understand what the 5v and GND is for on the mesa stepper axis segments. I somehow missed it on the manual..

My suggestion is to give up ecat-io and look for other solutions, such as mesa card or fpga or arduino (I don't know how fast they are )

Hi. Yes. I'm from RSA.
I have only used the rotary inductosyn  stuff as shown above, but the principle is the same as a normal resolver.

The linear/rotary inductosyn type has a low inductance (as far is I understand) and the mesa or pico products doesn't work for them, bwich is why I went for the farrand stuff.

But as noted by jmelson above, there are products for the normal wound type resolvers from pico, and mesa electronics.

so it depends very much on the rest of the hardware in the machine and if you can re use that. 

the sa-cnc club meetings are mostly online, so you don't have to travel to Johannesburg  to join. 

Reference routing (inspiration) for the above wiz part schematic. I doubt all that analog/digital isolation insanity is mandatory, but some does claim those motion control being noisy [rolleyes], and so best practice always just add them in if you are routing this. All what's left to do is the 3V3~5V translation and hooking up 50 gpios. Tomorrow. Maybe. 

My Riocore Kit looks forward its own faraday cage (EMP warfare protection [rolleyes x2[). Let's get in touch, Olivier - I'll send you one (or two!). 

You may already know this but here is the function qtvcp calls for tool diameter probing (probe_tool_z_diam):
github.com/LinuxCNC/linuxcnc/blob/master...obe_routines.py#L314

Can you describe, using this code where the problem is?
If I understand you properly, you are saying the tool doesn't lower enough to touch the probe on the side of the tool when soide probing in X+ direction.
Does that mean when doing X- probing the tool _is_ low enough?

Chris
 

Can you post the result of

ip a

Maybe  a routing/ip address issue?