Setting up Probe Basic on my machine questions and issues

More
1 year 8 months ago - 1 year 8 months ago #321408 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:
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.
[/code]
Last edit: 1 year 8 months ago by yoshimitsuspeed.

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

More
1 year 8 months ago #321409 by yoshimitsuspeed
If I click ignore the UI still closes and linuxcnc reports the following. 

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

More
1 year 8 months ago #321412 by yoshimitsuspeed
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

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

More
1 year 8 months ago - 1 year 8 months ago #321413 by Lcvette
JOG is required but metric increments can be used I'll

Try commenting out the usertabs ini setting

Delete custom Hall file in ini
Last edit: 1 year 8 months ago by Lcvette.

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

More
1 year 8 months ago #321478 by yoshimitsuspeed
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.

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

More
1 year 8 months ago #321480 by yoshimitsuspeed
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.

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

Moderators: KCJ, Lcvette
Time to create page: 0.271 seconds
Powered by Kunena Forum