Can I avoid reset (?) on WebREPL connection?

[peripi]

First of all! Great tool, previously worked with vs-code + PyMkr, this is a great improvement for me!

Im trying to learn how to use the web-repl, but find that the unit is reset every time that I attempt connect the REPL.

Using a browser I could connect to web_repl without reset, but using MicroPython Tools the unit is reset (as with serial connection). I cannot find a setting that avoids this. Is there one?

Thanks!

[lukaskremla]

By reset do you mean code execution is interrupted each time after connecting, but the file system is listed and REPL prompt is responsive?

Unless you're running into any exceptions or connection attempts failing - this is the intended and unfortunately necessary behaviour.

To facilitate the file system view, the plugin needs to run a script to print all the files/folders and details about them. And by that interrupting the code execution.

But it shouldn't interrupt your workflow too much.

You can send the Ctrl-D etc. shortcuts to interact with the device REPL and reset it - or use the Reset button in the REPL tab - the device will reboot and execute your main.py.

You can automate this with the upload run configuration, it can upload code and restart the device to execute it in one click.

Also - if at all possible, I recommend against using WebREPL. It is slow, has bugs and no where near as optimized and tested as this plugin's serial communication. If you need it, expect slower uploads and responsiveness

[peripi]

Thanks for your quick reply.

Yes, the code execution stops and I get a (responsive) repl-prompt.

The intended use case for me with the WebREPL is for remote (within local network) debugging (check REPL-print-outs) and possibly minor changes, everything else for sure via serial connection.

By the automatic "reset" at connection it seems to me this is not possible, as I understand it I cannot reach a state where "print"-statements are shown on the WebREPL? (I tried also via machine.reset() in the WebREPL).

Using this button to toggle connection:

[lukaskremla]

I see now.

It's a tricky feat to handle this in WebREPL.

By resetting the device, the connection is dropped and must be re-established.

The plugin should be able to do this, I worked on making this functionality a thing a while back and there haven't been complaints since.

However, while the plugin is re-establishing connection to your device, there is a short period of time when the plugin isn't connected to it, and the device is continuing with normal code execution.

Is the code you're executing just some quick prints that finish fast? It's possible that the code execution completes before the plugin is connected and can "see" the prints.

Try to add a couple second delay to your logic so the plugin has time to connect first. You could also test with some

while True:
   print("Hello World")
   time.sleep(1)

Add a delay/make a loop and try to restart the device, the REPL's reset button essentially does the same thing as the machine.reset() call, there is little difference.

Let me know if the delay helps.

[peripi]

In the specific project I work with at the moment (a mqtt-modbus gateway) I manage through sending debug-info via the mqtt, so its not really an issue at the moment. Its more that I think it would be a convenient way for OTA-debugging. Ie connect via WebREPL and monitor debug-outputs for say 10 minutes? This scenario would still not be possible with your suggestion, right?

Again this is not a big thing, just a nice feature, thanks for confirming the behavior. To conclude:
Online debugging OTA is possible via standard browser-WebREPL, that connects without "reset"
Online editing/file updating OTA: possible with the Plugin-WebREPL

[lukaskremla]

Yes, in order for the plugin to provide the file system view and some other features, it needs to interrupt the code execution, which makes it not fit for working as a REPL monitor that only prints out the output without affecting the device.

So your conclusion is correct.

But having non-disruptive WebREPL / Serial REPL monitoring functionality would definitely be good for the plugin.

I'll write it down in my notes for upcoming features/changes to the plugin - but note that it will take time until I might get to this. I'm currently working on MicroPython firmware flashing functionality for ESP, STM, RP2 and SAMD boards, that will take a while until I get it done.

Then I have a lot of other new features and changes planned.

In the future I'd like to add custom network REPL (that is free of the WebREPL weaknesses) and multi-device support, that will require rewriting the communication related parts of the plugin, and that's when it will be easiest to implement your suggestion. Can't provide an ETA yet though.

[peripi]

Sounds like exciting features!! Thank you for your feedback, and the plugin of course!

[lukaskremla]

You're welcome!

If you're enjoying the plugin, please consider leaving a review on the plugin's JetBrains marketplace page, it's greatly appreciated!

Thanks for opening a discussion, feel free to start a new one should you have further inquiries.

[peripi]

Just a short note back, have my node in sort of "production" now and made a change through the WebREPL. When I came back some hours later I found debugging info on the WebREPL, so I have to correct myself.

OTA debugging in the WebREPL is possible (I was under the impression that the WebREPL connection was lost during the "manual reset" to restart the project). The only thing that's not possible is in to connect to a running configuration without forcing a reset.

Thanks again, I will check the reviews!