"One Program to bring them all, and in the Network bind them..."
It is a testament to the power and flexibility of the Flex 6000 Series, that a product that has been available for a few years is still capable of so many more features as its software evolves and develops.
We are very fortunate to have some great programmers coming up with third party applications that extend SSDR's functionality.
One of the problems, as I see it, is that the present software architecture doesn't seem to allow for multiple controlling third party applications (i.e. if you use DDUtil, you can't use FRStack, or Pegasys Plus, or... - you get the idea).
Is FRS planning on opening up the third party control access, perhaps with some controls for conflicting command recognition, so that more than one third party utility can be used with another? At least, until/unless SSDR merges their features into itself?
Perhaps some future version of SSDR should allow a "shell" function, where the proper arrangements of script files will allow similar additional features, while being routed within SSDR???
Just think (and dreaming) out loud.
It would seem that that the hardware within the Flex as it stands is pretty busy and it might degrade the core functions to add "bells and whistles." I have thought about this also, and it would seem a more logical path would be to add external (maybe internal) hardware to take over these other tasks and keep the radio, itself, concentrated on the radio functions.
While FlexLibs are a great example of Object Oriented programming software as the ethernet protocols below, you can't say the same for SSDR.
People is a bit frightened when have to deal with: SSDR, SDR-Cat, SSDR-DAX-Control, DDUtils, FLDigi, LP-Bridge and CW-Skimmer.
I hope that starting from 2.0 realeases things will go better.
As far as I know, FRSStack, DDUtil, etc. call all coexist unless each has made assumptions about what their role in the world is and it conflicts with others... What doesn't work that should?
I am not sure what anyone is talking about. In order to compliment the functions of the Flex, it is necessary to set up a computer adjacent to the Flex to run these extra functions like rotor control. I think some hope that all of these functions will be accessible from the Flex directly. For example, wouldn't it be nice if the 6000's would send frequency data directly to a SteppIr so that DDUtil would not be needed.
That situation can be mirrored with SSDR and make it even more attractive to even those that would not consider an SDR for their shack.
I chuckle at these comments , especially Jims above, as this is exactly where I am at with my equipment setup today. A few month ago I posted a problem, and only found time a few week ago to get my remote station to work over my Local WAN/LAN setup (700 meters apart). Now I'm finding that I have to use DDUTIL, plus VAC's or Vcom's to get the SteppIR, Alpha-spid Rotor, and the LP-100A to all dance together. I have come to the conclusion that a remote computer is need for all these bells and whistles. I'm looking into using HRD to provide some help here. So my learning curve is still straight up!! Cheers K.
Simon Lewis really hit the nail on the head with his fanless small solid-state computer pointing that not only do we need third party software but, third party hardware. Perahps, like the Maestro, Flex will come out with a piece of enhancing hardware on the radio side.
- 4407 Conversations
- 1185 Followers
- 2503 Conversations
- 509 Followers
- 3007 Conversations
- 747 Followers
- 684 Conversations
- 138 Followers
- 2464 Conversations
- 719 Followers