You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run the script again, tessel run phone.js. You should see an stacktrace like this:
GPRS module connected to Tessel. Searching for network...
Sending Text from a Tessel! to xxxxxxxxxxx ...
{ message: 'Chain broke on AT+CMGS="xxxxxxxxxxx"', type: 'Error', name: 'Error', stack: 'stack traceback:
/app/node_modules/gprs-sim900/index.js:208: in function 'f'
/app/node_modules/gprs-sim900/index.js:194: in function 'temp'
/app/node_modules/gprs-sim900/postmaster.js:152: in function 'reply'
/app/node_modules/gprs-sim900/postmaster.js:166: in function 'f'
/app/node_modules/gprs-sim900/postmaster.js:86: in function '?'
/app/node_modules/gprs-sim900/packetizer.js:152: in function '?'
builtin/tessel.js:738: in function 'func'
[T]: src/colony/lua/colony-node.lua:54: in function <[T]: src/colony/lua/colony-node.lua:53>' }
Debug info:
tessel version
INFO v0.3.5
tessel version --board
INFO Serial #: TM-00-04-f0009a30-00614757-58d045c2
INFO Wifi Version: 0.0
INFO Firmware Version: 93df6d7
INFO Runtime Version: cdb8be3
This might have more to do with running the script before the device has connected network activity. We should create a PR that broadcasts when network is connected, then test this bug again to see if its resolved. I can do this...
This might also be due to the SIM900 not cycling properly during a ctrl+C event (or more specifically, resetting itself to a default state when the script is run again). So it would be in the middle of an event transmission and be in a different state than what the message parser expects.
I've noticed errors and inconsistent behavior with the module. To recreate on a Mac, do the following:
tessel run phone.js
.ctrl+c
tessel run phone.js
. You should see an stacktrace like this:Debug info:
Related to outstanding issue with this PR: #13
The text was updated successfully, but these errors were encountered: