I remember having this problem. What happened to me was that this
receive interface had multiple effects in components. I don't know
exactaly how to put it, but you've wired multiple components by the
same interface, the same instance of receiver.
I had this problem when I needed to use TOSSIM with multiple
components. What I did was to connect all of the in one module and
choose to initialize the most convenient one for the node. Since two
components were wired to the same instance of the receiver interface
(although they would'n be active at the same time), whenever I
received a message, events were triggered in both components. When I
started programming the motes, I separated the components and the
warning disappeared.
So, try to check out your configurations =)
2007/6/17, Ian Welch <[EMAIL PROTECTED]>:
I'm getting the follow warning
"calls to Recieve.recieve in CC1000ActiveMessageP fan out, but there is no
combine function fnction specified for the return type"
I looked in the NESC programming guide and couldn't figure out how to solve
me problem but did find out that this warning should not be overlooked. How
do I solve this warning, I'm thinking it's something to do with using
AMSenderC and ActiveMessageC?
Thanks ahead of time for the help.
-Ian
module InsoleC {
uses interface Boot;
uses interface Leds;
uses interface Timer<TMilli> as SampleDelay;
uses interface Timer<TMilli> as AckDelay;
uses interface Timer<TMilli> as Time;
uses interface Timer<TMilli> as TimeAck;
uses interface Atm128AdcMultiple as Multiple;
uses interface Atm128AdcSingle as Single;
uses interface Init as ADCInit;
uses interface Packet;
uses interface Receive as Receiver[am_id_t myid];
uses interface AMSend[am_id_t id];
uses interface Packet as DataPacket;
uses interface AMSend as DataSend;
uses interface PacketAcknowledgements as ACK;
uses interface GeneralIO;
uses interface GeneralIO as Battery1;
uses interface GeneralIO as Battery2;
uses interface LogRead;
uses interface LogWrite;
uses interface Suspend;
uses interface PowerControl;
}
implementation {
components MainC;
components LedsC;
components InsoleC;
components Atm128AdcP as MyADC;
components new TimerMilliC() as SampleDelay;
components new TimerMilliC() as AckDelay;
components new TimerMilliC() as Time;
components new TimerMilliC() as TimeAck;
components ActiveMessageC as Radio;
components new AMSenderC(6) as Data;
components HplAtm128GeneralIOC as BattIO;
components new LogStorageC(VOLUME_LOG,TRUE);
components MotePowerApp;
components SuspendApp;
//components new LogStorageC(VOLUME_STORAGE,FALSE) as
SampleStorageC;
InsoleC.Boot -> MainC;
InsoleC.Leds -> LedsC;
InsoleC.SampleDelay -> SampleDelay;
InsoleC.AckDelay -> AckDelay;
InsoleC.Time -> Time;
InsoleC.TimeAck -> TimeAck;
InsoleC.Multiple -> MyADC;
InsoleC.ADCInit -> MyADC; //Atm128AdcSingle was not included,
I dont think this is required
InsoleC.Single -> MyADC;
InsoleC.PowerControl -> MotePowerApp;
InsoleC.Suspend -> SuspendApp;
InsoleC.ACK -> Radio;
InsoleC.Packet -> Radio;
InsoleC.AMSend -> Radio;
InsoleC.Receiver -> Radio.Receive;
InsoleC.DataPacket -> Data; //Used to interface witht he data
packet
InsoleC.DataSend -> Data; //Dat packet
InsoleC.Battery1 ->BattIO.PortC6; //Used to monitor Battery
InsoleC.Battery2 ->BattIO.PortC7; //Used to monitor Batery
InsoleC.LogWrite -> LogStorageC;
InsoleC.LogRead -> LogStorageC;
//InsoleC.SampleWrite -> SampleStorageC;
//InsoleC.SampleRead -> SampleStorageC;
}
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
--
"The truth shall set you free"
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
