[Tinyos-help] Reduce tmote radio range
Hello everyone, I want to reduce the range of tmote so that i can get a multi hop topology. There are posts that say to change the CC2420Radio file parameters. Which parameters should i change in which file in that folder ??Thanks,Bhushan Be a chatter box. Enjoy free PC-to-PC calls with Yahoo! Messenger with Voice.___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Reduce tmote radio range
Youmustreduce the transmission power. With "SetRFPower" (C:\cygwin\opt\moteiv\tos\lib\CC2420Radio) command you can adjust the transmission power from your aplication. If you do not use this command, the default power transmision is set to 0x1F (31 - 0 dBm - max power) in "CC2420Const.h" file (in the same folder). Best Regards, Diego - Original Message - From: bhushan bhatt To: tinyos Sent: Friday, May 19, 2006 8:29 AM Subject: [Tinyos-help] Reduce tmote radio range Hello everyone, I want to reduce the range of tmote so that i can get a multi hop topology. There are posts that say to change the CC2420Radio file parameters. Which parameters should i change in which file in that folder ??Thanks,Bhushan Be a chatter box. Enjoy free PC-to-PC calls with Yahoo! Messenger with Voice. ___Tinyos-help mailing listTinyos-help@Millennium.Berkeley.EDUhttps://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] AF_UNIX
Hi , In socketswe say that the domain types are like AF_INET and AF_UNIX, the first is used for the Internet and the second one for the UNIX IPC,does it mean that to AF_UNIX domain is used to communicate with the process running in the same machine if yes during what secnarios do we use them bcoz in unix we have pipes and fifos2 communicate between the process which have the same ancestors...in same machinethen message queues ,shared memory etc between different unrelated process in the same machine and sockets between different machine... Thanks and Regards, Pradeep TR The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] motes localization for micaz
Hi all, I am writting to you in order to know if there is already an aplication for nodes localization. I have read part of the literature about nodes localization to know which algorithms there are. I have met with ROCRSSI algorithm. Has anyone implemented it? or which ones have been done? Thanks in advance, Andrés Note: we are using MicaZ _ Horóscopo, tarot, numerología... Escucha lo que te dicen los astros. http://astrocentro.msn.es/ ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Current consumption of a tmote sky
Thanks for the answer. I overlooked the indication on the datasheet, that 10uA is the max value. I would appreciate any suggestion to what I've done wrong with my measurements. Roman Joe Polastre wrote: The flash current consumption is 1uA in power down mode. You can lift the Vcc pin to the flash and measure it yourself :) -Joe On 5/18/06, Roman Lim [EMAIL PROTECTED] wrote: Hello I've just done a few current measurements and compared them to the datasheet from moteiv (http://www.moteiv.com/products/docs/tmote-sky-datasheet.pdf) I can't find out, why my numbers for MCU standby are so far away from the one in the datasheet (that says 5.1 μA avg., 21μA max.): Radio off, MCU in LPM1: 194 μA Radio off, MCU in LPM3: 38 μA Radio off, MCU in LPM4 (all clocks off, I guess this is standby): 35.5 μA I had then a short look at some other datasheets of things on the tmote sky platform. The deep power down current of the external flash memory alone seems to be 10 μA, how can the overall current be lower than that? Regards Roman ___ 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] Help about Tossim+TinyViz
Hi all, i created a simple program for broadcasting messages where every mote broadcast its ADC readings. If i install it on my motes it seems it works (i look at leds' work), but i cannot run TOSSIM. I type make pc and it's ok. Then ./build/pc/main.exe 5 for example and i can look at some messages on my shell. But if i try ./build/pc/main.exe -gui 5 and then i type in the same directory by another shell TinyViz , the TinyViz interface shows these 5 motes but nothing happens. Using paly,pause button and plugins nothing happens. I hope in your help! Cheers, Daniele ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Help with RSSI value
Hi, Sara I am not sure if you have found out the reason why your RSSI value is not correct. Basically CC2420 uses 2s complement for RSSI value. https://mail.millennium.berkeley.edu/pipermail/tinyos-help/2005-June/009922.html However, I have also done my measurement on the signal strength, the maximum RSSI value that I get is 0xFA, i.e. RSSI_VAL = -3, and the signal strength is -7 -45 = -52 dBm. In other word, the maximum signal strength will not go above negative value? I am not sure about this, would you please validate this for me. Thank you. Lin ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] problems with sending messages to a Java application
Hi!
Thanks for the ideas. Yesterday I realized what wasn't working. I had to
recalculate the crc and now it is working. Very strange, but as long as it's
working I don't mind:)
Adina
OK, I'm starting to get the picture I think...
But can you just send me the whole module code,
I'm having trouble figuring out which data is what.
Make sure you are using ints everywhere,
especially when calculating lengths. You may have
some place that thinks of your buffer as chars,
which would double the length value and cause an
overrun someplace that is thinking in ints.
Also, as long as you have the significant data length
at the receiver, you don't really need to fill the
rest of the buffer...or you could do a memset() on
the whole thing first...
MS
adina wrote:
Hi!
The Data_Message_PC is encapsulated in the TOS_Msg.data.
The idea is the following: I receive from a mote via radio the following
payload:
01 00 02 00 03 00 04 00 05 00 06 00
This data I want to stuff in the field actualData from the
Data_Message_PC.
typedef struct Data_Message_PC
{
uint16_t actualData[MAX_DATA];
}Data_Message_PC;
Let's say that the variable MAX_DATA is 8. This means that I have to
create
a Data_Message_PC message, which has 16 bytes of actualData, but I only
received 12 bytes via radio, so I need to stuff the rest of the bytes
with
some values(zero for example). So the Data_Message_PC that I want to
send
should look like this:
01 00 02 00 03 00 04 00 05 00 06 00 00 00 00 00
As I said before, I am trying to use a for loop like this:
for (i=0;ilengthDataReceivedByRadio;i++) data_pc-data[i] =
dataReceived-data[i];
for (i=lengthDataReceivedByRadio;iMAX_DATA;i++) data_pc-data[i] = 0;
If I try to send this, the send command fails.
Any idea is welcome,
Adina
I'm not entirely clear on what you are doing here. Is your
Data_Message_PC
encapsulated in TOS_Msg.data ? If not, and you are using java tools
Packetizer.java (which I think MIG generated files depend on) you'll
probably never see it...
I just sent a reply to a message:
Receiving packets from the base station
with a couple pointers to info about the message structure.
If you are trying to take a full TOS_Msg off the radio and stuff it
into your Data_Message_PC the message size will be too large and you
will not have the right crc. Perhaps you want to just copy the data
portions from one message to another?
Or are you trying to re-create the function of TOSBase, which sends
messages between the pc-UART-radio?
Also see how demo apps like Oscilloscope build their message packets.
MS
adina wrote:
Hello!
I have a problem with sending some a message over the UART. The
message
looks like this:
typedef struct Data_Message_PC
{
uint16_t actualData[MAX_DATA];
uint16_t lengthData;
}Data_Message_PC;
I receive a message from a node, that has the length of the actualData
of a
length less than MAX_DATA and I need
to send it to the UART, so that a Java application can parse the
message
received.
The Java application is using classes generated with MIG, so it always
expects that the actualData received
be of MAX_DATA length.
I have tried to use a for(which is the solution that should have
sense),
but
it doesn't seem to work.
for (i=0;ilengthDataReceived;i++) data_pc-data[i] =
dataReceived-data[i];
for (i=lengthDataReceived;iMAX_DATA;i++) data_pc-data[i] = 0;
If I try to do it like the following, I can see using
net.tinyos.tools.Listen that it has received the message, but this
doesn't
work for
me:((
memcpy(data_pc-data,dataReceived-data,sizeof(uint16_t)*lengthDataReceived);
call SendDataToUART.send(TOS_UART_ADDR,
sizeof(uint8_t)*(lengthDataReceived*2+7), m_msg))
Any help is more than welcome:)
Thanks,
Adina
--
Mobile Internet - E-Mail und Internet immer und überall!
GMX zum Mitnehmen: http://www.gmx.net/de/go/pocketweb
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] battery voltage micaz
Hello,I'm trying to measure the voltage of the batteries of my micaz nodes.When using the VoltageM component, I'm always getting values like Vbat= 3901, 4638, 4892, 5261, 5398, 5351, 5445, 5398 - So, 5,3 Volt for two AA batteries?? Seems very strange... When printing the raw 10-bit ADC value (so without the conversion (in the VoltageM component) Vbat = Vref * 1024/ADC_Count) the ADC_Count = 315, 258, 243, 230, 227, 229, 225,...So in order to get more realistic values like Vbat = 2900mV: the ADC_Count should be around 430... Everything is mapped right, I'm measuring the ADC-channel 30 for micaz...Anyone knows what is wrong? (the same problem has already been posted a month ago, http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-April/016227.html)Greetings,Robin ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Bug in SetUART1Baud()
I'm using MoteWorks 2.0, so I don't know which TinyOS tree it is. rpm -qa shows: $ rpm -qa tinyos-tools-1.2.0-2 avr-binutils-2.15tinyos-3 avr-libc-1.2.3-1 avarice-2.4-1.xbow make-3.80tinyos-1 nesc-1.2.4-1 avr-gcc-3.4.3-1 avr-insight-6.4-1 The existence of this bug is easy to check anyway. File: $TOSROOT/tos/platform/mica2/HPLUART1M.nc At line 83, there's a case for baud rate 115200. The break statement is missing and the fallthrough makes the function return FAIL without setting the rate. BTW, the make system always uses the HPLUARTM files in tos/platform/mica2, even if compiled for micaz. Is this intentional? I can see it's necessary because tos/platform/micaz doesn't contain HPLUART1M.nc, but might cause confusion in the future. Could someone please submit this to be fixed? I've never done it before. Regards, Harri ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] MoteIF stops relaying packets
Dear David and Henri, Thanks for your answer. First about debugging information. If I start a SerialForwarder with the -debug option, I do not get any message when the SerialForwarder stops forwarding. I also tried to use the C SerialForwarder, but I must be doing something wrong because I do not receive any message after I start it. Do I make an error witht the parameters? $ ./sf 9001 COM1 57600 tinynode However, the thread must still be active, because the message counter keeps incrementing even after the client stopped receiving them. By the way, did I mention this happened on a Windows XP machine? Best, Jacques David Gay wrote: On 5/18/06, Jacques Panchard [EMAIL PROTECTED] wrote: I am facing a peculiar problem with MoteIF. The setting is the following. A distant machine is connected to a sensor network via a base station. On the distant machine, I use a SerialForwarder to forward the messages received on the COM port. On my local machine, I am connecting to the distant machine using either a SerialForwarder or the MOTECOM variable, with the following parameter: [EMAIL PROTECTED]:9001 I receive the relayed packets for about an hour, and then no more packets anymore. No error message is displayed. If I restart the local java application, I receive the packets again (the remote SerialForwarder works just fine). Note that it could actually be the thread on the serial forwarder handling your client that hangs (i.e., the fact that restarting the client fixes the problem doesn't mean the problem wasn't in the server). Can you try using the C serial forwarder (in tools/src/sf) on the remote machine and see if you still get the problem? David Gay -- Jacques Panchard – PhD Student Ecole Polytechnique Fédérale de Lausanne Mailing address: EPFL - IC - LCA Bâtiment BC (BC 201) Station 14 CH-1015 Lausanne, Switzerland Tel: +4121 693 56 13 Fax: +4121 693 66 10 http://lcawww.epfl.ch/panchard ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] MoteIF stops relaying packets
On 5/19/06, Jacques Panchard [EMAIL PROTECTED] wrote: Dear David and Henri, Thanks for your answer. First about debugging information. If I start a SerialForwarder with the -debug option, I do not get any message when the SerialForwarder stops forwarding. I also tried to use the C SerialForwarder, but I must be doing something wrong because I do not receive any message after I start it. Do I make an error witht the parameters? $ ./sf 9001 COM1 57600 tinynode sf wants Unix-style serial-port names (so /dev/ttyS0 in this case), even on cygwin. It should've given you a warning to that effect. Beyond that, it doesn't print much, except a short one line message when a client connects or disconnects. David Gay ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Re: problem with serial comm on latest dev branch for tmote tinyos-2.x
Just to add to my observation, when I use the 'C' SerialForwarder and send a command to the mote to read from the flash, I get the the following error message : Note: sync I am not sure what this error message means in the context of the serial communication ? Thanks, Avinash On 5/18/06, Avinash Sridharan [EMAIL PROTECTED] wrote: Hi,I updated my tinyos-2.x dev branch a few days back. I was trying to compile an application which reads data of the flash of a tmote or micaz using the serial forwarder and a JAVA app (that I wrote using mig). This application was running without any problem a while back ( I hadn't updated my code for a while :) ). When I tried compiling my app with the new tree, I got the following warnings related to the serial comm, on doing make 'telosb' although the compilation went through fine. nesc1: warning: calls to Usart.isTxEmpty in Msp430SpiNoDmaP$0 are uncombinednesc1: warning: calls to Usart.isSPI in Msp430SpiNoDmaP$0 are uncombinednesc1: warning: calls to Usart.isUARTrx in Msp430SpiNoDmaP$0 are uncombined nesc1: warning: calls to Usart.isUART in Msp430SpiNoDmaP$0 are uncombinednesc1: warning: calls to Usart.isI2C in Msp430SpiNoDmaP$0 are uncombinednesc1: warning: calls to Usart.isUARTtx in Msp430SpiNoDmaP$0 are uncombined nesc1: warning: calls to Usart.getMode in Msp430SpiNoDmaP$0 are uncombinednesc1: warning: calls to Usart.isTxIntrPending in Msp430SpiNoDmaP$0 are uncombinednesc1: warning: calls to Usart.rx in Msp430SpiNoDmaP$0 are uncombined nesc1: warning: calls to Usart.isRxIntrPending in Msp430SpiNoDmaP$0 are uncombinedI was able to load the binaries on to the tmote and was able to connect to the tmote using the 'C' serial forwarder. But when I send a read flash command from my machine through the serial forwarder to a tmote connected on USB0, I think the tmote is not receiving the command. Although the serial forwarder says it has written the packet correctly. My questions is are the warnings above an indication of any problems with serial communication or should I be looking at some place else. And if yes, could I get pointers to fix them ?Thanks and regards, Avinash-- Phd Dept. of Electrical EngineeringUniversity of Southern California http://www-scf.usc.edu/~asridhar -- Phd Dept. of Electrical EngineeringUniversity of Southern Californiahttp://www-scf.usc.edu/~asridhar ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Re: problem with serial comm on latest dev branch for tmote tinyos-2.x
I don't think this is an 'error' message. This message appears when SF is functioning normally.- VinayakOn 5/19/06, Avinash Sridharan [EMAIL PROTECTED] wrote:Just to add to my observation, when I use the 'C' SerialForwarder and send a command to the mote to read from the flash, I get the the following error message : Note: sync I am not sure what this error message means in the context of the serial communication ? Thanks, Avinash On 5/18/06, Avinash Sridharan [EMAIL PROTECTED] wrote: Hi,I updated my tinyos-2.x dev branch a few days back. I was trying to compile an application which reads data of the flash of a tmote or micaz using the serial forwarder and a JAVA app (that I wrote using mig). This application was running without any problem a while back ( I hadn't updated my code for a while :) ). When I tried compiling my app with the new tree, I got the following warnings related to the serial comm, on doing make 'telosb' although the compilation went through fine. nesc1: warning: calls to Usart.isTxEmpty in Msp430SpiNoDmaP$0 are uncombinednesc1: warning: calls to Usart.isSPI in Msp430SpiNoDmaP$0 are uncombinednesc1: warning: calls to Usart.isUARTrx in Msp430SpiNoDmaP$0 are uncombined nesc1: warning: calls to Usart.isUART in Msp430SpiNoDmaP$0 are uncombinednesc1: warning: calls to Usart.isI2C in Msp430SpiNoDmaP$0 are uncombinednesc1: warning: calls to Usart.isUARTtx in Msp430SpiNoDmaP$0 are uncombined nesc1: warning: calls to Usart.getMode in Msp430SpiNoDmaP$0 are uncombinednesc1: warning: calls to Usart.isTxIntrPending in Msp430SpiNoDmaP$0 are uncombinednesc1: warning: calls to Usart.rx in Msp430SpiNoDmaP$0 are uncombined nesc1: warning: calls to Usart.isRxIntrPending in Msp430SpiNoDmaP$0 are uncombinedI was able to load the binaries on to the tmote and was able to connect to the tmote using the 'C' serial forwarder. But when I send a read flash command from my machine through the serial forwarder to a tmote connected on USB0, I think the tmote is not receiving the command. Although the serial forwarder says it has written the packet correctly. My questions is are the warnings above an indication of any problems with serial communication or should I be looking at some place else. And if yes, could I get pointers to fix them ?Thanks and regards, Avinash-- Phd Dept. of Electrical EngineeringUniversity of Southern California http://www-scf.usc.edu/~asridhar -- Phd Dept. of Electrical EngineeringUniversity of Southern California http://www-scf.usc.edu/~asridhar ___Tinyos-help mailing listTinyos-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] battery voltage micaz
I don't remember the solution to the problem in the previous email you reference, but I think they were reading the wrong ADC or getting wrong values somehow...perhaps Gina Upperman is still online here and can answer. But your values look suspiciously like they have been divided by two. Do you have an accidental bit shift someplace? MS R Gartz wrote: Hello, I'm trying to measure the voltage of the batteries of my micaz nodes. When using the VoltageM component, I'm always getting values like Vbat= 3901, 4638, 4892, 5261, 5398, 5351, 5445, 5398 - So, 5,3 Volt for two AA batteries?? Seems very strange... When printing the raw 10-bit ADC value (so without the conversion (in the VoltageM component) Vbat = Vref * 1024/ADC_Count) the ADC_Count = 315, 258, 243, 230, 227, 229, 225,... So in order to get more realistic values like Vbat = 2900mV: the ADC_Count should be around 430... Everything is mapped right, I'm measuring the ADC-channel 30 for micaz... Anyone knows what is wrong? (the same problem has already been posted a month ago, http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-April/016227.html) Greetings, Robin ___ 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] Bug in SetUART1Baud()
As to the use of mica2 files in micaz, David Gay (I think) once sent me a pointer to doc on the nesc include path...which I of course cannot find now...but that's the way it works. There's some worse ones that go all the way back to mica, and I think even avrmote (but don't quote me on that). Think of confusion as a TOS feature, not a bug... MS Harri Siirtola wrote: I'm using MoteWorks 2.0, so I don't know which TinyOS tree it is. rpm -qa shows: $ rpm -qa tinyos-tools-1.2.0-2 avr-binutils-2.15tinyos-3 avr-libc-1.2.3-1 avarice-2.4-1.xbow make-3.80tinyos-1 nesc-1.2.4-1 avr-gcc-3.4.3-1 avr-insight-6.4-1 The existence of this bug is easy to check anyway. File: $TOSROOT/tos/platform/mica2/HPLUART1M.nc At line 83, there's a case for baud rate 115200. The break statement is missing and the fallthrough makes the function return FAIL without setting the rate. BTW, the make system always uses the HPLUARTM files in tos/platform/mica2, even if compiled for micaz. Is this intentional? I can see it's necessary because tos/platform/micaz doesn't contain HPLUART1M.nc, but might cause confusion in the future. Could someone please submit this to be fixed? I've never done it before. Regards, Harri ___ 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] battery voltage micaz
On 5/19/06, Michael Schippling [EMAIL PROTECTED] wrote: I don't remember the solution to the problem in the previous email you reference, but I think they were reading the wrong ADC or getting wrong values somehow...perhaps Gina Upperman is still online here and can answer. AFAICT, there's no voltage sensor on the micaz (at least there's no sign of it on the schematic on Xbow's web site). The micaz tinyos 1.x Voltage component tries to read the built-in V_BG (bandgap) voltage. Perusing the atmega128 documentation suggests that that voltage is not stable until 40-70us after the ADC is enabled - so the problem may be that it isn't stable. I'm also unclear on how a measurement of V_BG (as setup in TinyOS 1.x's ADCREFM and HPLADCM modules...) relates to battery voltage. But your values look suspiciously like they have been divided by two. Do you have an accidental bit shift someplace? MS R Gartz wrote: Hello, I'm trying to measure the voltage of the batteries of my micaz nodes. When using the VoltageM component, I'm always getting values like Vbat= 3901, 4638, 4892, 5261, 5398, 5351, 5445, 5398 - So, 5,3 Volt for two AA batteries?? Seems very strange... When printing the raw 10-bit ADC value (so without the conversion (in the VoltageM component) Vbat = Vref * 1024/ADC_Count) the ADC_Count = 315, 258, 243, 230, 227, 229, 225,... So in order to get more realistic values like Vbat = 2900mV: the ADC_Count should be around 430... Everything is mapped right, I'm measuring the ADC-channel 30 for micaz... Anyone knows what is wrong? (the same problem has already been posted a month ago, http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-April/016227.html) ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] battery voltage micaz
I assume it's the same trick as the mica2 where the ADC Vref IS the battery, and you get an inverted reading from the internal ref which increases as the battery voltage droops. Is there a micaz schematic on the XBOW site? I keep looking for one at http://www.tinyos.net/scoop/special/hardware and then give up... Also, I just referenced your name in vain on having sent me a link to something that details the nesc include path, which I have lost as usual. Can you resend that (assuming it was you...) thanks MS David Gay wrote: On 5/19/06, Michael Schippling [EMAIL PROTECTED] wrote: I don't remember the solution to the problem in the previous email you reference, but I think they were reading the wrong ADC or getting wrong values somehow...perhaps Gina Upperman is still online here and can answer. AFAICT, there's no voltage sensor on the micaz (at least there's no sign of it on the schematic on Xbow's web site). The micaz tinyos 1.x Voltage component tries to read the built-in V_BG (bandgap) voltage. Perusing the atmega128 documentation suggests that that voltage is not stable until 40-70us after the ADC is enabled - so the problem may be that it isn't stable. I'm also unclear on how a measurement of V_BG (as setup in TinyOS 1.x's ADCREFM and HPLADCM modules...) relates to battery voltage. But your values look suspiciously like they have been divided by two. Do you have an accidental bit shift someplace? MS R Gartz wrote: Hello, I'm trying to measure the voltage of the batteries of my micaz nodes. When using the VoltageM component, I'm always getting values like Vbat= 3901, 4638, 4892, 5261, 5398, 5351, 5445, 5398 - So, 5,3 Volt for two AA batteries?? Seems very strange... When printing the raw 10-bit ADC value (so without the conversion (in the VoltageM component) Vbat = Vref * 1024/ADC_Count) the ADC_Count = 315, 258, 243, 230, 227, 229, 225,... So in order to get more realistic values like Vbat = 2900mV: the ADC_Count should be around 430... Everything is mapped right, I'm measuring the ADC-channel 30 for micaz... Anyone knows what is wrong? (the same problem has already been posted a month ago, http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-April/016227.html) ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] battery voltage micaz
Yes I know they are very suspicious ;) But I don't have any bit shift anywhere in my program(s)... Those are the actual values I'm gettingMichael, in your robocode you're getting the right values for mica2? But you're not using the VoltageM component. So, I decided to try the same thing you did: not using VoltageM. Although I know the Xbow MPR manual describes something about the mapping from ADC7 to the ADC channel 30, and by using VoltageM in micaz. RobotM.BVoltage - ADCC.ADC[ROBOADC_BVOLTAGE]; (I tried both ROBOADC_BVOLTAGE = 7 and ROBOADC_BVOLTAGE=30) but the dataReady-event never fires (although like I said before, I was expecting something like that when not using VoltageM)So, there remain 2 options: -the VoltageM component contains an error (e.g. wrong mapping / reading of the ADC channel)-Measuring Voltage in micaz is not possible? (although the xbow MPR manual claims it should be)greetings and thanks, R.On 5/19/06, Michael Schippling [EMAIL PROTECTED] wrote: I don't remember the solution to the problem in the previous email youreference, but I think they were reading the wrong ADC or gettingwrong values somehow...perhaps Gina Upperman is still online here andcan answer. But your values look suspiciously like they have been divided by two.Do you have an accidental bit shift someplace?MSR Gartz wrote: Hello, I'm trying to measure the voltage of the batteries of my micaz nodes. When using the VoltageM component, I'm always getting values like Vbat= 3901, 4638, 4892, 5261, 5398, 5351, 5445, 5398 - So, 5,3 Volt for two AA batteries?? Seems very strange... When printing the raw 10-bit ADC value (so without the conversion (in the VoltageM component) Vbat = Vref * 1024/ADC_Count) the ADC_Count = 315, 258, 243, 230, 227, 229, 225,... So in order to get more realistic values like Vbat = 2900mV: the ADC_Count should be around 430... Everything is mapped right, I'm measuring the ADC-channel 30 for micaz... Anyone knows what is wrong? (the same problem has already been posted a month ago, http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-April/016227.html) Greetings, Robin ___ 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] battery voltage micaz
I did the excavate thing a while ago and satisfied myself that the mica2 uses the moral equivalent of the Battery as the Vref. Since I couldn't find the micaz schematic I just assume that it's the same. I don't know why the 'Z uses the internal ref and the '2 has an external one. Maybe it's that settling time you mentioned. I was thinking I would find the full 'Z schematic as a separate document. But in the User Manual?...strange...Unfortunately it is not complete, it's missing the controller page. I guess it's the same as the '2...I hope. From a quick look the Vref section seems the same. As for the include path, I meant the implicit path. For instance nothing explicitly references hardware.h (in most apps anyway), but it automagically appears in the (pre-)compiled code, and, various source directories are searched in some (unspecified to me) order when compiling. I mentioned it because there was just a statement made about micaz using mica2/HPLUARTC.nc, which might confuse anyone below the level of prelate in the TOS hierarchy... oh, and my (hopefully vanilla and regular-guy kinda) TOS 1.1.7 install doesn't find a man page for ncc...is it really part of the standard install, and I didn't set my MANPATH right? MS David Gay wrote: On 5/19/06, Michael Schippling [EMAIL PROTECTED] wrote: I assume it's the same trick as the mica2 where the ADC Vref IS the battery, and you get an inverted reading from the internal ref which increases as the battery voltage droops. Well I was thinking that too, but I didn't want to spend lots of time digging through the code to confirm it... (the 1.x code doesn't very explicitly select which reference voltage to use) Is there a micaz schematic on the XBOW site? I keep looking for one at http://www.tinyos.net/scoop/special/hardware and then give up... http://www.xbow.com/Support/Support_pdf_files/MPR-MIB_Series_Users_Manual.pdf (it is on xbow's micaz web page...) Also, I just referenced your name in vain on having sent me a link to something that details the nesc include path, which I have lost as usual. Can you resend that (assuming it was you...) I don't think it was. But man ncc does tell you (at least with the latest toolchain), and compiling with -v will show you all the -I directives... 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] battery voltage micaz
Don't use my Robo code for Bvoltage. I have a whole different hardware scheme and it gets different values. However, you should be able to get the raw ADC readings using ADCC the way I do. The mica2 and 'Z hardware are different as well, which is why they read different channels, so your mileage may vary. If you are a nuts'n'bolts type, look at the micaz schematic, or what there is of it, in the UserGuide that David Gay just referenced, and read the ATMEGA section on using the internal ref. It's pretty turgid, but there may be a clue about the apparent x2 readings you are getting. sorry, I can't be much more help without actually doing work myself... MS R Gartz wrote: Yes I know they are very suspicious ;) But I don't have any bit shift anywhere in my program(s)... Those are the actual values I'm getting Michael, in your robocode you're getting the right values for mica2? But you're not using the VoltageM component. So, I decided to try the same thing you did: not using VoltageM. Although I know the Xbow MPR manual describes something about the mapping from ADC7 to the ADC channel 30, and by using VoltageM in micaz. RobotM.BVoltage - ADCC.ADC[ROBOADC_BVOLTAGE]; (I tried both ROBOADC_BVOLTAGE = 7 and ROBOADC_BVOLTAGE=30) but the dataReady-event never fires (although like I said before, I was expecting something like that when not using VoltageM) So, there remain 2 options: -the VoltageM component contains an error (e.g. wrong mapping / reading of the ADC channel) -Measuring Voltage in micaz is not possible? (although the xbow MPR manual claims it should be) greetings and thanks, R. On 5/19/06, *Michael Schippling* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I don't remember the solution to the problem in the previous email you reference, but I think they were reading the wrong ADC or getting wrong values somehow...perhaps Gina Upperman is still online here and can answer. But your values look suspiciously like they have been divided by two. Do you have an accidental bit shift someplace? MS R Gartz wrote: Hello, I'm trying to measure the voltage of the batteries of my micaz nodes. When using the VoltageM component, I'm always getting values like Vbat= 3901, 4638, 4892, 5261, 5398, 5351, 5445, 5398 - So, 5,3 Volt for two AA batteries?? Seems very strange... When printing the raw 10-bit ADC value (so without the conversion (in the VoltageM component) Vbat = Vref * 1024/ADC_Count) the ADC_Count = 315, 258, 243, 230, 227, 229, 225,... So in order to get more realistic values like Vbat = 2900mV: the ADC_Count should be around 430... Everything is mapped right, I'm measuring the ADC-channel 30 for micaz... Anyone knows what is wrong? (the same problem has already been posted a month ago, http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-April/016227.html) Greetings, Robin ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU mailto:Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help 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] battery voltage micaz
On 5/19/06, Michael Schippling [EMAIL PROTECTED] wrote: As for the include path, I meant the implicit path. For instance nothing explicitly references hardware.h (in most apps anyway), hardware.h is referenced from tos.h, which is magically included when you compile a TinyOS program (but if you pass -v to ncc, you will see somewhere a -fnesc-include=tos option, which is the source of the magic...) but it automagically appears in the (pre-)compiled code, and, various source directories are searched in some (unspecified to me) order when compiling. Well, as I said, make sure ncc gets a -v option, and you will see the full set of include paths searched. oh, and my (hopefully vanilla and regular-guy kinda) TOS 1.1.7 install doesn't find a man page for ncc...is it really part of the standard install, and I didn't set my MANPATH right? I did say the latest toolchain ;-) The TinyOS 2.x toolchain is supposed to work with TinyOS 1.x as of TinyOS 1.1.something recent. But looking at the release date for 1.1.15, I guess my fixes for using the 2.x toolchain in 1.x haven't made it out of CVS and into a minor release :-( David Gay ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] Dattatraya invites you to join Zorpia
Title: Zorpia: Invitation Email Dattatraya has sent you an invitation. Hi tinyos-help, Your friend Dattatraya from India, just invited you to his online photo albums and journals at Zorpia.com. See Dattatraya's friends: salil Victor Preethi So what is Zorpia? It is an online community that allows you to upload unlimited amount of photos, write journals and make friends. We also have a variety of skins in store for you so that you can customize your homepage freely. Join now for free! This message was delivered with the Dattatraya's initiation. If you wish to discontinue receiving invitations from us, please click here: Block future notifications Copyright(c) 2003-2005 Zorpia.com. All Rights Reserved. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
