Advanced Search

The 7I76E has been replaced with the 7I76EU which is available from a couple of sources.
 
The 7I92T option would work with your existing breakouts, but it would require
completely different hal/ini files.

 

Notice o053 in two instances above, so i am guessing they should be O upper case as the rest of them.

The T3D drive has an analog input option but no encoder output
(which is a bit uncommon) so will not work with the 7I97/7I97T.

A step/dir board would be required, a Mesa 7I96,7I96S or 7I76EU
are possibilities.

Yes, buying the 7i76e might be a good idea, but its difficult to get (out of stock everywhere) and i would wish to not need to rewire anything and configure.

Of course I could ask or look for a pc setup that works 100% with the newest rtai kernel and buy the same hardware, but its just strange that I cannot get that machine that worked really well with wheezy not working on debian 12.

On tomorrow i will try a couple more bios settings but all energy saving functions are disabled and I know I didn't had to fix so many things to get a jitter of about 8000.

@tommylight: this I have solved already and the machine sounds and works by jogging perfectly fine now, but I still get unexpected realtime error on task 1 on start up.

Currently I mostly do changes in the cpu ratio and other cpu settings like cpu bus frequency and if I setup a wrong value, lets say, cpu frequency 165 instead of 120 then the machine might make that strange movement, smooth but not all the time.

I attach 2 pictures of one windows screen (tweaker), so that you see the options. That are not anymore the current settings. Tomorrow I can show pictures of the other options available but I am sure it's setup correct.

In grub config I have only what was already there: "quiet" and I added "isolcpus=5" to it. I believe with wheezy I had isolcpus=1,2,34,5, but I am not sure anymore.
The cpu is a amd phenom ii x6 1055t.

Second shop from earlier:

And second shop from 9 months ago:

Last i checked, something that comes close to QtPlasmaC in functionality (not in usability by far, much harder to use) was over 170000$ with a 300A plasma source that costs 84000$, leaving the machine price at 86000$ for 6X2.5M cut envelope!
-
Here are some links that might help:
forum.linuxcnc.org/show-your-stuff/38547...-5m-cnc-plasma-build
forum.linuxcnc.org/show-your-stuff/48985...s-frequently-updated
forum.linuxcnc.org/show-your-stuff/35337...2m-work-area-or-12x7
forum.linuxcnc.org/show-your-stuff/35306-cnc-plasma-tube-cutter

Could someone help me find my error?
The program orients the spindle and calls an unknown control command in o word. I have attached the toolchange.ngc that is throwing the error.

I have T3D servo motors and a 7i97t board but it seems that it is not compatible. Which board would you recommend for 5 or 6 of these servo motors?

I would change the cable, first.
I have thrown so many HDMI cablles by now that i get irked when someone mentions them, from bad quality to wrong resolutions to not being able to run my 3440X1440 monitor at 100Hz!!!
I have a single HDMI cable here (here being my bedroom) that does 100Hz, the rest are a choice of 85Hz to 2560X1440 at 59Hz, i have more in the shop that are OK, but ALL Display Port cables i have do that and 4K easily, no matter how cheap or bad quality.

They should still work, but no guaranties, so:
-download them, make them executable and try to run them
-if they do not work, edit them using a text editor, not office, at the top change from python to python2, save, try to run them again
-if they do not work, edit and change from python2 to python3, save, try again.
In case they do run but error out or just close, try running them from terminal and see what errors they report.

denhen89 wrote:

EDIT: i have found the command and now linuxcnc is starting without unexpected realtime delay, axis moving, but it sound a bit strange, but smooth but with small stops between smooth movement. I will try to adjust bios cpu settings.


 

Is that while jogging with keyboard?
Try jogging using the mouse, as it might be a keyboard thingy.

I just uploaded the description and design of the EaserCAT 7000 board and the two plasma torch voltage readers THTIC and THTIC2 on github.
github.com/MetalMusings/MyOwnEtherCATDev...ith-thtic-and-thtic2

Reads the plasma voltage, feeds it to my EaserCAT-7000 card over I2C and makes it available either as raw data read from the ADC or scaled to calibrated plasma torch voltage.
I have used it for maybe an hour of cutting (feed time) and it just works. Very happy with it.
There are two versions, for a bit blurry reasons, but always good with options I guess.
The ADC card is small 55x32 mm.
 
 
 

Ideally you should get no dropped packets at all.

I does sound like a network latency issue.

One thing to do to test is to run say:

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

(will run for ~1 minute)
and see what the stats are

If there are no more network latency optimizations to do

You can increase the servo thread period (say to 2 ms)

Its also possible to make dropped packets not trigger following errors
(or cause path deviations) by specific hal file modifications
 

The parameters that store the location of the G30 are persistent. Even after rebooting the PC the G30 location will be the same. You only need to do G30.1 once.