FFB suddenly loss

Jason_Him · 29 July 2018 14:35

Hi, I found that my wheel will suddenly loss FFB while driving.
What I have set is 540 turning degree in SimuCube, I found that when I am in the corner, the car will suddenly go wide, like the turning degree back to 900 something, then gain back to 540, the car will snap back into the corner.

I don’t see any problem in device manager, I have this issue on 0.98 / 0.9.1 / latest version configuration tool, so I think it is not the problem about the tools. PC running with win7 64bit

Does anyone experienced this before ?

Thank you

Mika · 29 July 2018 14:59

supply a debug log from 0.10.4, there are events there that would show any reasons.

Jason_Him · 29 July 2018 16:01

Ok.
And it is only happen on R3E, no problem on AC and RF2

16sth · 29 July 2018 23:04

Maybe … Raceroom Racing Experience with SimuCube Open Beta .0.83

Loukas_Bourdas · 30 July 2018 09:48

When you loose the ffb dont press the button to cpear the faults. Enter granity and see what the fault is

Mika · 30 July 2018 10:17

Also the SimuCUBE Configuration Tool 0.10.4 will show the Fault Location ID right in the UI, as well as the fault reason for most common faults.

Jason_Him · 30 July 2018 10:31

SimuCUBE Boot : 0
SimuCUBE Boot : 10
SimuCUBE Boot : 4
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
event 90 : 3634
Read MMC value from Drive : 12000
Read Motor Resistance value from Drive : 2333
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
event 92 : 3796
event 93 : 3852
event 93 : 6294
event 93 : 5241
event 93 : 1531
event 93 : -2536
event 93 : -4482
event 93 : -3303
event 93 : 411
event 93 : 4441
event 93 : 6383
event 93 : 5252
event 93 : 1576
event 93 : -2465
event 93 : -4464
event 93 : -3117
event 93 : 255
event 93 : 3484
event 93 : 4805
event 93 : 3900
event 93 : 1549
event 93 : -605
event 93 : -1373
event 93 : -763
event 93 : 579
event 93 : 1569
event 93 : 1775
event 93 : 1357
event 93 : 979
event 93 : 948
event 93 : 949
event 93 : 949
event 93 : 949
event 93 : 949
event 93 : 11
event 94 : 12
event 95 : 12
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 Profile number : 3
Command: Request Profile data is for 55 byte set index : 0
Command: Request Profile number : 3
Command: Request Profile data is for 55 byte set index : 1
Command: Request Profile number : 4
Command: Request Profile data is for 55 byte set index : 0
Command: Request Profile number : 4
Command: Request Profile data is for 55 byte set index : 1
Command: Request Profile number : 5
Command: Request Profile data is for 55 byte set index : 0
Command: Request Profile number : 5
Command: Request Profile data is for 55 byte set index : 1
Command: Request hardware settings : 0
Command: Request analog input settings : 0
Command: Activate profile number : 3
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Event log download request : 0
Command: Start event logging : 0
Command: Activate profile number : 2
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 Profile number : 3
Command: Request Profile data is for 55 byte set index : 0
Command: Request Profile number : 3
Command: Request Profile data is for 55 byte set index : 1
Command: Request Profile number : 4
Command: Request Profile data is for 55 byte set index : 0
Command: Request Profile number : 4
Command: Request Profile data is for 55 byte set index : 1
Command: Request Profile number : 5
Command: Request Profile data is for 55 byte set index : 0
Command: Request Profile number : 5
Command: Request Profile data is for 55 byte set index : 1
Command: Request hardware settings : 0
Command: Request analog input settings : 0
Command: Event log download request : 0

Mika · 30 July 2018 10:39

Yep, that looks like just standard power-up… you will have to give the log when the fault has happened.

Jason_Him · 30 July 2018 10:45

I play the game with issues happened so many times, so I quit the game and get this log

Mika · 30 July 2018 11:01

ah, OK. There are no events in the log related to any USB issues or communications with IONI drive. Lets think what other issues could cause something like this.

Jason_Him · 30 July 2018 11:54

Will it be about source power supply issue ? Let say not enough electrcity

Jason_Him · 30 July 2018 11:56

Addition, I am using latest firmware and configuration tools

Mika · 30 July 2018 12:04

What kind of PSU do you have? Any power supply issue would usually give the Undervoltage Fault first. Is your kit a DIY kit?

Loukas_Bourdas · 30 July 2018 12:35

You are using the small mige? Ioni pro hc? There must be something different that triggers the problem only on that game. Could you upload your drc just in case?

Jason_Him · 30 July 2018 13:01

It is a 480W psu, small mige kit from Tomo

Jason_Him · 30 July 2018 13:03

Yes, amall mige with ioni pro hc
Where can I get that DrC file ?

Mika · 30 July 2018 13:10

There is nothing in drc files that could cause this without a clear fault indicator in the Configuration Tool.

Loukas_Bourdas · 30 July 2018 13:28

That’s why i wrote “just in case”. You can never be so sure. Anyway , you connect simucube straight to pc or do you use any hub? What motherboard? Usb 2.0 or 3.0 ?

Jason_Him · 30 July 2018 14:16

It is directly to motherboard with both usb 3.0

Actually it is the other set of my dd, I have another set exactly the same at home, whoch connect to PC through power usb hub, also with latest config tool and firmware, running with R3E without any issue

Loukas_Bourdas · 30 July 2018 14:43

If the usb 3.0 isn’t native and is through an asmedia controller , connect it to a native usb 2.0 port. The drc is basically the settings you have in granity. Either take photos of all your settings in granity or just save the drc through granity. Simracingbay most of the times uses sdr480 wich should be more than enough. You are using same settings in raceroom for both your rigs?