About this software 's issues

[CHN-STUDENT]

1. Start this software need to install the font even if it is already installed （Win10）
   
   see here: SourceCodePro font #25
2. Try to open a serial may need to select flashing firmware again even if the esp32 has installed
   
   I need to choose canceling then open this serial again.
   see here:NodeMCU-32S need burn firmware if the connection is disconnected and reconnected. #19
3. When run program then you want to open the code on device (ESP32), the debug out tell me open board file timeout
   
   And what number 1 means?
   4 . The debug info can not display fully on my device (ESP32)
   
   see here:cp210x serial port problem #26
4. When i need to reupload the code again,it gives me error reflush tree false
   
   see here:uPyCraft v1.1 Frequent issue after download completed, NameError: name 'os' isn't defined #31
   I have to choose disconnecting this device then open it again.
5. When i save the code by shortcut Ctrl+S , the code only saved on my device not computer?
   Please help me! Thanks!

[ouki-wang]

Currently unmanned

[barbudor]

@CHN-STUDENT
What is your problem?
Your report is useless. A bug report must include all details to allow reproduction.
Please details

• target board
• pc/Mac operating system
• what are you doing?
• what happens?
• how this is différent from expectation?
• have you seek help on the forum before raising an issue?

[CHN-STUDENT]

@barbudor Ok, thanks , i update it.

[barbudor]

Hi @CHN-STUDENT
First let me clarify that I am not involved with DFRobot or with the development of this software.
I am just a user, and while we all know that there are a few issues, the author made it clear that he/she doesn't have the resource for fixing this small bugs.
So either (1) we live with it as it is, (2) we walk away and look for a better software, or (3) we fork and fix it ourselves. As I'm not yet able to do (3), I've chosen (1).

However most of the problems that you are raising are either known or comes from a lack of experience with either uPyCraft or MicroPython.
There are workaround for some.

1. This is know and the workaround has already been given in the other issues. You have to install the font as Administrator, not as user.

2. You still doesn't say

• Which ESP32 board you are using (although it shouldn't make much difference)
• Which version of Micropython you have flashed
• If there is a code running on the board
  I generally have no problems to connect to my boards.
  For uPyCraft to work, it must have access to the REPL. On startup, uPyCraft is sending a Ctrl-C to the board to stop any running program and get access to the REPL. If this doesn't work and uPyCraft doesn't receive the REPL >>> prompt, it believes that the board if brand new and that MicroPython needs to be flashed.
  Why isn't your board responding ? As you are not providing enough details I can only guess from my experience:
• MicroPython it is crashed
• your Python software has disabled Keyboard Interrupt.
• your board is crashed
  uPyCraft can't do anything more than sending Ctrl-C. If the board doesn't behave as expected, uPyCraft can't do anything about it.
  You may try to reset the board and retry to connect until uPyCraft successfully get access to the REPL.
  It may not be possible and the board may requires reflashing the board to erase your program (if your program is the fault).
  As you don't provide a clear procedure how to reproduce your problem, I can't give specific advice.

3. I never faced this problem and you don't provide a clear procedure to reproduce it. So I can't help.
   But it looks like uPyCraft didn't get response as expected from your board and consider that there is a program running that doesn't stop.

4. Obviously your code mqtt.py is crashing the board. Is it because of the code or is it because your board is faulty, I don't know.
   But once again this is not the fault of uPyCraft.
   Note that I never use "download and run". I always "download" and then use "import" to run the code.
   I don't like much the way run is done. No rational, just a personal feeling.

other 4) It is very likely that your boot.py doesn't include import os.py
On 1st start/connection, uPyCraft send import osto the board so the os module is available. But if you reset the board by Ctrl-D then this import has been cleared unless you have it in boot.py.
Of course, we could ask to the author to always send import os before any other command that needs it. But that will impact performance to send this command when not needed.
So add import os in your boot.pi and you will be good.

5. Ctrl-S NEVER save the file to the device. Ctrl-S always save the file to your computer IF the file has been opened from the computer (workspace).
   If you open the board from the device, you can't do anything with it unless you "save as" an new file on the computer.
   Only Download can write a file to the board.

Let me know if you have further questions.

Cheers.