Advanced Search

PCW wrote:

Unexpected realtime delay on task 0 with period 25597

Is this a parallel port setup? (25597 sounds like a parallel port base thread time)

EDIT I see this is a 7I96S configuration but the 25597 thread period makes no sense
in that setup.

 

PCW already mentioned the issue, you have to fix it in your ini file, set the "servo period" to 1000000 ( 1 million), save and start the config again.

It is a Mesa 7i96 via ethernet cable, i'm not sure what is consider normal for that value but AXIS worked fine so im confused how it affects QTplasma.

very odd

im using a Dell optiplex 780 , What is strange to me is that AXIS works fine on the same exact settings but QTplasma has that error and thus i can't use the THCAD-10 , which was the whole point of me upgrading to the MESA hardware.i did disable dell's performance throttle in the bios and jitter was 15886 , which still didnt alleviate the error on QTplasma when i tried a new PnfConfig..


CPU(from terminal via "lscpu"): Intel core 2 duo CPU E8500 @ 3.16GHz
Network: (from terminal via "lspci -nn | grep -i net"): intel corp 82567LM-3 gigabit network connection(rev 2)

I dont have that option, see attached. only Qtplasma

Unexpected realtime delay on task 0 with period 25597

Is this a parallel port setup? (25597 sounds like a parallel port base thread time)

EDIT I see this is a 7I96S configuration but the 25597 thread period makes no sense
in that setup.

 

You error is nothing to do with Linuxcnc but related to your hardware. We need to know about your PC, (CPU and network card) First you need to disable any power saving features in your bios that affects latency.

Then follow my advanced guide here which covers all of the gotchas with modern hardware and operating systems.
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing

Try this

Read on the right side how to ....

Hello all it's been a number of years (3+) and i've finally got around to getting this working on this. I graduated as a mechanical engineer and felt comfortable enough to understand this stuff now.  I was able to connect my mesa 7i96, problem was that my linux distribution had issues connecting to the 7i96. I basically upgraded to the latest linuxcnc (currently on debian 12 with linux 2.9.3) and i have the machine moving using AXIS, for some reason when i try to setup the QTPlasmaC and it will not operate .

Here are the errors i'm getting(see image attached), what doesnt make sense to me is that my jitter is the same as when im using AXIS... and AXIS works great!

Honestly my only goal is for the machine to cut metal with the plasma torch and have a functional torch height controller, i dont care which GUI is used.

If anyone could please help me get this machine going i'd greatly appreciate it!!! I have projects that require plasma cut parts and i'm desperate for this machine to work.

Thank you in advanced , have a great day everyone!


 

Reliable computer will not help you, any computer will do.
The thing with plasma is they create huge amounts of interference when striking and arc, so grounding and proper shielding are mandatory.
Normally you can get away with Mesa 7i96S and THCAD, and they are extremely reliable.
Here are some ideas:
forum.linuxcnc.org/show-your-stuff/38547...plasma-build?start=0

Good afternoon everyone

Can you please help me with how to configure the Z axis drive and recognize the THCAD2 as an encoder? I have tried several times without success.

 

When trying to move the axis, an error appears calculating the movement of the Z axis.

 

This is the INI file type configuration

 

this is the HAL type file configuration

Please, can someone guide me?

INI and HAl files attached


 

 

 

There should be three of encoder A, numbered 0, 1, and 2. Click the arrow next to the encoder you want for arc voltage.

If you are using an encoder for ohmic comp you need to do that manually after PnCconf has completed, the default ohmic sensing for QtPlasmaC is done using a solid state relay rather than a THCAD.

You have 1 encoder on Mesa 7i96S and 6 more on Mesa 7i77, so you can use any of those for THCAD.
The issue of it not working might be changed encoder number in hal in the firmware, so use the "show hal configuration" from the "machine" menu to check what number is assigned to Mesa 7i96S encoder, should be 0 or 6.

Hello, I have 2 7i96s boards. The first one has the original factory firmware and is used for lab testing. I tested it with THCAD2 on the encoder input and was successful in receiving the frequency and reading it, showing the frequency speed. However, to my surprise, on the client's machine where there is another 7i96s that was updated to work and recognize the 7i77 plus the 7i84, I did not get the same result, it cannot read the frequency. After much analysis, the only thing different in the HAL programming is the configuration sserial_port_0=3000, which is different to enable recognition of the 7i84. Setting encoder-mode to 1 did not help. Why am I not getting the same result? Is there some configuration that I am forgetting to do?

 

Hello everyone, I'm already on the client's machine, I'm trying to apply part of what worked in the lab test with 7i96s and
I'm trying to do the same client configuration on the 7i77 that was done in the lab on the 7i96s. But on the 7i96s I have to put:

setp hm2_7i96s.0.encoder.00.counter-mode 1

setp hm2_7i96s.0.encoder.00.filter 0

setp hm2_7i96s.0.encoder.00.scale -1

and will read the frequency applied to ENCA+ and ENCA- of THCAD2.

However, the 7i77 does not accept this configuration. What is the procedure to make the 7i77 change the encoder to mode 1?

 

Does not show hm2_7i96s.0.encoder.00.velocity

 

How to configure the 7i77 encoder to accept frequency?

 

Thank you, I will follow your guidance and post step by step here.