1 ADC to 2 B2SX''s
Archiver
Posts: 46,084
I have a board that senses multiple inputs, and does calculations
using the different inputs. the only way to get it to operate is to
have everything connected.... and working.
with 3 inputs it is hard to tell what is causing the error, so with a
simple 2 pin header there are 4 states. by jumpering the pins, I can
ignore an input and use a fixed (pre-set) value for the calculation.
I can isolate and test each part separately.
With a similar jumper, your lead controller could output a control or
pause
your test BS2 could have a jumper and in 0 it looks to the lead BS2
for data, and in 1, looks to the TLC for data.
If you have outputs, you could also let each micro if it should be
controlling or in standby.
One note here is that in process control, I have to maintain the
current state (output value) so that a change of control does not
cause a system upset. Nothing like having a motor at 3/4 speed and
changing controllers and seeing the motor STOP, then ramp up,
overshoot, undershoot, and all the process changes that go with it.
Dave
--- In basicstamps@y..., "Jonathan Peakall" <jpeakall@m...> wrote:
> Dave,
>
>
> >
> > what about sending serial out from your 1st unit to the second
unit.
> > it would be able to see the current value all the time and if you
> > chose to take your second unit off line, it would not interupt
your
> > lead unit.
>
> That sounds like a good idea. I have the pins to spare, so that is
no
> problem. I had hoped to have them run independently, but this idea
should
> work.
>
>
> >
> > you could use a jumper to tell the program to look to the TLC or
to
> > look to the BS2. change the jumper and presto ! second unit would
> > take control.
>
> Not exactly sure what you mean here. Can you explain in detail?
>
> Thanks for the reply!
>
> Jonathan Peakall
using the different inputs. the only way to get it to operate is to
have everything connected.... and working.
with 3 inputs it is hard to tell what is causing the error, so with a
simple 2 pin header there are 4 states. by jumpering the pins, I can
ignore an input and use a fixed (pre-set) value for the calculation.
I can isolate and test each part separately.
With a similar jumper, your lead controller could output a control or
pause
your test BS2 could have a jumper and in 0 it looks to the lead BS2
for data, and in 1, looks to the TLC for data.
If you have outputs, you could also let each micro if it should be
controlling or in standby.
One note here is that in process control, I have to maintain the
current state (output value) so that a change of control does not
cause a system upset. Nothing like having a motor at 3/4 speed and
changing controllers and seeing the motor STOP, then ramp up,
overshoot, undershoot, and all the process changes that go with it.
Dave
--- In basicstamps@y..., "Jonathan Peakall" <jpeakall@m...> wrote:
> Dave,
>
>
> >
> > what about sending serial out from your 1st unit to the second
unit.
> > it would be able to see the current value all the time and if you
> > chose to take your second unit off line, it would not interupt
your
> > lead unit.
>
> That sounds like a good idea. I have the pins to spare, so that is
no
> problem. I had hoped to have them run independently, but this idea
should
> work.
>
>
> >
> > you could use a jumper to tell the program to look to the TLC or
to
> > look to the BS2. change the jumper and presto ! second unit would
> > take control.
>
> Not exactly sure what you mean here. Can you explain in detail?
>
> Thanks for the reply!
>
> Jonathan Peakall