Out of curiousity, this is related to a problem I had today... are these rewritten packets changed as far as received signal strength goes? As I said in a previous email, the micaz AM.h file declares TOS_Msg->strength as uint8_t and regular AM.h is uint16_t. Now my micaz messages being forwarded over the serial port are almost certainly in mica2 format, I'm not sure what to trust as far as strength goes.
> Date: Wed, 11 Jan 2006 01:37:39 -0800 > From: Jeongyeup Paek <[EMAIL PROTECTED]> > Subject: Re: [Tinyos-help] Micaz UART message length problem > To: Michael Schippling <[EMAIL PROTECTED]> > Cc: TINYOS HELP <tinyos-help@millennium.berkeley.edu> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > David's suggestions (or more like solutions) should work. > This has been an issue since the first release of MicaZ, > and identical issue is appied to telos-series also. > > > Here is a note that I had a year ago: > > > ============================================== > > TOS_Msg Packet format in CC2420 (MicaZ and TelosB) > ---------------------------------------------------- > > A. currently there are two TOSMessage formats/structures: > -MICA2 family (Mica, Mica2, Mica2dot), (tos/type/AM.h) > -CC2420 family (MicaZ / Telos), (tos/platform/micaz/AM.h, > tos/platform/msp430/AM.h) > > B. Legacy/MICA2 Users ----> This is what we are doing! > -Use host side tools (SerialForwarder, Surge gui etc) specifying MICA2 > "mode" (eg. SerialForwarder [EMAIL PROTECTED]:mica2 ) > > -make micaz using maintree tos/platform/micaz. > > In this configuration > All UART traffic to/from host is in MICA2 family TOSMsg format. Host > applications process messages using MICA2 format. The platform/micaz > "FramerM.nc" adapts UART traffic between the message types . > > Host application works directly across all platforms (mixed MICA2, > MICAZ) > > C. TELOS/MICAZ Only Users > -Must rebuild host side tools and use java tools specifying micaz > "mode" > > -make micaz using maintree tos/platform/micaz AFTER removing the local > "FramerM.nc" module. The tos/system "FramerM.nc" module handles > MICAZ TOSMsg > structure UART traffic. > > In this configuration > All UART traffic to/from host is in MICAZ family TOSMsg format. Host > applications process messages using MICAZ/telos format. > > Host application works in single platform (MICAz) network. > > * There are two 'FramerM' files in the tinyos tree. > 1. tinyos-1.x/tos/system/FramerM.nc > o This is the 'normal' file > 2. tinyos-1.x/tos/platform/micaz/FramerM.nc > o This file changes the Micaz/telos TOS_Msg header to > Mica2 header ONLY WHEN sending over the UART. > * If you want to use the latter to work, copy the latter to > "tinyos-1.x/tos/lib/CC2420/" > * If you want to go back to the native formats, the just remove the > file (which will use the former) _______________________________________________ Tinyos-help mailing list Tinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
