Rev Burner problem

[Hampsta]

Hi guys, I'm new to this so hoping you can help.
I have just setup GI-Max, SPID, Pro Shift and Rev Burner (within the last hour) and all is good except I can't get my Rev Burner to read right.
I have a Tacho that has a max RPM of 11000 but I can't get it to go that high.
I have selected 4 Cylinder on the Tach and Sim dash but if I go higher then approx 31200 PPM the needle stops climbing and starts dropping. The highest I can get is about 9200RPM.
I have played around and tried 6 and 8 cylinder settings just for the sake of it but same problem.
Can anyone help?
Also I tried to do a firmware upgrade on the Rev Burner but there is no jumber on the board to change to get into the right mode. Is this a different version apart from V1 and V2 listed on the site?

Thanks

[Hampsta]

Actually if it helps my Tacho is the same as the first pic on forum SR Hardware's Stands and display units for GI-Max/Pro/SPI-D and much more!.
Thanks

[Cristiano]

Hello.
this is a known issue with Type-R rev counters.
They are cheap and popular but sometimes they don't reach the top of the scale. Another problem with these rev counters is that the needle sometimes moves too slow.

I tested one myself last year:

http://www.symprojects.com/type-r-rev-counter-tested/

and I had the same problem.

Cristiano

[Hampsta]

Well that answers my question perfectly. Thank you very much and yes I did also notice the needle was rather slow. Back to the shops I guess, lol. Thanks again.

[RD Hardware]

Yup the Type R is know for this, we go through a few to find a good one and return the rest. They are reliable tho and a good price. To be honest, a better one will cost 3-5 times as much  I am always lloking for a better unit tho......

[cuttingedgedigitaltv]

Hello
I really do love the Rev Burner, But I still can't get it to work in Dirt 2 and I'm not sure what to do with the sneak peak Dirt 3 thingy. (when I click on the execute file it doesn't show anything connected or any simulators in the list). I tried configuring Dirt 2 but the lines to edit look a little different in my hardware config. plus there are two of them. one in the Documents/Dirt 2 folder and one in the Steam/Steamapps/Common/ Dirt2.
Also there is no jumper on my board to put in Bootload mode so I can't figure out how to update the firmware. (or do I really need to?)
Anyway I,m having fun with it just the same, I guess I'll get it figured out. Here's a video of my 1st day testing the device. http://www.youtube.com/user/CuttingEdgeDigitalTV

[Cristiano]

Regard Dirt 2, the correct file is the one in Docoments/Dirt2
If you don't know how to change it, send me a copy and I will change it for you.

The beta versione of SImDash with Dirt 3 requires .NEt Framework v.4
Probably it is missing oon your computer and you have to download it.

You don't need to upgrade the firmware of the rev burner, unless you use it with a speedometer.
The new rev burners don't have the jumper for the programming but two pad in on the board to link together.
I will add a picture to the website soon.

Cheers
Cristiano

[cuttingedgedigitaltv]

Hi and thanks for the quick response, Ive already edited the hardware config file but where you have ip=127.0.0.1 mine says ip=dpad I changed it anyway and it still didn't work. here is a copy of the line now....<motion enabled="true" extradata="1" delay="1" port="20777" ip="127.0.0.1"/>

also I have downloaded and installed .NET Framework v.4, But no worries I can wait for the official patch, and thanks reply about the firmware.

[nescafe37]

if the line reads in  that order then thats your problem buddy..
It should read exactly as follows
 

 <motion enabled="true" ip="127.0.0.1" port="20777" delay="1" extradata="1" />

[cuttingedgedigitaltv]

Ahhh okay I'll try that when I get home, I've never changed anything in it before don't know why it's out of order, I'll just copy and past the whole line in later. thanks.
Just out of curiosity can you give me a detailed description of how to apply the Dirt 3 patch?

[Cristiano]

Dirt3 is not a patch but a beta version of SimDash which only works with Dirt3.

Cheers
Cristiano

[cuttingedgedigitaltv]

Aaaaah okay I was wondering why I didn't see the other simulators listed.

[cuttingedgedigitaltv]

if the line reads in  that order then thats your problem buddy..
It should read exactly as follows
 

 <motion enabled="true" ip="127.0.0.1" port="20777" delay="1" extradata="1" />

Woo Hoooo! Finally found the problem with Dirt 2 I did a search for the hardware config file and found there are 3 of them. There is a hardware config file For Dirt 2 in the MY Games folder also (they are all the same)  I copied and pasted that line in there and it works fine now. I left the other 2 config files that I changed before like they were after I changed them, I don't guess that will hurt anything. anyway the Rev Burner works fine now. Thanks for your help I knew it was something on my end. . Now on to tackle Dirt 3.

[cuttingedgedigitaltv]

Dirt3 is not a patch but a beta version of SimDash which only works with Dirt3.

Cheers
Cristiano

Okay I need some help with this one. What do I do with the Dirt3 folder I downloaded? I tried to the Sim dash .exe and it just opens the sim dash panel but shows nothing connected on the Main tab, and no simulators are listed in the Simulator tab. I tried to copt and paste contents of the folder in the Sim Dash folder in c:/programfilesx86/Sym projects/SimDash.1.3.2 folder and I got an error and Sim dash would not start. So I had to uninstall and reinstall SimDash.1.3.2. I even tried just putting the plug in folder in the SimDash.1.3.2 folder but that didn't work either. what am I doing wrong?

[chris p duck]

I have the same on the dirt 3 beta plugin. (have insatalled .net framework v4) when I open simdash (from the dirt3 folder, once unzipped) it opens but on the first screen where you usually have the list of devices it just has the Line of red dots, no device names. on the sims tab where you would usually be able to configure settings for your sims there is nothing listed... I know it's a beta, so just some feedback so this can hopefully be resolved with the next release.