"READOUTPUTS" command?

[Artie2]

I'm probably overlooking something simple here, but as the person who's writing the program, how can I NOT know what state my outputs are in? Not sure I understand the purpose of this command.

However, I'm sure I'll have a "Doh!" moment shortly.

 

[Andrew Cowan]

Something like 'pulsout' or 'toggle' changes the state of the pin.

Could confuse things, I guess.

 

[sghioto]

Artie2,

Seems fairly self explanatory. Allows you store the current state of the output pins into a single variable. Useful if you need the program to run subroutines depending on the output pins state.

Steve G.

 

[Artie2]

Hey Steve; I guess I'm still not following the logic. If I'm writing the program, when it gets to that point where I decide which branch to take, won't I know the status of my output pins?

 

[lbenson]

Your program could be setting an output based upon an input, for instance based upon whether an ADC input is above or below a particular value. At any given point in the program, you might not know what had been set unless you had saved the setting somewhere. READOUTPUTS give you the ability to determine that setting without your having to explicitly save it.

 

[Artie2]

READOUTPUTS give you the ability to determine that setting without your having to explicitly save it.

Ah, now that makes sense. Thanks.