Fast Websocket sending causes stuttering? about websockets2_generic HOT 3 CLOSED

Thanks for using the library.

Can you provide more information so that the issue you're experiencing can be duplicated, identified and debugged, if exists.

As you know, the process, even though seems simple, requires the perfect cooperation of every underlying layers, such as

1. Nano-33-IoT core and hardware
2. WiFiNINA_Generic/WiFiNINA library
3. This WebSockets2 library
4. Your home network: routers, settings, etc.
5. The WebSockets Server you're connecting to
6. many more

It's advisable that you isolate the issue to be related to 1., 2. and/or 3.by using another board, such as ESP8266/ESP32. If the problem persists, then you'll know it's possible 3-6. If this is the case, it's better that you post on the issue on ArduinoWebsockets Issue as it's ESP32/ESP8266 related.

You can also use this independent SimpleWebSocket example of WiFiWebServer Library to verify if the issue is related to this WebSockets2 library.

You have to post the whole sketch, so that other people can duplicate the issue. Otherwise, nobody can have psychic power to guess what's wrong or waste time to recreate, and the issue will be closed.

from websockets2_generic.

Hello, I'm using the example sketch but I've modified it to send a string message every 16ms.

I've tried using it on my ESP32 and it does not have the same problem. The ESP32 works perfectly fine and the data comes in smoothly and quickly. So this leads me to believe it's:
a) not my server
b) not my internet connection
c) possibly not the library? Maybe there's a problem all Arduino Nano 33 IOT's have that causes this?

I've tried using the WifiWebServer library example you suggested on the Nano 33 iot but it still has the same problem.

Here's some of the code I used from that example. I modified it to send data every 16ms.

void setup()
{
  Serial.begin(115200);
  while (!Serial);

  Serial.print("\nStarting SimpleWebSocket on " + String(BOARD_NAME));
  Serial.println(" with " + String(SHIELD_TYPE));

  // check for the presence of the shield
#if USE_WIFI_NINA
  if (WiFi.status() == WL_NO_MODULE)
#else
  if (WiFi.status() == WL_NO_SHIELD)
#endif
  {
    Serial.println(F("WiFi shield not present"));
    // don't continue
    while (true);
  }

#if USE_WIFI_NINA
  String fv = WiFi.firmwareVersion();
  if (fv < WIFI_FIRMWARE_LATEST_VERSION)
  {
    Serial.println(F("Please upgrade the firmware"));
  }
#endif

  // attempt to connect to WiFi network
  while ( status != WL_CONNECTED)
  {
    Serial.print(F("Connecting to SSID: "));
    Serial.println(ssid);
    // Connect to WPA/WPA2 network
    status = WiFi.begin(ssid, pass);
  }

  // you're connected now, so print out the data
  printWifiStatus();
  wsClient.begin("/capstone/ws?clientId=1");
}

void loop()
{
  

  while (wsClient.connected()) 
  {
    // send a hello #
    wsClient.beginMessage(TYPE_TEXT);
    wsClient.print("1,234,562,456,777");
    wsClient.endMessage();

 
    delay(16);
  }

  Serial.println("disconnected");
}

from websockets2_generic.

As I suspect, I now think this is the issue is deeper inside the WiFiNINA library and/or Nano-33-IoT.

Can you make a simple sketch using WiFiNINA to demonstrate the issue, then post on WiFiNINA Issue.

Also search there to see if there is similar issues/fixes.

Hope you find out a solution. Please update then.

I'm closing the issue now because it's not something related to this library.

from websockets2_generic.