Setting up Probe Basic on my machine questions and issues
- yoshimitsuspeed
- Offline
- Elite Member
-
Less
More
- Posts: 165
- Thank you received: 0
13 Feb 2025 03:30 - 13 Feb 2025 03:42 #321408
by yoshimitsuspeed
Setting up Probe Basic on my machine questions and issues was created by yoshimitsuspeed
I'm working on getting PB installed. I went with the Dev version waiting for the rack toolchange updates to come through.
I'm pretty sure I did all the config stuff per the documentation page properly. I did it twice now as the first time I used my config that I had run QTDragon so when I got errors I figured I would start with a fresh axis only setup just in case.
So after going through the setup and config process, editing the files, etc, when I went to start up PB by clicking on my machines launcher it gave an error CANNOT FIND FILE FOR:custom.hal which was removed per instructions.
In the ini I added the lines in the instructions but it doesn't say to remove HALFILE = custom.hal so I didn't.
I can add custom.hal file back in or comment out that halfile line and restarting it will load to the next set of errors.
Next error I got was
FileNotFoundError: [Errno 2] No such file or directory: '/home/shopbot/linuxcnc/configs/Shopbot/linuxcnc.var'
So I changed file probe_basic.var to linuxcnc.var assuming that's all that was needed.
At this point it loads to the PB screen and a pop up with this error comes up.
[/code]
I'm pretty sure I did all the config stuff per the documentation page properly. I did it twice now as the first time I used my config that I had run QTDragon so when I got errors I figured I would start with a fresh axis only setup just in case.
So after going through the setup and config process, editing the files, etc, when I went to start up PB by clicking on my machines launcher it gave an error CANNOT FIND FILE FOR:custom.hal which was removed per instructions.
In the ini I added the lines in the instructions but it doesn't say to remove HALFILE = custom.hal so I didn't.
I can add custom.hal file back in or comment out that halfile line and restarting it will load to the next set of errors.
Next error I got was
FileNotFoundError: [Errno 2] No such file or directory: '/home/shopbot/linuxcnc/configs/Shopbot/linuxcnc.var'
So I changed file probe_basic.var to linuxcnc.var assuming that's all that was needed.
At this point it loads to the PB screen and a pop up with this error comes up.
Traceback (most recent call last):File "/usr/bin/probe_basic", line 8, in sys.exit(main())^^^^^^File "/usr/lib/python3/dist-packages/probe_basic/__init__.py", line 20, in mainqtpyvcp.run_vcp(opts, VCP_CONFIG_FILE)File "/usr/lib/python3/dist-packages/qtpyvcp/__init__.py", line 26, in run_vcprun(*args, **kwargs)File "/usr/lib/python3/dist-packages/qtpyvcp/app/__init__.py", line 129, in runlaunch_application(opts, config)File "/usr/lib/python3/dist-packages/qtpyvcp/app/launcher.py", line 78, in launch_applicationloadWindows(config['windows'])File "/usr/lib/python3/dist-packages/qtpyvcp/app/launcher.py", line 230, in loadWindowswindow = _initialize_object_from_dict(window_dict)^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^File "/usr/lib/python3/dist-packages/qtpyvcp/app/launcher.py", line 210, in _initialize_object_from_dictreturn obj(*args, **kwargs)^^^^^^^^^^^^^^^^^^^^File "/usr/lib/python3/dist-packages/probe_basic/probe_basic.py", line 53, in __init__self.load_user_tabs()File "/usr/lib/python3/dist-packages/probe_basic/probe_basic.py", line 87, in load_user_tabsuser_tab_folders = os.listdir(user_tabs_path)^^^^^^^^^^^^^^^^^^^^^^^^^^FileNotFoundError: [Errno 2]
No such file or directory: 'user_tabs/ # REQUIRED Setting for Probe Basic'
User tabs is in the folder so I'm not sure what to do here.
Last edit: 13 Feb 2025 03:42 by yoshimitsuspeed.
Please Log in or Create an account to join the conversation.
- yoshimitsuspeed
- Offline
- Elite Member
-
Less
More
- Posts: 165
- Thank you received: 0
13 Feb 2025 03:34 #321409
by yoshimitsuspeed
Replied by yoshimitsuspeed on topic Setting up Probe Basic on my machine questions and issues
If I click ignore the UI still closes and linuxcnc reports the following.
Please Log in or Create an account to join the conversation.
- yoshimitsuspeed
- Offline
- Elite Member
-
Less
More
- Posts: 165
- Thank you received: 0
13 Feb 2025 03:50 #321412
by yoshimitsuspeed
Replied by yoshimitsuspeed on topic Setting up Probe Basic on my machine questions and issues
Also is this required in imperial for a metric machine? Because my machine is in metric and I don't like it lol.
INCREMENTS = JOG .01in .001in .0001in # REQUIRED Setting for Probe Basic
INCREMENTS = JOG .01in .001in .0001in # REQUIRED Setting for Probe Basic
Please Log in or Create an account to join the conversation.
- Lcvette
-
- Offline
- Moderator
-
Less
More
- Posts: 1305
- Thank you received: 650
13 Feb 2025 04:07 - 13 Feb 2025 04:09 #321413
by Lcvette
Replied by Lcvette on topic Setting up Probe Basic on my machine questions and issues
JOG is required but metric increments can be used I'll
Try commenting out the usertabs ini setting
Delete custom Hall file in ini
Try commenting out the usertabs ini setting
Delete custom Hall file in ini
Last edit: 13 Feb 2025 04:09 by Lcvette.
Please Log in or Create an account to join the conversation.
- yoshimitsuspeed
- Offline
- Elite Member
-
Less
More
- Posts: 165
- Thank you received: 0
13 Feb 2025 20:20 #321478
by yoshimitsuspeed
Replied by yoshimitsuspeed on topic Setting up Probe Basic on my machine questions and issues
Ah progress. I commented out usertabs and relaunch it does the same for
raise IOError('The specified POSTGUI_HALFILE does not exist: %s' %
OSError: The specified POSTGUI_HALFILE does not exist: /home/shopbot/linuxcnc/configs/Shopbot/probe_basic_postgui.hal # ONLY 1 postgui hal file can be called at launch
Then between your comment being included in the error and then I noticed in Geany they were not red like other comments I tried deleting the # recommended/required comment after the lines that were throwing errors and the errors went away.
raise IOError('The specified POSTGUI_HALFILE does not exist: %s' %
OSError: The specified POSTGUI_HALFILE does not exist: /home/shopbot/linuxcnc/configs/Shopbot/probe_basic_postgui.hal # ONLY 1 postgui hal file can be called at launch
Then between your comment being included in the error and then I noticed in Geany they were not red like other comments I tried deleting the # recommended/required comment after the lines that were throwing errors and the errors went away.
Please Log in or Create an account to join the conversation.
- yoshimitsuspeed
- Offline
- Elite Member
-
Less
More
- Posts: 165
- Thank you received: 0
13 Feb 2025 20:59 #321480
by yoshimitsuspeed
Replied by yoshimitsuspeed on topic Setting up Probe Basic on my machine questions and issues
After removing # comments throwing errors PB still wouldn't switch the power on so I went and deleted all the # comments on lines after code and now it seems to be working properly.
I am used to code that accepts comments after code lines like that so I figured it would be best to keep it in there for reference but it didn't work till I deleted them all.
I suppose I could have tried putting them above or below if I cared enough. I assume that would work.
I just got in. Only note so far is the home all button being labeled HOMED is a little confusing.
I am used to code that accepts comments after code lines like that so I figured it would be best to keep it in there for reference but it didn't work till I deleted them all.
I suppose I could have tried putting them above or below if I cared enough. I assume that would work.
I just got in. Only note so far is the home all button being labeled HOMED is a little confusing.
Please Log in or Create an account to join the conversation.
- Lcvette
-
- Offline
- Moderator
-
Less
More
- Posts: 1305
- Thank you received: 650
13 Feb 2025 22:29 #321487
by Lcvette
Replied by Lcvette on topic Setting up Probe Basic on my machine questions and issues
when in doubt, it help to read the instructions which tell you to delete those comments 
Attachments:
Please Log in or Create an account to join the conversation.
- yoshimitsuspeed
- Offline
- Elite Member
-
Less
More
- Posts: 165
- Thank you received: 0
21 Feb 2025 00:23 #322136
by yoshimitsuspeed
Replied by yoshimitsuspeed on topic Setting up Probe Basic on my machine questions and issues
Fair enough. I thought I had gone through all the steps but I guess I missed it.
I just got a touch probe and want to set it up alongside my tool height setter.
Turns out the tool height setter I bought years ago is NC.
Without even thinking about checking I bought a NO probe which if I am thinking about it correctly if I wanted to wire them into the same pin it would have to be NO.
From what I can tell in reading though it seems like I should be able to wire them into separate pins on my 7i76e, distinguish one as NO, the other as NC, and get it to function properly correct?
And from reading it does sound like LinuxCNC still only has one probe function right? So in the configs I tie both sensors/pins to the single probe function correct?
I just got a touch probe and want to set it up alongside my tool height setter.
Turns out the tool height setter I bought years ago is NC.
Without even thinking about checking I bought a NO probe which if I am thinking about it correctly if I wanted to wire them into the same pin it would have to be NO.
From what I can tell in reading though it seems like I should be able to wire them into separate pins on my 7i76e, distinguish one as NO, the other as NC, and get it to function properly correct?
And from reading it does sound like LinuxCNC still only has one probe function right? So in the configs I tie both sensors/pins to the single probe function correct?
Please Log in or Create an account to join the conversation.
- Lcvette
-
- Offline
- Moderator
-
Less
More
- Posts: 1305
- Thank you received: 650
21 Feb 2025 01:00 #322143
by Lcvette
Replied by Lcvette on topic Setting up Probe Basic on my machine questions and issues
There is a way to do it in Hal, run a search on the forum for an example. I don't have one handy to share,. But it was xor component used I think from memory. Or maybe someone has something setup they can share.
Please Log in or Create an account to join the conversation.
- yoshimitsuspeed
- Offline
- Elite Member
-
Less
More
- Posts: 165
- Thank you received: 0
21 Feb 2025 01:39 #322151
by yoshimitsuspeed
Replied by yoshimitsuspeed on topic Setting up Probe Basic on my machine questions and issues
I found a couple posts earlier that were talking about using basically an or argument. Looking like this must be kind of what they were talking about.
My understanding being that this allows you to use one or the other which solves most issues.
It is weird because I was reading about using a touch probe and tool setter together as a way to do tool offsets and or just to zero the probe and I would have been sure I read that here or other linuxcnc group but maybe not.
So in a quick search it looks like XOR can be used to deal with one sensor being NO and the other being NC, but they are still only tying to the one probe function right?
I read a post where you Lcvett talked about setting offset on a cutter, facing a surface, then calibrating your probe off that surface. Which solves the one use case I can imagine for wanting to use both but it seems like a pretty janky solution.
I can see having two probes with two moving elements adds some complexity and probably some stack up. Is this just considered an unacceptable solution to calibrate Z on a probe? Or is it just that no one has bothered to implement a useful feature because it's not a priority?
My understanding being that this allows you to use one or the other which solves most issues.
It is weird because I was reading about using a touch probe and tool setter together as a way to do tool offsets and or just to zero the probe and I would have been sure I read that here or other linuxcnc group but maybe not.
So in a quick search it looks like XOR can be used to deal with one sensor being NO and the other being NC, but they are still only tying to the one probe function right?
I read a post where you Lcvett talked about setting offset on a cutter, facing a surface, then calibrating your probe off that surface. Which solves the one use case I can imagine for wanting to use both but it seems like a pretty janky solution.
I can see having two probes with two moving elements adds some complexity and probably some stack up. Is this just considered an unacceptable solution to calibrate Z on a probe? Or is it just that no one has bothered to implement a useful feature because it's not a priority?
Please Log in or Create an account to join the conversation.
Moderators: KCJ, Lcvette
Time to create page: 0.096 seconds