Please note that the following Software and Hardware is of the Version 1 board (beta) and is no longer in use. The software has been updated and is talked about near the very end of this thread
Hardware:
Software:
These are pictures of the unskinned version. When you first open the program without any skin file present, this is what you will see.
The main page for the Digital Outputs. You can turn each one on or off by clicking the corresponding button. Alternatively you can turn them all on or off with 1 push. The defaut on or off values can be set through the configuration window:
The main page for the Analogue Inputs:
The configuration page that will only be needed when setting things up. Settings are stored in a file and read in on load so this screen will not really be needed while in use:
The digital outputs can have animations assigned to them. Up to 30 frames can be set. The animation as a whole can be set to repeat either forever or a specified number of times up to 2,147,483,648 iterations. So you can either have over 2 billion runs through or run it forever, to only once. This is the setup screen for that:
The digital outputs and analogue inputs are given names that you can easily tell which is which. To do that easily on a touchscreen, there is an OSK:
This is the analogue input type selection area. You can choose what type of sensor is connected, as well as adjust each little variable. For instance, the temperature can be displayed in either Farenheit or Celcius. Also you can change the core voltage of the sensor to make small adjustments. If you place the outisde temperature sensor in your engine bay, you may want to increase the voltage so that it shows colder than it reads so that it is accurate compensating for the engine bay heat. In the picture you see the accelerometer options, where you can adjust the core voltage, as well as the voltage per g-force input to get maximum sensitivity and accuracy. Please note that the default settings are ideal for most if not all situations, but the flexibility is there for the future.
Here are the same images but skinned:
The software is designed to be as easy as possible to skin. To give you an idea of how easy, this is an example of how the unskinned images got to skinned images:
Code:
**BRUSHED METAL SKIN FILE**
**Global FusionForm Settings
>>MAIN
#BACKIMAGE#\Images\BMV2_Background.jpg
#TILESTRETCHBACKIMAGE#TILE
#SIZE#640;480
#TRANSPARENT#000255255
#COLOURDOWN#Transparent
#COLOURUP#Transparent
#LBLDOCOLOUR#FALSE
#LBLDOFONT#Arial Narrow;30;BOLD
** --> Show label remove comment: #LBLAICOLOUR#LightGray
#LBLAICOLOUR#FALSE
#LBLAIFONT#Arial Narrow;30;BOLD
#GBOXBORDER#FALSE
#GBOXDOLOCATION#12;54
** --> To show label remove comment: #GBOXAILOCATION#12;88
#GBOXAILOCATION#12;54
<<END
**Buttons
>>BTN_DEFAULT
#OFF#\Images\BMV2_Button.gif
#ON#\Images\BMV2_Button_Down.gif
#TXTCOLOURON#LightGray
#TXTCOLOUROFF#LightGray
#BORDERSIZE#0
#FONT#Arial Narrow;18;BOLD
<<END
Each button is seperate. You can skin none, all, or number of buttons inbetween with no problems. All the fonts are independant, as well as all the images. No more making 1 image and aligning button arrangements. Just tell it what image you want to use and it sticks it in there. All of the above skinned images, were created by using 9 small images totally under 80Kb in size TOTAL, not each. So you can imagine how efficient this is. Transparency is fully supported through *.gifs.
Just begin the button's name with a ">>" and end it with "<<END" and that is it. In the above example, "BTN_DEFAULT" is the button on the main page that sets all the digital outputs to their default values. The image for the off value is stored in the directory "Images" with the name of "BMV2_Button.gif". Pretty self explanitory.