Advanced Search

You are right, rodw, and I don't particularly like it. But that's how it is.
That part can be taken out, for sure.

Some news. I think it is now narrowed down to debian 12 and probably gcc 12.2
Hannes, your question on trixie, I thought I was on trixie on my development pc, no I was on 12.13.
And suspicion about va_args.
So I upgraded to trixie and gcc 14.2.0.
Recompiled, and now it doesn't segv anymore.
It continues after a short break, like it should.
The problem is in libusb1.0 when compiled with gcc 12 (if I understand right).
 

Thanks! I had completely forgotten to add the "user_dro_display" files to my machine configuration. Copying them over from the sim files fixed it.

In my case I had a deadman's switch that had to be held down to enable the jog wheel on the pendant so I set teleop mode when that button was pressed.  I don't think you should allow just jogging the wheel to change modes. There are some safety rules around this stuff. And yes having to switch modes to jog on screen or a pendant is frustrating but probably for safety.

The current component tries to change to manual/teleop mode even with a program running/paused. The changes made by Hannes prevents that. However, if a program is not running/paused and you start jogging, it will change to manual/teleop mode automatically. It could of course be discussed if the pendant should be "allowed" to do this just by jogging the wheel. But the PR by Hannes is really mainly bugfixes, so I would presume that it's best not to alter the behavior of the pendant more than necessary.

I have not been following this but if the system fails with a program running, there is a fault with the driver logic. Jogging should not be permitted unless the machine is in teleop mode and programs are not permitted to run in teleop mode.

The driver could request teleop mode with halui.mode.teleop and this will prevent a program from running. I did this with a hard wired pendant. Gmocappy is a good gui to demonstrate this because setting teleop mode makes it display the jog buttons.

The assert statement is setupAsyncTransfer() is the "big" issue. Simply removing that causes the reconnect to be triggered when trying to send a display update. For me that reconnection works without problems. For Hakan, it gets stuck/segfaults in libusb after reconnect. Somewhere along these lines:
forum.linuxcnc.org/38-general-linuxcnc-q...ment?start=80#343687
It would of course be good to get to the bottom of this. But since I can't reproduce this, it's a bit difficult to debug.

Both myself (with the original firmware) and Hakan can trigger the disconnect reliably by using the original component and jogging while a program is running.

On the development computer, I use the LinuxCNC 2.9.8 iso image / Debian 13. That one has libusb 1.0.28-1. I'm not at that computer right now, so cannot check the kernel version. But it's the stock one from LinuxCNC 2.9.8 iso (unless "apt upgrade" has updated it).

The standard 4b installer should install the xfce desktop.

The gnome-desktop is empty by default until you find stuff in the search bar and add it. I have not run it for years (last was on bullseye) but it was a bit daunting!

Sounds like something has gone wrong....

You could choose a desktop if you
sudo apt update
sudo apt install tasksel
sudo tasksel

Please run menu-config to set your wifi
 

Don't you hate it when AI quotes you back to yourself! 

Hi - I'm looking for new or used Mesa 7i96S board for CNC lathe conversion - Delivery to Hong Kong. Any simple alternatives for this if not available?

I'm converting WM210V lathe - so for inputs there will be two steppers/drivers, rotary encoder, lathe motor control board via three wires from potentiometer. Plan to use RPi Linuxcnc distro which i have been already playing around with.  

Thanks!

Anyone know why was this topic deleted?

Sorry i can not find anything causing that.
Can you start new topics as a continuation of those two and i can post the links there?
And please do not use the same exact tittles as the old ones, anything different to easier discern.
Thank you for your patience.

Are you sure it is +-15V ?
Maybe +-15V / KRPM ?

Does 7i76EU have field power?

hi. after running pncconf wizard, I cannot load linuxcnc because of error below, i was trying to setup sn04-p2 type proximity sensors on tb6 pins 0,1,2 and probe and estop on 4,5. Any ideas to resolve please? (note, im new to mesa and linuxcnc) thanks

Debug file information:
Note: Using POSIX realtime
./3020f.hal:31: Pin 'hm2_7i76e.0.7i76.0.0.input-00' does not exist
3994