-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AT CMD In AP mode can not send UDP packets #10
Comments
webrtcccccc, are you using the AT-CMD Test Tool or pushing commands manually? I am able to replicate a similar issue when using the Test Tool. Steps:
Resulting in - (Client) Send: AT+WIPADDR?
But, when I start the send, the Serial Monitor shows: Which is not the correct Remote IP or Remote Port, and this incorrect IP and Port propagate through each attempted 256 Byte Transmission, resulting in the same SEND_IDLE. However, if I:
After successfully sending the "HELLO" I can then use the AT+SSEND (Continuous random data transfer) without issue from both Client and SoftAP sides. Overall, I have manage to send and receive UDP packets on a two-way Client/SoftAP connection, but it seems to be a bit finicky. And my issue seems to stem from using the AT+SSEND (Continuous random data transfer) tool within the AT-CMD Test Tool v1.3.0 so we may be experiencing separate problems. |
Thanks for the reply. I use the raspberry raspi-atcmd-cli app to test AT CMD. |
My Scenario is below AT CMD: --AP Side AT+WCOUNTRY="US" AT+WSOFTAP=906,"MyWiFi","wpa2-psk","MyPassword" AT+WIPADDR="192.168.1.1","255.255.255.0","192.168.1.1" AT+SOPEN="UDP",1000 AT+SSEND=0,"192.168.1.2",1000,10 0123456789 RECV: +SEVENT:"SEND_IDLE",0,0 --STA side (Can not receive from AP) |
Dear newracom sir,
I use the AT CMD to enter the AP mode, but in AP mode it cannot be used to send UDP packets, the AT CMD is as follows.
AT
SEND: AT
RECV: OK
AT+WCOUNTRY="US"
SEND: AT+WCOUNTRY="US"
RECV: OK
AT+WSOFTAP=906,"MyWiFi","wpa2-psk","MyPassword"
SEND: AT+WSOFTAP=906,"MyWiFi","wpa2-psk","MyPassword"
RECV: OK
AT+WIPADDR="192.168.0.215","255.255.0.0","192.168.0.2"
SEND: AT+WIPADDR="192.168.0.215","255.255.0.0","192.168.0.1"
RECV: OK
AT+SOPEN="UDP",1000
SEND: AT+SOPEN="UDP",1000
RECV: +SOPEN:0
RECV: OK
AT+SSEND=0,"192.168.0.215",1000,10
SEND: AT+SSEND=0,"192.168.0.215",1000,10
RECV: OK
1234567890
SEND: DATA 0 10
RECV: +SEVENT:"SEND_IDLE",0,0
=========================================
But in STA mode, it can send UDP packets normally.
AT+WCOUNTRY="US"
SEND: AT+WCOUNTRY="US"
RECV: OK
AT+WSCAN
SEND: AT+WSCAN
RECV: +WSCAN:"2c:3b:70:00:00:12",915.0,-10,"[WPA2-PSK-CCMP][ESS]","MyWiFi"
RECV: OK
AT+WCONN="MyWiFi","wpa2","MyPassword"
SEND: AT+WCONN="MyWiFi","wpa2","MyPassword"
RECV: OK
AT+WIPADDR="192.168.0.215","255.255.0.0","192.168.0.1"
SEND: AT+WIPADDR="192.168.0.215","255.255.0.0","192.168.0.1"
RECV: OK
AT+SOPEN="UDP",1000
SEND: AT+SOPEN="UDP",1000
RECV: +SOPEN:0
RECV: OK
AT+SSEND=0,"192.168.0.215",1000,10
SEND: AT+SSEND=0,"192.168.0.215",1000,10
RECV: OK
0123456789
SEND: DATA 0 10
RECV: +RXD:0,10
The text was updated successfully, but these errors were encountered: