Yes you had previously mentioned the need to use the first board E Stop input
and not use the second board’s E Stop input. That was already correctly wired.
Matthew Herd
herd.m...@gmail.com
610-608-8930
> On Feb 16, 2021, at 7:14 PM, Jon Elson wrote:
>
> On 02/16/2021 03:58 PM, Matthew Herd
On 02/16/2021 03:58 PM, Matthew Herd wrote:
So I've got egg on my face on this one. It seems that changing to dout.07
in my config solved the issue. No idea why it didn't work for me before.
I'm certain I tried that in my config, but I can't say. Also, I tried the
sim config again and it
So I've got egg on my face on this one. It seems that changing to dout.07
in my config solved the issue. No idea why it didn't work for me before.
I'm certain I tried that in my config, but I can't say. Also, I tried the
sim config again and it worked this time. No idea why, but I'll take it!
I like your comments throughout. Gives me a feel of the why or what you were
trying to accomplish rather than something like
a = 5; // assign 5 into variable a.
Being nit picky I'd have done the following with the opposite logic.
// --- beg --- create & export hal_pins
for (n = 0; n
The hal_pi_gpio component seems to be beta stage
meaning I don't see anything wrong.
When I programmed full-time this was when I had to hand it over to
others to peer.
Where do I look for howto write a man page?
About the comp -
Written in old-school c
> On 15 Feb 2021, at 23:12, Ralph Stirling
> wrote:
>
>
> Is this possible? Any suggestions or examples to help?
I think that you can do anything you want to the widgets via the usual Gtk(?)
interface.
I have certainly moved widgets around inside a Glade tab using the python
handler
