Seeeduino Stalker v3 and XBee Wifi S6B

I am having problems communicating with an XBee s6b using AT on a Stalker V3.

My goal is simple; send ATMY and get the IP back with the stalker board. I can do this Via XCTU and an XBee Explorer, ATMY responds as expected returning the expected value of C0A80187 (192.168.1.135). Move to Stalker and the wheels fall off.

From the code below, I get the result:
IP Address: FF7776F6BA5020FF6466472…

Not at all what I expect -and- it is the same regardless if the xbee is on the stalker board or not.

If anyone has the secret-sauce here, I would be very appreciative.

Thanks much,

~David

This is the code:

#include <SoftwareSerial.h>
#define COMMAND_TIMEOUT 2000 // ms

const byte XB_TX = 0; // XBee’s TX (Dout) pin
const byte XB_RX = 1; // XBee’s RX (Din) pin
SoftwareSerial xB(XB_RX, XB_TX);

void setup()
{

Serial.begin(9600);
xB.begin(9600);

Serial.print("IP Address: "); printIP(); Serial.println();
}

void loop()
{

}

void printIP()
{
xB.flush();
xB.print(“ATMY”);
xB.print("\r");
waitForAvailable(7);

while (xB.available() > 0)
{
Serial.print(xB.read(),HEX);
}
}

int waitForAvailable(int qty)
{
int timeout = COMMAND_TIMEOUT;

while ((timeout-- > 0) && (xB.available() < qty))
delay(1);

return timeout;
}

Here is the thing, seeed is using pins 0 and 1 for the bee and uarts; they conflict and your just f’d if you want to debug via serial monitor and run an xbee. The board is “designed” to allow remapping of the tx/rx of the bee, (p5/p6) but there is a hardware design flaw that prevents it. I hate those guys, this board is junk. I wasted a week on this bs; no response from seeed… What a joke.