-
Hi,
My Sim900 does not accept the newline character. If you try :
Serial.print("AT\r"); ... Serial.print("0x1A");The problem persits ?
Best regards,
@nicolasc_eu -
It could well be the newlines that are causing problems. As @nicolasc_eu says, try using
Serial.printand explicitly sending the newline character that you want.Just a note that if you want to send 0x1A, you can do:
Serial4.write(0x1A); Serial4.print("\x1A") Serial4.print(myOtherData + "\x1A")but the following won't work:
Serial4.print(0x1A); Serial4.print("0x1A"); -
Oh, sorry for the mistake
-
Thanks for the replies will give this a go tonight and let you know the outcome.
-
I've managed to get a couple of messages to come through based on the following code:
Serial4.print('AT+CMGS=\"078177XXXXX\"\r') Serial4.print(msg + "\x1a")Where msg is just a string of text to test with.
However it is hit or miss it seems whether a message sends. I get a SMS probably once every 4 or 5 restarts of the device and re-flashing with the code.
I seem to be getting loads of garbled text coming back from the GSM module as I had in my first post. This seems to mess up the commands being sent also as sometimes if I send a command using Serial4.print("AT+blahcommand"); I then see in my terminal a mash e.g.:
ÿ¬þ¾ÿÿ·ýÛÅ'ÿ翼ïõ OK °ªþÿÃÀþYg:K blèó@¨èÿ!£æþ;AAT+CMGS="078177XXXXX" >I never sent "AAT+CMGS" I actually sent "AT+CMGS".
Also the spurious data coming back is everywhere.. I've tried messing with the baud rates to no avail. Further example:
| __|___ ___ ___ _ _|_|___ ___ | __|_ -| . | _| | | | | . | |_____|___| _|_| |___|_|_|_|___| |_| http://espruino.com 1v51 Copyright 2014 G.Williams >echo(0); GSM Starting.. =undefined AT+CMGF=1 > > OK > AT+IPR=2400 > > OK > ü_öÿþþ×÷ýÿºþéÞ¹}uæÏ×ÿÿoç»ãÔîwgò]¥wæ³×7½×:Åž¬^\mu £ê½Oð¯dX×ÿ¿°íÛþ®µ».ë nýûWï÷ïíÿÿ÷ú?ÿöýæó¦øÿf*ëû¾¿ÿOÛ§ÿ½ÕýÞöçs«=öú÷»9¾¿GýËçüíºÏ½ßÜËËÿöÿûWo? ¾Ýýú> ýëÿÿ?Í¿}ÿßÿýÿ> Ïf; sÞ÷ÛßêôwAT+CMGS="07817XXXXXX" > > +CMS ERROR: 3765 > ÿ®ÿ?÷¿ÿÿï þv_«¿ÏÛûvùß}öûþ¿×ßu÷ýø¹}¿ÿ»þ_ÿ¿YþýßýÎ}½øÏï|úõÞÿ§¿¿Þº/_»ßçü¶ÿú_¿Ûiñ®Þ]ßgÝõ~Û?ÿýo?}½ôþ~ûßgõÿûùß1á¿à§uù\ûíîö«ÉþUßë»ÿ·¼G7=ÝýþéöÕó^ñã£mÆó=¾ø³å¸Î»Ö]móoÓj·æv3}ÿÃß$ùü}Æ_ó´÷ÎüS~tøÙíïÿ¢eÛëØýfyóë´ùïûRßÃÿzb¿ÉÝów|}±=a_1ÛÊrðýùö3oço6ôPgÿY¶;? ¸=3ÝÿÿÖÿÛÙ²~óí/ûä¾Bo/î¸îÛûw{^÷/ÿåÝVúïß¹AJçÞ)^½ùÍû~ïöèùÖ³ÓÆAwÿ¿Ï~øÿçåÝ?çÞèiZï_«®¿×Vüò_àøÏÛïë»:þ.íã?½üÿÿ<ì=)ýËîÿëø~ßßÿ¿ùõËûsç÷ßÙ¡¿ößë éÿ½ÿÛþÿ÷¿¿³÷ÿüÿ[ѯc¿âåíïúZïã]÷ ÿíÇí¡õy=õø.«{ìçog©k:µï¶_õÈôÖ÷Ófªï¿Uµÿ¯×? ù3_þü/ïßÿ®ó»Ë¿ûÿï;??÷ÿ·ÿGëWz×ïiãú1·Htû½ÝÿñÏßïß¼=ý?÷þõ?s¿êÿóíÓîýúÅî9WWæ6«ïʶð§ôüÏOºjæ|YTw-ÏßÛë¼Õ<ÇÔ× ì ùºY.ü:Çß ERROR >That is using a low baud of 2400. I get similar issues with high baud. The lower baud however always results in the "ERROR" message, the higher bauds atleast register something but I still get the garbled outputs which means nothing.
The parsing script I use for Serial4.ondata is:
function handler(c){ ms=ms+c; if (c=='\r' || c=="\n" || c==">"){ console.log(ms); ms=""; } } Serial4.onData(function (d) {handler(d.data);});Im attempting to pick up /n /r and > (which is returned when the GSM wants you to enter the SMS text).
Sorry for the long and incoherent post but theres lots of small issues. I know the module is functioning at least as I have received text messages, saying that though the messages are also garbled e.g.
"i@@@f@@?@y@@@@@test"
It seems to be sending the messed up text and then appending my actual "test" message on the end.
-
Have you read this thread, particularly the bit about PDU encoding? http://forum.espruino.com/conversations/626/#comment7811
-
I'll check the tx connection and also the board power. I need Max of 2amps and also 5v. I've been using the bat pin on the espruino and I think it isn't strong enough to meet these requirements.
I'll also have a mess with the tx line. I'll try it on a different serial first to see if the spurious data coming back drops off.
-
@Hardware_Hacks there's a 1 Amp thermal fuse on the Espruino board, so that could cause you problems. If powering from USB, the PC is only guaranteed to provide 500mA too.
-
Thanks for all the help on this guys.
I have just wired up the GSM module to a 1000mAh battery with 3A output and only using the Espruino for reading the RX and TX lines. The text messages now come through it seems every time and the AT commands are more responsive.
I am still getting some spurious data coming through the lines but not half as bad as before here is what I am seeing:
=undefined _____ _ | __|___ ___ ___ _ _|_|___ ___ | __|_ -| . | _| | | | | . | |_____|___| _|_| |___|_|_|_|___| |_| http://espruino.com 1v52 Copyright 2014 G.Williams >>echo(0); GSM Starting.. =undefined AT+CMGF=1 > OK AT+IPR=9600 OK >Serial1.print("AT+CMGS=\"07817xxxxx\"\r"); =undefined AT+CMGS="07817xxxxxx" > >Serial1.print("testing a message" + "\x1a"); =undefined ÿÿÿýýÿÿÿòÿïÿÿÿþûÿÿþýÿûÿýýìÿÿÿþÿÿöóýÿÿøüóüÿÿþûÿýýÿûýÿýûÿùûÿúÿû÷testing a messageÿÿÿÿÿÿýÿýýÿÿÿÿûþÿ +CMGS: 9 > OK >The text message I receive is:
ÿÿÿýýÿÿÿòÿïÿÿÿþûÿÿþýÿûÿýýìÿÿÿþÿÿöóýÿÿøüóüÿÿþûÿýýÿûýÿýûÿùûÿúÿû÷testing a messageSubsequent messages are better:
>Serial1.print("testing a message again" + "\x1a"); =undefined testing a message againÿÿÿÿÿÿÿÿÿÿÿþÿÿ÷ÿWith the message received at the phone being:
testing a message againIs there a check I can put in place to remove these weird characters?
Currently using:
function handler(c){ ms=ms+c; if (c=='\r' || c=="\n" || c==">"){ console.log(ms); ms=""; } } Serial1.onData(function (d) {handler(d.data);});For serial data handling.
For anyone else with similar issues to this thread, power was the killer for me it seems.
-
Ignore the last message.. It now seems to be working fine. Must have been some dodgy wiring!
-
Just found this library which I think I might butcher up and create a module for us:
-
Just had a quick look through and since I'm still a js newbie I'm guessing I need to do the following:
- remove the serial port require
- replace all serial port references with similar serial references as per espruino serial.setup etc
- remove event emitter?! or does espruino have this lib in place already? and replace with ..?
Ok I'm stuck already @Gordon any tips? I don't mind doing the leg work :)
- remove the serial port require
-
That sounds about right... There is some basic event emitter stuff - check the reference (however it applies to all objects right now, not via a special EventEmitter class).
However you might be best off using callbacks instead... Especially as there's no
bindfunction yet. By the way, it uses regex too, and Espruino can't do that yet.Personally I'd just look at what it's doing and reimplement it... That would probably be easier than trying to convert, and you'd probably get a nicer result
-
I agree and its kind of what I was doing in my basic set up. Time to brush up on callbacks then :)
Thanks for the pointers
-
@Alex: I've just created an issue for this: https://github.com/espruino/Espruino/issues/318
I'm not 100% sure when it will come - will you need to bind arguments, or just
this?If you don't need args, you can always workaround it for now by doing:
Function.prototype.bind = function(thisArg) { var f = this; return function() { return f.apply(thisArg, arguments); }; }; -
Hi Gordon, thanks for the reply! I'm dynamically constructing a function that is passed to an object. That object will then be free to call the function with it's own this. The reason why I dont simply use apply in the object (which will work too ofcourse) is that our current backend binds the this of the object to the function beforehand so the input files are already finalized.
I'll try to see if your example works for me! Thank you so much :) -
Hi Gordon, it seems using the code in your example crashed the espruino. I did find a workaround which will suffice for now but using the bind() function would be much neater. I have branched the bug off on my git, maybe it can help you identify a problem. I'm using the 1.60 firmware.
My Git is here: https://github.com/AlexDM0/espruinoEVE
The branch espruinoBug shows the problem. If you upload the entire code it hangs clearly. The bind command is on line 161.
nicolasc_eu
Gordon
DrAzzy
Alex-
Post a reply
About
GSM2 Click Interfacing.
Posted by
@Hardware_Hacks
Hi All,
I'm a bit stuck when trying to send a text message via my GSM2 Click device which uses the M95 chip.
I have the module accepting AT commands through Serial4 however I really can't get the syntax working correctly to send a SMS message sucesfully.
I can carry out the following commands:
I firstly set the chip to Text Mode:
I then set the number to send the SMS to (I have added in the xxx's for anonymity)
As you can see there is a lot of garbled characters but the output is an "OK" at the end.
I then assume that the Serial4 is sat at the ">" prompt where I would then enter the text for the text message so I go ahead with the following command:
From here I know I need to send a CTRL+Z character at the prompt to send the message so I carry out the following:
However.. I receive nothing. I would expect to see an ID number pop up and the message to go through to my phone.
Any ideas where I am going wrong here I've been messing around with all the variants I can think of - changing the Serial.write to print and print to println with no luck.