Thank you so much for all the work and support provided!! that update is always welcome!!
1 Like
This update has now been released.
2 Likes
Simucube Firmware 1.0.60 is released.
Changes
- Update IONI firmware to 10801. Includes Simucube Force Reconstruction Filter V2.
- No automatic conversions are done to try to match the feelings from Reconstruction Filter v1. Adjustments to profiles are likely needed. Reconstruction Filter V2 at setting 4 should be similar to the original filter at setting 1.
- Add support for iRacing 360 Hz mode. Read iRacing_360Hz_readme.txt for instructions.
- Change new profile default damping and friction to 100 (previously 15) since they work with that value now by default already since 1.0.49 release.
- Change new profile default Simucube Force Reconstruction Filter value to be 4.
8 Likes
thank you very much! the new feature 360hz on iracing itâs fantastic!
1 Like
Do these filters only work in iracing or also in other simulators?
Reconstruction Filter V2 is device side filter that affects all FFB processsing.
Am I the only one that noticed that the source code repository for this was deleted?
https://github.com/SimuCUBE/SimuCUBE-OpenSource-Firmware
This no longer exists, nor can I find an updated official repository with the latest updates.
Also are the schematics and PCB design available per:
Open source hardware would imply that these should be available somewhere.
It was never fully open source. There was no open source interest in the development and we stopped updating it.
Years later it was pointed out to us that the contribution license agreement that we had there was maybe too restrictive, but I still think we had to have one in there.
The firmware was, the source was available and published on GitHub, you have deleted the repository. Forks of it still exist, but are not current.
-
I bought this platform on the premise that it would have source available so that I could alter it to suit my specific requirements.
-
You do not make a project open source and expect contributions just because you made it open source. You did and still do advertise that this is an âopen source hardware and firmwareâ device, it was sold on this premise, and I selected this platform specifically because of this.
-
Nobody is going to contribute back customisation that are specific to their own developed addons/hardware. I had plans to make bespoke modifications to add support for my home made load cell brake pedal, something that would be trivial for me if I had the source. This kind of alteration doesnât make sense to contribute, it doesnât benefit anyone else, and has no marketable value.
This has nothing to do with the fact that you sold it as an open source platform, and have reneged on the promise.
Still on your website today:
Why did you need to âupdate itâ to begin with, the public git repository should have been the master branch you were developing against and pushing code to. It would have automatically always been updated with zero extra effort on your part.
As for the âopen source hardwareâ, this is a complete lie if you donât release the schematic and PCB artwork. I specifically went looking for this when mine failed (as I posted in another thread), expecting to find it so I could effect a repair without guesswork. Firmware is software, so what part of the hardware was/is âopen sourceâ?
Not all source was ever opened. This was due to us making some serious bug fixing in the STM32 USB libraries to make the then-current version of STM32Cube generated USB stuff to work for FFB purpose. That, and the code that handled communications with our IONI servo drive, were not open source. The USB stuff due to already then copycat designs from China seeming to pop up, and the latter due to us not really wanting to support the same undocumented stuff on IONI side indefinitively - to give us flexibility to change and develop at a fast rate.
This was our premise - we wanted to be fully in control of the PC side experience (community creates features, we would do the UI side for it) so we could offer official user support for the product, which we wouldnât have been able to do with fully open source customizations.
no hardware was ever open source. Specifically, IONI servo drive is not open source.
Also, all interest (sales) in Simucube 1 totally died the moment we got the Simucube 2 out in 2019, so it was in our interest to give more boost to open source efforts which could then be easily copied by our competitors.
STM did eventually fix the bugs in their USB drivers, though.
Yes, I have worked with mixed open/closed projects, I understand that there are still some proprietary areas that may be licensed and canât be opened to the public.
Great, what does this have to do with anything? Youâre using the freely available ST libraries which youâre allowed to patch and publish, there is nothing proprietary here. I know the STM32 ecosystem VERY well, being the author of the open source stm32flash tool and having worked on numerous embedded projects that make use of the STM32 line of MCUs.
https://www.st.com/resource/en/license_agreement/SLA0044.txt
Under STMicroelectronicsâ intellectual property rights, the redistribution, reproduction and use in source and binary forms of the software or any part thereof, with or without modification, are permitted provided that the following conditions are met:
Also, you were not publishing it under an âopen sourceâ license as the agreement defines âopen sourceâ. The idea that this was preventing it being published is comical.
This is entirely on you and you should have considered this before you commited yourself to making this project open source. For gods sake, itâs still advertised today as open source even though you have quietly walked back this decision.
If itâs undocumented then do it, break it, you didnât publish the feature for general usage and as such developers should and will expect it to break. Let the copycatâs deal with the fallout of their products breaking because they used features that they should not have.
This was our premise - we wanted to be fully in control of the PC side experience (community creates features, we would do the UI side for it) so we could offer official user support for the product, which we wouldnât have been able to do with fully open source customizations.
Again, this is on you, canât be âopen sourceâ and still be fully in control. You have lied to your customers, itâs plain as day.
Again, if this is the case, why did you ever state the project is âopen sourceâ. You said it, not me. If the communication with the IONI servo drive are to be protected, compile it as a static library and provide that to link with. But that said, you have released it already prior, why is it now âclosedâ when it wasnât before?
With that logic, you could argue that itâs in your interest to send out a firmware update that breaks simucube 1, forcing your customers to upgrade to simucube 2.
You sold this product under the pretence of it being Open Source, both firmware and hardware. You do not get to change your mind after the fact. This is called âBait and Switchâ (Bait-and-switch - Wikipedia), and is illegal. The reason I purchased a Simucube 1 specifically was because it was promised to be open source⌠so where is the source?
I donât expect the IONI servo drive to be open source, as far as I am concerned itâs a separate product entirely.
What I do expect is the SimuCube motherboard (PCB) to be open source, and the firmware source code for the SimuCube motherboardâs STM32 MCU to be available.
For the record: