Scala-rider Q2 with TomTom Rider v2 - pairing problems
Pairing problems. Today, I managed to solve them, somehow. I had previously been able to use the setup quite nicely. Scala-rider headsets communicating with each other, and the main headset communicating with the TomTom Rider, and the TomTom Rider paired with my Nokia 6230. Then, disaster: I made the fatal error of attempting to pair the Rider with my new Nokia E51. Not only did it cause the Rider to repeatedly display a '..connecting to phone..' message, but it also screwed up the Rider/Headset pairing. Attempting to fix the problem only compounded it, so that in the end, I had no connection with the headset at all - even after the phone was removed from the picture.
Today I managed to get the two headsets to pair with each other by a) with each headset switched on, holding down the Ctrl button for about 10 seconds until there was a red/blue flashing light sequence, and b) holding the 'volume up' button for about 5 seconds to delete all pairings. Then I managed to pair the headsets by switching on and holding down both buttons together, until I got the same red/blue flashing with both headsets, which then recognised each other and returned immediately to a slow blue flash. I then tested that we could communicate, and after success, held down the Control button on the main headset until it flashed blue and red, then went through the menus on the TomTom Rider to connect a new headset (motorcycle). I can't believe it finally worked, and I can now hear instructions over the headset. Guess I'll have to wait until I get a new phone for the phone to be available though -the E51 isn't supported, for some inexplicable reason.
PostScript: I had problems with turning on comms manually, so (on advice from Cardo) I reset the pairings by holding down control (with unit turned on) until it flashes red/blue (flashes red first, but persist, keep holding!!), then holding 'Up' audio for 5 seconds. Paired with the other Q2, but then couldn't pair with the TomTom. After about 10 'required features not found' messages, I deleted all pairings again and tried to pair first with the TomTom. Success. I'm now going to pair with the other Q2 again, as per this post at PocketGpsWorld. Halfway down there's an entry by 'Ariel Lifschitz' from CardoSystems support. He states that the order of the pairings is crucial.
By the way, it didn't fix the comms initiation problem. I still have to yell into the mike to get the comms started. Used to be able to just press 'control' and comms would stay open until I pressed it again. I'm comin' at ya again, Cardo!!!!!! AAAARRRGGGHHH!!!!
Christ, life's hard sometimes ;)
Comments
Best regards from Germany, Frankfurt
Jochen and Jasmin
Best regards from Germany, Frankfurt
Jochen and Jasmin
We're off to France in a fortnight and I was getting majorly stressed!
Thanks
Julie from Devon
In Scala's userguide, it said to enter 0000 when pin is ask. Maybe TomTom have no chance to answer back this request from Scala. (no keyboard like mobilphone!). Can someone help please? Thanks a lot.
I have been working on this problem for the importer in the UK. (Also for my own use!) I have finally cracked it and have produced an info' sheet detailing the correct sep-up procedure. It all works fine after this set-up, you don't have to shout to get the vox working and you can use PTT if you prefer. If you want a copy it is published in the FAQ's on my web-site. Hope this helps!
Best regards,
Cliff
Even with your help I'm still unable to get my Q2 Multiset to operate according to specs provided in their advertising and Manual.
Initial attempts to pair a Tomtom Rider Q2 2nd edition using the manual's instructions (p6) failed. After repeated attempts from which I ended up with a pairing with the Tomtom and only an MC-button activated pairing (ie, no voice pairing despite having followed directions to reset Voice Connec Intercom preference to Primary and to ensure that Voice Connect was on (p10), I chose to reset all pairings (p5/6).
This too appeared to fail as I still had a pairing with the GPS. I repeated the process, with the same results.
Then I followed your link to Ariel Lifschitz, from Cardo Systems Support Center stating that the TTR2 had to be paired FIRST. I did that and then set up a Primary Pairing between the headsets, rechecked prefrerences and VC setting, but still cannot achieve Voice Connect activation.
My status right now is that I have Primary Buddy connection between the headsets and a connection from the rider's headset to the Tomtom, BUT I have no voice activation and must tap the MC button to initiate a conversation with my passenger AND I lose the connection with my passenger when the GPS cuts in with a command, and am required to reinitialise headset to headset connection via the MC button.
I'm frustrated and disappointed (more at the lack of simple set up than at the end functionality).
I've asked Cardo support for clear and concise instructions that enable me to restore Primary Buddy connection between the headsets WITH Voice Connect activation SO THAT it persists or re-connects to my passenger after a GPS instruction to the rider's headset.
The MP3 connection works as one would expect of a straight-through connection, though it would be a useful safety enhancement to be able to control MP3 volume from the headset to take advantage of Gain Control and avoid reaching for an MP3 player while under way, or having to stop to safely adjust volume (which is a bit hard to judge in the absence of ambient road noise present).
Thanks for shedding some light in a corner that should be floodlit by the Cardo as the manufacturers.
Any suggestions? Thank you.
By the way, I had both my headsets out of commission for about 6 months due to misplacing the battery charger. When I finally found the charger and went for a ride, they worked perfectly - the earlier difficulties with initiating comms seem to have fixed themselves. I can only guess that by completely discharging the batteries, all settings were somehow reset - I even had to go through the pairing process with the TomTom Rider v2, and it worked perfectly first time. I was cringeing as I waited for the ominous 'Required features not found' error, but it never appeared.
rH3uYcBX
This is a inquiry for the webmaster/admin here at blog.meteoroz.com.
Can I use some of the information from this post right above if I provide a link back to your site?
Thanks,
James