Date: Fri, 31 Aug 2012 08:38:41 -0700 (PDT) From: snoop To: xbee-api@googlegroups.com Message-Id: <00af8c5b-3baf-4f7d-a749-441e3d39a87d@googlegroups.com> In-Reply-To: References: <49108e0c-b2ec-4541-92b9-47bdad5a0377@googlegroups.com> Subject: Re: 64 bit MSB first 2 bytes are missing MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_2227_30240338.1346427521791" ------=_Part_2227_30240338.1346427521791 Content-Type: multipart/alternative; boundary="----=_Part_2228_395517.1346427521791" ------=_Part_2228_395517.1346427521791 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I think it is because it is an integer and it is clipping the leading zeros. The same would happen to the LSB void XBeeAddress64::setMsb(uint32_t msb) { _msb = msb; } On Friday, August 31, 2012 11:28:51 AM UTC-4, snoop wrote: > > If anybody has any insight, please let me know. > > On Wednesday, July 18, 2012 11:50:37 AM UTC-4, snoop wrote: >> >> I am missing the first 2 bytes when I convert the serial to hex >> >> String(rx.getRemoteAddress64().getMsb(),HEX) >> >> returns 13a200 >> >> I would like 0013a200 >> >> any thoughts? >> > ------=_Part_2228_395517.1346427521791 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit I think it is because it is an integer and it is clipping the leading zeros. The same would happen to the LSB

void XBeeAddress64::setMsb(uint32_t msb) {
_msb = msb;
}

On Friday, August 31, 2012 11:28:51 AM UTC-4, snoop wrote:
If anybody has any insight, please let me know.

On Wednesday, July 18, 2012 11:50:37 AM UTC-4, snoop wrote:
I am missing the first 2 bytes when I convert the serial to hex 

String(rx.getRemoteAddress64().getMsb(),HEX)

returns 13a200

I would like 0013a200

any thoughts?
------=_Part_2228_395517.1346427521791-- ------=_Part_2227_30240338.1346427521791--