(Solved) Difficulties Setting Up Probe Basic

More
30 Jul 2021 17:29 - 02 Aug 2021 01:12 #216365 by TannerFrisby
This issue has been resolved. Beneath is the summary, followed by the original post. This thread was previously called "Difficulties Setting Up Probe Basic". I have changed the thread title to better reflect the searchable terms someone experiencing a similar difficulty may use. 

Back Stroy: I had a machine configuration that used the default "Axis" display on Linux CNC 2.8 stretch preempt rt kernel. I attempted to change the display to "Probe Basic" after seeing it used on someone else's setup. I used the quick install and changed my configuration ini file to "DISPLAY = probe_basic". I could no longer launch my configuration.

Starting Hardware: Dell Optiplex 760 computer, HP L1950 Monitor, Mesa 7i76e, Canakit wifi dongle, wired usb keyboard, wireless usb mouse. 

Symptoms: I could open the LinuxCNC configuration with "DISPLAY =  axis" in the ini file but failed to launch when "DISPLAY = probe_basic". The probe basic screen would flicker on for a half-second before closing and outputting an error message (see attached error messages through the thread). After upgrading the monitor (see resolutions), I no longer saw the flicker, but still received an error and couldn't open. 

Resolutions: I was not using a monitor with the appropriate resolution and my computer was not capable of using OpenGL 2.1. I replaced my "1280 x1024" monitor with a required "1920 x 1080" and installed a graphics card (Dell AMD Radeon R5 240 1GB DDR3). 

/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Greetings all,

Hardware: Mesa 7i76e, 4-closed loop stepper drivers, gantry style XYZZ mill, 19" 1280 x 1024 monitor (not the recommended resolution for probe basic)
Software: Configuration works with axis display, but I am having an issue with probe basic. 
_________________________________________________________________

I am trying to set-up a probe basic user interface as I plan to integrate probing into my workflow.
I followed the installation guide here: kcjengr.github.io/probe_basic/quick_start.html

I edited a working .ini file with the following:

#DISPLAY = axis
DISPLAY = probe_basic

When I launch LinuxCNC, I get the attached error message.

 

File Attachment:

File Name: linuxcnc.report.txt
File Size:12 KB


Here is my attempted analysis:
________________________________

check_config: (trivkins kinematics) WARNING:
  INCONSISTENT coordinates specifications:
               trivkins coordinates=XYZZ
               [TRAJ]COORDINATES=XYZ

Comes from my double gantry system, but I'm not sure how to resolve this, or if I even need to.

[qtpyvcp.utilities.info][[36mINFO[0m]  The number of joints (4) is not equal to the number of coordinates (3) (info.py:391)
[qtpyvcp.utilities.info][[36mINFO[0m]  It is highly recommended that you update your config. (info.py:392)
[qtpyvcp.utilities.info][[36mINFO[0m]  Reverting to old style. This could result in incorrect behavior... (info.py:393)

Not tickled about these warnings though. I think it should be a non--issue as described later in my "intent" section.
___________________________________________

This seems to be the real crux:

hm2_eth: ERROR: Failed to execute '/sbin/sysctl -q net.ipv6.conf.eth0:avahi.disable_ipv6=1'
[...]
sysctl: cannot stat /proc/sys/net/ipv6/conf/eth0:avahi/disable_ipv6: No such file or directory

I would appreciate help with resolve this.
______________________________________________

My intent is to run an "AC 5-Axis table" on my currently XYZZ mill. I am using qty-4 closed-loop stepper motors and drivers and have a total of 5 step/dir outputs from my mesa 7i76e. First I plan on homing my ZZ joints using my current configuration. I will then close linuxCNC and open a (not yet made) 5-axis 5-joint configuration (while maintaining continuous power to the two Z drivers). I will manually flip a switch that will connect my 2 Z-driver's step pins in parallel and dir pins in parallel. Now a single step/dir pair from the mesa will drive both Z-drivers which have already been timed together. This will allow me to have an XYZ(Z)AC configuration with 6 drivers using 5 step/dir pairs. This should also eliminate the above joint/axis warning for the 5-axis configuration.

Attached is my .ini

 

File Attachment:

File Name: Eldorado.ini
File Size:5 KB


Thank you for taking the time to read through my issues. Any help is greatly appreciated!
-Tanner Frisby
Attachments:
Last edit: 02 Aug 2021 01:12 by TannerFrisby. Reason: Adding TL;DR summary, changing the title, closing the thread
The following user(s) said Thank You: Lcvette

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

More
31 Jul 2021 03:37 - 31 Jul 2021 03:51 #216418 by MoshKopp
It seems to be a problem with you gfx.card.
can you try a newer one that supports OpenGL 2.1

And what is the output of
ifconfig or ip a
 
Last edit: 31 Jul 2021 03:51 by MoshKopp.
The following user(s) said Thank You: Lcvette

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

More
31 Jul 2021 04:35 #216419 by Lcvette
Probe basic will only work with 1920x1080 screen resolution.

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

More
31 Jul 2021 04:35 #216420 by TannerFrisby
Thank you for such a quick reply. I am always impressed by this community.

By opening a terminal and typing 'ip a', I get the following:

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:25:64:e3:7c:40 brd ff:ff:ff:ff:ff:ff
    inet 169.254.7.199/16 brd 169.254.255.255 scope link eth0:avahi
       valid_lft forever preferred_lft forever
    inet6 fe80::225:64ff:fee3:7c40/64 scope link
       valid_lft forever preferred_lft forever

_______________________________________

Repeating the above with my "canakit wifi usb dongle", I get:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:25:64:e3:7c:40 brd ff:ff:ff:ff:ff:ff
    inet 169.254.7.199/16 brd 169.254.255.255 scope link eth0:avahi
       valid_lft forever preferred_lft forever
    inet6 fe80::225:64ff:fee3:7c40/64 scope link
       valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 1c:bf:ce:97:27:86 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.27/24 brd 192.168.0.255 scope global dynamic wlan0
       valid_lft 3489sec preferred_lft 3489sec
    inet6 2601:2c6:4700:54f0:1ad:c239:67a0:afe7/64 scope global noprefixroute dynamic
       valid_lft 3599sec preferred_lft 3599sec
    inet6 fe80::a35d:f56c:c8a6:e487/64 scope link
       valid_lft forever preferred_lft forever

I'm including this information as I get an error (I think connecting to the mesa card over ethernet) when I have my wifi dongle plugged in. I was going to start a separate thread asking about this later, but this seems like an opportune time.

______________________________________

As for the graphics card, is this the correct information?

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)

This is a $30 Craigslist special (Dell Optiplex 760) that was old enough to have a DB-25 parallel port.

If the graphics card (or lack thereof?) is the issue, could you recommend one to stuff in my mini-tower?

 

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

More
31 Jul 2021 04:39 - 31 Jul 2021 04:42 #216421 by TannerFrisby
Lcvette, is there a way to tell if this is my only issue? Also, is there a way to fit a 1920 x 1080 on my 19" 1280 x 1024 monitor, maybe with some unused black margins?

I will look into setting up a 1920 x 1080 monitor this weekend. 

Thanks,
Tanner Frisby
Last edit: 31 Jul 2021 04:42 by TannerFrisby.

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

More
31 Jul 2021 04:42 #216422 by Lcvette
No, the minimum resolution required is 1920x1080, is hard coded in by myself. Just wanted to let you know before you go buying parts. If you have no plans to use a monitor with that resolution then you won't be able to use probe basic. If you do then let us know when you have that monitor and we can continue on resolving the other issues.

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

More
31 Jul 2021 04:44 #216423 by TannerFrisby
Understood. In that case, I will swap monitors and report back.

-Tanner Frisby
The following user(s) said Thank You: Lcvette

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

More
31 Jul 2021 05:34 - 31 Jul 2021 05:34 #216426 by PCW
I'm pretty sure the built in Intel graphics of Core-Duo vintage
PCs do not support Open GL 2.1 (I had to add a graphics card
to try ProbeBasic on my old HP DC7800 which is similar to your dell)

The Ethernet issue is likely because you did not setup a static IP address
on the Ethernet port (10.10.10.100 suggested if the 7I76E is at 10.10.10.10)
Last edit: 31 Jul 2021 05:34 by PCW.

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

More
31 Jul 2021 16:02 - 31 Jul 2021 16:48 #216462 by TannerFrisby
Greetings all,
I switched to a monitor with the correct resolution (HP LV2311). Sadly, i still cannot launch DISPLAY = probe_basic. Just to verify, I am able to launch with the only change being DISPLAY = axis. 

Attached is my most recent error report. I looked at it briefly and it appears to be largely the same. After updating/upgrading from terminal, it looks like I went from 2.8.0 to 2.8.2: LINUXCNC - 2.8.0-pre3-68-ga88536efc2-20-gacab27a90
SMP PREEMPT RT Debian 4.9.228-1 (2020272-2 (2021-07-0519)
Also, my monitor change is reflected: display size: 1280x10241920x1080 pixels (338x270508x286 millimeters)
It appears a fair bit changed in the "traceback (most recent call last)" section, but I can't determine if it is relevant. 

File Attachment:

File Name: linuxcnc.r...7-31.txt
File Size:10 KB


Furthermore, here is some information about my OpenGL compatability:

glxinfo | grep 'version'
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 2.0
OpenGL version string: 2.1 Mesa 13.0.6
OpenGL shading language version string: 1.20
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 13.0.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16

What should my next troubleshooting steps be?
Attachments:
Last edit: 31 Jul 2021 16:48 by TannerFrisby.

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

More
31 Jul 2021 20:00 #216479 by Lcvette
First test is to try running the simulation version of probe basic to determine if it's hardware or software

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

Moderators: KCJLcvette
Time to create page: 0.129 seconds
Powered by Kunena Forum