This is probably not of interest to anyone, but I like to use the blscan command line program, usually the one that comes with Crazyscan. However it's .ini output doesn't include all the available parameters, and while it's report format includes all the important parameters, it is in a rather cumbersome text format that isn't easily imported into Excel.
So I decided to use Crazycat's SDK, and try to modify the blscan.cpp source. Since the report output contains what I was looking for in parameters, I decided to use it. I just removed most of the new-line feeds and replaced most of the labels with a comma so that it generates a CSV type output.
It's not finished, but it seems to work. After running a scan, I just double click on the report file, and it pops up in Excel, such as shown below:
![blscan-cvs1.jpg]()
Again, not sure if this would be of any use to anyone, but for me, it gives a quick easy view of the transponders on a sat in a format that allows me to quickly ID transponder parameters, particularly things like ACM/VCM and generic stream parameters that don't show up in the .ini transponder outputs. Only problem I've run into so far is that if I run a scan, and open the file in Excel, I have to close Excel before running another scan or it refuses to generate a new file. I guess I need a time stamp as part of the file name. I tested it on an XP-Pro-32 and a Win-7-64 machine, with my PROF-7500 and TBS-6925 respectively. I'm not sure what will happen when using a receiver that doesn't do advanced modes, or don't provide all the parameters to the program, or with some sats that have more complicated transponder modes. The columns might not line up properly. But so far everything seems to line up, although the PROF obviously doesn't show the ACM/VCM transponders.
Just unzip the file in it's own directory. Create Reports and Transponders sub-directories, and add streamreader.dll and blscan.ini. Probably best to change the name of the executable so as not to confuse with real blscan. It's a bit cumbersome to have to modify the .ini file, but that can be automated with scripts or other programs.
Thanks to Crazycat for making the SDK available. It's fun to play with.
EDIT: There may have been a problem with the attached zip file. I zipped it with 7zip, and I think I chose the wrong compression format. I replaced the file with a new one that corrects a couple errors, the main one being that plain DVB-S files didn't line up properly in Excel.
So I decided to use Crazycat's SDK, and try to modify the blscan.cpp source. Since the report output contains what I was looking for in parameters, I decided to use it. I just removed most of the new-line feeds and replaced most of the labels with a comma so that it generates a CSV type output.
It's not finished, but it seems to work. After running a scan, I just double click on the report file, and it pops up in Excel, such as shown below:
Again, not sure if this would be of any use to anyone, but for me, it gives a quick easy view of the transponders on a sat in a format that allows me to quickly ID transponder parameters, particularly things like ACM/VCM and generic stream parameters that don't show up in the .ini transponder outputs. Only problem I've run into so far is that if I run a scan, and open the file in Excel, I have to close Excel before running another scan or it refuses to generate a new file. I guess I need a time stamp as part of the file name. I tested it on an XP-Pro-32 and a Win-7-64 machine, with my PROF-7500 and TBS-6925 respectively. I'm not sure what will happen when using a receiver that doesn't do advanced modes, or don't provide all the parameters to the program, or with some sats that have more complicated transponder modes. The columns might not line up properly. But so far everything seems to line up, although the PROF obviously doesn't show the ACM/VCM transponders.
Just unzip the file in it's own directory. Create Reports and Transponders sub-directories, and add streamreader.dll and blscan.ini. Probably best to change the name of the executable so as not to confuse with real blscan. It's a bit cumbersome to have to modify the .ini file, but that can be automated with scripts or other programs.
Thanks to Crazycat for making the SDK available. It's fun to play with.
EDIT: There may have been a problem with the attached zip file. I zipped it with 7zip, and I think I chose the wrong compression format. I replaced the file with a new one that corrects a couple errors, the main one being that plain DVB-S files didn't line up properly in Excel.