Thứ Bảy, 5 tháng 11, 2016

Firmware 6.2 part 5

  • Apr 18, 2015
    Bet TSLA
    I got the first 6.2 update fairly early, which was 6.2.124, but I haven't seen anything new since. I'm not sure the newer updates have anything to offer a P85 with autopilot. Maybe some bug fixes?
  • Apr 18, 2015
    dirkhh
    Things seem confusing. There were changes to the behavior with muting when getting out of and back into the car.
    Some P85 owners seem to say that performance and consumption improved in .153 but I don't think there's hard data.
    Most everything else seems to be more applicable to Ds.
    And no one seems to know what's new in 101.36.2 which so far has only been seen in older pre-AP cars...
  • Apr 18, 2015
    gmontem
    Have any of the classic 85 owners noticed any speed improvements with .153?
  • Apr 18, 2015
    mdevp
    Is the P85D's 0-60 even better than 3.1secs with 6.2 (2.4.168) from .153?
  • Apr 18, 2015
    FlasherZ
    I received 6.2.160 this afternoon.
  • Apr 18, 2015
    pgiralt
    I have this printed out and posted on the door to my office at work :)
  • Apr 18, 2015
    Larry
    With my 101.36.2 in my Classic the seat belt chime only rings 3 times then stops when you first get in or if you take the belt off when still in D. It used to stay on until the belt was latched. Anyone else notice this?
  • Apr 18, 2015
    thecloud
    Got .160 last night. It still has Valet mode. I wonder if rebooting your center console (holding in both scroll wheels on the steering wheel until the screen goes black and restarts) would bring it back? Previous updates seem to have required more than one reboot to fix odd glitches like this.

    A word of warning: once you use Valet mode, don't ever forget your PIN! I had previously tried out Valet mode after the last firmware update, and for some reason thought the PIN was cleared once you successfully entered it to leave that mode. Then I tried selecting Valet mode just now, and it immediately went back into that mode without asking me to set a PIN. I had to rack my brain to remember the original PIN that I set last time (which I deliberately wanted to be something different than, say, my ATM PIN.) There is a reset available if you know your MyTesla password; fortunately I didn't need to find out if that worked.

    I suppose if you're pulling up to a valet stand, you don't want to be fumbling around to set a PIN while the valet is waiting, but I like the idea of being able to set a new PIN each time (sort of like a hotel safe), so it's fresh in my mind.

    And it turns out there is already a thread on this subject that I missed seeing before.
  • Apr 18, 2015
    smartypnz
    Tried to update on the "Tool", but it deleted my last entry - probably because the new one was done on the same day as the previous one.
  • Apr 19, 2015
    zwede
    It's always chimed a few times and then turned off ever since I got my car 14 months ago. Before anyone gets upset at me not wearing my seat belt: I back out of the garage first, and then put it on when I put the car in drive. Had to do it that way with my old car to turn around and see when backing up, and the habit has stuck even with the camera equipped MS.
  • Apr 19, 2015
    FlasherZ
    After my upgrade to .160, during the first few drives my car was located (on the nav map) about 200-300 feet southeast of where it was really located. Since then, it appears as if it may have self-corrected, but it was very odd.
  • Apr 19, 2015
    Larry
    Hmmmm. From a safety perspective shouldn't it keep chiming until you buckle it? Just weird that it changed I guess.
  • Apr 19, 2015
    wk057
    I rarely drive without a seat belt, even when just doing quick repositions and such.

    The behavior I've experienced the handful of times I didn't was that it would chime for quite a while (minute or so?), then give up for a short while, then repeat. It never fully gave up. Even with the passenger belt if there was a passenger... or annoyingly, if I had a box or heavy bag on the passenger seat, requiring me to buckle the passenger belt.
  • Apr 19, 2015
    PaulusdB
  • Apr 19, 2015
    Andyw2100
    Some quick observations having taken a couple of short trips with .168:

    The first only happened once, on the "outbound" leg, but not on the other end, so I have no idea what to make of this, but I'll explain, and continue to monitor it. In the past, if I had charged the car to say, 90% with range mode off, and it showed a charge of, say, 227 range miles, when I turned range mode on, just before starting a trip that I was also going to be tracking mileage for, the remaining range would change to 229 just after I turned range mode on. (I think it changed when I left that menu selection.) I noticed today that it did not change. Now I had also supercharged for the first time, so I can't say what the behavior would have been like before immediately after supercharging. But this time, with .168, when I made the switch from range mode off to range mode on, the remaining range did not increase by the expected two miles (or by anything.) I noticed as I started driving that it did seem that the rated range did not decrease for some time, so that may be where the increase was accounted for, but that makes measuring range used a bit difficult. I expected to see the same behavior when I reached the end of my trip and switched range mode off, meaning that unlike before .168, when the remaining range would have immediately decreased by a couple of miles, it would not. However that's NOT what I saw. The behavior when turning range mode off was exactly as before: my remaining rated range decreased by two miles.

    Take the above for what it's worth. I realize most of you probably don't care about this.

    Another thing I paid attention to was audio volume when opening and closing the door. I can't tell a difference from the behavior now, and the behavior I believe I've always had. With the audio playing if I open the door it continues playing, but at a lower volume. When I close the door the volume increases to where it was. If this is different from what was happening in .136 and .153 and other versions then it may well be "fixed." I went straight from .124 to .168. If it was also "broken" in .124, I guess I must not have noticed it. If I've misunderstood what people see as the problem, feel free to disregard this part too.

    I can't say anything about acceleration in insane mode because my wife was in the car and she gets motion sick if I drive in any way other than the proverbial little old lady who only drives on Sundays. I can say that one concern I had was that the go pedal would be so much more sensitive that the car would be a little tougher to drive efficiently in Insane mode, and I did not notice that at all. I expect the increased power is probably there if we ask for it, but it does not seem to be an issue if we don't. So that's good.
  • Apr 19, 2015
    rickgt
    Your Tesla app will send a notice. Then there will always be a small clock at the top of the 17" screen. Touch it and set the time for the update
  • Apr 19, 2015
    gregsapphire
    I got a P85D and am still waiting for .168.
  • Apr 19, 2015
    Ugliest1
    There are times when it intelligently doesn't chime, but I can't give you the well-researched if-then statements. For an example, in the ferry lineup we often take our belts off. When the ferry loads, we usually are travelling under 15km/hr, and the chimes do not activate (or, maybe they just activate once for 5 seconds). If I go above 15, they chime at frequent regular intervals. I like it!!

    And I can't recall this changing recently, it's been this way for months at least.
  • Apr 19, 2015
    Larry
    It must have just been a temporary glitch as I tested it multiple times today over a 3 hr drive and it worked fine. Chimes for 30 secs or so, pauses for 10, then restarts the cycle. It just wasn't doing that yesterday. Problem solved for now.
  • Apr 20, 2015
    Kilowatt
    I'm experiencing extremely slow UI after a few days with .153. Even the cruise control has response lag of seconds. Must try a reset.
  • Apr 20, 2015
    andrewket
    I was seeing lag as well. A rebooted fixed it. Audio stuttering etc. I tried to report it via the voice command "bug report" but that too was having problems.

    Likely a hung process or memory exhaustion.
  • Apr 20, 2015
    HankLloydRight
    So you received and installed a firmware update, and later that same day received and installed another update? What were the two build versions?
  • Apr 20, 2015
    castor
    Ha, I did the same !!!!
  • Apr 20, 2015
    ShortArc
    Just updated from v6.2 (2.4.136) to v6.2 (101.36.2) on my P85 Sig.

    New? "Model S will now display charge time remaining when you are Supercharging or CHAdeMO charging".
  • Apr 20, 2015
    brianman
    .153 had that IIRC
  • Apr 20, 2015
    Benjamin Brooks
    .136 has this as well
  • Apr 20, 2015
    smartypnz
    version (2.4.153) has bugs. Cruise reverted to 3 second hold and I often get a warning that driver assisted programs are not useable???
  • Apr 21, 2015
    HankLloydRight
    The first was .168 which brought me into the 6.2 world and then that afternoon, I got notified and installed the 101.36.2
  • Apr 21, 2015
    Bugeater
    Ok, thanks. I added the 2.4.168 to the database appearing on the day before 100.36.2 so they are both recorded.
  • Apr 21, 2015
    Torpedo Ted
    I wish the seat belt chime would NOT sound unless the car is not in park! Seems useless if the car can't go anywhere.
  • Apr 21, 2015
    wk057
    I know! I find it very annoying that it keeps chiming even when I put the car in park. Makes no sense.

    Also another minor bug: In 6.2 the 24h clock is not showing correct. It shows as 18.00, instead of 18:00 which is the correct way for Europe (it has always been correct before 6.2).
  • Apr 21, 2015
    brianman
    S85 loaner with autopilot hardware (P62xxx) I received today has 2.4.160.
  • Apr 21, 2015
    Stoneymonster
    P85+ w/o autopilot loaner I received today also has 2.4.160 firmware.
  • Apr 21, 2015
    Barry
    I just got an update notice. I'm currently on .153 (85D). Says it'll take 2.25 hours so I'll apply overnight.
  • Apr 21, 2015
    MrClown
    Same here. Installing now.
  • Apr 21, 2015
    xy46
    85D release notes got an update about the acceleration changes with .168. I don't remember .153 having that in the notes.
    20150421_180416.jpg
  • Apr 21, 2015
    Stoneymonster
    Received update notice today - installed v 6.2 (2.4.168). I have added it to the database.

    Unsure if it's real or not, but regenerative breaking doesn't seem as strong?
  • Apr 21, 2015
    xy46
    Someone says that every time :) But sometimes the toggle gets reset, make sure it's where you had it. Maybe even toggle it just to be sure it sticks.
  • Apr 21, 2015
    Stoneymonster
    Thanks - I had both those thoughts, too. :smile: Toggled the setting on/off several times, but it felt the same regardless. Probably just placebo effect. LOL
  • 1/1/2015
    guest
    I think they change it a bit every time just to mess with us.
  • Apr 21, 2015
    NSX1992
    I just installed version 168 and it does state the 0 to 60mph has been reduced from 3.2 to3.1 sec. Can't wait to try it out.
  • Apr 21, 2015
    breser
    Can confirm it wasn't there on .153 and is on .168.
  • Apr 21, 2015
    Cosmacelf
    Actually, it's a random number generator change - different cars get slightly different regen settings after every update :)
  • Apr 22, 2015
    tomas
    Geez, starting to feel that way. I always thought talk of regen changes was psychosomatic, but with 6.2 my normal is like low and my low is like none. May go to svc ctr and beg for latest build.
  • Apr 22, 2015
    mibaro2
    Strange. My car on 6.2.136 doesn't chime if I am in Park and remove my seatbelt. It has been this way for a year now. I wait at the GO Station picking up people, and often have the car in park and undo my seatbelt. When I put the car in drive, it will chime at me and I put my seatbelt back on.
  • Apr 22, 2015
    SteveS0353
    I tested this yesterday when my wife got out of the passenger seat. The car was in drive and the chime started as soon as she undid the seatbelt. I put the car in park, and the chime stopped, but the little red indicator on the console still flashed until she got out of the seat. It's behaved that way since I've had the car.
  • Apr 22, 2015
    breser
    Well my personal complaint about the seat belt chime is that I have the habit of stepping on the brake as soon as I get in the vehicle. I put on my seat belt with my foot on the brake typically. But as soon as I touch the brake and the car is awake it starts complaining that my seat belt isn't on.
  • Apr 22, 2015
    LaTache
    FWIW, I got software update yesterday from .153 to .160, was hoping for .168. Guess they are testing .168, before full roll out to P85Ds?
  • Apr 22, 2015
    wk057
    I got the .168 update last night on my P85D.
  • Apr 22, 2015
    xy46
    That is exactly how it feels to me, too. In fact, went in to toggle switch and tried it both ways. Even rebooted twice since it seemed to feel so different. I have read the many posts on here about how people seem to "sense" subtle changes that are probably not changes at all, but I have to agree this does feel different to me. Psychosomatic - maybe? Maybe not? :smile:
  • Apr 22, 2015
    wk057
    Sometime in the past few updates regen coming out of TACC got super feathered.

    Regen from manual control on the P85D has been slower to ramp than the P85 since I got it. I drive both regularly so this is not just in my head. lol.

    They are almost certainly tweaking how regen works on the P85D as they go. 100% certain. The P85 hasn't changed at all, however.
  • Apr 22, 2015
    Andyw2100
    Until a couple of days ago I had never driven any Model S other than my P85D, after having received my P85D. It was going in for the windnoise TSB, and to have the winter wheels taken off and the summer wheels put on, so I received a loaner S85. The first time I drove it down my block, which has a stop sign at the end of it, down a hill, I wondered what the heck was wrong with the regen, and assumed it must have been set to "low." It wasn't.

    The battery wasn't warm, and the regen limit was showing at about 35. But coming down the hill and completely removing my foot from the "Go" pedal, essentially asking for all the regen available, saw the regen bar go to about 15 or so. Obviously I needed to use the brakes, in a situation where with my P85D I would not have. I drove the car a bit more, but it has been mainly my wife driving it. The little bit I drove it, regen seemed to get better than that one experience with it, but still did not seem as strong as on my P85D.

    I guess the one question I have is what would be an explanation for the regen not immediately ramping up to whatever the regen limit was showing as when I released the "Go" pedal? I know there has been discussion of how fast the regen ramp up occurs, but I was watching the S85s regen bar, and it was stable at about 15 as the car was heading down the hill. (The battery was not close to fully charged.) The way regen behaved during those few seconds, it almost looked as if the regen limit was set to 15, instead of to 35.
  • Apr 22, 2015
    wk057
    Depends on speed. The RWD versions have much less regen at lower speeds than the P85D. That would be my guess as to what you experienced.
  • Apr 22, 2015
    Andyw2100
    Thanks.

    It was low speed, so I'm sure that's what it was.
  • Apr 22, 2015
    Bugeater
    That's exactly the behavior I see. It's not about when you're getting out, it's about when you're getting in.
  • Apr 22, 2015
    NigelM
    Doesn't happen here. Seat belt chime only comes on when the car reaches a certain speed (forwards or in reverse); it's always been like that.
  • Apr 22, 2015
    wk057
    Hmm. I agree with bresser. The chime comes on immediately upon hitting the brake for a few iterations, then silences. I'll have to check if this is different in the P85 eventually, but I know the P85D does it.
  • Apr 22, 2015
    Klaus
    My experience too. Tried it this morning. It starts chiming when I start driving, past the driveway, maybe 10 km/h ~ 6 mph.

    On the other hand, when we get home and my wife unbuckles before we're backed in all the way it chimes even when we're basically stopped. Chiming stops when I switch to park.

    This has never changed since we got the car almost 2 years ago.
  • Apr 22, 2015
    morbot
    Did some searching but didn't find anything...

    Anyone else having problems with screen brightness settings? I originally had my daytime brightness set to 65% and my night time brightness set to 35% then set it to auto... and it would change brightness accordingly.

    Since 6.2, it seems it just defaults to the daytime brightness even when it auto switches to night mode... its intensely bright :(
  • Apr 23, 2015
    Barry
    Now that you mention it, my screen seemed unusually bright when I pulled into the garage yesterday. I hadn't noticed it before.
  • Apr 23, 2015
    Kilowatt
    Yes, I've noted the same
  • Apr 23, 2015
    Forty Creek
    I also had this experience after the update. Seems like the previous brightness settings were lost. I switched my lights from AUTO to DAYTIME and then back to AUTO. I think this may have fixed the glitch. Did this recently, so I'm not positive that it worked.
  • Apr 23, 2015
    morbot
    Guess I'll try reporting it through the build in bug reporting system next time I notice it. Problem is, the days are getting so long that I'm not doing as much night mode driving.

    Hate to call that a "problem"... I love our long summer days here in Seattle :)
  • Apr 24, 2015
    KenN
    Bugs the hell out of me too. I too USED TO put my foot on the brake as soon as I get in. I am now re-training myself to put the seat belt on prior to touching anything. What I MIGHT do is buy one of those set belt extension things and leave it plugged in all the time, that way I never have to hear the chime, even if I choose to not wear the belt at all.
  • Apr 24, 2015
    apacheguy
    So the service center installed 160 into my P85 yesterday during my annual service. I noticed one minor change right away - the pins on the map that show "placed I've charged" have changed from with with gray lightning bolt to gray with white bolt.
  • Apr 24, 2015
    spentan
    IIRC, Elon said something about the Nav polling SpC status in real time roughly every 30 s. Do we have any idea how this information is factored in or what is done with it? Specifically, what parameters are polled and why do they need to be polled in 30 s increments. I have seen no evidence of this behavior on my car so I am quite skeptical of what Elon said.
  • Apr 25, 2015
    tomas
    I showed up to the San Juan SpC, had enough charge to get home, all chargers full and it still told me to charge there.

    So I'm skeptical hippo

    ImageUploadedByTapatalk1429954064.775516.jpg
  • Apr 25, 2015
    Danal
    Sometimes he confuses future and current tense. Nonetheless, will been there eventually.
  • Apr 25, 2015
    hiroshiy
    yep, me too. Setting to one of the day/night and then back to Auto seems to have fixed it.
  • Apr 25, 2015
    KenN
    I got 160 at the service center yesterday and found one small issue. My mirrors no longer tilt when in reverse. Tomorrow I'll reboot and see it fixes the problem. Not a big issue. P85 Classic.
  • Apr 25, 2015
    trils0n
    Same for me when I got 160. It seem that mirror settings were lost from profiles. Just re - adjust and update your profile.
  • Apr 25, 2015
    evp
    Every time the Service center installs a new version of the software I lose my mirror reverse settings. Have to reset them.
  • Apr 25, 2015
    dirkhh
    Got 6.2 (2.4.136) the night before a road trip to the West Coast. 4400 miles later, I found a few bugs -- some were probably pre-existing, some new to this release.

    * After sitting in the driver seat for a while during charging, I got out to get something from the back seat. I found the back door handle to be non-functional, and it tried to retract and crush my fingers. It then changed its mind and re-extended, now active. This happened twice, so I'm claiming it wasn't just a fluke of timing.

    * (not new) The charger port light color is often inconsistent. Some times white when it opens, some times dark.

    * If you have a trip active and stop for charging, get out of the car and come back, the map and energy windows go into "calculating route" mode forever. You must re-select the destination for it to actually finish calculating the route.

    * (seen before) Several times, the display switched to night mode when the sun was still shining brightly.

    * Trip Adviser told me that 118 rated miles was sufficient to do a 117 mile leg. That's highly unlikely.

    * Suggestion: the trip overview should list the mileage and estimated ETE for each leg of the trip.

    * The estimated time for charging for a segment appears to ignore the current state of charge, i.e. it'll tell you that you need 30 minutes charging at the next charger whether you start the leg fully charged or with just enough energy to complete the leg.

    * The radio turns on quietly when you open the door, then goes mute a few seconds later, independent of the mute state when you left.

    * The computed route from Reno to Grand Junction is different depending on whether Trip Adviser is turned on or off. When it's on, the route uses US6 from Provo to Green River; turn it off, and the route takes I15 down to I70.

    * My friend moved several hundred miles. I deleted her old address in my phone, then deleted her entry in my favorite places list, clicked on her new address in the contacts, and added her back to the favorites. The new favorite's description has the correct new address, but if you select it as a destination, the map point it routes to is the old deleted address. (Probable cause: both addresses were in the contact list for a while, the favorites list just points at "the first address of this contact" instead of making its own copy.) I found a way to reset the favorite correctly by manually typing in the address as a search.

    * Likewise, the new "lightning bolt" search for nearby charging stations fails the new-address test. Since I had charged at her new address, this location was added to the "I've charged here" list. But when I changed her address in the contacts list, the known charger's map location changed to her old house even though the displayed address continued to display the correct new address. I have no idea how to fix this one.

    * (not new) After a "Vulcan Death Grip" reboot, the car doesn't notice that it needs to re-scan the contents of the USB media drive until you decide to select a song to play. This should be done immediately at boot.

    * The U/I is MUCH slower to respond. Adding a new app, setting a window full-screen, clicking on a URL in the browser -- these all take so long that I'm often convinced the screen-touch didn't register.

    * Some nonsense routing decisions from Trip Adviser. Example: coming north from Harris Ranch with destination Burlingame, the suggested route is to Fremont, then drive insane East-Bay traffic and over the bridge. The correct route -- shorter, little traffic -- is Gilroy. Other example: destination is a hotel on the strip, the suggested route includes charging at the Los Vegas Supercharger followed by a 4-mile last leg to destination.

    * Enhancement: Traffic changes cause silent routing changes. Suddenly a diversion to a side-street appears, but no explicit warning that a re-route has happened.

  • Apr 25, 2015
    lolgas
    Same here. There seems to be something odd in the way they install updates at the SC...
  • Apr 25, 2015
    dsmith2189
    You should, if you haven't already, report these finding to Tesla HQ so that their QA team can address and fix known bugs in their next minor release.
  • Apr 25, 2015
    hiroshiy
    yup, this one drives me crazy. AAAAAAAAAAAAAAhhhhhhhhhh:cursing:
  • Apr 26, 2015
    Gr8pursuit
    KenN, trils0n, dirkhh,
    Thank you! I didn't know that mirror auto-tilt settings are always erased after SC update. This is the first time I use mirror auto-tilt... :)
  • Apr 26, 2015
    TES-E
    Another software update 4/25

    Anyone else get notified of a software update on their app. Got one yesterday afternoon but my car has been at the SC since Friday so I don't know what the update contains or if it automatically updated while sitting at SC overnight. Will find out when I pick it up Monday.
  • Apr 26, 2015
    araxara
    .160 was installed in mine at the service center on Friday. Bug fixes as far as I know. Don't see anything new that wasn't already in 6.2.
  • 1/1/2015
    guest
    You will also get the update notice when the Service Center updates your software.
  • Apr 26, 2015
    jweinstein
    I'm not sure what's new, as installation just completed...

    0958e2842f22f64da4cbfb67ad396c23.jpg

    906cb1d325bfbca76dda1a2a18565548.jpg
  • Apr 27, 2015
    ra-san
    Seems like this is only affecting some cars. I've seen multiple people complaining about this muting change, but I still haven't seen it happen on .168 (or .188 - not at the car to check, but one of those two). Also never noticed in earlier versions.

    Mine lowers the volume when the door is opened and raises it back when the door closes. No muting or pausing. It might be the case that it unpauses audio I left paused, but not even sure about that.
    I'd file a report, but also maybe ask for a re-flash?

    Are all you having this issue on the same audio hardware (studio or whatever vs. standard)? Is it all audio sources, just Slacker, etc.? Is it happening in new cars too, just older ones, etc.? And you do mean mute vs. pause?

    For reference, P85D made in December, upgraded sound, don't see the issue with Slacker - not certain I've confirmed with USB.
  • Apr 27, 2015
    dirkhh
    Indeed new - first sight of .188.
    Just yesterday I was guessing that we should see a new one, soon :)
  • Apr 27, 2015
    PaulusdB
    And with that number (2.4.188) we're back on track of our 'normal' version 6.2 schema.

    It seems 101.36.2 was an oddity after all.
  • Apr 27, 2015
    dirkhh
    Possibly - the report is from an 85 with autopilot. Every single car that reported 101.36.2 was non-AP...
  • Apr 27, 2015
    Gr8pursuit
    Your probably right on that, since no one has mentioned a new update.
  • Apr 27, 2015
    dirkhh
    And just to prove my point (I guess - after all, the world DOES revolve around me, right?) we got another report from a non-AP P85 who received 101.36.2 today...
  • Apr 27, 2015
    matbl
    Update scheduled for tonight. Classic nonAP S85. So we'll see soon...
  • Apr 27, 2015
    mesalum
    On iOS right? Not on Android.
  • Apr 27, 2015
    araxara
    I only have iOS devices, so I wouldn't know about Android. Doesn't the Android app provide notifications?
  • Apr 28, 2015
    matbl
    I got 2.4.188. Classic S85.
  • Apr 28, 2015
    PaulusdB
    So, Occam's razor still cuts as sharply as ever. :wink:
  • Apr 28, 2015
    GetAmped
    My car is parked in my Garage and I just received a notice to upgrade. It states the upgrade will take 2.5 hours to complete. Would be cool if we are getting the promised Self Driving features finally. Will post back after the update unless someone else does first.
  • Apr 28, 2015
    Phil K
    Just updated to 2.4.188
  • Apr 28, 2015
    Phil K
    Just updated to 2.4.188, S85 Autopilot.
  • Apr 28, 2015
    caps04
    The Sport Acceleration Mode is gone in 85D that was added in the last update. It's always in Sport now (0-60 in 4.4 seconds) which makes sense.

    Don't see any other changes, yet.

    IMG_2961.JPG IMG_2954.JPG IMG_2960.JPG
  • Apr 28, 2015
    caps04
    85D Sport Acceleration is now the default. Normal-Sport setting is removed.
  • Apr 28, 2015
    Khatsalano
    S85D, patching right now on morning of 4/28/2015 from .153. I'm sure there are lots of invisible upgrades beyond just removal of a button, but that remains to be seen. They seem to fine tune the drive train algorithms and fix many other issues with each "silent" no-notes patch.
  • Apr 28, 2015
    benjiejr
    Got notification for update. Applying now.

    I'll be sure to update the tracker when I know what the version is @dirkhh lol
  • Apr 28, 2015
    LetsGoFast
    Just loaded 2.4.188 on a P85D
  • Apr 28, 2015
    LetsGoFast
    I just completed .188 but I can't update the tracker until I get home because I have no idea what my pin is. :tongue:
  • Apr 28, 2015
    GetAmped
    After the .188 update my P85D is stating a "more insane" insane mode with a drop in the Zero to 60 from 3.4 seconds to 3.3 seconds, a more responsive accelerator pedal (??) and a high speed passing update supporting up to 155 mph. Guess this is important for all of the race track drivers??, don't see this being a useful update...other then bragging rights.
  • Apr 28, 2015
    andrewket
    3.4 to 3.3? It should be 3.2 to 3.1, afaik.
  • Apr 28, 2015
    ScepticMatt
    3.2 was 0-60 mph, 3.4 was 0-100 kph
  • Apr 28, 2015
    MarcG
    Any new details in the release notes? Did they remove the INSANE option?
  • Apr 28, 2015
    Terra117
    I installed 2.4.188 this morning.The Sport/Insane toggle is still there.
  • Apr 28, 2015
    Max Power
    P85D on 2.4.188 shows that Insane mode is now even more insane!

    K301zHw2.jpg
  • Apr 28, 2015
    spentan
    I think 168 had that as well.

    I'm driving to Vegas in about 60 mins so I don't wanna risk it taking longer than expected. I'll install it when I get there
  • Apr 28, 2015
    MarcG
    Yes, the "insane is more insane" bit was part of .168. Glad to see SPORT/INSANE selection is still an option!
  • Apr 28, 2015
    krisg81
    ..why would it not be?
  • Apr 28, 2015
    Stoneymonster
    Huh, I kind of liked having it optional. Sport mode can be a bit twitchy on the go pedal.
  • Apr 28, 2015
    paulwesterberg
    I agree, it was nice to turn it on for a bit, but normal was plenty for everyday commuting.
  • Apr 28, 2015
    MarcG
    Because the NORMAL/SPORT acceleration toggle was removed in the 85D as part of the .188 release. See the previous page of this thread for screenshots.
  • Apr 28, 2015
    benjiejr
    Also went to .188 - going to update tracker now
  • Apr 28, 2015
    AutoExcited
    Has anyone tested the 1/4 mile time since the update to a faster insane mode? Also, at one point, there was talk of a more responsive, faster "mid-range" 60-120 or 60-90, that was in addition to the top end update and the 0-60 update, do we know if that's still coming and if so when? Final question, has anyone tested the faster 0-60 and found it to be in the high 2's or is it just getting down into 3.0 seconds speed now?
  • Apr 28, 2015
    Garoq
    Just received the notification. Installing now.
  • Apr 28, 2015
    Torpedo Ted
    Because it makes no sense? There's absolutely no reason to have the toggle. It's purely a PR thing (incredibly successful one must say).
  • Apr 28, 2015
    brianman
    You say this with high confidence. Are there no efficiency differences between Normal and Sport (or between Sport and Insane)?
  • Apr 28, 2015
    krisg81

    Yes but after all the hype of having an "Insane" mode would make zero sense as to why they would remove it though. I get the 85D having one mode though.. But the P85D is known for the Insane mode, and taking that away would be a bad business move and also upset some customers I'm sure.
  • Apr 28, 2015
    andrewket
    .188 was installed on my P85D today at a service center.
  • Không có nhận xét nào:

    Đăng nhận xét