[Tinyos-help] IPv6 and serialforwarder/TinyOS
Hi, I want to connect a sensor to an IPv6 host. I thought there is an IPv6 version of serialforwarder, but I was unable to find it. Could anyone please send me a link to the IPv6 open source serialforwarder? Also, is there any other method that I can use to connect sensors to IPv6 hosts beside the serialforwarder. Thank you, Mostafa ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] About energy consumption per byte for R/W on the AT45DB flash
Hi David, Some months ago I worked with the FlashBridge tools on my micaz motes, in order to access the external flash and swap my buffers of information between RAM and Flash. You gave me a lot of good points on it, so I would like to ask you further information. I remember a good graph you sent to me about the current consumption on a AT45DB flash memory. Do you have more information on it? I mean, I need to estimate (also in a raw fashion) how much the writing and reading operations consume. Per byte read and written will be the best ;) Waiting for your answer, Best regards Daniele Daniele Munaretto Researcher DoCoMo Communications Laboratories Europe GmbH Landsbergerstraße 312 80687 Munich Germany Mobile : +49- 162- 2919-218 Office : +49- 89- 56824-218 Fax : +49- 89- 56824-300 [EMAIL PROTECTED] visit us in http://www.docomolab-euro.com http://www.docomolab-euro.com/ Managing Directors (Geschäftsführer): Dr. Toru Otsu, Dr. Narumi Umeda, Kazushige Yoshida Amtsgericht München, HRB 132967 ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] MDA300 Drivers
Hi, I am plan to buy MDA300 from xbow.where can i find latest drivers for MDA300 or it will shipped along with the board.Also do u know that these drivers have EEPROM(in MDA)interface. Plz help me in this regard. With thanks Sang___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] SurgeM.nc (accede to TOS_Msg)
Hello, I am working with the SurgeTelos application and I have a doubt that is centered in the SurgeM.nc file. I need to accede to the package (to the TOS_Msg), that is given back to the Send.sendDone (). One of the parameters of the method event result_t Send.sendDone (TOS_MsgPtr pMsg, result_t success) of the SurgeM.nc, is the message that has been sent by the node, no? From the TOS_MsgPtr it would have to obtain the TOS_Msg thus to be able to put it like parameter in the Send.send (gMsgBuffer, sizeof (SurgeMsg)). The way that I have thought is: TOS_Msg msg = *pMsg; But, not if it is the correct way to do it. Somebody could say to me if it is it, and in other case, to give some alternative me? Thanks _ ¿Estás pensando en cambiar de coche? Todas los modelos de serie y extras en MSN Motor. http://motor.msn.es/researchcentre/ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] (no subject)
Hi, i have a problem. I have to take datas from two different sensors on
Tmote-Sky(Light and Temperature) and send on two differente radio channel to an
other tmote-sky. After the transmission, radio turn off and then restart one
second before the next ADC sampling (I hope!).
I wrote this code but the transmitter doesn't work well
configuration SenseToRfm {
// this module does not provide any interface
}
implementation
{
components Main, SenseToInt, IntToRfm, IntToRfm_8, IntToLeds, TimerC, ADCC,
HamamatsuC as Sensor, DemoSensorC as Sensor_1, SenseToInt_PP;
Main.StdControl - SenseToInt;
Main.StdControl - IntToRfm;
Main.StdControl - SenseToInt_PP;
Main.StdControl - IntToRfm_8;
SenseToInt.Timer - TimerC.Timer[unique(Timer)];
SenseToInt.TimerControl - TimerC;
SenseToInt.ADC - Sensor.PAR;
SenseToInt.ADCControl - Sensor;
SenseToInt.IntOutput - IntToRfm;
IntToLeds - SenseToInt.IntOutput;
SenseToInt_PP.Timer - TimerC.Timer[unique(Timer)];
SenseToInt_PP.TimerControl - TimerC;
SenseToInt_PP.ADC - Sensor_1;
SenseToInt_PP.ADCControl - Sensor_1;
SenseToInt_PP.IntOutput - IntToRfm_8;
}
SenseToInt and SenseToInt_PP are the same, the only change is the sensor.
The code of IntToRfm is:
includes IntMsg;
configuration IntToRfm
{
provides {
interface IntOutput;
interface StdControl;
}
}
implementation
{
components IntToRfmM, TimerC, GenericComm as Comm
// HPLPowerManagement is only needed for AVR based platforms
#ifdef __AVR__
, HPLPowerManagementM as PM
#endif
;
#ifdef __AVR__
CountSleepRadioM.PowerManagement - PM;
CountSleepRadioM.Enable - PM.Enable;
#endif
IntOutput = IntToRfmM;
StdControl = IntToRfmM;
StdControl = TimerC;
IntToRfmM.Send - Comm.SendMsg[AM_INTMSG];
IntToRfmM.SubControl - Comm;
IntToRfmM.Timer - TimerC.Timer[unique(Timer)];
}
and IntToRfmM is:
includes IntMsg;
includes Timer;
module IntToRfmM
{
uses {
interface StdControl as SubControl;
interface SendMsg as Send;
interface Timer;
}
// these are only needed for Atmel AVR based platforms
#ifdef __AVR__
uses interface PowerManagement;
uses command result_t Enable();
#endif
provides {
interface IntOutput;
interface StdControl;
}
}
implementation
{
bool pending;
TOS_Msg data;
command result_t StdControl.init() {
pending = FALSE;
#ifdef __AVR__
call Enable();
call PowerManagement.adjustPower();
#endif
call SubControl.init();
return SUCCESS;
}
command result_t StdControl.start()
{
call SubControl.start();
return SUCCESS;
}
command result_t StdControl.stop()
{
return SUCCESS;
}
command result_t IntOutput.output(uint16_t value)
{
IntMsg *message = (IntMsg *)data.data;
if (!pending)
{
pending = TRUE;
message-val = value;
atomic {
message-src = TOS_LOCAL_ADDRESS;
}
if (call Send.send(TOS_BCAST_ADDR, sizeof(IntMsg), data))
return SUCCESS;
pending = FALSE;
}
return FAIL;
}
event result_t Send.sendDone(TOS_MsgPtr msg, result_t success)
{
if (pending msg == data)
{
pending = FALSE;
signal IntOutput.outputComplete(success);
}
call SubControl.stop();
call Timer.start( TIMER_ONE_SHOT, 4000 );
return SUCCESS;
}
event result_t Timer.fired()
{
call SubControl.start();
return SUCCESS;
}
}
The difference between IntToRfm and IntToRfm_8 is the value of AM_INTMSG (4 for
IntToRfm, 8 for IntToRfm_8). I would like to know if the code is correct and
whick are the bugs. Please help.
Thanks
Simone
--
Leggi GRATIS le tue mail con il telefonino i-mode di Wind
http://i-mode.wind.it/
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Reading time form basestation
Hi all, I am using tmote sky, tinyos 2 and fedora core 6. I hope that you can help me to read the time from BaseStation node ( attached to USB); so when the packets arrive from other mote to the baseStation, I can read it's arriving time! Is it possible to achieve this by modifying the basestation code. any advices will be appreciated . kind regards sara ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] standard input/output facilities of ncc
Dear all, It seems that ncc does not fully support standard input/output of GNU? It does not recognize fopen(), the linker keeps telling undefined reference to 'fopen' but strangely, it can recognize fclose()... Anyone knows the reason and how to deal with it? Thank you. Best Regards, Enric Y.H. Zheng___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Power saving in MicaZ.
Hi, I am writing Time Sync and Sleep scheduling algorithms for MicaZ.I don't know which component draws how much power with respect to time. Can u plz help me. With regards Sangeeth___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems with readToneDetector()
Hi Phil,
Sorry for not having replied before, I've been away a couple of weeks.
When there is a tone, thee LED toggles too, that's why I don't know what's
happening.
Thank you very much for your help.
Regards,
Jorge
On 4/3/07, Philip Levis [EMAIL PROTECTED] wrote:
On Mar 28, 2007, at 2:38 AM, Jorge Grande wrote:
Hello everybody,
I'm using TinyOS 2.0 and I'm trying to write an application for two
micaz motes using the microphone. One of the two motes (mote 1)
will beep each 1000 ms and the other one (mote 2), once it has
detected the tone, will toggle the green led (if it doesn't detect
the tone, it will turn one the red led). This mote checks every 50
ms if the tone has been detected; I'm using command startPeriodic
including in tos/lib/timer and command readToneDetector including
in tos/sensorboards/mts300/MicSetting.nc.
Here is part of the mote 2 application:
...
event void Timer.fired() {
if (call MicSetting.readToneDetector() == 0) //tone has been
detected
{call Leds.led1Toggle();}
else // tone has not been detected
{call Leds.led0On();}
}
async event error_t MicSetting.toneDetected() {
return SUCCESS;
}
...
The problem is that mote 2 is continuously toggling the green led,
even if mote 1 is not beeping but I don't know why.
Can anyone help me?
I'd email the folks who wrote the drivers; I'm not sure they all
ready tinyos-help regularly. It looks like the driver is just
checking an interrupt line when it does this test. Looking at the
code, it seems like it just returns 1 when the line is high and 0
when it's low... which suggests that the documentation of the return
value is incorrect. Does the LED toggle when there is a tone, or does
it stop toggling?
Phil
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] TOSSIM HELP
How to specify which mote is base station in tossim ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] TOSSIM HELP
U can do it by specifying 0 for the base station. cheers,vinay. santosh bhima [EMAIL PROTECTED] wrote: How to specify which mote is base station in tossim ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help - Ahhh...imagining that irresistible new car smell? Check outnew cars at Yahoo! Autos.___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Motelab motes sensorboard help
Hi all, I'm newbie to tinyos. I'm using motelab for test my application, but I don't know what sensorborad use to my application I read on motelab site that every Tmote sky has a light, humidity and temperature sensor I can use HamamatsuC and HumidityC in /tos/plataform/telos Or I must use InternalTempC, InternalVoltageC and VoltageM in /tos/platafom/msp430 And in this case where is the light sensor? And the external temp sensor? I can use Oscope application in \contrib\moteiv\apps\Oscilloscope\ when there is all sensorboard? I'm sorry for my English! Thanks for the help, Ciro ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problems with TOSSIM
Hello, I'm using the latest cvs-version of tinyos 2.x. Compiling the Blink example with make micaz sim as described in Lesson 11 of the tinyos 2.x tutorial generate some errors: $ make micaz sim error.out In file included from /opt/tinyos-2.x/tos/lib/tossim/sim_mac.c:34, from /opt/tinyos-2.x/tos/lib/tossim/tos.h:89: /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:14: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:97: warning: location of shadowed declaration /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:23: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:97: warning: location of shadowed declaration /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c: In function `sim_gain_allocate_link': /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:160: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:97: warning: location of shadowed declaration /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c: At top level: /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:167: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:97: warning: location of shadowed declaration In file included from /opt/tinyos-2.x/tos/platforms/mica/sim/HilTimerMilliC.nc:4 1, from /opt/tinyos-2.x/tos/system/TimerMilliP.nc:41, from /opt/tinyos-2.x/tos/system/TimerMilliC.nc:40, from BlinkAppC.nc:46: In component `AlarmCounterMilliP': /opt/tinyos-2.x/tos/platforms/mica/AlarmCounterMilliP.nc:30: `ATM128_CLK8_DIVIDE_32' undeclared here (not in a function) make: *** [sim-exe] Error 1 Any ideas?! Cheers Marcel ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Tmote Sky GPIO interrupt
Hey everybody,
I want to catch an impulse on the GPIO0 port of the Tmote Sky. I populated the
R14 to enable GPIO0 on the expansion connector and in my program
I am using interface MSP430Interrupt as port20, which is binded to
MSP430InterruptC.Port20 (this should be GPIO0 = port 2, pin 0).
This is a piece of my code:
result_t gpio() {
call port20.makeInput();
atomic edge = TRUE;
call port20.edge(edge);
call port20.enable();
call Leds.greenOff();
call port20.disable();
return SUCCESS;
}
async event void port20.fired()
{
call Leds.greenOn();
}
The green Led switches On and never switches Off. Can you tell me why? I call
gpio() from Timer.Fired event (every 4 seconds) and following command is also
switching off
the Led. But this is not going to happen. I am using Boomerang 2.0.4.
I would appriciate any help. Thanks, Jan.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] MDA 320 driver-PLZ HELP!!!!!!!!!!!!
Hi all, i am using micaz board with data acquisition board MDA320.But i don't find any drivers for MDA320 in net.we will be getting MDA320 from xbow in next few days.Does any one knew whether xbow supplies MDA320 driver CD along with the board?. If not can anyone Plz help me where can i find the MDA320 driver.Any help will be appreciated because i am strucked up in my work. With thanks Sang.___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Regarding Gps recievers of MTS 420
Hi all, thnx for ur previous responses.I tried running precomplied XMTS 420 app. that comes within Moteview software but it didn't gave GPS readings properly. The readings for all sensors except GPS receivers were shown correctly.But the fields corresponding to Gps like lat.,long. were shown as 0. So what may be the possible reason for this failure. I also tried XsensorMTS420 app. that comes within contrib/xbow folder but the same thing happened there also. The readings for all sensors were shown correctly except gps for which readings for all the fields were shown as 0. I saw the output using Xlisten app.as mentioned in getting started guide of Xbow.In case of output on cygwin some lines like bad-crc and fixed quality invalid was also coming.So what do they really mean Thanks Ankur jain - Check out what you're missing if you're not on Yahoo! Messenger ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: How to change TimerA to TimerB
On Thursday 19 April 2007 09:45, Firat TARAKTAS wrote: Hi Steve, I am mailing you according to statement below (TimerTMilli components uses Timer A). Do you inform me about how to make Timer to use TimerB instead of Timer A. Thanks for your help. I was wrong. In tos2 on msp430, TimerTMilli components *do* use Timer B. You can see the linkages in the msp430's configuration for AlarmMilli32C. Sorry; we were working on a project recently where we didn't have a 32kHz crystal and so changed the code to run the virtual timer off of Timer A. Best, Steve Firat TARAKTAS -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve McKown Sent: Thursday, April 19, 2007 5:37 PM To: tinyos-help@Millennium.Berkeley.EDU Subject: Re: [Tinyos-help] Simple question on TimerTMilli Hi, On Thursday 19 April 2007 05:53, Muhammad Azhar wrote: Hi all, I apologise if this is a rather basic question, but to set a timer to fire exactly 1s periodically (using TimerTMilli), do I input startPeriodic(1000) or startPeriodic(1024)? 'Coz all the while, I've always used the former, but I realised that it's never 1 sec, always faster than that. A colleague told me that using 1024 would make the timer fire every 1 sec, but didn't explain why. Thus, I'd like to clarify with you guys. How exactly does the 1024 convert to 1s? What if I'd like a timer of 1min then? Many thanks for your help. On the msp430 platforms, the millisecond virtual timer servicing TimerTMilli components uses Timer A. Timer A is configured to use SMCLK, which is set to DCO/4. The DCO is calibrated to 4*2^20 Hz, so Timer A's 1MHz timer is in fact 2^20 Hz. Because the conversion from microseconds to milliseconds in the timer code effectively uses a 10-bit shift, 1 second is 2^10 ticks, or 1024. So, 1024 ticks/sec * 60 secs/min = 61440 ticks/min. In case you're wondering why it's set up this way: converting between powers of 2 needs only fast bit shifts. Far more efficient than, say, dividing by 1000. Cheers, Steve ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help !DSPAM:462792d3221931902076913! ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] MDA300 Drivers
Yes, MDA300 drivers are available in CVS sourceforge. I don't know if these have readily available EEPROM interface. http://tinyos.cvs.sourceforge.net/tinyos/tinyos-1.x/contrib/xbow/ The pre-compiled XMesh apps for MDA300 is available in MoteView and the source for this app is available in MoteWorks. Regards, Giri From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of sangeeth kumar Sent: Friday, April 20, 2007 12:19 AM To: [EMAIL PROTECTED] Cc: tinyos-help@Millennium.Berkeley.EDU Subject: [Tinyos-help] MDA300 Drivers Hi, I am plan to buy MDA300 from xbow.where can i find latest drivers for MDA300 or it will shipped along with the board.Also do u know that these drivers have EEPROM(in MDA)interface. Plz help me in this regard. With thanks Sang http://adworks.rediff.com/cgi-bin/AdWorks/click.cgi/www.rediff.com/sign ature-home.htm/[EMAIL PROTECTED]/1166323_1160412/1165498/1?PARTNER=3OA S_QUERY=null target=new ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] MDA300 Drivers
On 4/20/07, Giri Baleri [EMAIL PROTECTED] wrote: Yes, MDA300 drivers are available in CVS sourceforge. I don't know if these have readily available EEPROM interface. http://tinyos.cvs.sourceforge.net/tinyos/tinyos-1.x/contrib/xbow/ The pre-compiled XMesh apps for MDA300 is available in MoteView and the source for this app is available in MoteWorks. Regards, Giri -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *sangeeth kumar *Sent:* Friday, April 20, 2007 12:19 AM *To:* [EMAIL PROTECTED] *Cc:* tinyos-help@Millennium.Berkeley.EDU *Subject:* [Tinyos-help] MDA300 Drivers Hi, I am plan to buy MDA300 from xbow.where can i find latest drivers for MDA300 or it will shipped along with the board.Also do u know that these drivers have EEPROM(in MDA)interface. Plz help me in this regard. With thanks Sang http://adworks.rediff.com/cgi-bin/AdWorks/click.cgi/www.rediff.com/signature-home.htm/[EMAIL PROTECTED]/1166323_1160412/1165498/1?PARTNER=3OAS_QUERY=null+target=new+ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] MDA300 Drivers
On 4/20/07, Demin Wang [EMAIL PROTECTED] wrote Does there exist an MDA300 driver for Tinyos2? Also is it possible to get the source code of XMesh free? or we have to pay for that. Thanks, Demin On 4/20/07, Giri Baleri [EMAIL PROTECTED] wrote: Yes, MDA300 drivers are available in CVS sourceforge. I don't know if these have readily available EEPROM interface. http://tinyos.cvs.sourceforge.net/tinyos/tinyos-1.x/contrib/xbow/ The pre-compiled XMesh apps for MDA300 is available in MoteView and the source for this app is available in MoteWorks. Regards, Giri -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *sangeeth kumar *Sent:* Friday, April 20, 2007 12:19 AM *To:* [EMAIL PROTECTED] *Cc:* tinyos-help@Millennium.Berkeley.EDU *Subject:* [Tinyos-help] MDA300 Drivers Hi, I am plan to buy MDA300 from xbow.where can i find latest drivers for MDA300 or it will shipped along with the board.Also do u know that these drivers have EEPROM(in MDA)interface. Plz help me in this regard. With thanks Sang http://adworks.rediff.com/cgi-bin/AdWorks/click.cgi/www.rediff.com/signature-home.htm/[EMAIL PROTECTED]/1166323_1160412/1165498/1?PARTNER=3OAS_QUERY=null+target=new+ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] Regarding Gps recievers of MTS 420
Hello Ankur, Do you have the GPS antenna connected properly and placed under the optimal sky visibility? Please look for GPS _fix field. If it reads 0, that means the receiver hasn't locked into GPS satellites. You may have to move the GPS antenna around until you get a valid fix (value =1). The Xlisten can't parse packets from XMTS420, a XMesh-enabled apps and hence you should use XServe/MoteView for this app. I hope that helps, Giri From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ankur jain Sent: Friday, April 20, 2007 8:03 AM To: tinyos-help Subject: [Tinyos-help] Regarding Gps recievers of MTS 420 Hi all, thnx for ur previous responses.I tried running precomplied XMTS 420 app. that comes within Moteview software but it didn't gave GPS readings properly. The readings for all sensors except GPS receivers were shown correctly.But the fields corresponding to Gps like lat.,long. were shown as 0. So what may be the possible reason for this failure. I also tried XsensorMTS420 app. that comes within contrib/xbow folder but the same thing happened there also. The readings for all sensors were shown correctly except gps for which readings for all the fields were shown as 0. I saw the output using Xlisten app.as mentioned in getting started guide of Xbow.In case of output on cygwin some lines like bad-crc and fixed quality invalid was also coming.So what do they really mean Thanks Ankur jain Check out what you're missing if you're not on Yahoo! Messenger http://us.rd.yahoo.com/mail/in/ymessenger/*http://in.messenger.yahoo.co m/ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Motelab motes sensorboard help
ciao ciro, Use the TELOS one. Cheers,vinay. Arslogica. Ciro Cardone [EMAIL PROTECTED] wrote: Hi all, Im newbie to tinyos. Im using motelab for test my application, but I dont know what sensorborad use to my application I read on motelab site that every Tmote sky has a light, humidity and temperature sensor I can use HamamatsuC and HumidityC in /tos/plataform/telos Or I must use InternalTempC, InternalVoltageC and VoltageM in /tos/platafom/msp430 And in this case where is the light sensor? And the external temp sensor? I can use Oscope application in \contrib\moteiv\apps\Oscilloscope\ when there is all sensorboard? Im sorry for my English! Thanks for the help, Ciro ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help - Ahhh...imagining that irresistible new car smell? Check outnew cars at Yahoo! Autos.___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problems with TOSSIM
On Apr 20, 2007, at 7:04 AM, Marcel wrote: Hello, I'm using the latest cvs-version of tinyos 2.x. Compiling the Blink example with make micaz sim as described in Lesson 11 of the tinyos 2.x tutorial generate some errors: $ make micaz sim error.out In file included from /opt/tinyos-2.x/tos/lib/tossim/sim_mac.c:34, from /opt/tinyos-2.x/tos/lib/tossim/tos.h:89: /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:14: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:97: warning: location of shadowed declaration /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:23: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:97: warning: location of shadowed declaration /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c: In function `sim_gain_allocate_link': /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:160: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:97: warning: location of shadowed declaration /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c: At top level: /opt/tinyos-2.x/tos/lib/tossim/sim_gain.c:167: warning: declaration of `link' shadows global declaration /usr/include/sys/unistd.h:97: warning: location of shadowed declaration In file included from /opt/tinyos-2.x/tos/platforms/mica/sim/ HilTimerMilliC.nc:4 1, from /opt/tinyos-2.x/tos/system/TimerMilliP.nc:41, from /opt/tinyos-2.x/tos/system/TimerMilliC.nc:40, from BlinkAppC.nc:46: In component `AlarmCounterMilliP': /opt/tinyos-2.x/tos/platforms/mica/AlarmCounterMilliP.nc:30: `ATM128_CLK8_DIVIDE_32' undeclared here (not in a function) make: *** [sim-exe] Error 1 We're in the midst of preparing the RPM for 2.0.1, and so there are a few tweaks going on as code moves around. Please be patient. Alternatively, check out the code from two weeks ago cvs up -D 2 weeks ago Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: RE: [Tinyos-help] MDA300 Drivers
Hi Giri, Sorry Giri,a blunder mistake.It is not MDA300,it is MDA320.where can i find latest drivers for MDA320 or it will shipped along with the board. Plz help as i was strucked up in my work. With regards Sang On Fri, 20 Apr 2007 Giri Baleri wrote : Yes, MDA300 drivers are available in CVS sourceforge. I don't know if these have readily available EEPROM interface. http://tinyos.cvs.sourceforge.net/tinyos/tinyos-1.x/contrib/xbow/ The pre-compiled XMesh apps for MDA300 is available in MoteView and the source for this app is available in MoteWorks. Regards, Giri From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of sangeeth kumar Sent: Friday, April 20, 2007 12:19 AM To: [EMAIL PROTECTED] Cc: tinyos-help@Millennium.Berkeley.EDU Subject: [Tinyos-help] MDA300 Drivers Hi, I am plan to buy MDA300 from xbow.where can i find latest drivers for MDA300 or it will shipped along with the board.Also do u know that these drivers have EEPROM(in MDA)interface. Plz help me in this regard. With thanks Sang http://adworks.rediff.com/cgi-bin/AdWorks/click.cgi/www.rediff.com/sign ature-home.htm/[EMAIL PROTECTED]/1166323_1160412/1165498/1?PARTNER=3OA S_QUERY=null target=new ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Simple question on TimerTMilli
On 4/20/07, Steve McKown [EMAIL PROTECTED] wrote: Hi Phil, On Thursday 19 April 2007 10:24, Philip Levis wrote: On Apr 19, 2007, at 7:37 AM, Steve McKown wrote: H In case you're wondering why it's set up this way: converting between powers of 2 needs only fast bit shifts. Far more efficient than, say, dividing by 1000. Actually, the reason has more to do with error and the effort/cost it would take to handle it. If you want 1kHz rather than 1.024kHz units, then you need to convert. Here's a modified version of a post I sent to the EmStar list a while back, when someone suggested just doing this ((timer * 1024) / 1000): The issue is whether you want precise 1024Hz timers or imprecise 1000Hz timers. You can get reasonably precise 1000Hz timers, but only if you are willing to do a bit of bookkeeping to keep track of partial ticks. This assumes a certain source clock frequency, right? In one project, we used a true 8MHz (8*10^6, not 8*2^20) crystal to get true microsecond granularity out of Timer A (SMCLK/8). The problem is if you want true ms: true ms = true us/1000, which is a far more expensive operation than pseudo ms = pseudo us 10. This is why I assume (and there's my problem of course...) that the original design decided to use 2^10Hz for milliseconds and 2^20Hz for microseconds and then selected the clock sources accordingly. Are we talking from different sides of the same point, or am I still missing it (the point)? All the best, Steve It sounds like you're both talking about the same point. Though, to be precise according to the TEP, just the interface TimerTMilli does refer to true milliseconds, only with potentially big, unspecified error bars. And as you note, in practice, most TinyOS platforms up to this point more conveniently measure time with 1/32768 of a second precision, from which 1/1024 of a second easily derives. So, the keen TinyOS user will use 1024 ticks per second in the timer milli interface -- though this is actually slightly platform dependent code, because it is absolutely in no way guaranteed to be true for all platforms. Partly because, there are many other sources of variation on a clock to make it deviate from precise 1024 or 1000 ticks per second -- such as temperature, voltage, component tolerances, etc. So the expert TinyOS user that *really* cares about true milliseconds will use some form of time synchronization from a more reliable, external clock source. Cory ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] CC1000 / BMAC In TOSSIM?
Hello! *I am running Tinyos build 1.1.15 I am trying to look at the affects of energy saving MAC modes in TOSSIM. I have finally managed to realize that I am not in fact missing something in finding the BMAC implementation but that it is included CC1000 Mica2 radio stack. My question is twofold 1 - Is there anyway to get TOSSIM to work with the CC1000 (or any other BMAC implementation)? I see that while there is a /platform/pc/CC1000Radio/ folder it says that the implementation there does not really work. i.e. if i modified the listening mode it will not change anything in the simulation. 2 - If there is no way to see data for BMAC are there any parameters in the mica1 stack that is used by TOSSIM that attribute to power management? The only thing I have been able to found is the HPLPowerManagementM module which allows one to enable power management but not to set a particular level. Thanks, Michael Gregoire Department of Electrical and Computer Engineering University of Massachusetts @ Amherst ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Simple question on TimerTMilli
On Apr 20, 2007, at 8:49 AM, Steve McKown wrote: This assumes a certain source clock frequency, right? In one project, we used a true 8MHz (8*10^6, not 8*2^20) crystal to get true microsecond granularity out of Timer A (SMCLK/8). The problem is if you want true ms: true ms = true us/1000, which is a far more expensive operation than pseudo ms = pseudo us 10. This is why I assume (and there's my problem of course...) that the original design decided to use 2^10Hz for milliseconds and 2^20Hz for microseconds and then selected the clock sources accordingly. It does. It turns out the operation is only expensive because the msp430-gcc doesn't do multiply well, so it is disabled in compilation. Specifically, it can produce incorrect output (doesn't multiply right) and can generate output that the assembler rejects. If you look at the Boomerang code, there are a couple places where multiplication is commonly but narrowly used (e.g., the random number generator) that they use assembly (well, directly address registers). Are we talking from different sides of the same point, or am I still missing it (the point)? Nope, you're right on. The one thing is that as soon as you have a 16MHz clock you can do 1024Hz perfectly (15625 ticks). Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Tmote Sky GPIO interrupt
If you populate R14, you need to set the corresponding connected pin to input
In Boomerang:
TOSH_MAKE_ADC3_INPUT();
-Joe
On 4/20/07, Jan Soukup [EMAIL PROTECTED] wrote:
Hey everybody,
I want to catch an impulse on the GPIO0 port of the Tmote Sky. I populated the
R14 to enable GPIO0 on the expansion connector and in my program
I am using interface MSP430Interrupt as port20, which is binded to
MSP430InterruptC.Port20 (this should be GPIO0 = port 2, pin 0).
This is a piece of my code:
result_t gpio() {
call port20.makeInput();
atomic edge = TRUE;
call port20.edge(edge);
call port20.enable();
call Leds.greenOff();
call port20.disable();
return SUCCESS;
}
async event void port20.fired()
{
call Leds.greenOn();
}
The green Led switches On and never switches Off. Can you tell me why? I call
gpio() from Timer.Fired event (every 4 seconds) and following command is also
switching off
the Led. But this is not going to happen. I am using Boomerang 2.0.4.
I would appriciate any help. Thanks, Jan.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] CC2420.h CC2420_SRXENC
Hello all! I'm not sure if this is the correct list to post this to, but I believe I've found a mistake in tos/chips/cc2420.h on line 163. CC2420_SRXENC = 0x0d, should actually be CC2420_STXENC = 0x0d, as defined at the bottom page 60 of the CC2420 radio datasheet. I figured I would post it here to document it. Cheers. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: Re: tossim segfaults on a tutorial app in a Linux machine
Hi, I got this from the archives. On Feb 27, 2007, at 9:27 PM, Philip Levis wrote: * On Feb 27, 2007, at 10:49 AM, pavan kumar wrote:* *** I am having a similar kind of error as posted in the link* * http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006- * * December/021625.html* *** Python 2.4.2 (#1, Feb 12 2006, 03:59:46)* * [GCC 4.1.0 20060210 (Red Hat 4.1.0-0.24)] on linux2* * Type help, copyright, credits or license for more * * information.* * from TOSSIM import ** * t = Tossim([])* * t.runNextEvent()* * False* * m = t.getNode(32);* * m.bootAtTime(1000);* * Segmentation fault* * The link does not provide any solution, we would like to know how * * you people* * solved it.* ** *** Could you perhaps answer the two questions I asked in that thread?* Here are the next steps to take: If giving a trace doesn't tell you where you are, then you need to step through the code. The first thing to do is determine if the SEGV occurs before, during, or after the TOSSIM function underlying bootAtTime(). So start python in gdb, and break on bootAtTime. This function is defined in tossim.c. If you SEGV before you get there, it's happening on the way in (Python - C++ - C); if it SEGVs after the breakpoint, it's either the function or on the way out (C - C++ - Python). You can break at the C++ level by breaking on Mote::bootAtTime. The issue is that I can't reproduce the problem, so I can't solve it by myself. Phil I used gdb ad traced the problem to simTime = t; in SimMoteP.nc... I tried the most recent CVS version, but I think the problem persisted. I get quite strange interpretations from stuff, especially from reading source codes and extracting information from it, but I may have gotten to the point now. You see, TOSSIM uses a C++ class to represent the mote, and when python calls a function it is wrapped to this class's corresponding function, which calls the SimMoteP's corresponding function. It seems that what happens is that the component itself was not created, so, when it tries to access variables such as startTime, which does not exist, segmentation fault happens. What I did was to prefix the variables with m_ (to avoid name clashes) and put them also into the class Mote. Although the node limit is 1000, which I also altered but whose effects I have not yet evaluated, I changed the tmp's in SimMoteP.nc from int to unsigned long int, which is the type of the value returned by sim_node() and the parameter type for sim_set_node(). I hope you forgive my mistakes in this message whatsoever =D -- Segmentation Fault ...de onde concluímos que a falha de segmentação é ninfomaníaca. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] CC2420.h CC2420_SRXENC
Thanks Jon, I'll take a look. -David -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Green Sent: Friday, April 20, 2007 12:19 PM To: tinyos-help@Millennium.Berkeley.EDU Subject: [Tinyos-help] CC2420.h CC2420_SRXENC Hello all! I'm not sure if this is the correct list to post this to, but I believe I've found a mistake in tos/chips/cc2420.h on line 163. CC2420_SRXENC = 0x0d, should actually be CC2420_STXENC = 0x0d, as defined at the bottom page 60 of the CC2420 radio datasheet. I figured I would post it here to document it. Cheers. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] SurgeM.nc (accede to TOS_Msg)
Sorry, but your use of the word accede is confusing...but I think you are asking how to copy a TOS_Msg to a new buffer. If that is the case the syntax you show msg = *pMsg; is called structure assignment, and may or may not work depending on the compiler. I would expect the compiler to complain if it can't do it, but I would also want to try some experiments to verify the behavior. Another way to do it is brute force: memcpy( destptr, srcptr, numbytes ); MS Elena Lamaza wrote: Hello, I am working with the SurgeTelos application and I have a doubt that is centered in the SurgeM.nc file. I need to accede to the package (to the TOS_Msg), that is given back to the Send.sendDone (). One of the parameters of the method event result_t Send.sendDone (TOS_MsgPtr pMsg, result_t success) of the SurgeM.nc, is the message that has been sent by the node, no? From the TOS_MsgPtr it would have to obtain the TOS_Msg thus to be able to put it like parameter in the Send.send (gMsgBuffer, sizeof (SurgeMsg)). The way that I have thought is: TOS_Msg msg = *pMsg; But, not if it is the correct way to do it. Somebody could say to me if it is it, and in other case, to give some alternative me? Thanks _ ¿Estás pensando en cambiar de coche? Todas los modelos de serie y extras en MSN Motor. http://motor.msn.es/researchcentre/ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Reading time form basestation
If you are receiving packets on the host PC side you should be able to use a regular programming interfaces to get a timestamp. In java: long time = System.currentTimeMillis(); If you really want the basestation to timestamp things itself then you probably need to invent a TOS_Msg that has a starting timestamp to send from host to base to get things started. If you want the re-Motes to do the timestamping, then you need to search this list for time or clock synchronization advice. was that the question? MS sara Khad wrote: Hi all, I am using tmote sky, tinyos 2 and fedora core 6. I hope that you can help me to read the time from BaseStation node ( attached to USB); so when the packets arrive from other mote to the baseStation, I can read it's arriving time! Is it possible to achieve this by modifying the basestation code. any advices will be appreciated . kind regards sara ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] standard input/output facilities of ncc
Since ncc is generally used for Mote programming, and motes have no file system, there's nothing to fopen(). Interesting that fclose() links though... I'm not sure if this would apply to simulation code though. If that's what you're after, I would look into how dbg() works. MS Enric wrote: Dear all, It seems that ncc does not fully support standard input/output of GNU? It does not recognize fopen(), the linker keeps telling undefined reference to 'fopen' but strangely, it can recognize fclose()... Anyone knows the reason and how to deal with it? Thank you. Best Regards, Enric Y.H. Zheng ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] backoff CSMA
I don't think there is an interface for munging up the backoff behavior. Search for backoff in the CC2420RadioM.nc file to see if there's anything you can modify. Also search this list for different MAC layers that may be more to your liking. Just shutting off CSMA will probably only help thruput if you have only one transmitter. If there is more than one mote sending and they don't play nice, I'd bet that most messages will be garbaged up and useless. MS Jeong Kwanhee wrote: Hello all!! I want to increase about throughput in micaz’s surge application. So, I’m currently doing to remove backoff and ack. However, I don’t know how to disable backoff. (I found how to disable ack.) I think that I have to use CC2420Radio or CC2420Control. Is right? I can’t find and do this. Give me a hint. My experiment is using micaz, tinyos 1.x.x. Regards. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Error in motelist
Hi I had the same problem and solved it with removing brltty, according to this bugreport: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/90172 roman Rafael Marin Perez schrieb: Hi all, I have changed from Ubuntu 6.10 to New Ubuntu 7.04. The problem is I can not now compile anythings for my telosb motes, but when I do a 'motelist', I get this error: ### $motelist Use of uninitialized value in substitution (s///) at ./motelist-linux.old line 90. Use of uninitialized value in pattern match (m//) at ./motelist-linux.old line 91. Reference Device Description -- - M4A9K6H5 (none) Moteiv tmote sky ### This problem don't happen when I have to Ubuntu 6.10. I have seen the motelist code of the line 90 where it try to find the files tty* in the directory /sys/bus/usb/drivers/usb/3-2/3-2:1.0/. These files don't exist therefore motelist do this error and don't find the device name. Does anyone have any idea, whats going on? Thank you, very much. Rafa. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] (no subject)
On Fri, April 20, 2007 4:45 am, [EMAIL PROTECTED] said: Hi, i have a problem. I have to take datas from two different sensors on Tmote-Sky(Light and Temperature) and send on two differente radio channel to an other tmote-sky. After the transmission, radio turn off and then restart one second before the next ADC sampling (I hope!). 1) Why is it necessary to change the radio channel? Is there some other method you could use? 2) Would it be possible to group the transmissions in a buffer, and alternate sending the buffers instead? I know this doesn't answer your question, but sometimes people don't know there are other methods available for selecting destination. Channel switching can take a long time, and be buggy. -- The difference between the right word and the almost right word is really a large matter- it's the difference between a lightning bug and the lightning. -Twain ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Compilation error in Surge(Urgent)
Hi, I was trying to install surge application in my tmoteinvent. When i gave the command make tmoteinvent it gives me the following compilation error. When i tried to download and compile the surge from the source forge repository also it give me this error. Where can i get a stable verison.If not how can i solve the problem. $ make tmoteinvent mkdir -p build/tmoteinvent compiling Surge to a tmoteinvent binary ncc -o build/tmoteinvent/main.exe -O -I%T/lib/Route -I%T/lib/Queue -I%T/lib/Broa dcast -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=tmoteinvent -fne sc-cfile=build/tmoteinvent/app.c -board=micasb -I/opt/moteiv/tos/sensorboards/in vent -I/opt/moteiv/tos/platform/tmoteinvent -I/opt/moteiv/tos/platform/tmote -I/ opt/moteiv/tos/platform/tmote/util/uartdetect -I/opt/moteiv/tos/platform/msp430/ adc -I/opt/moteiv/tos/platform/msp430/dac -I/opt/moteiv/tos/platform/msp430/dma -I/opt/moteiv/tos/platform/msp430/resource -I/opt/moteiv/tos/platform/msp430/tim er -I/opt/moteiv/tos/platform/msp430 -I/opt/moteiv/tos/lib/util/button -I/opt/mo teiv/tos/lib/util/pool -I/opt/moteiv/tos/lib/util/null -I/opt/moteiv/tos/lib/uti l -I/opt/moteiv/tos/lib/MultiHopLQI -I/opt/moteiv/tos/lib/netsync -I/opt/moteiv /tos/lib/sp -I/opt/moteiv/tos/lib/sp/cc2420 -I/opt/moteiv/tos/lib/timer -I/opt/m oteiv/tos/platform/msp430/timer -I/opt/moteiv/tos/lib/resource -I/opt/moteiv/tos /lib/sched -I/opt/moteiv/tos/lib/Deluge -I/opt/moteiv/tos/lib/Flash/STM25P -I/op t/moteiv/tos/lib/Flash -I/opt/moteiv/tos/lib/Spram -I/opt/moteiv/tos/interfaces -I/opt/moteiv/tos/system -I/opt/moteiv/tos/lib/CC2420Radio -I/opt/moteiv/tinyos- 1.x/tos/lib/CC2420Radio -I/opt/moteiv/tinyos-1.x/tos/lib/Drip -fnesc-scheduler=T inySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask -Wl, --section-start=.text=0x4800,--defsym=_reset_vector__=0x4000 -DLIB_DELUGE -DDELU GE_NUM_IMAGES=6 -mdisable-hwmul -I%T/lib/Deluge -DIDENT_PROGRAM_NAME=\Surge\ - DIDENT_USER_ID=\student\ -DIDENT_HOSTNAME=\wd222te9\ -DIDENT_USER_HASH=0x18a a6353L -DIDENT_UNIX_TIME=0x4629260cL -DIDENT_UID_HASH=0x195027d4L Surge.nchttp://surge.nc/-lm In file included from Surge.nc:42 http://surge.nc:42/: In component `SurgeM': SurgeM.nc : In function `SendData.runTask': SurgeM.nc:89: warning: suggest parentheses around assignment used as truth value In file included from /opt/moteiv/tinyos-1.x /tos/sensorboards/micasb/PhotoTemp.n c:58, from /opt/moteiv/tinyos-1.x /tos/sensorboards/micasb/Photo.nc:53 , from Surge.nc:42 http://surge.nc:42/: In component `PhotoTempM': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc: In function `Photo StdControl.init': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:135: `TOS_ADC_PHOTO _PORT' undeclared (first use in this function) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:135: (Each undeclar ed identifier is reported only once /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:135: for each funct ion it appears in.) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:135: `TOSH_ACTUAL_P HOTO_PORT' undeclared (first use in this function) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc: In function `TempS tdControl.init': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:159: `TOS_ADC_TEMP_ PORT' undeclared (first use in this function) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:159: `TOSH_ACTUAL_T EMP_PORT' undeclared (first use in this function) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc: In function `getSa mple.runTask': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:211: implicit decla ration of function `TOSH_SET_PHOTO_CTL_PIN' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:212: implicit decla ration of function `TOSH_MAKE_PHOTO_CTL_OUTPUT' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:213: implicit decla ration of function `TOSH_CLR_TEMP_CTL_PIN' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:214: implicit decla ration of function `TOSH_MAKE_TEMP_CTL_INPUT' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:251: implicit decla ration of function `TOSH_CLR_PHOTO_CTL_PIN' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:252: implicit decla ration of function `TOSH_MAKE_PHOTO_CTL_INPUT' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:253: implicit decla ration of function `TOSH_SET_TEMP_CTL_PIN' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:254: implicit decla ration of function `TOSH_MAKE_TEMP_CTL_OUTPUT' In file included from /opt/moteiv/tinyos- 1.x /tos/sensorboards/micasb/Photo.nc:53 , from Surge.nc:42 http://surge.nc:42/: In component `PhotoTemp': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTemp.nc: At top level: /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTemp.nc:64: `TOS_ADC_PHOTO_P ORT' undeclared here (not in a function)
RE: [Tinyos-help] backoff CSMA
TinyOS 1.x:
configuration CC2420RadioC
{
provides {
...
interface MacControl;
interface MacBackoff;
...
}
}
interface MacBackoff
{
async event int16_t initialBackoff(TOS_MsgPtr m);
async event int16_t congestionBackoff(TOS_MsgPtr m);
}
Connect to MacBackoff, and when you get an initialBackoff(...) or
congestionBackoff(...) event, return 0 or 1. This method wasn't very
friendly for systems that wanted to specify different backoff periods for
different outbound AM types. With extra programming, you can get the event
to set the backoff as you want it for any outbound message.
-David
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael
Schippling
Sent: Friday, April 20, 2007 1:30 PM
To: Jeong Kwanhee
Cc: tinyos
Subject: Re: [Tinyos-help] backoff CSMA
I don't think there is an interface for munging up the backoff behavior.
Search for backoff in the CC2420RadioM.nc file to see if there's
anything you can modify. Also search this list for different MAC layers
that may be more to your liking.
Just shutting off CSMA will probably only help thruput if you have only
one transmitter. If there is more than one mote sending and they don't
play nice, I'd bet that most messages will be garbaged up and useless.
MS
Jeong Kwanhee wrote:
Hello all!!
I want to increase about throughput in micaz's surge application.
So, I'm currently doing to remove backoff and ack.
However, I don't know how to disable backoff. (I found how to disable
ack.)
I think that I have to use CC2420Radio or CC2420Control. Is right? I
can't find and do this.
Give me a hint.
My experiment is using micaz, tinyos 1.x.x.
Regards.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Compilation error in Surge(Urgent)
Hi, I was trying to install surge application in my tmoteinvent. When i gave the command make tmoteinvent it gives me the following compilation error. When i tried to download and compile the surge from the source forge repository also it give me this error. Where can i get a stable verison.If not how can i solve the problem. $ make tmoteinvent mkdir -p build/tmoteinvent compiling Surge to a tmoteinvent binary ncc -o build/tmoteinvent/main.exe -O -I%T/lib/Route -I%T/lib/Queue -I%T/lib/Broa dcast -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=tmoteinvent -fne sc-cfile=build/tmoteinvent/app.c -board=micasb -I/opt/moteiv/tos/sensorboards/in vent -I/opt/moteiv/tos/platform/tmoteinvent -I/opt/moteiv/tos/platform/tmote -I/ opt/moteiv/tos/platform/tmote/util/uartdetect -I/opt/moteiv/tos/platform/msp430/ adc -I/opt/moteiv/tos/platform/msp430/dac -I/opt/moteiv/tos/platform/msp430/dma -I/opt/moteiv/tos/platform/msp430/resource -I/opt/moteiv/tos/platform/msp430/tim er -I/opt/moteiv/tos/platform/msp430 -I/opt/moteiv/tos/lib/util/button -I/opt/mo teiv/tos/lib/util/pool -I/opt/moteiv/tos/lib/util/null -I/opt/moteiv/tos/lib/uti l -I/opt/moteiv/tos/lib/MultiHopLQI -I/opt/moteiv/tos/lib/netsync -I/opt/moteiv /tos/lib/sp -I/opt/moteiv/tos/lib/sp/cc2420 -I/opt/moteiv/tos/lib/timer -I/opt/m oteiv/tos/platform/msp430/timer -I/opt/moteiv/tos/lib/resource -I/opt/moteiv/tos /lib/sched -I/opt/moteiv/tos/lib/Deluge -I/opt/moteiv/tos/lib/Flash/STM25P -I/op t/moteiv/tos/lib/Flash -I/opt/moteiv/tos/lib/Spram -I/opt/moteiv/tos/interfaces -I/opt/moteiv/tos/system -I/opt/moteiv/tos/lib/CC2420Radio -I/opt/moteiv/tinyos- 1.x/tos/lib/CC2420Radio -I/opt/moteiv/tinyos-1.x/tos/lib/Drip -fnesc-scheduler=T inySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask -Wl, --section-start=.text=0x4800,--defsym=_reset_vector__=0x4000 -DLIB_DELUGE -DDELU GE_NUM_IMAGES=6 -mdisable-hwmul -I%T/lib/Deluge -DIDENT_PROGRAM_NAME=\Surge\ - DIDENT_USER_ID=\student\ -DIDENT_HOSTNAME=\wd222te9\ -DIDENT_USER_HASH=0x18a a6353L -DIDENT_UNIX_TIME=0x4629260cL -DIDENT_UID_HASH=0x195027d4L Surge.nchttp://surge.nc/-lm In file included from Surge.nc:42 http://surge.nc:42/: In component `SurgeM': SurgeM.nc : In function `SendData.runTask': SurgeM.nc:89: warning: suggest parentheses around assignment used as truth value In file included from /opt/moteiv/tinyos-1.x /tos/sensorboards/micasb/PhotoTemp.n c:58, from /opt/moteiv/tinyos-1.x /tos/sensorboards/micasb/Photo.nc:53 , from Surge.nc:42 http://surge.nc:42/: In component `PhotoTempM': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc: In function `Photo StdControl.init': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:135: `TOS_ADC_PHOTO _PORT' undeclared (first use in this function) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:135: (Each undeclar ed identifier is reported only once /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:135: for each funct ion it appears in.) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:135: `TOSH_ACTUAL_P HOTO_PORT' undeclared (first use in this function) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc: In function `TempS tdControl.init': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:159: `TOS_ADC_TEMP_ PORT' undeclared (first use in this function) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:159: `TOSH_ACTUAL_T EMP_PORT' undeclared (first use in this function) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc: In function `getSa mple.runTask': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:211: implicit decla ration of function `TOSH_SET_PHOTO_CTL_PIN' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:212: implicit decla ration of function `TOSH_MAKE_PHOTO_CTL_OUTPUT' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:213: implicit decla ration of function `TOSH_CLR_TEMP_CTL_PIN' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:214: implicit decla ration of function `TOSH_MAKE_TEMP_CTL_INPUT' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:251: implicit decla ration of function `TOSH_CLR_PHOTO_CTL_PIN' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:252: implicit decla ration of function `TOSH_MAKE_PHOTO_CTL_INPUT' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:253: implicit decla ration of function `TOSH_SET_TEMP_CTL_PIN' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:254: implicit decla ration of function `TOSH_MAKE_TEMP_CTL_OUTPUT' In file included from /opt/moteiv/tinyos- 1.x /tos/sensorboards/micasb/Photo.nc:53 , from Surge.nc:42 http://surge.nc:42/: In component `PhotoTemp': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTemp.nc: At top level: /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTemp.nc:64: `TOS_ADC_PHOTO_P ORT' undeclared here (not in a function)
[Tinyos-help] Compilation error in Surge(Urgent)
Hi, I was trying to install surge application in my tmoteinvent. When i gave the command make tmoteinvent it gives me the following compilation error. When i tried to download and compile the surge from the source forge repository also it give me this error. Where can i get a stable verison.If not how can i solve the problem. $ make tmoteinvent mkdir -p build/tmoteinvent compiling Surge to a tmoteinvent binary ncc -o build/tmoteinvent/main.exe -O -I%T/lib/Route -I%T/lib/Queue -I%T/lib/Broa dcast -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=tmoteinvent -fne sc-cfile=build/tmoteinvent/app.c -board=micasb -I/opt/moteiv/tos/sensorboards/in vent -I/opt/moteiv/tos/platform/tmoteinvent -I/opt/moteiv/tos/platform/tmote -I/ opt/moteiv/tos/platform/tmote/util/uartdetect -I/opt/moteiv/tos/platform/msp430/ adc -I/opt/moteiv/tos/platform/msp430/dac -I/opt/moteiv/tos/platform/msp430/dma -I/opt/moteiv/tos/platform/msp430/resource -I/opt/moteiv/tos/platform/msp430/tim er -I/opt/moteiv/tos/platform/msp430 -I/opt/moteiv/tos/lib/util/button -I/opt/mo teiv/tos/lib/util/pool -I/opt/moteiv/tos/lib/util/null -I/opt/moteiv/tos/lib/uti l -I/opt/moteiv/tos/lib/MultiHopLQI -I/opt/moteiv/tos/lib/netsync -I/opt/moteiv /tos/lib/sp -I/opt/moteiv/tos/lib/sp/cc2420 -I/opt/moteiv/tos/lib/timer -I/opt/m oteiv/tos/platform/msp430/timer -I/opt/moteiv/tos/lib/resource -I/opt/moteiv/tos /lib/sched -I/opt/moteiv/tos/lib/Deluge -I/opt/moteiv/tos/lib/Flash/STM25P -I/op t/moteiv/tos/lib/Flash -I/opt/moteiv/tos/lib/Spram -I/opt/moteiv/tos/interfaces -I/opt/moteiv/tos/system -I/opt/moteiv/tos/lib/CC2420Radio -I/opt/moteiv/tinyos- 1.x/tos/lib/CC2420Radio -I/opt/moteiv/tinyos-1.x/tos/lib/Drip -fnesc-scheduler=T inySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask -Wl, --section-start=.text=0x4800,--defsym=_reset_vector__=0x4000 -DLIB_DELUGE -DDELU GE_NUM_IMAGES=6 -mdisable-hwmul -I%T/lib/Deluge -DIDENT_PROGRAM_NAME=\Surge\ - DIDENT_USER_ID=\student\ -DIDENT_HOSTNAME=\wd222te9\ -DIDENT_USER_HASH=0x18a a6353L -DIDENT_UNIX_TIME=0x4629260cL -DIDENT_UID_HASH=0x195027d4L Surge.nchttp://surge.nc/-lm In file included from Surge.nc:42 http://surge.nc:42/: In component `SurgeM': SurgeM.nc : In function `SendData.runTask': SurgeM.nc:89: warning: suggest parentheses around assignment used as truth value In file included from /opt/moteiv/tinyos-1.x /tos/sensorboards/micasb/PhotoTemp.n c:58, from /opt/moteiv/tinyos-1.x /tos/sensorboards/micasb/Photo.nc:53 , from Surge.nc:42 http://surge.nc:42/: In component `PhotoTempM': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc: In function `Photo StdControl.init': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:135: `TOS_ADC_PHOTO _PORT' undeclared (first use in this function) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:135: (Each undeclar ed identifier is reported only once /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:135: for each funct ion it appears in.) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:135: `TOSH_ACTUAL_P HOTO_PORT' undeclared (first use in this function) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc: In function `TempS tdControl.init': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:159: `TOS_ADC_TEMP_ PORT' undeclared (first use in this function) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:159: `TOSH_ACTUAL_T EMP_PORT' undeclared (first use in this function) /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc: In function `getSa mple.runTask': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:211: implicit decla ration of function `TOSH_SET_PHOTO_CTL_PIN' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:212: implicit decla ration of function `TOSH_MAKE_PHOTO_CTL_OUTPUT' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:213: implicit decla ration of function `TOSH_CLR_TEMP_CTL_PIN' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:214: implicit decla ration of function `TOSH_MAKE_TEMP_CTL_INPUT' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:251: implicit decla ration of function `TOSH_CLR_PHOTO_CTL_PIN' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:252: implicit decla ration of function `TOSH_MAKE_PHOTO_CTL_INPUT' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:253: implicit decla ration of function `TOSH_SET_TEMP_CTL_PIN' /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:254: implicit decla ration of function `TOSH_MAKE_TEMP_CTL_OUTPUT' In file included from /opt/moteiv/tinyos- 1.x /tos/sensorboards/micasb/Photo.nc:53 , from Surge.nc:42 http://surge.nc:42/: In component `PhotoTemp': /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTemp.nc: At top level: /opt/moteiv/tinyos-1.x/tos/sensorboards/micasb/PhotoTemp.nc:64: `TOS_ADC_PHOTO_P ORT' undeclared here (not in a function)
