While we're on the subject of broken CC1000's...
I was originally mostly unsuccessful in using the 'standard' TOS mica2
radio until an xbow engineer directed me to the contrib/xbow tree.
I assumed that all that xbow/tos/CC1000* code was my savior. However,
just recently I found that it too uses the 'standard' code (as far as I
can understand my reverse engineering of the compile sequence anyway).
Do you know if the difference is just the more convenient make defines
and a higher default xmit power?
thx
MS
David Moss wrote:
The preset table is actually in the CC1000Const.h file. You'll see it's an
array of register values starting with:
static const prog_uchar CC1K_Params[6][31] = {
....
};
There are two functions you can call in your application in TinyOS 1.x to
adjust the frequency through the CC1000Control interface:
command result_t TunePreset(uint8_t freq);
command uint32_t TuneManual(uint32_t DesiredFreq);
The difference between TunePreset and TuneManual is that TuneManual actually
calculates what the CC1000 register values should be, and the TunePreset
contains pre-calculated values.
The problem is the default CC1000 stack is broken when it comes to changing
frequencies at runtime. So if you plan on doing runtime frequency changes,
you should really be using Rincon's CC1000 stack (stable but unsupported) in
tinyos-1.x/contribs/rincon/tos/lib/CC1000Radio
-David
_______________________________________________
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
