wstr75

I love my RLX, but if I had a magic wand I'd make the interfacing electronics feeding information to the driver programmed to operate in a continuously "ON" background state. My definition of always "ON" is to have the electronics instantly jump out of sleep state the moment I get near the car and to stay in an "All Hands On Deck" state ready to provide instant information while the car is operating be it sitting in a parking lot, in my garage or going down the road.

I am frustrated with the slowness in the system getting up to speed as I back out of the garage. Most times the camera is not live until exiting the garage. Today as I was backing out of a convenience store parking space there was no camera for approximately 2 seconds after engaging reverse. The site was crowded and I had to engage forward and reverse twice to maneuver my way to an exit opening. The camera lagged the forward-reverse-forward-reverse gear shift changes each time by about 2 seconds. With electronics, the camera and cross-traffic nannies could be live the entire time the car is energized and when the transmission selector goes into reverse, imagery would be immediately presented on the screen together with the alert nannies for cross traffic voicing their warnings, if needed.

This should be a relatively easy task for Honda's software programmers. If Honda/Acura is reading this forum, make it happen!

getakey

what year RLX? All the electronics in my 2014 PAWS was slow although I don't recall the backup camera being as slow as you describe. I know have 2017 MDX and everything is much faster. Still not as zippy as I'd like, but night and day to the 2014 RLX

justnspace

iTrader: (1)

car electronics are outdated as soon as they step off the designing board.

getakey

Agree that they are outdated. However, outdated is different than slow performance. You can have a fast performing system that lacks new features and functions. IMO, the NAVI system in the 2014 RLX should have never made it through testing. It was virtually unusable.

justnspace

iTrader: (1)

I believe the cpu or processor used is the culprit. the MDX has the same complaint.
thus what I mean by "outdated". Honda decided to use a low end processor.

getakey

I understood what you meant, but I disagree that it should have made it into the car as is. You size the processor for the requirements. Its not like the owner is adding software that over taxes the processor. Its a closed system and they knew what the functional load would be. It should have been identified as a show stopper before it ever made it into the manufacturing stage by Alpine.

justnspace

iTrader: (1)

we're on the same page, you just said it more eloquently

getakey

ok great

wstr75

I owned a 2014 RLX PAWS and now own a 2016 RLX Hybrid. In many respects the 2016 is slower with user interface information than the 2014. Part of it may be in the communications between the gear shift buttons and the central brain. Part of it may also be attributed to hybrid system as you can tell it is "thinking" before engaging reverse or forward. This "thinking" lag has got to go. Did not have any thinking lag with gear shift selection with my 2014 RLX PAWS.

This same "thinking" lag came close to killing my bride and I one night as a car popped over a hill as I had committed to forward motion. It was T intersection onto a two lane road and we were making a left turn. That one second lag put the other car (who we determined was doing about 70 mph) about 103 feet closer to collision than needed. A 300 foot sight distance to that hill got unnecessarily thrilling that rainy night. https://www.google.com/search?q=feet...hrome&ie=UTF-8

getakey

thats interesting. In my MDX Hybrid, I do not see the delay as much as you describe

wstr75

Any one know if there is a software update that corrects the lag my car is experiencing? Getakey's MDX Hybrid is not experiencing the same lag, so maybe there is a software update applicable to the RLX Hybrid.

getakey

I have a BMW that has front and rear cameras, but not 360. The thing I like about it is that the cameras stay on when you shift from reverse to drive until you go faster than 15 mph. Great for parking

fsmith

The lag in the '14 SH-AWD NAV system that bothers me the most is the time it takes to boot the system and then to have it be fully functional. Trying to set a destination immediately after the system starts up, which itself is slow, is a painstakingly slow and annoying effort. It seems to take several minutes before the NAV is reasonably responsive (reasonably responsive meaning as fast as the slow '14 system ever gets). I don't know if it is caching data or just running code, but it seems to run at about 10% speed during that time. Anyone know what it's doing during its "slow period"?

getakey

its going through the startup of all of the software
even after that the NAVI is still slow. Entering an address on the touchscreen was very frustrating. That 2014 system was just bad

wstr75

I am suggesting Acura change the programming to have the electronics immediately begin booting up the moment it senses the key fob. The time accumulated as you walk up to the car, get in, buckle the seat belt and then push the start button is likely 10 seconds and would enable the car's brain to have gotten into full motion so the user never has to wait for operational information. Cameras would be live at that point and the car would be poised to immediately go into motion upon the pressing of the gear engagement button.

getakey

The only problem with that is starting the car takes the peak battery load. In marginal battery situations, car would not start. I'm starting to think that with more and more electronics, cars should have a "House" battery separate from the starter battery, but car makers don't want to add weight.

holografique

From what I could tell when I had my RLX, the system simply suffers from lack of proper compute resources (CPU/RAM) combined with over-done (unecessary) graphics and likely poorly written software code. All leading to a huge mess. During my use, it didn't matter whether it was booting, or in full operation, it always exhibited slow performance for me. Getakey said it perfect: it should NEVER have made it into production, period. Simply no excuse for it. Someone made a bad product decision, and in the end, top paying customers were left to deal with it.

I really doubt Acura is going to do anything to correct the NAV system in any of the existing year models, let alone the 2014 year model. The way they are going to deal with it is by redesigning it completely in the next gen RLX and then want you to buy that next gen RLX...