Advanced Search

I did read, and therein lies the problem, till 1990-2000 it was strictly called Silicium, it was on all periodic tables as such, and i was in school in the 80's and it was Silicium for sure. Somewhere there the transition started, maybe even earlier when integrated chips started to take over based on "silicon valley" name as there were Silicium and Germanium semiconductors, then came silicon chips !!!
some rare examples
www.istockphoto.com/vector/print-gm1363943047-435307903
www.spreadshirt.co.uk/shop/design/silico...ALiZ2ZZN5a3g-1435-32
And that is the only stuff i can find, internet archive does not have much before 2005.

As I stated in my first post (which you must have glossed over or ignored or do I just post shit that only I read), it was named Silicium because it was incorrectly thought to be a metal. It is now Silicon, as it was in the 1980's when I was at high school.

newsroom.lamresearch.com/10-Fun-Facts-About-Silicon?blog=true

Were you at school in the very early 1800's Tommy ?

Another thing people, not reading the full content of a post, even when in red letters people are not told to do something, yet they do and then say "it doesn't work".

Not wrong image. Some people didn't read the opening post completely.

 As stated in the opening post:

All images have been tested on a 4gb Rpi5 bought int Nov-Dec 2023, updated with latest EEPROM. Not official images by any length. It is recommended to use Balena Etcher. Rpi Imager has had issues with the images built by the program suite used to build the images.

That image is depreciated.
Please use the image on the downloads page

www.linuxcnc.org/iso/rpi-5-debian-bookwo...25-01-27-0140.img.xz

Hi! I've tried to install ethercat to the latest RPi5 image, however it does not work, seems to be some kind of kernel mismatch. I've managed to install it and get it working with cornholio's image found here (forum.linuxcnc.org/9-installing-linuxcnc...berry-pi-5?start=310). Any idea what might be the issue? Since I'm doing a fresh install I kind of want to install the latest :) Thanks!

For analog velocity mode servos you can leave the scale at the default value/range (+-10V)
or you can set it so that the PID settings are all in engineering units. To do this, you set
the scale/range to the velocity in machine units per second your axis move at 10V.
This means that  now the PID output is scaled directly in velocity. This also means the FF1
value is known (1.00)

Wrong image as it seems to be nearly 6GB in size.

I get this error message when trying to burn the image

Hallo zusammen,
es geht gerade ein Stückchen weiter.
Die B-Achse meines Schwenktisches wird ja mit einem linearen Kugelrollantrieb angetrieben.
Nun habe ich die Berechnung in der "trtfuncs.c" verändert. Die geänderte Datei ist angehängt.
Für die "trtfuncs.c" gibt es ja die Möglichkeit die Rotationsmittelpunkte der einzelnen Drehachen in der HAL zu definieren.
Das passiert, so glaube ich, in dieser Passage der trtfuncs.c aus der Version Linuxcnc-Version 2.9.3:

// Note: 'principal' joints are used
    double x_rot_point = *(haldata->x_rot_point);
    double y_rot_point = *(haldata->y_rot_point);
    double z_rot_point = *(haldata->z_rot_point);
    double          dx = *(haldata->x_offset);
    double          dz = *(haldata->z_offset);
    double          dt = *(haldata->tool_offset);

Gibt es die Möglichkeit weitere eigene "halpins?" ähnlich des "x-rot-point" einfach selbst zu erstellen?
Die Parameter für die Berechnung müssten wie die Drehpunkte in der HAL dfiniert werden können.

MfG Peter


 

You might want to try a simple ngc remap like this first:

Save this as 'm6remap.ngc' in your './remap_subs' folder

Add this to the [RS274NGC] section of your ini file:

Raw unedited video of assembling the thing, still removing some music doe to copyrights and that takes ages, but the video can be watched in entirety, over 2 hours of it with me ranting occasionally...

Silicium is Si, 14, not silicon.
30 years ago making this mistake would cost your job, now you can not find the correct name anywhere.

Salve Giorgio

How does scale come into play for velocity mode servos?  I see multiple different Scale callouts between the .ini and the Hal files.

From JT's configurator tool, in the .ini there are these values which I currently have defined as:
Scale for drives = 10
Analog Scale Max = 10
Analog Min Limit = -10
Analog Max Limit = 10
Encoder Scale = -634.92 (this one I understand, although might need a double check on the value. Calculated based on 500 ppr with .7875" in per rev of servo)

In the main.hal file, I only see this line referencing SCALE, which I assume to be the scale for drives listed above.  
setp hm2_7i97T.0.pwmgen.00.scale [JOINT_0] SCALE

I also have seen Output Scale referenced in other posts, is this the same as Analog Scale Max?

I set the PWM frequency to 75000 and enabled dither.

Thanks for the help

Hello, after updating 2.9.3 i get this error when starting qtdragon:
AttributeError: 'VCPWindow' object has no attribute 'btn_spindle_z_up_clicked'
2.10pre is starting normal
 

The data path you describe includes almost all of LinuxCNC.

Starting at the end, have a look in src/hal/drivers/hal_parport.c

Or if you want to send binary data, possibly src/hal/drivers/pluto_*