[Tinyos-help] Sensirion Tmote sensor
Hi, I noticed that the sht11 temp/hum sensor it is affected with self heat produced by the microcontroler. I measured the internal temp of TI msp430 and read 29 Celsius , the temperature read on sht11 is 27-28 Celsius and ambient temperature is 23-24 Celsius. I wonder if the sht11 is glued in some way plus the soldering or it is only attach to the mote by the soldering pads?? I want to unsold and isolate the sensor. Anyone has a work around, or saw the same effect?? -Bill PD: I have 10 tmotes and all have the same issue. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] bug in MSP430TimerM and MSP430TimerP
Hi,
I tried to use the inputdivider function to set the prescaler for the
timer and it didnt work. I check the implementation and I believe I should
be change from
async command void TimerA.setInputDivider( uint16_t inputDivider )
{
TACTL = (TACTL ~(ID_1|ID_3)) | ((inputDivider 8) (ID_1|ID_3));
}
to
async command void TimerA.setInputDivider( uint16_t inputDivider )
{
TACTL = (TACTL ~(ID_1|ID_3)) | ((inputDivider 6) (ID_1|ID_3));
}
the difference is in the shift operation, note 6 is the first bit
corresponding to input divider in Timer control register.
It worked with this change
-Bill
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] problem with UART com and Radio msg
Hi, I have problem when sending RF msg and continously talking to a digital sensor conected to UART0. The problem is that I receive bad crc packets, when transmiting, in a rate of 10%. If I disable de UART interrupts before sending and then enabled once sendDone , no bad crc msg appear. Does anyone knows why this may be happening? Note: the bad crc msg are changed in just 1 or at the most 2 bits!!(it its not segmentation fault, because i log the bytes that reach the SPI register and are ok) -Bill ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] interrupt vector numbers
Hi, why does in mica2 the interrupt vectors numbers are 1 less than in the Atmega128L.pdf datasheet. e.g. interrupt vector for SPI serial transfer complete, listed as 18 in the datasheet, is declared as 17 in iom128.h -Bill ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] many lost packets mica2
Hi, I had a mica2 conected to a digital oximeter through the UART0. The baudrate of the conexion is 4800 baudrate and the sensor sends data at a rate of 1920 bit/s (60 packets per seconds of 4 bytes each one). I merge sensor data into a TOS_Msg packet, and when it is full I send it over the radio. On the other side I have a tipical TOSBase aplication conected to a PC. A lot of packets seems to be lost, but when you dig in you realise that the lost are due to bad CRC code. Digging depper you find that the messaje differs from the original in one random bit (statistically taking, some times you get more than one, but in different bytes). To do this I replace the oximeter data with a known pattern. So my first thought was of segmentation fault. I log the SPI SPDR register into the Flash to then check the corresponding values, and everything seems OK!. My only guess now is that the radio and the UART0 share hardware lines. I dont know if this may be related to the prog_miso/mosi UART0 conection. And if this is true I dont know why this doesnt fail in tha case of UART0 comunication with PC and radio transmision. The only difference I see is the low baudrate of 4800 that may block more time the lines, I dont know?? I am pritty shure it is know sofware problem thanks in advance, any guess would help -Bill ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] many lost packets mica2
hi I had a writing mistake in my previous mail. I pretty sure it is not a software problem. -Bill ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] UART0 SPI CC1000
Hi, I dont understand if the prog_miso/mosi pins are the ones used for CC1000 SPI comunication with the micro in Mica2. I want to know if there is a problem in using UART0 and send/recv radio messages since it seems to share hardware lines. thanks, -Bill ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] problem with getContinuosData()
Hi, i have problem sending messages when using getContinuosData(). Everything looks like if it works, i mean i get the sendDone event with success result, but nothing seems to be going out the radio. I saw someone post the same problem, but got no answer, thanks in advane, -Bill ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
[Tinyos-help] change ADC reference on Mica2
the actual ADC reference on Mica2 is the supply voltage (3.3 V),isnt it?. Is it posibble to change this reference value, without mayor hardware changes. Cuase I wanted to measure voltages in the order of milivolts and I am thinking in a reference voltage like 10 mV. What would be the answer in Tmote platform?? thanks. -Bill ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] __attribute((packed)) on msp430
Hi,
the network types are nx_ or nw_ ?
http://nescc.sourceforge.net/networktypes/network-types.txt
thanks,
-Bill
The msp430 requires 16-bit aligned addresses for 16-bit operations.
In the MSP430 x1xx User's Guide, Section 1.4.5 RISC 16-bit CPU,
Instruction Set, Memory Organization,
Bytes are located at even or odd addresses. Words are only located at
even addresses as shown in Figure 1-3. When using word instructions,
only even addresses may be used. The low byte of a word is always an
even address. The high byte is at the next odd address.
In the MSPGCC Manual in section Byte and word issues
http://mspgcc.sourceforge.net/manual/x214.html:
Word operands must be located at even addresses. ... The processor's
behaviour when a word is accessed at an odd location is poorly
documented. In all current processors the lower bit is just silently
ignored. The effect is, therefore, the same as specifying an address
which is one less.
This is why the packed attribute is very, very bad for the msp430.
Your 32-bit args value is placed at an odd-value address with the
packed attribute. When given that odd address, the msp430 quietly
converts it to the next lower even address, thus overwriting your type
variable.
If your structure must be 5 bytes and byte aligned, use nesC's network
types (nx_uint8_t, nx_uint32_t, etc) and leave out the packed
attribute.
Cory
On 2/17/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi,
I have a problem when using __attribute((packed)) for a struct under
msp430 (telosb).
This is the struct I have
typedef struct{
uint32_t interval;
}start_args_t;
typedef struct{
uint32_t time;
}set_time_args_t;
typedef struct{
uint8_t type;
union{
start_args_t startArgs;
set_time_args_t setTimeArgs;
}args;
}Cmd_t __attribute((packed)) ;
Without the packed attribute the struct has a sizeof 6 and padding in
this way
type 1 byte
0x00 padding byte
args 4 bytes
With the packed attibute the struct has a sizeof 5, but the variable
type and the args starts at the same address. I mean that if I set first
the args and then the type field, I am rewriting the LSB of the args
field.
If I change the struct to this one
typedef struct{
union{
start_args_t startArgs;
set_time_args_t setTimeArgs;
}args;
uint8_t type;
}Cmd_t __attribute((packed)) ;
The packet attribute behaves well. It seems like if the odd field are
at
the end of the struct de packing behaves well.
I wonder if this a compiler related bug or I am missing something.
thanks in advance,
-Bill
___
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] telos acknowledge
Hi, I have a question related to system layer acknowledgement on telos motes. I did a few experiments to understand what happen when one enables the Mac.ackEnable(). The interesting thing I found is that when a mote send a message, with the Mac.ackEnable(), to other mote (direct addressing, without broadcasting), anyone listening with the Mac.ackDisable() would get the message as if it was sent to it. is that correct?, or I am making a misstake. If I am correct what happens with the AMStandard layer that filters the address. -Bill. PD: I used a BaredSendMsg interface, an set the address whitin the message structure. If the snooper mote is set with the Mac.ackEnable() it does not receive the message. ___ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
