console_test Problems with running python scripts that don't show the associated graph (AEGHB-811)

[mubai-w]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate.
• Provided a clear description of your suggestion.
• Included any relevant context or examples.

Issue or Suggestion Description

When I finish with two slices ESP32S3 console_test instance is running python esp_csi_tool.py -p COM5 and no relevant graph appears esp_csi_tool.py where the baud rate has been changed to 115200 Or how do I use the interface of the esp_csi_tool.py with two tablets of esp32s3 The version I'm using is esp_idf v5.3

[NingYuxiang]

The baud rate is set to 2000000 by default.

If you want to change it to 115200, you need to modify both the baudrate in the esp_csi_tool.py file and the ESP_CONSOLE_UART_BAUDRATE in the console_test program. However, note that a low UART baud rate may result in delayed data transmission, causing queue overflows and data loss.

[TindalosKorone]

I have the same problem with him, I'm using ESP32S2, although my log is reacting, but by the time of getting CSI data, the same happens. After that, I used putty to monitor at 921600, and I could obtain CSI data, but under the same baud rate , I don't see it in console_test

• As shown in the picture, my log stops under CSI RECV

• but you can see it in putty:
  

• Even if I use another software csi_data_read_parse.py , it can be displayed: