Connecting resistive "steering wheel media buttons"

there is the winamp control part of the default skin for version 2 Replace winamp with the title, and the Keys with your Keys.

>>DI_INPUTS
#STARTNEW#
#NAME#Winamp - Play/Pause
#KEYSEQUENCE#c
#MAINWINDOWTITLE#winamp
#PORT#3
#MINTIMEBETWEEN#500
#VIDPID#vid_04d8&pid_000c
#ENDNEW#
#STARTNEW#
#NAME#Winamp - Next Song
#KEYSEQUENCE#b
#MAINWINDOWTITLE#winamp
#PORT#3
#MINTIMEBETWEEN#500
#VIDPID#vid_04d8&pid_000c
#ENDNEW#
#STARTNEW#
#NAME#Winamp - Previous Song
#KEYSEQUENCE#z
#MAINWINDOWTITLE#winamp
#PORT#3
#MINTIMEBETWEEN#500
#VIDPID#vid_04d8&pid_000c
#ENDNEW#
#STARTNEW#
#NAME#Winamp - Stop
#KEYSEQUENCE#v
#MAINWINDOWTITLE#winamp
#PORT#3
#MINTIMEBETWEEN#500
#VIDPID#vid_04d8&pid_000c
#ENDNEW#
<<END

Quote:

---

Originally Posted by 2k1Toaster

there is the winamp control part of the default skin for version 2 Replace winamp with the title, and the Keys with your Keys.

>>DI_INPUTS
#STARTNEW#
#NAME#Winamp - Play/Pause
#KEYSEQUENCE#c
#MAINWINDOWTITLE#winamp
#PORT#3
#MINTIMEBETWEEN#500
#VIDPID#vid_04d8&pid_000c
#ENDNEW#
#STARTNEW#
#NAME#Winamp - Next Song
#KEYSEQUENCE#b
#MAINWINDOWTITLE#winamp
#PORT#3
#MINTIMEBETWEEN#500
#VIDPID#vid_04d8&pid_000c
#ENDNEW#
#STARTNEW#
#NAME#Winamp - Previous Song
#KEYSEQUENCE#z
#MAINWINDOWTITLE#winamp
#PORT#3
#MINTIMEBETWEEN#500
#VIDPID#vid_04d8&pid_000c
#ENDNEW#
#STARTNEW#
#NAME#Winamp - Stop
#KEYSEQUENCE#v
#MAINWINDOWTITLE#winamp
#PORT#3
#MINTIMEBETWEEN#500
#VIDPID#vid_04d8&pid_000c
#ENDNEW#
<<END

---

Doesnt this refer to digital Input?

Shouldnt it start:
>>AI_INPUTS
There are no references to voltages, how does the brain know which keysequence to send?
IE:
X = Output Voltage
Button UP / X = 3.7mV / Send hotkey a
Button DOWN / X = 0.74V / Send hotkey b
Button MODE / X = 3.38V / Send hotkey c
Button VOLUME UP / X = 3.96V / Send hotkey d
Button VOLUME DOWN / X = 4.45V / Send hotkey e
NO Button pressed / X= 4.84V / (Do nothing, Dont send hotkey)

thanks
:confused:

Oh sorry. Forgot about the analogue input thing. Those are for digital inputs. Let me get you an example for the analogue input

Sorry for the holdup.

I am looking at the version 2 code, and when I try it out, it doesnt always work as expected which could be pretty annoying when pressing buttons.

The good news is that the Uber Edition XNA and soon MDX (Just have 1 thing holding up a release) both will work perfectly and very easily.

The catch is that XNA requires a lot of other components to be installed to run correctly.Once it is running it is just fine, and the most powerful application for download now.

MDX is working 99%, but not releasable right now. As of now, it starts loads, runs, communicates with the brain and displays just fine. However, when you close the program there is an error with a "Program has crashed, click here to close it and send a report to M$" type error that is not catchable right now. I am working as hard as I can to get that sorted and I hope to have a download for Uber MDX within the week.

As for now, Uber XNA is the best. If you still want version #2, what you do is you set the "#HIGHTHRESHOLD#" and "#LOWTHRESHOLD#" values to the upper and lower voltage limits. Set the "HIGHKEYSEQUENCE" to the key value and the "LOWKEYSEQUENCE" to the value.

That should work. I have been programming Uber for over 3 months now and my mind is battling between syntax! :lol:

I suggest you use the XNA version though, and if you can wait a week, I highly reccommend using the MDX version because it will be 100%.

Again, sorry for the delay.

Best to wait for MDX then
thanks for prompt reply (its hard to do 100 things at once)

Uber MDX is 100% now. :)

Here is a link for it: http://www.fusioncontrolcentre.com/T...18-02-2008.rar

I am not making a thread for it until the configurator is up and running, but you are welcome to use it.

Is Uber MDX easier on the CPU? Version 2 spikes the CPU to 80% too much. All I'm doing is monitoring inputs on a 3000 ms interval and logging them.

From what I have tested, it is much better on the CPU.

You can try with the default skin just to see. And you can now tweak the 4 timers in the program. So you can record an analogue input to memory on the analogue input timer, and then log them with the logic timer which can be run at a seperate time.

Quote:

---

Originally Posted by 2k1Toaster

Uber MDX is 100% now. :)

Here is a link for it: http://www.fusioncontrolcentre.com/T...18-02-2008.rar

I am not making a thread for it until the configurator is up and running, but you are welcome to use it.

---

ETA on configurator ?

Quote:

---

Originally Posted by vultan

ETA on configurator ?

---

Programming away right now...

I have many other projects going on right now as well. So it is taking much longer.

Currently, I pretty much have the logic layout area complete with saving and opening.

So only things that dont currently work in the configurator: opening, graphics

The rest works. So if you can do it all in one go, and dont need graphics, it works! But if you want to save and start back later, that is going to take a longer time...

Until then, you can still configure it in NotePad, or Word, or WordPad, or DreamWeaver, or any XML editor, or any plain text editor just fine.