Spam detection software, running on the system "mail.Millennium.Berkeley.EDU",
has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: All: I am having some issues wiring to CTP. I have previously
tested the tutorial application for CTP with no problems. In my application,
I am trying to create a module that will do all communications so that I
can just swap out modules if I want to work with a different protocol. The
issue I have arises with wiring Send, RoutingControl, and RootControl. I
have currently just taken this code from the EasyCollection application and
pulled it over into a set of commands. The errors that I receive are: [...]
Content analysis details: (3.8 points, 3.3 required)
pts rule name description
---- ---------------------- --------------------------------------------------
3.2 FH_DATE_PAST_20XX The date is grossly in the future.
0.0 WEIRD_PORT URI: Uses non-standard port number for HTTP
0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60%
[score: 0.5000]
1.1 DNS_FROM_OPENWHOIS RBL: Envelope sender listed in bl.open-whois.org.
-0.6 AWL AWL: From: address is in the auto white-list
--- Begin Message ---
All:
I am having some issues wiring to CTP. I have previously tested the
tutorial application for CTP with no problems. In my application, I
am trying to create a module that will do all communications so that I
can just swap out modules if I want to work with a different protocol.
The issue I have arises with wiring Send, RoutingControl, and
RootControl. I have currently just taken this code from the
EasyCollection application and pulled it over into a set of commands.
The errors that I receive are:
NetworkCTP.nc: In function `Network.sendData':
NetworkCTP.nc:24: Send.getPayload not connected
NetworkCTP.nc:28: Send.send not connected
Along with similar errors for RoutingControl and RootControl.
The relevant wiring information is in NetworkCTPC.nc:
{
provides interface Network;
}
implementation{
components Network;
components CollectionC;
components new CollectionSenderC(0xee);
Network = NetworkCTP; //Not entirely sure about this line
NetworkCTP.Send->CollectionSenderC;
}
and within the module, in the sendData commands I call it via:
error = call Send.send(...);
So this is basically wired just like the collection example as far as
I can tell. I may just be having some trouble understanding, learning
to program for TinyOS has not been the easiest thing I've ever done!
Any tips or help would be appreciated!
Newlyn Erratt
--- End Message ---
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
