[Tinyos-help] MViz and TOSSIM
Dear Tinyos-Help This is my first cry for help, have been working through the tutorials with some success, however now I am stuck on getting MViz and TOSSIM to interact, and am struggling to find much documentation. Background info: Machine: Fedora 7, TinyOS 2, Java 1.5. I completed the following in the $TOSROOT/apps/MViz directory: make micaz sim This completed successfully and created the MVizMsg.class and MVizMsg.java files. I then moved into the $TOSROOT/tools/tinyos/misc directory and ran tos-mviz. Now I am not sure what swtiches to supply because I want to run this in a simulation (I have nothing physically attached) and so I provided: tos-mviz -comm micaz MVizMsg I get the following (a screen does appear and disappears as quickly): [misc]$ tos-mviz -comm micaz MVizMsg /opt/tinyos-2.x/support/sdk/java/tinyos.jar:.:/opt/tinyos-2.x/apps/MViz: Making MVizMsg Loading link Loading etx Loading reading Loading count Loading origin Loading interval Loading version ./mote.gif Exception in thread "main" java.lang.NullPointerException at net.tinyos.message.MoteIF.init(MoteIF.java:119) at net.tinyos.message.MoteIF.(MoteIF.java:110) at net.tinyos.mviz.MessageInput.createSource(MessageInput.java:72) at net.tinyos.mviz.MessageInput.(MessageInput.java:51) at net.tinyos.mviz.DDocument.main(DDocument.java:303) Am I missing something? If anyone else has had this working could you let me know what steps you have performed? Is there any more documentation? I have tried different switches with tos-mviz only to see other error messages. _ http://clk.atdmt.com/UKM/go/msnnkmgl001009ukm/direct/01/ ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Compliation error
Hi there
In an effort to try and understand networking, I copied some code from the
following link
(http://64.233.183.104/search?q=cache:lcu-HYOtTCUJ:www.et.byu.edu/groups/ececmpsysweb/cmpsys.2008.winter/tinyos.ppt+call+AMSend&hl=en&ct=clnk&cd=5&gl=uk)
and when I compile it I get the following error message:
[Simple1]$ make micaz sim
mkdir -p build/micaz
placing object files in build/micaz
writing XML schema to app.xml
compiling simple1AppC to object file sim.o
ncc -c -shared -fPIC -o build/micaz/sim.o -g -O0 -tossim
-fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\)
-finline-limit=10 -Wall -Wshadow -Wnesc-all -target=micaz
-fnesc-cfile=build/micaz/app.c -board=micasb
-DIDENT_PROGRAM_NAME=\"simple1AppC\" -DIDENT_USER_ID=\"AntMan\"
-DIDENT_HOSTNAME=\"FedAnt.Bikefact\" -DIDENT_USER_HASH=0xeeddd9a1L
-DIDENT_UNIX_TIME=0x4863bd91L -DIDENT_UID_HASH=0x35974569L -Wno-nesc-data-race
simple1AppC.nc -fnesc-dump=components -fnesc-dump=variables
-fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs
-fnesc-dump=tags -fnesc-dumpfile=app.xml
nesc1: nesc-semantics.c:145: language_name: Assertion `0' failed.
nesC: Internal error. Please send a bug report to the nesC bug mailing list
at [EMAIL PROTECTED]
make: *** [sim-exe] Error 1
[Simple1]$
To advise I have previously compiled many programs without this problem,
including BlinkToRadio.
I am trying to understand how the send and receive works so I can get each mote
to broadcast and then compile a local table of the n-hop motes. I wanted to
start again with a simple example and then expand out..
Below is the code I am compiling, can you advise what I am missing. I cannot
see what I have missed.
Thanks
Anthony
#ifndef SIMPLE1_H
#define SIMPLE1_H
typedef nx_struct MyPayload
{
nx_uint8_t count;
} MyPayload;
#endif
#include
#include "simple1.h"
module simple1C
{
uses interface Boot;
uses interface AMPacket;
uses interface AMSend;
uses interface SplitControl;
uses interface Receive;
}
implementation
{
task void sendMsg();
task void createMsg();
message_t myMsg;
int8_t myCount = 0;
event void Boot.booted()
{
call SplitControl.start();
}
event void SplitControl.startDone(error_t error)
{
post createMsg();
post sendMsg();
}
event void SplitControl.stopDone(error_t error)
{
}
task void sendMsg()
{
if(call AMSend.send(AM_BROADCAST_ADDR, &myMsg, 0) != SUCCESS)
{
post sendMsg();
}
}
event void AMSend.sendDone(message_t* msg, error_t error)
{
post sendMsg();
}
event message_t* Receive.receive(message_t* msg, void* payload, uint8_t
len)
{
return msg;
}
task void createMsg()
{
MyPayload* payload = (MyPayload*) call
AMSend.getPayload(&myMsg);
payload->count = (myCount++);
post sendMsg();
}
}
#include
#include "simple1.h"
configuration simple1App1C
{ }
implementation
{
components MainC;
components simple1C as Simple1;
components ActiveMessageC;
components new AMSenderC(0); // send an AM type 0 message
components new AMReceiverC(0); // receive an AM type 0 message
Simple1.Boot -> MainC;
Simple1.SplitControl -> ActiveMessageC;
Simple1.AMSend -> AMSenderC;
Simple1.Receive -> AMReceiverC;
}
COMPONENT=simple1AppC
include $(MAKERULES)
_
Great deals on almost anything at eBay.co.uk. Search, bid, find and win on eBay
today!
http://clk.atdmt.com/UKM/go/msnnkmgl001004ukm/direct/01/
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Confusion over AM_BROADCAST_ADDR
Hi there
I am trying to write some software that, in the TOSSIM environment, sends out a
packet to all nodes (unknown number), and each node responds upon receiving the
packet. This software would allow the creation of a table of all nodes within
range of the current node.
I am using AMSend.send to send my packet. The address is AM_BROADCAST_ADDR,
which I understand means it will send the packet to every node in range (i.e.
Broadcast)?
So, if I send it once any node, 0, 1, or more, would receive the packet and
send it back to the originating node.
I am unable to get this to work as expected, making me think I am not
completely understanding how this works.
I have stripped my code down to its simplest form, and found that on sending
out to AM_BROADCAST_ADDR I only get a response from one node (the originating
node)? Why is this? What am I missing?
Below is my code, TOSSIM code:
#include
#include "BlinkHop1.h"
module BlinkHop1C
{
uses interface Boot;
uses interface Leds;
uses interface Packet;
uses interface AMPacket;
uses interface AMSend;
uses interface SplitControl as AMControl;
uses interface Receive;
}
implementation
{
bool busy = FALSE;
message_t pkt;
bool first = TRUE;
task void sendMsg()
{
if (!busy)
{
BlinkHopMsg* hpkt = (BlinkHopMsg*)call
AMSend.getPayload(&pkt);
if (first)
{
if (call AMSend.send(AM_BROADCAST_ADDR, &pkt,
sizeof(BlinkHopMsg)) == SUCCESS)
{
dbg("Hop","\nFirst send so it goes to everyone, Sending packet with source =
%i\n TTL = %i \n destination = %i \n ", (int)hpkt->source, (int)hpkt->ttl,
(int)hpkt->destination);
busy = TRUE;
first = FALSE;
}
else
{
dbg("Hop","Send failed!!!");
}
}
else
{
dbg("Hop","Not the first time so not sending anything further, every node
should receive hat I sent out\n");
}
}
else
{
dbg("Hop","I am unable to send me packet\n");
}
}
task void Discover()
{
BlinkHopMsg* hpkt = (BlinkHopMsg*)call
AMSend.getPayload(&pkt);
if (first)
{
dbg("Hop","Creating packet\n");
hpkt->source = (int)TOS_NODE_ID;
hpkt->destination = -1;
hpkt->ack = FALSE;
post sendMsg();
}
else
{
post sendMsg();
}
}
event void Boot.booted()
{
call AMControl.start();
}
event void AMControl.startDone(error_t err)
{
if (err == SUCCESS)
{
post Discover();
}
else
{
call AMControl.start();
}
}
event void AMControl.stopDone(error_t err)
{
}
event void AMSend.sendDone(message_t* msg, error_t error)
{
if (&pkt == msg)
{
busy = FALSE;
post Discover();
}
}
event message_t* Receive.receive(message_t* msg, void* payload, uint8_t
len)
{
BlinkHopMsg* rpkt2 = (BlinkHopMsg*)call AMSend.getPayload(&pkt);
dbg("Hop","rpkt2 \n%i I have received a packet from %i destination %i \n",
(int)TOS_NODE_ID, (int)rpkt2->source, (int)rpkt2->destination);
return &pkt;
}
}
from sys import *
from TOSSIM import *
t = Tossim([]);
t.addChannel("Hop",stdout);
r = t.radio();
f = open("topo.txt","r");
lines = f.readlines()
for line in lines:
s = line.split()
if (len(s)> 0):
print " ", s[0], " ", s[1], " ", s[2];
r.add(int(s[0]), int(s[1]), float(s[2]));
noise = open("hist.txt","r");
lines = noise.readlines()
for line in lines:
str = line.strip()
if (str != ""):
val = int(str)
for i in range(1,3):
t.getNode(i).addNoiseTraceReading(val);
for i in range(1,3):
print "Creating noise for ", i;
t.getNode(i).createNoiseModel();
#t.getNode(31).bootAtTime(45654);
#t.getNode
[Tinyos-help] Tymo and TOSSIM not compiling
Hi there
I am trying to get the Tymo tutorial up and running and have put together my
App and C files and on compiling I have the following errors (make micaz sim):
In component `MHPacketM':
/opt/tinyos-2.x/tos/lib/net/multihop/MHPacketM.nc:28: `MHPacket.group' not
implemented
/opt/tinyos-2.x/tos/lib/net/multihop/MHPacketM.nc:28: `MHPacket.setGroup' not
implemented
/opt/tinyos-2.x/tos/lib/net/multihop/MHPacketM.nc:28: `MHPacket.localGroup' not
implemented
/opt/tinyos-2.x/tos/lib/net/dymo/DymoServiceC.nc:6:28: error: StorageVolumes.h:
No such file or directory
In file included from TymoAppC.nc:8:
In component `DymoNetworkC':
I have today downloaded the Tymo files from SourceForge.net, it is tymo0.2beta.
I installed the latest RPM files from the Tinyos.net last month for TinyOS.
I am not sure if I have made a mistake in my code, or if I am missing a file or
the wrong version. Still being on the learning curve I am struggling a little.
Could you help me, thanks.
I have read the previous post concerning this and Romain Thouvenin's reply on
Thu, 26 Jun 2008 15:04:23 -0700, but I can't see the relation as that is for
IRIS not micaz sim? Again, if I am wrong could someone explain?
Below is the code for my TymoAppC.nc && TymoC.nc:
configuration TymoAppC
{ }
implementation
{
components MainC;
components TymoC;
components DymoNetworkC;
components new TimerMilliC() as Timer;
TymoC.Boot -> MainC;
TymoC.SplitControl -> DymoNetworkC;
TymoC.Packet -> DymoNetworkC;
TymoC.MHPacket -> DymoNetworkC;
TymoC.Receive -> DymoNetworkC.Receive[1];
TymoC.MHSend -> DymoNetworkC.MHSend[1];
}
module TymoC
{
uses
{
interface Boot;
interface Timer;
interface SplitControl;
interface AMPacket as MHPacket;
interface Packet;
interface Receive;
interface AMSend as MHSend;
}
}
implementation
{
message_t packet;
enum
{
ORIGIN = 1,
TARGET = 6,
};
event void Boot.booted()
{
call SplitControl.start();
}
event void SplitControl.startDone(error_t e)
{
if (call MHPacket.address() == ORIGIN)
{
call Timer.startPeriodic(2048);
}
}
event void Timer.fired()
{
nx_uint16_t * payload = call Packet.getPayload(&packet, NULL);
error_t error;
*payload = 1664;
error = call MHSend.send(TARGET, &packet, sizeof(*payload));
if (error == SUCCESS)
{
dbg("Tymo","Good \n");
}
else
{
dbg("Tymo","Wrong \n");
}
}
event void MHSend.sendDone(message_t * msg, error_t e)
{
if ((e == SUCCESS) && (msg == &packet) && (call
MHPacket.address() == ORIGIN))
{
dbg("Tymo","Even better \n");
}
else
{
dbg("Tymo","The packet could not be sent \n");
}
}
event message_t * Receive.receive(message_t * msg, void * payload,
uint8_t len)
{
if (call MHPacket.address() == TARGET)
{
dbg("Tymo","Message received \n");
}
else
{
dbg("Tymo","Strange behaviour \n");
}
return msg;
}
event void SplitControl.stopDone(error_t e) {}
}
Microsoft is solely responsible for any e-tags and links that they put on the
bottom of my emails. These are placed on my emails without my consent and
against my will. I have neither agreed to them nor endorse them. I am sorry you
are forced to receive them. If you do not like them, please send a complaint to
Microsoft.
_
Invite your Facebook friends to chat on Messenger
http://clk.atdmt.com/UKM/go/101719649/direct/01/
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Tymo and TOSSIM not compiling
/tinyos-2.x/tos/lib/net/tymo/ForwardingEngineM.nc:202: warning: passing argument 2 of `PPacket.getPayload' makes pointer from integer without a cast /opt/tinyos-2.x/tos/lib/net/tymo/ForwardingEngineM.nc: At top level: /opt/tinyos-2.x/tos/lib/net/tymo/ForwardingEngineM.nc:218: conflicting types for `Intercept.forward' /opt/tinyos-2.x/tos/interfaces/Intercept.nc:31: previous declaration of `Intercept.forward' /opt/tinyos-2.x/tos/lib/net/tymo/ForwardingEngineM.nc:40: `Receive.payloadLength' not implemented /opt/tinyos-2.x/tos/lib/net/tymo/ForwardingEngineM.nc:40: `Receive.getPayload' not implemented In file included from /opt/tinyos-2.x/tos/lib/net/tymo/dymo/sim/DymoServiceC.nc:34, from /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoNetworkC.nc:38, from TymoAppC.nc:8: In component `DymoPacketM': /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoPacketM.nc: In function `DymoPacket.getType': /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoPacketM.nc:44: warning: passing argument 2 of `Packet.getPayload' makes pointer from integer without a cast /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoPacketM.nc: In function `DymoPacket.getSize': /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoPacketM.nc:49: warning: passing argument 2 of `Packet.getPayload' makes pointer from integer without a cast /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoPacketM.nc: In function `DymoPacket.createRM': /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoPacketM.nc:60: warning: passing argument 2 of `Packet.getPayload' makes pointer from integer without a cast /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoPacketM.nc: In function `DymoPacket.addInfo': /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoPacketM.nc:90: warning: passing argument 2 of `Packet.getPayload' makes pointer from integer without a cast /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoPacketM.nc: In function `processMessage.runTask': /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoPacketM.nc:132: warning: passing argument 2 of `Packet.getPayload' makes pointer from integer without a cast /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoPacketM.nc:148: warning: passing argument 2 of `Packet.getPayload' makes pointer from integer without a cast make: *** [sim-exe] Error 1 ---- > Date: Thu, 10 Jul 2008 08:49:32 +0200 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Re: [Tinyos-help] Tymo and TOSSIM not compiling > CC: tinyos-help@millennium.berkeley.edu > > On Wed, Jul 9, 2008 at 10:03 PM, Anthony Smee wrote: >> >> Hi there >> >> I am trying to get the Tymo tutorial up and running and have put together my >> App and C files and on compiling I have the following errors (make micaz >> sim): >> >> In component `MHPacketM': >> /opt/tinyos-2.x/tos/lib/net/multihop/MHPacketM.nc:28: `MHPacket.group' not >> implemented >> /opt/tinyos-2.x/tos/lib/net/multihop/MHPacketM.nc:28: `MHPacket.setGroup' >> not implemented >> /opt/tinyos-2.x/tos/lib/net/multihop/MHPacketM.nc:28: `MHPacket.localGroup' >> not implemented >> /opt/tinyos-2.x/tos/lib/net/dymo/DymoServiceC.nc:6:28: error: >> StorageVolumes.h: No such file or directory >> In file included from TymoAppC.nc:8: >> In component `DymoNetworkC': >> >> I have today downloaded the Tymo files from SourceForge.net, it is >> tymo0.2beta. I installed the latest RPM files from the Tinyos.net last month >> for TinyOS. >> >> I am not sure if I have made a mistake in my code, or if I am missing a file >> or the wrong version. > > That's it. The version code from the tymo sourceforge project is > deprecated, please use the latest CVS code of TinyOS instead. > > Regards, > Romain _ Invite your Facebook friends to chat on Messenger http://clk.atdmt.com/UKM/go/101719649/direct/01/ ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Tymo and TOSSIM not compiling
Hi Romain Sorry for my delayed response, I did copy tymo into my previous tree yes, but have since located the files and removed them. Is there something else I should have done? Thanks Anthony > Date: Thu, 10 Jul 2008 20:46:07 +0200 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Re: [Tinyos-help] Tymo and TOSSIM not compiling > CC: tinyos-help@millennium.berkeley.edu > > It looks quite strange. This is the same kind error messages as what > using recent code with old AM interfaces would produce. > > By any chance, you didn't copy tymo into your previous TinyOS tree? > > Romain > > On Thu, Jul 10, 2008 at 11:14 AM, Anthony Smee wrote: >> >> Hi there >> >> Thanks for your prompt reply, I have run the following: >> >> cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/tinyos co -P tinyos-2.x >> >> Which created, amongst many other things the directory tymo under >> $TOSROOT/TOS/LIB/NET >> >> Within here are sub-directories for mh and dymo. >> >> I then altered my Makefile as follows to incorporate these new directories: >> >> COMPONENT=TymoAppC >> >> CFLAGS += -I$(TOSDIR)/lib/net \ >>-I$(TOSDIR)/lib/net/tymo \ >>-I$(TOSDIR)/lib/net/tymo/dymo \ >>-I$(TOSDIR)/lib/net/tymo/mh \ >>-I. >> >> TFLAGS += -I(TOSDIR)/types >> >> include $(MAKERULES) >> >> Confusingly running make micaz sim gives the following results: >> >> In file included from /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHServiceC.nc:33, >> from >> /opt/tinyos-2.x/tos/lib/net/tymo/dymo/DymoNetworkC.nc:38, >> from TymoAppC.nc:8: >> In component `MHPacketM': >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc:38: conflicting types for >> `Packet.getPayload' >> /opt/tinyos-2.x/tos/interfaces/Packet.nc:108: previous declaration of >> `Packet.getPayload' >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc: In function >> `Packet.getPayload': >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc:39: warning: passing >> argument 2 of `SubPacket.getPayload' makes pointer from integer without a >> cast >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc: In function >> `Packet.payloadLength': >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc:48: warning: passing >> argument 2 of `SubPacket.getPayload' makes pointer from integer without a >> cast >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc: In function >> `Packet.setPayloadLength': >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc:52: warning: passing >> argument 2 of `SubPacket.getPayload' makes pointer from integer without a >> cast >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc: In function >> `MHPacket.destination': >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc:66: warning: passing >> argument 2 of `SubPacket.getPayload' makes pointer from integer without a >> cast >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc: In function >> `MHPacket.isForMe': >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc:70: warning: passing >> argument 2 of `SubPacket.getPayload' makes pointer from integer without a >> cast >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc:70: warning: passing >> argument 2 of `SubPacket.getPayload' makes pointer from integer without a >> cast >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc: In function >> `MHPacket.setDestination': >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc:74: warning: passing >> argument 2 of `SubPacket.getPayload' makes pointer from integer without a >> cast >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc: In function >> `MHPacket.setSource': >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc:78: warning: passing >> argument 2 of `SubPacket.getPayload' makes pointer from integer without a >> cast >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc: In function >> `MHPacket.setType': >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc:82: warning: passing >> argument 2 of `SubPacket.getPayload' makes pointer from integer without a >> cast >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc: In function >> `MHPacket.source': >> /opt/tinyos-2.x/tos/lib/net/tymo/mh/MHPacketM.nc:87: warning: passing >> argument 2 of `SubPacket.getPayload' makes pointer from integer without a >>
Re: [Tinyos-help] Tymo and TOSSIM not compiling
Cleaning out the tree and re-running CVS allowed me to compile the code. Thank you. Anthony Microsoft is solely responsible for any e-tags and links that they put on the bottom of my emails. These are placed on my emails without my consent and against my will. I have neither agreed to them nor endorse them. I am sorry you are forced to receive them. If you do not like them, please send a complaint to Microsoft. > Date: Mon, 14 Jul 2008 13:08:23 +0200 > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Re: [Tinyos-help] Tymo and TOSSIM not compiling > CC: tinyos-help@millennium.berkeley.edu > > On Sun, Jul 13, 2008 at 1:21 PM, Anthony Smee <[EMAIL PROTECTED]> wrote: > > > > Hi Romain > > > > Sorry for my delayed response, I did copy tymo into my previous tree yes, > > but have since located the files and removed them. Is there something else > > I should have done? > > > > Thanks > > > > Anthony > > Some interface changes occured in TinyOS between your previous tree > and the current one. So you can use Tymo only with the current tree, > as it uses the new interfaces. > > Regards, > Romain _ Play and win great prizes with Live Search and Kung Fu Panda http://clk.atdmt.com/UKM/go/101719966/direct/01/___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Increasing a node's transmit radius under TOSSIM
Hi there I am working on some code which discovers other nodes, in fact all nodes discover what is around them. It is possible that some nodes are hidden, that is they hear from others but can't communicate back. All of this is in the TOSSIM environment. Is it possible, that when a Node determines that another node is a hidden / asymmetric node, it can tell said node to increase its radio transmit radius and so, potentially, bring it out of its hidden status? From reading through the tutorials and looking at code I realise you could do this by changing the gain relationship between the two, or more, nodes, which would have to completed at the Python level. However I can't see how a nodes transmit radius can be increased, is there a command to complete this? Also, a second question, if I may, is it possible to ascertain the x / y co-ordinates of a node in a topology? Thank you. Anthony Microsoft is solely responsible for any e-tags and links that they put on the bottom of my emails. These are placed on my emails without my consent and against my will. I have neither agreed to them nor endorse them. I am sorry you are forced to receive them. If you do not like them, please send a complaint to Microsoft. _ Find the best and worst places on the planet http://clk.atdmt.com/UKM/go/101719807/direct/01/___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Detecting collisions over asymmetric links
Hi there Does anyone have any advise on the best way to detect a collision over an asymmetric link. I have managed to put something together, under TOSSIM, using multiple timers to try and detect asymmetric links. However it does not really deal with collisions, and so the code works, and then sometimes it does not which I put down to collisions I would prefer to be able to detect this and deal with it accordingly. Also along the same lines, does anyone have any advise on getting a consistent environment in TOSSIM? I have set the gain to be equal for every node's relation, and also a consistent noise but still my results differ with each run. Thanks Anthony Microsoft is solely responsible for any e-tags and links that they put on the bottom of my emails. These are placed on my emails without my consent and against my will. I have neither agreed to them nor endorse them. I am sorry you are forced to receive them. If you do not like them, please send a complaint to Microsoft. _ Win New York holidays with Kellogg’s & Live Search http://clk.atdmt.com/UKM/go/107571440/direct/01/___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Detecting collisions over asymmetric links
Hi there Sorry for the confusion, I am looking for advise on: a - How does one detect a collision b - How does one detect an asymmetric link I have written code to detect asymmetric links based around multiple timers that are running at different intervals waiting on packets to be received after a broadcast, if it does not hear any packets back it will eventually conclude that it has an asymmetric link. However, the node may not hear back from a broadcast due to collisions. I am looking for advise on how you detect a collision? Thanks Anthony Date: Mon, 4 Aug 2008 19:53:39 -0700 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [Tinyos-help] Detecting collisions over asymmetric links CC: tinyos-help@millennium.berkeley.edu what exactly do you mean by collisions on an asymmetric link? On Mon, Aug 4, 2008 at 1:09 PM, Anthony Smee <[EMAIL PROTECTED]> wrote: Hi there Does anyone have any advise on the best way to detect a collision over an asymmetric link. I have managed to put something together, under TOSSIM, using multiple timers to try and detect asymmetric links. However it does not really deal with collisions, and so the code works, and then sometimes it does not which I put down to collisions I would prefer to be able to detect this and deal with it accordingly. Also along the same lines, does anyone have any advise on getting a consistent environment in TOSSIM? I have set the gain to be equal for every node's relation, and also a consistent noise but still my results differ with each run. Thanks Anthony Microsoft is solely responsible for any e-tags and links that they put on the bottom of my emails. These are placed on my emails without my consent and against my will. I have neither agreed to them nor endorse them. I am sorry you are forced to receive them. If you do not like them, please send a complaint to Microsoft. Get fish-slapping on Messenger! Play Now ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Eric B. Decker Senior (over 50 :-) Researcher Autonomous Systems Lab Jack Baskin School of Engineering UCSC _ Win New York holidays with Kellogg’s & Live Search http://clk.atdmt.com/UKM/go/107571440/direct/01/___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Calculating a mote's radius under Tossim
Hi there I want to be able to ascertain a mote's radius, and I a little confused what it should be. Fro example, if I had three motes, see gain file example below, would each of those radius be: Mote 1 = 144 Mote 2 = 177 Mote 3 = 146 I am thinking it would be the maximum value as this would cover the Motes that also fall within this radius? Does this make sense? 1 2 144 2 1 136 2 3 177 3 2 146 1 3 121 3 1 115 Thanks Anthony P.s. the gain example is purely that, numbers off the top of my head. Microsoft is solely responsible for any e-tags and links that they put on the bottom of my emails. These are placed on my emails without my consent and against my will. I have neither agreed to them nor endorse them. I am sorry you are forced to receive them. If you do not like them, please send a complaint to Microsoft. _ Make a mini you on Windows Live Messenger! http://clk.atdmt.com/UKM/go/107571437/direct/01/___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Opportunities
Hi there I am a UK based Computer Science Masters mature student who is just finishing my project, which is using TinyOS and Tossim to optimise a topology based on DPSO (Distributed Particle Swarm Optimisation). Having enjoyed learning and working with TinyOS so much I was wondering if anyone could point me in the direction of companies in the UK that I could approach. I have fifteen years experience in the IT industry and this being my first experience of this industry I would love to do more. I appreciate any thoughts/contacts/questions you have. Regards Anthony Microsoft is solely responsible for any e-tags and links that they put on the bottom of my emails. These are placed on my emails without my consent and against my will. I have neither agreed to them nor endorse them. I am sorry you are forced to receive them. If you do not like them, please send a complaint to Microsoft. _ Discover Bird's Eye View now with Multimap from Live Search http://clk.atdmt.com/UKM/go/111354026/direct/01/___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] TinyOS 2.0.2 and Fedora 9
Hi there I have recently upgraded to Fedora 9 from 7, this entailed a complete rebuild of my machine. I have since installed TinyIS 2.0.2 again, I was developing under Fedora 7, and after completing the install, installing all the rpm files as detailed on the page: http://www.tinyos.net/tinyos-2.x/doc/html/install-tinyos.html, running CVS and having all the environment variables set I tried to compile the application Blink and get the following error messages: /opt/tinyos-2.x/tos/lib/tossim/tossim.c: In member function ‘variable_string_t Variable::getData()’: /opt/tinyos-2.x/tos/lib/tossim/tossim.c:116: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim.c:117: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim.c: In member function ‘Variable* Mote::getVariable(char*)’: /opt/tinyos-2.x/tos/lib/tossim/tossim.c:169: warning: deprecated conversion from string constant to ‘char*’ I have searched on this but unable to find anything. Any advise? _ Make a mini you and download it into Windows Live Messenger http://clk.atdmt.com/UKM/go/111354029/direct/01/ ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] TinyOS 2.0.2 and Fedora 9
Further to the email below, I missed the following error messages: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* _wrap_nesc_app_t_numVariables_set(PyObject*, PyObject*)’: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:1999: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2000: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* _wrap_nesc_app_t_numVariables_get(PyObject*, PyObject*)’: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2066: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2067: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* _wrap_nesc_app_t_variableNames_set(PyObject*, PyObject*)’: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2134: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2135: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* _wrap_nesc_app_t_variableNames_get(PyObject*, PyObject*)’: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2202: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2203: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* _wrap_nesc_app_t_variableTypes_set(PyObject*, PyObject*)’: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2270: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2271: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* _wrap_nesc_app_t_variableTypes_get(PyObject*, PyObject*)’: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2338: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2339: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* _wrap_nesc_app_t_variableArray_set(PyObject*, PyObject*)’: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2406: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2407: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* _wrap_nesc_app_t_variableArray_get(PyObject*, PyObject*)’: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2474: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2475: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* _wrap_delete_nesc_app_t(PyObject*, PyObject*)’: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2554: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2555: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* _wrap_new_Mote(PyObject*, PyObject*)’: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2698: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2699: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* _wrap_new_Tossim(PyObject*, PyObject*)’: /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2997: warning: deprecated conversion from string constant to ‘char*’ /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2998: warning: deprecated conversion from string constant to ‘char*’ g++ -c -shared -fPIC -o build/micaz/tossim.o -g -O0 -DIDENT_PROGRAM_NAME=\"BlinkAppC\" -DIDENT_USER_ID=\"root\" -DIDENT_HOSTNAME=\"FedAnt.bikefact\" -DIDENT_USER_HASH=0x7850d686L -DIDENT_UNIX_TIME=0x48f0cb2bL -DIDENT_UID_HASH=0x42e127fdL /opt/tinyos-2.x/tos/lib/tossim/tossim.c -I/usr/include/python2.5 -I/opt/tinyos-2.x/tos/lib/tossim > From: [EMAIL PROTECTED] > To: tinyos-help@millennium.berkeley.edu > Subject: TinyOS 2.0.2 and Fedora 9 > Date: Sat, 11 Oct 2008 16:27:17 +0100 > > > Hi there > > I have recently upgraded to Fedora 9 from 7, this entailed a complete rebuild > of my machine. I have since installed TinyIS 2.0.2 again, I was developing > under Fedora 7, and after completing the install, installing all the rpm > files as detailed on the page: > http://www.tinyos.net/tinyos-2.x/doc/html/install-tinyos.html, running CVS > and having all the environment variables set I tried to compile t
Re: [Tinyos-help] TinyOS 2.0.2 and Fedora 9
All, Please ignore this, I found the answer on an email chain. All solved now. Thank you. > From: [EMAIL PROTECTED] > To: tinyos-help@millennium.berkeley.edu > Subject: RE: TinyOS 2.0.2 and Fedora 9 > Date: Sat, 11 Oct 2008 16:59:26 +0100 > > > Further to the email below, I missed the following error messages: > > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* > _wrap_nesc_app_t_numVariables_set(PyObject*, PyObject*)’: > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:1999: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2000: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* > _wrap_nesc_app_t_numVariables_get(PyObject*, PyObject*)’: > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2066: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2067: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* > _wrap_nesc_app_t_variableNames_set(PyObject*, PyObject*)’: > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2134: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2135: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* > _wrap_nesc_app_t_variableNames_get(PyObject*, PyObject*)’: > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2202: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2203: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* > _wrap_nesc_app_t_variableTypes_set(PyObject*, PyObject*)’: > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2270: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2271: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* > _wrap_nesc_app_t_variableTypes_get(PyObject*, PyObject*)’: > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2338: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2339: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* > _wrap_nesc_app_t_variableArray_set(PyObject*, PyObject*)’: > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2406: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2407: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* > _wrap_nesc_app_t_variableArray_get(PyObject*, PyObject*)’: > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2474: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2475: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* > _wrap_delete_nesc_app_t(PyObject*, PyObject*)’: > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2554: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2555: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* > _wrap_new_Mote(PyObject*, PyObject*)’: > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2698: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2699: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx: In function ‘PyObject* > _wrap_new_Tossim(PyObject*, PyObject*)’: > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2997: warning: deprecated > conversion from string constant to ‘char*’ > /opt/tinyos-2.x/tos/lib/tossim/tossim_wrap.cxx:2998: warning: deprecated > conversion from string constant to ‘char*’ > g++ -c -shared -fPIC -o build/micaz/tossim.o -g -O0 > -DIDENT_PROGRAM_NAME=\"BlinkAppC\" -DIDENT_USER_ID=\"root\" > -DIDENT_HOSTNAME=\"FedAnt.bikefact\" -DIDENT_USER_HASH=0x7850d686L > -DIDENT_UNIX_TIME=0x48f0cb2bL -DIDENT_UID_HASH=0x42e127fdL > /opt/tinyos-2.x/tos/lib/tossim/tossim.c -I/usr/include/python2.5 > -I/opt/tinyos-2.x/tos/lib/tossim > > > > > >> From: [EMAIL PROTECTED] >> To: tinyos-help@millennium.berkeley.edu >> Subject: TinyOS 2.0.2 and Fedora 9 >> Date: Sat, 11 Oct 20
