Thanks for the info. I added the statement:
baud1 con 16572
and changed the following statement:
serin2 portc.4,baud1,[WAIT("$GPRMC"),STR sms\35]
Still no luck. Please help.
Thanks for the info. I added the statement:
baud1 con 16572
and changed the following statement:
serin2 portc.4,baud1,[WAIT("$GPRMC"),STR sms\35]
Still no luck. Please help.
___________________
WHY things get boring when they work just fine?
Which is the value of baud1?Code:serin2 portc.4,baud1,[WAIT("$GPRMC"),STR sms\35]
When you use wait string, remember that they are case sensitive "$GPRMC" is different from "$gprmc"
I already suggested you, in another thread, to use a timeout sequence. Your serin2 instruction will wait for the identifier and then it will wait for a string of 35 characters. If your GPRS will send only 34, serin2 will remain there waiting forever.
One turn around is the use of the timeout:
Al.Code:GPRSLoop: sms[0]=0 serin2 portc.4,baud1,500,GPRSTest,[WAIT("$GPRMC"),STR sms\35] GPRSTest: If sms[0]<>0 then goto label ?? ' here you check byte[0] for data presence goto GPRSLoop
Last edited by aratti; - 23rd October 2009 at 01:28.
All progress began with an idea
Thanks guys. Itīs up and running now. Love this Forum
Last edited by financecatalyst; - 23rd October 2009 at 17:03.
___________________
WHY things get boring when they work just fine?
The array was too small to hold the sequence of characters and code was kinda stuck there. I changed it to the following :
Baud con 188
sms var byte[65]
start:
serin2 portc.4,baud,500,start,[WAIT("$GPRMC"),STR sms\65\13] ' added 13 as well
If sms[0]<>0 then goto display
goto start
These are the only corrections I have done and it fired up.
___________________
WHY things get boring when they work just fine?
Bookmarks