Advanced Search

I think this issue with the deviation being higher than the P value specifies may be resolved in the correct_trim_length() method, by calculating the angle between the segments and calculating this max_trim so that it doesn't exceed P. I have to do some more digging in the meantime and wrap my head around this.

The code is very readable and well commented.

I copied out the Qlistwidget from the touch theme to my qss and it works pretty much the same as the touch them but I noticed the same problem on both......

If you hit a directory with a file name that is too long it will resize the Qlistwidget horizonally and push the scroll bar out of view. Any idea how to fix this?

hello,
I would like to know if it is possible for you to send me a complet list of all product that you use with references. Because for exemple i have a lot of problem to find a Servomotor and Servodriver Delta B3 750W X/Y, Delta B3 1000W Z and Bosch Rexroth C5 ballscrews with preloaded nuts.

DDRAFT4x2.comp

This one is designed to drive the air side of a zoned downdraft plasma table with 8 zones (2 in x direction and 4 in y direction)
the extraction duct has shutters triggered by an air solenoid so this is output pin heavy!
 

And a hal file you can add to your ini file. We found  adding an off delay which leave 2 zones open when crossing a zone boundary worked well.

 

Forum thread for pictures of machine is here 
forum.linuxcnc.org/plasma-laser/40517-do...ions?start=10#188738
 

JT wrote:

Sorry missed one of your questions and yes the touch screen file browser is here
gnipsel.com/linuxcnc/flexgui/touch.html#file-navigator

JT
 

Lol I think were moving past each other here. I see that "theme is checked first". I also have file_lw, I have the browser....that's not the issue.

The thing that is not really clear is that you can't use a qss file and still have any way to use the touch style widgets. It wasn't obvious until I looked in libflexgui and the python file that the THEME is just a premade qss file and the touch style widgets are just properties in the qss.

So I suppose the best way to have custom colors and the touch style stuff is just to copy the touch THEME qss out of libflexgui and stick it in the config directory, point at it with QSS and just modify it, otherwise it won't survive an update. I suppose this is probably where INPUT was going but that's probably a bit more difficult to impliment since it's written directly into the main qss.

Edit this file
sudo geany /usr/lib/python3/dist-packages/qtpyvcp/utilities/encode_utils.py
Move the koi8_r character set to the first position
For example, if I want it to display Chinese, just put utf-8 in the first place.
 
 

Hello. Good news I no longer drift on my Y axis, however when I turn my axis by hand, I have my scale which is correct to the micron and when my program runs, I have my Y which leaves at each directional pulse of two or 3 mm in positive. I tried to interact on the PID without success. As for the other axes they are well calibrated and no problem, does anyone have an idea of ​​this phenomenon. Thank you for your help.

Tommy has a great thread about using laptops, give that a read. Lenovos seem to be good.

You don't "need" an old computer, but sometimes if you need to get a computer, a used one can be "best bang for buck". I found one on the side of the road, $20 for a 3rd gen i5 and it's fine.

Generally with laptops turning off all the power saving stuff can be difficult.

Kinda

See my other post.

Please delete this if you want and I'll post in the error thread