SIM900 issues #830
Replies: 8 comments
-
Posted at 2015-11-25 by @gfwilliams Hi Jon, that's a really odd one. I think first steps would be to check Otherwise it's a matter of poking around in the actual HTTP implementation, but I'm not sure that would be an issue as it's been used quite a lot to date. The SIM900 module is by far the mode likely culprit. If you are in the Hope that's some help - let us know how you get on! What are your changes? If you could contribute them back it'd be great - anything that cleans up the SIM900 code or makes it more reliable would be great. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2015-11-25 by jonreid Thanks for that - I had just done some reading on the networking to understand the interface and was about to start trying that. But now there are stranger things going on when I try to upload new code it is real slow and I get http and networkJS modules not found and then when uploaded the console is running real slow and a few keystrokes behind :( Maybe I have a hardware issue going on here ? |
Beta Was this translation helpful? Give feedback.
-
Posted at 2015-11-25 by jonreid gprs.at.debug() is showing multiple response lines eg What would cause that ? |
Beta Was this translation helpful? Give feedback.
-
Posted at 2015-11-25 by @gfwilliams Maybe you're somehow instantiating multiple GSM modules that are all listening for the same data? Have you disabled the |
Beta Was this translation helpful? Give feedback.
-
Posted at 2015-11-25 by jonreid OK my bad - I introduced some multiple modules in my debugging. Took a hardware reset to recover from that. So back to the original issue - there are a number of error conditions from SIM900 that are not being caught which means the busy flag and the AT handlers are not being cleared hence everything stops. I am in the process of adding these error handlers in - once I have it running reliably am happy to submit back. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2015-11-26 by @gfwilliams That'd be great - thanks! The module itself isn't in a great state, and I've had some trouble getting the SIM900 modules I bought working here (region problems) so I haven't really been able to do much about it. Not sure if it helps, but the ESP8266WiFi_0v25 module might help out as I think it tries to handle a lot of things in a more sane way. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2015-11-26 by jonreid OK will check out that module for some consistency. Out of interest will the SIM900 module support the new HTTPS additions or are there changes required ? I would prefer to use the Parse Cloud functions but they only work over HTTPS |
Beta Was this translation helpful? Give feedback.
-
Posted at 2015-11-26 by @gfwilliams Yes, it should 'just work'. The only problem would be if the SIM900 didn't accept raw data when sending over a socket (maybe it wants some characters escaped), but I think you're probably safe. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2015-11-24 by jonreid
I am having an issue with my Pico logger project which is using a SIM800 board. It runs successfully for over a week posting data every 5 mins to Parse.com, but then a couple of times it has got into a 'stuck state'. It is currently in this state and I am trying to debug.
When I reset the application the SIM800 does connect and do 1 or 2 succesful POSTs and then gets stuck.
Before doing the send I check I have a valid IP and then start a POST request. With at.debug() on I can see that CIPSTART is successful then I get CONNECT OK but then nothing more - no DATA SEND as normal. Then after a 30s or so the SIM800 sends a CLOSED.
I am running a local copy of the SIM900 module as I have added some functions. How do I go about debugging this further ?
Beta Was this translation helpful? Give feedback.
All reactions