Sozbayraktar

OK. I solved my problem, I share the result for the ones who are interested.Total number of characters in your GET.... string should be exactly 110 chars since you set your payload length to 110. This 110 includes the cr/lf at the end. So in your terminal window you have space for 37 chars of tweet text. If your text is longer, it is not delivered. If shorter, you should complete it by hitting the enter key repeatedly until it is completed, if you just wait without completing, transmission again fails. Subhan95 already told that in his prescription but it was useless in my case since my trial tweet was already exceeding the limit.

Thanks a lot for this helpful guide. But I still could not deliver a tweet yet. I got OK result from GET/POST Command (I tried both of them.) but no tweet message in twitter. Thingspeak setup has gone smoothly, I got API KEY for twitter. What could be the problem?:...AT+CIPSEND=1,110OK> POST /apps/thingtweet/1/statuses/update?api_key= ..xxx.. &status= first messagePOST /apps/thingtweet/1/statuses/update?api_key= ..xxx.. &status=first messagebusy s...SEND OK