Advanced Search

I get an error from Axis:
Unknown word where unary operation could be. Position: Relative Actual

Searching took me to a page that said this certainly came from gcode interpretation. I have reduced my sub to just start and end statements:
o<z_touch> sub
o<z_touch> endsub
and still get the same error.

Nowhere in the various config files is the subroutine file name used, only the directory. Is this correct?

Thanks

9

A little note to the post above, the reason why the short circuit appeared today is most likely due to the very humid summer air we have here at the moment following a few days of rain.

I've started using the mill more and more lately and I'm amazed how good the finish is of the produced parts.

 

Today however it was my time to release the magic smoke...

I still have my homing speeds set very slow and I must have homed the machine hundreds of times since I finished the build. For this reason the homing takes a while to do. So today I turned on the machine and initiated the homing process while went outside to get some stuff.

When I came back I noticed a message on the screen about an amplifier fault. Didn't think much about until I cleared the fault and tried to jog the X-axis. It was then I noticed that the X-axis was completely jammed to one side and the poor proximity limit switch was all mangled.

 

I removed one of the belt covers and manually jogged the machine of the limit switch. When I tried to jog the X-axis it would always move in the same direction not matter which way I jogged it. It was now that the idea about the fiddly soldering in the DB-44 connectors popped up in the back of my head. Soldering the very tiny cables onto the DB-44 connector was a very fiddly business and the X-axis was the first one I did...

Opened up the control cabinet and took apart the DB-44 connector for the X-axis servo drive and after some poking with a tiny screw driver I found that the insulation had melted during soldering the twisted pair cables for the DIR-/DIR+ signals at the point where they crossed. Pried them apart and added some insulation thinking I had fixed the problem. But when I tested jogging the axis would still always move in the same direction.

Turns out that the short circuit had fried the DIR+ output on the first stepgen of the Mesa 7i96S board. Moved the X-axis to the fifth stepgen output for now and ordered and new Mesa 7i96S board from Welectron as I could see no visible damage on the board itself.

On a more positive note the 400V 2KW 3000/6000 RPM servo that I will be using for the spindle has arrived.

 

I now need to order some HTD 5M or HTD 8M pulleys and belts for it and then machine one of the pulleys to fit on the shaft for the quill drive (removing the magnets on the shaft in the process).

 

I'd also like to add a pneumatic cylinder for the tool release but I haven't found a suitable unit yet so that may have to wait.

 

Problem ist, dass Jogging in allen GUIs etwas anders gehandhabt wird. GMOCCAPY zb stellt eigene hal pins für externe buttons zur Verfügung. Wenn du das Poti sowieso einbinden möchtest dann würde das Sinn machen es jetzt anzugehen.

[edit]
Mit dem Poti wird dann übrigens 'halui.max-velocity.value' mit 0..1 skaliert und an ' halui.axis.jog-speed' weitergegeben. Das ist dann unabhängig vom GUI. Du kannst das gleiche Poti auch für den Vorschub Override verwenden.

I would not worry about the open loop test
and just test in LinuxCNC.

You only need an encoder if you are doing rigid
tapping or threading.

I dont see maximum input ratings on the analog input
but 12V is probably OK for a 10V input (the output would
never be set to 12V in normal operation if you set the
scaling and maximum output correctly)

Hier die aktuelle Doku:
linuxcnc.org/docs/master/html/config/ini-homing.html

Das mit den gleichen Vorzeichen für SEARCH_VEL und LATCH_VEL ist schon richtig für die Variante zwei. Hast du das schon mal probiert ?
LATCH_VEL sollte man um einiges kleiner wählen als SEARCH_VEL sonst macht die zweite Anfahrt keinen Sinn.

I have installed the driver mentioned here
(groups.google.com/g/linux.debian.kernel/c/HJQTXTdpBJo?pli=1)
on my laptop (see attachment) and was able to reduce the max ping time from 14ms to 0.155ms for long-term ping.
This one line
# sudo apt-get install r8168-dkms
 would have saved me a lot of installation and configuration work.
Now LinuxCNC runs stable on my laptop.

Hallo zusammen!           
(Debian 12, LCNC2.9.0 Pre1 und eine 7i76e mit gemeinsamem Home/Ref Switch auf X)
Sorry, ich hatte Projektpause bis jetzt und komme nun auf mein Homing Problem zurück. Ja, ich habe sowohl die EN Hilfe zur INi und Homing durchgelesen, auch die DE Version. Und diverse Postings zum Homing, wo mein Problem nicht auftaucht.
linuxcnc.org/docs/2.6/html/config/ini_homing.html

Auf die Gefahr, mich tw. zu wiederholen:
Beide schlagen ja vier Varianten vor, wovon bei mir mangels Index/GMS nur die beiden ersten ohne Index in Frage kommen. die erste ganz simpel: Achse fährt drauf auf den Schalter und drüber, dann zurück bis der (Ab-)Schaltpunkt erreicht ist und dann auf Home Position. Kann man machen, ich will aber die zweite Variante mit zwei Anfahrten.

Was ich haben möchte, ist Zeichnung 2, wo auf den Schalter gefahren wird, dann zurück und wieder langsamer drauf, um von da aus auf die mit Home definierte Home Position zu fahren (bei mir +10)

IN der Zeichnung von (...ini-homing.html) werden Search Vel positiv und Latch_Vel ebenfalls positiv vorgeschlagen. Das kann aber nicht funktionieren, weil die Richtungen entgegengesetzt sein müssen. Ich habe alles probiert, erst Search_vel positiv (geht nicht weil Home mit 10mm vor dem Schalter aus der pos. Richtung angefahren werden muss, also Search_Vel sollte ein Minus Wert sein, dann gegenläufig Latch_vel ein Positiver Wert.

Was passiert bei mir: Ich habe jetzt noch mal alle Werte, die das Homing beeinflussen, ausprobiert mit Vorzeichenänderung usw. auch der Vorschlag von Dir, tommyligt mit den +/- 10 Home_Offset Werten. Nichts hat mich weiter gebracht. Bei egal welchen EInstellungen fährt die Achse auf den Schalter, wenn der erreicht ist bleibt sie stehen und zeigt an dass die Home Pos. erreicht ist. Keine zweite Anfahrt, immer sofortiger Stopp.
Hier mein Auszug aus der .INI:
[AXIS_X]
MAX_VELOCITY = 125.0
MAX_ACCELERATION = 1500.0
MIN_LIMIT = 0.0
MAX_LIMIT = 700 [JOINT_0]
TYPE = LINEAR
HOME = 10.0
FERROR = 1.0
MIN_FERROR = 1.0
MAX_VELOCITY = 125.0
MAX_ACCELERATION = 1500.0
# The values below should be 25% larger than MAX_VELOCITY and MAX_ACCELERATION# If using BACKLASH compensation STEPGEN_MAXACCEL should be 100% larger.
STEPGEN_MAXVEL = 156.00
STEPGEN_MAXACCEL = 1750.00
P = 1.0
I = 0.0
D = 0.0
FF0 = 0.0
FF1 = 1.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0
MAX_OUTPUT = 0.0# these are in nanoseconds -
DIRSETUP = 10000
DIRHOLD = 10000
STEPLEN = 4000
STEPSPACE = 4000
STEP_SCALE = 640.0
MIN_LIMIT = 0.0
MAX_LIMIT = 720.0
HOME_OFFSET = 10.000000
HOME_SEARCH_VEL = -25
HOME_LATCH_VEL = 25
HOME_FINAL_VEL = 10
HOME_USE_INDEX = NO
HOME_IGNORE_LIMITS = no
HOME_SEQUENCE = 2
Ich wäre sehr froh wenn mir hier jemand helfen könnte!
Und danke schon mal für jeden Hinweis!
VG Arno

aparecido wrote:

JT wrote:

Looks like Phil added tandem joints about 3 years ago to the 2.9 branch.
github.com/LinuxCNC/linuxcnc/commit/f213...27a402ba6ec66ea54dfc

JT
 
Hmmm interesting, so if I didn't understand it wrong, the 'tandem function' is only really implemented in stepconf and in the files generated by it from version 2.9.* onwards....
 

That's correct, I changed to the 2.8 branch to see and the tandem function is not in that branch.

JT

Potentiometer für Vorschub und Eilgang habe ich schon hier liegen aber noch nicht eingebunden. Zum einrichten nutze ich AXIS, aber später möchte ich Probe Basic Lathe als Oberfläche nutzen, ist auch schon installiert

Hast du ein Potentiometer zum Einstellen der Jog Geschwindigkeit?
Falls nein welche Nutzeroberfläche verwendest du?

JT wrote:

Looks like Phil added tandem joints about 3 years ago to the 2.9 branch.
github.com/LinuxCNC/linuxcnc/commit/f213...27a402ba6ec66ea54dfc

JT
 

Hmmm interesting, so if I didn't understand it wrong, the 'tandem function' is only really implemented in stepconf and in the files generated by it from version 2.9.* onwards....

JT wrote:

I see that now, thanks for clarifying that for me... looks like someone has been working on the Stepconf tool.

JT
 

 

Yes, from what I understand by looking at the posts here on the forum, these options were first found in Pnfconf and then went to Stepconf as well.
 Here on the forum there are some topics about an ethernet card with ESP32 that is being tested/developed in open source to be able to use linuxcnc on PCs that no longer have a parallel port, suddenly in future Stepconf updates, they end up including the Esp32 option when all has already been developed/tested and published in the topic, it would also be of great help.

Looks like Phil added tandem joints about 3 years ago to the 2.9 branch.
github.com/LinuxCNC/linuxcnc/commit/f213...27a402ba6ec66ea54dfc

JT