WizFi250 in AP mode stopped relaying GET requests to microcontroller

Question

Hi, We are using WIZFI250-H in a great number of microcontroller based boards. The chip is used in UART mode and is initialised after every power up with the following commands. AT+MECHO=0 //disable echo AT+WANT=0\r"; //external antenna AT+WSET=1,T4iSSID //Access Point mode AT+WSEC=1,WPA2,12345678 AT+WNET=0,192.168.12.105,255.255.255.0,192.168.12.1 //static IP AT+WJOIN AT+SCON=O,TSN,,,80,1 //Open at once, TCP server normal, data mode The devices act as access points. Each one has its own SSID. Windows based computers access them and send GET requests to the WizFi250. The WizFi250 relays the request to a microcontroller over UART which in turn parses it and replies. Since a few months ago every WizFi250 has stopped relaying most of the GET requests it receives. Example: A windows based PC (win10 or win11) sends a GET request using Postman (www.postman.com) or a web browser. The request times out but the WizFi250 has not sent any UART character to the microcontroller. Any ideas on why is this happening? Maybe a significant information would be that this behaviour started happening simultaneously in every device.

WIZnet AI assistant (automated answer) · Accepted Answer

It sounds like you're experiencing a widespread issue with the WizFi250 modules not relaying GET requests to the microcontroller. Here are a few potential reasons and troubleshooting steps you can consider: 1. **Firmware Update**: Check if there has been a recent firmware update for the WizFi250 that might have affected its behavior. If so, review the release notes for any changes related to UART communication or TCP server functionality. 2. **Network Environment Changes**: Consider if there have been any changes in your network environment, such as new security settings, firewall rules, or interference that could affect the communication between the PC and the WizFi250. 3. **Configuration Consistency**: Ensure that the configuration commands are being executed correctly and consistently across all devices. Double-check the AT command sequence for any potential errors or changes. 4. **Error Logs**: If possible, enable any logging features on the WizFi250 or the microcontroller to capture error messages or unusual behavior during the request handling process. 5. **Hardware Check**: Verify that there are no hardware issues with the WizFi250 modules or the microcontroller boards that could be causing the problem. 6. **Testing with Different Tools**: Try using different tools or methods to send GET requests to see if the issue persists. This can help determine if the problem is specific to certain software or configurations. 7. **Community and Support**: Check the WIZnet community forums or contact WIZnet support for any known issues or additional troubleshooting steps related to the WizFi250. If none of these steps resolve the issue, it might be helpful to isolate a single device and perform a detailed analysis of its behavior to identify any specific causes. If you need further assistance, feel free to reach out. Best regards, WIZnet AI Support Team