Probing setup

tecno
Topic Author
Offline
Platinum Member

08 May 2019 20:22 #133186 by tecno

Replied by tecno on topic Probing setup

Will do this tomorrow, also do a Axis + probe setup just to verify where the issues are.

When you say comment out all hal and embedded tabs is this the files related to probe screen only?

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

newbynobi
Offline
Moderator

08 May 2019 20:36 #133188 by newbynobi

Replied by newbynobi on topic Probing setup

No, all ones!

I do recommend to split this huge hal files in separate files.
I have a main.hal file, where i just load the rt components and add that ones to the servo thread. This file also contains the axis joint setup, but nothing else.

Second file would be all stuff related to homing.

Third is spindle stuff.

If that does work i have a working machine!

Next would be cooling, next doors, next vacuum, next .....

Also my postgui.hal is a postgui.call list file whitch calls relevant postgui stuff in separate small files, as one for the tool offsets connections to gmoccapy, one for spindle feedback to gmoccapy one for the toolchange dialog etc.

The advantage of doing that way is the easier way to find errors, as you can disable part by part and running configurations etc. Coolant or spindle can just be transfered to hew configs. I bild my configs today just by copy files to bew folders, edit then to fit the new hal pin names and i am done.

Norbert

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

tecno
Topic Author
Offline
Platinum Member

08 May 2019 20:50 #133193 by tecno

Replied by tecno on topic Probing setup

Was für eine Aufgabe, das zu klären

I do not understand how to connect / implement these hal files

But I understand what you say just hard to wrap this around my head.

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

newbynobi
Offline
Moderator

08 May 2019 21:03 #133196 by newbynobi

Replied by newbynobi on topic Probing setup

Just split the files as you need them, save every file in your config folder and load each file with an entry in the ini file.

Read documentation about ini configuration.

Das wird schon alles, ist halt ein wenig Fleisarbeit und Lernen angesagt?

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

tecno
Topic Author
Offline
Platinum Member

11 May 2019 15:32 #133453 by tecno

Replied by tecno on topic Probing setup

I have found the tool change issue, here in ini

HAL]
HALUI = halui
HALFILE = GB_3speed.hal
HALFILE = mpg.hal
POSTGUI_HALFILE = custom_postgui.hal

Here was the error = NO TOOLCHANGE

# Include your custom_postgui HAL commands here
# This file will not be overwritten when you run PNCconf again

net spindle-vel-cmd-rpm-abs   => gmoccapy.spindle_feedback_bar
# net hm2_7i76e.0.7i76.0.0.spinout    => gmoccapy.spindle_feedback_bar

The Tool change was in postgui.hal

###################################################################
#        gmoccapy_postgui.hal file from Norbert Schechner         #
#                        spindle stuff                            #
###################################################################


net   tool-change        gmoccapy.toolchange-change   <=  iocontrol.0.tool-change 
net   tool-changed       gmoccapy.toolchange-changed  <=  iocontrol.0.tool-changed
net   tool-prep-number   gmoccapy.toolchange-number   <=  iocontrol.0.tool-prep-number
net   tool-prep-loop     iocontrol.0.tool-prepare     =>  iocontrol.0.tool-prepared

net   tooloffset-x       gmoccapy.tooloffset-x        <=  motion.tooloffset.x
net   tooloffset-z       gmoccapy.tooloffset-z        <=  motion.tooloffset.z
net tool-prep-loop         iocontrol.0.tool-prepare      <=   iocontrol.0.tool-prepared

Now INI is edited

[HAL]
HALUI = halui
HALFILE = GB_3speed.hal
HALFILE = mpg.hal
POSTGUI_HALFILE = postgui.hal

And this is postgui.hal now

###################################################################
#        gmoccapy_postgui.hal file from Norbert Schechner         #
#                        spindle stuff                            #
###################################################################


net   tool-change        gmoccapy.toolchange-change   <=  iocontrol.0.tool-change 
net   tool-changed       gmoccapy.toolchange-changed  <=  iocontrol.0.tool-changed
net   tool-prep-number   gmoccapy.toolchange-number   <=  iocontrol.0.tool-prep-number
net   tool-prep-loop     iocontrol.0.tool-prepare     =>  iocontrol.0.tool-prepared

net   tooloffset-x       gmoccapy.tooloffset-x        <=  motion.tooloffset.x
net   tooloffset-z       gmoccapy.tooloffset-z        <=  motion.tooloffset.z

# net spindle-vel-cmd-rpm-abs   => gmoccapy.spindle_feedback_bar
net hm2_7i76e.0.7i76.0.0.spinout    => gmoccapy.spindle_feedback_bar

So now tool change is working, but still some issues to be solved, some gmoccapy related and other are probe screen related.

**** GMOCCAPY GETINIINFO ****
Preference file path: gmoccapy_preferences
[]
**** GMOCCAPY INFO ****
**** No gmoccapy2.glade file present ****

**** GMOCCAPY INFO ****
**** audio available! ****
**** GMOCCAPY INFO ****
**** virtual keyboard program found : <onboard>
**** probe_screen GETINIINFO ****
Preference file path: gmoccapy_preferences
**** PROBE SCREEN INFO ****
**** To many increments given in INI File for this screen ****
**** Only the first 5 will be reachable through this screen ****
**** PROBE SCREEN INFO ****
**** no valid probe config in INI File ****
**** disabled auto tool measurement ****
toolnumber = 0 False
**** GMOCCAPY INFO ****
**** replaced btn_zero_g92 to btn_block_height ****
**** GMOCCAPY INFO: Gcode.lang found ****

(gmoccapy:4579): GtkSourceView-CRITICAL **: gtk_source_language_manager_set_search_path: assertion 'lm->priv->ids == NULL' failed
**** GMOCCAPY INFO : inifile = /home/bengt/linuxcnc/configs/GB_3speed/GB_3speed.ini ****:
**** GMOCCAPY INFO : postgui halfile = postgui.hal ****:

(onboard:4592): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
Emit interp-run
Emit interp-run
1 2
Emit interp-run
task: main loop took 0.149095 seconds
estopping / killing gmoccapy
Shutting down and cleaning up LinuxCNC...

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

tecno
Topic Author
Offline
Platinum Member

12 May 2019 11:23 - 12 May 2019 11:26 #133549 by tecno

Replied by tecno on topic Probing setup

Now I have copied the gmoccapy2.glade file from github I get even more errors.

File Attachment:

File Name: 20191205_d...5-12.txt
File Size:8 KB

Last edit: 12 May 2019 11:26 by tecno.

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

newbynobi
Offline
Moderator

12 May 2019 19:38 #133590 by newbynobi

Replied by newbynobi on topic Probing setup

Please read first, prior to copy files arround.
If you do not need gmoccaly screen 2 you do not need to install that file. If you need it, please build your own screen2. If you do not know howto build a glade screen, you do not need screen2!

In the prior post, there is no relevant gmoccapy error, you can igniore the gtk sourceview and the onboard errors.

Screen has started according to the output you posted.

So what is the problem? Please read hal documentation, as all mentioned till today was only missconfigured hal files.

Norbert

Norbert

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

tecno
Topic Author
Offline
Platinum Member

12 May 2019 20:00 #133593 by tecno

Replied by tecno on topic Probing setup

Norbert, do not get me wrong here but why is it that all these *error* message pop up if one just can ignore these? No I do not need screen2 as far as i know. So why is it that the error messages are there if no need for them? Same goes for the Gtk messages, something must be wrong don't you agree?

Not so easy for a beginner to wrap all this mystery around one's head with errors here and there.

Cheers
Bengt

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

newbynobi
Offline
Moderator

12 May 2019 20:11 - 12 May 2019 20:15 #133596 by newbynobi

Replied by newbynobi on topic Probing setup

It is not easy!

The errors i mentioned are not from gmoccapy and have been there for about 5 years, i agree that they are missleading, that is why i mentioned you can ignore them.

I do not see more errors, just a lot of informations!
Probe screen does tell you, that you do not have a valid probe configuration in your ini file!

Norbert

Last edit: 12 May 2019 20:15 by newbynobi.

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

Moderators: newbynobi, HansU

Time to create page: 0.089 seconds

Probing setup

File Attachment:

Attachments: