Jump to content

ivosmo

Finding my way
  • Posts

    7
  • Joined

  • Last visited

Profile Information

  • Location
    Poland

Car Info

  • Model
    Octavia 3 FL combi
  • Year
    2019

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

ivosmo's Achievements

Rookie

Rookie (2/17)

  • Conversation Starter
  • Dedicated Rare
  • First Post
  • One Month Later
  • Week One Done

Recent Badges

0

Reputation

  1. Turns out I was in the wrong and everything is working as supposed. Still I believe it would be better if the system activated also when front parking sensors activate automatically. So it turns out I was looking at PDF instructions manual (which I found somewhere on the Internet) and couldn't find any info regarding this matter. But today I downloaded the PDF manual from Skoda's website (by entering my VIN number first) and in this new PDF there is one additional sentence regarding the automatic emergency braking - it says it works only if parking sensor are activated by changing gear to "R" or by pressing a button on central console - just like it works in my car. Still I believie it would be better if it also worked by default when front parking sensors activate automatically. Anyways - "problem" resolved
  2. What about manoeuvre assist (auto braking) when going forwards? My car, when I creep forward in traffic, activates front parking sensors (little overhead view appears on the left of the infotainment main screen) and I get the beeps but unfortunately the „auto braking” icon is orange - so it’s disabled and the car won’t stop on it’s own. I would have to manually tap the icon first to change it to white…any idea why? And any way to make it „activated” by default when front parking sensors turn on on their own? It works if I press the parking sensors button near gear selector - the car will then stop on it’s own when going forward. But it’s not really helpful if I get distracted in traffic and the car in front of me stops suddenly…
  3. Hello! I have a question regarding the manoeuvre assist system - I can’t quite wrap my head around it. So I have a Skoda Octavia III FL with DSG7 gearbox. The car is equipped with front and rear parking sensors and rear camera. I have manoeuvre assist turned on in the „car” -> „setup” menu. When I change gear to R - rear facing camera turns on, parking sensors activate and I get the beeps as I get closer to an obstacle. If I don’t brake on my own - the car applies the brakes and stops on it’s own - all good. But then, when going forward: Scenario A: standing still, then let go off the brake pedal. The car starts driving forward, close to an obstacle (roll of bubble wrap ) the front parking sensors activate (infotainement shows overhead view of the car with all the grey-yellow-red stripes) but the „manoeuvre assist” icon on the infotainement system is orange (so it’s turned off) and the car keeps beeping but simply rides into the obstacle Scenario B: standing still I first press the parking sensors button on the center console (near the gear selector), the sensors and rear camera activate. The I let go off the brake pedal, car starts driving forward, I get the beeps as I get closer to the obstacle, the „manoeuvre assist” icon is white (so it’s turned on) and the the car automatically stops in front of the obstacle. It works like that every time - but why? It doesn’t make sense to me - the car is clearly capable of braking automatically when going forward but it doesn’t do it unless I manually press the parking sensors button OR tap the orange „manoeuvre assist” icon on the main screen when the parking sensors activate automatically. So when in a traffic jam the car in front of me starts going and then stops suddenly (and I don’t press the brake pedal) I will rear-end it - unless I manually press a button before… This seems wrong to me and kind of defeats the purpose of the system… Am I missing something? Is there a setting I can change to set the „manoeuvre assist” braking to be „on” by default when the parking sensors activate automatically? Or maybe it can be coded via VCDS? Here is a short video to show the issue (first clip is scenario A and second clip is scenario B). I would rather prefer it to be the other way around - i.e. I would like to have to press the button / icon to „disable” the system and not to „enable” it…
  4. Will the Altair 19” rims fit „older” Octavia 3 FL (not vRS, standard 1.5 TSI)? I believe they would need to be paired with 225/35 R19 tires for the older Octavia as older Extreme 19” rims were supposed to be used with 225/35 tires. Will this combo work? I kinda like the full silver look of Altairs and I’m looking for a set of bling wheels for summer for my Octavia 3 (also in silver colour so they would complement each other). Silver Extremes would be nice too but are very hard to come by - most are either black or anthracite - and I don’t really like the look and think they wouldn’t suit the car. Sooo…can Altairs be used with 225/35 tires and would they fit Octavia 3? I believe they should but cant find a picture anywhere - of Octavia 3 with them or even Altairs with 225/35 tires (all I can find is 225/40 of the current Octavia 4)
  5. OK thanks. Seems the issue is more complex than I thought. I did some testing and the gauge shows correct values when in range of 0-110 kW but it simply clips at 110 kW and won't go above (i.e. values calculated from torque and RPM logs are the same as shown on the gauge during driving - so I thought ECU is feedig it the correct data but cluster is unable to show them properly). I thought it's the same as, for example, a tachometer with range of 0-100 kph. It would show correct values when driving in the city but would stop at 100 kph during a motorway drive with higher speeds. Or similar to a kitchen scale when someone tried to weigh their bodyweight on it. So I though it's a matter of changing the gauge's range in cluster coding. But if it's not possible or is in fact ECU dependant then I i just won't bother. Thanks for the replies
  6. Thank you for the reply. I understand that it’s just computer generated and not an actual measured value (AFAIK there isn’t even a „engine power” or whatever it would be called measuring block in VCDS so I guess there just isn’t any sensor that would measure that). And I understand this gauge has no influence on the engine performance etc. It’s just a gauge. However it has to somehow take into consideration the actual engine parameters (presumably torque and RPM) as it „climbs” to the stock maximum of 110 kW quicker than before remap (as it should because the remap boosted the engine’s performance). I made couple logs of engine torque and RPM and calculated the engine’s kW output from that. Calm driving with ~40-50 kW at the gauge produces the same values when I calculate them in a spreadsheet log file. But going „full gas” the gauge tops at 110 kW and of course spreadsheet calculations go above that. That leads me to believe that the gauge actually shows kW value calculated from „real” measured torque and RPM. But it’s simply limited at the top end. If it’s not possible then I can just live with that. But looking at this vid it should be possible - the gauge goes up to ~ 284 kW which corresponds with the modded value od 387 PS stated by the author. But I might be completely wrong as I’m no expert at all 🙂
  7. Hello - quick question. I have a factory fitted VC in my 2019 Octavia 3 FL. I had the engine remapped recently (stage one). When I go into „sport” mode od my VC I get the usual „kW” gauge in bottom left showing current engine output. However it maxes out at stock 110 kW (1.5 TSI ACT). Is it possible to code it through VCDS to max out at the correct stage one values? After the remap it’s (supposedly) doing ~135 kW according to the dyno measurements. I think it correctly shows the current output but simply maxes out at 110 kW - it gets there much quicker then prior to remap. Is there a setting I could change through VCDS to correct the maximum value it’s showing?
×
×
  • Create New...

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.