Auto Tool Measurement setup,makes gmoccapy slow and difrent configation,

More
30 Apr 2023 14:01 #270308 by Aciera
the problem is in line 9 of your 'test2.11.hal':

source postgui_call_list.hal

This needs to be removed as it tries to access pins that are not yet available.

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

More
22 Jul 2023 18:27 #276009 by Kasper-001
hey i have moved it around , and replaced line 9 with   source custom_postgui.hal

but still get this 
Debug file information:
custom_postgui.hal:11: Pin 'gmoccapy.toolchange-change' does not exist

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

More
22 Jul 2023 20:11 #276015 by Aciera
The line needs to be _removed_.
The point is that having it there in the hal file will try to load gui-pins that are created only _after_ the hal file is executed. Hence the "postgui" entry in the ini file which means "hal file to be executed after the gui is created".

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

More
22 Jul 2023 20:24 - 22 Jul 2023 20:25 #276017 by Kasper-001
then i get this

hm2/hm2_7i92.0: registered
creating ladder-state
Found file(REL): ./custom.hal
CANNOT FIND FILE FOR:custom_postgui
Shutting down and cleaning up LinuxCNC...
Init tmp dir=/tmp/classicladder_tmp_GPq2hi
INFO CLASSICLADDER---I/O Modbus master closed!
extra emc serial data=8, parity=0, stop=1
INFO CLASSICLADDER---I/O Modbus master (Serial) init ok !
Running HAL shutdown script
ERROR CLASSICLADDER-   Error initializing classicladder user module.
hm2_eth: in hm2_eth_reset
hm2_eth: HostMot2 ethernet driver unloaded
hm2: unloading
Note: Using POSIX realtime
LinuxCNC terminated with an error.  You can find more information in the log:
    /home/cnc/linuxcnc_debug.txt
and
    /home/cnc/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal
cnc@debian:~$ 




my ini 
[HAL]
HALUI = halui
HALFILE = test2.11.hal
HALFILE = custom.hal
HALFILE = custom_postgui hal
POSTGUI_HALFILE = postgui_call_list.hal
SHUTDOWN = shutdown.hal
 
Last edit: 22 Jul 2023 20:25 by Kasper-001.

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

More
22 Jul 2023 20:34 #276018 by Aciera
First thing is to remove this line in your ini:
HALFILE = custom_postgui hal

second please post the content of this file:
postgui_call_list.hal

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

More
22 Jul 2023 20:52 #276019 by Kasper-001
custom_postgui hal removed from ini

# These files are loaded post GUI, in the order they appear

source custom_postgui.hal
 

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

More
22 Jul 2023 20:57 #276020 by Aciera
Looks ok.
So on startup these two hal files will be executed:
HALFILE = test2.11.hal
HALFILE = custom.hal

And after the gui is running this postgui-hal file will be executed
custom_postgui.hal

Are you getting any errors on startup now?

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

More
22 Jul 2023 21:02 #276021 by Kasper-001
it startes very slow , and does not look the same

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

More
22 Jul 2023 21:14 #276023 by Aciera

it startes very slow , and does not look the same

Not much to go on. Starting your configuration in a terminal may give you more information in the form of terminal output while the config starts.

Open terminal type:
$ linuxcnc
and choose your configuration in the config picker.

Alternatively try:
$ linuxcnc -l

(That is a lowercase L to load the last used configuration)

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

More
22 Jul 2023 21:22 #276024 by Aciera
Just as a side note as this is probably not the core problem:
I don't use auto tool measurement but looking at your custom_postgui.hal shows all the lines are commented out (ie this will not do anything at all):
# Include your custom_postgui HAL commands here
# This file will not be overwritten when you run PNCconf again


# The next lines are only needed if the pins had been connected before
#unlinkp iocontrol.0.tool-change
#unlinkp iocontrol.0.tool-changed
#unlinkp iocontrol.0.tool-prep-number
#unlinkp iocontrol.0.tool-prepared
# link to gmoccapy toolchange, so you get the advantage of tool description on change dialog

#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

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

Time to create page: 0.204 seconds
Powered by Kunena Forum