Uri Shaked

Results 619 comments of Uri Shaked

Note about the com0com workaround (from @jflamy): > you need to download the previous version 2.2.20 of com0com. The later version doesn't work (signing issues). Works fine with that version.

Note: this is now supported by [Wokwi for VS Code](https://marketplace.visualstudio.com/items?itemName=wokwi.wokwi-vscode). It uses the standard RFC2217 protocol, which is supported by the popular pySerial library. You can learn more [here](https://docs.wokwi.com/vscode/project-config#serial-port-forwarding)

> It seems there isn't a good RFC2217 node.js library. If you are only interested in textual data, then you can treat the RFC2217 server as a standard TCP socket....

The simulator is opening a TCP server. You need to connect to it to see the prints.

Wokwi open a TCP server. You need to connect to it, localhost:4000 (or whatever port you set in Wokwi.toml), not listen on port 4000

What does your wokwi.toml look like? Are you using a VS Code dev container or WSL?

Looks good. Does your code keep printing stuff to the serial monitor? You'll only see what's been printed **after** netcat has connected.

Thanks! Internally, we have a distinction between "attribute" and "variable": - Attributes come from diagram.json, and never change once the simulation has started. Attributes are always represented as strings in...

Thanks! > Regarding the api, you may still want to have string controls (setting the display contents?) The main use case I'm seeing for controls is for setting sensor input...

As a first step, we now have a "Create new project" button: ![image](https://user-images.githubusercontent.com/892318/120886047-99535700-c5f4-11eb-9a35-279f2c153d9c.png)