SatoBotLab
I’m dusting off an older rover that still runs an EZ-B v3 over Bluetooth and trying to make my ARC project more "plug and play" across two Windows laptops. The v3 pairs fine and shows up as two COM ports (SPP), but the COM number keeps changing between machines or after re-pairing (e.g., COM4 one day, COM7 the next). In ARC’s Connection control I can connect when the COM is correct, and I’m using a simple script to trigger it:
ControlCommand("Connection", "Connect", "0")
However, that relies on the preconfigured COM. I added the EZB Connect By Name skill hoping it could discover my controller by a friendly name (I renamed the Bluetooth device to "DriveBase"), but the log window stays empty and it never finds anything. I’m guessing that skill listens for the EZ-B WiFi broadcast (v4+) and not Bluetooth/serial from the v3.
Is there any supported way in ARC to connect to an EZ-B v3 by its Bluetooth device name (or otherwise auto-select the right COM) instead of hardcoding a COM port, or is there a recommended workflow/script to resolve the correct COM by Windows device name before issuing the Connection command?
Related Hardware (view all EZB hardware)
