I installed the new version of the CETE Memory Module yesterday afternoon. I’m sad to report the Drive Select memory issues are not yet resolved. CETE did fix the problem with memory when the MMI takes a longer time to load. However, this has cleared the waters such that the bigger issue is revealed:
The CETE Memory Module only remembers the Drive Select Mode for one start/stop/start cycle.
After one start/stop/start cycle, the Drive Select reverts to the original behavior, reverting to “Auto”. Here’s how I tested this today:
- Set Drive Select to RS1 via MMI last night
- Started car today at 1:00 PM - Car is still in RS1
- Drove ~20 minutes to a dog park - shut off the car with Drive Select still set to RS1
- Spent about an hour at the dog park
- Started car - Drive Select has reverted to “Auto”
- Used MMI to set car to RS1 mode
- Drove to cleaners - about 15 minutes, in and out, about 3-5 minutes
- Restart car, still in RS1
- Drove a couple minutes to Vons parking lot and shut off car
- Sat for ~20 minutes waiting for wife
- Started car - Drive Select reverted to “Auto”
- Used MMI to set Drive Select back to RS1 again
- Drove home, about ~10 minutes
- Car is now sitting in the garage - anyone care to wager on what mode the Drive Select will be in when the car is next started? I’ll bet $100 it’ll have reverted to Auto.
The above corroborates the experience I had last night after installing the revised CETE Memory Module. The module is only able to remember the last state of the Drive Select system for one start stop signal. This failure is repeatable, it happens every time regardless of the length of time the car runs or is shut off.
As I mention above, there is a slight improvement over the previous iteration, it no longer sends the signal too quickly. That issue appears to be solved. However, the more fundamental issue, the inability to function as promised for more than one start stop cycle. I’ll bet it has something to do with how the CETE module monitors the way the car is put into a different Drive Select mode combined with how the CETE module itself sends the signal to the car. CETE already says that in order for the Drive Select mode to be remember, the mode has to be set using the console buttons, not the steering wheel button. So, based on that, it’s reasonable to conclude that different signals sent to the Drive Select system aren’t the same. Could this be the issue? Is it possible that the CETE module doesn’t recognize its own signal in the same way the steering wheel button method doesn’t trigger the memory function? If so, in this scenario, because the CETE Memory Module doesn’t recognize its own signal, and therefore doesn’t know to remember it for the 2nd and future restarts. Make sense? Kinda funny if true; the CETE doesn’t see its own signal.
The only thing the module does correctly is remember the last state of the AS/S. I turned it off right after installing it yesterday, and it has stayed off. However, as you know, that already had been solved with the fully plug and play solution sold on eBay by the Australian seller for less than half the cost of the CETE product. And no futsing with wires.
At this point I’m left wondering why I’m the one beta testing this product? I paid $225 to trouble shoot CETE’s product. CETE should be paying me for the time and effort I’ve spent doing their work for them.
So, I don’t recommend getting one of these. Unless that is, you want to become one of CETE’s unpaid beta testers. Actually, its worse than unpaid, its the opposite of paid, its a you get to pay for the privilege of testing their product. To be clear, this is not the fault of the US sellers of this product. CETE has given them a faulty product. I’m mystified as to why CETE is distributing this while claiming purchasers will never have to put their cars into their favorite drive select mode again (paraphrased from CETE’s own product page!).
Bookmarks