AT Command

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi Freaks

Trying to communicate with SonyEricsson T68 using AT Commands.
Have studied several other projects that use AVR to send/receive SMS. Seems pretty straightforward.

For initial testing PC (Bray's Terminal) is used to send AT Commands to phone. MAX232 in between.

Anything sent from PC is immediately echoed back but PC never receive the expected "OK".
20 seconds after last AT Command is sent phone send "ERROR" to PC.

Have tested two T68 with same result so the problem should not be due to broken phone.
Obviously RS232-communication works since the phone reply.
Sending gibberish is echoed but phone don't reply with "ERROR".

I expected this first simple test sending "AT" and getting "OK" to work easy.
Most of my time yesterday was spent to searching on Internet for some explanation.
No success.
What am I missing?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I never played with T68 , but some with a T29 , sending & receiving SMS'es.

When the phone FSCK'ed up , and it DID ....

I had to send a BREAK , in order to establish comms again.

BREAK is TX "high for min 10 bitperiods" , i couldnt do it with the "uart" , so i disabled the uart tx function on my mega32, and set the portpin high for 500ms. Reenabled the uart tx , flushed buffers , and reset the AT-Statemachine.

There is an AT command to switch between OK or a numeric response 0/1/??.
And ATE1 turns on echo (phone echoes), ATE0 removes it ... if i remember correctly ..
I think the phone liked CR for EOL , not LF.
So a "\n" in strings should be a "\r"

/Bingo

/Bingo

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I think the phone liked CR for EOL , not LF.
So a "\n" in strings should be a "\r"

New day, new dawn...
I tested adding CR (actually before reading your post) and suddenly I got "OK" and other relevant replies from the phone.
Strange thing is I'm sure I've tested that yesterday too.

Anyway, GREAT RELIEF...
Thanks for your reply.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

hello lennart!
thanks for your reply,
but my problem is still present,before t68, i used t610 which replies "OK" by just pressing ENTER after AT,but with t68 AT is echo backed,i have no idea about CR,LF and EOL.
what should i do after/before AT comand.
Thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

hello lennart!
thanks for your reply,
but my problem is still present,before t68, i used t610 which replies "OK" by just pressing ENTER after AT,but with t68 AT is echo backed,i have no idea about CR,LF and EOL.
what should i do after/before AT comand.
Thanks

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Try ATI.

Imagecraft compiler user

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
what should i do after/before AT comand.
Nothing need to be sent before "AT"
After "AT" you send CR (0x0D).
The phone should reply "AT" and short time later "OK".