Advanced Search

I think 2.8 on Wheezy should work. The issue is Python 2.7 was deprecated from Debian Bullseye and on so the new Debian versions use Python 3

I have the same issue. I tried to rotate the G54 coordinate system slightly to account for a slightly misaligned part fixture. However, the G10 L2 P1 R1 command moved the origin around like described above. I would assume the coordinate system would be rotated around the origin of the respective coordinate system, thus not moving the origin. I could manually set the origin in the rotated coordinate system and then preview and movement of the machine were like expected.

Moreover, the G53 commands used during toolchange operations do not work anymore since LinuxCNC is throwing an error that limits are violated. I would assume the G53 is not affected by rotation of the coordinate system since it is machine coordinates?

I am using LinuxCNC 1.8.4. I would be very happy if someone could check this on a more current version of LinuxCNC since it might have been fixed already.

I know probe_basic and Qtdragon have their own probing procedures including rotating the part coordinate systems. Is this working or affected by this?

I heard a whisper the devs wanted to implement hal pins as 64 bit values with the next release (when  2.10 replaces 2.9) 

Remember a plasma cutter is a blunt axe, not a surgical scalpel.
Ask yourself is the cut quality adequate for welding and fabrication? It will never be like an accurately machined part.
The plasma primer has some info about cut heights and angularity
linuxcnc.org/docs/stable/html/plasma/pla...mer.html#_cnc_plasma
 

Thank for the reply

Ping stats 0% packet loss
Min/avg/max/mdev = 0.081/0.258/0.339/0.017 ms

Ethernet controller is intel 82579LM gigabit network connection (lewisville) (rev 4)

Thanks Peter,
So ... <= hm2_7i92.0.7i73.0.2.analogin0, 1, 2 are confirmed
as are both
<= hm2_7i92.0.7i73.0.2.enc0.rawcounts and
<= hm2_7i92.0.7i73.0.2.input-08

but I guess one is processing the data differently from the other.

Typically you use 1X quadrature mode for MPGs (the 7I73 default)

If in doubt about pin names, you can always follow the pin tree in halshow  or do something like:

halcmd show all | grep -i 7i73

(when linuxcnc is running)
 

Next task is Pendant encoder and feedrate pots.

I've a 7i92-7i77-7i73 combination.
From the 7i73 manual, I can use pins,3(IN0),4(IN1) and 5 (IN2) for 0-3.3v analogue inputs.
which I think I can call using
... <= hm2_7i92.0.7i73.0.0.analogin0, 1, 2

Then original Hurco mpg, (5 volt ) pulses can be connected pins 14 (IN8) and 15 (IN9) channels for a and b.
For which I think I need to set the mode
setp hm2_7i92.0.7i73.0.0.nvencmode1 4 (if quadrature scaled)

but then I am unsure how to refer to the pin.
my guesses .
.... <= hm2_7i92.0.7i73.0.2.input-08
... <= hm2_7i92.0.7i73.0.2.enc0.rawcounts

Are they interchangeable, or is only one effective depending on the mode?

As ever indebted to your kind selves.

I was on 2.9.3 and today I updated to 2.9.4
After the update the Jog from the keyboard no longer works.
If I press the buttons with the mouse they work.
In the ini file I have KEYBOARD_JOG=1 enabled
Does anyone know what the problem could be?

The first problem is real time issues with the network interface.

To get a rough idea where things are, can you run these two commands and reply with the results:

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

This will run for 1 minute and print statistics
(replace 10.10.10.10 with 192.168.1.121 if that's the 7I76Es address)

lspci | grep -i eth

(this should make it possible to determine the PCs Ethernet interface type)

I tried with new consumables because I was thinking about swirling due to a worn nozzle but ithe issue remains the same.
The air pressure/flow is automatically adjusted by the powermax and it’s air supply respects the manufacturer’s recommendations (pressure, flow, water/oil contamination etc…)

Regarding the cutting direction, I let Pronest decide for me but I will try on next cuts.
Do you think compensating the torch inclination could work?

Yes, if you decouple the linear axis (and comment out the net statement that connects
the PID output to the 7I77 analog output pin, you can simply setp the output voltage
with halcmd.
 

Saturation takes a lot of overload, and you find out after 30 seconds to 1 minute that is it overloaded to much as it starts smoking, a lot.
And yes, toroidal transformers are metal core, wound in a doughnut shape, while normal transformers have E and I sections alternatively pushed inside. Microwave transformers usually have all the E on one side and all the I on the other side welded together, but that is not the best way for efficiency, they are on for several minutes at a time so not important.

Could you share your complete setup for doing that type of work on the lathe?

Can you make a new basic config, with just PWM's and encoders and test again.
I recall a few years back i made a config that absolutely did not put anything on analog outs, wasted an hour looking through hal, could not find it, made a new config and it worked, never had the same issue before or after that.
Another thing to check is the Mesa supply voltage, the 5V side, if 7i97T uses 5V, many of 5V power supplies are really bad, but that would also trigger lost connection, not always, though, so worth checking.