I have been working on a new version of hal_pi_gpio.
It uses an array of structures to hold the features for each pin.
struct pinfo
{
hal_bit_t pval; // the last read value for inputs, the
desired output value for outputs
char pnum; // the rpi header pin number
char
On Tue, 9 Feb 2021 at 13:28, Thomas J Powderly wrote:
> loadrt hal_pi_gpio pi_pins={,,,}{,,,}{,,,}
> each 'quad' consists of braces enclosed data
I think that the modparam handling struggles with embedded commas
inside a single element.
I would suggest:
loadrt hal_gpio config=12or0,1i,23i,...
On 2/7/2021 6:59 PM, Chris Albertson wrote:
On Sun, Feb 7, 2021 at 9:41 AM Gene Heskett wrote:
Space for
it means pulling the crooked g0704 out before bringing it in. And more
than likely hurting myself getting it backed into the space. But I think
I'm a little smarter about such than I was
Point was to not let the current arrangement of equipment drive the
selection of what new mill you can buy because for not a lot of money you
can have the current arrangement of equipment changed. I'd guess the
labor cost in rural Indiana is less than here in So Cal.
If you are looking to get
Quick question.
There's a multi-axis operation in progress. For whatever reason one of the
servos throws out a fault and of course stops.
Should just the enables to the other servo drives be removed or should power be
cut to all drives.
I'm not really in favour of dropping out power because t
No experience on commercial systems. But I agree, a servo fault throwing
e-stop wouldn't be the best. The behaviour that seems standard on fault is
that the machine goes to power off which removes enable from all the other
axis and spindle is effective and limits the chaos to a reasonable lev
On Wednesday 10 February 2021 00:08:41 John Dammeyer wrote:
> Quick question.
>
> There's a multi-axis operation in progress. For whatever reason one
> of the servos throws out a fault and of course stops.
>
> Should just the enables to the other servo drives be removed or should
> power be cut t
