SimuCUBE Open Source Firmware Development Update Thread 3

The current project to get the new Simucube 2 firmware on the USB interface processor on Simucube 1 is mainly to enable support for the Simucube Tahko GT-21 wheel’s Simucube button feature, and to enable support for Simucube Wireless Wheel 2 wheels.

We know how many Simucube Wireless Wheel receiver modules have been sold, and we can estimate how many of the owners will buy either of them. The estimated ROI suggests it is highly non-profitable.

1 Like

Doesn’t matter to me if that’s ever going to be released or not. The thread alone for me is worth it to get my SC1 setup in a usable state some day. It’s not about the features or firmware, it’s the dedication/sharing that inspires.

It just makes me feel that I owe it to my SC1 and old hardware to get it up and running at some point.

Stuff like this is what gets my heart pumping and why I ended up in the simracing and DIY scene in the first place.

Being open and honest is what separates the good ones from the bad ones imho. A treat that’s missed nowadays where the business has been run over by bullshit marketing and secrecy (across the world and all fields).

1 Like

Bernhard if you have the original Lenze that we were using with the Argon it will indeed work with SC1.
The later high power Lenze that Dennis was selling unfortunately doesn’t run well at 48v.

I will try to find the drc file for the SC1 with Lenze for you.

If I remember correctly you also want to run the the 960 watt Meanwell power supply?

I will start searching for you. It has been a looooooong time since this topic has come up. :wink:

1 Like

Yeah, I still have THE “original” (like “the first Lenze ever for that application”). That’s the same model that Dennis later used to sell in his package when he opened up his business. I think he then switched to the 380V model with a different encoder too).

My main problem actually is hardware related as I have no casing to house the fat MW-960 PSU and SimuCube - which is a big no-no because of safety concerns (open wires and stuff in the middle of the living room). Running the Lenze on a smaller PSU however is a bit lackluster, so it’s 960 or nothing…

If somebody knows someone who might be willing to sell a case/housing for SC1+MW960 don’t hesitate to PM me :slight_smile:

You may want to check with Beano/Phillip. I know he had one up and running at one point.

It really is not the best motor for SC1. Voltage limited if I remember correctly.
I still have 2 or 3 of them. LOL

Yeah, it was a pretty good fit for the Argon though, maybe I’ll just go down that route instead and find myself some good ol’ “small MiGE” to play some “fun with sc1”. Lots of options for casings out there when you don’t have to piggypack some monster PSU…

…looking back I probably should have just kept the Mige too instead of just giving it away… lol🤦‍♂️ That “little” Chinese fellah would have aged really well!

1 Like

This firmware supported stm32f407 discovery with ionicube 1x ?

No, only Simucube is supported. It will not work on Discovery.

Hello
Any news ?

Two weeks ago I got it to start on the Simucube 1 board, but many things didn’t work, and I didn’t have time to debug it more. It is likely, that there were some issues with memory running out with the Simucube 1 (and Simucube 2 Classic) style profiles.

It will be January when I will next have time to work on it.

3 Likes

Cut profiles. We need 5-6 profiles probably, no more.

It should not be a big issue, maybe 20 is still ok.

The device worked in such way that it always reported 0.0.0 as its version number in the status query reply, and many other fields in that packet were also zeroed out, where as the same code in Simucube 2 works fine. Also some fields that definitively were being read into the status query from servo drive did in fact show correct data.

I added some debug printouts, but it turned out that those were much for the system and it got bricked,doesn’t reply to any commands from PC.

Looks like I will have to install it via DfuSeDemo the next time. But need to do code review to find code for the zero data issue…

4 Likes

Well so far i have only that one “Joni Takanen profile” so i do not know where more would be needed but i guess some profiles would be nice to have :smiley:
Great work and support Mika for doing this pretty much to show that you still remember old customers. This is truly remark of showing commitment to customers and support of products.

1 Like

Definitely not!
For iRacing alone I have many more profiles than 5-6, especially with newer content like the TCR cars that require a very different SC setup than any other cars.
Then there’s other titles such as RF2, KartKraft, ACC, AC etc.

Dan Suzuki uses individual profiles for most cars in iRacing and ACC, and for those of us who like to fine tune our profiles per car/car class, the idea of 5-6 total profiles is absurd - it’s not a Thrustmaster TX!

I don’t see why there’s any need to limit profiles, and it hasn’t been a problem for me or any of the other SC1 owners I know.
But if the benefits of a new updated FW with useable/useful features from the SC2 was to come to fruition, then I suppose I could deal with 25-30 profiles.

Hope you are all safe and well during this holiday season, and best wishes for the 2022.

1 Like

You could also opt to not use the ported FW at all if it can’t support your need for 500 profiles stored on the device.

Not sure though why profiles couldn’t just be stored on the PC and get loaded when needed though…? Are there any write cycle limitation concerns?

1 Like

Depends on how you gauge ‘ROI’.
Both my friend and I bought the SC1 wireless module and wireless wheels (Cube/Ascher) for the holidays, and thoroughly enjoying them.

Because of your ongoing commitment to supporting the SC1 (and all the many users who tirelessly provided crucial feedback that helped design the SC2 functionality), when ANYONE asks about what direct drive wheel to purchase, I always steer them firmly to Simucube (6 people so far across SC1/SC2) instead of Fanatec etc.
Anyone who has purchased an Simucube, will almost certainly purchase another Simucube product in the future, so ROI comes from loyalty and trust of the SC brand, which is fundamentally the ongoing efforts of Mika and the community - you don’t get any of that with other brands, other than the guys who are so financially locked into the Fanatec ecosystem from buying different wheels etc.
That’s not loyalty, that’s imprisonment!

2 Likes

I don’t think Mika has ever run out of writes, which suggests that number is far higher than any consumer would use.
500 profiles is a bit of a wild stretch :rofl:, but the idea of being able to load them from a folder on the PC is a good compromise if Mika were to limit to say 25 in return for updated functionality that noticeably improved the feel on SC1 devices.

2 Likes

I absolutely agree on this. The DD scene wouldn’t be what it is today without the efforts of GD. And those started even way before the SC1. They earned lifetime loyalty with great support and continuous effort.

1 Like

I do remember a conversation that there was a write cycle limitation on one of the chips on SC1.
I don’t remember which chip, or how many write cycles it could handle.

Afaik it was 10k write cycles on the SC1 (and also on the SC2 flash).