Feature request: Configure REPL echo over BT on Primehub

[antonvh]

With the Primehub, on the LEGO firmware, uart and REPL on the Bluetooth virtual com port are always echoed to the USB virtual com port. And vice versa. That is annoying.

Can you make this configurable on Pybricks? Default REPL on USB and optional REPL on BT?

Having a free uart/vcp on bt would open a lot of possibilities for inter-brick communication and brick-to-computer. You could then develop it via USB.

[laurensvalk]

We might be doing things quite differently in Pybricks; a lot of it is still open and to be decided. USB and Bluetooth Classic are not enabled yet. We focus on BLE because all hubs have it, and because we can use it in Pybricks Code.

At the moment, we are splitting the download-and-run communication stuff to a separate BLE service. This paves the way for easy hub-to-hub communication within user programs. (Without having to fall back to USB just to free up BT somehow.)

[antonvh]

That’s great news! Even more flexibility. Looking forward to it! I thought I’d send in this feature request early while 'things are still open and to be decided’. A Virtual Com Port over BT Classic would allow for wireless SPIKE-Prime <-> EV3 comms. Both ways. :P

…

On 22 Feb 2021, at 10:23, laurensvalk ***@***.***> wrote: We might be doing things quite differently in Pybricks; a lot of it is still open and to be decided. USB and Bluetooth Classic are not enabled yet. We focus on BLE because all hubs have it, and because we can use it in Pybricks Code <https://code.pybricks.com/>. At the moment, we are splitting the download-and-run communication stuff to a separate BLE service. This paves the way for easy hub-to-hub communication within user programs. (Without having to fall back to USB just to free up BT somehow.) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#261 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACW5HFVEFKR7V6ZYYT6VDTTAIPARANCNFSM4YADVVMQ>.

[laurensvalk]

We've summarized some of our plans for further discussion in #262, so we can close this one.