OK Im going to try and answer all the questions above in this post, but please keep bringing them.
I like this idea. How about an option for blinking or alternate/blinking lights?
I can write a WIN32 program that can apply timer and blinks to the LED's and even design it to execute with a screen saver. Unfortantly this will not work for the DOS users.
think going USB would be better than serial though. Im suprised that motherboards still have serial ports on them... and surely they will probably dissapear someday.
Serial may be the best method because it will allow the hardware to function for both DOS and Windows users. If your PC does not have a serial port you can purchase a USB to serial adapter fairly cheap these days. Windows will mimic this as a regual serial port so the program should still function.
I might have missed this while excitedly reading through, but can you test which LED is which? Like you click on the icons of each of the LEDs and the LED in the cabinet blinks or lights up?
Yes the program will actualy active a LED every time a check box is clicked. This way it makes it easy to create a batch file and perform diagnostics.
What about the pure DOS users ? Could the executable run in pure DOS?
Yes, the program I displayed will only function in Windows but the batch file and LED ON/OFF application will function at a DOS level.
When you exit a game will the lights go back off or would you have to run another game to reset them?
Currently this will be dependent on your front end. I beleive there again GLAUNCH allows an execution of a file before and after loading the rom. So you can execute another batch file after the game has exited. Somthing to consider to all the FE creators when desiging features.
So would you need to create a batch file for each individual game? Or, say, 6 different batch files by the number of buttons? (like, 1button.bat 2button.bat 3button.bat etc..) And so how would you go from a game that uses 3 buttons to a game that uses 6? Would that be a front-end implementation to figure out which batch file to call before launching the game?
There should be only so many combinations of button layouts. I was thinking about a dozen different layouts but the possibilites are endless. Just need to write as many batch files that will be needed. The front end will decide what batch file will get launched. If I have time I will try creating my own FE soon. I may ask the community to help later with batch file creations. I would like to embed a universal mame feature into the app where you specify your layout and the program spits all every batch file for every current mame game.
Oh yeah, will this only be in 'kit' form or will you release the software, as well?
Because of the compleity of the program/hardware allot of my creation will be propritairy. Meaning I would need to sell the hardware and software as a package. I'm not trying to do this to make money but you understand its not free. I will be lookign around after getting my proto type built for a sells partner. Maybe even include it in already built CP's. We will see!
How about us big 4 player control panel users which have 4 start, 4 credit, 26 player buttons . Will your program be able to handle all those? Will the hardware be able to support that many outputs?
The method I am using will allow the hardware to be daisy chained. Each piece of hardware will allow 14 LED's to be lit. 32 led boards can be plugged together to equal a possible combination of 448 led's. Wow light the entire house with that.
Not trying to put a damped on anything. Maybe someone knows how to get them little buggers to show some light better than I do.
I just started on this project today but believe I can find a good combination of power/led/brightness. Once I am finished I will have recomendations of different LED's and button color combinations. Worse case scenerio I cant get it to work you can use the leds to light up a drawing of your CP and mouse it somewhere on your bezel or CP to show what buttons are active. I am sure it wont come to this but its my plan B if the worst happens.
