Maybe we should find out what computers the beta testers are using and if they are not experiencing the same problems, then perhaps they should actively market those computers at a reasonable price so that the Flex community could purchase them and not have all the issues that people are having now.
I think the Flexradio definitely is up and coming and has a great future, but just reading the reflector day by day it seems that the issues are with computers and software, not software and hardware. Am I wrong in that analysis, or not?
Mark Griffin, KB3Z
Indeed, it is a difficult situation. Many are new to this type of radio as well as inexperienced with computers and the blame always seem to tend towards Flex. I have never had any problems other than having a corrupt version of Windows I didn't even know I had until a couple of problems cropped up which were fixed by fixing Windows. However, of late, it seems most if not all the problems are with the 6300. It would be so interesting to find out if it is a Windows problem or a 6300 problem.
San Juan Island, Wa.
My understanding is that all the processing is done 'in' the
radio and the computer merely acts as a display system.
Having said that, I wonder if most folks have any idea how
to test software? In particular Operating Systems? Because, as I understand it,
Smart SDR is actually the 6 series OS.
To properly test and OS such as Windows 10 is virtually
impossible. This is because the number of possibilities is enormous - for example
think about the number of motherboard/processors/memory/graphics cards/memory/ hard
disk/power supply/BIOS combinations that it is possible to put together. Even for
Microsoft it would be almost impossible to make even one example of each of the
permutations that could exist.
And when you have made one of everything, now install your OS
and then start to install all the different software packages that users might want
to have on their computer. Now start your testing - see you in about 200 years with the completed bug free product?
I know how difficult this task could be - I once had to write a paper on the exact subject. It was 25 years ago and the number of possible combinations at that time was in the hundreds, not the million upon million that exist today.
However, this is not the problem that FRS is facing.
Smart SDR only runs on the 3 radios in the 6 series. Essentially, there are only 3 OS's that it will 'talk' to, Win 7, 8 & 10. So it is not a major problem from a testing point of view.
Reading through all the posts relating to problems with SSDR 1.5, it seems to me that approximately 90% of the problems reported are from users of the 6300.
That leads me to suspect that the code in SSDR 1.5 is causing the problem, NOT the version of Windows that the user is running.
I further suspect that the problem actually lies with the updating of the 6300 firmware. The reason for think this way is that, as far as I understand the situation, the 6300 is a 'cut down' version of the 6500 & 6700.
I have reverted back to SSDR 1.4.16 running on my trusty I7 and Win7 64bit Pro for the time being.
I have every faith that at some point in the future, hopefully not to far away, that the guys at FRS will find the source of the problem and give us a fix.
For me, the 6300 is still the best radio I have ever had in over 50 years of playing radio and if I could afford it, I would love a 6500 but I can't see it ever happening.
I'm not holding my breath for 1.5.1 - my radio works just great as it is!
In the meantime, thank you Flex for producing a beautifully engineered radio from both a hardware and software view.
We have a good team of dedicated testers that have been running v1.5 in various forms for months without issue. The software we released had been in our Alpha team's hands for about three weeks without incident. As anyone in the electronics or software industry will tell you -- we all wish that things would either always work or break hard. The hardest issues to find are ones that appear rarely or are selective about where they appear. Unfortunately, the luck of the draw on this one was that no one on the Alpha team experienced the issue. But we will find it and get everyone an update just as soon as we can. The good news is that downgrading is quick and easy.
As has been mentioned here and on the other post about this, the computer and computer OS is not and can not be involved. The FLEX-6000 radios do all of their signal processing inside the radio -- at no time did your samples leave the radio ;-) This means that a computer issue will not cause this to happen so my recommendation would be to not alter your operating system, reinstall Windows, etc. We used to do a test in the early FLEX-6000 days where we would get the radio on frequency and in the right mode and start a QSO and then shut off the computer in the middle of the QSO. It works just fine and you can complete the QSO, etc. We got some feedback that the loss of the computer (especially in the remote case) should stop transmit so you can't do this today, but it does illustrate the point that the computer is not involved in your on-air signal. These things will help other SDRs that depend strictly on the precise timings, buffering, jitter, latency, etc on Windows, but not the FLEX-6000.
I'm not suggesting that the software quality is perfect, but it's pretty good for what it is and it's getting better. I know that Flex has made a significant investment in improving software quality, but they're in uncharted territory and demanding appliance-like stability from an experimental platform is probably not realistic.
I know that some people will take offense to this, but these are experimental recreational devices and will probably never reach the level of stability that we see from more traditional radio architectures.
Mike - N8MSA
Took the plunge and upgraded my 6300 to 1.5. PC and 6300 upgrade went smoothly. I only deleted 1.4.3 and kept 1.4.11 prior to download. I did not delete cat nor dax but ensured both were closed prior to upgrade. So far my 6300 v1.5 is smooth, stable and reliable cw, ssb, and digital. WNB works but I do not see the same dramatic results as posted here and that is because my local noise is already low and NR feature does a better job of eliminating what and the type of noise that I do have. Thanks for the new features w/in 1.5.