Advanced Search

forum.linuxcnc.org/18-computer/54369-use...ernet-boards?start=0
-
Lenovo X220 and T420S are utterly useless for LinuxCNC so stay away from them.
And as usual, there is absolutely no guaranties that any of the ones that work for me, will also work for you. I had 2 of the same Acer laptops, one was very good, one utterly useless, despite being the same model number, but had different processors.

Hallo zusammen

ich bin Neuling auf dem Bereich Ethercat im LinuxCNC. Eine Installation habe ich bereits zum laufen bekommen. Die Ethercat-Geräte werden erkannt. Nun versuche ich das ganze noch im LinuxCNC zum laufen zu bekommen. Stichwort, Hal-File und Ethercat-Config. Kann mir das hier jemand erklären? Das ich das Configfile anpassen muss ist mir klar. Nur was wie und wo? Welcher Eintrag steht für was usw…
ich hoffe mir kann jemand helfen.

ich habe diverse Bechoffkomponenten und Lichuan Drives, Servos und einen All in One Motor.
Warum Lichuan? Ich habe mit diesen schon erfolgreiche Projekte im TC umgesetzt und bin eigentlich sehr zu frieden. Nur im LinuxCNC hab ich noch nicht verstanden.

freundlich Grüsse und schönen Tag 

andypugh wrote:

pncconf does call mesaflash so if you don;t have mesaflash that might explain why discovery is not working.

Does "sudo apt-get install mesaflash" work?

Did you manage to create a config in Debian 12? If you did, then that same config should work in 11.
 

Hi Vector, tommylight and andypugh,

Thank you for the trouble-shooting discussion on Unspecified Error with Discovery option.

My computer is Raspberry Pi 4, Debian 12 Bookworm, the Kernel is Linux picnc 6.6.59-rt45-v8-behai-rt-build+ #1 SMP PREEMPT_RT Sat Nov  2 10:20:46 AEDT 2024 aarch64 GNU/Linux.

I am also able to ping it at 10.10.10.10, and I did have the same error when used Board Discovery.

Failing discovery, I selected:

[
Board name = 7i96s-Internal Data
Firmware = 7i96s_d
]

It appears to work, since I can move to other screens... I was not able to proceed any further, because I don't know what to do next yet.

Then I retry by running sudo apt-get install mesaflash, and afterward Board Discovery works:

[
Board name = Discovered: 7i96s
Firmware = ~/mesa0_discovered.xml
]

I am happy, this is a progress for me. I have read the configuration the HAL parts of the manual. But it still not registered yet... I have to do some more reading.

And also I have to learn how to connect the CL57T-V4 closed-loop motor driver the 7i96s.

Thank you and best regards,

...behai.

 

hello,
i would like to know if it is possible to send me a complet list of a material that you use with refenrences. Because for exemple, i have a lot of difficulty to find a sensormotor and sensordriver Delta B3 750W X/Y, Delta B3 1000W Z and Bosch Rexroth C5 ballscrews with preloaded nuts. If you have a websites to order all materials i'm interessed.
Thank's

blazini36 wrote:

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?
 

The width is set here based on the width of the longest item. I'm working on making that an ini selection to turn that feature on but I need to fix the touch style sheets sliders to work as expected.

JT

blazini36 wrote:

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 implement since it's written directly into the main qss.
 

Yes, touch style widgets are defined in the qss file.

You can only apply style to a widget once AFAIK the second time over writes the first time.

I added the themes to the examples so they are easier to find.

I've possibly improved the docs about themes.

JT
 

Wild guess, as I haven't looked at all, but it may be related to the compensation logic (used for backlash etc) - as I remember it's hard coded to allow 200% accels to fix position errors and is used for example for backlash and mapping and could cause such behaviors if it is involved in some way.

Hi,

I feel you pain, buying this kind of hardware as hobbyist through the big reseller in Europe was a challenge for me too. Many reseller aren't really interested in hobbyists.

I ended up purchasing my X/Y/Z servos from this store on AliExpress (seems to be no longer active): topstock.aliexpress.com/store/1155094

The spindle servo which I purchased later is a special high RPM version which nobody had listed online. After asking many sellers I finally got one to add it to their store (ignore the photo in the listing as it's showing the wrong servo): www.aliexpress.com/item/1005007120864062.html

The balls screws where the same story eventually however I was able to make a special order from L-system here in Sweden (l-system.se/) who sold me the ball screws and machined them for me.

Most of the smaller electronic stuff was bought from www.tme.eu which had the best prices and lot's of items in stock.
 

@Hmnijp,

Thank you for contribution.
Will first look into the joint.0 & joint.1 velocity spikes. As the planner is
not involved in calculating these values.

@Beef,

I already tested a spline using deviation.
I like the idea of Hmnijp, the industrial example.
 

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.