think theres a rolling road at gotboost in feb m8 be nice to have a look about your car if you pop down this way usually get a good turn out of seats down here when theres somethin goin on.
-
Hey Guest one of our sponsors Progressive Parts is running Black Friday and Cyber Monday offers - more details here
cool look forward to seeing this in feb then m8, just out of curiosity how much does this water/meth cost to buy? and how much is it to fill the water/meth tank on it?
It's currently about £1 a litre - finding a supplier who will sell to the public is tricky though 
My tank is 3 quart (3.4 litres) but I use a 50:50 water/methanol mix so I'll get 50 litres from £25 worth of methanol.
3.4 litres looks to last me 25-30 miles on full chat so it doesn't take long to get through, though if I poodle along off boost it isn't used.
Based on the above I'll essentially get ~400 miles on full boost from 25 litres
My tank is 3 quart (3.4 litres) but I use a 50:50 water/methanol mix so I'll get 50 litres from £25 worth of methanol.
3.4 litres looks to last me 25-30 miles on full chat so it doesn't take long to get through, though if I poodle along off boost it isn't used.
Based on the above I'll essentially get ~400 miles on full boost from 25 litres
Last edited:
Well, with the abundance of snow and salt on the roads over the past couple of weeks the car hasn't seen much else than the walls of my garage but I gave it a good run over the weekend, over to Badger5 and then up to Autosport at the NEC
The current map requires a minor adjustment to remove a boost deviation limit that is currently causing the car to log the following 17963 fault code: http://wiki.ross-tech.com/index.php/17963/P1555/005461
With the addition of the Forge MBC it is sometimes confusing the ECU when (as far I understand it) the readings given from the MAP sensor deviate from that of the MBC, which the ECU still believes is being provided by the N75. As the MBC is sustaining higher levels of boost there is sometimes a discrepancy between the values that can raise this fault code when the deviation is too high.
I've noticed this only happens when I'm holding the revs and feathering the throttle (i.e. in preparation to overtake) and then open it up to WOT, causing erratic boost readings that is confusing the ECU.
The annoying thing is that when this fault is triggered the car refuses to boost and I have to wait an indeterminate amount of time for the power to come back, or pull over and clear the code, though luckily this just requires a simple bench flash to remove the limit file from the map so that it is ignored under all circumstances so I'll look to get this done sometime over the next week.
Other than this the car is performing very well I went to Autosport in convoy with a friend's P1 Impreza tuned to 400 BHP which I was very surprised to keep up with 
From a rolling start and up towards naughty numbers the P1 gained 2-3 car lengthes towards the top end, making for big smiles I just love the buckets and buckets of torque that can be delivered instantaneously from sub-3,000 RPM
Now I've seen how it compares to something else I feel very happy with the car and look forward to Brands Hatch next Weds (hopefully by which time the map will also be sorted)
The current map requires a minor adjustment to remove a boost deviation limit that is currently causing the car to log the following 17963 fault code: http://wiki.ross-tech.com/index.php/17963/P1555/005461
With the addition of the Forge MBC it is sometimes confusing the ECU when (as far I understand it) the readings given from the MAP sensor deviate from that of the MBC, which the ECU still believes is being provided by the N75. As the MBC is sustaining higher levels of boost there is sometimes a discrepancy between the values that can raise this fault code when the deviation is too high.
I've noticed this only happens when I'm holding the revs and feathering the throttle (i.e. in preparation to overtake) and then open it up to WOT, causing erratic boost readings that is confusing the ECU.
The annoying thing is that when this fault is triggered the car refuses to boost and I have to wait an indeterminate amount of time for the power to come back, or pull over and clear the code, though luckily this just requires a simple bench flash to remove the limit file from the map so that it is ignored under all circumstances so I'll look to get this done sometime over the next week.
Other than this the car is performing very well
I went to Autosport in convoy with a friend's P1 Impreza tuned to 400 BHP which I was very surprised to keep up with From a rolling start and up towards naughty numbers the P1 gained 2-3 car lengthes towards the top end, making for big smiles
I just love the buckets and buckets of torque that can be delivered instantaneously from sub-3,000 RPMNow I've seen how it compares to something else I feel very happy with the car and look forward to Brands Hatch next Weds (hopefully by which time the map will also be sorted)
CupraBout
Guest
Well, with the abundance of snow and salt on the roads over the past couple of weeks the car hasn't seen much else than the walls of my garage but I gave it a good run over the weekend, over to Badger5 and then up to Autosport at the NEC
The current map requires a minor adjustment to remove a boost deviation limit that is currently causing the car to log the following 17963 fault code: http://wiki.ross-tech.com/index.php/17963/P1555/005461
With the addition of the Forge MBC it is sometimes confusing the ECU when (as far I understand it) the readings given from the MAP sensor deviate from that of the MBC, which the ECU still believes is being provided by the N75. As the MBC is sustaining higher levels of boost there is sometimes a discrepancy between the values that can raise this fault code when the deviation is too high.
I've noticed this only happens when I'm holding the revs and feathering the throttle (i.e. in preparation to overtake) and then open it up to WOT, causing erratic boost readings that is confusing the ECU.
The annoying thing is that when this fault is triggered the car refuses to boost and I have to wait an indeterminate amount of time for the power to come back, or pull over and clear the code, though luckily this just requires a simple bench flash to remove the limit file from the map so that it is ignored under all circumstances so I'll look to get this done sometime over the next week.
Other than this the car is performing very well
From a rolling start and up towards naughty numbers the P1 gained 2-3 car lengthes towards the top end, making for big smiles
Now I've seen how it compares to something else I feel very happy with the car and look forward to Brands Hatch next Weds (hopefully by which time the map will also be sorted)
Code is ready now for you robbie
just let me know when you can come down and I'll upload it.
Wow that was quick, awesome thanks
I'll give you a text in the week to confirm which night I'm free to head over Bill
ian_cupra
Guest
hey up mate, long time no speak, glad to see all is going well with it.
i'm up for a bit a rolling road action. got a few things i need to sort on mine though before i get it out on the rollers
Hey mate, yeah been a while, cheers
Hybrid RR day is definitely called for at some point!
You got your mani now??
ian_cupra
Guest
Hey mate, yeah been a while, cheers
Hybrid RR day is definitely called for at some point!
You got your mani now??
in a word no
been so busy with house, really need to ring them and sort it, i did PM them not so long ago,, but got a feeling they will have ignored me
Robbie is the MBC your running the forge UNOS boost controller or a different one? Not sure which to buy.
Glad your enjoying the car and giving her some stick!
Glad your enjoying the car and giving her some stick!
Similar threads
