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

[speedy_parker]

from h3rk:
Oh and by the way I'd like to reserve a place in line for when they become available to the rest of us, if I may.




This is looking great! Thanks for all the work guys.

[greenman100]

I like that idea. The each output could have two attributes like:
.state.default=1
.state.last=0

Already implemented.

[h3rk]

from h3rk:
Oh and by the way I'd like to reserve a place in line for when they become available to the rest of us, if I may.




This is looking great! Thanks for all the work guys.

Oh great, someone must have caught me out on the town, in drag, and now thinks I'm a she.

Dammit, it was just one night

[greenman100]

from h3rk:
Oh and by the way I'd like to reserve a place in line for when they become available to the rest of us, if I may.

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

[2k1Toaster]

Right on!

If the 'tied' output turns on with one press. The timer would cause it to turn off after set time. Possible use would be an actuator. It would prevent someone from having to use limit switches on their rocker-panel rocket launchers.

Already done!

All of my ideas can't be top-notch, but I have my moments. But I think you may know I'm not advertising all of them...yet. But you get to the good ones by blurting out all of the bad ones and getting them outta the way.

Keep them coming!

Sweet... Thank you.

I was wondering for the outputs if there could be a "save state" and/or "default state" option. What I mean is when the computer is powered off the board will keep whatever state it was in but also be able to return to its default state if wanted. I dont know if that made sense, if it didn't ill fix it later.

I like that idea. The each output could have two attributes like:
.state.default=1
.state.last=0

done.

Not the last state, but default state is saved as can be referred to by pushing the big 'ol default button on the screen. It is also the state that is loaded when the app starts. So if you want your lights on when the board comes on, but not your 3gillion dB bullhorn, you can set that.

Already implemented.

You beat me to it!

[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]

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

a ruffy shall ALWAYS worry about stock

[2k1Toaster]

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]

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.