Simucube 2 Pro — Rotates on startup and not functioning properly

2 Months ago I got the Simucube 2 Pro and it was working fine. Since today I got the following problem(s):

— When enabling High Torque the SC2 moves left and right on it’s own.
— Software is glitching and crashing in a strange way and can’t read the rotation of the SC2 properly
— Sometimes it doesn’t detect the SC2 when power on

I tried upgrading and downgrading the software and rebooting the SC2 Pro and deleting profiles but nothing seems to help.

Is there something else I can do to fix this problem or do I need to contact GPerformance (where I purchased from) to get a replacement or something?

Hi,

  1. Create a new profile, and make it as default profile. Then save settings to Simucube. Seems like the default profile has somehow gotten corrupted.
  2. Power-cycle the device. Other than the left-right movement, it should work OK.
  3. hit CTRL-E in True Drive to re-enable the absolute encoder mode to not have the movement at power-on.

Hi Mika,

Thank you so much for the quick reply! this solved the problems and the Simucube works as if brand new!

Kind regards and have a nice weekend

Mika, is that Ctrl-E shortcut available on all units?
What does it do exactly, and are there any concerns to have it easily accesible in user facing app where it can be accidentally triggered?
And if it’s a feature, should it be documented in User’s Guide.
Thanks

Its a service feature, that disables absolute encoder, tells the servo drive to reboot (it gets new calibration value for the encoder), and saves that calibration value to be used again by enabling absolute encoder mode, and saves servo drive settings and then commands servo drive to again reboot.

Its not documented because its a service feature and that users would start to use it for no reason, trying to somehow optimize their encoder calibration which is not of any use if there is no real reason to do it.

Just hitting the key combination does not actually initiate anything,though. It presents a menu for doing it.

1 Like

This kind of users probably never read the manuals anyway.
Having it in “Troubleshooting Instruction” section could have saved OP trouble of waiting for someone from GD to respond with the solution and let him unblock himself.
If not User’s Manual at least in Service Manuals, along with other missing things like FW downgrade instruction.

3 Likes

That would loose us the ability to track frequency on any issues with the encoders - loss of calibration, etc. It is a support tool so that we do not have to work with even more complex debug interface via remote support session.

If it ever becomes a “popular issue” that users would need help with, then we would document it. For support, we have gotten less than a handful of support requests where there has been help from this feature. Mainly, we use it ourselves to get development firmwares iniatialized to proper state at the office :slight_smile:

2 Likes