Switchfiles for dummies
Sun May 16, 2010 5:03 pm
Thread Courtesy of Downunder35m
Ever wondered how to configure the "switchfiles" and what all the setting mean?
Well ,I'll try to explain it here...
With a SE Navcore you can use the switchfiles to emulate different devices - meaning that a cheap x10 unit can get the look and feel of the biggest x40 unit.
To use the switchfiles you need a folder "config" in the root of your device.
Within this folder you can have 4 files :
model.txt
setconfig.txt
version.txt
cycle.txt
Setconfig.txt is the most important one.
The following "switches" are possible :
model:x30
runclean
viewmsg
sdid:1
runcheck
changedtext:You can type whatever you like
delgns
delmap
ttsoff
btoff
bton
fmon
fmoff
rm
nomsg
usesetting
cleanflash
noqfixdel
Please note : only use one switch for a function!!! E.g.: bton or btoff -never both as in the unmodified setconfig.txt
model: you can use ori,xls,x20,x30,x40,x40light(TTS working on ONE3rd),x40light2,x40light3,ttssdk -ori is for your original device and the x40light switches for the devices without BT or FM
runclean deletes not needed files like the sirf data for gl devices and vice versa
viewmsg displays boothelpmessages (run insave ram mode, x30 emu etc.)
sdid:1 only needed if you use different Navcores on several SD cards to make sure you keep your settings you need a "SDid.txt" with a corresponding number on each SD card
runcheck checks once some data and writes the result into "config.txt"
changedtext:You can type whatever you like
delgns deletes TMC-data - only useful if you really use TMC
delmap deletes "currentmap.dat" so that you can choose a map each time you start
ttsoff to deactivate TTS on devices without TTS function because the standard is "on"
btoff deactivates Bluetooth
bton to activate menufunctions like "Safety cams" - won't activate BT on device without the hardware!!
fmon necessary on some x10 devices and to enable the MP3 player(Jukebox) functions on some devices
fmoff turns the FM transmitter off
rm to delete some more files that are not needed in the current emulation
nomsg disables boot messages completely
usesetting same as sdid
cleanflash deletes the flash and therefore all settings are lost
noqfixdel only for devices with GL chip : on reset the quickfix data will be deleted ,and this setting prevents it - useless for SIRF chips
The "model.txt" is only used to override the model entry in the setconfig.txt - therefore it can be deleted except you use the cycle.txt,than the device switches between the settings of these two files after each reset.
Settings for the "version.txt" :
[color=#222222]TomTom GO, GO x00, GO x10, ONE 1st Edition, ONE 2nd Edition
A:7903
B:9183
Rider
A:7901
B:9181
Some ONE 30-Series, XL 30-Series, ONE XL, ONE 3rd Edition
A:8010
B:9369
[/color]
[color=#222222] XL Live 2009
A:8419
B:1257
[/color]
[color=#222222] Start
A:8544
B:1836
x20,x30,630
A:8351
B:9982
X40
A:9054
B:531676.2
[/color]But your device should work just fine without a version.txt.
I hope that helps to understand the emulations and settings for SE Navcores....
Ever wondered how to configure the "switchfiles" and what all the setting mean?
Well ,I'll try to explain it here...
With a SE Navcore you can use the switchfiles to emulate different devices - meaning that a cheap x10 unit can get the look and feel of the biggest x40 unit.
To use the switchfiles you need a folder "config" in the root of your device.
Within this folder you can have 4 files :
model.txt
setconfig.txt
version.txt
cycle.txt
Setconfig.txt is the most important one.
The following "switches" are possible :
model:x30
runclean
viewmsg
sdid:1
runcheck
changedtext:You can type whatever you like
delgns
delmap
ttsoff
btoff
bton
fmon
fmoff
rm
nomsg
usesetting
cleanflash
noqfixdel
Please note : only use one switch for a function!!! E.g.: bton or btoff -never both as in the unmodified setconfig.txt
model: you can use ori,xls,x20,x30,x40,x40light(TTS working on ONE3rd),x40light2,x40light3,ttssdk -ori is for your original device and the x40light switches for the devices without BT or FM
runclean deletes not needed files like the sirf data for gl devices and vice versa
viewmsg displays boothelpmessages (run insave ram mode, x30 emu etc.)
sdid:1 only needed if you use different Navcores on several SD cards to make sure you keep your settings you need a "SDid.txt" with a corresponding number on each SD card
runcheck checks once some data and writes the result into "config.txt"
changedtext:You can type whatever you like
delgns deletes TMC-data - only useful if you really use TMC
delmap deletes "currentmap.dat" so that you can choose a map each time you start
ttsoff to deactivate TTS on devices without TTS function because the standard is "on"
btoff deactivates Bluetooth
bton to activate menufunctions like "Safety cams" - won't activate BT on device without the hardware!!
fmon necessary on some x10 devices and to enable the MP3 player(Jukebox) functions on some devices
fmoff turns the FM transmitter off
rm to delete some more files that are not needed in the current emulation
nomsg disables boot messages completely
usesetting same as sdid
cleanflash deletes the flash and therefore all settings are lost
noqfixdel only for devices with GL chip : on reset the quickfix data will be deleted ,and this setting prevents it - useless for SIRF chips
The "model.txt" is only used to override the model entry in the setconfig.txt - therefore it can be deleted except you use the cycle.txt,than the device switches between the settings of these two files after each reset.
Settings for the "version.txt" :
[color=#222222]TomTom GO, GO x00, GO x10, ONE 1st Edition, ONE 2nd Edition
A:7903
B:9183
Rider
A:7901
B:9181
Some ONE 30-Series, XL 30-Series, ONE XL, ONE 3rd Edition
A:8010
B:9369
[/color]
[color=#222222] XL Live 2009
A:8419
B:1257
[/color]
[color=#222222] Start
A:8544
B:1836
x20,x30,630
A:8351
B:9982
X40
A:9054
B:531676.2
[/color]But your device should work just fine without a version.txt.
I hope that helps to understand the emulations and settings for SE Navcores....