The manual has the user using hyperterminal to send a text-file with the contents of +
in it. I think the escape is just +
, not +++
. Also, you have to wait a few seconds (two is default) of no serial activity before the escape character will work.
I'm not sure if sending a text-file causes the terminal to behave differently then just typing +
, or +++
, but it might be worth trying. Maybe it needs basically no delay between the three +++
, or it does something else (if the escape char is just +
)
Also, have you checked that your signals are not inverted? Maybe the usb-serial is defaulting to normally high, and the module wants normally-low, or vice-versa.
Confirmed in comments below as three +
characters, or +++
. You have to send it as a text file. I suspect that feeding hyperterminal a text file causes the three bytes to be sent as close to each other as possible, while typing them manually causes a ~200ms+ inter-character delay (e.g. as fast as you can manually hit the +
key).
Apparently the device has a much shorter "enter AT control mode" timeout them other similar devices, (like xBees, or such).
I don't know what to tell you, aside from the fact that you may have put the device into a strange serial mode (maybe you turned on an extra stop-bit, or set it to 7-bit serial).
I would recommend you try the configuration application that the manufacturer provides at the link about your module.
If that doesn't work, it looks like there is a mechanism for forcing it into a "configuration mode", which you can access by tying the nCTS/MODE/GPIO
pin high (to Vcc), and restting the module (by connecting nRESET
to ground temporarily).
From the manual:
In launching configuration mode, the system ignores the
default work mode parameters, and force to operate in the
AT+Instruction mode, this mode is commonly used to modify the
parameters with the configuration management program and to do
the function tests.
Look at section 4.2.1 in the PDF manual.
It's worth noting that if the module is correctly set up to join your network, it may be possible to fix it's configuration by connecting to it via WiFi. All the information about that should be in the manual.
Best Answer
First you need to understand the SOCKS protocol.
http://en.wikipedia.org/wiki/SOCKS
Then you need to implement that in your firmware.
Connecting the WiFi module to the access point is no different to any other access point. Establishing the authentication, IP address, etc is all exactly as per normal.
The only change comes when you want to make a request to the internet. Instead of making a direct request to the internet (say a HTTP "GET" request) you make a SOCKS request to the SOCKS proxy containing your request to the internet.