RN 171 WiFi module

[jmgelba]

Rather than starting a new thread, I'll tack on to the bottom of this one.

I have a RN 171 connected to a 18F2550. I can receive commands via usb and serout them to the RN 171 but I'm not getting a response. I can see data to and from the RN 171 but I cant get it to load in to a variable using serin. I've seen a few examples of this issue on the forum but no one documented how they fixed it.

serout  PORTC.6,2,[text, text1, text2]
serin PORTC.7,6,2000, main1, [wifi]
WRITE 50, wifi.0
write 51, wifi.1
write 52, wifi.2
write 53, wifi.3
write 54, wifi.4
write 55, wifi.5
write 56, wifi.6
write 57, wifi.7
ARRAYWRITE USBTXBuffer, [wifi]
GOSUB WaitToSend

Note that I used mode 2 for serout and mode 6 for serin. If I use mode 2 for serin, it times out and jumps to my "didnt get any data" routine at main1. Currently, using mode 6, wifi is full of 0's and it repeats the loop sending text1, text2, text3 again.

[EarlyBird2]

Do not include [ ] for serin item as these are used around a qualifier.

[jmgelba]

Nice catch.

However I only get 1 byte so in looking at the manual I need to use SERIN2 with the STR qualifier. Awesome I think, then I modify the code to the following and now I get nothing again. It hangs at SERIN2 until the time is up then it jumps to my loop again. Wifi is defined as BYTE[16]

serin2 portc.7,84,250, main1, [STR wifi\16]
WRITE 50, wifi.0
write 51, wifi.1
write 52, wifi.2
write 53, wifi.3
write 54, wifi.4
write 55, wifi.5
write 56, wifi.6
write 57, wifi.7
write 58, wifi.8
write 59, wifi.9
write 60, wifi.10
write 61, wifi.11
write 62, wifi.12
write 63, wifi.13
write 64, wifi.14
write 65, wifi.15

[amgen]

serin2 portc.7,84, [STR wifi\16]    'wait here till 16 total bytes rcvd

'now, 16 bytes are in wifi array starting at wifi[0]
'toggle led or something to tell you got 16 new bytes

continue on....................

[EarlyBird2]

Nice catch.

However I only get 1 byte so in looking at the manual I need to use SERIN2 with the STR qualifier. Awesome I think, then I modify the code to the following and now I get nothing again. It hangs at SERIN2 until the time is up then it jumps to my loop again. Wifi is defined as BYTE[16]

serin2 portc.7,84,250, main1, [STR wifi\16]
WRITE 50, wifi.0
write 51, wifi.1
write 52, wifi.2
write 53, wifi.3
write 54, wifi.4
write 55, wifi.5
write 56, wifi.6
write 57, wifi.7
write 58, wifi.8
write 59, wifi.9
write 60, wifi.10
write 61, wifi.11
write 62, wifi.12
write 63, wifi.13
write 64, wifi.14
write 65, wifi.15

Serin2 is waiting for 16 characters to be received if you do not send 16 characters it will eventually time out. This is a common issue with serial communication however SERIN2 gives you the "tools" to overcome this.

I use a start character to indicate the start of a command string and an end character as a termination, which is not unusual. A commonly used start character is "!" and end character is $0D (CR). You could follow the LCDOUT protocol and use $FE as the start character the choice is yours.

Having decided which start and end characters to use modify your code and obviously include the start and end characters in the string you are sending.

serin2 portc.7,84,250, main1, [WAIT("!"),STR wifi\16\%0D]
WRITE 50, wifi.0
write 51, wifi.1
write 52, wifi.2
write 53, wifi.3
write 54, wifi.4
write 55, wifi.5
write 56, wifi.6
write 57, wifi.7
write 58, wifi.8
write 59, wifi.9
write 60, wifi.10
write 61, wifi.11
write 62, wifi.12
write 63, wifi.13
write 64, wifi.14
write 65, wifi.15

[pedja089]

jmgelba,
It's not clear to me what you are trying to do with write command....
WRITE 50, wifi.0 - this will write only one bit, just 0 or 1
WRITE 50, wifi[0] - this will write only byte from array

[Dave]

I was going to say the same thing. Misuse of the indexing modifier. Byte indexing should use "[x]" and bit indexing should use ".x"

[jmgelba]

I cant assign a start and end character because the module returns many different responses depending on circumstance and they can be different lengths.
I did indeed screw up the bit vs byte indexing, and this is what is causing my issue with this test code. I made the changes and I can now write the bytes to EEPROM which I can read. I now have to figure out how to send those bytes as a string out the USB port, unless I do they byte to text conversion on the PC side.