I agree...since you need a proxy of some kind on a PCish host,
I would put parsing and encoding software there instead of pushing
it all the way out to the sensors. Appropriate Technology and all...
MS
J. Ryan Stinnett wrote:
As I said, the largest packet would be about 256 bytes, but the standa
Thanks Michael,
In the AM.h in TOS2 there are few defines only for addresses. The message
structure for the radio is changed, but the HDLC packets should be in same
format. The defines about HDLC are in fact in Serial.h and I can see that
flag byte is the same, so HDLC enabled program for TOS 1 sh
As I said, the largest packet would be about 256 bytes, but the standard
T2 application data length is 28 bytes, which seems far too small for
tagged data of any more than the simplest kind. This would mean you'd
likely have to split your data across multiple packets, which also adds
more comp
Ofcourse, what ever your saying regarding the XML on a sensor node is right.
As you said, it is the application that forced us to think in this way.
What do you think are the possible obstacles in using XML format for
messages and then parsing them at the sensor nodes.
Regards
Adi
On 8/2/07, J.
Interesting, so there apparently is an XML library... However, I still
can't see a real need for that on a mote. I've found that XML can be
useful way to store data on a computer that is connect to a sensor
network, but on the motes themselves I can't see why you'd want to go
that route. Is
Hi Ryan,
Later when I searched for it, I found something called TinyXML at
http://ics.yeditepe.edu.tr/tnl/html/tinyxml.html. Have look at it. I didnt
explore the capabilities of it.
Regards
Adi
On 8/2/07, J. Ryan Stinnett <[EMAIL PROTECTED]> wrote:
>
> If you mean parsing XML data in messages
If you mean parsing XML data in messages sent via the radio, I don't
think that would be very feasible. XML is a pretty verbose format, and
the largest packet the CC2420 can send is around 256 bytes. It would
probably be best to stick with more compact data representations.
- Ryan
Adi Malli
Hi all,
Has any one tried out having an XML parser running on the sensor nodes along
with TinyOS/nesC? Something like TinyXMLParser, which can interpret the XML
messages that a node receives?.
Any suggestions on this line would be of great helpful.
Regards
Adi
--
--
This could solidify your understanding on how to work with parameterized
interfaces:
http://nescc.sourceforge.net/papers/nesc-ref.pdf
-Brian
On 7/31/07, Yong, Chee Yeew <[EMAIL PROTECTED]> wrote:
>
> Hello all,
>
> I am having a bit of a problem wiring parameterised interfaces. The
> program
>
On 8/1/07, antonio gonga <[EMAIL PROTECTED]> wrote:
>
> Hey MS,
> I'm using Micaz and I changed TOSBase to work with Micaz->
>//CC1000RadioIntM as RMac,/* mica2 */
> CC2420RadioM as RMac,/* micaz */
> It's really a bit strange, I'm correctly receiving messages from
How about approaching it differently. Have each mote maintain a single timer
a list of its
neighbors. Each neighbor entry can be associated with a value that you
update every time
the timer fires and whenever the mote hears from that particular neighbor.
*There could be a solution involving multip
hi
I want to have a clock type of interface on my mica2 motes so that I can
keep track of events on the node. For example, I send out a Route Request in
a multihop network at some particular time. I wish to store this event as a
time event. Is such a component already present(in tinyos-2.x)or do I
Hi Phillip, thanks for the help,
I haven't tried using the debug interface, but I will.
Right after reading your mail I tried using another topology, more
mesh-like, and it worked. The net topology I was using was very
simple, just a plain tree topology, with one 4-node loop, and a "line"
of node
Hello,
The file RadioCoordinator defines the events starySymbol and byte, and
CricketM is one of the applications that happens to use the function. Am I
right in saying that CricketM implements the event defined in
RadioCoordinator?
I am thinking I am confused because I edited the CricketM code t
Hi All
Is there anyway I can access TOSSIM objects via nesC, e.g. I want to know mote
location stored in TOSSIM at runtime.
Looking Forward
faisal
Sick sense of humor? Visit Yahoo! TV's
Comedy with
That looks like it should work. You do know that there is another
yellowToggle() call in the standard TOSBase, right? Maybe they are
competing with each other...
Also by printing out messages, does this mean you are running a
simulator? Perhaps you can debug in and look at what's actually
happeni
Well, look at the micasb version. It wraps Photo (or Temp, I never remember)
which further wraps ADC (which does actually do something in-between...).
I'm going to assume that the telosb internal voltage sensor is implemented
as some kind of ADC as well. The basic pattern is:
// in some m
TimerC uses Timer/Counter1 which is 16 bits, so that's a theoretical max.
But you would have to go look at the code, or experiment, to see if there's
more headroom eaten up by data munging...
MS
Siirtola Harri wrote:
I'll need vry long measurement intervals for my application. What's
the ma
I accidentally hit send, or some combination of keys that said send,
and didn't complete the message. The other thing I was going to mention,
because I haven't seen the array usage:
TestM.MyTimers[0] -> TimerC.Timer[unique("Timer")];
maybe leave the [0] off? That's the way I use the TimerC mod
I believe that "they" changed the message structure slightly in T2
so as to be incompatible with any previous host software...Look
into the equivalent of types/AM.h to see what needs to be modified.
MS
Hristo Bojkov wrote:
Hello tinyOS coders,
I am new to TinyOS2. I have used TinyOS 1.1 for 6
On Aug 1, 2007, at 9:20 AM, Todd Roper wrote:
I went ahead and reset the two suspect nodes yesterday and as
expected,
they started sending data into the network again. This morning, I
discovered that one of them was trying to send through a node 2 this
time. (node 2 is not in the network).
I am a Research Assistant at WiSe MANet Labs in University of Memphis.
I am currently working on one project, for which it requires a Sensor
mote(Tmote Invent) should monitor all of its neighbors.So i am using
Multiple Timers to do so.For Monitoring motes, If a Mote A have 5 neighbors
it should ma
On Aug 1, 2007, at 4:38 AM, Hugo Sousa wrote:
I've even tried changing the CtpRoutingEngineP parameters in CtpP,
like Phillip said in another thread, but still doesn't work. Isn't CTP
prepared to handle tree root changes? What about topology changes?
In theory, it should handle tree root chang
>
> If it's trying to send to a node that doesn't exist, that's strange.
> It suggests memory corruption in the routing table. In theory, it
> should not stick with such a node very long, as the ack-based
> estimates will let it know that this is not a good node.
It seems that once it is stuck li
Hi,
Does anyone know how to install tinyos-2.0 on a Ubuntu feisty 64 bit OS?
Just find the instruction on the tinyos.net is for Ubuntu edgy.
Thanks in advance.
Hui
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium
Hi,
When I make in /opt/tinyos-1.x/tools/java, I get some errors : cannot
resolve symbol
Environment seems to be correctly installed :
- toscheck is OK.
- CLASSPATH=.;/opt/tinyos-1.x/tools/java
- which java --> ../UCB/jdkl.4.1_02/j2sdkl.4.1_02/bin/java
Any body knows why? Any help will be g
I'll need vry long measurement intervals for my application. What's
the maximum value for parameter 'interval' with MicaZ? 22,118,400
(0x1518000) binary milliseconds is 4 hours and fits in an uint32_t, does
it work? Or do I have to establish a counter?
Regards,
Harri
_
Hello,
I was wondering if exists an implementation of the Flooding Time Sync
Protocol (FTSP) for TinyOS-2.x.
I know that an implementation for TinyOS-1.x already exists, but I would
compare my program written in TinyOS-2.x with FTSP Algorithm.
I'm looking for a reply, thanks.
_
I've even tried changing the CtpRoutingEngineP parameters in CtpP,
like Phillip said in another thread, but still doesn't work. Isn't CTP
prepared to handle tree root changes? What about topology changes?
Hugo
On 7/30/07, Hugo Sousa <[EMAIL PROTECTED]> wrote:
> I'm simulating EasyCollection in TO
Hey MS,I'm using Micaz and I changed TOSBase to work with Micaz->
//CC1000RadioIntM as RMac,/* mica2 */ CC2420RadioM as RMac,
/* micaz */It's really a bit strange, I'm correctly receiving messages from
Motes in the Java Application, but whenever I send messages to t
> I looked at the document - and it contains a partial sample code. Still,
> is there a complete application sample somewhere that configures and reads
> from and ADC on telosb, and does something with it? Like TestAdc, just for
> real? By that I mean that it really configures the ADC, specifies wh
Thanks for the reply, but I wish it was that easy to solve.
I believe the problem to be that I am wiring the Timer erroneously in TestC.
However, I cannot put my finger on why my wiring is not acceptable to ncc.
Chee
> -Original Message-
> From: Michael Schippling [mailto:[EMAIL PROTECT
Dear Philip,
Thank you for your reply.
As you said that CC2420 LPL in Tinyos2.x works with
arbitrary topologies, I tried to use LPL with
collection protocol provided in tinyos2.0.2. I used
the LowPowerListening interface in my top level
application to set the sleep interval of TX and Rx
sides.
Jan,
> If the Read interfaces are not "good enough", take a look at
> tinyos-2.x/tos/chips/msp430/adc12/Msp430Adc12Client*.nc. These
> components export the msp430 specific functionality. If you use them
> your code will not be so portable anymore, but you can do things like
> high-frequency sampl
> Well, yeah...But doesn't every platform also have the "raw" ADC
> implementation
> which provides exactly the same interface, with a (well, to my low-level
> mind)
> more straightforward connection to the external world? Admittedly there
> are
> some 'tricks' that need to be performed to get, e.g
> Did deeper into DemoSensor. First of course you have to figure out
> which one and where it is...I don't (yet) have a tmote dev environment,
> but for the Mica's it's in tos/sensorboards/micasb/DemoSensorC.nc
DemoSensorC on telosb simply calls the internal voltage sensor - it's not
related to an
36 matches
Mail list logo
