BS2 MSRS and the BlueSmirf
I am having no luck·getting the Stamp recognize the ConnectionGranted string coming back from MSRS.
The Stamp will loop in its: SERIN 0, 84, 20, Wait_For_Confirm, [noparse][[/noparse]WAITSTR buffer \ 2, buffer2, buffer3, buffer4].
I am using a BS2 OEM module,·MSRS 1.5, a BlueSmirf and Free Serial Port Monitor.
As its running I see the RequestConnect command going to MSRS, I then see the ConnectionGranted reply from MSRS, but the Stamp doesnt recognize it and it just loops around and around and it will never send the RequestCommand.
I have soldered a wire to the red LED on the Smirf (Bluetooth Connected) to satisfy the IN5 command (which works rather well) so the Stamp starts its code when the serial connection is made.
Thinking it might be a Smirf vs EB500 thing I tried a direct serial cable connection, but this does the same thing also.
I also have several BS2 OEM modules as well as a couple of BS2 SX OEM ones, all these give the same results.
I cant find anyone with the same problem, so I cant blame the BoeBotControl.cs file, but I have also not read about anyone using the Smirf either.
Is there anyone who might know whats keeping the WAITSTR from seeing the FF 02?
The Stamp will loop in its: SERIN 0, 84, 20, Wait_For_Confirm, [noparse][[/noparse]WAITSTR buffer \ 2, buffer2, buffer3, buffer4].
I am using a BS2 OEM module,·MSRS 1.5, a BlueSmirf and Free Serial Port Monitor.
As its running I see the RequestConnect command going to MSRS, I then see the ConnectionGranted reply from MSRS, but the Stamp doesnt recognize it and it just loops around and around and it will never send the RequestCommand.
I have soldered a wire to the red LED on the Smirf (Bluetooth Connected) to satisfy the IN5 command (which works rather well) so the Stamp starts its code when the serial connection is made.
Thinking it might be a Smirf vs EB500 thing I tried a direct serial cable connection, but this does the same thing also.
I also have several BS2 OEM modules as well as a couple of BS2 SX OEM ones, all these give the same results.
I cant find anyone with the same problem, so I cant blame the BoeBotControl.cs file, but I have also not read about anyone using the Smirf either.
Is there anyone who might know whats keeping the WAITSTR from seeing the FF 02?
Comments
Its not a bluetooth thing at all, rather a serial comm issue.
I just cant get the timing right between them.
I have been using variations of the demo Stamp code and cannot get any better than the PC sending 20 to 30 requests to the Stamp and the Stamp replying with one.
In Free Serial Port Monitor I see many requests coming from the PC, Im not sure if the Stamp being bombarding by all these messages is jamming it up or if the timing of the serial just isnt correct.
I have everything set to 9600, Ive played with the rate a bit and this doesnt change anything.
If anyone has had any troubles with the serial configuration that has worked tham through, Id love to hear from you.
I know the stamp works, Ive been using them for years, I know MSRS works, because the LEgo NXT works fine too, so Its got to be something in-between.
Ive tried bluetooth, direct serial· and USB to serial connections, I get the same results every time.
Thanks...