Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need the latest SmartSDR and Power Genius Software?
SmartSDR v3.1.12 and the SmartSDR v3.1.12 Release Notes. | SmartSDR v2.6.2 and the SmartSDR v2.6.2 Release Notes.
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes. | Power Genius XL Firmware v3.4.16. | Power Genius XL Utility v2.2.10.
SmartSDR v3.1.12 and the SmartSDR v3.1.12 Release Notes. | SmartSDR v2.6.2 and the SmartSDR v2.6.2 Release Notes.
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes. | Power Genius XL Firmware v3.4.16. | Power Genius XL Utility v2.2.10.
USB Cable weirdness with MultiFlex in V3
When I am running both the M front and SSDR my USB cable that drives my Elecraft KPA500 and KAT500 is getting erroneous slice data. It appears that both the M and SSDR is reporting the same Slice.
Example: If I have USB cables configured for Slice A then if I use A on the M it commands the equipment, but if I also A on the SSDR it gets commanded. Same for B.
But then there is a case when I set the cables config to work on Slice D and Slice C on the SSDR will command it. And it may change on next time I run SSDR.
Without MultiFlex it tracks fine.
Also if USB cables is configured to work with TX Slice or TX Pan it also gets confused.
As for the Active Slice option I would have thought that if the M is running then SSDR would populate it's first Slice as then next in line Slice position (e.g. If the M just had A active then starting SSDR would have B as it's first slice).
So as it stands now using the USB cable to drive an external device could become hazardous.
Example: If I have USB cables configured for Slice A then if I use A on the M it commands the equipment, but if I also A on the SSDR it gets commanded. Same for B.
But then there is a case when I set the cables config to work on Slice D and Slice C on the SSDR will command it. And it may change on next time I run SSDR.
Without MultiFlex it tracks fine.
Also if USB cables is configured to work with TX Slice or TX Pan it also gets confused.
As for the Active Slice option I would have thought that if the M is running then SSDR would populate it's first Slice as then next in line Slice position (e.g. If the M just had A active then starting SSDR would have B as it's first slice).
So as it stands now using the USB cable to drive an external device could become hazardous.
0
Leave a Comment
Categories
- 69 Community Topics
- 1.9K New Ideas
- 119 The Flea Market
- 5.4K Software
- 4.9K SmartSDR for Windows
- 35 SmartSDR for Maestro and M models
- 85 SmartSDR for Mac
- 143 SmartSDR for iOS
- 149 SmartSDR CAT
- 67 DAX
- 278 SmartSDR API
- 7.1K Radios and Accessories
- 5.8K FLEX-6000 Signature Series
- 553 Maestro
- 14 FlexControl
- 723 FLEX Series (Legacy) Radios
- 149 Power Genius Products
- 117 Power Genius XL Amplifier
- 10 Power Genius Utility
- 22 Tuner Genius
- 41 Shack Infrastructure
- 22 Networking
- 89 Remote Operation (SmartLink)
- 50 Contesting
- 127 Peripherals & Station Integration
- 61 Amateur Radio Interests
- 404 Third-Party Software
Comments
I opened a support ticket for this.
Mike
Hit PTT on the slice that you want to transmit on and the USB CAT reporting will switch over to the slice that had the last PTT.
Andreas, N6NU
I tested this multiple times and it seemed to work fine. I would prefer that it the software actually changed the TX flag of the slice, so that the slice TX flag would only be enabled in the slice that has Multiflex PTT enabled. I think this would make the KAT500/KPA500 bandswitch as soon as the Multiflex PTT switched between clients.
Again, this could just be "operator error" due to the lack of documentation of Multiflex setup/operation.
I tested this multiple times and it seemed to work fine. I would prefer that it the software actually changed the TX flag of the slice, so that the slice TX flag would only be enabled in the slice that has Multiflex PTT enabled. I think this would make the KAT500/KPA500 bandswitch as soon as the Multiflex PTT switched between clients.
Again, this could just be "operator error" due to the lack of documentation of Multiflex setup/operation.
For amplifiers (and other devices inline with the transmit path) the recommended configuration is to set the source of the USB cables to TX Antenna and assign it to the physical output that the amplifier is connected to (ANT1 or ANT2). This allows two clients to operate independently if they are using different TX Antennas just like a single client.
If both clients are using the same transmit antenna, the USB cable will report the frequency of the last client that transmitted. If a different client transmits (not the last transmitter) then the USB cable will report the new frequency and then transmit. In this configuration, an appropriate TX Delay may have to be set to allow the hardware to change to a new band.
You can also set the USB cable source to TX Slice which will function the same but it will not be dependent on the TX Antenna. This can be helpful in certain situations but for amplifiers (since they are physically connected to a TX Antenna port on the radio) the TX Ant source is preferred.
I tested it using 2 laptop Clients, Win7, nothing running but SSDR--no CAT or DAX on either Client. Both using wired connections and neither using SmartLink.
Like you, I have a KAT500/KPA500 with the USB connections directly to the Flex.
I setup Client 1 on 20M, using my 20-SSB Global profile and using Slice A. I setup Client 2 on 40M, using my 40-SSB Global profile, also using Slice A. The 20M antenna is #1 on the KAT500 and the 40M antenna is #3 on the KAT500
The KAT500/KPA500 USB cables were set on TX Slice.
Using the MultiFlex window, I enabled PTT on Client 1. When I pressed MOX or the foot switch on Client 1, the KAT500 and KPA500 switched bands and selected Antenna #1. I then used the MultiFlex window to enable PTT on Client 2. When I pressed MOX or the footswitch on Client 2, the KAT500 and KPA500 switched bands and selected Antenna #3. So, the correct TX antenna and TX band were selected by the KAT500 and the KPA500.
That takes care of switching to the correct TX configuration. However, this does not address the need to provide the correct RX antenna to the "listening" Client machine. The KAT500 is selecting the antenna used for both RX and TX in my configuration. This not an issue with MultiFlex--it is an issue with the configuration of my antennas/antenna switching, which I need to work out.
The USB cables appear to work fine with MultiFlex.
Thanks for your feedback.
The Elecraft stuff doesn't really have an issue with bandswitching on TX, but I would prefer to have it switch when the MultiFlex PTT is enabled.
Again, we don't have much documentation, so it is hard to know how the designers intended MultiFlex to be setup/operated.