next »

This new version of FreeSCAN includes new features & bug fixes.

Direct Download -
http://scannow.org/files/FreeSCAN-0.9.msi

.9
------------------------------
-EZ Grab now has improved detection for different field types
-Also made to be more comaptible with IE, but for best results Firefox is still recommended
-Although it is not possible to assign quick keys to trunk systems, it is possible to assign QKs to trunk systems. By selecting this option,
FreeSCAN will assign the QK to all sites below the system.
-You can now drag'n'drop groups and sites around
-Improved statistics function
-Printing is back!
-Also supports printing to HTML, so you can download from your scanner, print to HTML, then simply copy & paste to your website.
-Added option to edit battery charge settings for XT scanners
-Added System Protect option
-Added ability to edit additional Service Search settings for XT scanners
-When you attempt to download/upload from/to the scanner and the scanner is in menu mode, FreeSCAN will now take it out of menu mode first, instead of the rude dialog box.
-Added P25 NAC option to Close Call
-You can now set the LCD brightness level on the 346XT
-Added band scope and tone out search option to service key assignment
-NAC logging may work
-Added experimental support for the BCD996XT & BC15XT. Looking forward to hearing some feedback from the beta testers. 15XT support may not work at all due to the fact that Uniden has not published the command protocol for it yet.
-Fix: an issue with modulation mode not being set under certain conditions
-Fix: an issue when uploading GPS range settings for conventional groups
-Fix: EZ-Grab would drop all data if you clicked on the window the wrong way
-Fix: A number "1" would appear in the comment field of RR import
-Fix: Audiotype not being set to analog when importing 396T UASD files
-Fix: Issues with settings priority mode on XTs
-Fix: Issues with setting display modes on XTs
-Fix: Issues with setting alert light behaviour on the 346XT
-Fix: Trunk frequency Number Tags and volume offset was not being downloaded from EDACS SCAT systems
-Fix: Uploading some Close Call settings to XT scanners
-Fix: Delete warnings.
-Fix: Various issues with Fire Tone OUt
-Fix: TGID Alert Colour not being downloaded from 396XT
-Fix: Can't download service search settings from certain scanner models
-FIx: Justifying multiple channel names may cause names to be overwritten
-Fix: FreeSCAN would not allow digital channels to be sent to an analog scanner
-Fix: When importing trunk sites from RR, they may be set to the wrong type
-Fix: DMS/DEG selection in preferences not being saves
-Fix: Downloading number tag and agc settings for custom search under 396xt
-Fix: Some close call settings not being downloaded from 396XT
-Other bug fixes & improvements

CAUTION ** DANGER WILL ROBINSON ** CAUTION **
-Before you wipe out your programming experimenting with System Protect, read the following:

Once System Protect is enabled and the system is uploaded to the scanner, System Protect cannot be turned off.

Protect will lock down the affected system to both the user and FreeSCAN.
This means that the user going through the front panel cannot delete or modify
a protected system other then locking out channels. If you try to access it through the programming menu,
the scanner will deny access.

Protected systems can't be downloaded back to software. It's a one way trip only.
If you try to download a protected system, all the scanner will send are blank channels.

You can still delete a protected system using FreeSCAN as you would a normal system. But it
cannot be deleted through the front panel.

Wow, Assaf.  Inital look is great!

One thing so far, just happened to click on Check for Updates.

No dialog box or anything to say "no."

Great job.

Kevin

As always a great job Assaf!
I look forward to giving the new features a try!
Marshall KE4ZNR

The installer is still seriously buggered up. Are you using the stuff built into Visual Studio to make the installer? If so, ping me and I'll walk you through the settings to get it working right.

Meanwhile, you *have* to uninstall the previous version first. Otherwise, the new installer will go through the motions but not actually do much (but will make a bit of a mess in Add/Remove).

Brad.

Assaf,

Here's the list that I've prepared.  Those starting with a "+" appear to be resolved.  The others have not.  Obviously, some are my preferences rather than bugs.

Most significant is the fact that the logging is still not logging conventional channels for me.

BTW, I was able to install over the 0.9 Preview version without any noticeable problem.

Thanks!

Dick

-The html printout shows the step size, but it would seem more useful to have it show audio type or CTCSS/DCS/NAC
+No print summary available-FIXED
+Rollover for Maximum Priority Channels appears when you rollover Priority Interval Time-FIXED
-Battery Save rollover says "This feature turns off RF power for 1 second and turns on it 300 ms ..." rather than "This feature turns off RF power for 1 second and turns it on 300 ms ..."
-C-Ch Logging rollover says "When data stream output function is set to extend..." rather than "When data stream output function is set to extended...".  Also there is an extra "." after <CC data> in that rollover message
+Close Call Override Mode rollover message says "Enable to this to allow you..." rather than "Enable this to allow you..."-FIXED
+Disable CC Hits with Scan rollover says "recentley" rather than "recently"-FIXED
+When I click on the Fire Tone Out tab I get the attached error message and I have to go to Task Manager to close the program.-FIXED
-Option for OFF, CTCSS/DCS Search, P25 NAC Search should be on the Searching tab rather than the Close Call tab
-Searching tab-Field should be Step rather than Search
-Logging doesn't log conventional channels
-When closing virtual scanner, would be better to go directly back rather than having to cancel virtual control setting window
-Print preview opens very small window
-The splash screen is so fast that there's no way to read it.
-The rollovers also appear a bit too fast to read fully.

You do have to uninstall the previous edition. However, this is fixed in the current version. When .9A comes out it will be a straight over install.

The installer is still seriously buggered up. Are you using the stuff built into Visual Studio to make the installer? If so, ping me and I'll walk you through the settings to get it working right.

Meanwhile, you *have* to uninstall the previous version first. Otherwise, the new installer will go through the motions but not actually do much (but will make a bit of a mess in Add/Remove).

Brad.

Assaf,

Here's the list that I've prepared.  Those starting with a "+" appear to be resolved.  The others have not.  Obviously, some are my preferences rather than bugs.

Most significant is the fact that the logging is still not logging conventional channels for me.

BTW, I was able to install over the 0.9 Preview version without any noticeable problem.

Thanks!

Dick

Sounds like version upgrading is working properly now. It's really strange you are seeing that, you are using a 396XT right?


-The html printout shows the step size, but it would seem more useful to have it show audio type or CTCSS/DCS/NAC
You can select which fields you want in the other tab. Those are the defaults though.


-Battery Save rollover says "This feature turns off RF power for 1 second and turns on it 300 ms ..." rather than "This feature turns off RF power for 1 second and turns it on 300 ms ..."
I did read this in your first message but I was unclear of what the difference was. Now after copying and pasting I see the words "it on" and "on it" are switched around.


-C-Ch Logging rollover says "When data stream output function is set to extend..." rather than "When data stream output function is set to extended...".  Also there is an extra "." after <CC data> in that rollover message
Ok i'll look into that.

-Option for OFF, CTCSS/DCS Search, P25 NAC Search should be on the Searching tab rather than the Close Call tab
It applies to either or though.

-Searching tab-Field should be Step rather than Search
Huh?

-Logging doesn't log conventional channels
-When closing virtual scanner, would be better to go directly back rather than having to cancel virtual control setting window
You only have to click on the X!

-Print preview opens very small window
That didn't happen on any of my systems but you are not the only one to report this. If you resize the window though, I think it should remember.

-The splash screen is so fast that there's no way to read it.
Well at least that you can never get tired of it.

-The rollovers also appear a bit too fast to read fully.
Unfortunately that's controlled by Windows. I think it is too fast as well.


I'll look into the things you mentioned in the mean time.. If you find anything else then just post it up.

Conventional logging works fine for me with the exception of the NACs. I see the NACs in the control window but they do not show up in the logging window.

Sounds like version upgrading is working properly now. It's really strange you are seeing that, you are using a 396XT right?

Right.

-The html printout shows the step size, but it would seem more useful to have it show audio type or CTCSS/DCS/NAC
You can select which fields you want in the other tab. Those are the defaults though.

Sorry I missed that.  Having the choices is great.

-Option for OFF, CTCSS/DCS Search, P25 NAC Search should be on the Searching tab rather than the Close Call tab
It applies to either or though.

I'm referring to the Tone/Code Search setting on page 75 of the reference manual which applies to the Srch/CloCall Opt menu on page 72.  It appears that there is one setting that applies to both Close Call and Searches which is why I thought it should be on the Searching tab with the other options for Srch/CloCall.

-Searching tab-Field should be Step rather than Search
Huh?

On the Searching tab you have a field marked "Search".  It should really be marked "Step" since that's what the dropdown sets is the step value.

-When closing virtual scanner, would be better to go directly back rather than having to cancel virtual control setting window
You only have to click on the X!

Yes, but that takes me back to the window on which I can set the comm port, baud rate, type of virtual display, etc.  I thought it would be cleaner when closing the virtual display to just go directly back to the main screen rather than stopping first at the comm port, baud rate, type of virtual display screen since I have no need to change those settings when I close the virtual display.

-Print preview opens very small window
That didn't happen on any of my systems but you are not the only one to report this. If you resize the window though, I think it should remember.

That's what I thought, too, but I can't get it to do that.  If I resize and then close it, it still opens small the next time.

New Problem, unfortunately.  When I try to upload data to the scanner I get an error which reads:

"FTO Error, may need to reinitialize settings.  FTO Upload aborted."

I have no FTO set.

Dick

I solved the FTO error problem by downloading the data from the scanner to Freescan and resaving the data file.  I closed Freescan, reopened it, and reloaded the data file.  It then uploaded okay to the scanner.  I'm thinking corrupted data so I think you can cross this one off the list.

I've been watching the logging for some additional time.  There are two hits on conventional now, but nowhere near what there should be based on what I'm hearing and  what I see on the virtual display.  The busiest channels are Milw PD conventional and I've only got the two hits there.  There have been other conventionals as well that haven't been logged including aviation and a neighboring county sheriff.

Dick

Sometimes you might have to reset the FTO settings from old files. I had to change the format around a bit to accomodate the new features in XT scanners. So are you keeping an eye on the Linear tab or the Review tab? Also if transmissions are very short, like about 1 second, they may not get logged.

I solved the FTO error problem by downloading the data from the scanner to FreeSCAN and resaving the data file.  I closed FreeSCAN, reopened it, and reloaded the data file.  It then uploaded okay to the scanner.  I'm thinking corrupted data so I think you can cross this one off the list.

I've been watching the logging for some additional time.  There are two hits on conventional now, but nowhere near what there should be based on what I'm hearing and  what I see on the virtual display.  The busiest channels are Milw PD conventional and I've only got the two hits there.  There have been other conventionals as well that haven't been logged including aviation and a neighboring county sheriff.

Dick

I don't use the FTO settings at all, but I have a feeling that they may have gotten messed up with that other problem with the crashes when I selected that tab.  In any event, that part's okay now.

Regarding logging, I'm watching both the linear and the review tabs--not appearing in either.  Additional information is that Freescan logs conventional frequencies just fine from my 246T and also that other software logs conventional frequencies from my 396XT.  It's not that the transmissions are too short since I'm listening and watching at the same time.  These are legitimate transmissions that aren't getting logged.

Dick

I have been watching my scanner and the logging and it is working for me (with the exception of NACs). There must be something different about our setups. I am logging all hits, even very short transmissions.

I've attached the csv file of my log for 4 hours tonight along with the same file with the conventional frequencies highlighted in yellow which I've saved in xls format.  As you can see, there were only 12 conventional hits in that time.  This is not even close to what actually took place since the scanner was mostly listening to the Milwaukee PD during that time on frequencies from 460.075-460.500.

As you can see, in addition to not including most of the conventional hits, the files don't properly reflect the systems, groups, and TGIDs for the trunking hits.  The csv is as it was exported.  I didn't sort it or move anything around.  The xls is different only in that I highlighted the conventional frequencies.  The on screen displays properly showed the systems, groups, and TGIDs as expected.

Perhaps this will provide some clue as to what my problem is.

Thanks.

Dick

I'm using a BCD396XT and have also noticed that 0.9 does not log conventional channels.  It seems to log trunked channels OK.  Note that if the scanner is stopped on a conventional channel (i.e.:  the squelch is open) and I hit the hold button in virtual control mode, the logger does log the conventional channel hit.

Also, I have noticed that the alert colours are not uploaded from the scanner for conventional channels.  The alert colours/tones are uploaded for trunked channels and in the fire tone out settings, but not for any of the conventional systems.

Regardless of this, thank you for a great program!

I'm going to try and figure out whats going on with both of these issues. The virtual control code for the 396XT is that exact same as is used for the 346XT, and thats what I use to test with. It seems to work on my end, which makes me wonder if there is some option set on the system or channel that is changing the way it gets logged.

Going to look into the alert colour. You say "upload from the scanner", do you mean download?

 Glad to see that FTO is working right though, seems like that was always a troubled area.

I'm using a BCD396XT and have also noticed that 0.9 does not log conventional channels.  It seems to log trunked channels OK.  Note that if the scanner is stopped on a conventional channel (i.e.:  the squelch is open) and I hit the hold button in virtual control mode, the logger does log the conventional channel hit.

Also, I have noticed that the alert colours are not uploaded from the scanner for conventional channels.  The alert colours/tones are uploaded for trunked channels and in the fire tone out settings, but not for any of the conventional systems.

Regardless of this, thank you for a great program!

Yes, I meant to say download from the scanner into FreeSCAN.  Thanks for your help.

Yes, I meant to say download from the scanner into FreeSCAN.  Thanks for your help.

Well I've thrown up .9A, give that a try. For the logging, there must be some subtle difference between the two that isn't obvious. That is just something that needs to be looked further into. No need to uninstall the previous version if .9 is already installed.

Looks like the alert colour issue is solved with .9A, thanks for the quick work.