WIFI Programming. Not able to see html on 192 IP

Technical Support
1

Product and Purchase

  • Product model: NexArm
  • SKU or kit name:
  • Purchase channel:
  • Controller board: ESP32

Software and Environment

  • Operating system:
  • Connection method:
  • Software version:
  • Firmware version:
  • Image version:
  • Tutorial step:

Issue Description

  1. What did you expect to happen?
  2. What actually happened?
  3. Error message or logs:

Reproduction Steps

  1. Ran and Deployment the WIFI Program. I see message in console for successfully running the wifi with SSID and Password.

  2. Connected to 192.168.4.1 via http

  3. used browser and curl both and received a timeout. How to debug?

Evidence

  1. Photos or short video:
  2. Wiring photo:
  3. Screenshot:

What You Have Tried

Urgency

  • Is this for a class, competition, or deadline?
2

The key check is which NexArm Wi-Fi program is running. The official browser demo and the external-control TCP service use different configurations.

  1. Upload the complete, unmodified 08 WIFI编程操作\WiFi_Test example. After reset, the serial output should include WiFi servo control demo started. and Open in browser: http://192.168.4.1.
  2. Connect directly to the NexArm_Servo_Control hotspot using password 12345678. Keep that connection active even if your device reports that the network has no Internet access.
  3. Open http://192.168.4.1, then test http://192.168.4.1/positions. The second address should return JSON containing the six cached servo positions.
  4. Confirm that loop() continuously calls system_loop_handler(). The HTTP server only processes requests while that function reaches g_server.handleClient().
  5. If the console instead shows SSID NexArm and password hiwonder, that is the separately documented TCP control setup at 192.168.4.1:8080. An HTTP request to port 80 does not test that service; use the WiFi_Test example for the documented HTML page.

If the unmodified example still times out, please post the complete serial output from reset, the exact SSID joined by the client, its assigned IP address, and whether /positions responds.

If this reply was helpful, you can mark it as the solution using the button below.