you tinyos version may not support micaz, please try for telosb. If same
problem then .......

On Tue, Mar 9, 2010 at 2:45 PM, <[email protected]
> wrote:

> Send Tinyos-help mailing list submissions to
>        [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> or, via email, send a message with subject or body 'help' to
>        [email protected]
>
> You can reach the person managing the list at
>        [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Tinyos-help digest..."
>
>
> Today's Topics:
>
>   1. Re: Sensor is always on... (Michael Schippling)
>   2. Problem with log function (Kartik Siddhabathula)
>   3. Re: Inserting delay in TOSSIM (Mojtaba Raznahan)
>   4. Problem with Microphone mts300 (iris platform)
>      (Alessandro Pinzuti)
>   5. Re: Problem Compiling For TOSSIM (Ziadyassin)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 08 Mar 2010 18:13:10 -0700
> From: Michael Schippling <[email protected]>
> Subject: Re: [Tinyos-help] Sensor is always on...
> To: Daniel Garcia Aubert <[email protected]>
> Cc: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> There is probably something about the sensor itself in
> your config file. Likely something like:
>       Main.StdControl -> mySensor;
> whatever it's name might be. As well as something that
> connects the Read to the actual "mySensor". You should
> be able to use that name like mySensor.stop().
>
> MS
>
>
> Daniel Garcia Aubert wrote:
> > Hi Michael,
> >
> > First, thanks for your help.
> >
> > How I can call Sensor.stop()?
> >
> > I use the sensor through interface Read. Wich looks:
> >
> > interface Read<val_t> {
> >   /**
> >    * Initiates a read of the value.
> >    *
> >    * @return SUCCESS if a readDone() event will eventually come back.
> >    */
> >   command error_t read();
> >
> >   /**
> >    * Signals the completion of the read().
> >    *
> >    * @param result SUCCESS if the read() was successful
> >    * @param val the value that has been read
> >    */
> >   event void readDone( error_t result, val_t val );
> > }
> >
> > I read tutorials and I don?t see something how Sensor.stop(); or
> > Sensor.star(); Because if  I use interfaceStdControl for Sensor I think
> > that I can't read sensor...
> >
> > Any idea? or I don't need turn off sensor for low power sensing.
> >
> >
> > 2010/3/8 Michael Schippling <[email protected] <mailto:[email protected]
> >>
> >
> >     Generally the Sensor.stop() command will un-power the device.
> >     You then need to call Sensor.start() before read().
> >     MS
> >
> >
> >     Daniel Garcia Aubert wrote:
> >
> >         Hi all!
> >
> >         If I get data of sensor with interface Read... the sensorboard
> >         is always on? In simulations Avrora specifies:
> >
> >         =======================================
> >         Node lifetime: 26542080000 cycles,  3600.0 seconds
> >
> >         SensorBoard: 7.56 Joule
> >           on:  : 7.56 Joule, 26542080000 cycles
> >         =======================================
> >
> >         I use T2.1, micaZ and sensor MTS310CB
> >
> >         How I can handle the sensorboard?
> >
> >         Thanks in advance!
> >
> >         --
> >         Daniel Garc?a Aubert
> >         Universidad Carlos III de Madrid.
> >
> >
> >
> ------------------------------------------------------------------------
> >
> >         _______________________________________________
> >         Tinyos-help mailing list
> >         [email protected]
> >         <mailto:[email protected]>
> >
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
> >
> >
> >
> >
> > --
> > Daniel Garc?a Aubert
> > Universidad Carlos III de Madrid.
> >
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 8 Mar 2010 19:43:58 -0800 (PST)
> From: Kartik Siddhabathula <[email protected]>
> Subject: [Tinyos-help] Problem with log function
> To: TinyoS help <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi All,
>
> I am having problem with my log function as sometimes my log read gives
> inconsistent values. Also, I am having some issues with the code which am
> sending as an attachment, like my send is executed only once whereas it
> should execute 10 times. Also whenever log contains the correct values it
> has the same value for the whole array, whereas the mote receives several
> values.
>
> Please help me find the error,
> Kartik
>
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20100308/3216b2e4/attachment-0001.htm
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: BroadcastC.rtf
> Type: application/msword
> Size: 11216 bytes
> Desc: not available
> Url :
> https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20100308/3216b2e4/attachment-0001.wiz
>
> ------------------------------
>
> Message: 3
> Date: Tue, 9 Mar 2010 08:51:52 +0330
> From: "Mojtaba Raznahan" <[email protected]>
> Subject: Re: [Tinyos-help] Inserting delay in TOSSIM
> To: <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain;       charset="us-ascii"
>
> Any idea ?
>
> -----Original Message-----
> From: Mojtaba Raznahan [mailto:[email protected]]
> Sent: Friday, March 05, 2010 6:46 PM
> To: [email protected]
> Subject: Inserting delay in TOSSIM
>
> Hi all,
> How can i insert a delay while runnig the simulation?
>
> Regards,
> Mojtaba
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 9 Mar 2010 08:11:58 +0100
> From: Alessandro Pinzuti <[email protected]>
> Subject: [Tinyos-help] Problem with Microphone mts300 (iris platform)
> To: tinyos-help <[email protected]>
> Message-ID:
>        <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> When I call the command readToneDetector() the output is always the
> same, how if the microphone detects always a sound....
>
> the code that I used is the following:
>
> ? ? ? event void Boot.booted(){
> ? ? ? ? ? ? ? call Microphone.enable();
> ? ? ? }
>
> ? ? ? void report_tone(){
> ? ? ? ? ? if(call Microphone.enable()==SUCCESS) call Leds.led2Toggle();
> ? ? ? ? ? ? ? if(call Microphone.readToneDetector() == 0) call
> Leds.led1Toggle();
> ? ? ? }
>
> ? ? ? async event error_t Microphone.toneDetected(){
> ? ? ? ? ? ? ? call Microphone.disable(); ? ? ?// I insert this line
> because I have read in a post that the .toneDetected() dosen't disable
> the interrupt
> ? ? ? ? ? ? ? return SUCCESS;
> ? ? ? }
>
> Can someone help me? Thanks in advance!
>
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 9 Mar 2010 01:44:39 -0800 (PST)
> From: Ziadyassin <[email protected]>
> Subject: Re: [Tinyos-help] Problem Compiling For TOSSIM
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
>
>
> Dear all,
> I installed TinyOS correctly, but while compiling TOSSIM I encountered the
> following error message :
> " $ make micaz pc
> mkdir -p build/micaz
>    compiling BlinkAppC to a micaz binary
> ncc -o build/micaz/main.exe  -Os -Wall -Wshadow -Wnesc-all -target=micaz
> -fnesc-
> cfile=build/micaz/app.c -board=micasb -DDEFINED_TOS_AM_GROUP=0x22 --param
> max-in
> line-insns-single=100000 -DIDENT_APPNAME=\"BlinkAppC\"
> -DIDENT_USERNAME=\"John\"
>  -DIDENT_HOSTNAME=\"vatchi\" -DIDENT_USERHASH=0x0e93fc00L
> -DIDENT_TIMESTAMP=0x4b
> 961d12L -DIDENT_UIDHASH=0x26d6e2c0L -fnesc-dump=wiring
> -fnesc-dump='interfaces(!
> abstract())' -fnesc-dump='referenced(interfacedefs, components)'
> -fnesc-dumpfile
> =build/micaz/wiring-check.xml BlinkAppC.nc -lm
> In file included from BlinkAppC.nc:39:
> In component `BlinkC':
> BlinkC.nc:39: interface Thread not found
> In file included from BlinkAppC.nc:39:
> BlinkC.nc: In function `Boot.booted':
> BlinkC.nc:50: interface has no command or event named `start'
> BlinkC.nc:51: interface has no command or event named `start'
> BlinkC.nc:52: interface has no command or event named `start'
> BlinkC.nc: At top level:
> BlinkC.nc:55: `run' is not in interface `NullThread'
> BlinkC.nc:59: `run' is not in interface `TinyThread0'
> BlinkC.nc: In function `TinyThread0.run':
> BlinkC.nc:62: interface has no command or event named `sleep'
> BlinkC.nc: At top level:
> BlinkC.nc:65: `run' is not in interface `TinyThread1'
> BlinkC.nc: In function `TinyThread1.run':
> BlinkC.nc:68: interface has no command or event named `sleep'
> BlinkC.nc: At top level:
> $ gcc -v
> BlinkC.nc: In function `TinyThread2.run':
> BlinkC.nc:74: interface has no command or event named `sleep'
> In component `BlinkAppC':
> BlinkAppC.nc: At top level:
> BlinkAppC.nc:40: component ThreadC not found
> BlinkAppC.nc:40: component `ThreadC' is not generic
> BlinkAppC.nc:41: component `ThreadC' is not generic
> BlinkAppC.nc:42: component `ThreadC' is not generic
> BlinkAppC.nc:43: component `ThreadC' is not generic
> BlinkAppC.nc:46: no match
> BlinkAppC.nc:47: no match
> BlinkAppC.nc:48: no match
> BlinkAppC.nc:49: no match
> make: *** [exe0] Error 1 "
>
> Please if anyone can help me solve this problem I will be very
> thankful..It's urgent.
> Best Regards.
> --
> View this message in context:
> http://old.nabble.com/Problem-Compiling-For-TOSSIM-tp22814097p27833429.html
> Sent from the TinyOS - Help mailing list archive at Nabble.com.
>
>
>
> ------------------------------
>
> _______________________________________________
> Tinyos-help mailing list
> [email protected]
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
> End of Tinyos-help Digest, Vol 83, Issue 27
> *******************************************
>
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to