Advanced Search

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.