Simucube 2 PRO Waiting for drive to get ready

Hi Mika

Some days ago my Simucube 2 Pro start to fail, and now doesnt works anymore.

Every time i turn on the switch button, i dont have the “beep beep” sound anymore, but i have the windows sound that detects the device well.

Yesterday, i downgrade from 2020.10 software, to 2020.07 and all worked fine again. I used the simucube all day with no problem.

But today when i restarted the pc, the servo has not response again. I tried the .04 and .01 software version witouth sucess.

I changed the usb cable for other, reconnected both psu again, and also connected to another pc, and with the same problem. Both psu have the blue light turned on, and the servo base light is blue permanently.

Hope you can help me


sc2 issue 2

Try this starting process:

  • Power ON SC2 base with TrueDrive Closed
  • Wait for Windows USB beeps and SC2 beeps
  • You can start TrueDrive now
1 Like

Thanks for the reply. I did that, and it worked 1 time. Now doesn’t work again. I power ON the SC2 base, it only beeps windows but not sc2.

I did this log

11:56:36.927: with logging
11:56:36.936: Opened style file
11:56:36.940: Warning: QMetaObject::connectSlotsByName: No matching signal for on_show_hide(QSystemTrayIcon::ActivationReason)
11:56:37.244: Warning: QMetaObject::connectSlotsByName: No matching signal for on_wirelessbutton_clicked()
11:56:37.249: Warning: QMetaObject::connectSlotsByName: No matching signal for on_exportButtonMenu_clicked_one()
11:56:37.252: Warning: QMetaObject::connectSlotsByName: No matching signal for on_exportButtonMenu_clicked()
11:56:37.263: wheel image: attempting to load: “wheels/wheelimage.png”
11:56:37.276: “D:/Archivos de Programa/Simucube 2020 10/simucubeprofiles.ini”
11:56:37.280: “D:/Archivos de Programa/Simucube 2020 10/profiles_autobackup.ini”
11:56:37.282: “D:/Archivos de Programa/Simucube 2020 10/profiles_autobackup.ini”
11:56:37.308: loadIncludedFirmwareVersion: included 1.0.30
11:56:38.268: EULA previously accepted.
11:56:38.278: Disconnected state
11:56:38.287: unable to open device, pid: 3423
11:56:38.295: unable to open device, pid: 3424
11:56:38.303: unable to open device, pid: 3425
11:56:38.307: Could not connect to SC2
11:56:39.265: Disconnected state
11:56:39.273: unable to open device, pid: 3423
11:56:39.281: unable to open device, pid: 3424
11:56:39.288: unable to open device, pid: 3425
11:56:39.291: Could not connect to SC2
11:56:40.256: Disconnected state
11:56:40.264: unable to open device, pid: 3423
11:56:40.271: unable to open device, pid: 3424
11:56:40.279: unable to open device, pid: 3425
11:56:40.282: Could not connect to SC2
11:56:41.265: Disconnected state
11:56:41.273: unable to open device, pid: 3423
11:56:41.284: unable to open device, pid: 3424
11:56:41.291: unable to open device, pid: 3425
11:56:41.295: Could not connect to SC2
11:56:42.263: Disconnected state
11:56:42.271: unable to open device, pid: 3423
11:56:42.279: unable to open device, pid: 3424
11:56:42.286: unable to open device, pid: 3425
11:56:42.290: Could not connect to SC2
11:56:43.263: Disconnected state
11:56:43.271: unable to open device, pid: 3423
11:56:43.278: unable to open device, pid: 3424
11:56:43.285: unable to open device, pid: 3425
11:56:43.289: Could not connect to SC2
11:56:44.263: Disconnected state
11:56:44.271: unable to open device, pid: 3423
11:56:44.279: unable to open device, pid: 3424
11:56:44.287: unable to open device, pid: 3425
11:56:44.291: Could not connect to SC2
11:56:45.263: Disconnected state
11:56:45.273: unable to open device, pid: 3423
11:56:45.281: unable to open device, pid: 3424
11:56:45.288: unable to open device, pid: 3425
11:56:45.291: Could not connect to SC2
11:56:46.262: Disconnected state
11:56:46.270: unable to open device, pid: 3423
11:56:46.277: unable to open device, pid: 3424
11:56:46.284: unable to open device, pid: 3425
11:56:46.287: Could not connect to SC2
11:56:47.265: Disconnected state
11:56:47.273: unable to open device, pid: 3423
11:56:47.282: unable to open device, pid: 3424
11:56:47.293: unable to open device, pid: 3425
11:56:47.296: Could not connect to SC2
11:56:48.260: Disconnected state
11:56:48.268: unable to open device, pid: 3423
11:56:48.275: unable to open device, pid: 3424
11:56:48.282: unable to open device, pid: 3425
11:56:48.286: Could not connect to SC2
11:56:49.261: Disconnected state
11:56:49.272: unable to open device, pid: 3423
11:56:49.283: Connected to SC2 Pro
11:56:49.288: reconnected
11:56:49.795: got a response
11:56:50.009: loadIncludedFirmwareVersion: included 1.0.30
11:56:50.012: shouldShowFirmwareUpdatePrompt: device reported 1.0.30
11:56:50.016: first connection done
11:56:50.019: no need to update
11:56:50.022: checked fw update need
11:56:50.255: got profiles
11:56:50.390: Configured in unexpected state
11:56:50.394: got hardware settings
11:56:51.470: got analog data and settings

Isn’t it perhaps a windows update thing? For some reason (perhaps because I have dozens of usb devices attached lol…) my updates always end up causing problems somewhere…

1 Like

Do You Know how many profiles are created in TrueDrive?
More than 30 profiles?

You can see how many in there:
D:/Archivos de Programa/Simucube 2020 10/profiles_autobackup.ini

1 Like

Hi @calandre32

I saw your support request through DSD. We will get you sorted, please answer to the email we sent.

There is a possibility that a simple inspection procedure that includes opening up the back cover of the device can fix the issue.

@Alfye20 The issue is no way related to amount of profiles.

2 Likes