Quote: Originally Posted by
durwood 
Well I couldn't do that because one button might feedback into another, but I think I could make do with 10 button control. SO basically, I could tell your software once the analog level falls below level "X" perform this keystroke?
They shouldnt feed into eachother. Just build a simple resistor DAC around them and voila!
Like this:
Quote: Originally Posted by
durwood Ok that is probably the problem I have with my current setup. I don't know what the clock rate is for a mouse, but between the rotary encoder, autohotkey and RR, the delay is quite large, at least larger than is desired.
By delay do you mean how fast from spinning the wheel to doing something? If you spin slower, does it work faster?
From the time the brain reads the value, to when the software spits out the command is usually under 3mS. The reading though is only done every 30mS on average. It can be sped up, but CPU cycles suffer.
The problem comes from the value. The encoder sends out short pulses usually, and then it must count those. Well if the brain doesnt count when that pulse is high, it will miss it, so it is sort of like a lucky guess situation for something like that. That is why what we will have will be an encoder to a analogue output based on absolute position. As long as the brain samples 2 times for every time it spins all the way around it knows what direction you are going.
Quote: Originally Posted by
durwood That's prefect then. As long as it shuts down before the soundcard powers off, then it should serve it's purpose. I assume turn on delay would happen after it is already booted into windows-correct?
Yes the outputs are all off until the brain communicates with the PC and then if the initial state is set to on, it will power on the output (amp). Then if the brain loses communication with the program, the outputs start their individual timers. When their timers are up, the respective output shuts off. The timer can be from 0 seconds (instant) to 30hours. This has a delay of about 1-2 seconds though initially to make sure it really has lost communication and your outputs dont just flicker each time it gets a hiccup! I will have the program sense shutdown calls through software and send out a call right before it goes into a suspend/shutdown mode instead of relying all on the hardware to figure out it has gone blind.
I will have the program watching for shutdown calls, and start the timer then instead of