Ok Georg und vielen Dank
Ich bin zwa nur auf der Hobby-Schiene in Holz aber es ist die Profiliga etwas ganz anderes wie das Cam von Freecad.


King regarde
Juergen

From what I've measured, the issue seems to be on the encoder side.

I initially thought that analog ground and power/system ground were connected. The original cables are currently in use. According to the diagrams, the analog signal for the axis is connected to the machine's frame/ground.

Is it better to isolate the analog ground from the system ground? Under what conditions is it strictly necessary to tie both grounds together?

Dear Everyone, 

we did some time ago a linux CNC retrofit with mesa board. We got mostly everything to work, probing and multi height sensor does not and I have to say i would love to get into it and spend the time to get QT dragon to work properly, but the time is becoming crucial and the machine should be running. 
Hence I would like to ask, if there is someone who would be able to either come hands-hand for a 1-2 days and or work remotely with us. Paid of course. 

It is a 1200x1000mm 3axis cnc german spindle, chineese base, completely new electronics from us with Mesa ethernet board. 
I have an xyz probe and tool length measure. 

I would prefer a european source just for the time difference but since it is rather urgent and we seem to be quite stuck in the process, i would take any help we can get. 

Any tip is more then welcome. 
(i will search the forum for the Tods and Davids of course, i saw many many cnc advice online and will try to reach out as well. ) 

I have a 1994 Kitamura Mycenter Zero with a Yasnac mx3 controller.
It has a Yaskawa Varispeed 626 mv3 C spindle drive,which stopped working—it’s completely dead. The repair technician said it would cost 2,000–3,000 € to repair. I found a used drive online for significantly less than the repair costs, but now here’s the problem: I bought the milling machine used and only received one manual and no parameters. (I’ve backed up the Yasnac controller’s parameters.) And since the old Yaskawa Varispeed is dead, I can’t get the parameters from it. Now I’m wondering if there’s anyone in the whole world who has a backup of the Yaskawa Varispeed 626 mv3 C parameters for the Kitamura Mycenter Zero, or knows where I can get one. Of course, I’ll pay for it.

You should be able to follow the MPG example in the  docs. It is for a parallel port but its really all the same with a Mesa card. I had no troubles with a 7i76e. You probably don't need the axis select......

Hallo Juergen,

danke fürs Nachprüfen – damit ist es klar: Der Fehler liegt bei uns, nicht an deinem Firefox.

Was passiert: Die Linux-Version von Takshak bringt eigene Kopien einiger Systembibliotheken mit. Beim Öffnen des Handbuchs hat Takshak dem Browser seinen eigenen Bibliothekspfad mitgegeben. Auf neueren Systemen (z. B. Debian 13) kann Firefox mit diesen älteren Bibliotheken nicht starten – deshalb öffnet sich nichts. Aus dem Terminal gestartet bekommt Firefox eine saubere Umgebung, darum funktioniert es dort.

Wir konnten das genau nachstellen und haben es behoben: Ab Takshak CAM 1.0.7 startet Takshak den Browser – und alles andere, was es außerhalb des Programms öffnet, etwa Ordner und Links – mit deiner normalen Systemumgebung. Getestet auf Debian 12 und 13: Das Handbuch öffnet sich, und die Hilfe einer Operation springt direkt zu ihrer Seite.

Bis 1.0.7 erscheint, findest du das Handbuch auf Deutsch online:
takshakcam.com/manual/de

Die beiden Meldungen in deinem Screenshot („Install Failed: Unable to enable systemd service“ und „Not running on one of the supported Live systems“) kommen übrigens von appimaged, einem separaten Hilfsprogramm für AppImages – nicht von Takshak. Für Takshak spielen sie keine Rolle.

Danke für deine Geduld und die Rückmeldung!

Viele Grüße
Georg

The firmware is installed. The mpg counts, but there is no connection to axis.

Unfortuately HALUI doesn't integrate well with guis.
Overrides changes in HALUI will show in QtDragon but not HALUI jog speed.
There has been some work on this recently but it hasn't made it in linuxcnc yet.

It's possible to add custom code/pins to qtdragon to help with integration.
Can you be specifics about what you need?

Looks fantastic in pics! haven't trued it yet.

Always interested in contructive feedback good or bad - really am.
But stuff like this makes me shake my head a bit.

Compiling problems aren't usually QtDragons fault - you didn't  mention what system you are compiling in so no one could help or evaluate the problem.

I'm sorry Qtdragon didn't suit you out of the box, but there is quite alot you could change.
For instance based on your pic, you could turn on the machine and home it, then the colors change from disabled to enabled and look like this:

 

Qtdragon has optional stylesheets to easily change colors, there are several built in.

If fonts are a problem you can change them too.
linuxcnc.org/docs/stable/html/gui/qtdragon.html#_stylesheets

If you asked nice I bet someone would have even helped you get something that works better for your eyes.

Or don't use it at all. Choice is yours. 
 

Look on the start page, should be a checkbox for 'advanced pages'
check that box on, then extra pages will be shown in sequence.

In my script, with G59.3, after I do those three lines, the only other thing I do is a quick G43 (no H needed) to reload the just-modified table entry.

If this is a 7I96 and not a 7I96S, you would need 7i96_inmd.bit firmware installed.
has this been done?
 

 Thank You for you input, I copied and made a separate tool_change.ngc for testing this tool probe in G59.3 somehow I was able to get that to probe and go back to previous WCS but my measure is still off tool tip about 9.5mm below Z0. My question is do I remove #<tool_length> = [#<spindle_setter_z> - #<setter_touch_machine_z>]p, li { white-space: pre-wrap; }hr { height: 1px; border-width: 0; }li.unchecked::marker { content: "\2610"; }li.checked::marker { content: "\2612"; }and update ; Write the measured length to the selected tool-table entry.G10 L1 P#<selected_tool> Z#<tool_length>p, li { white-space: pre-wrap; }hr { height: 1px; border-width: 0; }li.unchecked::marker { content: "\2610"; }li.checked::marker { content: "\2612"; }with G10 L1 P[#<_selected_tool>] Z[#5403 + #5063]

just want to be clear
Thankyou


 

Thank you for all the help over the years you have given me.