Advanced Search

Hey everyone - I have a modified taig that i am running with linuxcnc using a mesa 7i96s and a dell optiplex 7010 (i think). I am wondering what you all think is the easiest way to hook up a pendant? The only thing I care about is being able to jog the axis. I have been looking online and there seems to be so many ways to do it like daighter cards, different ifirmware, parallel ports in pci slot, but do any of you have experience on whats the most simple setup with purchasing a common pendant online?

Use an mdi command to issue the appropriate G10 command.

And here are voltages on a wet table.
 

Ok, little bit more intriguing than I first thought.
Not much of a dip there.
How to detect that? There are ways of course. 
 

Hi all, I marked a forum topic so as to be able to come back and read further and the pop up said it was 'saved to my favourites' . Alas I can find no such page anywhere. I would have thought it would be somewhere in my profile page?

Hello
I'm having a weird Qtplasmac 2.9.238.315 bug where my torch goes down when it should be going up - but only during THC corrections.
Normal Z axis movement is OK as it should, with homing, probing, etc.

THC is being used from voltage (THCAD-2) and arc OK signal is present. 

I tried reversing the Voltage Scale (from 0.009 to -0.009) and no changes. - it still is correcting in the reverse way. how weird is it!

Where could i start?

Thanks everyone

net Spindelrpm => gladevcp.Spindel
Got that... i just created the signal.name Spindel.rpm which is linked to gladevcp.Spindel.
There is still my problem where to get the float.out(?) from and link it to Spindel.rpm. My "favorite" spindle.0.speed-out is already linked -> Error "custom_postgui.hal:9: Pin 'spindle.0.speed-out' was already linked to signal 'spindle.0.speed-out'"

Sorry... German beginner

andypugh wrote:

Shortly after the release of 2.9.5 it was
noticed that a fix for a graphics bug in Gmoccapy had resulted in the
Axis touch-off dialog box no-longer working for non-zero entries.

I've been refraining from commenting on this till now, but i have to, i would absolutely prohibit changing anything that affects Axis GUI in any way, shape or form, from other GUI's or anything else.
Axis is and should remain bullet proof, that is the main reason i use it on all my machines (over 40 by now).
Destroying basic functionality on Axis to fix something already broken in GmoccaPy is plain absurdity.
I can absolutely understand if it was a mistake, but from a bit of reading it does not seem to.
I really hope i am wrong...

Recorded the voltage between tip and work piece during some 5 minutes. Was cutting a bunch of small holes.
 

They all look like this one, with some variation.
 

This was on a dry work piece. There is a clear voltage drop, somewhat slow, delayed recovery.
Triggered contact condition was a one-cycle voltage drop of 5 Volts.

 

Quick Update.

Using "Trixie" branch from here; salsa.debian.org/live-team/live-build/-/...rixie?ref_type=heads

I built a live-build package on a machine running Bookworm from the above repo. Installed the built package and was able to successfully build a Linuxcnc ISO without the raspi-firmware. As noted above hostmot2 firmwares are installed, a test run of Axis with the default gcode produced no errors, apart from latency due to being run in a virtual machine.

Building live-build packages from the above sources also works for building ISO on Linux Mint 22.1 Xia.

The goal would be to pin Linuxcnc to 2.9.4 during the ISO creation, as there seems to be a few issues reported by users with either the 2.9.5 or 2.9.6 branch.

try changing

to

Might be related to this:
github.com/LinuxCNC/linuxcnc/issues/3583

I tried to do it correctly so I wired them as normally closed. I have 2 limit switches on the axis and this one is also my home switch. 
If I follow your advice then I need to revert everything to have the other LS as HS. This is not an issue to be honest, just thinking about the consequences. 

Thank you Peter.  I reviewed the link you provided, but is there a document or manual which describes how to set this up?

That indicates a Ethernet latency issue.

What does the command

sudo chrt 99 ping -i .001 -q -c 60000 192.168.1.121

report?

(the command will run for one minute then print statistics)
 

When I move the engines after a while, I get this error. 

I can't figure out what the problem is. The connection seems to be fine.