SMS error : Falcom Samba 75

RickAtCrest · Post by **RickAtCrest** » Tue Feb 01, 2011 3:34 pm

Hello,

We obtained the Samba 75 specifically for use with HostMonitor and ran into the same error reported by another customer back in 2008:

"ERROR was returned on AT command: AT+CSMP=1,,0,240"

Comm settings are Com3 at 19200 and the modem is responding to AT commands.

I tried with both PDU and Text modes.

I've got experience with these devices so I connected to it with hyperterminal using the same comm settings and issued the following commands to send a test message:

at
OK
at+cmgf=1
OK
at+csca="+1xxxxxxxxxx"
OK
AT+cmgs="+1nnnnnnnnnn"
> This is a test^Z
+CMGS: 3

OK

The test worked.

Any suggestions? I'm willing to try diagnostic tools to help resolve this.

Cheers
-Rick

KS-Soft · Post by **KS-Soft** » Tue Feb 01, 2011 3:43 pm

Usually GSM modems does not provide any useful diagnistics

Could you try AT+CSMP=1,,0,240 command using hyperterminal?

Regards
Alex

RickAtCrest · Post by **RickAtCrest** » Tue Feb 01, 2011 3:54 pm

KS-Soft wrote:Usually GSM modems does not provide any useful diagnistics
Could you try AT+CSMP=1,,0,240 command using hyperterminal?

Regards
Alex

Here's the result

OK
AT+CSMP=1,,0,240
ERROR

I have friends at Falcom and will see if I can get more information regarding the behavior of the Samba with the CSMP command, but it's apparently not required to send an SMS message with my GSM provider.

-Rick

RickAtCrest · Post by **RickAtCrest** » Tue Feb 01, 2011 4:06 pm

Here's Falcom's supported AT command set reference:

http://www.falcom.de/uploads/media/Samb ... nd_set.pdf

The CSMP command is covered on page 231.

KS-Soft · Post by **KS-Soft** » Tue Feb 01, 2011 4:10 pm

Yeah, as usually just "error" without any description

AT+CSMP allows to set some options including Text or PDU mode.
As we know Falcom Samba should support this command.

I have friends at Falcom and will see if I can get more information regarding the behavior of the Samba with the CSMP command

That would be nice

Regards
Alex

KS-Soft · Post by **KS-Soft** » Tue Feb 01, 2011 4:33 pm

Can you try the following command?
AT+CSMP=1,0,0,240

Regards
Alex

RickAtCrest · Post by **RickAtCrest** » Wed Feb 02, 2011 9:39 am

I still get an error even when supplying the zero value for the validity period parameter. I also tried a value of one and got an error.

I was curious what the current values are and issued a query and here's what the response was:

AT
OK
AT+CSMP=1,0,0,240
ERROR
AT+CSMP=1,1,0,240
ERROR
AT+CSMP?
+CSMP: 17,167,0,0

OK

Let me know if there other things you'd like me to try. You can private message on the forum or my registered email address if it's too much detail for this thread.

* Edit - I forgot to say that we're running version 8.82

Cheers,
-Rick

KS-Soft · Post by **KS-Soft** » Wed Feb 02, 2011 4:14 pm

Yes, 167 is default value but I though it should accept 0 value as well.
Aha, my mistake - it does not accept 2nd parameter because we set 1 as 1st parameter, bit#5=0 means 2nd parameter skipped. But HostMonitor sent correct command...

Does it accept default value for 2nd parameter? AT+CSMP=17,167,0,240
If such command will lead to error as well while AT+CSMP=17,167,0,0 will be accepted, then I assume modem does not like 4th parameter - data coding scheme

Also, could you please type AT+CMEE=2 command before testing?
I hope then modem will provide useful diagnistic messages.

You can private message on the forum or my registered email address if it's too much detail for this thread

We don't use private messages, its hard to track such conversations.
E-mail is fine (support@ks-soft.net or just click HostMonitor/RCC menu Help->Support)

Regards
Alex

RickAtCrest · Post by **RickAtCrest** » Wed Feb 02, 2011 4:37 pm

Ok, success with both of the test commands you asked me to try.

Sending AT+CSMP=17,167,0,240 resulted in OK response

Sending AT+CSMP=17,167,0,0 also resulted in OK response

I then resent the first command (4th parameter = 240), then tested the ability to send a text message with that configuration.

The text message was successful.

Here is the hyperterminal history:

AT
OK
AT+CMEE=2
OK
AT+CSMP=17,167,0,240
OK
AT+CSMP=17,167,0,0
OK
AT+CSMP=17,167,0,240
OK
AT+CMGF=1
OK
AT+CSCA="+1xxxxxxxxxx"
OK
AT+CMGS="+1nnnnnnnnnn"
> This is a test^Z
+CMGS: 4

OK

KS-Soft · Post by **KS-Soft** » Wed Feb 02, 2011 8:39 pm

I see, thank you.
Could you try the following update www.ks-soft.net/download/ksgsmxlib16.zip ?
You need to close HostMonitor, unzip the file, replace current KSGsmXLib.ocx with new one, start HostMonitor again.

Regards
Alex

RickAtCrest · Post by **RickAtCrest** » Thu Feb 03, 2011 10:26 am

I think you may have linked the old version of the gsm ocx.

After closing HostMonitor, I renamed the original ocx "original_KSGsmXlib.ocx" and copied the new file into the HostMonitor8 directory as "KSGsmXlib.ocx".

I then ran HostMonitor and performed a message test. I received the same error as before:

Sending...
Com port open .. Ok
GSM modem initialization .. Ok
Error: Cannot send message to +1NNNNNNNNNN. GSM modem error. +CME ERROR: invalid input value was returned on AT command: AT+CSMP=1,,0,240
Com port close .. Ok
GSM modem deinitialization .. Ok

I double-checked that I had copied the new file into the correct folder and even ran regsvr32 to re-register the ocx, but it still used the original CSMP parameters as before.

I right-clicked both the original and new ocx, viewed properties, and see that both have a File Version number of 1.5.1.7. Not sure if that helps.

Let me know if you can think of anything I may have done wrong in trying the new ocx.

I want to add how much we appreciate the effort you have put into resolving this.

Cheers,
-Rick

KS-Soft · Post by **KS-Soft** » Thu Feb 03, 2011 5:05 pm

Sorry, that was our mistake. We do not have such modem at the moment so we sent you module without testing

I hope this one will work: http://www.ks-soft.net/download/ksgsmxlib16.zip

I want to add how much we appreciate the effort you have put into resolving this

No problem

Regards
Alex

KS-Soft · Post by **KS-Soft** » Sat Feb 05, 2011 5:39 pm

Does it work fine now?

Regards
Alex

RickAtCrest · Post by **RickAtCrest** » Mon Feb 07, 2011 10:55 am

Hi Alex, sorry for the delay in responding but I've been out of the office since Friday last week.

The new OCX fixed the last problem we had (great!) but a new error is popping up... fortunately it's easy to spot what it is.

Here's the error message when performing the test of the SMS alert:

Error: Cannot send message to +1nnnnnnnnn. GSM modem error. ERROR was returned on AT command: AT+CMGS="+nnnnnnnnnn",145>Message from HostMonitor (host changed status)

Test : Ping: (my IP was here)
Method: ping (timeout - 2000 ms)
Status : Host is alive
Date : 2/7/2011 10:40:

I see that you're sending a second parameter of "145" in the CMGS command. I'm not sure what that parameter is for, but the Samba doesn't like it. I confirmed that the problem is in the second parameter by trying the message in hyperterminal and get an error. Without the second parameter, the text message is sent just fine.

Is that an easy fix?

Cheers,
-Rick

KS-Soft · Post by **KS-Soft** » Mon Feb 07, 2011 7:07 pm

According to Samba 75 manual, it supports 2nd parameter for AT+CMGS command ("toda" parameter specifies type of destination address).
Samba manual does not say anything about possible values of this parameter but as I know its the same for any GSM modem where 145 means number in international format.
So, we don't know why it does not accept this command

I think you may setup HostMonitor to use PDU mode instead of Text mode.
Also you may try to get error description using terminal and commands like
AT+CMEE=2
AT+CMGS="+nnnnnnnnnn",145>Message

Regards
Alex