To elaborate a bit:

If we assume that you have a heterogenous network of motes all running
SPINE, you can poll the network over the air for their capabilities. If the
network consists of motes with both stock and custom sensors, you can
define new sensor board types within the SPINE framework that use both pre
written and your own custom drivers. What you would do then is to program
each mote with the sensor board type that matches its capabilities and once
the network is running, each mote will b able to publish their capabilities
once polled.

Is this the kind of ad-hoc you're after?

Cheers,
Martin kjeldsen

On Thursday, July 4, 2013, Martin Kjeldsen wrote:

> Hi Aaron,
>
> This can be a difficult task depending on how ad-hoc you want to be, i
> believe. If you want to know the capabilities of a stock-mote and know the
> type of sensor board you're dealing with you could probably use a framework
> like SPINE. But if you're dealing with motes whose making is not known to
> you (maybe with custom sensors hooked up to the ADC) this seems difficult
> if not impossible.
>
> I think your best bet is a functionality-mapping framework like SPINE that
> knows what sensors are present on stock-motes given a certain sensor board
> ( I.e SHIMMER, TelosB, etc).
>
> Really interesting question.
>
> Best regards,
> Martin
>
> tirsdag den 2. juli 2013 skrev Aaron :
>
>> Hello!  My group is interested in developing a framework for the ad hoc
>> re-tasking of sensor networks in response to emergency conditions.
>>
>> I'm wondering if there is any simple or recognized way to determine the
>> sensing capabilities of an arbitrary mote.  Assuming that you could run
>> arbitrary code on the mote in question, is there any precise way to
>> determine what types of sensors are available to a particular mote?  Eg. a
>> light sensor and an accelerometer are present, etc.
>>
>> Thank you,
>> Aaron
>>
>
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to