Thanks, that worked. I did that with “STM32 BOOTLOADER” under the “other devices” list and it worked. The game controller is recognized in the windows controllers section and responds when I turn the steering wheel left and right.
Moving on to part 3 of setup.
Actually it is explained in the beta SimuCUBE Firmware User Guide.
https://granitedevices.com/wiki/SimuCUBE_Firmware_User_Guide
OK, thanks. It’s a little confusing because there is a step by step guide for setting up and installing the simucube so I therefore followed that…I had no idea about the page you referred me to.
In Granity, I’m assuming we’re supposed to use “SimpleMotion USB (FT230X Basic UART)”. Or “SimpleMotion serial port (COM5)?” Both options work and successfully detect the device…
I think the latest Granity version has direct communication to the FT230X uart chip (the first option), and the Serial Com port is the “old” version of the communication method. You can use either one.
And yeah, we haven’t really integrated the new SimuCUBE firmware installation instructions to the main wiki. That is on list of things to do…
OK. I just realized I may have been doing this incorrectly. I would like to use the FFB settings program that allows me to use the new simucube features such as the reconstruction filter. I already converted the hex file and installed the mmos firmware according to the following page: https://granitedevices.com/wiki/Installing_MMos_firmware_into_SimuCUBE. Should I ignore the rest of the SimuCUBE Install Guide (parts 3, 4, and 5 https://granitedevices.com/wiki/SimuCUBE_install_guide) and instead follow the directions in the simucube firmware user guide you linked me to above?
When setting up my motor settings in Granity, are there any settings that differ between using my old setup (Ionicube 1x in simucube mode) and my new setup which is a true simucube setup? Or do I just use the same exact DRC file with no changes?
Hi,
You will then want to install the SimuCUBE Firmware; follow the instructions in the SimuCUBE Firmware User Guide. You don’t need to install MMOS first.
Same settings can be used. You can, however, check that Bus Address Offset (SMO) parameter is 0, and that there is sufficient voltage (1.5 V, for example) between the HV bus voltage and the FOV Over Voltage Limit. Otherwise, same settings should be OK to use.
If you plan on using exactly the existing IONI Pro or Pro HC you already have, then it is not required to upload any new DRC files.
Hi. Thanks for all the help so far.
I’m trying to install/update the simucube firmware for the first time but it keeps failing at the verifying stage. Any ideas? I went into DFU mode beforehand to install the “simucube-bootloader.dfu,” then powered simucube off, waited 1 minute, powered on (not in dfu mode anymore), windows driver installed upon powering on, opened “SimuCUBE Configuration Tool.exe”, clicked hardware tab and went through the wizard which successfully finds the firmware and the install completes the “201264 bytes sent” part, goes to verifying, then goes to fail.
Should I have the X4 mini USB plugged in maybe? I still only have the X3 from when I was using DfuSeDemo to install the simucube bootloader. I don’t think DfuSeDemo detects a boot device (upper-left drop-down menu) if both X3 and X4 mini USBs are plugged.
This can be caused by bad usb connection.
Which motherboard do you have, and which port on that motherboard are you using?
I’m currently using the MSI X99A XPower Gaming Titanium motherboard. I have it plugged into one of the USB 3.0 or 3.1 ports. It’s a standard one just labelled Gen1, not Gen1 Type-A or Gen1 Type-C like some other ports on the board are.
I’m going to try what look like USB 2.0 ports.
When I switch USB port and power simucube back up, can I attempt to try again right away with firmware install or do I need to open simucube-bootloader.dfu from DfuSeDemo and do that part again first?
EDIT: Other USB port worked great (and I didn’t do the simucube-bootloader.dfu from DfuSeDemo part again).
Thanks, it would appear that motherboard has the very problematic Asmedia USB3 chipset:
ASMedia® ASM1142 Chipset
• VIA® VL805 Chipset
• Intel® X99 Chipset
SimuCUBE is by far not the only device that has problems with Asmedia chip.
Thanks, it’s all done and working.
i have some questions regarding DRC files. Instead of using my previous one, I used the motor file from Granity’s motor page. I then changed some values like current (for higher torque) and PSU wattage (because I am using a PSP-600-48 600w PSU).
Can some please make sure my DRC pages look OK?
Also, when comparing to my old Ollie IONICUBE 1x setup (setup for simucube mode in Granity), there are a few differences:
IONICUBE 1x —> Simucube:
BDD Dynamic braking deceleration:
1 —> 16
MTC Thermal time constant:
1500 —> 500
MPP Peak power limit:
0 (power limit not used) —> 590
FOC Over current tolerance:
Maxiumum —> Low
FOV Over voltage fault threshold:
49.50 —> 50.00
FUV Under voltage fault threshold:
30.00 —> 20.00
FEV Over speed fault:
100 (6.25 revs/s) —> 140 (8.75 revs/s)
You definitively should put Over Current Tolerance to Maximum. I use 1500 as MTC. FOV depends on you HV bus voltage, please put it around 49.5 or 50 V if your HV bus is around 48.0 V.
My HV bus voltage is at a steady 48.5v is that 0.5v difference OK?
Does dynamic brake deceleration at 16 instead of 1 make any game/FFB difference?
The testing page with wheel resting at desktop currently shows “analog 1 in” at 1.59v, my Ollie IONICUBE 1x kit was at -0.06v. Is the current value OK?
I think at 48.5 V you should put it to 50.0 V. There is a check here that will prevent the IONI from initializing, if these are too close together. The exact specification is to have at least 2% safety headroom, which would make it 49.47 V on your system. I would add some more margin for voltage variations and put it 50.0 V.
IoniCUBE and SimuCUBE are different, I have never taken any interest in those analog in signals, so I suspect your signal levels are ok.
Fantastic. Thank you.
Do you know if the dynamic brake deceleration at 16 instead of 1 makes any game/FFB difference?
Please check your PM in the next day or two 
They don’t make any difference, that feature is only used when drive is being driven and a fault develops. It alters the behavior on motion stop.
Hello
Can you help me i have problem.
I was using mmos till now and installed Simucube all went fine, but when it was all done Encoder count per revolution was 0 and wheel is unusable.
Config is: ioni pro hc 25a, large midge 40000cpr
Do i hve to go to “enabel Ioni USB configuration” and do something there?
Hi guys!
A report came to me telling that the fresh install is again broken in 0.9.4. You can wait for tomorrow morning for the fix, or put SimuCUBE to Firmware update mode via the firmware update wizard, cancel when it says that simucube found in firmware update mode, and then use the 0.9.3 zip to downgrade to that. Then run the wizard using that version, verify correct operation, and then update to 0.9.4.
My sincere apologies for the inconcenience!
