Advanced Search

yeah that's the chap..

Sorry, I misunderstoeod the issue. Tuning the PREEMPT_RT kernel to minimize latency can solve some following errors and it is not documented anywhere in one place and those who follow my guide have had some impressive results as shown in user comments in the video.
This was a very hard topic to put together in a coherent manner.

The drive is a WK600 series VFD, looking at the modbus manual, I think it is true modbus?
I have attached the modbus details

Rod,
Analog drives with following errors on some axis/joints, so why are you pushing your video that will not help?
How is your software solution going to help for hardware issues???

From what a vaguely recall, i did some test and had no success of pinpointing it.
This sort of issues are lingering on from PlasmaC where it would run several cuts then stop at random and do nothing, requiring stopping the machine and using "run from here" to continue.
PhillC did find the issue but apparently not the exact source of the issue, the Z axis would not retract to set height and remain waiting, did fix it to a certain extent where it was very usable and happening rarely.
QtPlasmaC has another similar issue, where running a program would start, got to pierce coordinates and wait there indefinitely despite Z axis being at the correct height. This happened in PlasmaC about once or twice in a full days work, on QtPlasmaC happens way more often, sometimes 3 to 5 times per sheet.
All this is way past being important, i did voice my concerns during the development about not implementing useless features into it and PhillC ignored most of it to the point that i recused myself from participating anymore, it was disheartening to see:
-PhillC sabotaging his work by implementing useless features, always, always requested by users with a single plasma machine and mostly no or little experience
-my complaints being ignored, while i had over 15 machines in daily use
-my input about the functionality being ignored completely, like : float switch MUST react and stop the machine even during jogging, this has ruined many torches and would have ruined much more if they did not have magnetic holders.
-UP/DOWN/ARC_ON LED's on the main screen MUST be usable even while not cutting to check standalone THC's like Proma
-seeing all the effort made by PhillC and later you going to waste as PlasmaC and QtPlasmaC got so bloated and so unreliable that i had to stop using QtPlasmaC completely, and actually thinking of slowly moving the remaining PlasmaC machines to my old hal THC stuff, that never fails, ever. Yes, PlasmaC is usable and mostly reliable
-etc etc
-
Sorry Snowwy and Phill, but i have discussed this before with both of you, even on the phone, so to recap, this is not fixable, must be started over.

You should also measure the voltage drop through the contactor feeding the Indramat, it can be worn out and making a poor connection, failing when under load.

Crusader2050 wrote:

was this ever resolved? one of the youtubers I watch is currently having a similar problem with a different make of mill but with the same "following" error..

Yes its resolved but its a process, not a simple switch. My video shows  best practice for PREEMPT_RT tuning which should resolve following errors.

 

You mean RotarySMP ?

was this ever resolved? one of the youtubers I watch is currently having a similar problem with a different make of mill but with the same "following" error..

Ok, well that went over my head. Was so focused on the LWR issue.

You need to get rid of most of the "UNMATCHED" messages in the syslog.
"UNMATCHED " are usually caused by bad latency or very commonly by using RealTek network adapters.
If you have a Realtek network adapter, you should install the r8152-dkms or r8168-dkms driver via apt.

Can you show the output of "lspci -k"? Only the network interfaces are of interest.

+1 if you have good latency

Thanks everyone. 

Now I can make Yaskawa Sigma X  OP state and jog move from LinuxCNC stably.  ( Just did EoE disabled. )
Slave : SGDXS-xxxxA0x EtherCAT(CoE) SERVOPACK Rev02.09

According to the specification on Web, ( www.e-mechatronics.com/product/servo/sgm...c/xs_ether/spec.html)

LRD, LWR and LRW   seem to be supported. (attached image)
 
​​​But Sorry, I'm not familier with this problem.

Which configuration seems to be better in this situation?

refClockSyncCycles="-1" , with messages "Failed to get reference clock time: Input/output error"
refClockSyncCycles="1" no messages

Should I check some error from log? 



 

Thanks, Mark.

I did not include the pendant yet because I had to be aware of scope creep. I also didn't include things like coolant/Fogbuster valve control and a touch-off probe.