I have Granity 1.13.0
Do you get that error in the Configuration Tool still after manually flashing 1.6.1?
Yes, still same errors.
Use decimal values to fine tune filters.
Hi Ryder,
Switch S1 back to normal mode after flashing Bootloader via DFUseDemo, but before updating fw. Power down the Simucube before moving the switch. Does that work for you, after powering up and then trying fw flash from the Configuration Tool?
Cheers,
Beano
Just had a remote assistance session with him. Turns out he was Finnish as well.
Fault symptom: Couldnāt connect with Granity, and the Firmware couldnāt connect either.
Reason: his SimpleMotionV2 address offset was 5, where as it should be 0. Firmware didnāt find it, and somehow didnāt manage to release Simplemotion from that kind of state.
We flashed MMOS, could then connect, reset the bus address offset to 0, saved, and flashed successfully.
3 Likes
We had a debugging session with Mika. Works now!
I had wrong address offset for some reason in my granity setup.
Ha cheers guys, top effort 
Glad its all sorted!
Yep, funny as the offset didnāt have any effect when using MMOS, but the new firmwareā¦ hmmā¦ I must investigate and make sure that at least releasing the bus will work every time.
Good point, would have caused me a bit of delay too. Might have seen this early on in alpha once, I think. Flashing back to MMoS like you did and setting bus address fixed it. Not sure if I messaged you about it. But anyway recoverable, albeit with a bit more effort.
But making it foolproof probably the best option.
Well that is a new one! Good job figuring it out!!
Are you cataloging the problems that have come up and the cure?
This would be very nice so we can create a troubleshooting doc.
Again nice fix!
Of course - I have a list, and also I already put this into the user guide.
Also, we would prefer to keep improving our own user guide, so that it will benefit most people. We will eventually integrate that to the āoldā SimuCUBE wiki pages when the pages get an overhaul. There is already some work done for that behind the scenes.
Of course, given its a wiki, everyone can contribute
How do you access this offset setting?
I had a customer that had issues connecting to granity back when still ysing mmos.
Its in Granity,
https://granitedevices.com/wiki/Granity_user_guide/Goals
And does not affect connecting when mmos is installed.
Some Windows versions install very old drivers for the ftdi RS485 chip, that require update before connection works.
Hi Joe, it was the SMO bus address offset or something like that.
Thanks Guys,
Learning some new stuff during these problems!
Now if I could only remember all of it! LOL
Hey Mika,
See below a quote from a comment I made on iRacing. Some weird Comms-behaviour issues I experienced last night.
History: I used chipset-based usb2 connection. Because I needed more ports on my pc, I added in an Orico P3usb-4V card, with VIA chipset. In game, FFB behaved very weird, something I saw with even Argon years ago, when working with VIA-based USB chipsets. FFB will behave touch and go, i.e. working/disappearingā¦but this is besides the point and VIA chit.
My issue came when removing the VIA drivers, and the card. I then switched back to original Config with wheel connected to the chipset usb2. Reset pc and Simucube. Tested the wheel in windows with Config Tool open. Then behaviour like below.
[quote]This is a new issue, I had some unexpected micro-FFB stutters last night after connecting to a pci-e usb3 card.
Removed the card and switched back to on-chip usb2. Rapidly turn wheel back and forth caused Comms loss between IONI and Config Tool. At first the wheel animation in the Config Tool will catch slightly, then it froze altogether. Had to reset a Simucube to get it going again. Happened another 2 times after, since then, nothing. I opened the FEV limit even more, as the first time the motor faulted just before this freeze-event.
Something Mika cab check out at his leisure.
Cheers,
Beano[/quote]
Since I flashed to the Simucube firmware, in Assetto Corsa, I sometimes get a pink screen and crash back to UI if the full ffb rate is running, or just crash back to UI if half ffb rate is ticked.
Before this I was running 1.15.1, & mmos, never had this issue
Windows 10
Gigabyte EX-58 DS4 motherboard
GTX1080
So now Assetto Corsa, and rFactor 2 will not work for me.
But I canāt revert back to the mmos. When I open the DfuSe demo, there is nothing in the available Dfu devices drop down menu. I have even tried the S1 switch, no effect, even after power cycling.
And both usb ports are connected