New buffered motion stream clock synchronization method. Reduces average time difference in buffered multi-axis interpolation under 50 ns.
New motor regeneration method in SimuCUBE mode. Reduces heating of regenerative resistor on SimuCUBE.
Improved effectiveness of encoder signal crosstalk filtering when Torque bandwidth limit TBW is set to 680 Hz or less. This may reduce motor noise in high inductance motors with incremental encoders.
For SimpleMotion developers
Added support for new SimpleMotion CB1_FORCE_ENABLE flag to ignore missing physical ENABLE signal to the drive
Drive now ignores all writes to SMP_CONTROL_BITS2 variable
Fixes
Fixed calculation of power used in Maximum peak power MPP thus improving accuracy of the maximum peak power feature.
Update: scroll down to see discussion about later 1.6.90 version.
Update firmware seems great less overall motor sound its quite a bit quieter overall. and now the weird popping noise and ācross talkā is gone at tbw 1000+ 4700 Unlimited ect!
Also the motor feels smoother/ same goās for the ffb
Did 50 laps Brands Hatch with the iRacing Nissan GTP and the new firmware feels really good. I couldnāt stop driving. I used TBW 680 before and now Unlimited with recon 3. Noise (sound) from the motor is reduced which is nice. You can still feel some noise (ffb) in the wheel when slaloming on the straight but thatās probably down to iRacings poor 60 hz force feedback.
Iāve just run with the new 1.6.30 but have 1 or 2 issues, Iām running the Simtronics encoder @ 3.7mil. Iāve found the FFb drops for a split second then returns but the biggest problem was during a race were I lost FFb & axis direction and a grinding sorta noise from the motor and grainy feel on the wheel, I power cycled the wheel and all returned just fine but in the next session I loose ffb & direction again.
Iāve reverted back to 1.6.1 and all my isseues disappear but I also find the Ffb feels better with a fuller feel while driving compared to 1.60.30
Hi, agree with you that the FFB feels better with a fuller feel while driving with the 1.6.1 when using an earlier firmware, i feel less understeer and its more easier to catch slides with older firmware 1.6.0. Tested on GT3 PC2 with few cars on Fuji and other a couple of other laser scanned tracks. However my wheel stopped working after checking the two versions trying to resolve this, although the new fw seems to have eliminated much of the noise at all frequency ranges for me, which is great.
I tried the new firmware briefly last night. It seems their is some sandyness or grainyness, where nefore there was none.
But I will have to test some more
For me the new firmware is an early Christmas present.
Since I replaced my 10k encoder with 40k version and setting [TBW] above 680 my motor were hissing as if somebody was deflating a tire right in front of me.
I could reduce this noise to an acceptable level by lowering [ML] an [MR] in Granity, but I never got rid of the grainy noise/feeling.
Now, with [ML] and [MR] measured and set (very close the original motor spec) and even with [TBW] set to Unlimited the motor is dead silent and there is no more grainy noise/feeling.
I am happy with this new firmware, thanks @Tero and @Mika
Just upgraded the Ioni firmware to my small Migeā¦ I can now run unlimited TBW, before I could only go up to 680 before inductance grinding noises started. The wheel just feels smoother,as a direct result I have reduced the reconstruction filter from 5 to 3 and have upped the ffb 10-20% ( from my own preference ). I hammered round road america for an hour in the Porsche in iRacing, played with the settings and did not have any glitches.
I had considered getting a uprated encoderā¦ not any more, canāt see the point after this update.
What can I say other than a big āthank youā to Mika and Teroā¦ They keep making the OSW better and better.
Can you report whether there were any faults in the IONI when viewed via Granity, when you lost FFB totally? As this is a beta of the IONI firmware, there could be some issues there that cause this, and we really would like to get them fixed before bundling this to SimuCUBE firmware.
Will reinstall the beta and attempt to make it fault againā¦ It happened during a race so I powercycled to get going again so no idea of fault codes, so to be clear you would like Simucube error code on the UIā¦ anywhere else ?
I would like a screenshot of the Granity Testing -tab if possible. Also the SimuCUBE configuration tool will show a reason for the wheel fault in the top of the screen.
also, cycling e-stop will clear all faults in SimuCUBE mode on the IONI drive. Can you test if that helps?
Remember that Assetto and other titles offer much higher resolution than say iRacing (60hz), and with DD becoming more common (Fanatecās upcoming launch), game devs are going to start working on providing higher resolution.
Software can use the SinCos/Biss encoders much higher capabilities to create better feel.
So, at least for me I think it was a worthwhile investment to future guard my OSW - I got the $150 option from SimRacingBay and can feel the differences in AC.
