Discussion:
LED colours in Halshow,
(too old to reply)
andy pugh
2017-01-28 02:52:51 UTC
Permalink
Raw Message
Maybe everyone has been assuming "it must be only me" for the last
several years.
iI took a recent forum post[1] for me to realise that, actually, Red
for False and Yellow for True is _not_ obvious.

On IRC PCW suggested that Black for false and Bright Green for true
would be unambiguous and not be confused with the current scheme.

[1] https://forum.linuxcnc.org/24-hal-components/32241-mpeg-pendant-6-axis-axis-a-b-c-no-move-please-help-cnc-ver-2-3-0
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916
EBo
2017-01-28 03:10:18 UTC
Permalink
Raw Message
I would have to dig around, but I remember that there are standardized
color schemes for such things. It is also important in that there are
people with something called "color blindness",,,
Post by andy pugh
Maybe everyone has been assuming "it must be only me" for the last
several years.
iI took a recent forum post[1] for me to realise that, actually, Red
for False and Yellow for True is _not_ obvious.
On IRC PCW suggested that Black for false and Bright Green for true
would be unambiguous and not be confused with the current scheme.
[1]
https://forum.linuxcnc.org/24-hal-components/32241-mpeg-pendant-6-axis-axis-a-b-c-no-move-please-help-cnc-ver-2-3-0
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Emc-developers mailing list
https://lists.sourceforge.net/lists/listinfo/emc-developers
andy pugh
2017-01-28 03:46:44 UTC
Permalink
Raw Message
Post by EBo
I would have to dig around, but I remember that there are standardized
color schemes for such things. It is also important in that there are
people with something called "color blindness",,,
There is an ISO standard, but that assumes context. Red = bad green =
good, yellow = information

There is no way to know the subjective value of a HAL pin, it could be
"True, the machine is definitely on fire" or "true, all parts made
today passed inspection"
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916
EBo
2017-01-28 03:58:24 UTC
Permalink
Raw Message
Post by andy pugh
Post by EBo
I would have to dig around, but I remember that there are
standardized
color schemes for such things. It is also important in that there are
people with something called "color blindness",,,
There is an ISO standard, but that assumes context. Red = bad green =
good, yellow = information
There is no way to know the subjective value of a HAL pin, it could be
"True, the machine is definitely on fire" or "true, all parts made
today passed inspection"
Fair enough. Would that mean that the hal pins need another attribute
"color for value"?
andy pugh
2017-01-28 18:06:50 UTC
Permalink
Raw Message
Post by EBo
Fair enough. Would that mean that the hal pins need another attribute
"color for value"?
No. This is only one small part of a rarely-used debugging tool.

This actually turns out to be a rather simple change.
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916
Gene Heskett
2017-01-28 20:25:02 UTC
Permalink
Raw Message
Post by andy pugh
Post by EBo
Fair enough. Would that mean that the hal pins need another
attribute "color for value"?
No. This is only one small part of a rarely-used debugging tool.
I can't qualify it as "rarely-used" here, Andy. I don't have a hal file
that doesn't have some outputs that are there just to watch something.
Most often would be the output of several modules, that if I put a
halmeter on that point will tell me how far it overshoots in encoder
counts, while doing a g33.1's reversal at maximum penetration. On TLM,
with its on purpose slow reversal (so I don't break drive parts, that
motor can if just reversed) I find that with that fairly heavy 5" chuck,
the turn-around overshoot is so large that doing rigid tapping at more
than 200 rpm isn't worth the effort because it will coast on, running
the tap to the bottom of the hole and pull back a broken tap. Not
exactly economical. 250 rpm=3.4 turns of the chuck.
Post by andy pugh
This actually turns out to be a rather simple change.
Good. I'd assume it only applies to bit states?

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)
Genes Web page <http://geneslinuxbox.net:6309/gene>
andy pugh
2017-01-28 22:03:35 UTC
Permalink
Raw Message
Post by Gene Heskett
I can't qualify it as "rarely-used" here, Andy. I don't have a hal file
that doesn't have some outputs that are there just to watch something.
You run "Halshow" all the time? Even when the machine is running normally?
--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1916
Gene Heskett
2017-01-29 04:38:20 UTC
Permalink
Raw Message
Post by andy pugh
Post by Gene Heskett
I can't qualify it as "rarely-used" here, Andy. I don't have a hal
file that doesn't have some outputs that are there just to watch
something.
You run "Halshow" all the time? Even when the machine is running normally?
Not halshow, but halmeter's. Sometimes as many as 8 when I am tracing my
often broken logic. But when its working, the stub stuff rarely gets
excised from the hal file when its working, but the halmeters don't get
started when I no longer need them.

In working on those chuck locking collar's I had 2 problems today.

Running the G0704 to drill the stuff in the rim preparatory to fitting a
5mmx.8 draw screw to tighten it on the edge og the spindle flange, I had
it positioned and touched off at the centerline of the screws, bore, so
I took a wild guess at how deep the screw hole should be, guessed 1.5"
because I had not found when the er-32 nut holding the drill, was going
to hit the rim and chew it up. g1 f2 z-1.5". And when I hit the return
key it drove z down to -1.5, but it drove it at about 50 ipm, moving the
work piece in the vice, so I had to start over, locating it in the vice
& making sure it couldn't move again. When I had restored its position
in the vice, and touched off a new x0y0z0 position, I uparrowed in the
MDI history and reran it. Worked perfectly. Murphy? DamnedifIknow.

Then I took the ring, whose gap I had not sawn yet, off the mill and
chucked it on the lathe from the inside, and proceeded to make first
swarf. I had not reduced the error and ferror settings below 10.xxx if
the .ini file yet. But I fooled around, driving it by hand for close to
2 hours spindle run time, without a single joint error.

But one thing's bugging me, this damned pi doesn't always ack the key up,
so the axis I needed to bump a thou, keeps on moving at creep speeds
until I hit and release a key. Any key. It like the keyboard has its
name in the priority list at a very low priority position. Looking at
the usb stuff when it has nothing else to do.

Anybody know anything about that? It's been an intermittent since day
one. I have several keyboards, and when its of a mind to make a problem,
changing keyboards has never helped, as is a reboot will often clear it
up All are usb, and if it being a problem, switching from wired to
wireless doesn't effect the error rate.

Clues? I've tickled it extensively without a finger to put on it.

Thanks everybody.

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)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Gene Heskett
2017-01-28 05:33:17 UTC
Permalink
Raw Message
Post by andy pugh
Maybe everyone has been assuming "it must be only me" for the last
several years.
iI took a recent forum post[1] for me to realise that, actually, Red
for False and Yellow for True is _not_ obvious.
On IRC PCW suggested that Black for false and Bright Green for true
would be unambiguous and not be confused with the current scheme.
[1]
https://forum.linuxcnc.org/24-hal-components/32241-mpeg-pendant-6-axis
-axis-a-b-c-no-move-please-help-cnc-ver-2-3-0
Thats a jolly good idea Andy, particularly if the halmeter code could be
updated to match. I can read red/green/blue/black from 15+ feet away,
but I can only read the black text for perhaps 7 or 8 feet at best. And
when I am standing in front of the G0704, I am all of 6 feet away from a
322" monitor at an acute angle of about 60 degrees.

The old mans $0.02.

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)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Loading...