Gauges for Evoscan v0.97
Thread Starter
Account Disabled
iTrader: (465)
Joined: May 2005
Posts: 8,824
Likes: 2
From: Central FL
Gauges for Evoscan v0.97
Just thought I would put up a thread for anyone that has created custom gauges. If you are interested in sharing them with the forum, please feel free to post them up here.
I for one, have not even used GaugeView1.xml and I do not see it in my 0.97 update. Anyone have an idea where I can find this xml file?
I for one, have not even used GaugeView1.xml and I do not see it in my 0.97 update. Anyone have an idea where I can find this xml file?
I tried to mess around with some gauges the other night, got a few custom ones created but I coul dnever figure out how yo get the background (the square the surrounds the gauge) to take any color other than the nasty gray so I gave up.
I really want to set the background area to transparent or black to match my desktop background. I read through the dundas gauge info and it looks like it is a container property, but the way it is implemented in evoscan does not seem to allow you to modify the properties of the container....
I'll look and see if I can find the file you are looking for, you may just have to create it by creating a layout and saving it or something....
I really want to set the background area to transparent or black to match my desktop background. I read through the dundas gauge info and it looks like it is a container property, but the way it is implemented in evoscan does not seem to allow you to modify the properties of the container....
I'll look and see if I can find the file you are looking for, you may just have to create it by creating a layout and saving it or something....
Originally Posted by TTP Engineering
I for one, have not even used GaugeView1.xml and I do not see it in my 0.97 update.
Eric
here is a gauge template I created this A.M.
http://home.comcast.net/~lexx1313/Gr...peed-knock.xml
it has:
tach
knocklight with color based state
knock sum text with color based state
speed
tps text wtih color based state
Just save the xml file to your EvoScan v0.97\GaugeTemplates folder then go to gauges, add/edit, select "Graphite-tach-speed-knock", assign knock sum to both knocklight and knocksum, tps to tps, speed to speed, engine speed to default.
Not very pretty but it does show how to use states and create a simple combo gauge..
http://home.comcast.net/~lexx1313/Gr...peed-knock.xml
it has:
tach
knocklight with color based state
knock sum text with color based state
speed
tps text wtih color based state
Just save the xml file to your EvoScan v0.97\GaugeTemplates folder then go to gauges, add/edit, select "Graphite-tach-speed-knock", assign knock sum to both knocklight and knocksum, tps to tps, speed to speed, engine speed to default.
Not very pretty but it does show how to use states and create a simple combo gauge..
Last edited by Mad_SB; Oct 18, 2006 at 01:38 PM.
Thread Starter
Account Disabled
iTrader: (465)
Joined: May 2005
Posts: 8,824
Likes: 2
From: Central FL
This is what I was emailed for the knock gauge. It does not work like this for me.
<?xml version="1.0" standalone="yes"?>
<NewDataSet>
<Table1>
<Top>22</Top>
<Left>1370</Left>
<Width>467</Width>
<Height>332</Height>
<GaugeTemplateFileName>KnockIndicator</GaugeTemplateFileName>
<GaugeRefreshRate>0</GaugeRefreshRate>
<DataRequestItemsSerialized><SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:clr="http://schemas.microsoft.com/soap/encoding/clr/1.0" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<a1:ArrayList id="ref-1" xmlns:a1="http://schemas.microsoft.com/clr/ns/System.Collections">
<_items href="#ref-2"/>
<_size>1</_size>
<_version>1</_version>
</a1:ArrayList>
<SOAP-ENC:Array id="ref-2" SOAP-ENC:arrayType="xsd:anyType[16]">
<item xsi:type="a3:Globals+GaugeDataItem" xmlns:a3="http://schemas.microsoft.com/clr/nsassem/EvoScan/EvoScan%2C%20Version%3D1.24.0.0%2C%20Culture%3Dneu tral%2C%20PublicKeyToken%3Dnull">
<GaugeType>StateIndicator</GaugeType>
<TemplateName xsi:null="1"/>
<GaugeName id="ref-4">Color Indicator</GaugeName>
<GaugePointerName href="#ref-4"/>
<DataItem id="ref-5">Knock Sum</DataItem>
<DataKey id="ref-6">KnockSum</DataKey>
<Min>0</Min>
<Max>50</Max>
</item>
</SOAP-ENC:Array>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
</DataRequestItemsSerialized>
<Reserved1 />
<Reserved2 />
<Reserved3 />
<Reserved4 />
<Reserved5 />
</Table1>
</NewDataSet>
<?xml version="1.0" standalone="yes"?>
<NewDataSet>
<Table1>
<Top>22</Top>
<Left>1370</Left>
<Width>467</Width>
<Height>332</Height>
<GaugeTemplateFileName>KnockIndicator</GaugeTemplateFileName>
<GaugeRefreshRate>0</GaugeRefreshRate>
<DataRequestItemsSerialized><SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:clr="http://schemas.microsoft.com/soap/encoding/clr/1.0" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<a1:ArrayList id="ref-1" xmlns:a1="http://schemas.microsoft.com/clr/ns/System.Collections">
<_items href="#ref-2"/>
<_size>1</_size>
<_version>1</_version>
</a1:ArrayList>
<SOAP-ENC:Array id="ref-2" SOAP-ENC:arrayType="xsd:anyType[16]">
<item xsi:type="a3:Globals+GaugeDataItem" xmlns:a3="http://schemas.microsoft.com/clr/nsassem/EvoScan/EvoScan%2C%20Version%3D1.24.0.0%2C%20Culture%3Dneu tral%2C%20PublicKeyToken%3Dnull">
<GaugeType>StateIndicator</GaugeType>
<TemplateName xsi:null="1"/>
<GaugeName id="ref-4">Color Indicator</GaugeName>
<GaugePointerName href="#ref-4"/>
<DataItem id="ref-5">Knock Sum</DataItem>
<DataKey id="ref-6">KnockSum</DataKey>
<Min>0</Min>
<Max>50</Max>
</item>
</SOAP-ENC:Array>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
</DataRequestItemsSerialized>
<Reserved1 />
<Reserved2 />
<Reserved3 />
<Reserved4 />
<Reserved5 />
</Table1>
</NewDataSet>
Originally Posted by TTP Engineering
This is what I was emailed for the knock gauge. It does not work like this for me.
Give the one I posted a link to a shot and see if you have better luck with it.
Trending Topics
Thread Starter
Account Disabled
iTrader: (465)
Joined: May 2005
Posts: 8,824
Likes: 2
From: Central FL
Originally Posted by mad_VIII
I pasted that into a new xml in the gaugetemplate folder and got an exception when I tried to add that gauge.
Give the one I posted a link to a shot and see if you have better luck with it.
Give the one I posted a link to a shot and see if you have better luck with it.
The crappy part appears to be that you have to manually select what does what in the gauge each time you open it.
TTP: can you post the actual file, now that you've fixed it.
Also, if you save the gauge as a Gauge Layout, it will remember all the channel assignments. (I just tried it)
Even though it's mostly eye candy, I love playing with this stuff... I just haven't had time lately. I spent a lot of time trying to make the ones in 0.9 work, before finally realizing the states and numeric stuff wasn't enabled yet.
Also, if you save the gauge as a Gauge Layout, it will remember all the channel assignments. (I just tried it)
Even though it's mostly eye candy, I love playing with this stuff... I just haven't had time lately. I spent a lot of time trying to make the ones in 0.9 work, before finally realizing the states and numeric stuff wasn't enabled yet.
States are working now, I would like to figure out how to do a peak hold function. The biggest gripe i have is not being able to set the gauge container color....... Hope that gets fixed.
I spent a lot of time messing around with the various signal filters and conditioners trying to simulate a peak hold, but they didn't really seem to have any effect at all (this was with v.9). Peak hold is critical for knock counts.
Ok I will add a peak hold feature.. that will be awesome! which means you will be able to have two pointers on the gauge... one for actual and one for peak hold!
I will do some extreme testing on the next version to make sure all my default gauge containers get included in the installer.
TTP: The gauge dataitems are remembered in the GaugeLayout.. make sure you press save.. you can even see them in the file you posted... "DataItem id"
also attach it as a file.. this forum messes with the xml special characters. Or using the forum "code" block feature will help.
Also if your settings aren't saving make sure this blank file exists:
c:\program files\evoscan\evoscan v0.97\SavedSettings\EvoScan.xml
Edit: turns out the "savedsettings" dir/ was not created during install
Also the background container thing I'll check this out..
I will do some extreme testing on the next version to make sure all my default gauge containers get included in the installer.
TTP: The gauge dataitems are remembered in the GaugeLayout.. make sure you press save.. you can even see them in the file you posted... "DataItem id"
also attach it as a file.. this forum messes with the xml special characters. Or using the forum "code" block feature will help.
Also if your settings aren't saving make sure this blank file exists:
c:\program files\evoscan\evoscan v0.97\SavedSettings\EvoScan.xml
Edit: turns out the "savedsettings" dir/ was not created during install
Also the background container thing I'll check this out..
Last edited by evo4mad; Oct 19, 2006 at 04:09 PM.
Originally Posted by evo4mad
Ok I will add a peak hold feature.. that will be awesome! which means you will be able to have two pointers on the gauge... one for actual and one for peak hold!
I will do some extreme testing on the next version to make sure all my default gauge containers get included in the installer.
TTP: The gauge dataitems are remembered in the GaugeLayout.. make sure you press save.. you can even see them in the file you posted... "DataItem id"
also attach it as a file.. this forum messes with the xml special characters. Or using the forum "code" block feature will help.
Also if your settings aren't saving make sure this blank file exists:
c:\program files\evoscan\evoscan v0.97\SavedSettings\EvoScan.xml
Edit: turns out the "savedsettings" dir/ was not created during install
Also the background container thing I'll check this out..
I will do some extreme testing on the next version to make sure all my default gauge containers get included in the installer.
TTP: The gauge dataitems are remembered in the GaugeLayout.. make sure you press save.. you can even see them in the file you posted... "DataItem id"
also attach it as a file.. this forum messes with the xml special characters. Or using the forum "code" block feature will help.
Also if your settings aren't saving make sure this blank file exists:
c:\program files\evoscan\evoscan v0.97\SavedSettings\EvoScan.xml
Edit: turns out the "savedsettings" dir/ was not created during install
Also the background container thing I'll check this out..
How are you checking for bug regressions between versions Evo4Mad? That's going to be a full time job going forward and you probably will need to get a full time tester to look at that stuff.
Originally Posted by TTP Engineering
This is what I was emailed for the knock gauge. It does not work like this for me.
Shouldn't those > and < be < and > respectively? if so it would look like this
<?xml version="1.0" standalone="yes"?>
<NewDataSet>
<Table1>
<Top>22</Top>
<Left>1370</Left>
<Width>467</Width>
<Height>332</Height>
<GaugeTemplateFileName>KnockIndicator</GaugeTemplateFileName>
<GaugeRefreshRate>0</GaugeRefreshRate>
<DataRequestItemsSerialized>
<SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:clr="http://schemas.microsoft.com/soap/encoding/clr/1.0" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<a1:ArrayList id="ref-1" xmlns:a1="http://schemas.microsoft.com/clr/ns/System.Collections">
<_items href="#ref-2"/>
<_size>1</_size>
<_version>1</_version>
</a1:ArrayList>
<SOAP-ENC:Array id="ref-2" SOAP-ENC:arrayType="xsd:anyType[16]">
<item xsi:type="a3:Globals+GaugeDataItem" xmlns:a3="http://schemas.microsoft.com/clr/nsassem/EvoScan/EvoScan%2C%20Version%3D1.24.0.0%2C%20Culture%3Dneu tral%2C%20PublicKeyToken%3Dnull">
<GaugeType>StateIndicator</GaugeType>
<TemplateName xsi:null="1"/>
<GaugeName id="ref-4">Color Indicator</GaugeName>
<GaugePointerName href="#ref-4"/>
<DataItem id="ref-5">Knock Sum</DataItem>
<DataKey id="ref-6">KnockSum</DataKey>
<Min>0</Min>
<Max>50</Max>
</item>
</SOAP-ENC:Array>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
</DataRequestItemsSerialized>
<Reserved1 />
<Reserved2 />
<Reserved3 />
<Reserved4 />
<Reserved5 />
</Table1>
</NewDataSet>
As Evo4Mad said, I manually added a SavedSettings directory, then copied an XML file into there, renamed it "EvoScan.xml", and deleted it's entire contents. The first time you rerun the program, you'll get an error message and the channel list will be blank. Just close and rerun it. Now, it's back to normal operation, except all the settings save perfectly!
THANKS!
THANKS!






