Advanced Search

I used the same exact values for my AXIS setup. I didn't randomly guess them, they operate well on AXIS. My whole machine worked with GRBL for 2-3years straight no issues, i just couldn't achieve THC with GRBL & would sometimes have issues with EMI.

Setup:
7i96 with THCAD-10
Nema 23 495oz motors(1.8degree , 3amps max) with
TB6600 drivers(running 1/4 microstepping at 3amps max) (i will upgrade them later after i sort this out), two 36v supplies(10amp each),
SFU1605 Ballscrew on all axis'. 

(It was a somewhat budget build)

My stepper scale is perfect at 2032, max velocity of 150in/min(~3800mm/min) and max accel of 50inch/sec^2 (~1270mm/sec^2).

I've played around and purposely made the machine loses steps and it happens around 200 inches/min, 180 it stabilizes and 150 is what i chose as extra margin of safety.


I only used chatgpt for coding questions or how to edit bios etc, my master's degree is in AI (i'll be done in May 2025); Ironically I'm struggling to figure this one out..lol , but i will not give up ! Even if l have to read the whole entire LinuxCNC PDF and QTplasma documents or learn how the code itself works, i will do it!

 

 

mal136 wrote:

...the machine moved but the stepper motors just kinda danced back and forth they didnt actually move the gantry at all. 

Any advice on why that is occuring?

Probably because the scaling, velocities and accelerations are not set properly.
My advice: Stop using chatGPT, it can not help with these types of issues, yet, set the values properly in PncConf, not just random values. Read about how to get those values right based on what you actually have on your machine.
Or take some pictures of the machine and upload them here, we can figure out a lot from pictures.

I changed the "servo period" to 1000000 and i re-did the config using PNFconfig and the machine moved but the stepper motors just kinda danced back and forth they didnt actually move the gantry at all. 

Any advice on why that is occuring?

My jitter went up a lot for some reason and was measuring 46060 for servo thread and 44293 for base thread.

Do i have a hardware issue with my computer ? I'm reading through the linxcnc documents and QTplasma docx as we speak but it doesnt really dive into some of these issues so im a bit lost on what i can do to resolve this.

I'm sorry to be a burden and i hope it doesnt come off as annoying but im really trying my best here , dedicating hours of trial and error and endless chatgpt questions to learn.

Thank you again everyone for your help, this is my first linuxcnc machine.

I'm genuinely confused how AXIS works perfectly fine and QTplasma doesn't operate as it should, any idea why?

forum.linuxcnc.org/18-computer/44828-rem...rd?start=1380#286200

Was this what you were referring too?

Hatte noch was vergessen, das gehört auch noch mit dazu 

Danke für den Tipp, flipflop hats gebracht 
Hier die Lösung für meinen Einsatzzweck mit 2 Tastern und einem Relais zum Schalten von einem Pneumatik-Magnetventil:

Vielleicht kann es ja jemand brauchen.
CLOCK wird, wie man sieht, nicht gebraucht.


Viele Grüße
Olli

Ideas... not sure if its even plausible yet, just thinking out loud.

Need some more info:
-parallel port or Mesa or something else?
-where did you get the info about loadrt gantry thing?

I just realized that the 3D probe is normally open and Z probe is normally closed. 


Can it still be connected to the same input pin? 

I use a parallel port card and I don't have any more free inputs......

Hi Arciera,

the ./installer script seems to fail every time.
But ./build_lcnc && ./start_lcnc works fine. Maybe the problem is in ./deps_lcnc.

The custom trajectory planner component "tpmod.so" has already some logic inside now.
It is succesfully linked to multiple libraries. link.

It can load the gcode file using "tpAddline" & "tpAddCircle". "tpAddRigidTab" is also used, but later on we have
to talk about implementation properties like synchronised motion for tapping, wich are unknown for me now what to do.

This all then is stored into the vector library.

During loading it add's also empty fillet segments to the vector library and creates the fillets using the filletizer library based
on the given G64 values.
In the same flow the motionizer library calculates optimal trajectory velocity's using curvature extrema's, vm's, lenght's.
This optimalisation is done every gcode load cycle, as i don't know how to do it else. It's a fast algo, so i think it

Then step by step we make progress to the code.
We can decide if we use a max buffer size for our vector library. For example buffer 500 segment's max.
This is more or less how lcnc it does at the moment. We can also decide to make a ringbuffer. A buffer with
250 segments in the past and 250 segments in the future.


 

Hello there!
I have recently mostly finished my CNC mill. It is a 3 axis moving gantry, with two motors on the Y axis.

After lots of troubleshooting and learning about linuxcnc, I finally (!) got all 4 joints to home.
I can jog X and Z as I should be able to, but with Y that's a different story: only one of the Joints moves during jogging.
After only implementing the 4 joints and declaring joint_1 and joint_3 as Y in the ini didn't work, I tried adding loadrt gantry [.....] . The syntax with this one is a hassle. About 3 hours later I got linuxcnc to post with it, only to find out that it didn't change anything at all.

I can later (got them on a thumb drive right now) post my .hal and .ini if that helps. Maybe someone knows an answer already.


Thanks to you all in advance!

I've just moved from the Premt-rt to the rtai kernel, using the above method and uname does show the rtai kernel is loaded, so all well there I think.

LinuxCNC program opens, is there a way to check I do have Linuxcnc for RTAI kernel?

Stepconf wizard opens.

Latency Test does not open.

None of the docs open, I did get this message
"An error occurred. The following details are provided: E: /tmp/apt-dpkg-install-u3Rr2j/00-linuxcnc_1%3a2.9.3_amd64.deb: trying to overwrite /usr/share/applications/linuxcnc-documentation.desktop which is also in package linuxcnc-doc-en 1:2.9.3"

In case it's relevant,  I didn't manage to load linux.image using the dpkg command, so used 'Linuxcnc' in synaptic package manager.

Not sure how to resolve these issues?

Unless you want to change the matrix_kb component,
this is probably most easily fixed with some hal logic
(lut5 can do this in one step)

another question on this topic:
is there a way somehow to set up matrix_kb (or do some magic in HAL) to forbid to read any other buttons if one is already pressed? For eg. to avoid unexpected behavior of chip conveyor if both forward and reverse buttons are pressed simultaneously.

Thank you.

Thank you both, I replaced U5 and U7 and my machine is working again.