(1) if you are using the "old" interfaces (ie, SendMsg and
ReceiveMsg), then you should wired to GenericComm, not SPC.
Unfortunately the nesC wiring checks aren't completely functional.
(2) SPSend and SPReceive are preferred. They provide the full SP
functionality (message futures, reliability, time stamping, etc) that
is not provided when you use SendMsg or ReceiveMsg.
SPMessage is an abstract data type interface for sp_message_t. You
should never directly modify or access the members of sp_message_t,
instead you should use the SPSend/SPMessage interfaces.
The nesdoc documentation in /opt/moteiv/doc/nesdoc does describe each
of these interfaces and how they should be used.
-Joe
On 5/22/06, Adam <[EMAIL PROTECTED]> wrote:
I am a moteiv Boomerang beginer, and have two confusions:
(1)
I got the "uncombine" warning when I add a command interaction module using
SPC to Delta in Boomerang:
// receive/process/send control message
Impl.SendCtrlMsg -> SPC.SendMsg[AM_CMDMSG];
Impl.RecvCtrlMsg -> SPC.ReceiveMsg[AM_CMDMSG];
Then in *M.nc, I added
//=================================================================
event result_t SendCtrlMsg.sendDone(TOS_MsgPtr _msg, result_t success) {
return SUCCESS;
}
//=================================================================
event TOS_MsgPtr RecvCtrlMsg.receive(TOS_MsgPtr _msg) {
call Leds.yellowToggle();
return _msg;
}
After comiple, it succeed, but I get this warning message:
"nesc1: warning: calls to ReceiveMsg.receive in SPM fan out, but there is no
comb ine function specified for the return type"
How should I combine this with MultiHop?? Please specify (I am a beginner).
(2) I have a big confusion on the relationship the following interfaces in
the context of SPC:
Send // do I must use getBuffer before call?
SendMsg
RreceiveMsg
SPSend
SPReceive
In what situation, which interface is preferred? In MultiHopDataM, they use:
interface SPSend;
interface SPSendNext;
interface SPMessage;
interface ReceiveMsg;
Why not use SendMsg instead of SPSend? Or Why not use SPReceive instead of
SPReceive?
Please help. Thanks in advance.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cory Sharp
Sent: Thursday, May 18, 2006 2:41 PM
To: jose m
Cc: [email protected]
Subject: Re: [Tinyos-help] warning: uncombined call
It means you have _more than one_ component wiring to an event that is
expecting _at most one_ component wiring to it. "Expecting at most one"
means the event returns some value that is "uncombined", so the signaller
receives the return value from only one of the wired components.
Cory
On 5/18/06, jose m <[EMAIL PROTECTED]> wrote:
> Hello all,
>
> I receive this warning after compilation. ¿what this means?
>
> calls to Pool.allocate in CPSReceiveM are uncombined
>
> thanks in advance,
>
> José
>
>
>
>
>
> ___________________________________________________________
> 1GB gratis, Antivirus y Antispam
> Correo Yahoo!, el mejor correo web del mundo
> http://correo.yahoo.com.ar
>
> _______________________________________________
> Tinyos-help mailing list
> [email protected]
> https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-h
> elp
>
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
