BC Tool / BCT15

[PHOENIX_SCANNER]

I have been playing with freescan so far on my BCT15 and have the scanner pretty well programmed, but decided to try BC Tool.

It communicates with the scanner just fine, but does not see the programming that was put in by Free Scan.

It gives an error message to the effect that "there is no programming in your scanner", when I go to download the programming that is in the scanner.

Ideas?

Also, I have tried using both programs to log and had poor results. I am used to using WIN500 to do logging on my PSR style scanners, and it works great. I logs any DCS or CTCSS codes that pop up on channels that were previously unknown, and records audio for whatever channels it is told to do so on.

Free Scan and BC Tool usually DON'T catch the codes, and the audio record function of BC Tool works very poorly, almost never recording anything, and usually when it does record something, it says "deleted" after soon after. It seems they both react too slowly, and I was wondering if this is the blame of the slow serial interface that uniden scanners use. I know on my PSR type scanners the interface is probably at least twice as fast, and it seems faster than that. The control feature of BC Tool is also very laggy, lagging far behind what is really happening on the scanner.

Has anyone else run across these issues and if so have they found any solutions, and would any other software work better?

Thanks.

[UPMan]

Unless you have set the port speed to a slow rate, logging should be virtually instantaneous. Are you judging the speed based on how long it takes to program? If so, when it is being programmed the scanner has to create new index points for every item (system, channel group, channel) sent to it, resulting in a delay while the scanner processes the data. It doesn't have to do this when outputting log data (or when reading system info out of the scanner).

I've not used the record/loggin functions from FreeScan or BC Tool, but most recorders that use a VOX start have a problem in that the very beginning of a transmission will be lost. Since most transmissions are short, this could result in a lot of small seemingly empty files.

I've seen some software that will continuously record, then automatically backtrack and create files only from the start of audio, but I don't think I've seen this done with scanner recording/logging software. When I really need to capture a transmission (usually for diagnostic purposes), I'll record continuously, then post-process by running the recording through Audacity and have it delete all the "white space" between transmissions.

[Mike_G_D]

PHOENIX_SCANNER,

After reading your post I decided to download and try BCTool. Like you, I have been using FreeScan and have been wanting to try BCTool for awhile now. Also like you, I am using a BCT15.

I have downloaded and installed BCTool and it seems to be working fine. It is logging very quickly (tones and all) and it read my BCT15 fine (which has, up until now, been programmed by FreeScan).

So, I must assume that your problem must be a result of some setting or configuration on your PC. I suspect the COM port settings.

When I first ran BCTool I set it to run on the com port my BCT15 was attached to (in my case, COM PORT 2) and ran the find radio function. It found my BCT15 right away. After that I downloaded the memory programming which went fine and the program started logging right away.

I am still getting used to the BCT15 and FreeScan so am now adding BCTool to that "get used to" list. So far, I do like the look of BCTool a little better than FreeScan but will have to use them both for awhile and see which works best for me.

One thing I think I like is the little balloon message that pops up in the lower right with info on what is currently being received.

-Mike

[ka3jjz]

A lot of folks I know keep both packages handy - BCTool for general logging and FreeScan for programming. Recently FreeScan just added some import abilities for BuTel ARC files (conventional freqs only for now, trunking is coming...) to assist if you are moving from one of those packages, and it has other features as well. As both are free, you lose nothing keeping both in your pocket, as it were. 73 Mike

[bonus1331]

I use BcTool exclusively for logging and recording my 15 and has never had a glitch with clean audio.
Definitely a config issue on your part.
Let me know if I can help.

[mlconnell]

I am using bctool on my BCT-15 and like it alot. Dont have any problems except that the detect my scanner does not ever find the scanner. It may be because I am using a Serial --> USB conversion cable ?? Just my thoughts on it. When I select the comport and speed it connects right up and works great. Logging is really fast and recording is not bad on my end. I also tried Freescan and it loaded up my scanner and the programming from bctool with no problems. Liked Freescan but am used to bctool so I have em both for now. Does anyone know the major differences between bctool & Freescan?

[PHOENIX_SCANNER]

Ok, well it sounds like I have more investigating to do here. It could be a hardware issue with my sound card possibly. It just doens't record many sound bites. Most are deleted as if there was nothing there.

UPMan the logging is quick, and yeah I was judging by the speed at which programming is uploaded. My GRE uploads are many times faster so I thought that had something to do with it, but I guess not. DCS / CTCSS decoding / logging works fine on BCTool so long as the tx is long enough. If it is short it doesn't catch it very often.

On a related note I saw a post by UPMan regarding NFM vs. FM settings and the impact on decoding today, and wonder if this could be a factor in this equation as well...hmm....

Well, thanks for the input to all, back to the drawing board...

By the way as far as I can tell free scan doesn't do audio files so BC Tool has an edge in that regard.

[ShawnInPaso]

Hey Phoenix.........

I doubt this is the issue but it might be worth a look with regard to your sound card:

IF you are using Windows -

From the control panel, select 'sound and audio devices'.
Then the audio tab
Then have a look at which input is selected for audio input (e.g. mic in or line in).

Perhaps the correct input was changed by the software and needs to be set correctly.

just my .02 cents

[PHOENIX_SCANNER]

Thanks, I'll double check.

[SouthSoundScanner]

"It gives an error message to the effect that "there is no programming in your scanner", when I go to download the programming that is in the scanner.

Ideas?"

Try the "bcTool_reset_tool" it should be in the bcTool program files. It worked for me.

[PHOENIX_SCANNER]

Originally Posted by KC9GLG

"It gives an error message to the effect that "there is no programming in your scanner", when I go to download the programming that is in the scanner.

Ideas?"

Try the "bcTool_reset_tool" it should be in the bcTool program files. It worked for me.

Thanks a million for pointing that feature out. It was the answer I was looking for. Not only does the program now recognize the scanners programming, the tone logging works much better now.

If anyone is ever having issues with BCTool, just hit that reset button in the program files folder.

Thanks again.

[Zard0z]

If you stayed with freescan It would not have been an issue!

Just kidding.... I have both too but I must say freescan has had
no issues ... even with Windows 7 >http://www.radioreference.com/forums...ml#post1005741

[cifn2]

Ah that could be my issue, I don't have an audio cable hooked up, I have only the USB cable, it won't decode without the audio cable input to scan right?