SAP Bluetooth cradle

[whitenemesis]

Have been trying this out, and seems that the connecton time after leaving the car is pretty hit and miss - sometimes almost immediately, and sometimes several minutes (10+). I don't have the runon time contact name listed in the phonebook.
I have tried leaving the phone in range and not in range, didn't seem to make a difference to th phone coming out of remote sim mode on it's own.

You have to create the contact yourself!

 

[pos.k]

what I meant was, that even without the contact created, the disconnection period seemed...flakey!

 

[whitenemesis]

what I meant was, that even without the contact created, the disconnection period seemed...flakey!

Ah! I see, sorry

I wonder if we are confusing two seperate events?

The Run-on Time works on the COMAND and sets the time the COAMND maintains telephone functionality after the unit is switched off.

Does the SAP module have a seperate delay timer? I notice the SAP module is operational (i.e. the blue leds are on and flash when the phone is within range) even when the COMAND is off

 

[pos.k]

my original query on this was without COMAND fitted as I had the audio 20 until saturday, and the delay seemed variable and extended. Since fitting the comand unit, this has still been variable and unpedictable,
needs some documenting and testing methinks!

 

[whitenemesis]

Mercedes, don't you just love 'em?

 

[amwebby]

It would be nice if you could repeat the "lost BT connection" test a couple of times.

I have repeated this several times, at different run-on tiimes, as I said in my earlier post. All those tests have been within range of the Peiker BT device, which may distort the results, which is why I am going to condcut further tests moving the phone out or range of the BT unit. Is this what you mean?

 

[Diesel Benz]

I have repeated this several times, at different run-on tiimes, as I said in my earlier post. All those tests have been within range of the Peiker BT device, which may distort the results, which is why I am going to condcut further tests moving the phone out or range of the BT unit. Is this what you mean?

Sorry I was not clear, yes I mean more testing when the phone is out of the range of the BT unit. Your tests within the range clearly show that the run-on timer works for you, which I envy.

But I was wondering about the case you described earlier where the phone was left to BT SAP mode for a long time even if it had lost connection to the car. According to my experience this should not happen (unless the phone gets somehow confused).

 

[Diesel Benz]

my original query on this was without COMAND fitted as I had the audio 20 until saturday, and the delay seemed variable and extended. Since fitting the comand unit, this has still been variable and unpedictable,
needs some documenting and testing methinks!

Sorry but I got a bit lost when we took the thread out of the original context, do you mean the time for the phone to disconnect when it is close to the car within the BT range and the car doors closed and locked after a drive?

I have not been testing this but it could be from variations on the time the car goes to sleep, the phone system possibly affecting this. I only did one test myself and even there could not figure out the exact time (between 12 and 25 minutes). It could well be different on your car and in any case I would not consider it being any fault if the "time to sleep" varies and if it becomes different with Comand installed (just guessing though).

 

[whitenemesis]

Sorry I was not clear, yes I mean more testing when the phone is out of the range of the BT unit. Your tests within the range clearly show that the run-on timer works for you, which I envy.

But I was wondering about the case you described earlier where the phone was left to BT SAP mode for a long time even if it had lost connection to the car. According to my experience this should not happen (unless the phone gets somehow confused).

This isn't something I have experienced. Once the phone is out of range of the BT it reverts to normal operation. If I move back into range the car will again capture the phone and remote SIM activated.

If the car is locked this has to be within the Run-on time, if unlocked (e.g. I'm cleaning it) this can happen any time.

 

[Diesel Benz]

This isn't something I have experienced. Once the phone is out of range of the BT it reverts to normal operation. If I move back into range the car will again capture the phone and remote SIM activated.

If the car is locked this has to be within the Run-on time, if unlocked (e.g. I'm cleaning it) this can happen any time.

OK, fine, I must have misunderstood an earlier post from yourself or then it was from someone else. This is good, then I think my experience aligns very well with yours excluding the non-support of the Run-on time on my Comand (unless someone is able to explain how that can be made working on a W221).

 

[whitenemesis]

This isn't something I have experienced. Once the phone is out of range of the BT it reverts to normal operation. If I move back into range the car will again capture the phone and remote SIM activated.

If the car is locked this has to be within the Run-on time, if unlocked (e.g. I'm cleaning it) this can happen any time.

But what's frustrating is that if the ignition is not on or in position 1, any calls will be "missed"

 

[amwebby]

Sorry I was not clear, yes I mean more testing when the phone is out of the range of the BT unit. Your tests within the range clearly show that the run-on timer works for you, which I envy.

But I was wondering about the case you described earlier where the phone was left to BT SAP mode for a long time even if it had lost connection to the car. According to my experience this should not happen (unless the phone gets somehow confused).

OK, we're on the same page then. This has only happened to me twice, once was the supermarket incident and I suppose it is possible the call was made as I left the car but before I was out of range.

On another occasion my experience is the same as whitenemesis, the call was lost. That is to say there was no message and no record of the call, I only discovered it when the other party phoned me back.

 

[whitenemesis]

If a call is in progress (or instigated) before the Run-on time ends the shutdown will be delayed until the call is ended, then the timer starts.

COMAND will not shutdown until active calls are finished, if you are quick you can delay the shutdown indefinately by keep making calls!

 

[amwebby]

I was taking that as a given, but hinking about it, that is why my call received while I was in the supermarket carried on (i.e the chap leaving me a mesage) when I was out of range. It had been instigated when I was in range and the car owned the SIM connection.

What I and DiselBenz are intrigued by is the hand back of the SIM to the phone. It is axiomatic that, when the BT SAP connection drops the phone will grab the SIM back. What is not so clear is the intervals between the SAP BT device renewing its authorisation to use the SIM and if it is possible for there to be an overlap. Even if there is, once a call is placed the device with the strongest authority, i.e the phone, should take over, forcing the other one to drop. That's the theory anyway.