Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread Tim Ellison
No.  They are not software defined radios.

-Tim



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken
Sent: Monday, November 19, 2007 10:54 PM
To: FlexRadio@flex-radio.biz
Subject: [Flexradio] Power SDR w/other radios

Hello,

I have been using the new Flex-5000 and loving it!
However, I also have a TS2000 and an IC7000.  Can the Power SDR be used
with either one of these radios?

Thank you.

Ken
K3YI

___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/


___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/



Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread Jim Lux
Quoting Tim Ellison [EMAIL PROTECTED], on Tue 20 Nov 2007 07:40:14 AM PST:

 No.  They are not software defined radios.

See other lengthy post about the semantics of software defined  
radio. In short, software defined can mean whatever you want it to  
mean.

More correctly, they are non-user reconfigurable software defined  
radios that are incompatible with PowerSDR.

A better statement is that PowerSDR's general design is compatible  
only with Flex-Radio style hardware architectures, and it only  
includes hardware drivers for the SDR1000, Flex5000, and SoftRock. (or  
radios with essentially identical interfaces).

jim, w6rmk

___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/



Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread Philip Covington
On Nov 20, 2007 11:27 AM, Jim Lux [EMAIL PROTECTED] wrote:
snip
 A better statement is that PowerSDR's general design is compatible
 only with Flex-Radio style hardware architectures, and it only
 includes hardware drivers for the SDR1000, Flex5000, and SoftRock. (or
 radios with essentially identical interfaces).

 jim, w6rmk

I use PowerSDR with the QS1R receiver board.  The QS1R does not appear
as a sound card to the PC.   I have to add four lines of code and
recompile PowerSDR to make it work with QS1R:

InitQS1R();
ExitQS1R();
SetFrequency(float value);
GetBlock(float * real, float * imag, int length);

A class named qs1r.cs implements these functions by calling into a C
dll that talks to libUSB.

So PowerSDR is pretty versatile and adaptable...

73 Phil N8VB

___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/



Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread k5nwa
Jim Lux wrote:
 
 The IC7000 *is* a software defined radio, just the software happens to  
 be a prom that is not user changeable.
 
 
 
 jim, w6rmk
 
 

Darn what ever happened to words having meaning, I guess that went with 
the politically correct crowd.

Software is soft versus Firmware which is firm and not changeable on 
the fly. Then there is hardware which is wired together therefore very 
hard to change at all.

So if you allow words to mean what they say a Software Define Radio must 
have it's code in RAM so it can be easily changed hence soft.

This reminds me of an discussion I had with a fellow on another list, he 
called the SDR-1000 a Superheterodyne receiver instead of a Direct 
Conversion Receiver. The only problem with his argument was that the 
Super in Superheterody does not stand for great it stands for 
Supersonic, or beyond hearing which unfortunately the SDR-1000 fails.

Back to my cave.

Cecil
k5nwa

___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/



Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread Duane - N9DG

--- Jim Lux [EMAIL PROTECTED] wrote:

 Actually, terms like SDR get bandied about quite a bit with
 different  
 people meaning different things.  Here's some background.
 flame suit on.. this gets controversial

For me personally, Joe average(?) ham, I'm not really that
concerned with all the hair splitting definition semantics of
what SDR is or isn't. To me it all really comes down to
simply this:

It's all about the 'S' in 'SDR'. And the if the 'S' isn't
routinely changing the 'D' significantly, then all you have
left is just 'R'.

So for me most of my future radio dollars will be directed
toward radios with lots of mfg.
supported/encouraged/permitted activity in the realm of the
'S'  'D', the 'R' will then take care of itself. A lot of
ham radios that do fit the typical definition of 'SDR' are
failing miserably when it comes to my stated position above.

And I'm finding it increasingly difficult to even consider
radios that have large HW constraints to their SW
define-ability.

Duane
N9DG





  

Be a better sports nut!  Let your teams follow you 
with Yahoo Mobile. Try it now.  
http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ

___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/



Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread Philip Covington
On Nov 20, 2007 12:33 PM, Jim Lux [EMAIL PROTECTED] wrote:
 Quoting Philip Covington [EMAIL PROTECTED], on Tue 20 Nov 2007
 08:42:01 AM PST:


  On Nov 20, 2007 11:27 AM, Jim Lux [EMAIL PROTECTED] wrote:
  snip
  A better statement is that PowerSDR's general design is compatible
  only with Flex-Radio style hardware architectures, and it only
  includes hardware drivers for the SDR1000, Flex5000, and SoftRock. (or
  radios with essentially identical interfaces).
 
  jim, w6rmk
 
  I use PowerSDR with the QS1R receiver board.  The QS1R does not appear
  as a sound card to the PC.   I have to add four lines of code and
  recompile PowerSDR to make it work with QS1R:
 
  InitQS1R();
  ExitQS1R();
  SetFrequency(float value);
  GetBlock(float * real, float * imag, int length);
 
  A class named qs1r.cs implements these functions by calling into a C
  dll that talks to libUSB.
 
  So PowerSDR is pretty versatile and adaptable...

 This is interesting..
 How do you integrate that into the UI?  Seems that there would be a
 fair number of places in console that need tinkering with to make it
 work.  Maybe not?

No other changes needed - just adding those 4 function calls takes
care of it (along with adding the qs1r.cs class that does the
DllImport of the qs1r.dll).  Everything else (firmware and fpga
loading) is done automatically in the call to InitQS1R().  It
literally takes me 5 minutes to download the latest PSDR in SVN, add
the above, and then recompile.

73 Phil N8VB

___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/



Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread Jim Lux
Quoting k5nwa [EMAIL PROTECTED], on Tue 20 Nov 2007 08:40:44 AM PST:

 Jim Lux wrote:

 The IC7000 *is* a software defined radio, just the software happens  
  to be a prom that is not user changeable.



 jim, w6rmk



 Darn what ever happened to words having meaning, I guess that went with
 the politically correct crowd.

 Software is soft versus Firmware which is firm and not changeable
 on the fly. Then there is hardware which is wired together therefore
 very hard to change at all.

 So if you allow words to mean what they say a Software Define Radio
 must have it's code in RAM so it can be easily changed hence soft.


What about if it's stored in EEPROM?  Changeable (soft), yet static (firm)

At work, we've sort of gravitated to
software - code that runs on a CPU
firmware - what's inside the FPGA
hardware - what's been soldered

This still leaves open a lot of discussion (what do you call something  
that runs on a microcontroller instantiated in a FPGA or on one of the  
powerPC cores in a Virtex Pro?)

Is Verilog software and the compiled bitstream firmware?

And, this varies from some common other usages:
hardware - what cannot be changed
firmware - what the manufacturer can change at manufacturing time,  
but users cannot
software - what the user can change, post delivery

To a certain extent, in the business world, the semantics are driven  
by institutional requirements.  Most places have different validation  
and test requirements for hardware and software (not much point in  
pyro shock or environment testing software, code walkthroughs don't do  
much for RF hardware designs).  But there's always those boundary  
cases.. Is a CPLD a hardware component and the logic that defines its  
function software? Or, is the programmed part the hardware  
component. What about a anti-fuse programmed Actel part?  What about a  
Xilinx or Altera with configuration RAM loaded from an offboard EEPROM.


  There's a sort of bifurcation in configuration management too.   
Hardware has drawing trees and the like.  Software has code  
repositories and tools like CVS,SVN, SourceSafe.

And there's other issues: How do you define interface control  
documents with the logic able to be changed at run time? For a complex  
ASIC you can create a datasheet that lays out the control and status  
registers and the timing behavior, etc..  What about that same  
function instantiated as part of a bigger design in a 6 megagate part  
like a 6000 series Virtex 2.

Such issues are what I get paid to work on these days..for spacecraft  
radios, NASA is a small volume customer that is thrifty, much like  
hams, so we can't just dictate thou shalt do X (like DoD can, buying  
radios in billion dollar lots), but we still want to get some of the  
benefits of open software/firmware standards for those radios. We also  
are like hams in that we want long useful life for the hardware (We  
want to use that spare $2M radio we bought for the 1998 mission that  
we have sitting on the shelf for a 2010 mission.  Read really cool  
thing I found at a hamfest 2 years ago).  Just like hams, we also  
like to have all the functioning and internals laid out for us so we  
can tinker and modify, or just understand what it will do in an  
off-nominal situation(i.e. no magic proprietary modem ASIC).  We tend  
to be concerned about efficiency because space qualified processors  
are a couple generations, if not more, behind... we're just starting  
to use a 100MHz SPARC V8 as a bold advance from a 25 MHz SPARC V7, no  
multi GHz Intel CoreDuos or AMD QuadCores flying to Mars or Jupiter  
any time soon. And besides, when all you've got is a 200W solar panel,  
you don't want to burn all your Joules on computing..you want to leave  
some to run that RF Power Amplifier.


Our challenge is figuring out what the right level of abstraction and  
specification is.  Too general, and the standard is worthless.  Too  
specific, and the compliance cost to conform exceeds any of the  
speculative savings from having a standard.  The manufacturers all are  
more than happy to quote you a price to comply to whatever standard  
you care to give them.



 This reminds me of an discussion I had with a fellow on another list,
 he called the SDR-1000 a Superheterodyne receiver instead of a Direct
 Conversion Receiver. The only problem with his argument was that the
 Super in Superheterody does not stand for great it stands for
 Supersonic, or beyond hearing which unfortunately the SDR-1000 fails.


And hey, since there's another mix and filter operation in the  
software, is it a single conversion or double conversion receiver?  
What if the A/D sampling operation is used as a downconversion (in  
bandpass sampling).  Many oxen are gored, many ricebowls spilled,  
etc, from such descriptions, if only because the terms come with some  
baggage from previous experience. (That's why Analog Devices and Maxim  
describe their I/Q parts as Zero-IF rather than direct 

Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread Jim Lux
Quoting Duane - N9DG [EMAIL PROTECTED], on Tue 20 Nov 2007 08:56:38 AM PST:


 --- Jim Lux [EMAIL PROTECTED] wrote:

 Actually, terms like SDR get bandied about quite a bit with
 different
 people meaning different things.  Here's some background.
 flame suit on.. this gets controversial

 For me personally, Joe average(?) ham, I'm not really that
 concerned with all the hair splitting definition semantics of
 what SDR is or isn't. To me it all really comes down to
 simply this:

 It's all about the 'S' in 'SDR'. And the if the 'S' isn't
 routinely changing the 'D' significantly, then all you have
 left is just 'R'.

 So for me most of my future radio dollars will be directed
 toward radios with lots of mfg.
 supported/encouraged/permitted activity in the realm of the
 'S'  'D', the 'R' will then take care of itself. A lot of
 ham radios that do fit the typical definition of 'SDR' are
 failing miserably when it comes to my stated position above.

 And I'm finding it increasingly difficult to even consider
 radios that have large HW constraints to their SW
 define-ability.


You're not alone.

There are some practical problems.. sometimes the hardware constraints  
come from some performance reason (however, semiconductors are getting  
better every day..20 years ago, a 10 MHz A/D with 10 bits was really  
awesome.  Now you can get 14 bits at 1GHz).  We're probably a ways  
from the HF nirvana of the 30 bit converter at 125 MSPS where you hook  
an antenna to the A/D, and you're done.  Likewise, high power  
amplifiers have their idiosyncracies that are not all entirely  
compensatable in software.

Probably a bigger issue is the legal one.  Hams are a small volume  
market compared to radios in general. The radio in general market has  
regulatory restrictions on just how flexible that radio can be to  
prevent users from just loading up a version of the software that  
radiates out of band or receives where you're not supposed to be  
listening.  So, a manufacturer that is trying to leverage commercial  
radio designs for the ham market (since the ham market can't support  
huge RD budgets) winds up building radios that inherently are  
not-user-modifiable. And, there's the Part 15 rules, too. (having the  
software in mask rom or OneTimeProgrammable PROM makes it easier to  
pass FCC muster for ham rigs.)

It's instructive to look at all the hoops that Icom had to jump  
through to get the IC-7000 approved.. their filings are on the FCC  
website.

Think of the complexities in modern autotuning HF amplifier designs..  
they have little microcontrollers that sense the RF frequency and turn  
the amp off if you're out of band, and you can bet that  
microcontroller isn't something you can easily modify.

We're faced with a real challenge.. It's easy to build a software  
radio based on a PC and a simple LO/QSE/QSD like the Flex or SoftRock  
that has instantaneous bandwidth of over 100 kHz.  Even if you put  
(closed non-modifiable) firmware into the DDS control that restricts  
the DDS frequency to the ham bands, you could receive and transmit 50  
kHz outside the bands.  Historically, this hasn't been a big problem  
(transmitting) because the radios were inherently narrow band.  Even  
if you were set on LSB, and tuned the VFO to 7. MHz, the most you  
could do is transmit something at 6.995 or so.  So the regulators have  
guard bands between the allocations and spurious emissions  
requirements to accommodate this.

The last thing we want the regulators to do is mandate hardware  
frequency limits (e.g. filters).  Nor do we want them mandating  
nonmodifiable firmware/software to achieve the same thing.

Jim, W6RMK


___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/



Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread Jim Lux
Quoting Philip Covington [EMAIL PROTECTED], on Tue 20 Nov 2007  
08:42:01 AM PST:

 On Nov 20, 2007 11:27 AM, Jim Lux [EMAIL PROTECTED] wrote:
 snip
 A better statement is that PowerSDR's general design is compatible
 only with Flex-Radio style hardware architectures, and it only
 includes hardware drivers for the SDR1000, Flex5000, and SoftRock. (or
 radios with essentially identical interfaces).

 jim, w6rmk

 I use PowerSDR with the QS1R receiver board.  The QS1R does not appear
 as a sound card to the PC.   I have to add four lines of code and
 recompile PowerSDR to make it work with QS1R:

 InitQS1R();
 ExitQS1R();
 SetFrequency(float value);
 GetBlock(float * real, float * imag, int length);

 A class named qs1r.cs implements these functions by calling into a C
 dll that talks to libUSB.

 So PowerSDR is pretty versatile and adaptable...

This is interesting..
How do you integrate that into the UI?  Seems that there would be a  
fair number of places in console that need tinkering with to make it  
work.  Maybe not?  I've been following the logic to control SDR1Ks and  
F5Ks, and there's a fair amount of back and forth between console and  
the device layers to configure them, make sure the firmware is loaded,  
etc.  I haven't looked at it in the context of if I had a minimalist  
abstract radio, how would i hook it in.

Jim, W6RMK

___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/



Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread [EMAIL PROTECTED]

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken
 Sent: Monday, November 19, 2007 10:54 PM
 To: FlexRadio@flex-radio.biz
 Subject: [Flexradio] Power SDR w/other radios

 Hello,

 I have been using the new Flex-5000 and loving it!
 However, I also have a TS2000 and an IC7000.  Can the Power SDR be used
 with either one of these radios?

   
You would be better off using a program like Ham Radio Deluxe for the 
TS2000 and IC7000.  You can also use HRD with the SDR1000 and Flex-5000 
although some functions wont work as the SDR/Flex programs have 
developed features which HRD doesn't fully recognise yet.

You can download HRD at http://forums.ham-radio.ch/

Dave (G0DJA)

___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/



Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread k5nwa
At 01:20 PM 11/20/2007, you wrote:
SDR defined and explained

http://en.wikipedia.org/wiki/Software-defined_radio



John P. Basilotto
W5GI
Chief Operating Officer
Marketing and Sales
Office  512 535-5266
FAX512 233-5143
www.flex-radio.com


You are quoting a definition that is subject to change at any minute, 
nice try but that is hardly proof one way or the other.

I have an account there, I could go in there and change it, so could 
anyone else. It even mentions that there are no references to 
authorities to insure correctness.

I'm even willing to bend the meaning of the words to accept Flash or 
EEProm memory, but unless it's changeable by the user, how is it any 
different from hardware that must be sent back to the factory for changes.


Cecil
K5NWA
www.softrockradio.org  www.qrpradio.com

Blessed are the cracked, for they shall let in the light. 


___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/



Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread john
SDR defined and explained

http://en.wikipedia.org/wiki/Software-defined_radio



John P. Basilotto
W5GI
Chief Operating Officer
Marketing and Sales
Office  512 535-5266
FAX512 233-5143
www.flex-radio.com
 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim Lux
Sent: Tuesday, November 20, 2007 11:28 AM
To: [EMAIL PROTECTED]
Cc: FlexRadio@flex-radio.biz
Subject: Re: [Flexradio] Power SDR w/other radios

Quoting k5nwa [EMAIL PROTECTED], on Tue 20 Nov 2007 08:40:44 AM PST:

 Jim Lux wrote:

 The IC7000 *is* a software defined radio, just the software happens  
  to be a prom that is not user changeable.



 jim, w6rmk



 Darn what ever happened to words having meaning, I guess that went with
 the politically correct crowd.

 Software is soft versus Firmware which is firm and not changeable
 on the fly. Then there is hardware which is wired together therefore
 very hard to change at all.

 So if you allow words to mean what they say a Software Define Radio
 must have it's code in RAM so it can be easily changed hence soft.


What about if it's stored in EEPROM?  Changeable (soft), yet static (firm)

At work, we've sort of gravitated to
software - code that runs on a CPU
firmware - what's inside the FPGA
hardware - what's been soldered

This still leaves open a lot of discussion (what do you call something  
that runs on a microcontroller instantiated in a FPGA or on one of the  
powerPC cores in a Virtex Pro?)

Is Verilog software and the compiled bitstream firmware?

And, this varies from some common other usages:
hardware - what cannot be changed
firmware - what the manufacturer can change at manufacturing time,  
but users cannot
software - what the user can change, post delivery

To a certain extent, in the business world, the semantics are driven  
by institutional requirements.  Most places have different validation  
and test requirements for hardware and software (not much point in  
pyro shock or environment testing software, code walkthroughs don't do  
much for RF hardware designs).  But there's always those boundary  
cases.. Is a CPLD a hardware component and the logic that defines its  
function software? Or, is the programmed part the hardware  
component. What about a anti-fuse programmed Actel part?  What about a  
Xilinx or Altera with configuration RAM loaded from an offboard EEPROM.


  There's a sort of bifurcation in configuration management too.   
Hardware has drawing trees and the like.  Software has code  
repositories and tools like CVS,SVN, SourceSafe.

And there's other issues: How do you define interface control  
documents with the logic able to be changed at run time? For a complex  
ASIC you can create a datasheet that lays out the control and status  
registers and the timing behavior, etc..  What about that same  
function instantiated as part of a bigger design in a 6 megagate part  
like a 6000 series Virtex 2.

Such issues are what I get paid to work on these days..for spacecraft  
radios, NASA is a small volume customer that is thrifty, much like  
hams, so we can't just dictate thou shalt do X (like DoD can, buying  
radios in billion dollar lots), but we still want to get some of the  
benefits of open software/firmware standards for those radios. We also  
are like hams in that we want long useful life for the hardware (We  
want to use that spare $2M radio we bought for the 1998 mission that  
we have sitting on the shelf for a 2010 mission.  Read really cool  
thing I found at a hamfest 2 years ago).  Just like hams, we also  
like to have all the functioning and internals laid out for us so we  
can tinker and modify, or just understand what it will do in an  
off-nominal situation(i.e. no magic proprietary modem ASIC).  We tend  
to be concerned about efficiency because space qualified processors  
are a couple generations, if not more, behind... we're just starting  
to use a 100MHz SPARC V8 as a bold advance from a 25 MHz SPARC V7, no  
multi GHz Intel CoreDuos or AMD QuadCores flying to Mars or Jupiter  
any time soon. And besides, when all you've got is a 200W solar panel,  
you don't want to burn all your Joules on computing..you want to leave  
some to run that RF Power Amplifier.


Our challenge is figuring out what the right level of abstraction and  
specification is.  Too general, and the standard is worthless.  Too  
specific, and the compliance cost to conform exceeds any of the  
speculative savings from having a standard.  The manufacturers all are  
more than happy to quote you a price to comply to whatever standard  
you care to give them.



 This reminds me of an discussion I had with a fellow on another list,
 he called the SDR-1000 a Superheterodyne receiver instead of a Direct
 Conversion Receiver. The only problem with his argument was that the
 Super in Superheterody does not stand for great it stands for
 Supersonic, or beyond hearing which unfortunately the SDR-1000 fails.


And hey, since

Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread Tim Ellison
All hair splitting, defining word definitions, etc, aside...

The significant part of the answer is the no part.  And in the case, no 
actually means no. :-)

-Tim



-Original Message-
From: Jim Lux [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 20, 2007 11:27 AM
To: Tim Ellison
Cc: [EMAIL PROTECTED]; FlexRadio@flex-radio.biz
Subject: Re: [Flexradio] Power SDR w/other radios

Quoting Tim Ellison [EMAIL PROTECTED], on Tue 20 Nov 2007 07:40:14 AM PST:

 No.  They are not software defined radios.

See other lengthy post about the semantics of software defined
radio. In short, software defined can mean whatever you want it to
mean.

More correctly, they are non-user reconfigurable software defined
radios that are incompatible with PowerSDR.

A better statement is that PowerSDR's general design is compatible
only with Flex-Radio style hardware architectures, and it only
includes hardware drivers for the SDR1000, Flex5000, and SoftRock. (or
radios with essentially identical interfaces).

jim, w6rmk

___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/



Re: [Flexradio] Power SDR w/other radios

2007-11-20 Thread Jim Lux
Quoting Tim Ellison [EMAIL PROTECTED], on Tue 20 Nov 2007 11:20:20 AM PST:

 All hair splitting, defining word definitions, etc, aside...

 The significant part of the answer is the no part.  And in the   
 case, no actually means no. :-)

 -Tim

But here's a fascinating thing... PowerSDR *could* support the IC7000  
or the TS2000B or the Orion or the ...

You could use PowerSDR's user interface to send commands to and get  
status back from the 7000.
You could feed the audio to and from PowerSDR, and use PowerSDR's very  
powerful filtering, AGC, recording, etc. features.


Granted, you don't get some of the performance aspects of doing the  
modulation and demodulation in the PC (like multiple receivers in the  
passband)


But that's kind of the cool thing about software radios in general..  
with half way decent interface abstractions, the RF hardware becomes  
just a peripheral interface, controlled as you like it.

It's sort of like the popularity of programs such as HRD.. they  
essentially abstract the radio's function and present a common user  
interface for all radios.


One could argue that maybe the direction to head for PowerSDR type  
products is to let UI specialists (HRD) take on that aspect of radio  
control, making the software like PowerSDR more of a radio abstraction  
layer that controls the RF hardware and the DSP processing.  CAT on  
steroids, if you will.

But, as you say, for today, PowerSDR doesn't support the IC7000 and TS2000.


Jim


___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/



Re: [Flexradio] Power SDR w/other radios

2007-11-19 Thread Dudley Hurry
Ken,

Nope..  Nearly all other radios are Software Controlled Radios,  the 
5K is a Software Defined Radio.The Softrock can be used with 
PowerSDR console also.

73,
Dudley
WA5QPZ

At 09:54 PM 11/19/2007, Ken wrote:
Hello,

I have been using the new Flex-5000 and loving it!
However, I also have a TS2000 and an IC7000.  Can the Power SDR be used
with either one of these radios?

Thank you.

Ken
K3YI

___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/

-- next part --
An HTML attachment was scrubbed...
URL: 
http://mail.flex-radio.biz/pipermail/flexradio_flex-radio.biz/attachments/20071119/18a75755/attachment.html
 
___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link: http://www.mail-archive.com/flexradio%40flex-radio.biz/
FlexRadio Knowledge Base: http://kb.flex-radio.com/
FlexRadio Homepage: http://www.flex-radio.com/