SMS Server Tools 3
This site is hosted by Kekekasvi.com
 Menu
Basic information:
Additional information:
Support:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

 Search
Custom Search

 Visitor locations
 
 SMS Server Tools 3 Community
Welcome, Guest. Please login or register. Sun May 19, 2024 21:40
SMSTools3 Community » Help and support Bottom

[outdated] Nokia 3510i, put_command expected (OK)|(ERROR), timeout occurred.

  This topic is locked

Page:  1

Author Post
Member
Registered:
Sep 2009
Location: Sweden
Hi all!

I've been trying to setup an sms server for quite a while now without success :|

My first guess was that I couldn't use a usb cable to connect my phone (nokia 35101) but after some configuring that part seems to be working. So, my second guess was that the baudrate could be the error, I've tried 9600, 19200 and a few more with no success.

Now I have no idea of what to try. Here's my smsd log:


On the line "2009-09-01 18:02:46,7, GSM1: ->" there is a strange symbol, a box with two zeros and a "1" and an "A" so I'm guessing the smsd has a problem interpreting the messages from the mobile, right?

And my smsd conf:

Thanks in advance! SHiR0

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
shir0 wrote
My first guess was that I couldn't use a usb cable to connect my phone (nokia 35101) but after some configuring that part seems to be working.

How did you verify that it's working completely? Using some terminal program like minicom? Did you get the OK response for AT command?

Quote
So, my second guess was that the baudrate could be the error, I've tried 9600, 19200 and a few more with no success.

You probably have tried 115200 and rtscts = yes, as those settings are the default values. If the device worked well while using other terminal program, what values was used with it?

Quote
On the line "2009-09-01 18:02:46,7, GSM1: ->" there is a strange symbol, a box with two zeros and a "1" and an "A" so I'm guessing the smsd has a problem interpreting the messages from the mobile, right?

It represents a sent data. When smsd tries to initialize the modem and there was no answer for the AT command, smsd tries to send a PDU termination character which is Ctrl-Z (1A in hex). This may help if a communication was broken and the modem is still waiting a PDU string. In your case it did not help.

Some interface modules are known to be problematic when a communication starts. It may have something to do with FBUS/MBUS protocol. I do not know about this adapter cable for 3510i, but at least it does not look like the simplest one. In some cases, even up to 5 or 10 retries are needed until the communication starts to work.

In your setup you use cs_convert = no setting. This has nothing to do with a communication problem, but have you noticed that with this setting you should create message files using GSM character set or Unicode? If you are sending messages with 160 characters / part and creating a file using ISO or UTF-8, cs_convert will convert the alphabet to GSM which is the most usual way.

Member
Registered:
Sep 2009
Location: Sweden
Topic owner
Quote
How did you verify that it's working completely? Using some terminal program like minicom? Did you get the OK response for AT command?

I thought that the line in smsd.log with the hex character was a reply from the phone (though not interpreted correctly). But now that you told me it was a "ctrl-z" sent from smsd I guess it isn't working after all.
Another thing that i thought was a good indication was that with rtscts = yes I got:


And with rtscts = no I got:

And therefore I assumed that the connection was working.

But all my assumptions seems to be based on a misunderstanding since i thought the "GSM1: -> AT" parts were replies from the phone. :oops: I just read about wvdialconf briefly and when I ran it I got

According to dmesg the phone is suppose to be connected on ttyUSB0. From the looks of it I guess its the cable right? Maby the serial cable might do the trick? :mrgreen:


« Last edit by shir0 on Tue Sep 01, 2009 19:04, 179 months ago. »
Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
shir0 wrote
According to dmesg the phone is suppose to be connected on ttyUSB0. From the looks of it I guess its the cable right? Maby the serial cable might do the trick? :mrgreen:

Yes, the port looks correct.

Probably the cable is broken, or it needs some special driver. Can you test this cable on Windows?

Member
Registered:
Sep 2009
Location: Sweden
Topic owner
Quote
Yes, the port looks correct.

Probably the cable is broken, or it needs some special driver. Can you test this cable on Windows?

Now that you mention it, there was a drivers cd included. I've got windows on my lappy, perhaps I'll try it tomorrow. I doubt the cable's broken since its brand new, on the other hand, it did require some force to connect it to the phone. Probably the worst connector I've ever seen :mrgreen:

  This topic is locked

Page:  1

SMSTools3 Community » Help and support Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.