Advanced Search

Controlador: PLC 1200
Sistema operativo: Ubuntu con Linux 2.6.32-122-rtai
Versión LinuxCNC: 2.5.0

 
 

Dear Community,
i hope this is the right place to describe a bug on the XHC-WHB04B-6 Driver.
My environments are LinuxCNC 2.8.4 with Debian 10.10 and 2.9.1 with Debian 12 ( in both the same issue )
If I use the XHC-WHB04B-6 part , are all functions working very well ... so far so good.
If I change from man Mode to MDI and use the jogwheel on the XHC-WHB04B-6, so change the mode from MDI back to man. Mode.
In Automatic exactly the same behavior ...... so far so good, but now the bug ....... if I do it the same on a running program, so will freeze in the XHC-WHB04B-6, because the Automatic Mode can not switch back to the man Mode.
To get open again,  ... switch off the Machine, switch off the XHC-WHB04B-6, start again the LinuxCNC, switch on the
XHC-WHB04B-6 and all will works again very well.
I looking about the HAL to find solutions about the problem, but in the HAL its impossible to fix this issue, its seems to be hard coded.
I looking to the source code, to find anything ( my knowledge in C+ or C++ have tight borders ).
I found something to fix the issue, but its not really working.
Result:
-The switch back to the man Mode is only working in Step Mode or in Con Mode, not in MPG Mode.
-It is possible to switch to Con Mode or to Step Mode on the XHC-WHB04B-6, its impossible to switch to the MPG Mode.
To switch to the MPG Mode has the driver no solution, just in the start is the XHC-WHB04-6 in the MPG Mode.
My idea, to fix this issue was in the hal.cc of the source code to switch in the MPG Mode if the CNC is in MDI or automatic Mode
and nothing will freeze in and working well.
I tried to programing a switch back to MPG Mode, without any faults in compiling the code, but isnt works.
Is anyone there in the community, with experience in C+ ; C++ for help to fix this issue ?
Thank you so much in advance.
Best regards
Reinhard

I would say the output of lcec_configgen is syntactically correct for an ethercat-conf.xml file.
And if you only use recognized devices you can use the generated output directly.
You may still want to change the name"Dx" parameter to something sensible and possibly more.
So it is a really good starting point.

The challenge comes with devices/slaves that are not recognized by lcec and the generic driver is used.
The output from lcec_configgen is syntactically correct as mentioned but it lacks context. It doesn't know
which PDO should be connected to which linuxcnc module and pin. The work to look in the manual
and see what the PDOs actually do remains. With cia402 drives there are boiler-plate examples usually
with great success. Again, a starting point that fixes the syntax of the config file, but the work to understand
how to use the unit still remains.

Doesn't immediately sound related. Would expect a digital IO from the unit to be involved
and not only movement of an axis.

There are some ways to troubleshoot
- any error or info message, if any, in a popup window from the hmi
- any error or info output from linuxcnc in the terminal window where it is started
- the last say 20 line from the command "sudo dmesg" especially when ethercat related 
and one then need to match that with the configuration
- hal file
- ini file
- ethercat-conf.xml
Sometimes the error is obvious, more often the info doesn't directly identify the problem.
You can have a go and look at the info and see if you can spot where it goes wrong, and why.
I can have a look too but then I need all listed info.
 

Not easily at the moment.
That particular button uses multiple images for each LED state, Qtvcp draws LEDs on top of the standard button drawing, adding another could easily be added to the code.
Qtvcp could use either technique.

What would control the LEDs? HAL pins ? Toggle state?

You add a new pdoentry for 606C to the 1A00 PDO in your ethercat-conf.xml file. In this entry idx, subidx, bitlen, is from the A6 manual, you chose a name for "halPin".
Inside you hal file you can then use that name. E.g. like lcec.0.X.yourname
In this example 0 is your first ethercat interface, X is the name of your slave. See "halshow" -> Pins ...

Hi all,

After upgrading from LinuxCNC 2.9.3 to 2.9.4, I encountered an issue in QtDragon where the tool probing routine (qt_auto_probe_tool) starts before I press the “OK” button in the manual tool change dialog (M6).

This behavior was not present in 2.9.3. Previously, the probing would only begin after confirming the tool change.

I found that explicitly disabling the automatic probing behavior in the INI file resolves the issue:

ini
[DISPLAY]
AUTO_TOOL_PROBE = False

This stops QtVCP from launching the tool probe automatically right after M6, allowing me to call the probing subroutine manually after user confirmation.

LinuxCNC 2.9.4 (Debian Bookworm)

QtDragon UI

Manual tool change with M6 remap (calling qt_auto_probe_tool.ngc manually after M6)

I hope this helps others running into the same problem.
If this change in behavior is intended in 2.9.4, it might be worth documenting.

Thanks!

Hi taloot, I am very new to CNC and am trying to setup my home made machine with QTPlasmaC. This post processor is a .doc file, Fusion is prompting me for a .cps post configuration file. Am I missing another step or something really obvious for how to load this post into my Fusion library? Appreciate any advice!

Bump to remove it from "No replies" section.
This was also posted somewhere else on the forum and replied, so this remains a test post.
Thank you.

Moved to "PlasmaC" section.

Not sure if base period is required to run EtherCAT, i can not recall it being mentioned from what i read on this forum.
Either way, your latency results are terrible and to see just how terrible add --show at the end of the latency-histogram line.
In short:
-If you do need base period use older LinuxCNC ISO with Debian Wheezy, does not work with Mesa EtherNET boards and might most probably not work with EtherCAT
-If you do not need base period use the latest 2.9.4 ISO, do not edit or modify anything, just install a new RT-Preempt kernel, 6.13 should do just fine
-Make a config, run the machine, see if LinuxCNC complains about anything, if not = happy machinning

Que controladora usa?

Thank You Andy, Im sure it was my fault, just to old and Technologically inferior to comprehend.

Great ! i have to figure out how to load the error files to a USB Stick .
The builder was a bit of a Conspiracy theorist... he had everything locked down.

Hi all,

I'm new to Lcnc, and have been for the past week trying to get my PC to hit the right latency levels.
After a week i've managed to get the base thread down from 126us to about 90us (worst case) which I've read is okay if you're using it with ethercat.

However I've noticed most of the graphs, especially for the servo period Histogram Latency graph that the shapes that most users have is a single peak. I've always been getting 3 peaks.

I'd like to confirm whether having this type of histogram shape is normal? or whether this shape indicates further sources of latency to be reduced. 

For Background:

Setup:QBiX-GLKB4125-A1 Mini -PC  J4125 Processor

I've grubbed out all i can think of to help the latency with a small amount of success to when it was out of the box

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash kthread_cpus=0,1 irqaffinity=0,1 rcu_nocbs=2,3 nohz_full=2,3 isolcpus=2,3 rcu_nocb_poll nohz=on intel_pstate=disable amd_pstate=disabled amd_idle.max_cstate=1  processor.max_cstate=0 idle=halt skew_tick=1 idle=poll cpufreq.off=1 cpuidle.off=1 intel_idle.max_cstate=0 nowatchdog nosoftlockup igb.EEE=0 apm=off nosmt=force acpi_irq_nobalance i915.enable_rc6=0 i915.enable_dc=0 i915.enable_psr=0 i915.enable_fbc=0 drm_kms_helper.poll=0 pcie_aspm=off r8168.aspm=0 r8168.eee_enable=0 mitigations=off pcie_aspm=off hpet=disable"

got the governor running on performance, and .sh to set the IRQ affinities.

disabled stuff in the bios

updated drivers via the terminal but haven't yet tried updating the NIC,Graphics, and Chipset drivers from the manufacturer.

Any help would be much appreciated, as I'm new to linux. Thanks.