IDTracker !!! Debug?

[RonnieUSA]

What are these, and how to fix it?

000:39:03.467 BCSendIV - Timeout (SQL)
000:39:05.639 BCSendIV - Timeout (RMC)
000:39:07.670 BCSendIV - Timeout (VOL)
000:39:09.779 BCSendIV - Timeout (STS)
000:39:11.904 BCSendIV - Timeout (GLG)

Thank You

I see this a lot.

 

[brscanning]

What are these, and how to fix it?

000:39:03.467 BCSendIV - Timeout (SQL)
000:39:05.639 BCSendIV - Timeout (RMC)
000:39:07.670 BCSendIV - Timeout (VOL)
000:39:09.779 BCSendIV - Timeout (STS)
000:39:11.904 BCSendIV - Timeout (GLG)

Thank You

I see this a lot.

The timeouts occur when the scanner does not response to a command. Does it affect the tracking? If not, you can disregard them.

 

[RonnieUSA]

The timeouts occur when the scanner does not response to a command. Does it affect the tracking? If not, you can disregard them.

I'm not sure.

 

[brscanning]

I'm not sure.

Does ID Tracker stop or does it continue tracking? ID Tracker was written so that interruptions in communications would not stop the tracking process. These interruptions can be caused by the scanner not responding in time because it is doing something else or they can be caused by other programs on the computer consumming a high amount of resources preventing ID Tracker from functioning properly.

These interruptions are usually temporary and should not affect overall performance. Depending on your system these timeouts may occur more frequently. I am running a fairly high end system and rarely see timeouts. ID Tracker III usually consumes less than 1/2 of a percent in CPU time when running even when recording audio.

 

[RonnieUSA]

Does ID Tracker stop or does it continue tracking? ID Tracker was written so that interruptions in communications would not stop the tracking process. These interruptions can be caused by the scanner not responding in time because it is doing something else or they can be caused by other programs on the computer consumming a high amount of resources preventing ID Tracker from functioning properly.

These interruptions are usually temporary and should not affect overall performance. Depending on your system these timeouts may occur more frequently. I am running a fairly high end system and rarely see timeouts. ID Tracker III usually consumes less than 1/2 of a percent in CPU time when running even when recording audio.

Is there away to turn off the debug thing? It still logs while it's running, because it doesn't stop till I click on the red x to close it.

Thank You for your time, and help.

 

[brscanning]

Is there away to turn off the debug thing? It still logs while it's running, because it doesn't stop till I click on the red x to close it.

Thank You for your time, and help.

I am assuming that you are referring to the debug window popping up automatically. I can probably add an option to disable this.

 

[RonnieUSA]

I am assuming that you are referring to the debug window popping up automatically. I can probably add an option to disable this.

It's only popped up once with build 1.15.1, but to be able to turn the window off would be nice. Also where is the debug log saved to?

 

[KC0CSE]

FREESCAN

With freescan can you program in a fav's list?

 

[brscanning]

It's only popped up once with build 1.15.1, but to be able to turn the window off would be nice. Also where is the debug log saved to?

The debug log is stored in memory and not saved to a file.

I am currently looking into the best method of disabling the automatic popup of the debug window.

 

[brscanning]

ID Tracker III - Version 1.15.2

Ronnie,

I have added the option to control the debug window popup. It is disabled by default.

Download: ID Tracker III

Change History: ID Tracker III Version / Install Notes

 

[RonnieUSA]

Ronnie,

I have added the option to control the debug window popup. It is disabled by default.

Download: ID Tracker III

Change History: ID Tracker III Version / Install Notes

Got it, Thank You!!