Results 1 to 10 of 29
8th March 2016, 03:18 AM #1TomTom Master
Join Date : May 2012Location : At homePosts : 1,497Thanks: 2,672
- 6,235 PostsRep Power : 15Reputation : (2840)
Calibrating screen Tomtom
Thanks to this tool DSUser teacher has never been easier to calibrate our GPS screen.
[Login or Register to remove this advertisement]
Download and get a compressed file, unzip it and you get this:
The teacher has already included a text in Spanish explaining how to proceed. (intrucciones.txt)
In this tutorial I will explain how I've done to me, and as I proceeded if it helps you, although it is very simple.
After having unzipped the first thing we do prepare files tool in our screen. In this example we work on a gps square 4: 3 screen (small screen).
Calib folder must eliminate the calibG file that is for large screens and retain the calibP.
The calibP file rename it by removing the "P" leaving the name as calib
The folder is displayed like this:
In the event that our screen is large (16: 9) we have to leave the calibG as calib file renaming, and deleting the file calibP
This step is very important because it is the base of the tool.
We have prepared files, copy the two folders to the root of GPS (calib and SdkRegistry). If you already have a folder sdkregistry, they are combined with one another. Remember to back up your sdkregistry folder in the GPS before making any changes.
With folders on the GPS disconnect the pc gps, safely and start it. We will see in the menu that has made us an icon called calibration. If you do not see the icon on your gps may be because you have 10 things in sdkregistry and GPS menu you are only capable of displaying 10 things. This happened to me and what I did is delete files x50 emulation of this NavCore.
If you click on the icon Calibrating the GPS shows us a screen similar to this:
We must press where the cross, which will be moving across the screen in all four corners and finally in the center is: Try to touch as centered on the cross, to take the coordinates well.
The application will create a text file named "cal", which will contain four numbers separated by a space, these numbers are the coordinates of the axes of your screen. In case you do not like as has been centered screen, delete the text file "cal" and can repeat the operation.
Sorry for the translationOrni Reviewed by Orni on . Calibrating screen Tomtom Thanks to this tool DSUser teacher has never been easier to calibrate our GPS screen. Download link: MEGA (https://mega.nz/#%21eU92GLJa%211QeZgKWOmoMW9ZuyEIpWzOFI6POF_QhwaGLEvcynKOk) Download and get a compressed file, unzip it and you get this: Rating: 5
The Following 13 Users Say Thank You to Orni For This Useful Post:
- [ Click To Expand ]
Alfred_ML (8th March 2016), baeta (9th March 2016), biggerdave (8th March 2016), elgayoleon (8th March 2016), Gat67 (21st August 2016), Jolly-Joker (8th March 2016), neskiuck (17th February 2017), OneLover (2nd July 2018), pepepepote (23rd April 2016), Punchinelo (9th March 2016), Schwan (30th March 2018), zebandido (18th August 2016), zinom (28th March 2018)
30th March 2018, 05:05 AM #2Join Date : Apr 2015Location : PortugalPosts : 7Thanks: 12
- 1 PostRep Power : 15Reputation : (10)
Some extra info i've found about touch calibration. I have a TomTom One XL and had problems with touch calibration. thanks to you and a little more info, i solved my problem. Hope this can help many people.
An adjustment can be made by placing a file called cal.txt in the root directory of your TOMTOM. All firmware versions since 8.051 require the sequence in this order:
MaxX MinX MaxY MinY
(where X = left/right and Y = up/down)
For Left/Right calibration:
MaxX affects the LEFT edge of the screen
Increase MaxX - touch point moves to the RIGHT of where you touched
Decrease MaxX - touch point moves to the LEFT of where you touched
MinX affects the RIGHT edge of the screen
Increase MinX - touch point moves to the RIGHT of where you touched
Decrease MinX - touch point moves to the LEFT of where you touched
For the Y axis, the process is the same only in the up/down axis.
I had this same problem with my old GO 740 and had to make some adjustment to access the bottom areas of the screen. My file looks like this:
926 77 830 200
If you press and hold the reset button in the bottom of your unit briefly and or Now, press and hold the power button until the screen appears with white text on black background, then you can release the button. You will see a line on the screen that looks like this:
Touchscreen calib. data: 76 932 140 861
BEWARE! On THAT screen, the data is MinX MaxX MinY MaxY. Don't use that order when you create your cal.txt file! Anyway, this shows you where the unit calibration is by default if there is not any cal.txt file to change it., so you use this as a starting point for your adjustment. If your screen showed the numbers above, that would the same as if you had created the cal.txt file that looked like this: 932 76 861 140
You should create the file with Notepad or another very basic text editor that will allow you to create the file as BARE text and does not require line break at the end of lines.
TO USE APP Calib you shouoldnt create file cal.txt, because it will append the exist data in cal.txt file, so you have to calibrate and then see if cal.txt exists with new info, different from the one in tomtom boot info. If you create an empty cal.txt file and start your tomtom, you cant use touch because it has no data, so if you create it, you have to put the coordinates inside.
If you have some problem with touch just start reboot tomtom with USB cable attached to it and PC to explore its internal storage if its the case.
29th June 2018, 12:31 PM #3Administrator
On the Dutch TomTom page, EOL system
But the SdkRegistry is quite interesting to test it on for instance my Rider v2 which have also
a small menu like above
29th June 2018, 12:38 PM #4Join Date : Sep 2014Location : GermanyPosts : 594Thanks: 2,117
- 783 PostsRep Power : 15Reputation : (164)
TomTom and their statements. Luckily, they don't always keep to it . So you don't get any services for EOL-devices like new maps, but always the last current NC (at the moment).
Make a try with one of the addons.
29th June 2018, 07:15 PM #5
Yesterday after the installation of 9.510 via TTHome I just tested the sound. Today I pushed the tests further and noticed that when I use the keyboard to enter an address, the letter displayed is the letter to the right of the selected one. For example with keyboard QWERTY: you tap on W and it is E displayed. So it is not possible to select the first letters to the right of the keyboard "Q", "A", "'", "123".
Also, from time to time the display jumps from one menu to another.
Thank you very much Alfred_ML for your menu extension, that I am quick to use and returns to you my first impression.
First, it gives access to a larger menu with more options and very reactive.
Regarding TomTom Services, I know they are not available for EOL devices. But when
By selecting Plan Route (Page 2) menu, there is option Traffic, If we could replace it by Radar or add an extra option Radar, it would be perfect.
Finally, I mix the 2 SdkRegistry of this menu extension and that of 9.510 downunder and added the folder skins of downunder. Indeed, I wanted to calibrate my screen with ts_calibrate in the folder skins of Downunder and also enjoy its skins options. Without success.
Is there a way to calibrate the screen? Especially to solve my keyboard problem (see above)?
29th June 2018, 08:14 PM #6Administrator
If I understand correctly now, you are further away from a solution than ever before.
What do you expect now of this GO 720?
The sound must be restored as first
The sound worked well with your previous software
Previously read nothing about that the keyboard would not work properly.
It is not to be hoped that the wrong data is now in the calib file
There is a calibration description available, so that is basically no problem
Now the speedcams and radars, which are just to pick up here via Maeverick twice a week.
You do not need a special menu button for that than there are already.
It is simply a matter of making those places (POI) visible on your screen and there is already a menu button for, remains there to a sound to it, some have to have a patch, but that is automatically done by Fastactivate.via the meta.txt list.
Again the question, the internal memory is now empty so that only one of them SDHC card can be worked?
Hang on for the calibration, please.
29th June 2018, 08:17 PM #7Administrator
So, your TT does no longer give you an "a" when you enter an address or you have to press on weird spots in the menu to select something?
It usually means your digitser for the screen is partially faulty but you might be able to "fix" it without buying a new one.
All current Navcore can use a texfile "cal.txt", located in the root of the device to override the default calibration of the digitiser.
I will base my instruction on that and not on the cilb.txt for older Navcores (little bit different).
Ok, how do I know the values for the cal.txt?
Start your TT (best after a reset) and when the drums start press and hold the power button - this will show you the Linux status screen with all hardware related info.
Row 4 from the top shows your current bootloader, row 4 from the bottom shows the original calibration data of the digitiser.
Only the first values are of interest, the rest shows the voltage for the digitiser.
As an example from my device:
93 921 147 840
The values are:
93 = min X
921 = max X
147 = min Y
840 = max Y
One word of advise: the values inside the cal.txt are in a different order!
The sequence of the cal.txt is : Max X Min X Max Y Min Y
That means the 93 921 147 840 on the status screen translate to 921 93 840 147 inside the cal.txt!
With those values the will react exactly the same way as without the cal.txt present, if that is not the case check the values and the place again.
Keep in mind this is only an example and you have to use the values as shown on your status screen!
Normal touchscreens use a co-ordinate system and a point calibration, TT prefers to calibrate the start and end of the X- and Y- axis, so be prepared for a lot of reboots and changes inside the cal.txt!
I only describe how to calibrate the Y-axis, procedure is identical for the X- axis.
As by my example start changing the mx Y value.
If you lower the value the reaction on the screen should go down, if you increase the value the reaction should go more to the top of the screen.
Change the value by about 50, save the cal.txt in the root of your device and boot the TT.
You should notice a little difference already.
Try to remember by how much it has changed to get an estimate on how much further you need to change this value only.
Once you reach a point were you think it feel ok start the address input with the big keyboard for the finetuning.
Hint: If you notice after the changing the max value there is barely any change adjust it by about 200 and try again, if still no real change use the min value to start the calibration.
You now change both the min and the max value to get the most accurate result, using a touchpen is a good idea.
Only minor changes in the values should made at this stage and only one value at a time, otherwise you might end up messing around.
The final check should confirm the menu buttons work fine, all characters and numbers in the screen keyboard are assigned correctly and the zoom buttons in the map screen are working.
Don't be too disapointed to notice the keyboard works but the zoom buttons don't - they are very small and in the corners so only a perfect calibration will get them back working.
In case the input is off in both axes you should still start with the Y section to get the height correct before adjusting the x axis.
Changing both at the same time makes it really hard to figure out what change caused the reaction on the screen.
I hope this will to get your TT going again.
As a real world example:
The Y axis on tendriver's X20 was out of calibration & had to be lowered. The original Y values, on the Linux status screen, were: 134 856. After re-calibrating the Y axis back into alignment, the new Y axis values were 460 50. These new values were entered into the cal.txt file.
Keep in mind this is only an example, and you have to use the values as shown on your status screen!
29th June 2018, 08:26 PM #8Administrator
Here is some more interesting information:
What is the correct Navcore and map for your device
Even though we provide the tutorials and map charts it seems to be hard for noobs to determine what to choose.
I will now try to explain the right way:
1. The best Navcore is always what Home offers as latest official update!
All other Navcores can work but there are no guarantees!
2. We always provide the latest maps in our red stickies, so instead of asking simply check the dates of the postings in the map thread.
Map versions always go up by 5 in the first digits. 895.xxx, 900.xxx, 905.xxxx and so on - every 3 months a new round....
Some maps increase only by one like 901.xxxx, this indicates the map was updated by TT due to major errors.
3. For a downloaded map to work the Navcore needs to be patched and the map activated - you can confirm the later by checking for a .dct file inside the map folder that corresponds to the map name.
With that out of the way, how do you choose the right map?
You need to know the Navcore version number, you can check the info in the menu for that or the contents of the file ttgo.bif.
You also need to know what coverage you need. There are single country maps and especially for Europe the different versions that cover parts of the continent.
To check what map version is current and the coverage as well, you should use the TT website and visit the map shop.
Don't worry, you don't have to buy a map, before you reach that point TT shows you what map is available for your device and the current version number of the map.
With that knowledge you check our map thread.
Scroll down to the map you need and check if there is a meta code posted with the download link - without the meta code the map is not usable!!
If there is no code you either need to wait or use a different map - check the map chart what map version is suited for your Navcore.
In case your version (of the Navcore) is not in the chart the next lower number in the chart tells you what you need.
So much for the maps used on official Navcore versions, now how to use the latest full featured maps with Navcore versions higher than your offical Navcore number.
As said at the beginning, there is no guarantee an onoffical Navcore will work as expected, but we do our best to make the impossible possible
One word in advance: The latest available Navcore version is not always the best the choice!
Devices considered to be compatible with basically any Navcore have the following features:
Screen resolution of 480x272
64mb of Ram
All other devices have to accept certain limitations.
I already said that a Navcore needs to be patched if you use our maps,
for unofficial Navcores it also means you need to use modified files.
I provide Navcores that are already patched suited for most devices, you can also use the so called SE versions, but they need to be manually adjusted, check the Switchfiles thread in the tutorials.
Those unofficial Navcores should be selected so the suit your needs.
This means selecting an older version can sometimes be of benefit, especially for old 32mb devices.
Be aware that from NC 9.02xx on all map features are supported, so if you already use a Navcore version in that range there is no real need to go higher.
The main difference between the various V9 Navcores is the official support for devices and of course bug bixes (for versions in the same range).
There are some other minor things like "improved route calculating speeds", changes for speed cam handling (especially for France) but they are more or less cosmetic.
If you want to use V9 Navcores on an oldie be aware that sometimes you have to use a different Navcore in case the one you selected won't work at all.
This is a known problem and must be accepted as we not always get what we want in life
Addon: problems after updating
If you follow the above you should not get any problems
But I try to list the most common causes:
You did not use the latest version of FastActivate - always double check if the version you have really is current!
You downloaded a map with no available meta code - check for the meta code before you download a map, especially if you select a map with installer!!
Your Navcore is not patched - if you can confirm FastActivate created a .dct file for your map and you also used it to patch your Navcore, it is possible the patching did go wrong.
In that case try the patching again, if necessary use a different tool, best choice: original yDG patcher for DOS.
If in doubt, before you post for help, do a clean install of map and Navcore.
That means installing all from scratch on an empty device - make a backup using Windows Explorer first, confirm hidden and system files are shown.
29th June 2018, 10:50 PM #9
I must thank you for the trouble I give you to help me and for all the time you spend with me.
First, I'm going to make order in this thread.
I have 3 devices:
TT XL 30 1GB (32 MB Ram): Works very well under NC 9.401 (Max Ram on small devices 2012) + latest map France and Israel v1010 +Sppedcam (patched FastActivate). Also, the main menu is expanded with all options (TomTom Services included) +Sppedcam
GO 720 (64 MB Ram): Works great under NC 9.510 (Downunder) + latest map France and Israel v1010 +Sppedcam (patched FastActivate). Also, the main menu is expanded with all options (TomTom Services included) +Sppedcam
TT XL IQ 2 GB (64 MB Ram): this is the one of this thread. NC 9.510 (TTHome) + latest map France and Israel v1010 +Sppedcam (patched FastActivate). Also, the main menu is extended thanks to Alfred but no TomTom Services, calibration problem.
I created the cal.txt file with the data
218 821 328 666
218 min X
821 max X
328 min Y
cal.txt in the root
Tested same offset: tap on W and it is E displayed.
Is there a tool to automatically calibrate the screen like ts_calibrate in the folder skins of Downunder?
P.S. I have to go to my grandchildren, I will come back Sunday
29th June 2018, 11:09 PM #10Administrator
I'm rather sure I don't have such a tool
Have a great time with your grandschildren