*NEW* USB Input/Output Board -- Fusion Brain

[mezz64]

Ok, I'm a little confused on the state saving part. If I were to say turn on output number 1, then shut down the computer, when I turn it back on will output 1 remain on? I'm pretty sure you've said yes to this but in your last post when you said "Not the last state", it threw me off a little.

[Ruffy]

Quote: Originally Posted by greenman100

There will be 100 available immediately. There is no need for worry as to stock.

a ruffy shall ALWAYS worry about stock

[2k1Toaster]

Quote: Originally Posted by mezz64

Ok, I'm a little confused on the state saving part. If I were to say turn on output number 1, then shut down the computer, when I turn it back on will output 1 remain on? I'm pretty sure you've said yes to this but in your last post when you said "Not the last state", it threw me off a little.

No it will not currently go to the last state it was in. It goes to the default state which you can set.

When you configure it all, you can choose which outputs you want high and which low as a default. Those are what are loaded when the program starts or when you click the default button.

Would it be better to make it the last state? All would be required is writing the current state to memory instead of just dumping it like it does now. That would require the program to be allowed read/write access after you push the close button.

What do you guys want?

[mezz64]

Could it be made an option to choose between using the last state or the default state for an output? My main reason for wanting the last state is I would hope to use this to control a circuit to switch between a front/rear speaker setup and a front active setup, I'd like it to resume which ever configuration I had chosen when I shutdown, since the dsp configuration will load what was used last. If it were to revert the wrong way, I could accidentally send some nasty low frequencies through my tweeters and that would most certainly be bad.

[2k1Toaster]

Quote: Originally Posted by mezz64

Could it be made an option to choose between using the last state or the default state for an output? My main reason for wanting the last state is I would hope to use this to control a circuit to switch between a front/rear speaker setup and a front active setup, I'd like it to resume which ever configuration I had chosen when I shutdown, since the dsp configuration will load what was used last. If it were to revert the wrong way, I could accidentally send some nasty low frequencies through my tweeters and that would most certainly be bad.

Hmmm. Sure. Would you want something on the fly, or set through a config option and not to be seen again without opening another menu. So easy to go default/last state, or not so easy. Because the more stuff I put on the main screen, the more cluttered it becomes, and therefore not as TS friendly.

I could get away with some more buttons I think to toggle that... Shouldn't be too hard to implement.

[h3rk]

My vote is to keep the display as clean as possible. maybe a config page setting.

[2k1Toaster]

Quote: Originally Posted by h3rk

My vote is to keep the display as clean as possible. maybe a config page setting.

Your wishes are my command.



That will be a feature now. Well not, now but soon. Before release.

[inFused]

2k1Toaster,

Do you think you could set the "last state" vs "default state" option per relay control? That'd please everyone, and also allow for some people to run some relays based on the default state and some on the last state.

I know that complicates things a bit :P

[2k1Toaster]

Quote: Originally Posted by inFused

2k1Toaster,

Do you think you could set the "last state" vs "default state" option per relay control? That'd please everyone, and also allow for some people to run some relays based on the default state and some on the last state.

I know that complicates things a bit :P

That's what the plan is.

And I like your user name.

[greenman100]

Yeah, to restate the above:

There will be two options for "saving state"

Default - this is the value that automatically loads when the computer finishes starting up.

Last known - this will maintain a value for as long as the PIC has power.

I recognize that it would be nice to save the last known state into non-volatile RAM, but I need to look into whether the PIC has the ability to do that. I'm not sure.

[mezz64]

So the board will retain power once the engine is off, any idea of the current draw?

[2k1Toaster]

Quote: Originally Posted by greenman100

Last known - this will maintain a value for as long as the PIC has power.

I recognize that it would be nice to save the last known state into non-volatile RAM, but I need to look into whether the PIC has the ability to do that. I'm not sure.

I can make it software based but that would mean it will go to the last known state, only when the computer is on. So if output 1 is set to last known state as a default setting, and is on right when the computer shuts down, the output will shut off while the computer is off. Then once the computer and program start up again, it will go back to on with no user touch.

We could set it through hardware, but like you said, that is constant power draw.

[greenman100]

Quote: Originally Posted by mezz64

So the board will retain power once the engine is off, any idea of the current draw?

Well it doesn't have to... it's up to you to maintain the last known state if you want. If you do, the drain of the board is about 20mA + whatever relays you use

Alternatively, you can just let the PC hold the last state, and wait until it boots up... if that makes sense.

We're still fleshing out the details... We'll do a full writeup once it's finalized.

On another note, we got the beta boards today.

[greenman100]

We need to get a feel for how many people want accelerometers.

The minimum order is 100, or pay a big setup fee for making the boards.

The accelerometers would sell for $20, and be capable of measuring +/- 6g in any direction (triple axis)

[2k1Toaster]

I want one! Do I count?