Tim - As I tried to explain in the article, one of the prime reasons for incorporating FreeDV as a native mode of FlexRadio units is to differentiate FlexRadio's (truly) software defined radio architecture versus other vendors radios. FlexRadio can add FreeDV as a new mode; Icom, Kenwood, etc. cannot because their architectures are mostl…
Tim - As I tried to explain in the article, one of the prime reasons for incorporating FreeDV as a native mode of FlexRadio units is to differentiate FlexRadio's (truly) software defined radio architecture versus other vendors radios. FlexRadio can add FreeDV as a new mode; Icom, Kenwood, etc. cannot because their architectures are mostly hardware-defined. For a cutting edge HF radio designed in the 21st century, it would be nice, and RELEVANT if it were able to offer a new mode such as FreeDV that was also designed in the 21st century. Also, see the followup on this discussion in Zero Retries 0155.
Tim - As I tried to explain in the article, one of the prime reasons for incorporating FreeDV as a native mode of FlexRadio units is to differentiate FlexRadio's (truly) software defined radio architecture versus other vendors radios. FlexRadio can add FreeDV as a new mode; Icom, Kenwood, etc. cannot because their architectures are mostly hardware-defined. For a cutting edge HF radio designed in the 21st century, it would be nice, and RELEVANT if it were able to offer a new mode such as FreeDV that was also designed in the 21st century. Also, see the followup on this discussion in Zero Retries 0155.
Hi Steve - The API is super good news for FreeDV and radio hacking in general. Flex can focus resources on future R&D that way instead of FreeDV.