[Tinyos-help] Java Listen tool
Hello, I'm currently following the Lesson 6 for tinyos-1.x online tutorial about displaying data on a PC. I'm using Imperial College's BSN system. When I tried the Java Listen tool using baud rate 57600, the following 'error' message came out: TOS_Msg length is invalid: header_length=5,real_length=36 ... modifying msg to f it Received message:1A 00 00 00 00 00 7E 00 0A 7D 01 00 0A 00 01 00 63 0B 8F 0B 4F 0B 67 0B 6F 0B 7F 0B 7F 0B 83 0B 4F 0B 6B 0B 1A 00 00 00 00 TOS_Msg length is invalid: header_length=5,real_length=36 ... modifying msg to f it Received message:1A 00 00 00 00 00 7E 00 0A 7D 01 00 14 00 01 00 6B 0B 6B 0B 6F 0B 7B 0B 77 0B 7F 0B 7F 0B 7B 0B 7B 0B 7B 0B 1A 00 00 00 00 . . .and so on So next I used explicit telos baud rate as in export [EMAIL PROTECTED] :telos and the msg length invalid error message was gone but the received messages are still similar to the above format. 1A 00 00 00 00 00 7E 00 0A 7D 01 00 9E 75 01 00 73 0B 77 0B 77 0B 7B 0B 7F 0B 77 0B 83 0B 57 0B 7B 0B 7F 0B 1A 00 00 00 00 00 7E 00 0A 7D 01 00 A8 75 01 00 7B 0B 73 0B 7F 0B 87 0B 57 0B 77 0B 7B 0B 7B 0B 83 0B 63 0B 1A 00 00 00 00 00 7E 00 0A 7D 01 00 B2 75 01 00 77 0B 7F 0B 7F 0B 7B 0B 7F 0B 7F 0B 87 0B 4B 0B 6F 0B 7B 0B What I want to know is: What is TOS_Msg length is invalid...? How do I correct it? Why is my data packet format different from the online tutorial? Mine starts with 1A 00 00 00 00 00 ... If I only starts looking at 7E 00 onwards like the online tutorial then why is my source address (in grey) and channel (in brown) keeps changing while the counter (in green) is constant? Or do I look at them wrong? Sorry for the long post but I really need help in this. Been stuck for a week.. Thanks, Ferry ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] sendDone() called before receive
Hi Philip Preciesly im looking for time between send() and receive() Regards Faisal - Original Message From: Philip Levis [EMAIL PROTECTED] To: Faisal Karim [EMAIL PROTECTED] Cc: tinyos-help@Millennium.Berkeley.EDU Sent: Tuesday, April 3, 2007 4:06:47 AM Subject: Re: [Tinyos-help] sendDone() called before receive On Apr 2, 2007, at 12:49 PM, Faisal Karim wrote: Hi Philip Im trying to measure the time that a packet required to be received by the destination. So roughly saying packet propagation time. You need to be more precise. You mean, time between send() and receive ()? Or do you mean time between the first bit being transmitted (after CSMA) and receive()? Or do you mean the time between the first bit being transmitted and the last bit being received (but not including the code time to signal receive())? Or do you mean the propagation time for an individual bit? These times all have different values. What, specifically, are you trying to measure? Phil TV dinner still cooling? Check out Tonight's Picks on Yahoo! TV. http://tv.yahoo.com/___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] Any info on radiation pattern of telosb?
Hi Azhar, You can check Tmote Sky Datasheet (http://www.moteiv.com/products/docs/tmote-sky-datasheet.pdf) and Technical Report for MicaZ motes An Empirical Study of Radio Signal Strength in Sensor Networks Using MICA2 Nodes Jian Ma, Qianbin Chen, Dian Zhang and Lionel M. Ni Regards, Aleksandr. Hi all, How can I find out more info about the radiation patterns of telosb? 'Coz when I placed the motes normally (i.e. with the battery pack touching the ground) versus placing the motes 90 degrees up (i.e. with the long edge of the battery pack touching the ground through the help of blu-tacks), I get somewhat different results, although I've used the same program. Also, I'm wondering if the radiation is affected by the presence of metal casings in the building? Thanks. Regards, Azhar ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-h elp ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problem with uncombined call
Hi to all, I'm new to Agilla and I've got a warning compiling, it says nesc1: warning: calls to ReceiveMsg.receive in AMStandard are uncombined. Anyone could tell me how to solve this problem? I've used GenericComm to create a new instruction that sniff packet in the air, but I've got this warning and can't go on.I don't understand where the problem is, so please help me. Thank you all. Bye Elnorg _ Scarica Messenger 8.1 e chiama gratis in tutto il mondo! http://get.live.com/it-it/messenger/features ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Task is not interrupted by timer event
Hi,
I wrote the following test code for checking different TinyOS 1.x behaviours.
The timer fires every 6 seconds. During the event handle routine I switch the
green led on for 1 second, post the testTask and end with switching on the
yellow led for 1 second. Inside the testTask I switch on the red led for also 1
second.
I tested this code on telosb hardware. The behaviour is correct:
Green light on
Waiting about 1 second
Green light off
Yellow light on
Waiting about 1 second
Yellow light off
Red light on
Waiting about 1 second
Red light off
I.e., the task is scheduled correct after the fired event is processed.
module TestMoteM
{
provides interface StdControl;
uses interface Timer;
uses interface Leds;
}
implementation
{
command result_t StdControl.init()
{
call Leds.init();
return SUCCESS;
}
command result_t StdControl.start()
{
call Timer.start (TIMER_REPEAT, 6000);
return SUCCESS;
}
command result_t StdControl.stop()
{
call Timer.stop();
return SUCCESS;
}
void wait(uint16_t s)
{
uint16_t i, j;
for (j=0; js; j++)
for (i=0; i50; i++)
TOSH_uwait(1);
}
task void testTask()
{
call Leds.redOn();
wait(1);
call Leds.redOff();
}
event result_t Timer.fired()
{
call Leds.greenOn();
wait(1);
call Leds.greenOff();
post testTask();
call Leds.yellowOn();
wait(1);
call Leds.yellowOff();
return SUCCESS;
}
}
In the second test case I changed the testTask as follows:
task void testTask()
{
call Leds.redOn();
wait(10);
call Leds.redOff();
}
I.e. the red light is on for about 10 seconds during the testTask is running.
What I would expect is that during the red light of the testTask is on, the
Timer fires again (because the timer delay is shorter than task processing
length), the new fired event interrupts the testTask, and the green light goes
on. But this doesn't happen. The new fired event is processed after the
testTask is finished.
Is this behaviour correct? By which kind of events the testTask would be
interrupted? Or is anything in principle wrong in my code?
Best regards,
Jürgen
--
Jürgen Reichmann
Siemens AG, CT SE 2
D-81730 Munich, Germany
Phone: +49 (0) 89 636 45455
Email: [EMAIL PROTECTED]
Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Heinrich v. Pierer;
Vorstand: Klaus Kleinfeld, Vorsitzender; Johannes Feldmayer, Joe Kaeser, Rudi
Lamprecht, Eduardo Montes, Jürgen Radomski, Erich R. Reinhardt, Hermann
Requardt, Uriel J. Sharef, Klaus Wucherer Sitz der Gesellschaft: Berlin und
München
Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684
WEEE-Reg.-Nr. DE 23691322
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] telosb and mica2
hi all, i want to know if telosb is compatible with mica 2? thanks - Need Mail bonding? Go to the Yahoo! Mail QA for great tips from Yahoo! Answers users.___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Problem with uncombined call
On Apr 3, 2007, at 1:49 AM, Roberto Gerardi wrote: Hi to all, I'm new to Agilla and I've got a warning compiling, it says nesc1: warning: calls to ReceiveMsg.receive in AMStandard are uncombined. Anyone could tell me how to solve this problem? I've used GenericComm to create a new instruction that sniff packet in the air, but I've got this warning and can't go on.I don't understand where the problem is, so please help me. Thank you all. Bye Elnorg Please check the archives, or take a look at the TinyOS programming manual (which is on tinyos.net). One of the programming hints is Never ignore combine warnings. Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Java Listen tool
Hi Ferry, R u sure ur interpretation of the packet data is correct? I think it should be as follows, by looking at the tutorial: 7E00 is the destination address 0A and 7D are group ID and handler ID respectively Msg length is the next one byte, i.e., 01 in ur case (that may be a reason why u r getting this invalid message length error) Source address is 0100 (red and first one byte from grey, so it is constant) Next two bytes are the sample counter (last one byte from grey, first one byte of green) Channel is 0100 (last one byte of green, first one byte of the next color), so channel ID is not changing, either... Hope this helps Bibudh On 4/3/07, Ferry Cialis [EMAIL PROTECTED] wrote: Hello, I'm currently following the Lesson 6 for tinyos-1.x online tutorial about displaying data on a PC. I'm using Imperial College's BSN system. When I tried the Java Listen tool using baud rate 57600, the following 'error' message came out: TOS_Msg length is invalid: header_length=5,real_length=36 ... modifying msg to f it Received message:1A 00 00 00 00 00 7E 00 0A 7D 01 00 0A 00 01 00 63 0B 8F 0B 4F 0B 67 0B 6F 0B 7F 0B 7F 0B 83 0B 4F 0B 6B 0B 1A 00 00 00 00 TOS_Msg length is invalid: header_length=5,real_length=36 ... modifying msg to f it Received message:1A 00 00 00 00 00 7E 00 0A 7D 01 00 14 00 01 00 6B 0B 6B 0B 6F 0B 7B 0B 77 0B 7F 0B 7F 0B 7B 0B 7B 0B 7B 0B 1A 00 00 00 00 . . .and so on So next I used explicit telos baud rate as in export [EMAIL PROTECTED] :telos and the msg length invalid error message was gone but the received messages are still similar to the above format. 1A 00 00 00 00 00 7E 00 0A 7D 01 00 9E 75 01 00 73 0B 77 0B 77 0B 7B 0B 7F 0B 77 0B 83 0B 57 0B 7B 0B 7F 0B 1A 00 00 00 00 00 7E 00 0A 7D 01 00 A8 75 01 00 7B 0B 73 0B 7F 0B 87 0B 57 0B 77 0B 7B 0B 7B 0B 83 0B 63 0B 1A 00 00 00 00 00 7E 00 0A 7D 01 00 B2 75 01 00 77 0B 7F 0B 7F 0B 7B 0B 7F 0B 7F 0B 87 0B 4B 0B 6F 0B 7B 0B What I want to know is: What is TOS_Msg length is invalid...? How do I correct it? Why is my data packet format different from the online tutorial? Mine starts with 1A 00 00 00 00 00 ... If I only starts looking at 7E 00 onwards like the online tutorial then why is my source address (in grey) and channel (in brown) keeps changing while the counter (in green) is constant? Or do I look at them wrong? Sorry for the long post but I really need help in this. Been stuck for a week.. Thanks, Ferry ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] sendDone() called before receive
On Apr 3, 2007, at 12:51 AM, Faisal Karim wrote: Hi Philip Preciesly im looking for time between send() and receive() So why not just measure that? Why look at sendDone()? Phil ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re to Re: [Tinyos-help] telosb and mica2
hi Vinay, can you explain why if it is possible? because i have these two types and i want to form a network by using them togather. thank you vinay murthy [EMAIL PROTECTED] wrote: Dear Maala, It is not compatible. Vinay. Boushra MAALA [EMAIL PROTECTED] wrote: hi all, i want to know if telosb is compatible with mica 2? thanks - Need Mail bonding? Go to the Yahoo! Mail QA for great tips from Yahoo! Answers users.___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help - Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. - Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit.___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] AT45DB Simulation?
Hi David, Following is your reply to someone on TinyOS-help list around last year. I was wondering if you managed to write a simulation for AT45DB? Best Regards, Wali. 2) Is there a simulator type of support for flash (either separately or in TOSSIM), which would allow me to test my code of reading and writing to flash, without actually using a mote (like telosb or mica2)? No. I guess I should write an at45db simulation (but not this week...). David Gay _ It’s tax season, make sure to follow these few simple tips http://articles.moneycentral.msn.com/Taxes/PreparationTips/PreparationTips.aspx?icid=WLMartagline___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] how to disassemble and riassemble an elf file?
Hi, I'm a student of computer science, i would know how i can disassemble, modify and finally riassemble an elf file. I'm trying with avr-gcc but i have found many errors of 'unknown opcode' during the riassembling. The steps: Compile Blink to a mica2 binary: 1) ncc -o build/mica2/main.exe -O0 -gstabs+ -board=micasb -target=mica2 -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -finline-limit=10 -fnesc-cfile=build/mica2/app.c Blink.nc -lm compiled Blink to build/mica2/main.exe 3850 bytes in ROM 36 bytes in RAM avr-objcopy --output-target=srec build/mica2/main.exe build/mica2/main.srec avr-objdump -d build/mica2/main.exe build/mica2/main.s 2) avr-gcc -Os -mmcu=atmega128 -Wa,-gstabs -I/usr/local/avr/include/ -o main.elf main.S _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Problems with readToneDetector()
Hello everybody,
I'm using TinyOS 2.0 and I'm trying to write an application for two micaz
motes using the microphone. One of the two motes (mote 1) will beep each
1000 ms and the other one (mote 2), once it has detected the tone,
will toggle the green led (if it doesn't detect the tone, it will turn one
the red led). This mote checks every 50 ms if the tone has been detected;
I'm using command startPeriodic including in tos/lib/timer and command
readToneDetector including in tos/sensorboards/mts300/MicSetting.nc.
Here is part of the mote 2 application:
...
event void Timer.fired() {
if (call MicSetting.readToneDetector() == 0) //tone has been detected
{call Leds.led1Toggle();}
else // tone has not been detected
{call Leds.led0On();}
}
async event error_t MicSetting.toneDetected() {
return SUCCESS;
}
...
The problem is that mote 2 is continuously toggling the green led, even if
mote 1 is not beeping but I don't know why.
Can anyone help me?
Thanks in advance
Jorge
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Delays when receiving packets with Boomerang
Hi Joe, We did not extensively test the patch. The two problems you found were things we did not test. Regarding reproducing the problem of missed SFDs, you could set up a scenario similar to what I've explained in earlier e-mails. We can also give you access to our code. However, the code we have developed is mainly for our experiments and hence implements a lot of other things which makes it a bit more complex to use and not at all needed for reproducing the problem. Let me know if you want to try our code anyway. Best Regards, Martin On Fri, 2007-03-16 at 11:04 -0700, Joe Polastre wrote: Hi Martin, I've tried your patch, and it actually degrades performance in high bandwidth utilization cases. Receive is inadvertently called, and often the same packet is received multiple times due to a race condition that is caused by adding your patch. As for the radio missing SFD, I haven't been able to directly observe this. If you have a test case that shows this behavior, I can try it out. -Joe On 2/22/07, Martin Jacobsson [EMAIL PROTECTED] wrote: On Mon, 2007-02-19 at 13:28 +0100, Martin Jacobsson wrote: I don't know how long address decoding takes, but it's 7 bytes from the SFD to the end of the address byte. That's 56 bits, which on a 250kbps radio is 224 us. So if there's any series of atomic blocks that run a bit longer than that (224us + address decode time), then you might run into an issue like this. I believe that all of the MSP430 nesC implementations (TinyOS 1.x, Boomerang, TinyOS 2.0) make all interrupts non-preemptible for programming simplicity, so this could be a very real problem. Boomerang does not use the address decoding feature in the CC2420 and if it did, I use a broadcast destination address. Anyway, my hello packets are very small. They only carry a payload of two bytes. This would mean that SFD is high for 14 bytes (= 448us). Perhaps that is small enough. When I get some time, I will try to see if it is possible to reproduce the error with a large packet size as well. I have now done some more experiments. It is possible to reproduce the error also with a large packet size. Instead of a 2 bytes payload, I used 25 bytes and it still happens. The important factor seems to be the frequency of packets. The closer it is between two consecutive packets, the bigger the chance. Hence, it is more plausible that the software misses the raising flank of SFD and not the lowering flank. Best Regards, Martin Jacobsson ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] how to get tossim virtual location of a mote?
Dear I am a student of University of Catania, I would like to make a program where is possible to change the congestion window of mac protocol in base of the motes's location. Because I saw an your message where you wrote that you have some problem(the same of my). I tell you if you solve this problem. Thanks Salvatore Costanzo ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Attaching sounder component to tmote sky?
Hi, Has anyone here successfully attached a sounder component to a tmote sky mote? What did you do? I would like to be able to use the sounder interface like I once did with the mica2 motes. Thanks. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] node transmission failure
hye guys i am working on a project which reqires programming with motes... i am working with mica and micaz right now i am able to install programs on motes... but when i try to verify hardware's. it just give me an error node transmission failure and sometimes bad packet or long packets. did any body have experience on this. if anybody can help me out that would be highly appreciated. i am using tinyos-1.x and moteview.. and hardwares are serial and parallel cables, mib510,mts300 sensors .. please help me guys with thanks and regards Rakesh Kumar Lakhanpal __ Yahoo! India Answers: Share what you know. Learn something new http://in.answers.yahoo.com/___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Matlab with Tinyos anyone can help ?
HII
Good day
I am having the same problem currently.
Can anyone give me an idea on how to solve this problem?
Thank you very much!!
Hii
I am right now working on connecting Matlab with tinyos. I want to
send some data from matlab to tiny os.
According to the tiny os lesson i did set up environment required
between them.
now when i write commnds like
1)
connect('com1')
Warning: Could not connect: COM1
In c:\tinyos\cygwin\opt\tinyos-
1.x\tools\matlab\comm\connectToSerial.m at line 34
In c:\tinyos\cygwin\opt\tinyos-1.x\tools\matlab\comm\connect.m
2)
net.tinyos.sf.SerialForward.main({'-comm','COM1'})
??? Undefined variable 'net' or
class 'net.tinyos.sf.SerialForward.main'.
I dont know how to solve this problem..
Help me out
Nirav
--
-
Don't get soaked. Take a quick peek at the forecast
with theYahoo! Search weather shortcut.___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Sensing 512 samples using MIC on MICAz
Hi All I am struggling with sensing and transmitting on the MICAz. Once MIC senses 512 samples as one frame at around 8kHz, it stops sensing and transmits 16 packets whose payload contains of 32 samples. When frames are plotted in the base station, the first frame looks good, moving up like being saturated. From the second frame, it goes down to 211 and keeps going on. I set timer as one shot mode to switch from sensing to transceiver, and vice versa. Have anyone bumped into this problem? Thanks in advance, HoMin ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] the high speed sampling application for MICAz
Hi My name is Long in CE deparment at Kansas State University. Our Department recently bought wireless sensor products (MICAz, MIB520CB,MTS310CB) from Xbow company. We want to apply high speed sampling application up to 300Hz. Since Xbow don't have high speed application and they let me to contact with you to see whether you have such application for MICAz. Thanks Long ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] how to get tossim virtual location of a mote?
Do u mean Congestion Window or Contention Window? MAC protocols have Contention Window, as far as I know, Congestion Window is something related to Transport-layer protocols. On 3/29/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Dear I am a student of University of Catania, I would like to make a program where is possible to change the congestion window of mac protocol in base of the motes's location. Because I saw an your message where you wrote that you have some problem(the same of my). I tell you if you solve this problem. Thanks Salvatore Costanzo ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Found few errors -- need help
Hi all, I working on Telosb motes and tiny OS 1.x. I compiled a TestSounder program which is in \cygwin\opt\tinyos-1.x\apps\MicaSBVerify folder. Following are the errors found from this folder tinyos-1.x\tos\sensorboards\micasb\SounderM.nc 1. Parse error 2. Implicit declaration of function TOSH_SET_SOUNDER_CTL_PIN. 3. In function StdControl.start. Kindly help me out. Thanks Vasudha - The fish are biting. Get more visitors on your site using Yahoo! Search Marketing.___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] TinyOS 2.0 I2C Slave implementation on mica2/mica2dot
Hello, I posted this message eariler, but it had html in it, got scrubbed and wasn't very visible. Anyway ... The TinyOS sourceforge page has an I2C slave driver for atMega128-based motes under tinyos-1.x/beta/I2C Is such an implementation available for TinyOS 2? If not, is anyone planning to work on it? thanks, omar ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: RE: [Tinyos-help] telosb and mica2
Also the network communication specification followed by Telosb and Mica is different. Telosb uses Zigbee while mica does not use zigbee. Only difference in frequency is not the necessary reason for them not communicating with each other. Please correct me if I am wrong. - Nikhil Shah ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] telosb and mica2
thank you vinay murthy [EMAIL PROTECTED] wrote: HI Maala, Because Telosb and MIca 2 both has different Micro COntroller and different Radio. Cheers,vinay. Boushra MAALA [EMAIL PROTECTED] wrote: hi Vinay, can you explain why if it is possible? because i have these two types and i want to form a network by using them togather. thank you vinay murthy [EMAIL PROTECTED] wrote: Dear Maala, It is not compatible. Vinay. Boushra MAALA [EMAIL PROTECTED] wrote: hi all, i want to know if telosb is compatible with mica 2? thanks - Need Mail bonding? Go to the Yahoo! Mail QA for great tips from Yahoo! Answers users.___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help - Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. - Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit.___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help - Need Mail bonding? Go to the Yahoo! Mail QA for great tips from Yahoo! Answers users. - It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar.___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] TINY OS PROBLEM
Not sure why this only happens with some of your devices but the output you sent shows that you are trying to use the dapa programmer: uisp -dprog=dapa... Which is not right. Check out how to set it up to use the MIB-600... In my case I set this in the MakeXbowLocal file: DEFAULT_PROGRAM=mib510 MIB510=/dev/ttyS5 And there is some indication that this could work for your mib: DEFAULT_PROGRAM=eprb EPRB=10.1.1.238 ## use your net addr There may be other env variables or make syntax that you can use but I do my best to forget everything that I don't need to know... Also when trying to use the java programs to communicate you need to set your MOTECOM variable correctly. I'm not sure what that means for the MIB-600, however it oughta be in the manual or google-able. What you show is [EMAIL PROTECTED]:19200 which is the wrong device and the wrong baud rate too boot. And a little hint... You don't need to do an image screen capture. When using the bash shell you can simply redirect text output into a file like this: whatever-command file.txt MS Edward Yip wrote: Dear Sir/Madam, I have face some problem with tiny os on developing my sensro netwprk, i hope you can help me to slove the problem, thx. My working env are: PC: Window XP Pro SP1 with Tiny-OS 1.1 installed Program Board: MIB-600 Sensor: Mica MTS-300 1. when i program some of my sensor, it will show error as atteched screen cap, i have try to follow the instruction to slove that problem i found in the internet, (http://www.tinyos.net/faq.html#SEC-54), but it seems that it still cannot work, i have a total 3 sensor, 1 work properly but 2 cannot. please help me.. 2. I try to follow the instruction of the tutorial i found on net (http://www.tinyos.net/tinyos-1.x/doc/tutorial/lesson8.html), when i got % java net.tinyos.tools.BcastInject read_log 2 Sending payload: 65 6 0 0 0 2 0 0 0 0 0 [EMAIL PROTECTED]:19200: resynchronizing Waiting for response to read_log... i cannot receive any data, can you show me how to connect with my MIB-600? Thx! ~ Edward Yip ~ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Sensing 512 samples using MIC on MICAz
I'm afraid I have no hope of an idea of what's wrong without getting a gander at the actual code. Also I don't know what you are sampling that is movng up like being saturated and then shouldn't keep going down... More info? MS Ho Kwon wrote: Hi All I am struggling with sensing and transmitting on the MICAz. Once MIC senses 512 samples as one frame at around 8kHz, it stops sensing and transmits 16 packets whose payload contains of 32 samples. When frames are plotted in the base station, the first frame looks good, moving up like being saturated. From the second frame, it goes down to 211 and keeps going on. I set timer as one shot mode to switch from sensing to transceiver, and vice versa. Have anyone bumped into this problem? Thanks in advance, HoMin ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] the high speed sampling application for MICAz
At 300 Hz you should be able to use the regular Timer interface to fire every 3ms...EXCEPT after T1.1.10 they put in a low limit of 4ms in the TimerC.start() code. My belief is that this is unnecessary because I've been running mica2's with 1ms Timer ticks for years using T1.1.7. So you could just try hacking out the hacked in limit and see if it works for you. MS [EMAIL PROTECTED] wrote: Hi My name is Long in CE deparment at Kansas State University. Our Department recently bought wireless sensor products (MICAz, MIB520CB,MTS310CB) from Xbow company. We want to apply high speed sampling application up to 300Hz. Since Xbow don't have high speed application and they let me to contact with you to see whether you have such application for MICAz. Thanks Long ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: RE: [Tinyos-help] telosb and mica2
On Tue, April 3, 2007 2:37 pm, nikhil said: Also the network communication specification followed by Telosb and Mica is different. Telosb uses Zigbee while mica does not use zigbee. Only difference in frequency is not the necessary reason for them not communicating with each other. Please correct me if I am wrong. - Nikhil Shah I'm not sure if you are referring to the packet type or the encoding, but you are basically correct. If I understand the specifications correctly, the two radios work in different ways. They transmit using different strategies, different radio encodings, and different error correction. Even if they were the same frequency, it would be unlikely that they could talk to each other. The CC2420(Zigbee) chip is also more intelligent -- it does some of the processing itself that the CC1000 requires the CPU to do. The Mica uses a different radio yet from the Mica2 and the MicaZ/Telosb/etc. and is completely incompatible with all the others, even at the same frequency. I'm not sure there is a clear table of these differences out there. There ought to be, there are many types of motes on the market, and there should be a quick reference. Does anyone still update a TinyOS wiki? -- The difference between the right word and the almost right word is really a large matter- it's the difference between a lightning bug and the lightning. -Twain ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Voltage of AVcc pin on Tmote Sky-Pin1
Hi, Thanks Michael. I am using the 1.5V reference, I want to know how much does the reference voltage varies. I am planning to use a voltage regulator if it varies much, because Tmote allows to use external reference. As the sensor output is between 0-10mV I am getting very low resolution so either I have to lower the reference or amplify my signal. Usually sensor outputs are low voltage so what is generally done and how a constant supply is maintained? Any suggestions? Thank you Manu Suryavansh UFL Michael Schippling [EMAIL PROTECTED] wrote: If the telos is like the mica's the AVcc pin is pretty much the battery supply, so 2.9v is reasonable. Is there a spec someplace that says it should be 2.5v? If the above is true it's actually a feature...yes, a ratio-metric sensor is a voltage divider, and the output will change with the supply voltage. But (on the mica's at least) the ADC reference voltage is tied to the battery and droops by the same amount, so they remain (mostly) calibrated to each other. tricky design...do you think it was intentional? MS manu suryavansh wrote: Hi, I measured the voltage of the AVcc pin on tmote sky using a multimeter and it shows to be 2.9 volts. Is it not supposed to be 2.5 volts?- I want to use that pin to give supply to my sensor but if that voltage keeps varying then output will not be correct because the sensor is ratiometric and its output depends on the power supply. Is this the correct way to do this? Any suggestions will be helpful. Thank you Manu Suryavansh University of Florida Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help - We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list.___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: RE: [Tinyos-help] telosb and mica2
Let's compare the two radios, along with ZigBee vs. TinyOS. CC2420: * Hardware supported 802.15.4 compatibility - although it takes some amount of software support to make it 100% compatible. * Not ZigBee without software support. Implementation of the ZigBee protocol is what makes something ZigBee. TinyOS baseline does not implement the ZigBee protocol, but it can. Here's a comparison: ZigBee specs make for high power networks (even though it's marketed as low power), geared for building applications that can support dedicated power supplies for coordinator and router nodes. End nodes can be very low power and made using very inexpensive hardware because they aren't intelligent. ZigBee is only a marketing term for an industrial-driven wireless protocol that is not TinyOS. TinyOS philosophy is geared toward actual low power networks - where the equivalent of ZigBee 'end nodes' are allowed to do processing in terms of routing, which improves the energy consumption of the network as a whole. TinyOS networks can survive on batteries for a number of years. ZigBee routers/coordinators can survive on D-cell lithium batteries for ~2 weeks. ZigBee == indoors only. TinyOS == indoors and outdoors. You can make a network that acts like a ZigBee network in TinyOS, but you could also make a network that is more efficient than a ZigBee network in TinyOS. Depending on the target application, claiming to be ZigBee certified may not be a good thing. Continuing on... * Direct Sequence Spread Spectrum (DSSS) modulation * 2400 - 2482 MHz * Packet radio - sends and receives entire packets of information, does automatic reception, CRC's, acks, AES-128, etc. CC1000: * Can implement the 802.15.4 specified headers through software * 300 - 1000 MHz * FSK modulation * Byte radio - sends and receives bytes. Software is responsible for generating and detecting packet preambles, as well as everything else. -David -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Benjamin Madore Sent: Tuesday, April 03, 2007 12:32 PM To: nikhil Cc: tinyos-help@Millennium.Berkeley.EDU Subject: RE: RE: [Tinyos-help] telosb and mica2 On Tue, April 3, 2007 2:37 pm, nikhil said: Also the network communication specification followed by Telosb and Mica is different. Telosb uses Zigbee while mica does not use zigbee. Only difference in frequency is not the necessary reason for them not communicating with each other. Please correct me if I am wrong. - Nikhil Shah I'm not sure if you are referring to the packet type or the encoding, but you are basically correct. If I understand the specifications correctly, the two radios work in different ways. They transmit using different strategies, different radio encodings, and different error correction. Even if they were the same frequency, it would be unlikely that they could talk to each other. The CC2420(Zigbee) chip is also more intelligent -- it does some of the processing itself that the CC1000 requires the CPU to do. The Mica uses a different radio yet from the Mica2 and the MicaZ/Telosb/etc. and is completely incompatible with all the others, even at the same frequency. I'm not sure there is a clear table of these differences out there. There ought to be, there are many types of motes on the market, and there should be a quick reference. Does anyone still update a TinyOS wiki? -- The difference between the right word and the almost right word is really a large matter- it's the difference between a lightning bug and the lightning. -Twain ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Voltage of AVcc pin on Tmote Sky-Pin1
Unfortunately I don't know anything about the telos devices so I can't be much more help there. If it's a fixed regulated ref and your sensor is a voltage-divider and runs off the un-reg batteries then you'll have difficulties. As to lowering the ref to get better range at 10mv, I have one word: noise. It would be better to amplify the signal with an op-amp (the LM324 has a nice down-to-0-rail swing feature) or perhaps a simple transistor circuit. MS manu suryavansh wrote: Hi, Thanks Michael. I am using the 1.5V reference, I want to know how much does the reference voltage varies. I am planning to use a voltage regulator if it varies much, because Tmote allows to use external reference. As the sensor output is between 0-10mV I am getting very low resolution so either I have to lower the reference or amplify my signal. Usually sensor outputs are low voltage so what is generally done and how a constant supply is maintained? Any suggestions? Thank you Manu Suryavansh UFL */Michael Schippling [EMAIL PROTECTED]/* wrote: If the telos is like the mica's the AVcc pin is pretty much the battery supply, so 2.9v is reasonable. Is there a spec someplace that says it should be 2.5v? If the above is true it's actually a feature...yes, a ratio-metric sensor is a voltage divider, and the output will change with the supply voltage. But (on the mica's at least) the ADC reference voltage is tied to the battery and droops by the same amount, so they remain (mostly) calibrated to each other. tricky design...do you think it was intentional? MS manu suryavansh wrote: Hi, I measured the voltage of the AVcc pin on tmote sky using a multimeter and it shows to be 2.9 volts. Is it not supposed to be 2.5 volts?- I want to use that pin to give supply to my sensor but if that voltage keeps varying then output will not be correct because the sensor is ratiometric and its output depends on the power supply. Is this the correct way to do this? Any suggestions will be helpful. Thank you Manu Suryavansh University of Florida Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help We won't tell. Get more on shows you hate to love http://us.rd.yahoo.com/evt=49980/*http://tv.yahoo.com/collections/265 (and love to hate): Yahoo! TV's Guilty Pleasures list. http://us.rd.yahoo.com/evt=49980/*http://tv.yahoo.com/collections/265 ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] CC2420 packet size
Hi, How can I change the default total packet size for CC2420 in tinyos-1.x? As per the packet structure defined in AM.h for telos motes, the default total size seems to be 40 bytes including 28 bytes for the data payload and excluding the extra fields which are not sent over the radio. thanks, Abhishek -- All you need in life is ignorance and confidence, and then success is sure. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Voltage of AVcc pin on Tmote Sky-Pin1
Voltage reference is a completely different concept than the AVcc. For the precision of measurements it is the voltage reference stability that matters. For information about the stability of the voltage reference and for the information regarding how to measure the voltage reference please consult the msp430f1611 datasheet. Best regards, Rob Robert Szewczyk Moteiv Corporation On 4/3/07, Michael Schippling [EMAIL PROTECTED] wrote: Unfortunately I don't know anything about the telos devices so I can't be much more help there. If it's a fixed regulated ref and your sensor is a voltage-divider and runs off the un-reg batteries then you'll have difficulties. As to lowering the ref to get better range at 10mv, I have one word: noise. It would be better to amplify the signal with an op-amp (the LM324 has a nice down-to-0-rail swing feature) or perhaps a simple transistor circuit. MS manu suryavansh wrote: Hi, Thanks Michael. I am using the 1.5V reference, I want to know how much does the reference voltage varies. I am planning to use a voltage regulator if it varies much, because Tmote allows to use external reference. As the sensor output is between 0-10mV I am getting very low resolution so either I have to lower the reference or amplify my signal. Usually sensor outputs are low voltage so what is generally done and how a constant supply is maintained? Any suggestions? Thank you Manu Suryavansh UFL */Michael Schippling [EMAIL PROTECTED]/* wrote: If the telos is like the mica's the AVcc pin is pretty much the battery supply, so 2.9v is reasonable. Is there a spec someplace that says it should be 2.5v? If the above is true it's actually a feature...yes, a ratio-metric sensor is a voltage divider, and the output will change with the supply voltage. But (on the mica's at least) the ADC reference voltage is tied to the battery and droops by the same amount, so they remain (mostly) calibrated to each other. tricky design...do you think it was intentional? MS manu suryavansh wrote: Hi, I measured the voltage of the AVcc pin on tmote sky using a multimeter and it shows to be 2.9 volts. Is it not supposed to be 2.5 volts?- I want to use that pin to give supply to my sensor but if that voltage keeps varying then output will not be correct because the sensor is ratiometric and its output depends on the power supply. Is this the correct way to do this? Any suggestions will be helpful. Thank you Manu Suryavansh University of Florida Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help We won't tell. Get more on shows you hate to love http://us.rd.yahoo.com/evt=49980/*http://tv.yahoo.com/collections/265 (and love to hate): Yahoo! TV's Guilty Pleasures list. http://us.rd.yahoo.com/evt=49980/*http://tv.yahoo.com/collections/265 ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] CC2420 packet size
You can increase the data portion of the structure by defining TOSH_DATA_LENGTH in your Makefile. For example: CFLAGS += -DTOSH_DATA_LENGTH=64 tony Abhishek Jain wrote: Hi, How can I change the default total packet size for CC2420 in tinyos-1.x? As per the packet structure defined in AM.h for telos motes, the default total size seems to be 40 bytes including 28 bytes for the data payload and excluding the extra fields which are not sent over the radio. thanks, Abhishek ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] TinyOS and the default event
Does the 'default event .' capability work in tinyOS 1.x ?? I built a simple test using the Timer module and commented-out the 'Timer.fired' event in my 'testM.nc' and the compiler complained that I had not implemented the event. The event is properly defaulted in the TimerM.nc module. Thanks !! Please let me know if I am writing to the wrong list Richard ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] TinyOS and the default event
On 4/3/07, Richard Dobbis [EMAIL PROTECTED] wrote: Does the 'default event …' capability work in tinyOS 1.x ?? It's a feature of the nesC language, not of TinyOS x.y. And yes, it does work, but now how you think it does... I built a simple test using the Timer module and commented-out the 'Timer.fired' event in my 'testM.nc' and the compiler complained that I had not implemented the event. The event is properly defaulted in the TimerM.nc module. Thanks !! Providing default handlers for an event is a way for the provider of an interface to allow that interface to not be wirred. However, it does not allow users of that interface to omit implementing the interface. I.e., if your module says uses interface Timer as Foo, then it *must* implement Foo.fired, irrespective of the presence or absence of a default event handler in the provider of the Timer interface. David Gay ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
RE: [Tinyos-help] Any info on radiation pattern of telosb?
Hi Aleksandr, Thanks for the suggestions. But I don't quite understand the two diagrams from the first link (http://www.moteiv.com/products/docs/tmote-sky-datasheet.pdf), particularly, what their headers mean: Figure 12 : Radiated pattern of the Inverted-F antenna with horizontal mounting (from Chipcon AS) Figure 13 : Radiated pattern of the Inverted-F antenna with vertical mounting (from Chipcon AS) I have tried googling for Chipcon AS to search for more info on these 2 diagrams, but until now, I can't seem to get it. What does horizontal mounting and vertical mounting mean? Does it refer to the way the telos was mounted, or does it refer to the omnidirectional radiation pattern, which, from a 3D view, is shown from a horizontal point of view and a vertical point of view respectively? If the former, what would the horizontal and vertical mounting look like (with the battery pack included)? I found another link, http://www.ece.rochester.edu/research/wcng/papers/conference/holland_secon06.pdf which solely tests on the range and radiation pattern of tmote sky. However, I don't quite understand the first three graphs (all three are similar, but with different power levels). What I don't understand is that the graph is one of Packet yield vs. distance and angle at high/medium/low transmit power, but from the graph, I see packet yield and y(ft) vs x(ft). Thus, if either x or y is the difference in angle, what does the -ve value represent? Thanks in advance for your inputs. Regards, Azhar From: Sadkov Aleksander [EMAIL PROTECTED] To: tinyos-help@Millennium.Berkeley.EDU Subject: RE: [Tinyos-help] Any info on radiation pattern of telosb? Date: Tue, 3 Apr 2007 12:11:41 +0400 Hi Azhar, You can check Tmote Sky Datasheet (http://www.moteiv.com/products/docs/tmote-sky-datasheet.pdf) and Technical Report for MicaZ motes An Empirical Study of Radio Signal Strength in Sensor Networks Using MICA2 Nodes Jian Ma, Qianbin Chen, Dian Zhang and Lionel M. Ni Regards, Aleksandr. Hi all, How can I find out more info about the radiation patterns of telosb? 'Coz when I placed the motes normally (i.e. with the battery pack touching the ground) versus placing the motes 90 degrees up (i.e. with the long edge of the battery pack touching the ground through the help of blu-tacks), I get somewhat different results, although I've used the same program. Also, I'm wondering if the radiation is affected by the presence of metal casings in the building? Thanks. Regards, Azhar ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-h elp ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] micaX timer/capture/misc stuff
Just in case anyone is interested I've posted a small lump of code for using various TOS-un-supported ATMEGA128 Timer and Port features: http://www.etantdonnes.com/Motes/AVR128timers.zip Contents: HPLPort.nc -- interface for byte access to I/O port HPLPortCM.nc -- impl of above for Port C, read or write whole port HPLT1pwm.nc -- interface for PWM or freq-gen output using Timer1A,B HPLT1pwmM.nc -- impl of above using PortB5,6 (PWM1A,B) as outputs HPLT3capture.nc -- interface for Timer3 timing capture (or PWM input) HPLT3captureM.nc -- impl of above using using PortE7 (INT3) as input HSMotors.nc -- interface to run Hobby-Servo PWM motors HSMotorsM.nc -- impl of above, with a bunch of confusing control code EncDrive.nc -- example user code for HSMotors to us added encoder For the last three, if you want to run small motors for robots or something, there's more info about an encoder hack that I'm developing at: http://www.etantdonnes.com/ROBOCAR/encoder/ It's all documented at what I consider superior-TOS levels, meaning the files have relevant comments, and are tested at about the average level... MS ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
