Advanced Search

I'll attach more pictures

Thanks for reply my friend, Servo motors are rotating but feedback not showing in display, I don't know where to connect +5v & 0v

Regards
Pankaj

Hello everyoneI'm concerned about the servo-thread.tmax value
I made a lot of adjustments. But I can’t count on getting good results with this equipment.
I collected information in the form of pictures.
I ask you to look and evaluate the result of my work.
Perhaps nothing needs to be done and the result is good.
Either I ask for help on how to achieve a better servo-thread.tmax
I apologize for my English.
 

Looks nice, clean and uncomplicated! Thanks for showing it.

Maybe the easiest is change the INI setting:
[DISPLAY]
DISPLAY = qtvcp -i qtdragon

and run linuxcnc from the terminal.

meister wrote:

i agree that there should be a new modular system so that everyone can incorporate their own ideas.
But this already exists: forum.linuxcnc.org/18-computer/49142-lin...cp5?start=450#308969

that is the opposite of what i am suggesting

Cant do this anymore bye all wrote:

Instead of reinventing the wheel does anyone see an issue with using the standard db25 pinout that used by std parallel port break out boards ?

yeah but they never stopped improving the wheel. the first wheel was probably shit. paraport standard is old n busted and needs to be paraport compliant. thats also the first board everyone already made

what i am suggesting is basically a 7i76 (without mesa smart serial stuff) that reflects the common cnc machine in 202x, what we can just plug our coreboard into boards into and run what ever we want.

but its fine, i see this isnt what we are talking about, i will move along.

Okay, I think it is better now. See beginning of the script for configuration options.
By default it tries randomize window position to avoid burn-in.
You should also hide the taskbar and set black wallpaper to avoid static elements on the screen.
Fullscreen mode is also available.

ohh your code looks so clean

lets help each other out, because my axis mentor has recently resigned

github.com/cakeslob/regularmac_800

i have some other odds and ends for axis if you interested. like the backplot coloiurs and stuff, but it doesnt look like you really need my help

You would typically scale the encoders with a fixed number
with  the encoder scale setting parameter.
Then all the jog increment values for the mux would be the same
for all axis

Hi Cmorley

Since recently, the "DEFAULT_LINEAR_VELOCITY" and "DEFAULT_ANGULAR_VELOCITY" in ini settings have not been working in qtdragon master.

Whatever value you enter, after starting qtdragon it is 15 and 360 respectively

I also have a slightly older version of master 2.10.0-pre0-3309, and it works fine in this version

How do I find the handler file (& what does it do)

Does this mean that qtdragon.external-pause is likely to dissappear the net time I reinstall linuxcnc?

Thanks

song_gy wrote:

Yes, I use it. I think it's a great project.
 

Thanks, I'd love to see screen shots of your GUI you made.

If you need anything added best place to catch me is the IRC on the #linuxcnc channel.

JT

I can only see one output value per selection is possible.

I need these values:

Fast setting: x-scale: 0.00125 y-scale: 0.003125 z-scale: 0.0005
Medium setting: x-scale: 0.00025 y-scale: 0.000625 z-scale: 0.0001
Slow setting: x-scale: 0.00005 y-scale: 0.000125 z-scale: 0.00002

I need these different settings because each axis has a different encoder and because i always want the z axis to move less per turn.

edit2:

 Since you only have 3 options for jog increments you only need
one mux8 component. (any individual MPG PPR related scaling would
be done by a fixed factor elsewhere)

Think of mux8 as a 1/8 selector switch with 8 inputs and one
output and a 3 bit binary code that selects the switch position.
 

Ok, fine! Sure I can. But it's a very light weight implementation. Only those features I need for my use case are implemented. Actually, most time I use the macrotab feature, even more than applying G-code (from FreeCAD).

Yes, I'm also happy that I tried to apply Qtvcp. It fits perfectly my needs and I was amazed how little code I had to write in my handler file.
Thanks a million for this excellent work!

Karin