MpTweetSendMessage

Hello,

I’m trying to send an SMS with MpTweetSendMessage but it doesn’t seem to work, even though remote connection works through the sim.

My setup is as follows:

EM1612 PLC, with 0RMSM1335.4G linked on the ETH port.

The modem has a SIM card inserted with data and sms plan.

The Site Manager works fine, I am able to connect to the PLC SDM for example, by creating a tunnel in the Gate Manager.

Seeing as the only uplink is the SIM card, all looks fine on this side.

The MpTweet component reports no error, and its active.

When I use the function MpTweetSendMessage, I can see the MpTweet.SentMessages counter increase and no error reported.

However I’m not receiving anything on the mobile.

In the log of the Site Manager I found this error:

Apr 14 14:38:25 SiteManager daemon.info IO: Receive SMS request from agent PLC at 10.0.0.2 (tcp)
Apr 14 14:38:29 SiteManager daemon.info IMCP: SMCP RECV 10.0.0.2:8888 SMCP(1:1) Type=2 Item=1 Len=16 CHAL:1ee7b455 SIGN:0
Apr 14 14:38:29 SiteManager daemon.info IMCP: SMCP XMIT 10.0.0.2:8888 SMCP(1:1) Type=3 Item=1 Len=60 CHAL:e881563b SIGN:9dba1ce3
Apr 14 14:38:30 SiteManager cron.err SMS[1832]: Mobile modem error response: +CMS ERROR: Unknown error
Apr 14 14:38:30 SiteManager cron.err SMS[1832]: Cannot send SMS -- only email targets supported

Am I missing some configuration to enable SMS sending ?

Anyone else had this problem ?

I think you require the 0RMAS.SMS license for this. Do you have that available for the respective gatemanager?
help link - sms license

Hi Jan,

Thank you for your feedback!

I think that license is required if you select to route your SMS messages through the Gate Manager (I’m thinking if you use SiteManager without SIM card, the Wifi or ethernet one),

but in my case I cannot even select the Gate Manager as SMS Alert gateway, which seems natural if the modem has a SIM card.

That license is listed on the Gate Manager in the help.

Maybe someone who is familiar with these licenses can answer?

Not sure if the absence of the license is why you can’t select gatemanager als alert gateway.
Only thing I found in AH is this:
Sitemanager config for Uplink 2 SMS
mptweet use case alarm message

I did not fill this in the first post, but I tried also using it as described in the help, but the error is the same.

  • I filled my name and number in the receiver list in the mptweetcore configuration, also the message in the Message List and tried sending via the Send input of the Core.
  • I filled a Request of type Command Request, and one of type Status Request
  • When sending a message to the SM (SiteManager) from my configured mobile number, I can see it in monitor mode in the Received array
  • I can also see in the log that the SM tries to reply with the configured message but fails with the same error like in the first post
  • I also tried to fill my number and text in the MpTweetCorePar structure, and send it via the Send input of the MpTweetCore in monitor mode, this fails with the same error

But I’m interested in using the MpTweetSendMessage function as its more straightforward.

I think I am either missing some configuration or that license (but why if this SM can do everything by himself locally, a GM license does not make sense to me)

I enabled debug mode and now the log displays more info, regarding the same error (I removed my mobile number from the log):

Apr 16 07:13:25 SiteManager daemon.info IO: Receive SMS request from agent PLC at 10.0.0.2 (tcp)
Apr 16 07:13:25 SiteManager daemon.info IMCP: SMCP XMIT 10.0.0.2:8888 SMCP(1:1) Type=3 Item=1 Len=60 CHAL:e9727e32 SIGN:c2665c06
Apr 16 07:13:28 SiteManager cron.debug SMS[19565]: SMS RQ='/READ/UNREAD'
Apr 16 07:13:29 SiteManager daemon.info IO: Receive SMS request from agent PLC at 10.0.0.2 (tcp)
Apr 16 07:13:29 SiteManager cron.debug SMS[19566]: SMS RQ='/+40xxxxxxxxx/status=TRUE'
Apr 16 07:13:29 SiteManager cron.debug SMS[19566]: SMS{*} => +40xxxxxxxxx
Apr 16 07:13:29 SiteManager cron.debug SMS[19566]: opening "/dev/ttym0"...
Apr 16 07:13:29 SiteManager cron.debug SMS[19566]: MOBILE CMD: AT+CMGF=0
Apr 16 07:13:29 SiteManager cron.debug SMS[19566]: MOBILE RSP[0]: OK
Apr 16 07:13:29 SiteManager cron.debug SMS[19566]: MOBILE CMD: AT+CMGS=35
Apr 16 07:13:29 SiteManager cron.debug SMS[19566]: MOBILE RSP[0]: '> '
Apr 16 07:13:29 SiteManager cron.debug SMS[19566]: MOBILE CMD: 0001000B910467367031F2000016737A985E9FF7A8D26A51113C97DD741D08CA1C023130^Z
Apr 16 07:13:29 SiteManager daemon.info IMCP: SMCP RECV 10.0.0.2:8888 SMCP(1:1) Type=2 Item=1 Len=16 CHAL:f06dbbe5 SIGN:0
Apr 16 07:13:29 SiteManager daemon.info IMCP: SMCP XMIT 10.0.0.2:8888 SMCP(1:1) Type=3 Item=1 Len=60 CHAL:e9728053 SIGN:353af53e
Apr 16 07:13:33 SiteManager daemon.debug IO: opening "/dev/ttym0"...
Apr 16 07:13:34 SiteManager daemon.err IO: Unable to lock file /dev/ttym0: Resource temporarily unavailable
Apr 16 07:13:34 SiteManager cron.err SMS[19566]: Mobile modem error response: +CMS ERROR: Unknown error
Apr 16 07:13:34 SiteManager cron.debug SMS[19566]: closing "/dev/ttym0"...
Apr 16 07:13:34 SiteManager cron.err SMS[19566]: Cannot send SMS -- only email targets supported

This issue is being worked on in the local B&R office. We’ll post a solution here.