Advanced Search

I am working at tuning some older digital (step/dir command) servos, that don't have any auto tuning capabilities.  In order to avoid needing to use an  oscillo scope I would like to be able to connect a square wave siggen signal to the velocity command input of an unused stepgen on a 7i76eu (I also have a 5i85 for encoder feedback.)  I loaded the siggen, and made the hal connections, set all the parameters and enabled everything from halshow.  I can see the input for the stepgen's velocity-cmd changing, but I don't think any steps are being generated (no changes of any of the stepgen's count or feedback pins.  

Where am I going wrong?  Is this another situation where changes to parameter pins are only effective in a hal file at startup?

I was hoping to just create a little hal file that I can load manually after Linuxcnc was running to set tuning parameters then plug one of the drives step/dir plugs into the testing plug to run the tuning (moving them back to their regular position when running.)

Ah okay gotcha.

Ill plot the mentioned signals this weekend when im back at the machine.
Latency on my host is ~20k with max jitter when opening mulitple tabs max 45k

would lowering/increasing the SyncCycles value help with this?

Hello everyone!
I am currently connecting my two 7i84U and my 7i74 to my 7i97T. 
But i have a few problems with it. 
Can someone please send me the right firmware for that config? I have tried a few and it wouldnt work. Also the encoders stopped working after the new firmeware. Does anyone have a solution for that? The 7i74 and the 7i84U has power. And the leds work.

Great, i forgot to ask that

but normal need use WHITOUT this expensive hat , only gpio pin out and shift level converter can use 3,3V gpio pin to out 5V and traight to driver step and dir and enable pin.
how this made if ewer newer not has understand anything code nd not understand what need doing code, understand only good all hardware how connect and build,
i have rpi4 and SD card have linuxcnc rpi4 image, working and boot ok, (whit HDMI display) but not boot whit pi hut mikro HDMI to vga cable.
how make this gpio pins can take out gpio pin to driver DM556. were can download setting hal and ini file or what need add to rpi4, normal peoples NOT can understand and write hard code to rpi, hal or ini or what possiple need doing, not know.
i just buy rpi4, paraller port BOB, cheap chinese 10$ board, encoder, rotary SW, shift level converter modules, 3,3V to 5V, all buttons, DM556 drivers, nema 23 470 OZ/3Nm motors, lot hardware but not can made code anything.

help need send to me files what need copy and paste to rpi4 linuxcnc and were folder need add. not know were and what and how.

Becksvill wrote:

hey guys

just wondering whats the latest on this.

cheers

andrew

 


Still work in progress

github.com/LinuxCNC/linuxcnc/pull/3807

you can read above, if anyone wants to test what's done so far, they can download the debs from github build artifacts
github.com/LinuxCNC/linuxcnc/actions/runs/22982518117?pr=3807
the above is today's build, scroll to the end of the page for the debs for the different systems, I think I got it to the point where it is in a good enough state for sim testing by the community
To test it set planner type 2, I have included a zip file in this post with my testing settings for planner type 2.
YangYang is refactoring the code, he put planner type 1 on pause because there are certain limitations with TP1 implementation, he cannot reach high speed on short segments.
TP2 will be the general base idea, but much needs to be refactored, the feed override needs to be reworked, kinematics TP and RT servo-thread need to be reworked, there is talk in the github about this, any extra mind is appreciated.
At the moment TP2 generally works, what's still missing from my implementation is spindle sync, I never tested probing or adaptive-feed.
as far as running gcodes and MDI, I believe everything works, but it is far from hardened, it is just me doing testing in a sim, if you put it on your machine, it is at your own risk, play with it in the sim, and let me know how it goes, here, in the gihub PR, or even on my github fork.

They are same

github.com/grandixximo/linuxcnc-ethercat

this just has one small optimization

dc-phased is latency dependent, can you plot in halscope, app-phase, pll-error, and servo thread?

No.
USB pendant goes to USB on PC, not to Mesa.

If i get a USB pendant, do i need to have an MPG interface on the controller board? (like the Mesa 7I76EU) or can i just use the USB communications into the LinuxCNC PC? Not sure if i need to connect the pendant to the PC or to the controller.
Any help would be appreciated.

Thanks.

In Europe, try Grotius Machine Tools, the owner is well known on this forum

The Linuxcnc installer uses Bookworm (V12)
The Debian installer is currently Trixie (V1 3)
Trixie has better uefi support at boot

Linuxcnc installer uses Debian's Live Build which is the same as what Debian uses so its odd
so install Debian Trixie and type sudo apt install linuxcnc-uspace linuxcnc-uspace-dev to get v 2.94 (missing a few minor bug fixes)
Install Debian Sid (aka testing) do the same and get v 2.97 (missing one minor bug fix)
Follow this process  on Trixie or Bookworm and then follow the steps in the docs here to get 2.98 (current version)
linuxcnc.org/docs/stable/html/getting-st...th_preempt_rt_kernel

Der verwendete Zeichensatz war UTF-8 und ich hatte auch mehrere Editoren ausprobiert, Überall wurde der Code passend interpretiert. Gedit direkt in Linux hat ihn auch ohne krytische Zeichen richtig angezeigt, nur im maschineneigenen G-Code Fenster kamen dann die wirren Zeichen zum Vorschein.

Ich hab mir anderweitig auch noch Hilfe geholt, und wir haben den Fehler gefunden.
Wie schon richtig vermutet, war ein Sonderzeichen Schuld an der Misere...
Allerdings nicht unsichtbar, sondern offen im Code zu sehen:
'-' ist im Editor klar zu lesen, aber effektiv gibt's da 3 Varianten davon, den Geviertstrich, den Halbgeviertstrich und den Bindestrich. Der letztere ist in der Darstellung ein Minus-Zeichen. Da die AI in den meisten Fällen (außer sie wird direkt aufgefordert ein anderes Format zu nehmen) Textfiles so generiert, dass sie für digitale Druckvorlagen genügen, kommt je nach Zusammenhang im Text, der Geviertstrich, vielleicht auch als 'em-Slash' bekannt, zur Anwendung.
Auf den ersten Blick fällt das nicht auf, aber wenn man ihn dann unmittelbar neben einem Minuszeichen sieht, kann man den Unterschied erkennen.
Ich hab dann meine Schnipsel diesbezüglich geändert und seitdem funktioniert es so wie es sein soll.

Danke für eure Hilfe und Gedanken!

Freddie

Xnke wrote:

I downloaded the official Debian installer image (not the LinuxCNC specific one) and it ran and installed absolutely fine, didn't even complain about missing firmware, grub installed fine, and it didn't even hiccup once.

That is/was my next question/tip/request/advice!
Thank you.

1. had good and bad experience with some of those companies, and almost (almost) always the machines are made in china.
-Some German companies have smaller machines that are good and do what they advertise, cant recall company names
-i know of a German company that sells machines made in 2024 using RS232 communication to PC (to damn old controller, still being made), it works, i would not sell nor buy such a machine because of that, although mechanically it is nice:
forum.linuxcnc.org/show-your-stuff/55825...ial-connection-to-pc

CSM enabled does not make any difference for my install when using the LinuxCNC live USB image.

I downloaded the official Debian installer image (not the LinuxCNC specific one) and it ran and installed absolutely fine, didn't even complain about missing firmware, grub installed fine, and it didn't even hiccup once.

From here, I'll follow the normal install instructions for installing the preempt-RT kernel and linuxCNC from packages.