Simucube 2 - Waiting for drive to get ready

Seems today after not changing anything that my Simucube 2 Sport has decided to become unresponsive.

Running Simucube 2 Sport and True Drive v1.0.10

Operating mode is stuck on “Waiting for drive to get ready” and the emergency stop isnt registering as toggling, its stuck on E-Stop is PRESSED.

Have turned e-stop on and off many time, turned the wheel on off, restarting pc and trying a different USB to no availability.

Any ideas?

1 Like

We have had a report that opening the True Drive software before starting the device can make this happen. Can you try to start the device without the software being open, to see if it makes a difference?

1 Like

Still the same thing unfortunately.

My suspicion would be a fault within the estop button. Please contact your reseller for further analysis.

You can also click the “Download Debug Event Log” button after this happens (it is on the last tab in True Drive software) and paste the content here. There might be a hint for us to see what is happening inside the device.

All of it is just “Drive init stage 4, phasing, current position : 3202834” with no sign of mention of the estop.
Will get in touch with my reseller, thanks.

You might want to do the debug log immediately when starting the device to get a climpse on what happens near the very beginning of the log, before it goes to the Drive Init Stage 4.

Full log from starting, don’t think it answers too much though

Timestamp : 2051

Wireless: State change : 2

Simucube Boot : 1

Simucube Boot : 0

Simucube Boot : 10

Flash settings data loaded : 0

First-time drive initialization : 0

Initial config has been previously performed. Initializing Drive. : 0

State: Initializing Drive : 0

Drive Firmware update : 0

Drive firmware updated successfully : 0

Command: Request profile number : 0

Command: Request profile name for profile : 0

Command: Request profile byte data for profile : 0

Command: Request profile number : 1

Command: Request profile name for profile : 1

Command: Request profile byte data for profile : 1

Command: Request profile number : 2

Command: Request profile name for profile : 2

Command: Request profile byte data for profile : 2

Command: Request profile number : 3

Command: Request profile name for profile : 3

Command: Request profile byte data for profile : 3

Command: Request hardware settings : 0

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 0

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 1

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 2

Timestamp : 3809

Wireless: State change : 3

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 3

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 4

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 5

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 6

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 7

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 8

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 9

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 10

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 11

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 12

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 13

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 14

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 15

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 16

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 17

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 18

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 19

Command: Request analog input settings : 0

Command: Request bytedata for analog profile : 20

Command: Set calibrated analog axis mode : 0

Drive init stage 1, position : 3343856

Read MMC value from Drive : 15500

Read Motor Resistance value from Drive : 1200

Read CPR from Drive : 4194304

Read Drive Version ID from drive : 40000

Simucube 2 Serial Number : 451

SM Watchdog disabled successfully : 0

Successfully applied DRC data to Drive : 0

Read MMC value from Drive : 15500

Read Motor Resistance value from Drive : 1200

Read CPR from Drive : 4194304

Read Drive Version ID from drive : 40000

Simucube 2 Serial Number : 451

Waiting for servo to be ready : 0

Drive init stage 3, position after faults cleared : 3343860

Drive init stage 4, phasing, current position : 3343856

Drive init stage 4, phasing, current position : 3343860

Drive init stage 4, phasing, current position : 3343860

Drive init stage 4, phasing, current position : 3343860

Drive init stage 4, phasing, current position : 3343860

Drive init stage 4, phasing, current position : 3343856

Drive init stage 4, phasing, current position : 3343860

Drive init stage 4, phasing, current position : 3343860

Drive init stage 4, phasing, current position : 3343861

Drive init stage 4, phasing, current position : 3343859

Command: Event log download request : 0

Drive init stage 4, phasing, current position : 3343859

Command: Event log download request : 0

Brett from HRS express posted me a replacement button and all is sorted - so must of been dead hardware on the emergency stop. Great service from him as usual :slight_smile:

4 Likes

Great to know it is sorted now! I was a bit worried as well, as somehow it did manage to get past the “check if e-stop is up” phase, pointing towards anything from e-stop fault to something more serious

1 Like

@Matthew_Allen Can you tell us the serial number of the product (on a sticker on the back of the device). We want to check if there were any failure indicators or difficulties for the unit when it passed the production programmer&tester at the factory.

Serial number is 451

1 Like

Who is this I am having the same exact problem how could I get in touch with someone I bought mine off eBay would it still be possible ?

Write a support ticket via simucube.com - thats the official support channel.