Missing Something? BlueSMIRF Ignores Stop Bits?

I have a pic that communicates at 9600,8,N,2. Works fine with Hyperterminal and a serial cable with a com port configuered at 9600,8,N,2.

After receiving the BlueSMIRF and placing it on my breadboard in place of the serial cable, I was able to connect to it in Hyperterminal at 9600,8,N,1. I entered command mode by sending +++.

Then according to the AT command sheet, I should enter

ATSW20,39,0,1,1 to change it to 9600,8,N,2 and store it that way so at each power up it is set to talk to the PIC.

I issue that command and then follow by ATSI,8 to see that it is now set correctly at 9600,8,N,2. The BlueSMIRF then responds with the expected “0027,0000,0001”. Best I can tell, it is now set at 2 stop bits instead of one. So I exit command mode with ATMD. Since the PIC is connected and sending an “!” every 10 seconds, I should then begin seeing the data come from the PIC and end up on Hyperterminal.

No such luck. And, when I disconnect in Hyperterminal and configure the port to 9600,8,N,2, it won’t connect to the BlueSMIRF at all. It responds with “Can’t open COM Port”.

Am I missing a simple step somewhere to get it to use 2 stop bits and read the data coming from the PIC?