Advanced Search

I think that for Yaskawa, the safest approach is to use Yaskawa’s own tool (SigmaWin+), since it knows the hardware and the drive’s constraints, and it’s also the approach their support can reproduce and help with if something goes wrong.

Ja EMV ist ein großes Thema und man sucht im dunkeln was da stört kann man messen aber nur die Industrie hat die Möglichkeit Datenkabel können in frage kommen hatte ich schon mit ein Monitor-Kabel.Da du ein Metalsteg eingebaut hast ist in dem Bereich was nicht ganz sauber.
Ich tippe auf die Grünen Datenkabel oder ist T3 ein Netgerät ? Vielleicht das.
Auch können die China Komponenten schuld sein hatte ich schon mit
ein Handylagerät das hat total das Fungerät gestört.
Was mir auch aufgefallen ist dein Netzfilter der ist ja ok aber es könnte
mit RCD Probleme geben muss nicht . Das ist heute auch ein großes Thema weil jede LED-Schaltung Ableitstöme produziert und irgend wann sind 30mA erreicht und dann macht es klick.

Gruß
Juergen

Do you mean 2.4.8 or 2.8.4 ?
(2.4.8 was released around 15 years ago)

Pasting this into the message body has destroyed the indentation. As it contains embedded Python this means that it won't work at all.

Can you attach the script as a file instead?

(I tried correcting the file, but it became too difficult in the Python code without doing real code analysis)

You should be able to install a previous Bookworm ISO, then update the LinuxCNC version (this should actually be automatic).

The 2.9.4 ISO will definitely be Bookworm as it precedes the Trixie release.
www.linuxcnc.org/iso/

Then use the Synapric package manager to update LinuxCNC.

Can you give the _exact_ error message?

It feels like, for whatever reason, the motor drivers are inhibited. Do you see any movement at all?

Do you mean that the pendant did not recover in the above situation after you had commented out the assert line?

You could enable all logging by adding the "-a" option when loading the xhc-whb04b-6 component. It will write a lot of things to the terminal... which makes it easier to figure out if it gets stuck in some specific part of the code.

Hi,
i made a new install on my system today but fail again

- I downloaded and installed Bookworm 12.13 from the Probe Basic site  kcjengr.github.io/probe_basic/probe_basi..._stable_install.html
- i did sudo apt update
- i did sudo apt upgrade
- i downloaded the AMD64 Deb for PC
- i did cd~
- i did cd Download
- i did sudo dpkg -i linuxcnc-uspace_2.9.8_amd64.deb

the result after the last step

sudo dpkg -i linuxcnc-uspace_2.9.8_amd64.deb
Selecting previously unselected package linuxcnc-uspace.
(Reading database ... 123705 files and directories currently installed.)
Preparing to unpack linuxcnc-uspace_2.9.8_amd64.deb ...
Unpacking linuxcnc-uspace (1:2.9.8) ...
dpkg: dependency problems prevent configuration of linuxcnc-uspace:
 linuxcnc-uspace depends on libboost-python1.74.0 (>= 1.74.0+ds1); however:
  Package libboost-python1.74.0 is not installed.
 linuxcnc-uspace depends on libboost-python1.74.0-py311; however:
  Package libboost-python1.74.0-py311 is not installed.
 linuxcnc-uspace depends on libgpiod2 (>= 1.5.1); however:
  Package libgpiod2 is not installed.
 linuxcnc-uspace depends on libmodbus5 (>= 3.1.4); however:
  Package libmodbus5 is not installed.
 linuxcnc-uspace depends on libtk8.6 (>= 8.6.0); however:
  Package libtk8.6 is not installed.
 linuxcnc-uspace depends on libudev-dev; however:
  Package libudev-dev is not installed.
 linuxcnc-uspace depends on iptables; however:
  Package iptables is not installed.
 linuxcnc-uspace depends on blt; however:
  Package blt is not installed.
 linuxcnc-uspace depends on mesa-utils; however:
  Package mesa-utils is not installed.
 linuxcnc-uspace depends on python3-tk; however:
  Package python3-tk is not installed.
 linuxcnc-uspace depends on python3-numpy; however:
  Package python3-numpy is not installed.
 linuxcnc-uspace depends on python3-opengl; however:
  Package python3-opengl is not installed.
 linuxcnc-uspace depends on python3-configobj; however:
  Package python3-configobj is not installed.
 linuxcnc-uspace depends on python3-xlib; however:
  Package python3-xlib is not installed.
 linuxcnc-uspace depends on libgtksourceview-4-dev; however:
  Package libgtksourceview-4-dev is not installed.
 linuxcnc-uspace depends on tcl8.6; however:
  Package tcl8.6 is not installed.
 linuxcnc-uspace depends on tk8.6; however:
  Package tk8.6 is not installed.
 linuxcnc-uspace depends on bwidget (>= 1.7); however:
  Package bwidget is not installed.
 linuxcnc-uspace depends on tclreadline; however:
  Package tclreadline is not installed.
 linuxcnc-uspace depends on tclx; however:
  Package tclx is not installed.
 linuxcnc-uspace depends on python3-pyqt5; however:
  Package python3-pyqt5 is not installed.
 linuxcnc-uspace depends on python3-pyqt5.qsci; however:
  Package python3-pyqt5.qsci is not installed.
 linuxcnc-uspace depends on python3-pyqt5.qtsvg; however:
  Package python3-pyqt5.qtsvg is not installed.
 linuxcnc-uspace depends on python3-pyqt5.qtopengl; however:
  Package python3-pyqt5.qtopengl is not installed.
 linuxcnc-uspace depends on python3-opencv; however:
  Package python3-opencv is not installed.
 linuxcnc-uspace depends on python3-espeak; however:
  Package python3-espeak is not installed.
 linuxcnc-uspace depends on python3-dbus.mainloop.pyqt5; however:
  Package python3-dbus.mainloop.pyqt5 is not installed.
 linuxcnc-uspace depends on python3-pyqt5.qtwebengine | python3-pyqt5.qtwebkit; however:
  Package python3-pyqt5.qtwebengine is not installed.
  Package python3-pyqt5.qtwebkit is not installed.
 linuxcnc-uspace depends on espeak-ng; however:
  Package espeak-ng is not installed.
 linuxcnc-uspace depends on pyqt5-dev-tools; however:
  Package pyqt5-dev-tools is not installed.
 linuxcnc-uspace depends on gstreamer1.0-tools; however:
  Package gstreamer1.0-tools is not installed.
 linuxcnc-uspace depends on espeak; however:
  Package espeak is not installed.
 linuxcnc-uspace depends on python3-poppler-qt5; however:
  Package python3-poppler-qt5 is not installed.
 linuxcnc-uspace depends on psmisc; however:
  Package psmisc is not installed.

dpkg: error processing package linuxcnc-uspace (--install):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9+deb12u13) ...
Processing triggers for desktop-file-utils (0.26-1) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for shared-mime-info (2.2-1) ...
Errors were encountered while processing:
 linuxcnc-uspace


 

I have added a bit more logging to the component..
The component is attempting to connect, it says, but I wonder if it actually tries and why that doesn't work.

That's right. Linuxcnc doesn't use an ESI file.
The ethercat master reads out the info it needs from the slave directly.

The safest way to update the SII eeprom contents of the drive is to use TwinCAT.
There are a number of steps needed, but in principle not difficult.
Download and install TwinCAT from Beckhoff it you don't already have it,
Place the ESI file you got from support in C:\TwinCAT\3.1\Config\Io\EtherCAT
or where your twincat installation is.
In this video I update the firmware on a device, the principle is the same for your drive.
Go to 5:20 for the relevant part.

 

Okay. I did not really think that libusb_fill_interrupt_transfer() would solve the issue. But that IS the correct function to use in any case.

If the disconnect happens only at mode switches, I'm pretty sure it can be solved simply by modifying the xhc-whb04b-6 component. Maybe we need to add some more (temporary) logging to the component to pinpoint the issue.

It appears our dongle firmware is different by one version increment. But of course the hardware side is the important one for compatibility. I would think that there is a good chance that the hardware is compatible or the same.

The sticker on my pendant 
 

Had two crashes yesterday. Mode switching. libusb_fill_interrupt_transfer() isn't the solution.
 
I had commented out the assert() in setupAsyncTransfer and let it continue
Failed here github.com/LinuxCNC/linuxcnc/blob/0673e3...whb04b-6/usb.cc#L541





 

Hi at all,

Yesterday, after many Month of working without any problem, my Mill stops with an error "Positionerror ...".
My config runs on Probe Basic with a MESA 7i96S and a7i85S (for the aditional linear-encoders)

I restartet Probe Basic, but every time I tried to reference, i allways got the same error and not just one axle moves.
Also I checked the voltages and all seems OK.
To find out if there ist just a basic funktion, i startet a new config with the wizard. 
After setting up the MESA 7i96s (IP 10.10.10.10), opend up the test-movement-mask, activating the axle, i tried to move the axle, but nothing. (The HAL-Scope shows a feedrate like it should do)
I Tried this for X, Y and Z but nothing!

So at this moment I`m wondering if there is a problem with the MESA Card.
Is there someone who had a similar issue and could give me a tip.
By the way, if I move the axles by hand, all the linear-Encoders at the 7i96S works fine.

Thanks a lot.
Jens  
 

Hi Tommy,
Scaling was wrong...
My number was per seconds in my mind not per minute so 60 time slower !

Thanks

Marco

 

So sieht meine Steuerung mit EtherCat aus. Servos von Lichuan über AliExpress und StepperOnline über deren Website gekauft. Nutzen alle das cia402 Profil, lassen sich also identisch ansprechen. Einzig die vid (Vendor ID) und pid (Product ID) sind anders, müssen also in der ethercat-conf.xml angepasst werden. Man kann die Treiber meines Wissens entweder direkt am Gerät einstellen oder über die ethercat-conf.xml mit SDOs. Letzteres habe ich aber noch nicht ausprobiert. 

Als IO nutze ich Beckhoff Module (EL1018, EL1008 und EL2008 sowie Potentialverteilermodule) weil ich das besser finde als die IO Pins der Motortreiber zu nutzen. Brauche eh mehr als die Treiber bieten. 

Als LinuxCNC Rechner und EtherCat Master läuft ein Raspberry Pi5 8GB. Das größte Problem hatte ich mit EMV, EtherCat scheint deutlich anfälliger zu sein als was ich von Profinet auf der Arbeit gewöhnt bin. Deshalb habe ich im mittleren Kanal einen geerdeten Metallsteg eingesetzt, so scheinen die Probleme behoben zu sein. War leider im Platz etwas begrenzt, sonst hätte ich das Schütz -Q1 nicht direkt unter die IO-Module gepackt.