Date: Tue, 8 May 2012 10:05:42 -0700 (PDT)
From: snoop <alexander.ros...@gmail.com>
To: xbee-api@googlegroups.com
Message-ID: <3783936.2693.1336496742718.JavaMail.geo-discussion-forums@ynmc31>
Subject: Modem Response is cripling communication
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_2691_5439559.1336496742717"

------=_Part_2691_5439559.1336496742717
Content-Type: multipart/alternative; 
	boundary="----=_Part_2692_20398013.1336496742717"

------=_Part_2692_20398013.1336496742717
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

When I run the AT response in the example folder, it works great when the 
xbee has constant power.  But when I unplug the battery and run the arduino 
from a cold start.  It returns a modem status reponse of 8A(associated) and 
criples all further communication.  It swaps high serial for the low 
and it never issues the assoc command. Any suggestions?
------=_Part_2692_20398013.1336496742717
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

When I run the AT response in the example folder, it works great when the xbee has constant power.&nbsp; But when I unplug the battery and run the arduino from a cold start.&nbsp; It returns a modem status reponse of 8A(associated) and criples all further communication.&nbsp; It swaps&nbsp;high serial for the low and&nbsp;it&nbsp;never issues the assoc command. Any suggestions?
------=_Part_2692_20398013.1336496742717--

------=_Part_2691_5439559.1336496742717--