One XL series

This is probably a silly question, but I've seen people talk about problems with the ONE series or problems with the XL series, so is my ONE XLS considered in the ONE series or the XL series?

Blump3345 wrote:This is probably a silly question, but I've seen people talk about problems with the ONE series or problems with the XL series, so is my ONE XLS considered in the ONE series or the XL series?

It's in the ONE XL series. What are you trying to do?

tendriver wrote:It's in the ONE XL series. What are you trying to do?

I was trying to update it with a newer NC, but after several tries with different NCs, I couldn't get the RDS traffic receiver to work (whole unit freezes up after a few seconds) and the computer voices to work, so I just gave up. With different NCs, I could get one or the other to work, but not both at the same time. I mentioned these in other posts a while ago.
But when I see people say something works with the ONE series or they say they have problems with the XL series, I wonder which group mine fell into. I'm not looking at anything particular, just curious.

Blump3345 wrote:I was trying to update it with a newer NC, but after several tries with different NCs, I couldn't get the RDS traffic receiver to work (whole unit freezes up after a few seconds) and the computer voices to work, so I just gave up. With different NCs, I could get one or the other to work, but not both at the same time. I mentioned these in other posts a while ago.
But when I see people say something works with the ONE series or they say they have problems with the XL series, I wonder which group mine fell into. I'm not looking at anything particular, just curious.

As a reminder, Most of the SE navcore downloads are defaulted to X40. The RDS traffic receiver needs X30 or lower.

tendriver wrote:As a reminder, Most of the SE navcore downloads are defaulted to X40. The RDS traffic receiver needs X30 or lower.

OK, thanks, maybe I'll give it another shot. Am I any better off making my own DSA NC or using a pre-made SE NC?

Blump3345 wrote:OK, thanks, maybe I'll give it another shot. Am I any better off making my own DSA NC or using a pre-made SE NC?

Run this: TomTom Current Configuration {29.09.2011} Post the results here.

tendriver wrote:Run this: TomTom Current Configuration {29.09.2011} Post the results here.

Results (I know there are newer maps):
TTGO.BIF:
DeviceName=TomTom ONE XL
DeviceVersionHW=ONE XL
BootLoaderVersion=55250
ApplicationVersionVersionNumber=8010
ApplicationVersion=9369
CurrentMap=USA_and_Canada
CurrentMapVersion=880.3867
TTNAVIGATOR.BIF:
TTGO.BAK:
Not Found...
TTGO.ORI:
Not Found...

Blump3345 wrote:Am I any better off making my own DSA NC or using a pre-made SE NC?

Go the SE route. DSA adds a bunch of junk that takes up to much storage space.

Hmm, the bunch of junk is only the added Linux tools, which is only a few KB.
The rest is basically the same you would get for an SE in the outsourced folder, except that they files are always present.
Since it makes no difference if the files are still inside the ttsystem or extracted into a folder (ecept for sving Ram and for not needed stuff) I don't really know what you call "much storage space" ...
But I agree that a SE might be the easier way for an unexperienced user.