This section provides a list of WizFi250 AT commands and their effects. Users can input
commands and parameters through USART line. Every command starts with the characters “AT”. Any other initial character will cause an error in return. Commands and parameters are all ASCII characters, e.g. When you input 'AT+MMSG=1', you can input
ASCII characters 'A', 'T', '+', 'M', 'M', 'S', 'G', '=', '1' and 'Enter Key' which
should be CR(0x0d), but neither CRLF(0x0d, 0x0a) nor LF(0x0a).
Some parameters are mandatory and the others are optional. (refer to Command Tables)
Parameters must be entered in an order of format column given by the command tables.
Even though an optional parameter is not used, the comma delimiters must still be
included in the command. In most cases, valid commands return the characters [OK].
Invalid inputs return [ERROR]. The possible responses sent by WizFi250 to the user
side are described at Responses.
Below is a possible example which users can input. As you can see, WizFi250 return
“\r\n” back instead of “\r”, which means user (host system) always handle '\r\n'
as a only delimiter.
Input by User | AT\r (0x61 0x74 0x0d) |
---|---|
Output from WizFi250 | AT\r\n[OK]\r\n (0x0d 0x0a 0x5b 0x4f 0x4b 0x5d 0x0d 0x0a) (* “AT\r\n” is Echo back of user input) |
Responses are listed below.
Response | Meaning |
---|---|
[OK] | Command Request Success |
[ERROR] | Command Request Fail |
[ERROR: INVALID INPUT] | Wrong command or parameter |
[ERROR: INVALID SCID] | Wrong Socket ID |
[ERROR: WiFi Status] | Wrong WiFi Status (Some commands work only with Wi-Fi Joined status) |
[ERROR: Mode Status] | Wrong Mode Status (Some commands do not work in Data mode) |
[CONNECT x] | TCP Connection established & Socket Open |
[DISCONNECT x] | TCP Connection closed & Socket Close |
[Link-Up Event] | WiFi Connection was established |
[Link-Down Event] | WiFi Connection was closed |
[Reset Event] | System reset occurred (not by user) |
Basic Commands | |
---|---|
AT | Terminal Check |
WiFi Commands | |
AT+WJOIN | WiFi Association |
AT+WLEAVE | WiFi Disassociation |
AT+WSCAN | WiFi Scan |
AT+WSET | WiFi Configuration |
AT+WSEC | WiFi Security Configuration |
AT+WNET | Network Configuration |
AT+WSTAT | Get Current WiFi Status |
AT+WREG | Country Configuration |
AT+WWPS | WiFi WPS Connection |
AT+WANT | WiFi Antenna Configuration |
AT+WP2P_START | Start WiFi Direct |
AT+WP2P_STOP | Stop WiFi Direct |
AT+WP2P_PEERLIST | Get WiFi Direct peer list |
AT+WP2P_INVITE | Invite WiFi Direct peer ID |
AT+WCHECK | Check Wi-Fi status using Ping and Re-association with AP |
Management Commands | |
---|---|
AT+MPROF | Profile Management |
AT+MFDEF | Perform Factory Reset |
AT+MRESET | Perform System Reset |
AT+MMSG | Set Message Print Level |
AT+MMAC | Set MAC Address |
AT+MINFO | Get System Information |
AT+MECHO | Set Echo Mode |
AT+MHELP | Print Command Description and Usage |
AT+MMCUPS | MCU Power Save Enable/Disable |
AT+MWIFIPS | Wi-Fi Power Save Enable/Disable |
AT+MCWUI | Change WebServer User Information |
AT+USET | UART Configuration |
AT+MSPI | SPI Configuration |
AT+MAIRCMD | Air Command Configuration |
AT+MEVTMSG | Print [Listen x] as soon as it opens up a socket through TCP server. |
AT+MEVTFORM | Event Message Form |
Basic commands are listed below.
AT
Check if AT Command Terminal is working.
[OK]
Commands related to WiFi are listed below.
AT+WJOIN
In the STA mode, it joins with the BSS selected by AT+WSET, AT+WSEC.
And in the AP mode, it starts to run as an Access Point.
Joining : (SSID) Successfully joined : (SSID) [Link-Up Event] IP Addr : xxx.xxx.xxx.xxx Gateway : xxx.xxx.xxx.xxx [OK]
Already Associated : (Mode) [OK]
AT+WLEAVE
In the STA mode, it leaves current BSS, but in the SoftAP mode, it stops to run as Access Point.
[Link-Down Event] [OK]
[OK]
AT+WSCAN=<SSID>,<BSSID>,<Channel>
Return the scan results filtered by parameters.
<SSID>: SSID Filter (Optional)
Scan only the AP which has this SSID.
<BSSID>: BSSID Filter (Optional)
Scan only the AP which has this BSSID.
<Channel>: Channel Filter (Optional)
Scan only the AP in this Channel.
* When combining these filters, it works at the same time. For example, if you enter AT+WSCAN=TestAP,00:08:DC:11:22:33', it only scans the AP which has TestAP as SSID and 00:08:DC:11:22:33 as BSSID in all the channel.
Examples)
Index/SSID/BSSID/RSSI(-dBm)/MaxDataRate(Mbps)/Security/RadioBand (GHz)/Channel ... [OK]
AT+WSET=<WiFiMode>,<SSID>,<BSSID>,<Channel>
<WiFiMode>: WiFi Mode to set (Required)
This changes current WiFi mode.
Parameter | Meaning |
---|---|
0 | Set Wi-Fi mode as STA mode |
1 | Set Wi-Fi mode as AP mode |
<SSID>: Target/Own SSID (Required, Max: 32 Character)
Mode | Meaning |
---|---|
STA | The SSID of target AP |
AP | Its own SSID to run |
<BSSID>: Target BSSID (Optional, Form: xx:xx:xx:xx:xx:xx)
Mode | Meaning |
---|---|
STA | The BSSID of target AP |
AP | Not used. if any, it will be ignored |
<Channel>: Target/Own Channel (Optional)
Mode | Meaning |
---|---|
STA | In STA mode, the Channel of target AP |
AP | In AP mode, its own Channel to run (Default: 6) |
* There are 2 Wi-Fi modes in WizFi250, STA mode and SoftAP mode. When users execute AT+WJOIN command, it works as Wi-Fi mode previously selected by the user. It can be selected or checked by AT+WSET and AT+WSEC commands, and it is the only way to handle Wi-Fi mode.
* AT+WSET, AT+WSEC commands save its parameters into the profile automatically, so the user does not need to save the current profile.
Examples)
[OK]
AT+WSET=?
<WiFiMode>,<SSID>,<BSSID>,<Channel> [OK]
AT+WSEC=<WiFiMode>,<SecType>,<Key>
<WiFiMode>: Target WiFi mode to set (Required)
Parameter | Meaning |
---|---|
0 | Set Wi-Fi mode as STA mode |
1 | Set Wi-Fi mode as AP mode |
<SecType>: Security type (Optional)
Parameter | Meaning |
---|---|
OPEN | None |
WiFi Auto Security | |
WEP | WEP (* Not support at SoftAP mode) |
WPA | WPA1 - TKIP |
WPAAES | WPA1 - AES |
WPA2AES | WPA2 - AES |
WPA2TKIP | WPA2 - TKIP |
WPA2 | WPA2 - Mixed |
<Key>: Security key value
Method | Length |
---|---|
WEP | 5 or 13 (ASCII), 10 or 26 (HEX) |
WPA | 8 ~ 63 (ASCII), 128 (HEX) |
* There are 2 Wi-Fi modes in WizFi250, STA mode and SoftAP mode. When users execute AT+WJOIN command, it works as Wi-Fi mode previously selected by the user. It can be selected or checked by AT+WSET and AT+WSEC commands, and it is the only way to handle Wi-Fi mode.
* AT+WSET, AT+WSEC commands save its parameters into the profile automatically, it works as Wi-Fi mode previously selected by the user.
* Minimum key length is 8 bytes in WiFi Auto Security.
In case of WEP mode and 5 bytes key, you should input the key with HEX type.
AT+WSEC=0,,12345(X)
AT+WSEC=0,,3132333435(O)
In case of OPEN mode, you should input the 8 bytes dummy string. Then WizFi250 will ignore the dummy key in OPEN mode.
AT+WSEC=0,,(X)
AT+WSEC=0,,12345678(O)
Examples)
[OK]
AT+WSEC=?
<WiFiMode>,<SecType>,<Key> [OK]
AT+WNET=<DHCP>,<IP>,<SN>,<GW>
<DHCP>: DHCP On/Off (Optional)
Parameter | Meaning |
---|---|
0 | DHCP Off, Static |
1 | DHCP On, DHCP Client |
Mode | Meaning |
STA | DHCP Client On/Off |
AP | Not used. if any, it will be ignored |
<IP>: IP Address (Optional)
<SN>: Subnet Mask (Optional)
<GW>: Gateway Address (Optional)
Mode | Meaning |
---|---|
STA | AP(Router) gateway address |
AP | Not used. if any, it will be ignored |
* When you turn DHCP On in STA Mode, <IP>,<SN>,<GW> are not needed. If you input them at this time, they will be stored in the memory. They can be used later when set as Static(DHCP Off) without inputting these parameters.
* In AP mode, DHCP Server will always run despite DHCP option,
and Gateway option will not be used, So both options will be ignored.
[OK]
AT+WNET=?
Note that <IP>,<SN>,<GW> address of response are not actual addresses, but addresses stored in the memory. So when DHCP is on, it usually different from actual addresses.
<DHCP>,<IP>,<SN>,<GW> [OK]
AT+WSTAT
IF/SSID/IP-Addr/Gateway/MAC/TxPower(dBm)/RSSI(-dBm) ... [OK]
AT+WREG=<Country>
Input a two letter country code (ISO 3166-1 A2) like US.
[OK]
AT+WREG=?
Refer to ISO 3166-1 A2
<Country> [OK]
AT+WWPS=<Mode>,<PinNum>
Join with an AP through WPS method
<Mode>: WPS Mode (Required)
Parameter | Meaning |
---|---|
0 | WPS_PBC_MODE |
1 | WPS_PIN_MODE |
<PinNum>: Pin Number (Pin Mode: Required, PBC Mode: N/A)
* The maximum pin number letter is 8.
Examples)
[OK]
AT+WANT=<Antenna type>
You had better not use this command unless it's absolutely necessary.
<Mode>: WiFi Antenna Type (Required)
Parameter | Meaning |
---|---|
0 | u.FL Antenna |
1 | PCB Antenna |
3 | Auto Selection |
[OK]
AT+WANT=?
<Antenna Type> [OK]
AT+WP2P_START
STA MAC: CE:52:AF:C6:CF:B5 [OK]
AT+WP2P_STOP
[OK]
AT+WP2P_PEERLIST
P2P Peers: 0: 'SHV-E250S' on channel 1 [OK]
AT+WP2P_INVITE=<Peer ID>
<Peer ID>: Peer ID to invite. This is from <AT+WP2P_PEERLIST> command.(Required)
[OK]
AT+WCHECK=<time>,<ping try>,<ping error>
It must be set as service mode in order to use Re-association function.
This function only exist later vision of F/W 1.0.3.5.
To use this option, you must enter a non-zero value.
<time>: try to ping (to gateway) each time. 10 ~ 86400(required, unit:sec)
<ping try>: count of ping. 5 ~ 20(required, unit:number of times)
<ping error>: WizFi250 will be disassociated if ping timeout is more than this. 1 ~ 20(required, unit:number of times)
Examples)
[OK]
AT+WADNS=<DNS Server1>,<DNS Server2>
<DNS Server 1>: DNS Server 1
<DNS Server 2>: DNS Server 2
Examples)
[OK]
Commands related to Network are listed below.
AT+SCON=<OpenType>,<SocketType>,<RemoteIP>,<RemotePort>,<LocalPort>,<DataMode>
Opens a socket and if it is a TCP Client, establishes TCP connection with remote peer device.
<OpenType>: Socket open type (Required)
Parameter | Meaning |
---|---|
O | open at Once |
S | register as a Service |
SO | open at Once & register as a Service |
* AT ONCE: Assigns a socket immediately and if the socket is a TCP Client, tries to connect peer socket.
* AS SERVICE: Registers its information to the profile. When WiFi Joined, socket open/connect will be performed automatically. If you want to use this after reset, It should be saved by using AT+MPROF=S
<SocketType>: Socket protocol to use (Required)
Parameter | Meaning |
---|---|
TSN | TCP Server Normal |
TSS | TCP Server Secured |
TCN | TCP Client Normal |
TCS | TCP Client Secured |
USN | UDP Server Normal |
UCN | UDP Client Normal |
* 'Secured' means TCP connection through SSL Encryption.
* Actually, there is no Server/Client concept in UDP protocol. This concept is used to decide peer address purposes. If a UDP Server receives any packet, its default peer address will be changed to the address of the packet, so if you send data after that, it goes to the changed address. But If you use UDP Client, its …default address stored by AT+SCON will never be changed.
<RemoteIP>: Remote IP address
Protocol | Parameter Application |
---|---|
TCP Server | N/A |
TCP Client | Required |
UDP Server | Optional |
UDP Client | Required |
<RemotePort>: Remote port number
Same condition with upper, RemoteIP
<LocalPort>: Local port number (Required)
Local port number should not be duplicated with others which have opened before. When the value is 0, in case the socket was a TCP/UDP Client, a random port number will be selected. If it was a TCP/UDP Server, it will return an error message.
<DataMode>: Mode to run (Optional, default: 0)
Parameter | Meaning |
---|---|
0 | Open as Command mode |
1 | Open as Data mode |
* About Command/Data mode, refer to Command mode & Data mode
Examples)
[OK]
AT+SCON=?
Use for check if previous input parameters are correct.
<OpenType>,<SocketType>,<RemoteIP>,<RemotePort>,<LocalPort>,<DataMode> [OK]
AT+SMGMT=<SocketID>
Closes the selected socket and releases all its resources.
<SocketID>: Socket ID (Required)
Parameter | Meaning |
---|---|
0 ~ 7 | The socket ID to close |
ALL | All the opened sockets |
* Opened socket information can be found by using '?' option.
Examples)
[OK]
AT+SMGMT=?
This prints all of the opened sockets statuses.
Number of Sockets : x (SCID/Socket/Mode/Remote/Local/DataMode) <SocketID>,<SocketAddr>,<SocketType>,<RemoteIP>,<RemotePort>,<LocalPort>,<DataMode> ... [OK]
AT+SSEND=<SocketID>,<RemoteIP>,<RemotePort>,<SendSize>,<Timeout>
This is used only in command mode, not in data mode. It is not required in data mode as you can input directly, but if you exit from data mode to command mode by inputting '+++', you can send data through this command.
<SocketID>: Socket ID (Required)
<RemoteIP>: Remote IP Address
Protocol | Parameter Application |
---|---|
TCP Server | N/A |
TCP Client | N/A |
UDP Server | Optional |
UDP Client | Optional |
* In case of TCP Server waiting for a client on listen state or in case of undecided remote address of the UDP Server (meaning its remote address is 0.0.0.0:0), this command will fail.
<RemotePort>: Remote Port Number
Same condition with upper, RemoteIP
<SendSize>: Data size to send (Required)
Valid Range: 1 ~ 100,000,000 Byte
<Timeout >: Set timeout value (milliseconds unit) (Optional)
If the transmission takes time more time than timeout value, it will fail and return error response. Default value is 10s + (100s / 1 MB)
Examples)
[OK]
AT+SDATA
In data mode, it can be changed to command mode temporally by using serial '+++' input. After that, to return to the data mode, you can use this command. If it is not data mode, [ERROR] response will be returned.
[OK]
AT+SFORM=<Format>,<Start>,<Delim>,<End>,<Cls1>,<Cls2>
Define the header of received data which is used at command mode. For example, default receiving format look like below.
“{0,192.168.0.216,59834,5}hello(0xd)(0xa)”
This means ASCII code “hello” was received from 192.168.0.216:59834 by socket ID 0, and its length was 5. You can change this format to suit your system through this command. Factory default option is
“111111111,7B,2C,7D,0D,0A”
<Format>: Decide each of header items to use. (Required)
If you want to set it to active, input '1', if not, input '0'.
Order | Meaning |
---|---|
0 | Header Start |
1 | Socket ID |
2 | Delimiter |
3 | Remote IP Address |
4 | Remote Port Number |
5 | Data Length |
6 | Header End |
7 | Data End 1/2 |
8 | Data End 2/2 |
* At default format, '{' '}' is header start and end, ',' is delimiter, 0xd,0xa is data end 1,2.
< Start>: Header Start Character (Required)
< Delim>: Delimiter Character (Required)
< End>: Header End Character (Required)
< Cls1>: Data End Character 1/2 (Required)
< Cls2>: Data End Character 2/2 (Required)
Examples)
[OK]
AT+SFORM=?
<Format>,<Start>,<Delim>,<End>,<Cls1>,<Cls2> [OK]
AT+SOPT1=<Option>,<Value>
<Option>: Option to configure (Required) <Value>: Value of the option (Required)
Option | Value |
---|---|
10 | Escape sequence(+++) Timer(millisecond, default 1000, 1~10000) |
Examples)
[OK]
Commands related to system management are listed below.
AT+MPROF=<Action>
You can save/load the environmental information in the RAM to/from flash ROM, or check the setting values in both of them through this command.
<Action>: The action to perform (Required)
Parameter | Meaning |
---|---|
VD | Get saved profile |
VG | Get current profile |
L | Load profile |
S | Save profile |
* There is no '?' option at this command.
Examples)
[OK]
+WSET=... +WSEC=... +WNET=... +WREG=... +SCON=... +SFORM=... +MMSG=... +MMAC=... +USET=... +MECHO=... +FWEBS=... [OK]
AT+MFDEF=FR
Factory Reset means that all of environmental variables return back to the default state. (You can check that by using AT+MPROF command)
[OK]
AT+MRESET
System will reboot after this command.
[OK]
AT+MMSG=<Level>
<Level>: Message Print Level (Required)
Parameter | Meaning |
---|---|
1 | Not Print Responses |
2 | Print Responses, Events (Default) |
3 | Print Responses, Events, Debug Logs |
Examples)
[OK]
AT+MMSG=?
<Level> [OK]
AT+MMAC=<MAC>
<MAC>: MAC Address (separated by colon) (Required)
Examples)
[OK]
AT+MMAC=?
<MAC> [OK]
AT+MINFO
FW version / HW version <FWver> / <HWver> [OK]
AT+MECHO=<Action>
If you turn the echo mode off, you cannot see the characters that you inputted returning. It is easy to use to turn off when Host MCU handles AT Command control.
<Action>: Echo Mode (Required)
Parameter | Meaning |
---|---|
0 | Echo Off |
1 | Echo On (Default) |
Examples)
[OK]
AT+MECHO=?
<Mode> [OK]
AT+MHELP
This is command usage guide for user convenience.
... [OK]
AT+MMCUPS=<Action>,<Timeout>
MCU Power Save Mode can be selected through this command.
<Action> : MCU Power Save Mode (Required)
Parameter | Meaning |
---|---|
0 | MCU Power Save Mode Disable |
1 | MCU Power Save Mode Enable |
* while using MCU Power Save Mode, WizFi250 cannot use serial communication.
<Timeout> : MCU Power Save Timeout value (Required)
Valid Range : 10 ~ 3600000 (unit:ms)
cc
[OK]
AT+MWIFIPS=<Action>,<Delay>
Wi-Fi power save mode can be selected through this command.
<Action> : Wi-Fi Power Save Mode (Required)
Parameter | Meaning |
---|---|
0 | Wi-Fi Power Save Mode Disable |
1 | Wi-Fi Power Save Mode Enable |
2 | Enables power save mode while attempting to maximize throughput |
* To using Wi-Fi Power Save Mode, WizFi250 has to connect to Access Point. And WizFi250 can only use this mode in station mode.
<Delay > : Return to Sleep Delay
If it is set with a bigger value, the performance will improve but the power consumption will rise.
Action | Application |
---|---|
0 | N/A |
1 | N/A |
2 | Required |
* This parameter is used only to set 2 of <Action> parameter.
* It must be set to a multiple of 10. When set to 0, the timeout period default to 2 beacon intervals (approximately 204ms).
* It can be set to 0 ~ 90
[OK]
AT+MWIFIPS=?
<Status > : Current Wi-Fi Power Save Status
Return value | Meaning |
---|---|
0 | Wi-Fi Power Save Mode Disable |
1 | Wi-Fi Power Save Mode Enable |
[OK]
AT+MCWUI=<Current ID>,<Current P/W><New ID>,<New P/W>
User ID and User Password used by web server can be changed through this command
<Current ID> : Current ID (Required)
<Current P/W> : Current Password (Required)
<New ID> : New ID which you want to change (Required)
<New P/W> : New Password which you want to change (Required)
Examples)
[OK]
AT+MCWUI=?
<Current ID>,<Current P/W> [OK]
AT+USET=<Baudrate>,<Parity>,<WordLen>,<StopBit>,<FlowCon>
UART parameter can be set through this command. Factory default parameter is “115200,N,8,1,N ”.
<Baudrate>: Set the Baud-Rate. (Required)
Parameter | Meaning |
---|---|
300 | 300 bps |
600 | 600 bps |
1200 | 1200 bps |
2400 | 2400 bps |
4800 | 4800 bps |
9600 | 9600 bps |
14400 | 14400 bps |
19200 | 19200 bps |
38400 | 38400 bps |
57600 | 57600 bps |
115200 | 115200 bps |
230400 | 230400 bps |
460800 | 460800 bps |
921600 | 921600 bps |
1843200 | 1843200 bps |
<Parity>: Set the Parity-Bit type. (Required)
Parameter | Meaning |
---|---|
N | None |
O | (Reserved) |
E | (Reserved) |
<WordLen>: Set the Word-Length. (Required)
Parameter | Meaning |
---|---|
7 | (Reserved) |
8 | 8 bits |
* 7 bits word length with no parity bit is not allowed.
<StopBit>: Set the Stop-Bit. (Required)
Parameter | Meaning |
---|---|
0.5 | 0.5 bits |
1 | 1 bits |
1.5 | 1.5 bits |
2 | 2 bits |
<FlowCon>: Set the Flow-Control method. (Required)
Parameter | Meaning |
---|---|
N | None |
HW | Hardware Flow Control |
Examples)
[OK]
AT+USET=?
<Baudrate>,<Parity>,<WordLen>,<StopBit>,<FlowCon> [OK]
AT+MSPI=<Interface>,<SPI Option>
<Interface>: Choice of interface (Required)
If <Interface> set 0, WizFi250 Will set the interface it received first.
For example, If MCU sends UART signal to WizFi250, WizFi250 will be set as UART interface. On the other hand, If MCU send SPI signal to WizFi250, WizFi250 will be set as SPI interface.
Parameter | Meaning |
---|---|
0 | Auto(Default) |
1 | UART |
2 | SPI |
<SPI Option>: Configure SPI Option (Optional when use SPI)
Value | Bit3 | Bit2 | Bit1 | Bit0 |
---|---|---|---|---|
0 | LSB_FIRST | CLOCK_IDLE_LOW | CLOCK_FALLING_EDGE | |
1 | MSB_FIRST | CLOCK_IDLE_HIGH | CLOCK_RISING_EDGE |
Examples(Received through UART interface):
Examples(Received through SPI interface):
[OK]
AT+MSPI=?
<Interface>,<SPI Option> [OK]
AT+MCSTGPIO
[OK]
AT+MCUSTOM=<custom code>
Examples)
Default custom code is WIZNET
[OK]
AT+MCUSTOM=?
WIZNET [OK]
AT+MAIRCMD=<OpenType>,<SocketType>,<LocalPort>,<Option>
<OpenType>: Air Command mode type (Required)
Parameter | Meaning |
---|---|
O | open at Once |
S | register as a Service |
* AT ONCE: Assigns a Air-Command-socket immediately.
* AS SERVICE: Registers its information to the profile. When WiFi Joined, Air-Command-socket open will be performed automatically. If you want to use this after reset, It should be saved by using AT+MPROF=S
<SocketType>: Air-Command-Socket protocol to use (Required)
Parameter | Meaning |
---|---|
T | TCP Server Normal |
U | UDP Server Normal |
<LocalPort>: Local port number (Required)
Local port number should not be duplicated with others which have opened before. When the value is 0, in case the socket was a TCP/UDP Client, a random port number will be selected. If it was a TCP/UDP Server, it will return an error message.
<Option>: Reserved (Required)
Examples)
<OpenType>,<SocketType>,<LocalPort>,<Option> [OK]
AT+MEVTMSG=<Status>
It is able to print TCP Server Status with [Listen x].(x:socket number).
A user can decide whether WizFi 250 will print out Listen message or not in initialization mode on TCP server.
This command is made for mbed library.
Uses 1 Parameter and set status of socket as 0,1 for each relevant below table.
<Status>: Printing status (Required)
Parameter | Meaning |
---|---|
0 | No display [Listen x] message |
1 | Display [Listen x] message |
Examples)
[OK]
AT+MEVTFORM=<format>
It is able to control format and printing status of WizFi250 event messages.
Uses 10 Parameters and set event message as 0,1,2 for each relevant one
<Format>: Event Message Format (Required)
0: No display
1: Full Message
2: Short Message
AT+MEVTFORM=abcdefghij
0(No display) | 1(Full Message,Default) | 2(Short Message) | |
---|---|---|---|
a | WizFi250 Version 1.0.3.6 (WIZnet Co.Ltd)\r\n | \r\n[0]\r\n | |
b | \r\n[CONNECT %x]\r\n | \r\n[1]\r\n | |
c | \r\n[DISCONNECT %x]\r\n | \r\n[2]\r\n | |
d | \r\n[Link-Up Event]\r\n | \r\n[3]\r\n | |
e | \r\n[Link-Down Event]\r\n | \r\n[4]\r\n | |
f | \r\n[Reset Event]\r\n | \r\n[5]\r\n | |
g | \r\n[TCP Send Error]\r\n | \r\n[6]\r\n | |
h | \r\n[P2P Fail Event]\r\n | \r\n[7]\r\n | |
i | \r\n[LISTEN %x]\r\n | \r\n[8]\r\n | |
j | Joining : … Successfully joined : … IP Addr : … Gateway : … |
Examples)
[OK]
AT+MEVTFORM=?
<Format> [OK]
Commands related to additional functions are listed below.
AT+FPING=<RepeatCnt>,<TargetIP>
<RepeatCnt>: Repeat Count (Required)
Valid Range: 1 ~ 50 (unit:number of times)
<TargetIP>: Target IP Address (Required)
Examples)
Ping Reply : xxx ms ... [OK]
AT+FDNS=<HostName>,<Timeout>
<HostName>: The domain name to search (Required)
<Timeout>: Maximum Delay (milliseconds unit) (Required)
Valid Range: 1,000 ~ 1,000,000 (unit:ms)(Recommend: 1000)
Examples)
xxx.xxx.xxx.xxx [OK]
AT+FWEBS=<Action>,<Type>
Web server can be set through this command. The default setting is to start web server when Wi-Fi link up event occurs. ( Factory default parameter is “0,M” )
<Action>: The action to perform (Required)
Parameter | Meaning |
---|---|
0 | Web server Stop |
1 | Web server Start |
<Type> : The web server launch type (Required)
Parameter | Meaning |
---|---|
A | Web server start when Wi-Fi link up event occurs |
M | Web server start when enter AT+FWEBS command after Wi-Fi is joined. |
* If <Action> parameter is 1 and Wi-Fi is joined, WizFi250 starts web server immediately without regard for <Type> parameter. If Wi-Fi is not joined, web server is started according to <Type> parameter. If you want to use <Type> parameter after reset, it should be saved using AT+MPROF=S
Examples)
[OK]
AT+FWEBS=?
<Status>: Current WEB Server status
Return value | Meaning |
---|---|
0 | Web server Stop |
1 | Web server Run |
<Status>,<Type> [OK]
AT+FGPIO=<action:0>,<gpio_number> AT+FGPIO=<action:1>,<gpio_number>,<gpio_value> AT+FGPIO=<action:2>,<gpio_number>,<config_value>
GPIO can be set through this command.
<action>: The action to perform (Required)
Return value | Meaning |
---|---|
0 | Get GPIO value when <mode> is 0 |
1 | Set GPIO value when <mode> is 1 |
2 | GPIO Initialize |
<gpio_number>: Available GPIO number (Required)
Return value | Meaning |
---|---|
1 | GPIO 1 |
5 | GPIO 5 |
6 | GPIO 6 |
7 | GPIO 7 |
8 | GPIO 8 |
<config_value>: Current GPIO Configuration Value (It can be used when action is 2)
Return value | Meaning |
---|---|
0 | INPUT_PULL_UP (Input with an internal pull-up resistor) |
1 | INPUT_PULL_DOWN (Input with an internal pull-down resistor) |
2 | INPUT_HIGH_IMPEDANCE (Input - must always be driven, either actively or by an external pullup resistor) |
3 | OUTPUT_PUSH_PULL (Output actively driven high and actively driven low - must not be connected to other active outputs) |
4 | OUTPUT_OPEN_DRAIN_NO_PULL (Output actively driven low but is high-impedance when set high - can be connected to other open-drain/open-collector outputs. Needs an external pull-up resistor) |
5 | OUTPUT_OPEN_DRAIN_PULL_UP (Output actively driven low and is pulled high with an internal resistor when set high - can be connected to other open-drain/open-collector outputs) |
<gpio_value>: Current GPIO Value (It can be used when action is 1)
Return value | Meaning |
---|---|
0 | Low |
1 | High |
Examples)
If <action> is 0
<gpio_value> [OK] ex) AT+FGPIO=0,1 0 [OK]
If <action> is 1 or 2
[OK]
AT+FGPIO=?
<mode>: Current GPIO mode
Return value | Meaning |
---|---|
0 | Input |
1 | Output |
* <mode> can be set to 0 automatically when <config_value> is set to 0,1 or 2. If <config_value> is set to 3,4 or 5, <mode> can be set to 1 automatically.
<gpio_number>: Available GPIO number
<config_value>: Current GPIO Configuration Value
<gpio_value>: Current GPIO Value
Examples)
{<mode>,<gpio_num>,<config_value>,<set_value>} [OK] ex) {1,1,3,0},{1,5,3,0},{1,6,3,0},{1,7,3,0},{1,8,3,0} [OK]
AT+FSOCK=<Option>,<Value>
When there is no socket connected, it try to reconnect the server using this option.
6,8 options must be set as service mode(AT+SCON=S) for Auto Reconnection.
Profile(AT+MPROF=S) has to be saved after AT+FSOCK
This function only exist later vision of F/W 1.0.4.1.
This is for extended options of Socket. It will be added continuously.
<Option>: Extended options of Socket (Required)
Parameter | Meaning |
---|---|
1 | TCP Send error timeout (value : 2000~20000ms) |
6 | Recreates Socket then attempts Auto-Reconnection after <Value> seconds (value: 10~1000) |
8 | Automatically resets WizFi250 module. when there is no socket connected (value: 5~1000) |
<Value> : Value of extended option (Required)
Examples)
[OK]
AT+FSOCK=?
<Extened option 1><2><3><4><5><6><7><8> [OK] ex) 5000,0,0,0,0,10,0,30
AT+FOTA
User can update firmware in OTA mode which can be entered by this command. Refer to Wi-Fi OTA
[OK]
AT+FWEBSOPT
[OK]
There are two user interface modes between WizFi250 and User-System.
Command mode is the default communication mode and all AT Commands can be used only at this mode. Through AT Commands, users can do 'WiFi Configuration', 'Sending/Receiving Data', 'Managing System', and so on. WizFi250 treats all received data from users as AT command. If all received data follows the correct command format, WizFi250 processes it and returns a proper response to user.
Data mode, on the other hand, is the mode which passes data of application layers to peer devices directly, without AT commands or any other interventions. It can be considered as a black box which passes all USART input to USART output directly. Its concept is simple but to enter this mode, Users need to set the environment properly through AT Commands.
Users can enter Data mode by writing '1' at '<DataMode>' parameter of AT+SCON command. Make sure that there are no open sockets before performing this, because Data mode works with one socket only. (So if you try to open another socket in data mode it will fail). If the socket of Data mode is closed, the mode will be changed to Command mode automatically so users can input AT Commands. If users set AT+SCON command as service with data mode option and save the profile, Data mode will be started when WiFi is joined, so the user does not need to set environments anymore. If the system boots or reboots at that time, WiFi Join will also be started automatically. Users can exit from data mode temporally by entering '+++' in a row (Wait for a second until [OK] response show up). Any AT Command can be entered during Data mode except AT+SCON command. If you want to return to data mode again, you just need to enter AT+SDATA. If you want to exit Data mode completely, close the socket by using 'AT+SMGMT=0' or 'AT+SMGMT=ALL'.
In Command mode, you can make more than one socket, and you can send/receive data through opened sockets at the same time by using AT Command. You can send data to specific socket opened through AT+SSEND command and receive data with information header which informs you on the socket number, the peer address and the received data length.