Advanced Search

Hello,
I am running 2.8. I am not very experienced with LinuxCNC but got it all running with the parports. Now I try to get it working with the pokeys57CNC but there are almost no examples so I don't know what files I have to change. It is more than only following the instructions on page 10 I guess. Do I have to change the .hal and .ini files also and if yes are there good examples?
The machine_is_on changes the state of the pokeys when assigned correctly and just 1 time I managed that but I lost it somewhere in the process.
Apology for the late response. I wasn't notified of a reply. I checked the box now.

I would check the 7I76E input you use for ARCOK  in halshow
to see if it switches as expected when the torch is fired.

Note that ARCOK signals from relay contacts may need a larger
load current than the 7I76E inputs sink (wetting current) so you
may need to add an external resistor (say 1K 2W) from the 7I76E
input to GND to provide this current.
 

knipknap wrote:

I randomly get situations where LinuxCNC is not following the gcode precisely, instead taking shortcuts. I have configured G64 as follows:

RS274NGC_STARTUP_CODE = G17 G21 G40 G49 G64 P0.001 G80 G90 G94 G97 G9
 

RS274NGC_STARTUP_CODE is only valid during startup, do not expect any of those codes to last past the first line of the first G code program you run.

The RS274NGC_STARTUP_CODE does not take the place of a good preamble in each G code file.

G code programs can change anything while running and thus render the RS274NGC_STARTUP_CODE a waste of time.

linuxcnc.org/docs/stable/html/gcode/over...gcode:best-practices

JT

I am unable to get a successful arc okay signal from my primeweld cut60 plasma cutter to qtplasmac. I wired the arc okay signal using 24v power from the 7i76e board and sinking it to one of the inputs just like a limit switch. When I go to cut out a part qtplasmac fires three times and says no arc okay signal was found. Is anyones wiring of arc okay different than mine, can anybody please share how you connected your arc okay signal? Thank you all for amazing help

Yes, the 24V common/negative needs to connect to the 7I97 encoder GND.
 

Well that was a silly mistake. Thank you very much!

Anton wrote:

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.

I forgot how hard i tried to get Debian to acknowledge some flaws in their distro. I also raised issues with the PREEMPT_RT development team. In the end noone cares.

I think in the end the fault lies with the Linux kernel as the R8168 is poorly supported by the R8169 kernel driver and the R8168 driver is not in the kernel. This is where DKMS comes in as it allows installation of kernel modules which are recompiled if you use another kernel (most of the time)

Sorry I did not read your post earlier. This is all covered in my Debian config document. I need to add a bit on IRQ pinning which is in a sticky on the forum here
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing

and the last question, should i connect the ground of the 24VDC on the encoder ground ?

I'm running LinuxCNC 2.8.4-1-gb7824717b.

I'm hesitant to update, don't want to risk being unable to use the machine...

MDI_COMMAND = MDI_COMMAND = (debug,MDI button pressed)

Well this would explain the error you got. This line should be:
MDI_COMMAND = (debug,MDI button pressed)

 

I made a video about it. Maybe this will help someone.

english


german

Here are my various mods:

.ini file
[RS274NGC]
PARAMETER_FILE = linuxcnc.var
SUBROUTINE_PATH = ncsubroutines:/home/steve/linuxcnc/subroutines

HAL
HALUI = halui

[HALUI]
# add halui MDI commands here (max 64)
MDI_COMMAND = MDI_COMMAND = (debug,MDI button pressed)

postgui_call_list.hal
# touch off Z
net ztouchoff halui.mdi-command-00 <= pyvcp.z-zero

custompanel.xml
<button>
<font>("Helvetica",14)</font>
<width>3</width>
<halpin>"z-zero"</halpin>
<text>"Z"</text>
</button>

There are other mods, the jog button pyvcp example. They work fine until I try my added touchoff Z button, when I get the error and the jog buttons no longer work. So I think it's the Z button section in error, rather than some other part.

I made your change, saved and restarted Axis. Same error message.

The error 'Unknown word where unary operation could be.' points to a syntax error in Gcode.

If the interpreter was unable to find the subroutine then you would get error like
'seeking o-word: o<z_touch> from line .. '.
So there is something else going on.

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

That is correct, the interpreter will search for the subroutine in the paths declared.

If you change this:
MDI_COMMAND = o<z_touch>call

to
MDI_COMMAND = (debug,MDI button pressed)

And you press the button, do you get a message like this: