Looking forward to the new FW. 
Mika and Tero,
There have been several guys lately having issues having the Simucube plugged into USB3.0 ports. After moving to USB2.0 things are fine.
Is there any way in the new firmware to make the Simucube more compatible with USB3.0?
I would guess at some point we will no longer see USB2.0 ports on PC motherboards anymore.
Talk later,
Joe
Our firmware is running currently on an USB3.0 port. However, its only one computer (so far) and not very lengthy test sessions, so issues could still arise. The hardware (microcontroller) only supports USB2.0, so there’s the limitation. Device descriptors and that kind of stuff should be backwards compatible, so there shouldn’t be anything there either. So, there is not much we can do.
My personal experience of USB3 has varied. I found that many wireless 2.4 GHz peripherals, such as Logitech mice and keyboards, will not function at USB3 ports, as USB3 emits just a tiny bit too much RF interference on that band. I had to move my cordless receivers away from the computer on USB extension cables to get my mouse and keyboard (Logitech Nano and Logitech Unifying receivers) to work properly.
Mika thanks for the response.
Another question for you.
Is the driver for the SMV2 portion of the simucube slightly different than the SMV2 used on the IONI1x?
The reason I ask is in the last few months I have talked to a few previous Argon users that switched to Simucube and had to install the ftdi chip drivers again.
Thanks,
Joe
SimuCUBE has a bit different and newer version of FTDI’s USB serial chip than what is used in SMV2 adapters so the older installed drivers might not have had support for it, hence the need to install the latest FTDI drivers.
1 Like
I currently use my SimuCube (both ports) connected via USB3.0 as my motherboard does not have any 2.0 ports. I don’t believe I’ve had any issues, but should I put a 2.0 extension cable inline to force 2.0 mode?
No, as the microcontroller hardware only supports USB2.0 anyway, so it won’t make any difference. Its already using 2.0 mode.
Using a USB2.0 hub in between can help if there is any incompatibility issues (bad motherboard drivers, etc.).
Perfect. Thank you, Mika.
I thought a periodic update in this thread might be a good idea. Please keep your comments and questions in the Discussion thread.
Update of May 25, 2017
Completed things:
Communication methods to/from a configuration tool have been designed.
Internal state machine on the firmware is now working.
Configuration tool on for PC is being implemented.
Todo-list:
Complete the configuration tool so that it at least minimally works.
Implement configuration of Ioni drive directly from the configuration tool.
Implement a few effects other than the constant force as required by iRacing. Goal: At least rFactor should be working before the first beta release.
After the first beta:
Implement buttons reading with debouncing.
Fix analog inputs to work correctly.
4 Likes
Great update, kiitos hyvin paljon!
Cheers,
Beano
Glad to have found this thread! I had read about the proposed Simucube replacement for MMos to bring more versatility and hopefully better plug and play compatibility with many SIM titles that to date still don’t feel great.
iRacing seems to work really well out of the box (using Jason Jodarski’s settings), but those same settings don’t work well with AC, RRE, Rfactor2 etc.
I’m excited to see new developments with this new software and would love to think that through the community we could help create something similar to SC4 that has many different profiles for getting setup quickly with all the many titles available. Is it safe to say that at least for now the potential offer of integrating SC4 with Simucube is ‘off the table’ with the impending launch of the Accuforce V2?
I rarely touch Granity and hope that this new software offers an easy to use interface that makes it a breeze to switch between SIMs without every having to mess around inside Granity.
I would be happy to test out early versions - I like to tinker!
Exciting times for Simucube! I still believe that it’s the best option for SIM racing by a very large margin. It just needs to incorporate the plug and play functionality across the main racing titles. If that can be achieved there is no reason why it can’t crush any competition out there as the physical hardware setup is almost plug and play with the guides for setting index point from people like Jason. I can’t thank him enough for this - my Simucube starts up without issue, always indexed and always read to go.
Just the software part needed.
Cheers!
Please replace that lines in your .rcs of RaceRoom and try it again, i think that will help you.
You can backup you own file before or make a new and use them at the same time.
FFB Rumble Pad=“0” // Type of FFB controller: 0=wheel, joystick etc with force feedback, 1 = pad with rumble motor
FFB Gain=“1.0” // Strength of Force Feedback effects. Range 0.0 to 1.0.
FFB Min Force=“0.0” // Minumum force, from 0.0 to 1.0
FFB Min Force Linear Percentage=“0.01” // Minumum force linear percentage
FFB Throttle FX on steer axis=“1” // 0 = Throttle effects on throttle axis, 1 = throttle effects on steering axis.
FFB Brake FX on steer axis=“1” // 0 = Brake effects on brake axis, 1 = brake effects on steering axis.
FFB stationary friction=“0.0” // Amount of friction applied to the steering wheel when vehicle is stationary
FFB stationary friction speed=“2.7780001” // Below this speed the stationary friction starts to be applied, in m/s
FFB steer vibe freq mult=“0.0” // Controls frequency of steering vibration. Recommended: 0.5 to 1.0, 0.0 disables steering vibration.
FFB steer vibe zero magnitude=“0.0” // Magnitude of steering vibration at 0mph (reference point).
FFB steer vibe slope=“0.0” // Slope of line defining magnitude as a function of frequency (used with FFB steer vibe zero magnitude).
FFB steer vibe wave type=“0” // Type of wave to use for vibe: 0=Sine, 1=Square, 2=Triangle, 3=Sawtooth up, 4=Sawtooth down.
FFB steer force average weight=“1.0” // How much weight is given to new steering force calculations each frame (0.01 - 1.0). Lower values will smooth out the steering force, but will also add latency.
FFB steer force exponent=“1.0” // Steering force output “sensitivity”. Range 0.0 to infinity. 0.0 to 1.0 = higher sensitivity, greater than 1.0 = lower sensitivity.
FFB steer force input max=“11500.0” // Recommended: 11500 (-11500 if controller pulls in the wrong direction).
FFB steer force output max=“0.03” // Maximum force output of steering force, recommendation 0.8 to 2.0
FFB steer force grip weight=“1.0” // Range 0.0 to 1.0, recommended: 0.4 to 0.9. How much weight is given to tire grip when calculating steering force.
FFB steer force front grip exponent=“0.0” // Range 0.0 to infinity, recommended: around 1.0. Exponent applied to grip weight.
FFB steer force rear grip exponent=“0.0” // Range 0.0 to infinity, recommended: around 1.0. Exponent applied to rear grip loss weight.
FFB steer damper coefficient=“0.0” // Coefficient to use for steering damper. Range: -1.0 to 1.0
FFB steer damper saturation=“0.0” // Saturation value to use for steering damper. Range: 0 - 1.0
FFB steer force balance mode=“0” // Mode for how to add the steering forces together (lateral, load and diff). Acceptable values: 0 = lat + load + diff, 1 = sqrt(lat^2 + load^2 + diff^2), 2 = sqrt(lat^2 + load^2) + diff, 3 = sqrt(lat^2 + (load + diff)^2), 4 = sqrt((lat + load)^2 + diff^2)
FFB steer load multiplier=“0.0” // Multiplier for vertical load on front tires. Range: 0 - infinity
FFB steer lateral multiplier=“10.0” // Multiplier for lateral forces. Range: 0 - infinity
FFB steer rack factor=“0.3” // How much of the lateral forces comes from steering rack. Range: 0 - 1.0
FFB steer load change exponent=“1.0” // Exponent for the change in load on front tires. Range: 0 - infinity
FFB steer load change breakpoint=“1.0” // Breakpoint (value that will not be changed) for the exponent on the change in load on front tires. Range: 0 - infinity
FFB steer spring coefficient=“0.0” // Coefficient for steering spring. Range: 0.0 - 1.0
FFB throttle vibe freq mult=“0.0” // Scales actual engine frequency to force FFB vibration frequency. Suggested range: 0.10 to 0.50
FFB throttle vibe zero magnitude=“0.0” // Magnitude of engine vibration at 0rpm (reference point).
FFB throttle vibe slope=“0.0” // Slope of line defining magnitude as a function of frequency (used with FFB throttle vibe zero magnitude).
FFB throttle vibe wave type=“0” // Type of wave to use for vibe: 0=Sine, 1=Square, 2=Triangle, 3=Sawtooth up, 4=Sawtooth down.
FFB rumble strip magnitude=“0.0” // How strong the rumble strip rumble is. Range 0.0 to 1.0, 0.0 disables effect.
FFB rumble strip freq mult=“0.0” // Rumble stip frequency multiplier 1.0 = one rumble per wheel rev.
FFB rumble strip wave type=“0” // Type of wave to use for vibe: 0=Sine, 1=Square, 2=Triangle, 3=Sawtooth up, 4=Sawtooth down.
FFB rumble strip pull factor=“0.0” // How strongly wheel pulls right/left when running over a rumble strip. Suggested range: -1.5 to 1.5.
FFB jolt magnitude=“0.0” // How strong jolts from other cars (or walls) are. Suggested Range: -2.0 to 2.0.
FFB shift jolt magnitude=“0.0” // How strong jolts you get from shifting. Suggested Range: -2.0 to 2.0.
FFB shift effect duration=“0.0” // Duration of shift effect in seconds
FFB slip effect=“0.0” // Slip effect, from 0.0 to 1.0
ffb slip freq multiplier=“1.0” // Slip effect frequency. 1.0f = 1 cycle per wheel rev
ffb slip wave type=“0” // Slip effect wave type
FFB pedal throttle vibe zero magnitude=“0.0” // Throttle pedal vibration at 0rpm (reference point)
FFB pedal throttle vibe slope=“0.0"
FFB pedal throttle slip vibe=“0.0” // Throttle pedal vibration on tire slip
FFB pedal brake slip vibe=“0.0” // Brake pedal vibration on front tire slip
FFB pedal brake vibe slope=“0.0” // Slope for brake pedal vibration based on speed and braking %
spring based range lock enabled=“1” // Spring based range lock on/off
spring based range lock strength=“1.0” // Strength of the spring based range lock
spring based range lock max rotation=“1080” // Max wheel rotation, used when setting up spring based range lock
Menu Control - Left Click=”(0, 89, 0, 8)“
Menu Control - Right Click=”(0, 89, 0, 8)“
Menu Control - Back=”(0, 89, 0, 8)"
I will try to make this Thursday update a tradition.
This week, we have started the configuration tool implementation. Some things work already, most of the things do not.
7 Likes
Wow that looks great well done
Top effort, luv it! Thanx for the regular updates, Mika!
Cheers,
Beano
Hi again, its me.
Analog axises and wheel are now being updated in the main UI window, as well as some motor parameters.
This week, some stuff happened in the background regarding analog inputs. Now they work. All that is left to do is to make the UI to configure them, while at the same time learning how to make such UI. And add all those axises to show up on the main window as well. This first dialog will take some hours tomorrow to implement correctly.
Then we will move on to finally implement our new “dropdown and select motor & encoder” feature. For that, unfortunately we have to update SimpleMotion library to a new version first, on the SimuCUBE firmware side of things. Not to say that its not had a small restructuring in itself this week…
We have noted feedback on having the Ioni MMC available for user to tinker with, and that will be added to the profile settings. All currently adjustable filters on Ioni will be there too.
I think we will defer button inputs, working endstop effect, desktop spring effect, working profile management and force effects other than iRacing to after first CLOSED beta version. Open Beta will have at least compatibility with more simulators. But as you can see, progressing steadily…
5 Likes
Thanx Mika for the update once again, significant progress since I saw it 2 weeks ago, very impressed how fast you are going down the list and ticking the boxes!!
Great stuff!!
Cheers,
Beano
Thanks for the update. Think are looking great. Can’t wait to test it!
Thank you for the updates. It’s nice to see the progress and I look forward to testing when it’s ready with support for other titles.
Dean
sounds great. And button support is not a priority at the start, I think.
Desktop spring effect not at all.