On Tuesday 15 September 2020 07:16:05 andy pugh wrote:

> On Tue, 15 Sep 2020 at 11:13, Gene Heskett <ghesk...@shentel.net> wrote:
> > So getting that pair of messages twice each in the terminal, and
> > again in the axis gui when its activated doesn't seem warranted.
>
> Is the message addf before or after the functions that create the
> inputs?

What you snipped was in in order it appears in the .hal 
file. Here it is again, with geany's line numbers:

73 loadrt  message  names="XFault","ZFault" messages="Axis Z Fault","Axis X 
Fault"
[...]
116 addf        ZFault                                  jog-thread
117 addf        XFault                                  jog-thread
[...]
274 setp ZFault.edge false
275 setp XFault.edge false

on the terminal screen I am seeing:

hm2/hm2_7i90.0: registered
MOTION: setting Traj cycle time to 1000000 nsecs
MOTION: setting Servo cycle time to 1000000 nsecs
Axis X Fault
Axis Z Fault
Axis X Fault
Axis Z Fault
note: MAXV     max: 2.000 units/sec 120.000 units/min
note: LJOG     max: 2.000 units/sec 120.000 units/min
note: LJOG default: 1.350 units/sec 81.000 units/min
note: jog_order='ZX'
note: jog_invert=set(['X'])

This is long before axis has fully drawn its screen, and its repeated
on the lower right corner of the axis right hand panel for 
pyvcp stuffs when that screen is fully drawn when e-stop is released
by the F1 key.  Not before.

There is no machine motor power at this point, not until the F2 key
has been pressed.

I have added a oneshot, whose output is currently not "wired up" in hal,
to cover any power up glitches for .75 seconds after F2 is enabled, 
but this occurrence is well before it gets triggered by motion being enabled.

The man page for "message" leaves much to be desired, it took me at least
an hour to cobble up that loadrt line to make 2 separate, independent
messages. Triggered by the status of its name used as a signal. None of that
for more than 1 message is mentioned in the man page.  So its entirely 
possible I'm doing it wrong.

The target when the driver disables itself, is to unhome the machine since 
a driver has done a shut down destroying its homed reference. Doing that 
unhome with halui, is also very slow, seconds to kill the homed indicators 
in the axis dro/backplot window. I think when its all wired up in .hal, that
I'll unhome only the axis that faulted. Minor details,

Thank you Andy.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>


_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to