o.biz
Onderwerp: Re: [Flexradio] Spam: Question about CAT/Console logic
Hi Jim,
Keep up the pressure.
It's kinda amusing to read about PowerSDR regressions in one mail, and
the lack of formal api's and documentation in the next.
I spent a life time (successfully) developing complex
Rob Dennison wrote:
> Grab the cash!
And stop bloviating myself? Not for a million bucks. Well, maybe.
73
Frank
AB2KT
___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz
Archive Link
Hi Frank,
Grab the cash!
Rob
On Thu, 11 Oct 2007 12:20:09 -0400 Frank Brickle <[EMAIL PROTECTED]>
writes:
> Rob Dennison wrote:
>
> > Keep up the pressure.
>
> I don't think you quite understand. There *is* no leverage here.
> There are only two things that matter: (1) lines of working sou
Rob Dennison wrote:
> Keep up the pressure.
I don't think you quite understand. There *is* no leverage here.
There are only two things that matter: (1) lines of working source
code (2) cash.
*Every*thing else is bloviation.
73
Frank
AB2KT
___
Flex
Hi Jim,
Keep up the pressure.
It's kinda amusing to read about PowerSDR regressions in one mail, and
the lack of formal api's and documentation in the next.
I spent a life time (successfully) developing complex hardware/SW
systems. We never ever allowed prototypers to develop production SW
Jim Lux wrote:
> OK.. but that shows giving an error like "badarg" (if I feed you a float
> when you want an int, for instance).. but, where is the information
> about the semantics of a message (e.g. is it Hz or MHz) maintained?
Sorry, the free answer line has run out. Further details available
At 03:49 PM 10/10/2007, Frank Brickle wrote:
>Jim Lux wrote:
>
> > Is it the intention to follow these recommendations?
>
>The model we're following is the source distribution for ejabberd.
So, then, we can expect to need to create (or read) something along
the lines of
http://www.process-one.net
At 03:39 PM 10/10/2007, Frank Brickle wrote:
>Jim Lux wrote:
>
> > I note that Thompson's thesis makes lots of mention of WBF (Well Behaved
> > Functions) implemented within OTP that raise exceptions when the
> > specification doesn't describe what's supposed to happen in the
> > circumstances tha
Jim Lux wrote:
> Is it the intention to follow these recommendations?
The model we're following is the source distribution for ejabberd.
73
Frank
AB2KT
___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/fle
Jim Lux wrote:
> I note that Thompson's thesis makes lots of mention of WBF (Well Behaved
> Functions) implemented within OTP that raise exceptions when the
> specification doesn't describe what's supposed to happen in the
> circumstances that have occurred. (p126, Rule2)...
I think you mean Arm
At 02:37 PM 10/10/2007, Frank Brickle wrote:
>Jim Lux wrote:
>
> > (Which seems to put a huge burden on the receiving node's error
> > reporting infrastructure)
>
>Lifting that burden is one of OTP's main jobs.
ALthough Thompson seems to assert that the receiving node is supposed
to put enough de
At 02:34 PM 10/10/2007, Frank Brickle wrote:
>Jim Lux wrote:
>
> > And presumably, those messages to the DSP software and RF hardware are
> > defined somewhere? (if only implicitly in the fact that sender node and
> > receiver node have consistent software that has common semantics, i.e.
> > is Fre
Jim Lux wrote:
> (Which seems to put a huge burden on the receiving node's error
> reporting infrastructure)
Lifting that burden is one of OTP's main jobs.
73
Frank
AB2KT
___
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/m
Jim Lux wrote:
> And presumably, those messages to the DSP software and RF hardware are
> defined somewhere? (if only implicitly in the fact that sender node and
> receiver node have consistent software that has common semantics, i.e.
> is Frequency in MHz or Hz, etc.)
Of course. The significant
At 01:10 PM 10/10/2007, Frank Brickle wrote:
>Bob Tracy wrote:
>
> > The code I'm playing with now runs a little differently, it interfaces
> > directly with the radio API (whatever that turns out to be). I have been
> > using an API of my own design for testing in lieu of anything concrete from
>
At 12:49 PM 10/10/2007, Frank Brickle wrote:
>Bob Tracy wrote:
>
> > The co
>(2) A little chunk of data arrives at the node's doorstep. The
>node is then responsible for making sense of the CAT command
>according to *its own* internal model of the radio. In other
>words, it's this node that thin
Bob Tracy wrote:
> The code I'm playing with now runs a little differently, it interfaces
> directly with the radio API (whatever that turns out to be). I have been
> using an API of my own design for testing in lieu of anything concrete from
> the Flex guys. It probably will have to change give
Bob Tracy wrote:
> The code I'm playing with now runs a little differently, it interfaces
> directly with the radio API (whatever that turns out to be). I have been
> using an API of my own design for testing in lieu of anything concrete from
> the Flex guys. It probably will have to change give
Jim,
I replied directly to you with a relatively long message before I saw you
had posted this on the reflector. I repeat it here less the attachments.
.
Jim,
Yes, that is the basic strategy for all CAT commands in the current
architecture. Some of the console properties were in ex
19 matches
Mail list logo
