walmis

I'll provide some evidence supporting a possible GPLv3 violation. I've examined strings extracted from the Moza executable, which hint at an underlying connection to the open-source VPforce TelemFFB project. Within Moza's code, we see identifiers like vp_dcs and VpAlgorithm that incorporate the "vp" prefix, a clear nod to VPforce, though they don't exactly mirror VPforce’s original identifiers. This suggests that Moza's software may be a derivative work inspired by or partially based on TelemFFB. Given the technical leap from Python to C++, Moza likely used AI-powered tools, potentially GPT-based, to translate parts of the Python-based TelemFFB core code into C++ for their compiled binary. If Moza's code does indeed derive from TelemFFB, GPLv3 would require them to release their own source code under the same open-source license, something they haven't done. This evidence suggests that Moza may have created a derivative product based on TelemFFB without complying with GPLv3, raising concerns about a possible license violation. Next we see hastily 1:1 copied effect adjustment names They even copy pasted damage variables into their export.lua (even the line endings match!) So to summarize (thanks ChatGPT)

Worse yet is that DCS does not take account which device and which axis is bound in the controls. If there are multiple FFB devices, DCS will send X,Y axis effects and trim position to multiple FFB devices. So if you have FFB stick and pedals connected at the same time, both pedals and stick will receive the stick (x,y) trim position. Luckily we made workarounds when using TelemFFB. Additionally DCS could add more data to export.lua interface, such as actual trim position, the rest we can implement in TelemFFB app.

https://discord.gg/XEXZmQHk3T this one should be unlimited

Hey, until the website is done you can join the VPforce discord: https://discord.gg/XEXZmQHk3T There's a #faq channel with the most relevant information.

Hi, I can jump in here So a couple of advantages of the top of my head: Rhino is plug-and-play DirectInput, so no additional software is required for it to run on FFB supported games. Rhino has bigger motors and much higher gear reduction - much more torque Bigger motors with active cooling don't overheat in normal use cases. Price Here's a video showing versatility of the system in action, showing a mechanical implementation of the Rhino DIY motor kit for a custom cyclic from one of my first clients

Hey guys, I've noticed some FFB related discussions, so I figured I'll jump in a bit since I'm working in the field for quite a while So I have been developing a a plug and play FFB system for the past few years, and recently started shipping first motor kits and first 'RHINO' FFB bases. The FFB motor kit is aimed for cockpit builders and hobby mechanics who want to build their own stick/cyclic, It solves the complicated problem of system control, motor power delivery, USB communication, etc. I very much hope more people will (re)discover FFB and we, FFB users, will receive more love from ED. Feel free to join my discord server: https://discord.gg/XEXZmQHk3T to keep in the loop about the latest developments. My YouTube channel with some FFB demos: https://www.youtube.com/user/walmis

Good stuff, just don't forget one important piece for such high powered equipment

Hey guys, some quick test flights: I've also made a discord server, so most of the stuff is happening there: https://discord.gg/Y7YmFGHbee

That type of gimbal works perfectly fine for the forces applied in this application. Of course if one wants 20kgf, you might skip the Rhino and build a DYI machine. But as a compact Brunner alternative it works perfectly fine. Disclaimer: while the gimbal might look similar to yours, I have it redesigned from scratch.

The servo drive can be driven up to 30-35A (the limitation is the current-sensing feedback path gets saturated with 1mOhm shunts, MOSFETS are rated up to 175A). But according to the motor datasheet, peak current is within the servo driver's current limitation. I'll need to test the real world performance. Maybe it's possible to push it more. The 57BLF03 does indeed have a D shaft: Can you elaborate more on "shaft-winding"? sounds interesting

Yes, definitely! Got my hands on a few samples of 86BLF03 motors. Installed the servo drive. Works a treat. Happy to say I will be able to supply them. Demo of the big boy in action with the 57BLF03 for scale: https://gfycat.com/unrulyentirebilby

Hey guys, I've uploaded an album featuring RHINO FFB Base. https://imgur.com/gallery/Do6Jr0T

I have this planned. It will be easy to disable X or Y axis and adjusting the feedback parameters as desired for the single axis!

Been researching how to improve the implementation of the Friction effect. Think I found a solution. This will be a solution to implement a Helo Collective for example without messing with complex mechanics.

The motors are rated 3000rpm at 24V. I have used these with my first base, which has 1:24 ratio pulleys. Works just fine