Advanced Search

I'm adding a touch probe to a ChinaZone 6040 with a Mesa 7i76e card following what seems to be pretty simple instructions from forum.linuxcnc.org/49-basic-configuratio...obe-with-a-mesa-7i96.  It's really close, but generating an error. 

When I click on "Tool Touch Off Z" in the side panel, I get a blank error (see attached pic):
<l> (?) [x]

Where should I look to find the problem?  I've gone through the example a few times and am just missing it somehow.  I've checked the Linux logs, but haven't found anything yet.

• Axis 2.8.4 (I can upgrade if that would help)
• Hal Meter signal probe-in turns to true when the touch probe is triggered, so the wiring & HAL seem correct
• I've run each of the commands in the ngc file using the MDI tab and they all function as expected
• The 5 updated files are attached and each has it's full path in the comments at the top of the file
  
  Thanks,
  Ted

as a new linux user, can someone give tips on how to install/try this twincat utility?

Python3-distro installed. Installed Mesact 2 from terminal.
Now connected to Mesa board.
Thanks for the help.

Lathe using axis X & Z drives and 7196s

I connected up X-axis to step and direction #1 pins, joint 0 and then calibrated, all working.

Now I'm trying Z-axis, looks like it's supposed to be step and direction #0, joint 1 but it's not working (yet), I'm trying to see the direction pin in HAL show, but can't seem to find it, where can I find the direction pin TB1-4 in HalShow?   

I can see joint.0&1.motor-pos-cmd changing
I can see stepgen.00&01.counts changing

Much appreiated

This is the normal debian.org settings



JT

I tried adding Debian repositories, haven't found the settings Synaptic is happy with security wise.

gbsd86 wrote:

Synaptic repositories
 

OK your using Rod's OS and he prob deleted it the scoundrel LOL

JT

Synaptic repositories

hmm AI says to install distro with pip and that I don't want.

I removed the code that used distro.

JT

This is on my dev PC
JT

would certainly be pretty sweet, PB does change fairly frequently since it isn't in the main linuxcnc repo. and i certainly struggle with good ways to a successful method to ensure users can easily update any required changes.

does this seem like something you might want to run with?if so let me know, you are welcome to join us in the qtpyvcp chat:

matrix.to/#/#qtpyvcp:matrix.org

it is hugely helpful when we get folks who can help propel the project forward! A great group of folks and an awesome supportive culture! feel free to pop in!

Then just send me an mail (adress is in my profile)

In the end, the problem was in the switched analog signal and the GND of the analog signal. After swapping it works without a problem.

I checked OS version (see below). Is Debian 12 Bookworm.
Using Gdebi, installation fails because of python3-distro.
Synaptic search doesn't show python3-distro. Also not in the list of python3 files.
Have the zip file of python3-distro. Haven't been able to figure out how to install it.


g@debianNC:~/Downloads/python3distro/distro-master$ uname -a
Linux debianNC 6.1.0-13-rt-amd64 #1 SMP PREEMPT_RT Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux
g@debianNC:~/Downloads/python3distro/distro-master$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm

For most of the Java applications I've written over the years I included sanity checks of the configuration that executed as early as possible during the startup process before something else had the possibility of crashing due to missing invalid or configuration.

Below is a snippet of code from the Java based DNS server I wrote long ago (unlogic.se/projects/eagledns).

 

Now given how good LinuxCNC and Probe Basic is working I haven't really had to roll up my sleeves and get to familiar with how the bootstrap/initialization of the user interfaces works. But I guess in the case of Probe Basic maybe a hook or method for checking the configuration could be added in QtPyVCP that each derived user interface could then implement and check the configurations before QtPyVCP  proceeds to load the actual GUI.