BeeryGaz
I've connected an Arduino SIM900 via the USB/ttl device and I've got the device working reasonably well. I had all sorts of issues with the Wavecom modem on a USB dongle so I've tried this instead.... Any chance you could have a look at this ? Thankyou
When I have HS send a message I get the message twice, here is the detailed debug, it appears a command isnt supported ?
2016.04.03-08.15.54: Sending watch dog message
2016.04.03-08.15.54: Sending: AT
2016.04.03-08.15.55: Response: <cr><lf>OK<cr><lf>
2016.04.03-08.15.57: Sending message to 61409839735
2016.04.03-08.15.57: Content: Virtual alarm is activated
2016.04.03-08.15.57: Sending: AT+CSCA?
2016.04.03-08.15.57: Response: <cr><lf>+CSCA: "+61418706275",145<cr><lf><cr><lf>OK<cr><lf>
2016.04.03-08.15.57: Sending: AT+CMGS=37
2016.04.03-08.15.57: Response: <cr><lf>>
2016.04.03-08.15.57: Sending: 07911614786072F511600B811604899337F50000A71AD6B49C5E0FB34161 7658DE06A5E7A0F0989EB687E96532
2016.04.03-08.16.03: Failed to send message: Unsupported feature: SendSmsFeature: Send SMS (Error in sending command 07911614786072F511600B811604899337F50000A71AD6B49C5E0FB34161 7658DE06A5E7A0F0989EB687E96532: )
2016.04.03-08.16.03: Trace: at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.SendMessage (Sms message)
at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.ProcessMess ageQueue()
2016.04.03-08.16.03: Base exception: at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.SendMessage (Sms message)
at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.ProcessMess ageQueue()
2016.04.03-08.16.04: Sending message to 61409839735
2016.04.03-08.16.04: Content: Virtual alarm is activated
2016.04.03-08.16.04: Sending: AT+CMGS=37
2016.04.03-08.16.14: Failed to send message: Unsupported feature: SendSmsFeature: Send SMS (Error in sending command AT+CMGS=37 : +CMGS: 159 OK )
2016.04.03-08.16.14: Trace: at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.SendMessage (Sms message)
at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.ProcessMess ageQueue()
2016.04.03-08.16.14: Base exception: at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.SendMessage (Sms message)
at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.ProcessMess ageQueue()
2016.04.03-08.16.15: Sending message to 61409839735
2016.04.03-08.16.15: Content: Virtual alarm is activated
2016.04.03-08.16.15: Sending: AT+CMGS=37
2016.04.03-08.16.15: Sending watch dog message
2016.04.03-08.16.15: Response: <cr><lf>>
2016.04.03-08.16.15: Sending: 07911614786072F511A00B811604899337F50000A71AD6B49C5E0FB34161 7658DE06A5E7A0F0989EB687E96532
2016.04.03-08.16.19: Response: <cr><lf>+CMGS: 160<cr><lf><cr><lf>OK<cr><lf>
2016.04.03-08.16.19: Firing async MessageSent event.
2016.04.03-08.16.19: Sending: AT
2016.04.03-08.16.19: Ending async MessageEventHandler call
2016.04.03-08.16.20: Response: <cr><lf>OK<cr><lf>
2016.04.03-08.16.30: Sending watch dog message
2016.04.03-08.16.30: Sending: AT
2016.04.03-08.16.30: Response: <cr><lf>OK<cr><lf>
2016.04.03-08.16.40: Sending watch dog message
2016.04.03-08.16.40: Sending: AT
2016.04.03-08.16.40: Response: <cr><lf>OK<cr><lf>
2016.04.03-08.16.50: Sending watch dog message
2016.04.03-08.16.50: Sending: AT
2016.04.03-08.16.50: Response: <cr><lf>OK<cr><lf>
I've connected an Arduino SIM900 via the USB/ttl device and I've got the device working reasonably well. I had all sorts of issues with the Wavecom modem on a USB dongle so I've tried this instead.... Any chance you could have a look at this ? Thankyou
When I have HS send a message I get the message twice, here is the detailed debug, it appears a command isnt supported ?
2016.04.03-08.15.54: Sending watch dog message
2016.04.03-08.15.54: Sending: AT
2016.04.03-08.15.55: Response: <cr><lf>OK<cr><lf>
2016.04.03-08.15.57: Sending message to 61409839735
2016.04.03-08.15.57: Content: Virtual alarm is activated
2016.04.03-08.15.57: Sending: AT+CSCA?
2016.04.03-08.15.57: Response: <cr><lf>+CSCA: "+61418706275",145<cr><lf><cr><lf>OK<cr><lf>
2016.04.03-08.15.57: Sending: AT+CMGS=37
2016.04.03-08.15.57: Response: <cr><lf>>
2016.04.03-08.15.57: Sending: 07911614786072F511600B811604899337F50000A71AD6B49C5E0FB34161 7658DE06A5E7A0F0989EB687E96532
2016.04.03-08.16.03: Failed to send message: Unsupported feature: SendSmsFeature: Send SMS (Error in sending command 07911614786072F511600B811604899337F50000A71AD6B49C5E0FB34161 7658DE06A5E7A0F0989EB687E96532: )
2016.04.03-08.16.03: Trace: at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.SendMessage (Sms message)
at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.ProcessMess ageQueue()
2016.04.03-08.16.03: Base exception: at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.SendMessage (Sms message)
at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.ProcessMess ageQueue()
2016.04.03-08.16.04: Sending message to 61409839735
2016.04.03-08.16.04: Content: Virtual alarm is activated
2016.04.03-08.16.04: Sending: AT+CMGS=37
2016.04.03-08.16.14: Failed to send message: Unsupported feature: SendSmsFeature: Send SMS (Error in sending command AT+CMGS=37 : +CMGS: 159 OK )
2016.04.03-08.16.14: Trace: at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.SendMessage (Sms message)
at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.ProcessMess ageQueue()
2016.04.03-08.16.14: Base exception: at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.SendMessage (Sms message)
at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.ProcessMess ageQueue()
2016.04.03-08.16.15: Sending message to 61409839735
2016.04.03-08.16.15: Content: Virtual alarm is activated
2016.04.03-08.16.15: Sending: AT+CMGS=37
2016.04.03-08.16.15: Sending watch dog message
2016.04.03-08.16.15: Response: <cr><lf>>
2016.04.03-08.16.15: Sending: 07911614786072F511A00B811604899337F50000A71AD6B49C5E0FB34161 7658DE06A5E7A0F0989EB687E96532
2016.04.03-08.16.19: Response: <cr><lf>+CMGS: 160<cr><lf><cr><lf>OK<cr><lf>
2016.04.03-08.16.19: Firing async MessageSent event.
2016.04.03-08.16.19: Sending: AT
2016.04.03-08.16.19: Ending async MessageEventHandler call
2016.04.03-08.16.20: Response: <cr><lf>OK<cr><lf>
2016.04.03-08.16.30: Sending watch dog message
2016.04.03-08.16.30: Sending: AT
2016.04.03-08.16.30: Response: <cr><lf>OK<cr><lf>
2016.04.03-08.16.40: Sending watch dog message
2016.04.03-08.16.40: Sending: AT
2016.04.03-08.16.40: Response: <cr><lf>OK<cr><lf>
2016.04.03-08.16.50: Sending watch dog message
2016.04.03-08.16.50: Sending: AT
2016.04.03-08.16.50: Response: <cr><lf>OK<cr><lf>
Comment