qtdragon - probing issues

More
3 years 4 months ago - 3 years 4 months ago #273523 by rodw
Replied by rodw on topic qtdragon - probing issues
Probably reinstall linuxcnc from debs.
This explains how to do it for Bookworm
  linuxcnc.org/docs/2.9/html/getting-start...etting-linuxcnc.html
If you are on Bullseye change bookworm to bullseye on this linesudo echo "deb buildbot2.highlab.com/debian/ bookworm 2.9-uspace" | sudo tee -a
Last edit: 3 years 4 months ago by rodw.

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #273524 by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon - probing issues
I'm using Bookworm and 2.9. I'll give that a try.

Thanks Rod.
The following user(s) said Thank You: rodw

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #273527 by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon - probing issues
I loaded the latest version per Rods instructions. Probing is now somewhat working.

What I am seeing now is when probing Z, the initial probe is VERY slow. After it makes initial contact the probe backs off at (PROBE RAPID) and then probes at (PROBE SPEED).

I have also notice that the touch screen randomly stops working but the mouse clicks still works. Some times I will push a button and LCNC just exits.

I was able to get this from a report during a failure:
[QTvcp.QTVCP.WIDGETS.BASIC_PROBE][[36mINFO[0m] Basic Probing routine completed without errors (basic_probe.py:231)
[QTvcp.QTVCP.WIDGETS.BASIC_PROBE][[36mINFO[0m] Probe Process finished - exitCode 0 exitStatus 0 (basic_probe.py:212)
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
/usr/bin/linuxcnc: line 977: 9020 Segmentation fault $EMCDISPLAY -ini "$INIFILE" $EMCDISPLAYARGS $EXTRA_ARGS
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
8970
9016
Stopping realtime threads
Unloading hal components
RTAPI_PCI: Unmapped 65536 bytes at 0x7f0394bdd000
Note: Using POSIX realtime

I think the Segmentation fault is the most concerning here.

I also got a QTVCP error in /usr/lib/python3.11/json/decoder.py line 340, in decode. Extra data in Line 2 column 1 (char 199)

I'll keep playing and gathering data.

John

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #273536 by tommylight
Try using a usb on the back of PC.
If this is a RPI, they tend to have issues with power and powering USB ports so a good power supply with a good cable is a must.
If the touch is USB ppwered, try another cable.
Unplug USB you do not need .

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #273547 by JohnnyCNC
Replied by JohnnyCNC on topic qtdragon - probing issues
I'm using a BAT1-J1800 with a USB pendant and an ASUS USB touch screen. I never had this problem with 2.8.4. I think I am running Ubuntu Mint 19.3 on that SSD. I 'm just swapping SSDs to go between my working machine and the new setup I am testing.

I could test without the pendant since the screen jogging works. I am also not sure that when I say the touch screen doesn't work that it is an across the board thing. I check for that the next time I am testing. I also noticed that sometimes I just have to push the button a little longer. Usually a quick tap is all it takes.

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #273548 by rodw
Replied by rodw on topic qtdragon - probing issues
Your PC is clearly not happy with its USB side of things.
lsusb is nothing to do with Linuxcnc
Seems like a USB device is being disconnected randomly (hotplug)
If there is a hardware fault, the slow performance could be explained by spurious interrupts.

If your J1800 has a Baytrail chipset, there is a long standing linux bug with spurious overtemperature errors.
I would have thought it should be fixed in  kernel 6.1
 

Please Log in or Create an account to join the conversation.

Moderators: cmorley
Time to create page: 0.442 seconds
Powered by Kunena Forum