Nothing showing in the USB menu when I open the app on Mac

[benvallack]

The app opens ok but the USB menu on the connection screen is empty. Is this a known issue?

[anla-xu]

@benvallack Please provide your version number of mystudio

[benvallack]

@anla-xu 3.1.0 thanks!

[anla-xu]

@benvallack I have used several Macs that can be detected normally. I'm not sure why your computer can't detect it, but you can check whether the computer detects bacis or atom through the command ls -l /dev .check it when connected and check it after disconnected to see if there are changes.

[benvallack]

OK so it does work when I plug in the Atom USB port. But nothing shows up when I try and connect the main unit (BASIC). Can you confirm if I should have the rocker switch turned on or off and if I need the external power cable connected to connect to the BASIC usb port? (ATOM worked with no external power). Is there any other thing I need to do to get the BASIC one to be recognised?

[anla-xu]

@benvallack I'm very sorry, I can't solve your problem temporarily, no need to do any settings. In theory, as long as you connect to the computer through the usb link, the app can recognize BASIC. I'm not sure what caused it. It may be related to the system. Maybe you download it. Try another version?

[anla-xu]

@benvallack Have you installed the basic driver for m5? If not, please download and install first.(https://github.com/elephantrobotics/myStudio/releases/download/v3.1.2/CP210x_VCP_MacOS.zip)

[benvallack]

Ah this may well be the issue, however I am seeing a warning that says the developer needs to update the softare and it’s not letting me install it.

[anla-xu]

@benvallack If Apple users find that their files are damaged during installation, please use the command sudo spctl --master-disable to trust the software. If you have any questions, please submit an error screenshot

[maximilianimus]

@anla-xu hi :) i have the same issue. When connected to ATOM then mystudio see the board, but when i'm trying to connect to base as via usb type-с also via usb type-a then mystudio doesn't indicate "base" usb port connection.

mycobot 280 with raspberry pi
ver. of mystudio is 3.1.3
ver. of macos is 12.2.1
CP210x_VCP_MacOS was successfully instaled

[maximilianimus]

@anla-xu hi :) i have the same issue. When connected to ATOM then mystudio see the board, but when i'm trying to connect to base as via usb type-с also via usb type-a then mystudio doesn't indicate "base" usb port connection.

mycobot 280 with raspberry pi ver. of mystudio is 3.1.3 ver. of macos is 12.2.1 CP210x_VCP_MacOS was successfully instaled

The same issue on Windows os :(
ATOM is avaliable but base is not.
Also set up the drivers shown below

[anla-xu]

@maximilianimus Please try version 3.1.4

[maximilianimus]

@anla-xu hi. i downloaded the windows package from github. The name of package is Mystudio.Setup.3.1.4.exe.
But when i installed it on the main screen is showing version 3.1.3

[Benoit-P-B]

@anla-xu this was never resolved. I also had the same problem by using windows 10 and installing myStudio version 3.4.1... cannot find USB Port of myCobot 280 with M5 stack.... so in the end I was able to solve this by going and downloading & installing the following files that you list elsewhere:

CP210z_VCP_Windows.zip for Basic,
CDM21228_Setup.zip for Atom.

[JChrysanthemum]

Still not working on 280 m5, for the old version (3.1.2) or the latest one (3.5.1) on win 10. Have you stopped maintaining the old products?

Luckily, I found your doc for installing CP210X, CP34X, and CDM21228 manually:
https://docs.elephantrobotics.com/docs/gitbook/4-BasicApplication/4.1-myStudio/4.1.1-myStudio_download_driverinstalled.html

CHEERS!

Could you add this installation to your next version?

[alebarra]

Same problem with ubuntu both 22.04 and 24.04 and myStudio 3.6.1.
myStudio always show "no data".
The serial port works correctly, I'm sending commands via serial to my ultraArm and it works perfectly.
the problem seems to be that myStudio does not recognize the serial, even starting it with sudo and the user in the dialout group.
the two images show the problem: