SmartSDR v3.8.20 and the SmartSDR v3.8.20 Release Notes
SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
Power Genius XL Utility v3.8.9 and the Power Genius XL Release Notes v3.8.9
Tuner Genius XL Utility v1.2.11 and the Tuner Genius XL Release Notes v1.2.11
Antenna Genius Utility v4.1.8
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Slice confusion in DX4WIN (and others?)
This brings up a second question. Does a list of recognized problems/issues/concerns exist that we can consult prior to listing a "problem" or "question?" I scan the community for similar issues before writing one, but sometimes that can be hard to sort out.
Thanks, everyone - great community here, and good responses!
Answers
-
All CAT enabled third-party programs are designed for VFO-A and VFO-B type radios, not multi-slice radios. The SmartSDR CAT implementation follows this de facto standard by only operating on slice A (as VFO-A) and slice B (as VFO-B). This is covered in the SmartSDR CAT documentation.
We do not have an on-line list of reported or active defects. You just need to search the community and then ask the question or report the problem if you cannot find a reference to it.0 -
Hi Duane, Tim is said it all... DX4WIN and all the other logging programs only see VFO-A for clicking on a spot and logging the band, Freq and so on.... I always keep VFO-A and VFO-B for the QSX freq on the band of interest so when I double click on a spot I get the right info set into the log.... Dennis, k0eoo0
-
OK, and this is "the way it currently is" for a "2-VFO" transceiver. Those with rigs that fit this description, including the FLEX-6300 will probably have no issues with that answer. However, the whole point of the 6500 and 6700 is that extra slices (either 2 or 6 of them) are now available. I could be listening to (for example) a DXpedition on two different bands, with QSX for each, meaning all four of my slices are assigned. Looks like the "other" band is suddenly looking better - how do I now, quickly, work and log him? Either we need a quick method to reassign Slice(n) to VFO-A and Slice(m) to VFO-B, or some other method that more intelligently determines which slice is used for TX and which for RX. Someone with a 6700 will have the same problem but in spades! That's part of the beauty of a new paradigm in radios - new ways to use them that don't fit the old mold! Now Flex could decide they're only going to mimic current radios in their instruction sets, but I think that would be a shortsighted answer.
1 -
I think Flex and others are giving all these ideas some thought. I expect we'll be able to define what VFO/Slice gets logged and so on in the future, I just don't know when that might be.... In the mean time I plan to use the other slices to monitor bands of interest and keep VFOA/B on the slice I'm currently working.... Its a bit awkward but its going to take time before the ROW gets hip to power of the slice, hi, hi....0
Leave a Comment
Categories
- All Categories
- 292 Community Topics
- 2.1K New Ideas
- 537 The Flea Market
- 7.5K Software
- 6K SmartSDR for Windows
- 146 SmartSDR for Maestro and M models
- 363 SmartSDR for Mac
- 250 SmartSDR for iOS
- 231 SmartSDR CAT
- 174 DAX
- 355 SmartSDR API
- 8.8K Radios and Accessories
- 7K FLEX-6000 Signature Series
- 41 FLEX-8000 Signature Series
- 851 Maestro
- 44 FlexControl
- 848 FLEX Series (Legacy) Radios
- 803 Genius Products
- 421 Power Genius XL Amplifier
- 279 Tuner Genius XL
- 103 Antenna Genius
- 245 Shack Infrastructure
- 167 Networking
- 405 Remote Operation (SmartLink)
- 130 Contesting
- 635 Peripherals & Station Integration
- 125 Amateur Radio Interests
- 875 Third-Party Software