Issues with SMS

Hi Derek, Brett,

I have a new issue with my Hal.  The SMS module which was working, suddenly stopped.

When diagnosing the issue, I see this in debug:

Member for

16 years 10 months

brett

16 years 3 months ago

Given your getting something back but its looks like gibberish this smacks of a baud rate mismatch.

Have you tried microcom with a baud setting (I've just made up one here) to verify your phone will talk to you.

# microcom -s 9600 /dev/ttyUSB0

Without checking the source I'm not sure what default baud rate is used from the xap-sms.

Member for

16 years 5 months

BodgeIT

16 years 3 months ago

Hi Brett, nice to see you back, glad things are going well in States.

Funny thing is my sms was working no problem.

I tried the command and got alot of info coming back, looked liked xml but wasn't:

sg><d<dsb></dsb15</in>55><sec/sec>e><srme>Cname>1160<<<date>0000b><h/hr><min>55</min><sec>34</sec></date><src><name>CC02</name><id>01160</id><type>1</type><sver>1.0er></ch1><s>009atts>><chtts>0/wattch2><watts0</w</ch3r>28.mpr><<hrs>>000.2><h0.3</<h06></h08>00h08>001.00><h0.9</<h140</h116>00/h16>>001.8><01.1<<h22.3</hh24>0/h246>00126></days>0016><d02</d003>0003><d011</d05>0/d05>0018<><d07</d08>0018><d00</d10>0d10><000<<d12></d12>00003><d10</d115>0015><000</<d17>/d17>>0000><d190</d10>0020><d00</d22>0d22>0000<><d24</d245>0005><d00</dd27>0d27>0000<<d29></d29>0000><d30</ddays>><m010</m02>0002><m00</m04>00m04><000</m06>/m06>0000<><m08</m08>0009><m10</m111>0011><m00<//mths><y1>000</2>000/y2>00000><y4>000</yrs><></m<mate>00009><hr>hr><m</min>40</</datc><na02</<id>0/id><>1</tsver>/sverc><catts>5</wa/ch1><wat000</></chh3><w00000ts><<tmpr</tmpist><h02></h024>00004><01.8<<h087</hh10>0/h10>2>00012><01.0><h1.1</hh18></h180>001h20>001.3><h1.6</<h26>5</h2rs><dd01>/d01>0012><d03</d04>0014><d14</dd06>0d06>0016<<d08</d08>00009><d10</d111>0011><000</<d13>/d13>>0000><d150</d16>0016><d00</d18>0d18>0000<<d20</d201>0001><d00</d23>0d23><000<<d25></d25>00006><d20</d28>

 

Not sure if this is what is expected?

Member for

16 years 10 months

brett

16 years 3 months ago

You've plugged in a current cost haven't you?

That data is what you would see from a currentcost device on /dev/ttyUSB0 your SMS device has probably bump along one /dev/ttyUSB1

Verify this and adjust the DEVICE in the SMS page.  If you have both a current cost and a Phone they can't BOTH be /dev/ttyUSB0 can they!

Member for

16 years 5 months

BodgeIT

16 years 3 months ago

erm...can't they?  If only I'd looked at the info coming in, I may have figured that out for myself..

All good once more.

Thanks

Gary