Multiple Escort Passport 9500ix/ci Truelock data sharing

[STiMULi]

Today I got my second 9500ix and let me tell you I am happier than a pig in doo doo.

Now I can point one at the front of the car and one at the back of car. It will be almost like having Arrows!!! (If you believe any of the garbage in the previous sentence you deserve what you get)

In real life it is because I have two vehicles driven in different manners and I don't want to keep moving them around for the wear and tear factor. I do hide one of them but the other one is in a vehicle that has many devices in that will already attract thieves and I am cautious about where it is parked and it's generally secure

Anyway the point of this post is to discuss the merging of Truelock data.

I have already figured out that the data from one device can be shared with the other. I wanted to do this because I have chosen to do the manual learn rather than the AutoLearn function and I did not want to have to do the same learns again if I could avoid it.

Doing so got me to thinking that users in a particular area could share this data.

For instance a new 9500ix could be used in a given area for a period of time allowing only autolearn data to be saved. This could be the baseline from which other new users in the same area could start their marking and muting.

Over time, as we tend to trust each other, we could share this data with local users. Because this data contains information that the user adds it could become very useful in noting the hiding places of LEOs in that particular area.

Too bad that we could not use mapping as I have suggested in another thread but if we are cautious we could define a pretty good baseline for Hideouts.

If anyone knows of a way that this data can be interpreted in any other manner please let us know in the thread or PM me.

Merging the data is an aspect that I am not yet sure of how we would do yet. Perhaps we could discuss the logic here.

(ANYONE IN THE SOUTHERN ARIZONA AREA WANT TO TRY THIS WITH ME? LET ME KNOW VIA PM)

What do you guys think?

[rocky2]

It would be cool if we could merge all the files together from all over the country into one big file. Then you would have the lockouts and speedtrap locations for the whole country.

[Cips]

It would be cool if we could merge all the files together from all over the country into one big file. Then you would have the lockouts and speedtrap locations for the whole country.

I had said that a good while back and members mentioned it would never happen. 'What if LEO's sabotage the database?' is what I got in response. But this would be tremendously helpful to those that rravel a lot and don't want to be annoyed by the 'false alerts.' That's why they bought a 9500 series RD, isn't it?

[voyager7]

Good idea.
like Cips said you would have to trust the other person that he or she was not messing with the data they sent you.

[CJR238]

Cool idea, but i wouldn't necessarily trust what others lock out or mark . To share data like this the one sharing really needs to know what they are doing.

If there was mapping so a new user could see what he/she is getting, then maybe.

For me knowing/remembering the general places where lock outs are is very important, but marked locations from others would be nice. It may be different for different people.

[STiMULi]

The trust factor would be a biggie. It would be THE BIGGIE.

There are people on this forum that I know are from (my) town and they may be willing to trust my efforts.

I am guessing that one file type could be an AutoLearn filetype, meaning all data would be obtained only through that manner and then it could be something like "Metro City_name-File_creator-A-datecode.ext"

The Manual only would look like "Metro City_name-File_creator-M-datecode.ext"

Note the A vs M

We could create a thread based on the Metro areas or States and perhaps with the authority of the site managers store these files within the site attached to the thread postings.

A smart user would always make a backup before testing a file from anyone else.

I would not want too mar my reputation on the board and I am sure others would feel the same way. That would be one way to build or attempt to insure trust for the origin and usability of the files.

[Cips]

The trust factor would be a biggie. It would be THE BIGGIE.

There are people on this forum that I know are from (my) town and they may be willing to trust my efforts.

I am guessing that one file type could be an AutoLearn filetype, meaning all data would be obtained only through that manner and then it could be something like "Metro City_name-File_creator-A-datecode.ext"

The Manual only would look like "Metro City_name-File_creator-M-datecode.ext"

Note the A vs M

We could create a thread based on the Metro areas or States and perhaps with the authority of the site managers store these files within the site attached to the thread postings.

A smart user would always make a backup before testing a file from anyone else.

I would not want too mar my reputation on the board and I am sure others would feel the same way. That would be one way to build or attempt to insure trust for the origin and usability of the files.

I think that's the only way this would ever happen.

[redrider]

I have already figured out that the data from one device can be shared with the other.

I also have two 9500ix units. I would be interested to hear some details about how you can share or merge the true lock data, because one of mine has been all over the US, and the other is pretty much virgin.

Can you please provide an explanation or instructions how to share or merge the data between two detectors?

[STiMULi]

Plug in RD "A" (This is the RD with the most Truelock data)
Using the EscortRadar site Download the latest location database.
Open Escort Detector Tools. From the Main tab choose Merge your data. This will merge the location database with your latest Truelock data.
When this is complete then choose the Advanced Tab. From there choose the Backup button. Then backup to a file name you can remember as the "original data" for that particular RD. It would probably be best to include the last 4 digits of the Serial number of RD ("A") in the file name. The Serial number is listed in the upper right hand corner of Detector Tools Program.

This is now the most updated file you have that includes the latest database and all of your most recent Truelock information.

If you wish that RD "B" start out exactly like RD "A" is then do the following.

Plug in RD "B" (This is the new RD)
Open Escort Detector Tools and then choose the Option tab. Place a check next to each portion of data you wish to become just like RD "A".
Choose the Advanced Tab. Click on the Remove button. This action will remove all data that was checked on the Options tab.
When you have removed all data then click on the Restore button. Choose the file name you saved RD "A" to. It should be the file name that ends in the last four digits of the serial number of RD "A"

When this is complete RD "A" and "B" should be the same.

At this point you should Backup RD "B" in the same manner as you have RD "A" by using the last four digits of RD "B" serial number.

A variation of this is how files could be shared from user to user in a given area.

[EscortRadar]

I do not recommend doing this mainly because of Truelock.

Truelock records the frequency of the radar signal along with the location. Slight variances may cause one 9500ix to report a slightly different radar frequency for a falser radar alert than another 9500ix.

If you leave AutoLearn on then it should correct these over time.