Most recent activity
-
- 5 comments
- 2,289 views
-
I've just turned on the modem, and sent AT, but sometimes it fails because of those messages.
Shouldn't it be sent only on turning modem up?
var gprs; Bluetooth.setConsole(true); var at; console.log("Turning Cell on"); require("iTracker").setCellOn(true, function(usart) { console.log("Waiting 30 sec for GPRS connection"); at = require('AT').connect(usart); at.debug(); }); > Turning Cell on Waiting 30 sec for GPRS connection ] "\r" ] "\nRDY\r\n" ] "\r\n+" ] "PACSP1\r\n" ] "\r\nR" ] "DY\r\n" ] "\r\n+" ] "PACSP1\r\n" ] "AT\r" ] "\r\nOK\r\n" >at.cmd("AT\r\n") ["AT\r\n" =undefined ] "\r\nR" ] "DY\r\n" ] "\r\n+" ] "PACSP1\r\n" ] "\r\nR" ] "DY\r\n" ] "\r\n+" ] "PACSP1\r\n"
I can't connect to the network anymore.
It only happens when the SIM card is present.
What do i do? -
Thanks @Gordon,
Yes, By serial I mean over Bluetooth. I'm really not sure what's happening.
RDY is sent when ME initialization is successful. But I never received it before, now i'm wondering, in the GSM/GPRS example, there is a wait of 30 seconds before connecting to GSM.
var gprs; console.log("Turning Cell on"); require("iTracker").setCellOn(true, function(usart) { console.log("Waiting 30 sec for GPRS connection"); setTimeout(function() { // ... },30000);
Is it really necessary? Because I ain't doing it.
Should I wait that long before registering to the network? -
Hey guys,
everything works fine until some point.
Then It starts dumping tons of RDY and +PACSP1 on serial that was meant for modem.
And when it does, there is nothing i can do to stop it, not even reseting the board... I mean, it stops while the modem is down, but once i bring it up it won't stop until i reset the board.I do have setConsole set on init. I also run it after boot, this isn't helping.
Bluetooth.setConsole(true);
I can't run a simple AT command.
Have you guys seen that behaviour before?
When I took the ammeter out the program worked flawless.