I have an Acer tablet PC which has the Ericsson F3307 modem built in.
I have written some software which requires the modem to dial a connection. Included in this connection is setting the PDP context.
I do this by issuing the command
AT+CGDCONT=1,"IP","apnname"
While playing with this command, I also set the context '2' which has left me with two PDP contexts defined, so when I type
AT+CGDCONT?
it returns
AT+CGDCONT?
+CGDCONT: 1,"IP","apnname","0.0.0.0",0,0
+CGDCONT: 2,"IP","mytest","0.0.0.0",0,0
I have tried issuing the command
AT+CGDCONT=2
To remove entry 2, but it just blanks it.. it doesn't remove it from this list.
+CGDCONT: 1,"IP","apnname","0.0.0.0",0,0
+CGDCONT: 2,"IP","","0.0.0.0",0,0
Does anyone know if there's a way of removing these entries, or doing a HARD RESET on the modem so that it forgets these settings ?
Thanks,
Rich
Related
I just received three USB TTL adapters each with a different chipset, and was testing them.
The CP2102 (I already own one, and it works normally) shows a weird defect: either by connecting it to another adapter (either of the two) or working in loopback, it will not TX data. No led activity, no bytes received on the other side (when it's connected with another adapter).
By chance though I noticed that when I close minicom (Ctrl-A, X, Yes), all that wasn't sent before, gets send at the same time after minicom closed (at least certain amount of data, I tried sending a file in ASCII mode and only a handful of rows of it was transmitted to the other adapter when I closed minicom).
OS is Ubuntu 19.04 64bit, and I'm running minicom as root from a terminal window. Either leaving out the baudrate (defaults to 115200) or setting it explicitly to 9600, the same thing happens.
Is this adapter toasted, and it's good just for RX-only appliations, or is there a way to get it back together?
You should try to disable Hardware Flow Control in minicom settings:
$ minicom -s
Then go to
Serial port setup
and set
Hardware Flow Control
to No
In the end, the adapter was not "defective", it just doesn't play nice with the minicom application in particular.
I fetched the other "working" CP2102 adapter that I had bought few years ago, to be used for another project from where I switched out a CH340G, and I could use it as expected both in TX and RX with a PHP script that I wrote for a SIM800L.
Then I connected to it with minicom because I needed to issue some commands manually, and the same thing that I describe in the question above also happened with this other CP2102.
I made a few modifications to my PHP script to make it act as a normal, user operated serial console, and I could both send commands and receive responses succesfully, where minicom couldn't.
I then fetched the "supposedly broken" CP2102 adapter, and I also could use it correctly with my homemade PHP serial console, whereas minicom simply didn't accept any user input.
While I was reading about AT-COMMANDS and their functions, I realized that there are types of them according to the character that came after AT.
Like +, %, $, #, *, &, \ or a letter.
1.What do each of these characters refer to? "I need details"
I'm interested in commands that have #, but my modem doesn't get me any of them when I entered AT+CLAC.
2.Can I activate those command by another `AT-COMMAND` or not?
NOTE:
I'm working on a phone modem.
The following is good to keep in mind. GSM modems have a number of standards that they "adhere" too. Basically the standards build ontop of each other in the following manner:
Serial Asynchronous Automatic Dialling and Control (V.25ter)
AT command set for GSM Mobile Equipment (GSM 07.07)
AT Command extended command syntax (manufacturer specific - you will need a manual from them)
Two very important facts to help you out when you don't want to read through too many documents are:
You can verify if a AT Command is supported by using the =? syntax. Normally when a command is supported by a modem then you will get a response with acceptable command values and an OK. Otherwise you will get an ERROR response back when it is not supported.
Some (not all) modems support the AT+CLAC command which outputs all supported AT commands.
So going back to the original question 1 :)
"+" are usually standard GSM AT Commands which you will find in the GSM 07.07 specification or the V.25ter specification.
"&" are usually low level serial configuration AT commands based upon V.25ter.
"%" tend to be manufacturer specific AT commands. So best bet here is to check your modem manufacturers AT Command Set documentation if it exists.
"$" tend to be manufacturer specific AT commands. So best bet here is to check your modem manufacturers AT Command Set documentation if it exists.
"#" tend to be manufacturer specific AT commands. So best bet here is to check your modem manufacturers AT Command Set documentation if it exists.
"*" tend to be manufacturer specific AT commands. So best bet here is to check your modem manufacturers AT Command Set documentation if it exists.
Moving onto your second question...
Unfortunately you cannot "activate" commands. They are built into the firmware of your modem. And as you see above there are manufacturer specific AT commands that are not implemented on every GSM modem out there.
There is one thing that you can double check and that is if you are really connected to your AT Command interface. There are usually a number of interfaces for example for GPS, manufacturer propriatory, and PPP interfaces. With the latter (PPP interfaces) you can infect execute AT commands but the command set is extremely restricted. This you can verify by executing an ATI command. I know for example with Sierra Wireless modems PPP interfaces are identified as APP1, APP2, and APP3. But this is again modem manufacturer specific.
I am trying to make WOL working on my MythTV box but I am doing something completely wrong as I cannot get the box to turn on.
I am running Mythbuntu 12.04. The MB is ASUS P8H61-I LX R2.0 which supports WOL as to my knowledge.
When I run ethtool eth0 via terminal I get this:
Supports Wake-on: pumbg
Wake-on: g
So I know the network card supports WOL as well.
When I turn the box off and then tries to send a magic packet, nothing happens at all. So either I have a wrong setup on the box or I am sending the packet the wrong way.
My router is the Netgear CG3000, but I am unsure what I have to setup in that to make it work if anything is needed to set up.
The box's local IP is 192.168.0.11
Is there a setup or something that I am missing somewhere?
This is a NIC issue with the motherboard
I am using Prolink PSH300 HSUPA GSM Modem connect to my laptop and using tera term to test the connect.
First I entered AT it will response me OK
AT
OK
AT+CMGF=1
OK
AT+CMGS="+6581XXXXXX" (then I pressed enter error was returned)
ERROR
Sometime it won't return me error but just hang there no > return.
Could anybody advise me what to do?
In your port initialization I would suggest you add these two lines-
port.DiscardOutBuffer();
port.DiscardInBuffer();
These will do a PurgeComm native WIN32 call, that will be resetting the hardware flow control lines.
Also add DtrEnable/RtsEnable = true lines to before opening the port connection.
Scenario: My nokia mobile conected to pc over bluetooth link.
commands: at (result ok), at+Cmgf=1(ok), but at+cmgs="mob.no">"hello"ctrl+z (result +cms error 500). I solved it by making a small change to extra initialisation setting in bluetooth modem. How, i explain here.
conrol panel -> phone and modem -> selected the blue tooth modem -> click properties. In the dialog window that opens goto advance tabs and change the existing extra initialisation commands: from whatever existed to any of the following as mentioned in the website below:
cksaheb.blogspot.in/2011/03/extra-initialization-command-for-gprs.html. My problem for sending sms solved.
I have the same problem. you must check antena connection.
Your GSM can't fine the network.
I am trying to configure my Arduino Wi-Fi module (RN-XV) with HTerm. However, when i connect it, it starts giving me strange output to the Recieved Data box. Squares and some characters, but nothing that i could read or use. What might be the problem?
(Problem shouldnt be anything about the values i set before connecting, because those settings worked with other guy)
Thanks!
Sounds like the com port speed is set wrong
According to the manual Manual
9600 baudrate, 8 bits, No Parity, 1 stop bit, and hardware flow control disabled is the default setup.
If this does not work try different com speeds.