2210 & BlueTooth Connection

[Commander]

Like many others I had problems with TT3 dropping the BT connection from the TT GPS to my 2210, so much so that I reverted to TT2.

Whilst there seems no doubt that TT V 3.04 fixes the lookup problem (Many thanks to DavidW for his comprehensive open letter) the jury still seems to be out as to whether it fixes the BT problem, with postings going both ways. Are we hearing from a disproportionate number of people for whom it does not work, with many of those for whom it clears up the fault keeping quiet?

I want to give TT3 another go now and would appreciate some guidance as to how I should set up my 2210.

There seems little doubt, as I understand it, that the programme goes in main memory with the maps (GB & MROE) on a storage card; but given that I have both a 256MB SD and a 256MB CF card available, which slot should I use? I know that there are issues with SD cards.

The details of my cards are as follows:-

SD

Front:- Viking Interworks A03223094
Back:_ SD M256 B1 0417 TJ3448 H Made in Japan

Can anyone (DavidW) tell the manufacturer and advise if this is good, bad or indifferent. How can I tell the speed of the card?

CF
Front:- Viking Interworks 256MB
Back:- A02460380

When connected to my card reader it shows up as TOSHIBA 256MB

As I have no CF devices to use in the slot, I have no pressing reason for favouring one or the other. My overriding requirement is for a stable system so I will use whichever card the collective wisdom of Pocket GPS World recommends. A small point is that I use my Ipaq a lot for listening to recorded radio programmes (recorded using the highly recommended Replay Radio www.replay-radio.com ) and I find it quicker & easier to remove the SD card rather than the CF card to put it into the card reader to upload new material.

Thanks in advance for your help.

Peter

[DavidW]

The jury is certainly still out as to the stability of Navigator 3.03 / 3.04T - my impression is that it's causing less problems for people than 3.01 / 3.02T did, especially when teamed with GPS 3.03, though it may not yet be perfect.

I've been away for a couple of weeks, and reading through the various posts on the subject is interesting, to say the least.


Certainly it seems that the 'open letter' helped TomTom work out what needed attention.


I can't identify the manufacturer of your SD card, save to say that, to my knowledge, the code is not a Sandisk code, so it shouldn't be a faulty card. Toshiba and Panasonic seem to produce the best performing SD cards (Panasonic having a slight edge on Toshiba), and I don't recognise the code as being from either of those manufacturers. That means, most likely, it's a reliable card that may not have absolutely top end performance, but is, I hope, stable (either that, or a manufacturer I thought I could identify reliably has changed their codes!).


I think your other comments sort this out nicely. CompactFlash memory is almost invariably better performing than SD - so it seems to make sense to put your TomTom maps on your CompactFlash card, and use the SD card for radio programmes (which fits nicely with your comment about it being easier to move that card between your Pocket PC and card reader).



David

[Commander]

Thanks for the reply David, I had noticed that you hadn't been around and was hoping that it was not due to ill health.

It would have been nice to have been told that my SD cards were Panasonic, however they are working well.

For the record and in case it might help someone else, I have used the following setup for the last three weeks
iPAQ 2210 Rom 1.10 TTN 3.03 GPS3.03 Prog in main memory, maps & POI on CF card. CheckPOInt 3.02 in main memory.

It has, overall, proved very stable. I have used it every day and only had two lockup, both were where motorways join and I wonder if they might be mapping errors. One M6/M62, the other M25 anticlockwise joining M1.

The other observation is that on a number of occasions (8ish I guess), it has dropped all satalite info "Position Unreliable", only to regain it all instantly. I have no explanation for this.

Peter

We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?.
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!