Flex Repeater Spots Utility

KD0RC

Here is a good reason to use the FlexRepeaterSpots utility in a contest.

With all those stations just south of 28.300, it is very easy for a US ham to go down there without thinking about it. I put a band edge marker in FlexRepeaterSpots to help remind me not to go there in the heat of battle. Here is the Config.ini entry that I used:

Spot: freq=28.300 name=SSB_Band_Edge mode=LSB SpotColor=RED SpotBackColor=YELLOW

KD0RC

FlexRepeaterSpots V1.11 is now available on GitHub:

https://github.com/KD0RC/FlexRepeaterSpots/releases/tag/FlexRepeaterSpots_V1.11

    // ***********************************************************************

    // V1.11

    // Added ability to use as many slices as the radio will support.

    // ***********************************************************************

I didn't realize just how much I rely on FLexRepeaterSpots in everyday operation. I had four slices open on 2 meters so that I could compare coverage and latency of a set of linked repeaters. Slices C and D did not get their options set when I clicked the repeater spots. I really had to think about what was wrong when it dawned on me that I hard-coded two slices for my 6400. Now that I have an 8600, I have a way to test for more slices.

This update should work with however many slices a radio has, so it should be good to go for 6700 users.

If you upgrade to this version, you will need to uninstall the previous version first. Use the Windows Settings, Apps screen to do the uninstall. Do not delete anything manually.

KD0RC

FlexRepeaterSpots V1.13 is now available on GitHub:

https://github.com/KD0RC/FlexRepeaterSpots/releases/tag/FlexRepeaterSpots_V1.13

    // ***********************************************************************

    // V1.13

    // Upgraded so it will compile under Visual Studio 2022.

    // Upgraded FlexLib to V 4.x.

    // ***********************************************************************

    // V1.12 (not released separately)

    // Fixed bug where slice index got lost causing app to crash.

    // Added ability to select which radio to connect to.

    // ***********************************************************************

New this time is the ability to select the radio that you want, or just specify ANY and it will connect to the first radio it finds. If you have multiple radios on the same LAN, this new feature is indispensable. If not, you can leave it at the default of "ANY".

If you upgrade to this version, you will need to uninstall the previous version first. Use the Windows Settings, Apps screen to do the uninstall. Do not delete anything manually.

WX7Y

WORKS Super, I love the ALL connection when I have two radio and only one online at a time, SLICK.

Thanks for the Update

Bret WX7Y

KD0RC

Thanks Bret, I appreciate it!

KD0RC

FlexRepeaterSpots V1.14 is now available on GitHub:

https://github.com/KD0RC/FlexRepeaterSpots/releases/tag/FlexRepeaterSpots_V1.14

    // ***********************************************************************

    // V1.14

    // Fixed MultiFlex issue where the correct active slice was not being set.

    // ***********************************************************************

My new 8600 is showing me bugs in my code that I never saw before… The problem is that a rig with more than two slices can have different slice indices on each GUI client in a MultiFlex situation. I found the problem when slices 0, 1 and 3 were on one GUI client (SmartSDR) and slice 2 was on the other GUI client.

Slices 0 and 2 were set as the active slice (one active slice on each client). As long as I used slice 0 or 1, I got the desired results. As soon as I switched slice 3 to active, it actually changed slice 2 on the other client, as it was the first active slice that it found.

In any event, it is all sorted out and working for me. Please let me know if you have any issues with the new version.

If you upgrade to this version, you will need to uninstall the previous version first. Use the Windows Settings, Apps screen to do the uninstall. Do not delete anything manually.

ea5wa

I'm using v1.14 but I can only display the memories of my Flex 6600.

All the lines that I add to config file are not displayed

Where is config.ini saved, because looking at the folder, there is a different config file to the one I open from the File Menu

Thanks and 73

KD0RC

I can't seem to recreate that situation. Do you have the same frequency and spot name in both memory and in the Config.ini file? If so, you will only get one or the other. If the name or frequency are different, you will get both.

Can you post a picture of your SmartSDR screen on 2 meters when the above file is in FlexRepeaterSpots?

WX7Y

hi Len no I took those out of the Flex Memory list

Maybe it’s only doing it because I Run FreeDV-Flex on my Raspberry pi

Which actually gives me the FDVU and FDVL mode from a waveform

ea5wa

I only have these spots in config.ini (different to the ones in the memories list) but none of them are displayed in Smartsdr.

I can only see the memories when is configured ON in config.ini file, but Spots included in config.ini are never displayed

KD0RC

I can't recreate that behavior.

Do you have a transverter for 2 meters set up on the XVTR tab of Radio Setup? Without this, no 2 meter spots will show. Do you have spots defined at other frequencies?

ea5wa

Yes, I have a xvtr configured and working correctly.

I have also other bands spots but none of them are displayed. Only the memory Channels from smartsdr are displayed if I set it as ON in the config.ini file

KD0RC

Very strange behavior… Can you post your Config.ini file here? I wonder if there is something in there that I did not accommodate in the code. Also, do you have Config spelled with a capital "C"?

ea5wa

I put a picture of my config.ini file

KD0RC

I can't use the picture to re-create the issue, can you post the file here or send it to me in an email? You might need to zip it to post it here.

The name of the file must be Config.ini, not config.ini. Can you verify that it is Config?