i recently switched from MMOS to Simucube 0.9.7 for my simracingbay osw setup.
Servo Motor: MiGE 130ST-M15015 30Nm 10000ppr (40000cpr)
PSU: Mean Well 480W/720W peak (Noiseless) 30Nm
Servo drive: Ioni Pro HC (25A)
now if i turn the wheel, in game or on the desktop there is a small Beep and in that very moment of the beep there is no feedback from the wheel.
in that moment in the Advanced Tab in the SimuCube Configuration Tool the SMBus error counter is rising.
it occures even more frequent if i increase the force reconstruction filter setting.
been testing around a bit, switched to 0.9.8 and got a hint whats wrong. 0.97 did just show motor fault:
0.9.8 shows “motor fault: over current…” - been using the same settings for the past 1,5 years in mmos without troubles.
searches the web and found a suggestion to set the FOC Setting to Maxium (using very high normaly) so i tried to set the FOC setting in Granity to Maximum - which made the situation better but it still ocures frequently. 11 Times in 3 N24 Laps.
SimuCUBE Boot : 0
Flash settings data loaded : 0
Initial config has been previously performed. Initializing Drive. : 0
State: Initializing Drive : 0
First-time drive initialization : 0
SMBus baudrate initialized successfully : 0
Read MMC value from Drive : 19000
Read Motor Resistance value from Drive : 1247
Read CPR from Drive : 40000
Read Drive Version ID from drive : 11201
SM Watchdog disabled successfully : 0
Waiting for faults to clear : 0
Waiting for servo to be ready : 0
SMBus baudrate initialized successfully : 0
State: Drive initialization was successful : 0
SM Watchdog enabled successfully : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 1
Command: Request hardware settings : 0
Command: Request analog input settings : 0
Command: Set hardware settings data : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 0
Command: Set Profile data is for 55 byte set index : 0
Command: Set profile settings for profile : 0
Command: Set Profile data is for 55 byte set index : 1
Command: Set profile settings for profile : 1
Command: Set Profile data is for 55 byte set index : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 1
Command: Set Profile data is for 55 byte set index : 1
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 2
Command: Set Profile data is for 55 byte set index : 0
Command: Set profile settings for profile : 2
Command: Set Profile data is for 55 byte set index : 1
Command: Set hardware settings data : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 0
Command: Set Profile data is for 55 byte set index : 0
Command: Set profile settings for profile : 0
Command: Set Profile data is for 55 byte set index : 1
Command: Set profile settings for profile : 1
Command: Set Profile data is for 55 byte set index : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 1
Command: Set Profile data is for 55 byte set index : 1
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set profile settings for profile : 2
Command: Set Profile data is for 55 byte set index : 0
Command: Set profile settings for profile : 2
Command: Set Profile data is for 55 byte set index : 1
Command: Set hardware settings data : 0
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Set analog input settings data : 0
State: Saving settings to flash : 0
SM Watchdog disabled successfully : 0
SM Watchdog enabled successfully : 0
State: Operational : 0
Command: Set settings not changed : 0
SMBus baudrate initialized successfully : 0
SMBus baudrate initialized successfully : 0
SMBus baudrate initialized successfully : 0
SMBus baudrate initialized successfully : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 1
Command: Set calibrated analog axis mode : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 1
Command: Request hardware settings : 0
Command: Request analog input settings : 0
SMBus baudrate initialized successfully : 0
SMBus baudrate initialized successfully : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 1
Command: Set calibrated analog axis mode : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 1
Command: Request hardware settings : 0
Command: Request analog input settings : 0
SMBus baudrate initialized successfully : 0
SMBus baudrate initialized successfully : 0
SMBus baudrate initialized successfully : 0
SMBus baudrate initialized successfully : 0
SMBus baudrate initialized successfully : 0
Command: Event log download request : 0
You should put Over Current Tolerance to Maximum. You can also try to raise the Over Voltage Fault Threshold a bit, like, 50.0 or even 51.0 V.
You are not the first one that has only recently reported faults with the 30 Nm Mige motor. Can you check what is the fault location ID in the Granity Testing tab when this has just occurred?
**Actual torque exceeded target torque indicating that torque controller might have became unstable. **
Check parameters MR and ML which may cause instability or overshooting of torque. If unsure whether they are correct, see Tuning torque controller. If no help, then increase Over current toleranceFOC. Ultimately try setting FOC to Maximum.
i will try to raise the threshold and keep yopu updated
also when in Granity have Granity set your MR and ML by using the auto detection button… It could be tat your servo is not liking whatever numbers were set previously.
Hello guys,
I am new around here as I recently purchased a used simucube osw kit with small mige. Currently it has the latest firmware installed and it works well to the point I get some random disconnects and other weird behaviour like yesterday while lapping around Hungaroring in single player ACC session the wheel tried to rip off my wrists on the main straight. The SMbus error counter keeps increasing even while I leave everything idle. I tried to identify the problem myself, but I struggle to do so. The previous owner claims that he had no problems. I must say that my power outlets are not properly grounded as I live in a building with two wire electrical installation. I have followed the guide on doing proper grounding and I have a ground wire running from the wheel rim to the quick release, then from the motor mount to the cooler master case and PC case. My rig is wooden by the way if that info matters.
Would you please help me identify what the problem is and why the simucube keeps disconnecting?
What information would you want me to peovide?
I am currently writing from my phone, but as soon as anyone here engages to help I will power on the rig and give all the info needed.
I am currently so frustrated from the disconnects that I don’t even want to go near the rig.
Forgot to mention that I tried 3 different usb cables and all USB ports on my mainboard, I even tried connecting ONLY the simucube, having even the mouse and keyboard unplugged to check if any other usb device is doing any conflicts.
EDIT:
Sorry to duplicate my potential fix, but I wrote in two different threads (SimRacingBay simucube 1 OSW keeps disconnecting randomly), so I am gonna leave this here for anyone else having similar issues. I hope it helps someone!
I think I fixed my problem. I still don’t want to celebrate, but this is the first time I had the wheel connected for around 30 minutes now without any SMBus error count - it still shows 0. Previously I had like 50 errors for the first 5 minutes of powering on the simucube.
I then went and made a quick practice session around Hungaroring in ACC with 100 FFB (12 amps) in Simucube Configuration Tool and 40% gain in the game - it was perfect. No errors, no disconnects nothing!
What I did:
I enabled Ioni usb configuration, started Granity and I did the coil test and the values that the software suggested after making the test were a bit different from what I had. I changed to the suggested values but I also increased FOV from 49.5 to 50.5. I also tried a different USB port once more. Now I am not sure what did the job, but I am very happy.
Just to be sure - would you guys please confirm that a value of 50.5 FOV is safe ? I could possibly go back to 49.5 and see if it still works, but I don’t want to change anything now when it works if not needed.
50.5 V FOV is safe to use. There is still plenty of margin before hard limits, enabling the voltage dissipation to work correctly.
Most likely all sorts of grounding and ground loop issues are the root cause to the issue. Simucube devices are designed to work when properly grounded.
Yes, Mika, thanks for your input. I know simucube is very sensitive to grounding, but I still can not relate my “success” to anything ground related. I mean I did the grounding procedure two weeks ago and did not change anything regarding grounding, but I did software changes and to be honest I changed the USB port I was using. Now I am afraid to go back to previous USB port because I just don’t want to risk it. I stick to “If it works, don’t change anything!” moto
Sorry to reply under my own post but… I knew I had to wait before I call it a win…
Yesterday I had so much fun using the simucube for hours without a single disconnect or anything.
I powered off the PC, the simucube and everything and I haven’t changed anything. Today when I started the rig agian - same old story. The error counter got to 40 for 20 sec. I have no idea what causes the problem as I haven’t attached or detached any peripherals, additional hardware or whatever. No changes to software etc. The only thing that I can think of is the order in which I power on things, but I don’t remember how I did it yesterday to try and do it the same way.
EDIT:
I unplugged the simucube usb cable from the PC, plugged it back in and then I turned it off and on again with the power switch above the power cord and now I get no errors. Any idea what may be causing this problem ?
I have 3 arduinos, usb headset, mouse and keyboard attached via USB.
