Probe Basic program run time stays 0:00:00
06 Apr 2022 22:47 #239477
by cheburs
Probe Basic program run time stays 0:00:00 was created by cheburs
Timer doesn't start when i run gcode and always stays 0:00:00
Have added in .iniand
time.hal contains:
My config - github.com/kriksis/Thor-cnc-7i76
Thnaks!
Have added in .ini
POSTGUI_HALFILE = hallib/time.hal
time.hal contains:
loadrt time
loadrt not
addf time.0 servo-thread
addf not.0 servo-thread
net prog-running not.0.in <= halui.program.is-idle
net cycle-timer time.0.start <= not.0.out
net cycle-seconds qtpyvcp.timerseconds.in <= time.0.seconds
net cycle-minutes qtpyvcp.timerminutes.in <= time.0.minutes
net cycle-hours qtpyvcp.timerhours.in <= time.0.hours
My config - github.com/kriksis/Thor-cnc-7i76
Thnaks!
Please Log in or Create an account to join the conversation.
06 Apr 2022 23:24 #239479
by Lcvette
Replied by Lcvette on topic Probe Basic program run time stays 0:00:00
What version? If this is 2.9 master py3 branch time is not used anymore and you need to use the probe_basic post GUI Hal file instead, the time code is now in there
Please Log in or Create an account to join the conversation.
06 Apr 2022 23:44 #239481
by cheburs
Replied by cheburs on topic Probe Basic program run time stays 0:00:00
Its 2.8.2
Please Log in or Create an account to join the conversation.
11 Apr 2022 19:55 #239967
by Lcvette
Replied by Lcvette on topic Probe Basic program run time stays 0:00:00
you need to condense your post gui files into one file, i think only one can be called. likely why time.hal is not functioning correctly
Please Log in or Create an account to join the conversation.
11 Apr 2022 23:06 - 11 Apr 2022 23:07 #239994
by andypugh
Replied by andypugh on topic Probe Basic program run time stays 0:00:00
You can call a single POSTGUI_HALFILE that contains references to several other HAL files:you need to condense your post gui files into one file, i think only one can be called. likely why time.hal is not functioning correctly
# Ordinary halfile commands
net somesignal somepin someotherpin
# Include HAL from a separate file
source halfile1.hal
# and another file
source halfile2.hal
# and carry on with normal hal-y things
net signel56 pyvcp.0.in1....
Last edit: 11 Apr 2022 23:07 by andypugh.
Please Log in or Create an account to join the conversation.
12 Apr 2022 15:07 - 12 Apr 2022 15:08 #240053
by cheburs
Replied by cheburs on topic Probe Basic program run time stays 0:00:00
It worked putting all in one postgui file.
Im using vistacnc pendant and in their .hal file there is this line -
and also time.hal uses pin halui.program.is-idle.
I get an error that pin is already linked.
How can i make them both happy?
Im using vistacnc pendant and in their .hal file there is this line -
net program.is-idle halui.program.is-idle => vc-p4s.program.is-idle
I get an error that pin is already linked.
How can i make them both happy?
Last edit: 12 Apr 2022 15:08 by cheburs.
Please Log in or Create an account to join the conversation.
12 May 2022 09:23 #242767
by GuiHue
Replied by GuiHue on topic Probe Basic program run time stays 0:00:00
With halui.program.is-idle being an out pin, simple modifactions of the pin assignment should work:
Delete from above:
net prog-running not.0.in <= halui.program.is-idle
replace by:
net program.is-idle not.0.in
You can connect a HAL out pin to multiple IN pins, however, it must be within one signal name. The signal name ist the first part after the net command.
Delete from above:
net prog-running not.0.in <= halui.program.is-idle
replace by:
net program.is-idle not.0.in
You can connect a HAL out pin to multiple IN pins, however, it must be within one signal name. The signal name ist the first part after the net command.
Please Log in or Create an account to join the conversation.
Time to create page: 0.116 seconds