? How do I define
transmit power and frequency?
Cheers,
Urs
On 11/24/10 6:19 PM, Michael Schippling wrote:
Do you have antennas attached? And of course,
define the frequency and transmit power correctly?
Those were the two things that tripped me with mica2's.
MS
Urs Hunkeler wrote
I believe there is a TestSerial demo program in TOS2.x
that you could use as an example.
MS
José Eduardo S. C. Xavier wrote:
Can anyone help me to know how to send data via uart to telosB?
Thanks
search for the solution? inside those files?
regards
No dia 23 de Novembro de 2010 17:53, Michael Schippling
sc...@santafe.edu mailto:sc...@santafe.edu escreveu:
I believe there is a TestSerial demo program in TOS2.x
that you could use as an example.
MS
José Eduardo
on to VMWare installation, probably that is why not
too many people has post the problem.
Regards and thank you for the quick answer,
Javier.
On Sun, 14 Nov 2010 11:30:39 -0700, Michael Schippling sc...@santafe.edu
wrote:
I suppose it's too late to look at your old install,
but can you run
I suppose it's too late to look at your old install,
but can you run this in your new cygwin shell:
cygcheck -s
It will dump out a lot of info about paths and version
numbers, one of which should be the base dll ID, like:
Cygwin DLL version info:
DLL version: 1.5.18
AFAIK,
correctly - then simply connecting the ADC to
ground should not have worked at all? And the voltage that I was
reading - that came as a feedback from the ground wire then?
Thanks again!
On Tue, Nov 9, 2010 at 1:31 AM, Michael Schippling sc...@santafe.edu wrote:
Less than an order of magnitude
Less than an order of magnitude off...
Not bad for failing memory circuits.
I think the ATMEGA might have been around 250K.
Or maybe the 165f818 PIC...
MS
Yong, Chee Yeew wrote:
Not being a lot of help here, but I measured / calculated the input
impedance of the MDA300 ADC input recently, and
By mentioning XMDA300 I will guess that you are using Moteworks.
A quick look at the RelayM.nc file shows that it is a simple driver
for turning an I/O pin on and off, so it's probably the code that
you want to use in your app. If your moisture sensor is on the same
mote as the relay you probably
The Moteworks system from Memsic (ne Crossbow) has drivers for the
MDA320, but I'm not sure if any of the current TOS 2.x versions
support it directly. I don't see anything in the last TOS1.x
which I use. Maybe someone using T2 can point you to other sources.
As for documentation, it's pretty
Are you sure your CLASSPATH is correct?
If there a directory named net/tinyos/util
I think you may be missing the . in CLASSPATH.
If the util directory is not there then something
is wrong with the install and you could try redoing it.
If there is a good tinyos.jar in CVS someplace you should
be
The received RSSI value is not sent over the serial connection
between a base-station and the host. You will need to modify
the base-station code to extract the rssi from the message trailer
and insert it into the message body before it forwards the message.
Long ago I remember some discussion of
What are you reading through the sensor board via ADC?
AFAIK there are a few mostly useless sensors, temp, light, sound
on that board. If you are not using those but are connecting to
some external devices maybe you can just eliminate the board
and connect directly to the 51-pin I/O. I have a
-2.1.1/support/sdk/java/net/tinyos/tools. This doesn't work
because I don't know where the Listen.class file is located so I'm just
sure where to put the plot.class file.
On Wed, Oct 20, 2010 at 4:18 PM, Michael Schippling sc...@santafe.edu
mailto:sc...@santafe.edu wrote:
You should
You should probably read a bit about Java and it's ideas of program
structure before you really frustrate yourself...
But to answer your question:
Basically package names and directory structures should be congruent.
Put your file in the same directory as Listen.java if you want to
run it with
for your help！
Best regards
2010/10/19 Michael Schippling sc...@santafe.edu mailto:sc...@santafe.edu
Usually the message sent to the I2C device
contains the register address along with
the data. Look carefully at the message
format spec for your device.
MS
bin chen
Usually the message sent to the I2C device
contains the register address along with
the data. Look carefully at the message
format spec for your device.
MS
bin chen wrote:
Hi,
I need to connect an I2C device to the telosb mote. The I2C device
has a device address, besides, it has
You haven't included the part of your program where 'msg' is declared,
so it's hard to say exactly why the compiler is whining...
The problem with packet is that variables can only be declared at the
beginning of code blocks in C and Nesc. A code block is surrounded by
{ } braces, so declarations
Prior to TOS1.1.10 one could use a Timer() interval of 1,
but at that version a lower limit of 3 was instilled --
I think to avoid some kind of timing problem with micaz's.
The limit was enforced by having start() return an error
rather than just upping the ante and returning as it seems
to be
export MOTECOM=ser...@com19:tmote
This is a holdover from my use of tmote sky devices
but I think :telosb also works. I've had problems
with COM ports over 15 on WinXP. YMMV.
Don't use S.F. but there's probably a command option
to set the server port number.
MS
z qin wrote:
Hello,
I am
This won't be much help because I've never used UartStream...
The fact that you get a single byte would point to there being
some kind of state failure in your program that disables
subsequent receptions. In fact I would be surprised if you
really need to control the interrupt directly in your
If you are using TOS2.x I hear the TestSerial parogram
does bi-directional communication. You can also see my
posted code for a (possibly too complicated) example
using TOS1.x:
http://www.etantdonnes.com/Motes/schipTOS.zip
MS
Salman B.M.R wrote:
Hi all
I want to know how to send
Make sure that is the JRE you are using when you run programs.
type java should tell you the bin directory.
MS
JC de Dios wrote:
Hello,
After searching a lot from Google and following some instructions, I
still cannot find the solution to my error. When I run any java
application
IIRC, Xmesh handles messages just like regular old TOS
in respect to message type dispatch. You need to have
a receive method configured, and may have to address the
message to the specific nodeID, rather than BCAST.
I think most messages are just re-broadcast to the
base station rather than
You basically need to send messages in sequence, one from the
sendDone() of the other. I have in my config file:
// Status replies to send
RoboMsgM.RStatusMsg - RComm.SendMsg[AM_ROBOSTATUSMSG];
In RoboMsgM.nc, a method that does the first, radio, send:
call RStatusMsg.send( TosBaseId,
If it's bipolar maybe it needs a shrink?
sorrycouldn't resist.
You'll need to bias the signal up such that it never
goes below 0v or above the nominal 3.3v supply voltage.
It might be as easy as using a couple of resistors, one
to the signal and one to the supply. I'd start with
around
I don't know of any software fix for a signal that
is out of the range of the ADC input.
MS
Naila Munaf wrote:
You mean i should use a DC level shifter in hardware so that signal will
be positive all the time,But im preferring not to use it,instead i want
to make some changings in
and this is my question why?
Thanks, Omar
-Original Message- From: Michael Schippling
[mailto:sc...@santafe.edu] Sent: 08 August 2010 17:22 To: Omar
Bouzid Cc: 'Tinyos-help@millennium.berkeley.edu' Subject: Re:
[Tinyos-help] Why my received signals incoherent?
Please, can you
Look carefully at the arguments in these two calls from sendDone()
and then send us a new question:
call SendMsg1.send(TOS_BCAST_ADDR, msg1 ,sizeof(struct TreeReqMsg));
call SendMsg2.send(TOS_BCAST_ADDR, sizeof(struct TreeReqMsg),msg2);
MS
Mitra Baratchi wrote:
Dear all
I am
to
noise effect rather than to the random inconsistent behaviour in the
functionality of sensor nodes themselves. So, what do you think?
Again your help is highly appreciated. Omar
-Original Message- From: Michael Schippling
[mailto:sc...@santafe.edu] Sent: 09 August 2010 17:16
You can pass options to the GCC compiler by putting this
in your makefile:
CFLAGS += -S
That particular option causes the compiler to stop before
the assembler pass. When I tried it with a mica2 compile
I got a build/mica2/main.exe file that actually contained
the generated assembly code. YMMV
Please, can you define coherent signals?
What is your sample rate? If you are trying to sample sound
you will get very curious results if you are below the Nyquist
frequency of your signal.
MS
Omar Bouzid wrote:
Hi all,
I'm using three sensor nodes (MICAz + MTS310), positioned at the same
I do mobile robotics with mica2's as the controller.
I use them purely for the two-way radio and low power
consumption. My system is in a small area -- 4x8 foot
table at most -- so ad-hoc networking plays no part.
I have noticed but not explored work being done on mobile
nets with changing
I have successfully sent a message from a PC host to an
Xmesh node, however I personally have not tested that in
a multi-hop environment.
On the node the message is configed as:
// messages we receive
App.CalibMsg - MULTIHOPROUTER.Receive[CPAM_CALIBMSG];
Which causes this method to be
You should be able to use VoltageC to get the value.
The difference in the two DemoSensorC examples you
have is that someone decided to use DemoChannel
as an intermediate name rather then DemoSensor,
probably to enhance code re-usability (not).
It may be that the simulator implementation returns
In a .bat file or from the DOS Command line:
set motecom=ser...@com19:tmote
Or you can use the MyCompuker-Properties-EnvironmentVariable
panel to set it for all time.
MS
ashkan ekhtiari wrote:
Hi michael
You wrote to correctly set the MOTECOM environment, would you please
Your update() code looks like it should work
to bump down each reading by one on each call.
You could try testing it standalone, put in print
traces, or run in a debugger to see what is really
going on...
MS
CHEN WEIMING wrote:
Hello, all:
I edited the java code in Oscilloscope to display
config commands manually in my cygwin
shell and then do the env check .. this classpath error goes off..
I am totally confused why so ? and how I can make it solve..
Thanks
HS
--- On *Thu, 29/7/10, Michael Schippling /sc...@santafe.edu/* wrote:
From: Michael Schippling sc
new in cygwin and tinyos.. Just learning it..
Please elaborate your previous mail guideline ..
I couldn't understand much ...
In which file should i place my command written in tinyos.sh file?
Thanks
HS
--- On *Wed, 28/7/10, Michael Schippling /sc...@santafe.edu/* wrote
The point of the locked variable is to prevent two sends
from being done at the same time. You should not use a second
locked2 variable in your second send. Although I would
expect some to most of the messages would not overlap.
I didn't work through your random timer calculation,
but maybe just
My understanding is that scripts in the /etc/profile.d
directory get run by bash when it starts a login shell.
This should be done by /cygwin.bat as:
bash --login -i
If that isn't happening, you could try sourcing the
script explicitly in your .bashrc
Also give a gander to man bash for more
The usual way to add an option to the nescc compile line
from your app/Makefile is this:
PFLAGS += option
so this might work:
PFLAGS += TINYSEC=true
Although you might need it to be -DTINYSEC=true if it is
a #define being set. You should see whatever you put in
PFLAGS in the nesc
: [Tinyos-help] String manipulation
To: Michael Schippling sc...@santafe.edu mailto:sc...@santafe.edu
Hi, thanks for your help.
I actually misstyped when i was writing the previous message.
I have two keys, k1 and k2 declared like this: uint8_t k1[10] =
1234543253; uint8_t k2[10
to be done first?
MS
Francesco Ficarola wrote:
Michael Schippling ha scritto:
I'm not certain that read() is queue-able. You may need to
start a subsequent read() from the readDone() of the previous.
First try putting your led1 toggle in Sensor_7 done, because
(if they are not queueing) that one
Integer arithmetic is fully supported, although the ATMEGA
instruction set is 8-bit -- maybe the MSP is 16bit, I forget --
so there is some overhead. I'm not sure if 64 bit values are
usable but I believe anything up to 32 bit works fine.
There is a lib for float (4 byte) arithmetic, but there is
, 7/19/10, Michael Schippling /sc...@santafe.edu/* wrote:
From: Michael Schippling sc...@santafe.edu
Subject: Re: [Tinyos-help] [*] Regarding sending and receiving
To: Kartik Siddhabathula siddhabathulakar...@yahoo.com
Cc: harsh...@cse.iitk.ac.in, TinyoS help
tinyos-help
This works for me on mica2:
void func()
{
uint8_t key1[10] = 1234543253; uint8_t key2[10] = 1234543323;
int i ;
uint8_t result[10];
for(i = 0; i 10; i++)
result[i] = key1[i] ^ key2[i];
}
You did name key1,2 differently (k1, k2) in your code snippet
but that should have given a syntax
I'm not certain that read() is queue-able. You may need to
start a subsequent read() from the readDone() of the previous.
First try putting your led1 toggle in Sensor_7 done, because
(if they are not queueing) that one is probably the one that
actually executes. Also try doing just one read() and
Messages will be lost. Get over it...
The number will vary depending on the distance
between motes, and whether they can all hear
each other (see Hidden Node Problem). I think
TOSSIM has a whole modeling system for testing
message failures, but I've never used the sim.
I also found that
Muddle through the doc/tutorial pages to get an idea
how to program TOS and reqire the demo apps.
MS
Walter Bishop wrote:
I'm trying to measure temperature and/or light intensity from a
mda100CB attached to a micaz mote.
I've read the tinyOS documentation and tutorials, and tried the Blink,
send me your modified mica2 TOSBase code may it
help me .. i shall be thankful to you for your this kindness
--- On *Fri, 7/16/10, Michael Schippling /sc...@santafe.edu/* wrote:
From: Michael Schippling sc...@santafe.edu
Subject: Re: [Tinyos-help] parallel interface
?)
And then send it to a website (I have no ideia in how to do this one).
Thanks in advance.
(I'm using micaz with mib520 board)
2010/7/15 Michael Schippling sc...@santafe.edu:
Please post any error messages that you get.
I would recommend leaving SerialForwarder out of the loop
Just start O'scope
My understanding of global variables is that anything
declared outside of a function definition is allocated
in the heap at link time, and the final size of that
heap is what is reported as RAM usage. All variables
inside functions (that are not labeled static in real C)
are just names for stack
I use this to get the Source. It opens the right kind of
channel based on the setting of the MOTECOM envvar:
// get the TOS connection
PacketSource ps = BuildSource.makePacketSource();
if (ps == null)
{
System.err.println(
Please post any error messages that you get.
I would recommend leaving SerialForwarder out of the loop
Just start O'scope with the MOTECOM envar setting that
you would have used with SF -- something like:
ser...@com1:mica2
where the port name and mote type match your system.
MS
Walter
I think you have to program the USB chip separately
using software from FTDI or the chip's mfg. Look into
the interface chip's doc.
MS
Michael Ireland wrote:
Hello all - I have manufactured some TelosB motes and run into a
problem: They do not identify correctly. They will program and operate
That darned tos-install-jni only works for some lucky people.
I'm afraid I don't use it or TOSComm so I can't help much.
See if you can find (google or search this list for TOSComm
and tos-install-jni) any doc on what actually gets installed.
You should be able to do it by hand. It is similar to
Michael Schippling írta:
All nodes in a system share one radio frequency/channel,
so only one message can be on the air at a time. The MAC protocol
attempts to prevent two nodes from transmitting at the same time, but if
it fails the received result is usually garbage so sometimes messages
All nodes in a system share one radio frequency/channel,
so only one message can be on the air at a time. The
MAC protocol attempts to prevent two nodes from transmitting
at the same time, but if it fails the received result is
usually garbage so sometimes messages are dropped due to
interference.
In TOS 1.x look for TimerM.nc and TimerJiffyAsyncM.nc
for 1ms and 32us timers, respectively. Jiffy is only
in the micaz tree but can be copied wholesale to mica2.
I'm sure there are simulacra in T2 but I don't use it.
MS
dhb2...@columbia.edu wrote:
I have a question about using a timer for the
In C (and Nesc) declarations must be at the top of a code block,
right after an opening brace:
{
Data_t* newData;
...
}
Perhaps you are trying to write Java instead?
MS
CHEN WEIMING wrote:
Data_t* newData = call DataPool.get();
newData-seqNum = 5;
for codes
It should be, and both of your examples should also be implicit
(not requiring the cast). However there may not be an int64 type...
MS
shri humrudha wrote:
Hi,
For example:
C: float b;
int a=(int) b;
nesC: uint16_t a;
uint64_t b=(uint64_t) a;
In nesC is this
Are you running this on a simulator or a real mote?
I think there was an answer to part of your problem
a day or two ago: you may need to use the packed
attribute in your structure definition to prevent
types from being padded to fit some processor's
idea of their boundaries. I think, but am not
We don't know what program you are using to send data,
but there is probably a TimerM.start() call in it that
sets the number of milli-sec (actually 1024/sec) between
sample periods. TimerM.fired() gets called each period
and should be the thing that initiates the sample.
You can reduce the
search this list and the TOS code for packed
MS
Omar Cheikhrouhou (yahoo) wrote:
The shown output is when using TOSSIM.
And how to use packet attribute? Is there any documentation?
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
Good, someone finally found the new repository of mostly useless
information from ex-xbow. It looks like the board has a bunch of
solder pads on standard .1 centers, so you could probably put
in a ribbon cable header. Or just solder wires to what you need.
One side or the other of the board will
Almost all of the atmega pins are brought out to the 51pin connector.
Specifically, PortC, which is called PW for some reason, is completely
available if you don't use any add-on sensorboard. See my pinout list:
http://www.etantdonnes.com/Motes/ATMEGApins.txt
You can use my original email
I don't know if there are any actual guidelines for
how long one can busy-wait, but I would avoid anything
beyond the low two digits of micro-seconds. Waiting
blocks Task execution which is necessary for the Timer
and Radio (at minimum) code to work properly.
TOS1 had a TimerJiffyAsync module
I can't find a schematic for the mda300, and it looks like
the xbow.com website doesn't even know that they sell Mote
related hardware at the moment...every-time I follow my
trusty links to their site the pages have been moved, some
kind of new business-process-re-engineering I guess...
Perusing
I read one opinion on this list recently that one could simply
switch TOS versions in Moteworks with some environment variable
or other. Search back a month or so and see if my memory is of
any use what'so'ever... But, even if the memory is correct, IMHO,
it probably doesn't work, worth a try
Your understanding seems to be correct.
There's no need to redefine DATA_LENGTH because your
total message payload is smaller than the default value.
Are you having troubles implementing?
If so post your code and the actual errors.
MS
Sam Azzaro wrote:
Hi all,
i want to do communicate two
Permission denied is probably coming from the file system
not the compiler. You may have installed or built as root
or someone who has higher access permissions than whomever
you are trying to build as now, and that particular file
or directory is not accessible to you. Try changing the file
There are various ways to read/write controller pins in TOS.
I only use TOS1.x which had a set of macros:
TOSH_ASSIGN_PIN(PWM1Aout, B, 5); // port,pin B5a == PWM1Aout
TOSH_MAKE_PWM1Aout_OUTPUT();
TOSH_CLR_PWM1Aout_PIN();
TOSH_SET_PWM1Aout_PIN();
There are often modules to do
...
Cool
MS
Eric Decker wrote:
On Tue, Jun 22, 2010 at 9:30 AM, Michael Schippling sc...@santafe.edu
mailto:sc...@santafe.edu wrote:
Err. Uh...Wot?
That second paragraph appears to have fairly standard English
syntax and grammar but makes absolutely no sense to me
matter
because your
include file is protected against being included twice.
On Mon, Jun 21, 2010 at 12:22 PM, Michael Schippling sc...@santafe.edu
mailto:sc...@santafe.edu wrote:
In re: creating real global variables under NESCC.
WOW! I think you've got it. Almost anyway
Search for enableAck(). I use it on mica's under T1,
but I'm not sure what's available in T2.
MS
Omar Cheikhrouhou (yahoo) wrote:
When sending a message from node 1 to node 2. In node 1 the sendDone is
executed which means that the message is sent with success however in
node 2 the
is: do I really care, since I have hacked
global passing into all my interface definitions and will
have to go de-hack them all once more...
wow!
thx!
MS
Eric Decker wrote:
On Sat, Jun 19, 2010 at 6:36 AM, Michael Schippling sc...@santafe.edu
mailto:sc...@santafe.edu wrote:
Just
Just because the code is shared, doesn't mean that the data memory
is shared as well.
Just a WAG on my part, but I would assume that TOSSIM runs each
mote instance on a different stack and sets each instance's global
memory area to different locations as well. In writing that last
phrase it
If you are on MSWidows, do not use the /opt/... syntax in Java CP
settings, it is specific to cygwin.dll users, of which Java is not.
Use the full path, e.g.: C:/cygwin/opt/...
MS
Stefano Kismet Lenzi wrote:
On Wed, Jun 16, 2010 at 18:51, John conque...@aol.com wrote:
I'm trying to make the
I think the problem is in your TOS* variables.
I have them set like this:
vincent:schip [207] echo $TOSDIR
/opt/tinyos-1.1.7/tos
vincent:schip [208] echo $TOSROOT
C:/cygwin/opt/tinyos-1.1.7
Because the /opt/... syntax is only relevant to programs
which use the cygwin dll. Java does not, so it is
In T1 there was an interface in the radio control modules
that allowed one to enable software ACK in the code:
in the config file:
// to enable ACK behavior
TOSBaseM.MacControl - RMac;
where Rmac is one of:
CC1000RadioIntM as RMac, /* mica2 */
/* CC2420RadioM as RMac, /* micaz
I would think that you could send more than 50 messages/sec
using the Iris, but it is close enough to the limit...
Look at how the Oscilloscope demo app aggregates a number
of samples into a single message.
MS
徐经纬 wrote:
I use mts310+iris mote for experiment. I try to get data for all
The bible is here:
http://nescc.sourceforge.net/papers/nesc-ref.pdf
But, as with all bibles, the why question is left as
an exercise for the reader. In this case the BNF is also
somewhat higher-level as well. E.g., the grammar for
'=' and '-' appears to be the same, but the the
semantics are
It's always a good policy to include a description of the
platform, actual situation, and the exact error message text
in any request for help here since we don't magically know
what you are trying to do
But, from your message I am going to intuit that you are trying
to run a listen type
I was just thinking about this myself, googled tinyos stack usage,
and look what I got!
http://docs.tinyos.net/index.php/Stack_Analysis
No telling if it is useful or correct or not though.
MS
swayanti das wrote:
Hi All
could anyone tell me how to measure the runtime memory usage in
This is what I was referring to:
Re: JNI Questions
by Michael Schippling-2 Apr 07, 2010; 11:25am
okokok, I use the old snuffly javacomm20 for windows not TOSComm,
but here's what I have in my JRE:
jre/bin:
getenv.dll win32com.dll
jre/lib
You need to send messages in the TOS_Msg or message_t format.
Find the struct definition for the telos platform.
For TOS1.x it is in: opt/tinyos-1.x/tos/platform/telos/AM.h
and probably something similar for T2.
The tricky parts are: values of 0x7E and 0x7D need to be
escaped because they are
wrote it. CS at University of Utah. So I suspect it is
pretty good. He's been working on this kind of thing for quite some time.
the Safe TinyOS stuff is his baby. Safe TinyOS turns on run time checks.
eric
On Fri, May 21, 2010 at 9:11 AM, Michael Schippling sc...@santafe.edu
You have not set the MOTECOM variable correctly.
See the Environment panel in the Eclipse Run Configuration window.
MS
syxu wrote:
Hi all,
When I run a Java program in Eclipse for TOS application, it reports
s...@localhost:9002 mailto:s...@localhost:9002 died execption and my
program can
Search back on this list for the last few weeks for my, other's,
posts about what needs to be setup in your Java Runtime Env in
order to execute any Java program that connects to a TOS basestation.
I run TOS-to-Java programs under Eclipse all the time. Once you have
your JRE setup right, all you
18.5.10, Michael Schippling /sc...@santafe.edu/*
a écrit :
De: Michael Schippling sc...@santafe.edu
Objet: Re: [Tinyos-help] types
À: raoudha baklouti raoudha_baklo...@yahoo.fr
Cc: tinyos-help@millennium.berkeley.edu
Date: Mardi 18 mai 2010, 19h59
In common TOS
/writes
within the same START transaction.
I hope do you understand my problem, thaks...
2010/5/18 Michael Schippling sc...@santafe.edu mailto:sc...@santafe.edu
If the T2 impl is like the T1 version there are four bits
you can send to I2C read/write, which are conveniently
You can always try to do a switch on your MoteID to execute
different code in different devices. I don't think there is
a memory limitation in the simulator
MS
sania aziz wrote:
*TinyOS simulator (Tossim) has a mjor limitation that all motes must
have same code. In my opinion, it
If the T2 impl is like the T1 version there are four bits
you can send to I2C read/write, which are conveniently
not defined or described anywhere:
/*
** I2CPacket read/write command flags,
** defined in I2CPacketM.nc but not in a header file...
*/
#define STOP_FLAG 0x01 //send stop/end
You can find most everything anyone knows about mspgcc at:
mspgcc.sourceforge.net/
MS
Andres Vahter wrote:
Hi,
I have mspgcc toolcain installed and it is working well with telosb.
How can I use it for building and uploading a simple example program
from TI webpage: MSP430F22x2,
In common TOS usage a structure with Msg in it is the payload
portion of a TOS_Msg or message_t structure that is transmitted
over the radio, or serial UART between the base-station and host.
Usually you can imagine the Msg being overlaid on the TOS_Msg.data[]
array set aside for user payload.
This won't be much help since I'm using TOSBase under T1...but...
The default behavior of MICA basestations was to map incoming
micaZ 802.whatever headers to the old style mica2 headers. I once
saw mention of where/how this happens but have totally forgotten.
You might find something with an
You environment variables may not be set correctly.
The first, TOS build, errors could be due to
not having a MAKERULES variable or the wrong
rules file. The javac error is probably due to not
having a valid Java SDK bin directory in your PATH.
Search this list and google for further advice.
MS
Basically, don't worry...
Received messages are sent to your code in sequence.
Each receive() method is executed in a task and tasks
can only run one at a time. The actual radio receive
is done with interrupts, so you shouldn't miss anything
unless you let your messages overrun your tasks.
On
The problem is that you only have 4Kb of RAM on a real device
and the length field you can specify in a message is 8bits long...
MS
avinash chaurasia wrote:
sorry i got the answer it should be like
env CFLAGS=-DTOSH_DATA_LENGTH=1000 make micaz sim
and it works
but when i increase message
If all the hardware is identical, and connected identically,
you should be able to use TOS without changes. Just don't
access the missing components.
However I believe there is a bootloader that needs to be
installed on the mote so it can be programmed via the USB.
I've seen scant mention of it
201 - 300 of 2385 matches
Mail list logo
