Advanced Search

*facepalm* I must have clicked every option except that one.

Well at least now I understand how to rename the drives in the xml file to make organising things simpler.

Here's the output from halcmd show pin

What are the basic pins I need for motion?

And a massive thank you to everyone who takes the time to offer help and guidance, it's genuinely amazing.

I seem to have gotten the following error to not kick in, I turned the velocity and acceleration to 1 and that seems to let the axis move more than about .25" at a time. Still looking into the index not kicking in.

Goodmorning, 
i am new here and still a noob with LinuxCNC. I would ask if i can share a github page where I have collected what i have learned with LinuxCNC using EtherCAT and a OMRON R88D drive. I think it may be useful for other beginners like me that would like to approach LinuxCNC with OMRON R88D drive. The collection of what i learned is still incomplete and lacks of many things.

If yes, in which section i can share it?

Thanks.
sparviero

try toggle or toggle2nist components.

The halui pin works.
nfortunately, it is currently very sensitive. If you press the button for too long, the pump switches off again or toggles between on and off.

I would need to add something that checks whether the button has been pressed again. 
Does anyone have any ideas?

Click the D1 node. Obviously it is called D1 in ethercat-conf.xml

Thanks rodw.

Turns out that the error was misreporting the line number. When I parameterized the subroutine I inadvertently left a stray > on line 33.

Here's the result of halshow after following your instructions. Is my drive perhaps not defined correctly or something like that? I don't seem to have any pins like your screen shot shows.

Thanks for looking into this issue.

I opened the attached file I ran the following commands without encountering any issues:

G10 L2 P1 X0 Y0 Z0
G10 L2 P2 X0 Y0 Z0
G10 L2 P3 X0 Y0 Z0

However as soon as I set the value of G56 using the probing function highlighted below the error appears when the probing has finished.

 

This seems to be related some type of state that gets set during the probing of G56. Because if I probe G56 with no file open and then open the attached file it triggers the error immediately without any further input required.

 

hallo, danke für die info. cmos batterie vor 14 tagen getauscht.
festplatte fest..

auf dem foto ist ein warndreieck auf der festplatte zu sehen,
kann ein mbr fehler sein.

karlhe

epineh wrote:

Awesome, those new tabs look great, the invert button on the scale is a nice touch. 
Russell.

I'll second that.

Top work

Danke, habs hinbekommen!

Die Fräse fährt jetzt wie sie soll, beim Verfahren mit den Cursor-Tasten hört man allerdings immer leichte Aussetzer.
Ich nutze eine Logitech Funktastatur, deren Empfänger immer schon etwas heikel war.

Ich werde am Wochenende mal eine meiner größeren G-Code Dateien abfahren lassen (mit Stift statt Fräser), und aufpassen ob das im Normalbetrieb überhaupt auftritt.

Im Anhang noch die Letztversion der Config-Dateien.

Hallo!

Ich hatte das letztens auch, da war es eine schlechte Steckverbindung der Festplatte.

Wird die Platte im Bios denn erkannt, und stimmt die Boot-Reihenfolge im Bios?
Gibt es eine Fehlermeldung?
Eine leere Bios Batterie kann sowas auch auslösen.

A long time since I played with this. I think you should use [ ] symbols. But check the docs

Good luck with this. There is no reason why you can't run a 1.024 Ms servo thread if that's important to remain  synced.. Its just a hal file setting...