Clement Nyirenda | 21 Oct 18:04 2014
Picon

Measuring MICAz Battery Voltage Reading in TinyOS2-1.2 TOSSIM simulations

Dear Colleagues:

I am running TOSSIM simulations of the CTP algorithm by using codes in tinyos-2.1.2/apps/testsTestNetwork. I am using make micaz sim under the TinyOs2.1.2 environment.

I would like to evaluate the energy aspects of CTP. I, therefore, need to get battery voltage level. I tried to use the DemoSensorC component, but it was always giving a huge constant value (48879), which is clearly not correct. This is also confirmed in http://tinyos.stanford.edu/tinyos-wiki/index.php/Sensing, where it has been mentioned that DemoSensorC gives fake voltage readings for MICAz.

When I tried to used the VoltageC component directly, I got the following error:

In component `Atm128AdcC':
/opt/tinyos-2.1.2/tos/chips/atm128/adc/Atm128AdcC.nc:74: no match
make: *** [sim-exe] Error 1

I commented out Atm128AdcP.Atm128Calibrate -> PlatformC; in line 74 of Atm128AdcC.nc, which causes the above error and initialized prescaler in Atm128AdcP.nc, which is in the same folder as Atm128AdcC.nc, to ATM128_ADC_PRESCALE_16 and disabled the platform prescaler option (ATM128_ADC_PRESCALE). I run make micaz sim again. This time, it complied successfully. But when I run python test.py, I am getting 0 for battery voltage. I tried to change the ADC Channel in VoltageP the following options:
    ATM128_ADC_SNGL_ADC0
    ATM128_ADC_SNGL_ADC1
    ATM128_ADC_SNGL_ADC2
    ATM128_ADC_SNGL_ADC3
    ATM128_ADC_SNGL_ADC4
    ATM128_ADC_SNGL_ADC5
    ATM128_ADC_SNGL_ADC6
    ATM128_ADC_SNGL_ADC7
I recompiled and run python test.py but I was still getting zero values for battery voltage.

I, therefore, would like to find out the proper steps that I must take in order to read battery voltage in TOSSIM when simulating MICAz motes under the TinyOs2.1.2 environment.

Your assistance will be greatly appreciated.

Best regards

*****
 Clement

<div><div dir="ltr">
<div>
<div>Dear Colleagues:<br><br>
</div>I am running TOSSIM simulations of the CTP algorithm by using codes in tinyos-2.1.2/apps/testsTestNetwork. I am using make micaz sim under the TinyOs2.1.2 environment.<br><br>
</div>I would like to evaluate the energy aspects of CTP. I, therefore, need to get battery voltage level. I tried to use the DemoSensorC component, but it was always giving a huge constant value (48879), which is clearly not correct. This is also confirmed in <a href="http://tinyos.stanford.edu/tinyos-wiki/index.php/Sensing">http://tinyos.stanford.edu/tinyos-wiki/index.php/Sensing</a>, where it has been mentioned that DemoSensorC gives fake voltage readings for MICAz.<br><br>When I tried to used the VoltageC component directly, I got the following error:<br><br><blockquote class="gmail_quote">In component `Atm128AdcC':<br>/opt/tinyos-2.1.2/tos/chips/atm128/adc/Atm128AdcC.nc:74: no match<br>make: *** [sim-exe] Error 1<br>
</blockquote>
<div><br></div>
<div>I commented out Atm128AdcP.Atm128Calibrate -&gt; PlatformC; in line 74 of Atm128AdcC.nc, which causes the above error and initialized prescaler in Atm128AdcP.nc, which is in the same folder as Atm128AdcC.nc, to ATM128_ADC_PRESCALE_16 and disabled the platform prescaler option (ATM128_ADC_PRESCALE). I run make micaz sim again. This time, it complied successfully. But when I run python test.py, I am getting 0 for battery voltage. I tried to change the ADC Channel in VoltageP the following options:<br>&nbsp;&nbsp;&nbsp; ATM128_ADC_SNGL_ADC0 <br>&nbsp;&nbsp;&nbsp; ATM128_ADC_SNGL_ADC1<br>&nbsp;&nbsp;&nbsp; ATM128_ADC_SNGL_ADC2<br>&nbsp;&nbsp;&nbsp; ATM128_ADC_SNGL_ADC3<br>&nbsp;&nbsp;&nbsp; ATM128_ADC_SNGL_ADC4<br>&nbsp;&nbsp;&nbsp; ATM128_ADC_SNGL_ADC5<br>&nbsp;&nbsp;&nbsp; ATM128_ADC_SNGL_ADC6<br>&nbsp;&nbsp;&nbsp; ATM128_ADC_SNGL_ADC7 <br>
</div>
<div>I recompiled and run python test.py but I was still getting zero values for battery voltage.<br><br>
</div>
<div>I, therefore, would like to find out the proper steps that I must take in order to read battery voltage in TOSSIM when simulating MICAz motes under the TinyOs2.1.2 environment.<br><br>
</div>
<div>Your assistance will be greatly appreciated.<br><br>
</div>
<div>Best regards<br>
</div>
<div>
<br clear="all"><div><div>
<div>
<div>&#65290;&#65290;&#65290;&#65290;&#65290;</div>
<div>&nbsp;Clement <br>
</div>
<a href="http://nthambazale.com/" target="_blank"></a><br>
</div>
</div></div>
</div>
</div></div>
IBRAHIM AHMED NEMER | 20 Oct 11:04 2014
Picon

I need a help

Really I want to modified the FTSP protocol to do another function within the code that is: each node when receive the local time of other nodes and the global time of the root node; this node will make an average value for all these values and update its time to this time!

any help, comments and suggestions 

Many thanks to all.
<div>
<div>Really I want to modified the FTSP protocol to do another function within the code that is: each node when receive the local time of other nodes and the global time of the root
 node; this node will make an average value for all these values and update its time to this time!
<div><br></div>
<div>any help, comments and suggestions&nbsp;</div>
<div><br></div>
<div>Many thanks to all.</div>
</div>
</div>
Rinoa Harasashi | 20 Oct 07:58 2014
Picon

Adding a second SHT11 sensor to TelosB

Hi,

We are trying to add a second SHT11 sensor to our TelosB - we replicated and renamed HplSensirionSht11C.nc, HalSensirionSht11C.nc, SensirionSht11C.nc, and HplSensirionSht11C.nc in platforms/telosa/chips/sht11. We also made sure than the references inside the files were correct.

In addition, we edited hardware.h in both platforms/telosa and platforms/telosb:

// HUMIDITY
TOSH_ASSIGN_PIN(HUM_SDA, 1, 5);
TOSH_ASSIGN_PIN(HUM_SCL, 1, 6);
TOSH_ASSIGN_PIN(HUM_PWR, 1, 7);

// HUMIDITY 2, RINOA ADDED

TOSH_ASSIGN_PIN(HUM_SDA, 2, 0);
TOSH_ASSIGN_PIN(HUM_SCL, 2, 1);
TOSH_ASSIGN_PIN(HUM_PWR, 1, 3);

We used GIO0, GIO1, and GIO2 for the data line, clock line, and power line respectively.

Our test program compiles, but it seems like the second SHT11 isn't working. Did we forget anything?

Thanks! ^_^ 
<div><div dir="ltr">Hi,<div><br></div>
<div>We are trying to add a second SHT11 sensor to our TelosB - we replicated and renamed HplSensirionSht11C.nc, HalSensirionSht11C.nc, SensirionSht11C.nc, and HplSensirionSht11C.nc in platforms/telosa/chips/sht11. We also made sure than the references inside the files were correct.</div>
<div><br></div>
<div>In addition, we edited hardware.h in both platforms/telosa and platforms/telosb:</div>
<div><br></div>
<div>
<div>// HUMIDITY</div>
<div>TOSH_ASSIGN_PIN(HUM_SDA, 1, 5);</div>
<div>TOSH_ASSIGN_PIN(HUM_SCL, 1, 6);</div>
<div>TOSH_ASSIGN_PIN(HUM_PWR, 1, 7);</div>
<div><br></div>
<div>// HUMIDITY 2, RINOA ADDED</div>
<div><br></div>
<div>
<div>TOSH_ASSIGN_PIN(HUM_SDA, 2, 0);</div>
<div>TOSH_ASSIGN_PIN(HUM_SCL, 2, 1);</div>
<div>TOSH_ASSIGN_PIN(HUM_PWR, 1, 3);</div>
<div><br></div>
<div>We used GIO0, GIO1, and GIO2 for the data line, clock line, and power line respectively.</div>
<div><br></div>
<div>Our test program compiles, but it seems like the second SHT11 isn't working. Did we forget anything?</div>
<div><br></div>
<div>Thanks! ^_^&nbsp;</div>
</div>
</div>
</div></div>
Vandana Bhasin | 20 Oct 07:28 2014
Picon

(no subject)


Hi,

When I compile my program with 'make micaz', my exe file is built,, but when I compile with 'make micaz sim'

In interface `HplAt45db':
/opt/tinyos-main-master/tos/chips/at45db/HplAt45db.nc:120: syntax error before `data'
/opt/tinyos-main-master/tos/chips/at45db/HplAt45db.nc:135: syntax error before `data'
/opt/tinyos-main-master/tos/chips/at45db/HplAt45db.nc:179: syntax error before `data'
In file included f rom /opt/tinyos-main-master/tos/chips/at45db/At45dbC.nc:33,
                 from /opt/tinyos-main-master/tos/chips/at45db/WireBlockStorageP.nc:20,
                 from /opt/tinyos-main-master/tos/chips/at45db/BlockStorageC.nc:35,
                 from PartitionToIndexAppC.nc:27:
In component `At45dbP':
/opt/tinyos-main-master/tos/chips/at45db/At45dbP.nc:411: conflicting types for `At45db.read'
/opt/tinyos-main-master/tos/chips/at45db/At45db.nc:166: previous declaration of `At45db.read'
/opt/tinyos-main-master/tos/chips/at45db/At45dbP.nc:424: conflicting types for `At45db.write'
/opt/tinyos-main-master/tos/chips/at45db/At45db.nc:73: previous declaration of `At45db.write'
In file included from /opt/tinyos-main-master/tos/chips/at45db/HplAt45dbC.nc:24,
                 from /opt/tinyos-main-master/tos/chips/at45db/At45dbC.nc:33,
                 from /opt/tinyos-main-master/tos/chips/at45db/WireBlockStorageP.nc:20,
                 from /opt/tinyos-main-master/tos/chips/at45db/BlockStorageC.nc:35,
   &n bsp;             from PartitionToIndexAppC.nc:27:
In component `HplAt45dbByteC':
/opt/tinyos-main-master/tos/chips/at45db/HplAt45dbByteC.nc:235: conflicting types for `HplAt45db.read'
/opt/tinyos-main-master/tos/chips/at45db/HplAt45db.nc:134: previous declaration of `HplAt45db.read'
/opt/tinyos-main-master/tos/chips/at45db/HplAt45dbByteC.nc:240: conflicting types for `HplAt45db.readBuffer'
/opt/tinyos-main-master/tos/chips/at45db/HplAt45db.nc:119: previous declaration of `HplAt45db.readBuffer'
/opt/tinyos-main-master/tos/chips/at45db/HplAt45dbByteC.nc:253: conflicting types for `HplAt45db.write'
/opt/tinyos-main-master/tos/chips/at45db/HplAt45db.nc:178: previous declaration of `HplAt45db.write'
In file included from /opt/tinyo s-main-master/tos/chips/cc1000/CC1000Const.h:51,
                 from /opt/tinyos-main-master/tos/chips/cc1000/CC1000ControlM.nc:41:
/opt/tinyos-main-master/tos/chips/atm128/sim/atm128const.h:19:22: error: pgmspace.h: No such file or directory
In file included from PartitionToIndexAppC.nc:43:
In component `CC1000ControlM':
/opt/tinyos-main-master/tos/chips/cc1000/CC1000ControlM.nc: In function `cc1000SetFrequency':
/opt/tinyos-main-master/tos/chips/cc1000/CC1000ControlM.nc:166: implicit declaration of function `pgm_read_dword'
/opt/tinyos-main-master/tos/chips/cc1000/CC1000ControlM.nc:187: implicit declaration of function `pgm_read_word'
/opt/tinyos-main-master/tos/chips/cc1000/CC1000ControlM.nc: In function `CC1000Control.tunePreset':
/opt/tinyos-main-master/tos/chips/cc1000/CC1000ControlM.nc:302: implicit declaration of function `pgm_read_byte'
make: *** [sim-exe] Error 1

1.I searched for pgmspace.h file using find command, it was present in .zip format. But I am unable to unzip the file using unzip commad. It says it is retreiving but doesn't show a retrieved file in the same directory.
2. Why are errors coming when compiling for sim directory.

Please help...

Regards

Vandana



<div><div>
<div class=""><br></div>
<div class="">Hi,</div>
<div class=""><br class=""></div>
<div class="">When I compile my program with 'make micaz', my exe file is built,, but when I compile with 'make micaz sim' <br class="">
</div>
<div class=""><br class=""></div>
<div class="">In interface `HplAt45db':<br class="">/opt/tinyos-main-master/tos/chips/at45db/HplAt45db.nc:120: syntax error before `data'<br class="">/opt/tinyos-main-master/tos/chips/at45db/HplAt45db.nc:135: syntax error before `data'<br class="">/opt/tinyos-main-master/tos/chips/at45db/HplAt45db.nc:179: syntax error before `data'<br class="">In file included f
 rom /opt/tinyos-main-master/tos/chips/at45db/At45dbC.nc:33,<br class="">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-main-master/tos/chips/at45db/WireBlockStorageP.nc:20,<br class="">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-main-master/tos/chips/at45db/BlockStorageC.nc:35,<br class="">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from PartitionToIndexAppC.nc:27:<br class="">In component `At45dbP':<br class="">/opt/tinyos-main-master/tos/chips/at45db/At45dbP.nc:411: conflicting types for `At45db.read'<br class="">/opt/tinyos-main-master/tos/chips/at45db/At45db.nc:166: previous declaration of `At45db.read'<br class="">/opt/tinyos-main-master/tos/chips/at45db/At45dbP.nc:424: conflicting types for `At45db.write'<br class="">/opt/tinyos-main-master/tos/chips/at45db/At45db.nc:73: previous declaration of `At45db.write'<br class="">In file included from /opt/tinyos-main-master/tos/chips/at45db/HplAt45dbC.nc:24,<br class="">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-main-master/tos/chips/at45db/At45dbC.nc:33,<br class="">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-main-master/tos/chips/at45db/WireBlockStorageP.nc:20,<br class="">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-main-master/tos/chips/at45db/BlockStorageC.nc:35,<br class="">&nbsp;&nbsp;&nbsp;&amp;n
 bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from PartitionToIndexAppC.nc:27:<br class="">In component `HplAt45dbByteC':<br class="">/opt/tinyos-main-master/tos/chips/at45db/HplAt45dbByteC.nc:235: conflicting types for `HplAt45db.read'<br class="">/opt/tinyos-main-master/tos/chips/at45db/HplAt45db.nc:134: previous declaration of `HplAt45db.read'<br class="">/opt/tinyos-main-master/tos/chips/at45db/HplAt45dbByteC.nc:240: conflicting types for `HplAt45db.readBuffer'<br class="">/opt/tinyos-main-master/tos/chips/at45db/HplAt45db.nc:119: previous declaration of `HplAt45db.readBuffer'<br class="">/opt/tinyos-main-master/tos/chips/at45db/HplAt45dbByteC.nc:253: conflicting types for `HplAt45db.write'<br class="">/opt/tinyos-main-master/tos/chips/at45db/HplAt45db.nc:178: previous declaration of `HplAt45db.write'<br class="">In file included from /opt/tinyo
 s-main-master/tos/chips/cc1000/CC1000Const.h:51,<br class="">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 from /opt/tinyos-main-master/tos/chips/cc1000/CC1000ControlM.nc:41:<br class="">/opt/tinyos-main-master/tos/chips/atm128/sim/atm128const.h:19:22: error: pgmspace.h: No such file or directory<br class="">In file included from PartitionToIndexAppC.nc:43:<br class="">In component `CC1000ControlM':<br class="">/opt/tinyos-main-master/tos/chips/cc1000/CC1000ControlM.nc: In function `cc1000SetFrequency':<br class="">/opt/tinyos-main-master/tos/chips/cc1000/CC1000ControlM.nc:166: implicit declaration of function `pgm_read_dword'<br class="">/opt/tinyos-main-master/tos/chips/cc1000/CC1000ControlM.nc:187: implicit declaration of function `pgm_read_word'<br class="">/opt/tinyos-main-master/tos/chips/cc1000/CC1000ControlM.nc: In function
  `CC1000Control.tunePreset':<br class="">/opt/tinyos-main-master/tos/chips/cc1000/CC1000ControlM.nc:302: implicit declaration of function `pgm_read_byte'<br class="">make: *** [sim-exe] Error 1<br class="">
</div>
<div class=""><br></div>
<div class="">1.I searched for pgmspace.h file using find command, it was present in .zip format. But I am unable to unzip the file using unzip commad. It says it is retreiving but doesn't show a retrieved file in the same directory.</div>
<div class="">2. Why are errors coming when compiling for sim directory.</div>
<div class=""><br></div>
<div class="">Please help... <br>
</div>
<div class=""><br></div>
<div class="">Regards</div>
<div class=""><br></div>
<div class="">Vandana<br>
</div>
<div class=""><br></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
</div></div>
Andreas Weigel | 17 Oct 16:39 2014
Picon

Change-suggestion for atm128rfa1 RadioDriverLayer to make it safe to use for atmega64/128/256rfr2

Hi everyone,

Suggestion: Add the following line somewhere to the init code:
RX_SYN &= ~(1 << 6);

Rationale:
I just had some "fun time" with a self-made C-port (not very beautiful, 
but it does its job) of the atm128rfa1 RFA1DriverLayerP (and the 
corresponding rfxlink layers).

Letting four ATmega256rfr2-based nodes send out broadcast packets as 
fast as possible (having the whole stack in place, including backoffs 
etc.), lead to RADIO_ASSERT(!radioIrq) being triggered in the RX_END 
ISR. After some happy debugging and thinking (is my protocolstack 
actually to slow in processing the tasklet code stuff?) I was sure that 
this should not be possible.

I then stumbled across a new and greatly-documented feature of the rfr2 
named RX_OVERRIDE, which is enabled on this chip by default (who does 
such things?). This seems to lead to RX_END interrupts which are 
triggered very soon (< 20 us) after the corresponding RX_START. In rare 
circumstances when RX_START was interrupted again by the RadioAlarm 
interrupt (and correspondingly, the TosRandomCollisionLayer 
RadioAlarm.fired() code was executed), service_radio got deferred long 
enough to allow for the RX_END to occur and the RADIO_ASSERT to happen. 
Deactivating RX_OVERRIDE solved the problem.

I do not know (as I could not try out or know how fast the actual TinyOS 
stack handles the code), if this problem would really affect an 
ATmega256rfr2 running TinyOS (which I did not), but I think it at least 
very possible. Considering this, I suggest to add the code shown above 
to the init function of the driver to make the current radio driver safe 
for all rfr2-type chips (also in case someone "ports" the code to rfr2 
and is -- like me -- unaware of this new feature), so that other people 
are spared the pain I just lived through during the last few days

Regards,
Andreas
Abhishek Trivedi | 17 Oct 04:10 2014
Picon

From: Abhishek Trivedi

Hi

http://nhconstitucion.cl/center.php?general=dwqd3em7mrb4v5

abhishek_2180 <at> hotmail.com

IBRAHIM AHMED NEMER | 13 Oct 05:35 2014
Picon

What this sign mean |= in nesc language ?

 

What does this sign mean |= in nesc language ?

Any comment !

 

BR.

<div>
<div class="WordSection1">
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">What does this sign mean <span>|=</span> in nesc language ?<p></p></p>
<p class="MsoNormal">Any comment !<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">BR.<p></p></p>
</div>
</div>
Wen Wen | 8 Oct 22:24 2014
Picon

Compiling C file (.c, .h) with TinyOS using GMP library

Hi All,

Thank you in advance!

I wrote my own .c and .h file using gmp library, but I need to use functions wrote in my .c file in my TinyOS application. How should I include this .h file, and how can I link gmp library to my TinyOS application? 

I think I should do something to the makefile, however, I am new to NesC, would you please show me an example?

Thanks!

Owen
<div><div dir="ltr">Hi All,<div><br></div>
<div>Thank you in advance!</div>
<div><br></div>
<div>I wrote my own .c and .h file using gmp library, but I need to use functions wrote in my .c file in my TinyOS application. How should I include this .h file, and how can I link gmp library to my TinyOS application?&nbsp;</div>
<div><br></div>
<div>I think I should do something to the makefile, however, I am new to NesC, would you please show me an example?</div>
<div><br></div>
<div>Thanks!</div>
<div><br></div>
<div>Owen</div>
</div></div>
András Bíró | 8 Oct 17:53 2014

Re: rfa1 acknowledgements

Hi Elena,

You're right, there's no hw-ack driver for the rfa1. There's no specific reason behind it, we just didn't really need it when we ported the rf230 driver for rfa1. But it should be quite easy to do this with the help of the existing soft-ack driver. If you want to do this, please share the results with the community (e.g. create a pull request on github).

Best,
Andras Biro

2014-10-06 14:41 GMT+02:00 Elena Chervakova <elena.chervakova <at> imms.de>:
Hi all,

I'm looking at the rfa1-port, is it true, that hardware acknowledgements are
not implemented/cannot be used? Is there a specific reason for that?

Best regards,
Elena Chervakova


--

Dipl.-Ing. Elena Chervakova
Wissenschaftliche Mitarbeiterin
System Design

IMMS Institut für Mikroelektronik- und Mechatronik-Systeme gemeinnützige GmbH
Ehrenbergstrasse 27
D - 98693 Ilmenau

Tel.  : +49.3677.6955.58
Fax   : +49.3677.6955.15
E-Mail: elena.chervakova <at> imms.de
WWW   : http://www.imms.de

Geschäftsführer: Prof. Dr. Ralf Sommer -  Dipl.-Ing. Hans-Joachim Kelm
Aufsichtsratsvorsitzender: Dr. Jörg Prinzhausen
Sitz: Ilmenau - Rechtsform: Gesellschaft mit beschränkter Haftung
Registergericht: Amtsgericht Jena HRB 303807

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich
erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie
diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht
gestattet.

This e-mail contains confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail.
Any unauthorised copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
_______________________________________________
Tinyos-help mailing list
Tinyos-help <at> millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

<div>
<div dir="ltr">
<div>
<div>
<div>Hi Elena,<br><br>
</div>You're right, there's no hw-ack driver for the rfa1. There's no specific reason behind it, we just didn't really need it when we ported the rf230 driver for rfa1. But it should be quite easy to do this with the help of the existing soft-ack driver. If you want to do this, please share the results with the community (e.g. create a pull request on github).<br><br>
</div>Best,<br>
</div>Andras Biro<br>
</div>
<div class="gmail_extra">
<br><div class="gmail_quote">2014-10-06 14:41 GMT+02:00 Elena Chervakova <span dir="ltr">&lt;<a href="mailto:elena.chervakova <at> imms.de" target="_blank">elena.chervakova <at> imms.de</a>&gt;</span>:<br><blockquote class="gmail_quote">Hi all,<br><br>
I'm looking at the rfa1-port, is it true, that hardware acknowledgements are<br>
not implemented/cannot be used? Is there a specific reason for that?<br><br>
Best regards,<br>
Elena Chervakova<br><br><br>
--<br><br>
Dipl.-Ing. Elena Chervakova<br>
Wissenschaftliche Mitarbeiterin<br>
System Design<br><br>
IMMS Institut f&uuml;r Mikroelektronik- und Mechatronik-Systeme gemeinn&uuml;tzige GmbH<br>
Ehrenbergstrasse 27<br>
D - 98693 Ilmenau<br><br>
Tel.&nbsp; : +49.3677.6955.58<br>
Fax&nbsp; &nbsp;: +49.3677.6955.15<br>
E-Mail: <a href="mailto:elena.chervakova <at> imms.de">elena.chervakova <at> imms.de</a><br>
WWW&nbsp; &nbsp;: <a href="http://www.imms.de" target="_blank">http://www.imms.de</a><br><br>
Gesch&auml;ftsf&uuml;hrer: Prof. Dr. Ralf Sommer -&nbsp; Dipl.-Ing. Hans-Joachim Kelm<br>
Aufsichtsratsvorsitzender: Dr. J&ouml;rg Prinzhausen<br>
Sitz: Ilmenau - Rechtsform: Gesellschaft mit beschr&auml;nkter Haftung<br>
Registergericht: Amtsgericht Jena HRB 303807<br><br>
Diese E-Mail enth&auml;lt vertrauliche und/oder rechtlich gesch&uuml;tzte Informationen.<br>
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt&uuml;mlich<br>
erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie<br>
diese Mail.<br>
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht<br>
gestattet.<br><br>
This e-mail contains confidential and/or privileged information.<br>
If you are not the intended recipient (or have received this e-mail in error)<br>
please notify the sender immediately and destroy this e-mail.<br>
Any unauthorised copying, disclosure or distribution of the material in this<br>
e-mail is strictly forbidden.<br>
_______________________________________________<br>
Tinyos-help mailing list<br><a href="mailto:Tinyos-help <at> millennium.berkeley.edu">Tinyos-help <at> millennium.berkeley.edu</a><br><a href="https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help" target="_blank">https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help</a><br>
</blockquote>
</div>
<br>
</div>
</div>
IBRAHIM AHMED NEMER | 8 Oct 15:55 2014
Picon

ATS using Micaz

Hi all,

Is there any code on Average time synchronization in this archive ?

 

Many Thanks,

<div>
<div class="WordSection1">
<p class="MsoNormal">Hi all,<p></p></p>
<p class="MsoNormal">Is there any code on Average time synchronization in this archive ?<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Many Thanks,<p></p></p>
</div>
</div>
Abinaya Inbamani | 4 Oct 08:41 2014
Picon

integration with humidity sensor-reg

hi friends,
i am using iris motes and mda100 sensor board..
 as we have 51 pin connectors in mda100 sensor board i am trying to integrate the  humdity sensor into it..is it possible? 
if so can anyone give some idea regarding this integration  and implementation?


--
- Regards,
  Abinaya.
<div><div dir="ltr">hi friends,<div>i am using iris motes and mda100 sensor board..</div>
<div>&nbsp;as we have 51 pin connectors in mda100 sensor board i am trying to integrate the &nbsp;humdity sensor into it..is it possible?&nbsp;</div>
<div>if so can anyone give some idea regarding this integration &nbsp;and implementation?</div>
<div>
<br clear="all"><div><br></div>-- <br><div dir="ltr">- Regards,<div>&nbsp; Abinaya.</div>
</div>
</div>
</div></div>

Gmane