Welcome to the 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 refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

(my) Experience with SmartSDR V4(+)

Hel, OE8TTR
Hel, OE8TTR Member ✭✭

Hi FLEX-/V4 fellows,
I don't want to keep my experiences with SmartSDR V4 (and FLEX-6600) from you! :-)

My experiences/expectations with SSDR v4(+) on my FLEX6600 are rather mixed/disappointing, and I will probably revert back to V3.10.15 (at least everything worked reasonably well with that version!). Why? Because with V4 and the 6K6, I have so many SW bugs that I didn't have with V3.10! I have now installed V4+ a total of 3 times, each time strictly following FLEX's recommendations (DC, cold boot, etc.) – the third time, I didn't even import any profiles so as not to corrupt anything and to “start from scratch”. 
Result: Still the same bugs/crazy behavior! My conclusion: Currently unusable with my FLEX6600 and definitely not worth the purchase price!

But let me start with the positive:
...The only positive effect I have observed (and I am surprised that no one has commented on this difference to V2/3 yet - not even from FLEX, Hi) is that in SPLIT mode, or with multiple open slices, the NF no longer drops as much and is therefore much more effectively distinguishable in the left/right NF channel. This has been problematic with low/weak signals – it's better in V4 now (But still significantly worse than the rice box competitors).

But now to the negative aspects and the BUGS, which are my main focus:
...NB/WNB: are hardly effective (okay, they were/are rather forgettable in V3 too, hi) – not to mention the lack of controls.
...NR: works better than in V3, but the signal loss is much too high and cannot be mitigated in any way due to the lack of a control option (almost all of the “rice box competitors” can do this (much) better!).

...ANF: works, but again no possibility for individual adjustment (no controls! Too much attenuation for low signals!).
But ANF has another, even more serious “major bug” (at least with my 6600)! This bug can be described as follows: If CW is preset for a selected band, then ANF works, but if for example, SSB is preset for this band and you then switch to CW, activating ANF completely masks the signal noise with a loud, endless "beep-beep -beep“ (on the NF side, of course!). If you then activate NR as well, you suddenly have no NF at all! Switching NR off again results in endless ”beep-beep-beep"! Switching ANF off results in a return to normal! This can be repeated as often as you like! If the CW setting remains and you change the band arbitrarily and then return (CW is still preset), then ANF works and NR is also possible at the same time – if that's not a fatal bug, then I don't know what is!!!
...DIV: Long awaited (...) and it works... on the slice display... but has NO function in real life... REALLY? But it gets worse... when I activate ESC (on the 6600), it results in a loud, endless "Beeeep" (NF) and ANT1 shows S9+++ on the S-meter in Slice-A... ****...

Does anyone else have this or similar “problems” and perhaps a solution/suggestion (apart from opening a service ticket, hi)? If so, every hint is welcome - it's definitely worth reporting or trying again!

My personal conclusion at the moment is that SmartSDR is increasingly developing in the direction of “intelligence-degenerative mass suitability” (the SW/AI knows/can do better than the user) – but there are still supposed to be "DXers" who attach particular importance to being able to “tease out” weak signals even in increasingly challenging environments. This is certainly not the case with a “one size fits all” approach!
If the whole thing weren't so sad, it would actually be laughable - for my part, I will think very carefully about whether I really want to “upgrade” to an SDR from the 8K series, because at some point enough is enough (and yes, I've been with FLEX since Gen1/FLEX-1000...).

Oh yes, I almost forgot... my 6600 is going in for service soon to have “corroded/sticky relays” replaced... Almost all of my previous FLEX units had to go to the service workshop at least once – in contrast, I have TRXs here that are around 40 yrs old and have been working without complaint and without repair since day 1 – but that's another topic...

73 de Hel, OE8TTR

Comments

  • Hel, OE8TTR
    Hel, OE8TTR Member ✭✭

    …again back on V3.10.15 and everything works as before - next try after a new release/bugfix… :-)

  • Troy NW1B
    Troy NW1B Member ✭✭

    Here is my quick assessment of the new structure. I'm not sure but it seems that Flex might have it backwards. One should NOT pay a premium for early access as you'll just have to work thru the bugs while if you waited 30 days it typically gets worked out.

    So I'd propose early access be the discounted rate and after it's all worked out , that be the full price.

    Ok so I'm being flip.. but really , I just can't see paying extra just to have to spend all this time getting things back up and running. I can wait the 30 days…

    I've said it before, I'm not in this for the computer aspect so I really don't enjoy the troubleshooting. I'm really surprised at all the bugs that happened when I pushed to V4 ( I did just the basic NO PAY upgrade). I can't imagine the issues with the new features versions that you pay for.

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.