Advanced Search

You want to attach those two files here? Or you could also open an issue on my github repo and attach them there:
github.com/Sigma1912/LinuxCNC_Demo_Configs/issues

Hello, does the N4D3E16 test work correctly? I'd also like to order one to try it out.

Aciera wrote:

Exactly. The other problem is that there are some people who have their work inside the code base and think that they now 'own' 'their' part of the code and are thus above having it reviewed.

Also I _very_ much hope that LinuxCNC as a project has moved past the stage where somebody can 'just add' a new GUI to the master branch.

I see you're keen on taking things out of context and bending totally unrelated words. No worries. Here's the context for anyone who cares:

sourceforge.net/p/emc/mailman/emc-develo...OOK.COM/#msg59393097

github.com/LinuxCNC/linuxcnc/pull/4580#issuecomment-5833848754

github.com/LinuxCNC/linuxcnc/discussions/4566

I never purported to 'own' anything, nor did I ever call QtPlasmaC 'mine'. I believe quite the opposite in fact, PlasmaC and QtPlasmaC are the product of everyone who contributed to it over the years and there have been many. It's true that I hold the distinct privilege of being called one of the "maintainers" of that portion of the LinuxCNC project. Which is traditionally how GUIs have been handled.

I feel very strongly about the work we've done; I'm proud of it in a way I don't expect you to understand. The complete ignorance and disregard of not only the history but also the literal thousands of hours of coding, painstaking reviews, diffs exchanged, emails, forum posts, spreadsheet bug trackers, passionate debates, ideas, time spent in front of a plasma cutter, etc. is ... disappointing.

Similarly it's what disappoints me about the way Chris was treated.

I apologize JT, you may have your thread back.

Hello,

The issue I was having with the checkout page was resolved by the webmaster.

Regards,
Brennen

And actually if you thing about it Flex GUI "is" a plugin for LinuxCNC.

You install Flex GUI using your favorite method apt, gdebi or command line and set the DISPLAY = flexgui it can't get much simpler than that.

JT

So to get back on the subject of Flex GUI it is the only GUI that is very flexible and requires no programming to create the exact GUI "you" want without knowing anything about programming. If you just have one axis that's not a problem, Flex GUI can be as simple or as complex as you want. No other GUI is easy to change the look and feel and function for a non programmer.

JT

There should be halui pins to do want you want to do. The halui docs say " halui is used to build a User Interface using hardware knobs and switches."
But over time I have found some guis use these pins which stops you from using them. guis don't have hardware knobs and switches so they should respect the boundaries of the original LinuxCNC design intent. I don't know if your GUI is using these pins or not.

I was looking into this as well. I have a 7i73 board to use in the control panel, and google AI was pretty helpful in getting me pointed in the right direction. I have not completed the project though.

by the way, i was looking at using encoders rather than pots. because there could be a disconnect between the pot position and what QTdragon is expecting it to be when the machine restarts.

Is the noise on the analog wiring side or the encoder side?
Are the original analog cables in use? If yes, those will have an analog ground and a general machine ground, should not be wired together, although i had a single case when it was a must.

BSAT wrote:

It doesnt change with feeds or speed changes or end mill changes. Its always there.

Does the rastering change with those changes?
Might want to try with a single or dual flute on some aluminium with the same high spindle speed and different feed rates to see if the distance changes, in general, if it does change would point to servo/tuning issues, if it does not would mean mechanical issue.
Would be nice to also do same feed rate, but vary the spindle speed.
Thinking of it, at what spindle speed are you cutting and what mill? I might have missed that.

Henk72 wrote:

@ the forum moderator: feel free to remove my question above.

Leaving it for now, we can decide later if it would be better to leave or delete.
Thank you.

Dear forum,

I found more information related to what I am trying to do on section 2.8 of  www.linuxcnc.org/docs/html/gui/qtvcp.html#cha:qtvcp  . I will first try to go through these sections and see how far I can come...

@ the forum moderator: feel free to remove my question above.

Hi guys,
I am trying to get my A6 servo up and running as a spindle in PV mode. UI is QT_Dragon. I am using the cia402pv library. I can't get the motor to move... I used the example from the github page... 
control word stays on 4 and status word is 5640... Nothing makes sense to me.
I can see that all the pins are populated... encoder is responding, acceleration increases when turned by hand... 

It would be great if you guys could take a look at if for me. 
    

Dear forum members,

I am progressing well with the conversion of my 1980 MAHO MH300 to a linuxCNC based machine. I made a replacement console consisting of a high res screen (not a touch-screen) and keyboard + Estop etc. console (see attached image). I copied the layout of the console, including two potentiometers from a DMG machine. On the DMG these are intended for rapid traversal override and feed override. I am now trying to make QTDragon_HD to run and read that this GUI was not intended for keyboard use.... However, I do like the way the QTDragon gui screen is build up and would like to try to adapt it in such a manner that I can set these overrides with the potentiometers. Similar to the Estop I would like to go for an implementation where the console hardware (physical estop button and physical potentiometers) set the hal signals and that the QTDragon_HD GUI only displays (follows) the setting set by the button and potentiometers. For the Estop I think I made this work, but from what I have read thus far I think the QTDragon_HD does not allow these override sliders to be set by another HAL output. Is this indeed the case? I am still quite inexperienced in LinuxCNC, HAL and Qtvcp, maybe I overlooked something. Any help or suggestion is welcome! 

I have reached out & got the updated servo files. But they said it will only help with i templates moves. If im seeing thisnproblem in a straight line then there is a mechanical issues.

I have reached out to clear path & the point me to tormach.

I have set it up per their instruction, its there. I set it up tighter or looser, its there, ive replace contact bearings on the axis, its there.

I autotuned the servos, helped maybe a little. But still there.

At this point I gotta think its a limitation/configuration of the servos that I dont readily have access too. By accident as much as I have messed with, it should have made a difference one way or the other. But it seems to be the same no matter what.