Advanced Search

In fact, with torque control, I don't think Linuxcnc is up to the task, you should choose OMRON..... PMAC controller.

Usually, the controller with a position closed-loop, the generation of following errors, and the PID controller of the upper computer, has little to do with it, because the position loop can be adjusted in the drive. At the same time, the following error = the maximum feed speed is proportional to the position loop gain

You should get the vendor's ethercat definition, which provides the scaling function....

Oh so those are now all in one file?
There were 3 back then, quick start, documentation and integrator's manual.
I recall thinking "how is this software under 5MB in size while documentation is nearly 30MB???"
Good times.

Just a heads up. Tommy's link is to Linuxcnc v 2.6 and our release version is now 2.9 so it will be obsolete in places.
The PDF files are available from the Documention page but are just a copy of the content in the HTML version which I tend to use in preference,
But none the less I too was gobsmacked when starting off to find the documentation runs to 1347 pages!
2.9 version: linuxcnc.org/docs/stable/pdf/LinuxCNC_Documentation.pdf
 

Can you post your config files?

What part worked?

The motors will move even if the TMC doesnt configure. motor0 and motor 1 are connected to the same output buffer, if the buffer is damaged motors0 and 1 wont get the enable signal it looks like

Hi. Thanks for your help after a new cable this is now working.

However I noticed and issue with Stepconf wizard. It will not allow you to have multiple outputs as enable. If I set pins on the second breakout board to enable those setting are not reflected in the HAL file. However If I manually create the line for port1 then enable works on the second card.

Unsure if this is correct behaviour. This may also be why I could not get the Breakout board working. Just possibly a trap for new players. It is tempting to use enable as the test for the breakout board as you have access to switch it from the main panel without running any gcode. But without manual intervention this will not work.

Thanks.

That last piece of the puzzle did it !!!!!!!

It now  launches, embedded.  

Thanks so much for all the help !          Hopefully others will benefit from this adventure.

The Nativecam looks to be a newer version than the one I have been using.   Now I have to get current with the changes over time.

 

 

EMBED_TAB_COMMAND = gladevcp -x (XID) -U --catalog=mill/usr/share/linuxcnc/gladevcp/NativeCAM/ncam.ui

It should be in curly brackets {XID}.

Regards
Giovanni

I have been hoping that BecksVill (Andrew) would return, he has the same issue as me (Tab but empty) Unfortunately he has not been in the forum for 15 days

Thanks a lot, it kinda works now or at least i can move the motors. Only weird thing is motor0 and motor1 aren't working but the other 6 do, so that's a good thing i guess.
Oh and sorry again for my stupid questions.
see ya

Thanks for all the help !

I inserted the space that you pointed out.          Same result, NativeCAM tab but it is empty.

I launched in terminal by typing Linuxcnc and then selecting the axis simulator

Below is the terminal window messages.       I see a couple issues but don't know why.

Below is the terminal window messages,  I see a couple issues but do not know how to resolve them.
I also included the ini file.

 

 

Start with the HAL part, that is what most people seem to be scared of, but it was and is the main reason why i liked LinuxCNC as you can do almost anything with it, within reason.
And then there is components, plenty of those included and the ability to write your own to fit your needs, so the possibilities are nearly endless.
As for 342 pages, nah, i'we read much longer not enjoyable, while this was very, very enjoyable/interesting.
It opens a whole new world of possibilities.
Does the Z have limit/home switches?

Max_velocity in the ini file is in units per seconds (mm or inch), while everything in GUI is in units per minute, hence divide or multiply by 60.
The error you are getting is because you are requesting higher step rate than possible given the base period in use and timings for the software stepgens RPI uses, so you have to lower the step rate, or use less microstepping on the drives to get more velocity, but this will make more vibrations al low motor speeds. Still, do give it a try with microstepping at 4 and step scale.....
Step scale is motor steps per rotation multiplied by the microstepping value and divided by the pulley tooth/diameter/tooth pitch, in your case for a normal 1.8 degree per step motor that is 200 steps per rotation of the motor and pulley since it's directly driven, multiplied by 8 microsteping in the drives and divided by 20 tooth of the GT2 (GT2 is 2mm pitch between teeth) or 40mm
200*8=1600/40=40steps per mm for metric machine.
If you do set the drives to 4 microsteps, the scale in the ini file has to be changed to 20.