Advanced Search

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.

Could I get a picture of the edge find button? If you use print screen button on your keyboard it will allow you to copy the screen to the clipboard or save a picture of your screen to your hard drive.

What behavior do you want M6 to do?

Tool change at G30 will allow you to manually change tools away from the part.

1. Add "TOOL_CHANGE_AT_G30=1" to the [EMCIO] portion of your INI file.
2. Power on your machine & home all axis.
3. Jog to the position you want to do manual tool changes at.
4. Type G30.1 into MDI and run it. This will save the current machine position as the location to go to when a tool change is called.
5. Test the machine. It should now rapid to this location when you call M6

linuxcnc.org/docs/2.6/html/gcode/gcode.html#sec:G30-G30_1

Thanks for chiming in. I'm hopeful that this is not the solution I'm after. My goal is to convert these signals within LinuxCNC using something like the BLDC HAL component or something of that nature then spitting out the results via some of my available outputs on my Mesa cards. Surely Hopefully it can be done in HAL and not need an external converter board. These PICO boards would hurt the wallet too much as well, 600USD for 4 that's 850CAD and that's about half of my net worth

#machineShopOnAShoestring

I would recommend your 7i76e option you mentioned in your first post.

Wheezy is far too old to expect stuff to still work. its well past end of life
Whilst the linuxcnc guys have done an amazing job keeping RTAI working for all these years its also past end of life.
Without the Linuxcnc devs, RTAI would not exist today.
Preempt_RT has won the real time wars.
If the default Linuxcnc ISO works reliably for you, it will work with a 7i76e

But like any modern OS, things are more complicated today and there are a number of optimisations I cover here
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing
 

there is no comparison. Linuxcnc's QTplasmac, a Mesa 7i96 and a THCAD2 will give you a high end system for almost nothing. Its feature set is very extensive. The difference is that the THC is managed internally by Linuxcnc, not an external THC so the system knows much more about what I'd going on and has much more ability to provide consistent results.
This is quite an old video but it shows what you can do

And the cut recovery features

nothing comes close!

spammer booted

Spammer booted

Problem is that $1 contains a float which bash can't handle, so try:

I believe these lines were the problem:

net tool-prepare-request <= iocontrol.0.tool-prepare
net tool-prepare-confirmed => iocontrol.0.tool-prepared

Not sure if those came from PNCconf, but I commented them out and it seems to have resolved the issue.

Mach 3 is at a point where it is hard to run unless you have a really old version of windows. i used it for years until i hit issues in windows 10. so i would make the switch which i did do
when it comes to plasma and THC Linux with Mesa has probably the cheapest THC solutions out there but I'm in the US so duties and taxes could factor into it to some degree.