ID Tracker
Updated: 01/17/10

Reporting Errors / Issues

Before reporting issues with ID Tracker, please check with the FAQ list below.  If the does not answer your question, please include the following with reporting issues:

ID Tracker FAQ


Q. Why is ID Tracker freeware?
   
A. I developed this software for my own personal use because available software did not suite my needs.  I released it to the public so that others might get some use from my efforts.  By releasing the software as freeware, I am not compelled to support or enhance it.  I can release the software as is.

Q. ID Tracker II does not operate properly with my GRE scanner.
   
A. If you reprogram your GRE scanner, YOU MUST RELOAD the scanner image by checking the Reload GRE Image in the Settings dialog in order for ID Tracker II to function properly.

YOU MUST DISABLE THE CCDUMP and DSP COMMS functions of the scanner.  These functions interfere with the communications to the scanner.  If you are using Win500 to program the scanner, these are under the Extended Settings "Dump trunking data to PC/IF" and "Echo DSP comms to PC/IF".


Q. ID Tracker is not recording audio.
   
A. In order to record, you must enable global recording as well as enabling recording for each system that you wish to record.
 
To do this, enable recording in the "Settings" screen or by right clicking on the main display. Then enable recording for each system in the "Edit System" screen or by right-clicking on the system indicators on the main display.
 
To verify recording, there is a recording indicator just above the signal level on the main display. If it turns red when an ID is active, ID Tracker should be recording. If not, check to see if you can record scanner audio using the Windows Sound Recorder.

Q. Will ID Tracker support the new XXXX scanner?
   
A. I will only add support for scanners that I personally own or which have protocols close to the scanners which I own.  Some of the newer scanners have protocols that are significantly different from the older models.  Without actually owning one of these scanners, it would require too much effort to develop and maintain the software to support these scanners.  Scanners that are supported can be found here:
ID Tracker / ID Tracker II / ID Tracker III

I have had requests to support the following scanners but currently do not plan on supporting them unless my situation changes:

Uniden Models:  BC895, BC246T
Radio Shack Models: Most do not support computer control.

Note: The BC246T is missing one of the commands (GLG) in it's protocol that is necessary for ID Tracker to support the scanner. All of the supported Uniden scanners using the newer protocol provide this command.


Q. ID Tracker does not record properly.  It sometimes creates zero length files or generates the error "Error: MMSYSTEM296 The file cannot be played on the specified MCI device."   There may also be repeated bits of audio in the WAV file.
   
A. These problems are a result of the sound system's inability to handle the rapid record starts and stops. These problems occur more often on older Windows 98 and Windows ME  systems but may occur on newer systems as well.  Upgrading the sound system (such as using a good sound card instead of the built in system) or the operating system may resolve the issues but there are no guarantees on this.

Q. When tracking is stopped, the scanner is left in an un-muted state.
   
A. This is a result of certain scanners not responding to the muting control commands as expected.  If the problem persists, try disabling the "Enable Muting" option in the ID Tracker settings.

Q. Will ID Tracker program my scanner?
   
A. ID Tracker and ID Tracker II were never intended to program scanners. There are enough programming applications around already. Also, with the number of scanners supported by the ID Tracker applications, it would take much more time than I have available to properly support all the scanners.

Q. ID Tracker does not always log or record hits.
A.   This may be due to the Minimum Log Time being set to high.  The Minimum Log Time is designed to prevent short unwanted transmissions with no meaningful information.  The default is set to 2000 ms or 2 seconds.  Any transmission shorter then this time will no be logged or recorded.

Baton Rouge Area Scanning Home Page