Sim I/O or console data to-and-from external JS process, in real time

[toysonlocation]

After asking around on the regular makecode lists, I've been directed here in case someone hopefully knows how to achieve this: pipe makecode/microbit sim data in real time to another JS workflow (via ANY method, such as classic JS console or maybe a socket), and then have that other workflow also send back data (via simulated sensors, for example) to the makecode sim. The other workflow would be a real time processor of the sim data, written also in JavaScript and perhaps in another HTML frame, and pass back state for the simulated microbit to handle. Please advise!

[pelikhan]

Jacdac uses a mechanism called "control simmessages" in pxt that allows to send a buffer through a C++ function or through a HTML window message (to/from jacdac simulator iframe).

The API is implemented in pxt however loading iframes in the editor is restricted to known URLs, so you would have to create a local build of the editor to allow yours.

That being said, it may turn out that Jacdac is the right abstraction for you and we can make it work for your scenario. We already support a switching between simulated or hardware data in the micro:bit editor. I'm wondering what's the gap to make it useful in your scenario.

(Note I'm confused about the difference of both workflows)

[pelikhan]

Here is a potential way to do this without having to fork makecode. It is using jacdac (disclaimer).

This solution is based on the jacdac devtools, that allow to load a makecode editor side by side with another web site that's running the jacdac code. Both communicate via iframe messages.
You would load a custom web site that would then communicate to your robot simulator tool.

makecode editor <-> proxy web site <-> robot simulator

Now messages are jacdac packets so you'll need to use use jacdac services to send/receive state updates between the makecode simulator and the robot simulator.

Concretely, the students would model their rover as a device with 2 motor + sonar services using jacdac blocks. Motor commands are sent from makecode to the motor simulator and sonar events are polled back from the motor simulator to makecode.

[pelikhan]

I wouldn't be against pro typing this with you; I can help with the jacdac plumbing but I am not well versed in robot simulators.

[toysonlocation]

Hi pelikhan - I'm super sorry for vanishing. I got covid in early May and am only now getting back on track for this project. I am also not well versed in robot simulators! However, I've done a number of visual/mechanical applications, and this is going to be part of a STEM curriculum that I'm pretty excited about. I really appreciate your (back in April) above note. What would you like to see on deciding whether or not this is something for you?

[pelikhan]

Please take a look at what we've built with jacdac. I don't have the time to take on something else at the moment.

If you can map your system as a "service", you could leverage our infrastructure.

[toysonlocation]

Thanks - I'll have a look at your most recent release and docs and probably have to inquire here and there.