Probe Basic Help

our hal files look to be almost identical but im still not getting and data to the Probe_basic DRO for the spindle.

i feel like my connection between the correct hal pins and what you showed me earlier is not correct.

here is my hal and ini file.

#==================
# SPINDLE
#==================

[SPINDLE_9]
P = 0.0
I = 0.0
D = 0.0
FF0 = 1.0
FF1 = 0.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0
MAX_OUTPUT = 6225
ENCODER_SCALE = -4096
OUTPUT_SCALE = 6225
OUTPUT_MIN_LIMIT = -6225
OUTPUT_MAX_LIMIT = 6225

Man I'm really sorry, I was thinking about it and it's been 5 years since I setup my configs and I rarely look at the spindle speed. So I went and checked and mine isn't connected either.. I will tinker with it to connect and let you know what is needed.

It actually dawned on me that I bought a high end load sensor back then I intended to install and I completely forgot a out it.. need dig around and find that too and get it installed and connected and working!

so for now your artificially displaying the speed? basically whatever the SXXXX M3/M4 code had? and not an actual encoder signal?

I am using a DMM DST-120 motor ( the biggest thing they had) which obviously has a built in encoder, and that is the signal I am feeding my 7i96.

the gui is setup like that for those not using encoder feedback. it is a way to see the commanded speed and any speed adjustment calculated from the increase of the spindle override setting. for encoder feedback machines I am making the left side spindle rpm display a stacked widget with two readouts. the user can set which they want to be visible in the settings page. I am making the encoder feedback readout a hallabel with a predefined pin base name that will be in the custom_postgui hal file. they will just need to edit for main hal file net pin they want to pull data from. in my case it will pull from the filtered net pin. that should cover everyone and leave it flexible for any type of float input.

however while setting up a py2 dev machine i noticed some breakage that needs to be resolved prior to me pushing a new update for the deb10 version. so may be a few days until that is sorted out.

Thanks for the update. Ill wait till then!

Hi I have tried to install probe basic several times including fresh installs of Linux CNC 2.8.4 Debian 10 Buster PREEMPT RT ISO.
Here is the error i get each time. Error during installation process (com.probebasic.core):
Execution failed (Unexpected exit code: 1): "python -m pip install --user --upgrade git+https://github.com/kcjengr/qtpyvcp.conversational-gcode.git"
I have had a look at the github but i dont see anything that can help me.
I have no idea what my next step from here would be and any help would be appreciated.
Thanks Jim

currently if you are using python 3.11, the pip installs no longer works, we are working on creating a deb package which hopefully will future proof qtpyvcp and probe basic installations.  if you are on older python versions then the script installer is a good way to go, but know that it will soon become broken as well when the python version is upgraded through apt.

Exactly as I suspected I need to learn more about Linux. Currently doing a YouTube course that might even teach me what version of what I have on my machine. Hope the future proofing works out. Thanks for your reply.

thanks, we just had a script installer working flawlessly the other day and the latest batch of updates included python 3.11 and that tanked us so now its a scramble. hopefully nearing the end with the debian package builds, just a few things left to iron out and we will post a link for deb down load and instructions for installing.