finch Posted April 25, 2021 Share Posted April 25, 2021 Print in progress, need to modify some parts so I can use the MSSFB2 potentiometers (or something better) for now 1 Link to comment Share on other sites More sharing options...
RealDCSpilot Posted April 25, 2021 Share Posted April 25, 2021 Started to put my project on github: https://github.com/Flashgod-VR/G940-Total-Conversion-Kit 3 i9 13900K @5.5GHz, Z790 Gigabyte Aorus Master, RTX4090 Waterforce, 64 GB DDR5 @5600, Pico 4, HOTAS & Rudder: all Virpil with Rhino FFB base made by VPforce, DCS: all modules Link to comment Share on other sites More sharing options...
finch Posted April 25, 2021 Share Posted April 25, 2021 38 minutes ago, RealDCSpilot said: Started to put my project on github: https://github.com/Flashgod-VR/G940-Total-Conversion-Kit what laser cutter do you have? I wanted buy one or use a laser on my 3d printer, thanks Link to comment Share on other sites More sharing options...
RealDCSpilot Posted April 25, 2021 Share Posted April 25, 2021 (edited) 7 minutes ago, finch said: what laser cutter do you have? Sorry, didn't cut it myself. I found a company in my city which did the laser cutting. I also considered printing them myself with carbon filament, but i took the "quicker" road Edited April 25, 2021 by RealDCSpilot 2 i9 13900K @5.5GHz, Z790 Gigabyte Aorus Master, RTX4090 Waterforce, 64 GB DDR5 @5600, Pico 4, HOTAS & Rudder: all Virpil with Rhino FFB base made by VPforce, DCS: all modules Link to comment Share on other sites More sharing options...
frumpy Posted April 26, 2021 Share Posted April 26, 2021 Wow! A full size FFB-stick is on my bucket list for things to do in life. I wonder, are all information / software / STLs complete? So if I press "stop" on the internetbutton and work with the info I have, is it possible to do this on my own? Is there a parts list? 1 Link to comment Share on other sites More sharing options...
RealDCSpilot Posted April 26, 2021 Share Posted April 26, 2021 Please, never ever press "stop" on the internetbutton. Parts lists and information is all there: https://github.com/o-devices/bldc-ffb-joystick-base https://github.com/Flashgod-VR/G940-Total-Conversion-Kit 1 i9 13900K @5.5GHz, Z790 Gigabyte Aorus Master, RTX4090 Waterforce, 64 GB DDR5 @5600, Pico 4, HOTAS & Rudder: all Virpil with Rhino FFB base made by VPforce, DCS: all modules Link to comment Share on other sites More sharing options...
Fri13 Posted April 26, 2021 Share Posted April 26, 2021 2 minutes ago, RealDCSpilot said: Please, never ever press "stop" on the internetbutton. http://www.turnofftheinternet.com/ 1 i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S. i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K. Link to comment Share on other sites More sharing options...
MAXsenna Posted April 26, 2021 Share Posted April 26, 2021 http://www.turnofftheinternet.com/Good one Fri!Sent from my MAR-LX1A using Tapatalk Link to comment Share on other sites More sharing options...
Alan Fistwood Posted April 28, 2021 Share Posted April 28, 2021 @propeler Will your firmware-board be able to use the sensors integrated into the hoverboard motor? Link to comment Share on other sites More sharing options...
propeler Posted April 28, 2021 Author Share Posted April 28, 2021 49 minutes ago, Alan Fistwood said: @propeler Will your firmware-board be able to use the sensors integrated into the hoverboard motor? No. It is not enoug resolution for precise control of motor using integrated hall sensors. Hall sensors works good when motor rotates at sertain speed, but for FFB purpose motor is almost static in most cases, where hall sensors are useless. Link to comment Share on other sites More sharing options...
Alan Fistwood Posted April 28, 2021 Share Posted April 28, 2021 (edited) My progress so far, I scratched the previous design for now, because just in hardware and motors the price is over the 200€ mark, checked on my local marketplace and since used overboards sell for just 50€ I can get two motors for cheap, and by direct driving I can also save on belt and pulley, so I am working on this gimbal wich is similar to the original g940 but upscaled a lot, overal way simpler, still a long way to go before it's printable Edited April 28, 2021 by Alan Fistwood Link to comment Share on other sites More sharing options...
Donglr Posted May 3, 2021 Share Posted May 3, 2021 On 4/24/2021 at 7:45 PM, walmis said: Did a force test on my machine. Currently I get ~5kg @ 18-20A motor current, motor dissipates around 60 Watts at that current. (Motor phase resistance is around 0.135ohm) Quite impressive what that little thing can pull. And a massive thumbs up for pulling something like this off. Ich had a look at your GitHub but it seems "only" the schematics and a lib are available atm. Do you plan on releasing the source code as well as the step files to actually build the complete joystick hardware? Also you use one controller per motor, meaning two STM32 control two motors so only one axis per STM32. How do you make one device out of it that gets recognized as a single joytsick? Link to comment Share on other sites More sharing options...
walmis Posted May 4, 2021 Share Posted May 4, 2021 Quote Also you use one controller per motor, meaning two STM32 control two motors so only one axis per STM32. How do you make one device out of it that gets recognized as a single joytsick? There are actually 3 controllers, 1 is the "master" which talks to the motor controllers, does USB stuff and does the effect calculations and so on. 11 hours ago, Donglr said: Do you plan on releasing the source code as well as the step files to actually build the complete joystick hardware? Yeah, I'm planning to put the firmware and project also on github eventually, I'm just want to "mature" it a bit, so everything works correctly. Link to comment Share on other sites More sharing options...
Chuls Posted May 4, 2021 Share Posted May 4, 2021 (edited) On 5/4/2021 at 8:25 AM, walmis said: Yeah, I'm planning to put the firmware and project also on github eventually, I'm just want to "mature" it a bit, so everything works correctly. I have been working on the firmware for ATMega32UX devices (such as the Arduino Micro or Leonardo) in this repo: https://github.com/jmriego/Fino/ Most of the code online about force feedback firmware seem to have been based on the VNWheel repo so I'm sure you can reuse some of my code. I have tested every single effect and have all of them working as expected. I compared the results against a MS FFB2 for all effects, directions, axis, etc. so I hope this helps! Edited May 5, 2021 by Chuls 1 2 Link to comment Share on other sites More sharing options...
robjos1 Posted May 18, 2021 Share Posted May 18, 2021 On 4/22/2021 at 5:58 PM, propeler said: Yep. Now one axis firmware already is on github https://github.com/o-devices/bldc-ffb-wheel-firmware for two axis will be available as well soon here https://github.com/o-devices Hi, Just wondering how you were getting on with the 2 axis code? I'm keen to try it out, I've noticed the single axis code is down too? Link to comment Share on other sites More sharing options...
propeler Posted May 18, 2021 Author Share Posted May 18, 2021 17 minutes ago, robjos1 said: Hi, Just wondering how you were getting on with the 2 axis code? I'm keen to try it out, I've noticed the single axis code is down too? I have a version of finished firmware and UI for it already sent to the guy who owns device. He will test it when returns from business trip and I will post it with instructions how to flesh it and how to connect encoders. For now it supports custom board. If tests will perform OK i will make a version for ODrive as well in couple of days. If you are interested I can send you this version of firmware. Doy you have ODrive or board from link which I posted on github? Link to comment Share on other sites More sharing options...
robjos1 Posted May 18, 2021 Share Posted May 18, 2021 Ah cool, yea so I have a standard 2 channel Odrive V3.6 56V and a number of different bldc motors to try. Would be great to get some code to test, does it work odrive native or do you need to run a arduino pro micro with the code in between? Link to comment Share on other sites More sharing options...
propeler Posted May 19, 2021 Author Share Posted May 19, 2021 17 hours ago, robjos1 said: Ah cool, yea so I have a standard 2 channel Odrive V3.6 56V and a number of different bldc motors to try. Would be great to get some code to test, does it work odrive native or do you need to run a arduino pro micro with the code in between? Ok. I can prepare version ODrive. Encoders? Now it is for SPI AS5048 and similar. It is native code, no other peripheral needed. ODrive will be recognized as FFB joystick in Windows. 1 Link to comment Share on other sites More sharing options...
robjos1 Posted May 20, 2021 Share Posted May 20, 2021 Thanks thats perfect. So at the moment I use AMT102 running 8192CPR. Seems to work well under normal odrive control. https://www.cuidevices.com/product/resource/amt10.pdf Link to comment Share on other sites More sharing options...
SeppForcher Posted June 4, 2021 Share Posted June 4, 2021 Is it possible to get a version to test for the custom board? Link to comment Share on other sites More sharing options...
SquidgyB Posted June 4, 2021 Share Posted June 4, 2021 Hello there! I'm in the process of building my own FFB joystick using hoverboard motors, an ODrive and off the shelf/home-tool modified parts. The "prototype" (likely also end product!) is currently being assembled and built - I'm looking at an MDF box with 2 live hoverboard motors, and two (currently) disconnected motors (it's actually cheaper to buy broken hoverboards than bearings, and driving another two motors requires an additional ODrive unit an what I can only imagine would be a fairly decent amount of work to get them talking to each other - and the PC, as one unit, controlling 4 motors set on two axes), a gimbal built from aluminium 3D printer shaft clamps (SK16), a car propshaft/steering universal joint spider, and some carbon fibre and aluminium tubing and aluminium block/plate. I have a (very) small lathe, small milling machine/drill, bench sander and disc cutter, so the tools I'm using aren't crazily unobtainable, but I do have a little garage workshop setup. I'll post some photos once I have something that isn't just a pile of random bits, but my main question/request goes to propeler - could I possibly also have a copy of the firmware you're using for the ODrive? I'm looking at using the TLE5012 encoders - I'm not sure if that's the same or significantly different to the ones you're already using? 2 Link to comment Share on other sites More sharing options...
Alterscape Posted June 6, 2021 Share Posted June 6, 2021 Hi Propeler, could you share the ODrive firmware with me as well, please? I've got a current ODrive with AS5048s and the motors you specified. Still waiting for cut/bent parts to arrive, but the plan is to build your gimbal as drawn! 1 Link to comment Share on other sites More sharing options...
robjos1 Posted June 9, 2021 Share Posted June 9, 2021 On 5/19/2021 at 5:16 PM, propeler said: Ok. I can prepare version ODrive. Encoders? Now it is for SPI AS5048 and similar. It is native code, no other peripheral needed. ODrive will be recognized as FFB joystick in Windows. Just wondering too how you were getting on, my single axis test bench is all ready to go 1 Link to comment Share on other sites More sharing options...
propeler Posted June 10, 2021 Author Share Posted June 10, 2021 (edited) 16 hours ago, robjos1 said: Just wondering too how you were getting on, my single axis test bench is all ready to go If you have single axis, there are good news for you In scope of building FFB wheel there version of firmware available already. First one is for ODrive and incremental encoder pair. It can be downloaded from here https://megafile.cc/d/P9or/odrive-ffb-wheel-20210530. In archive there is two folders. One with firmware aand one with UI for changing settings. First connect components as on diagram: Second - upload hex file from firmware folder to ODrive (for example I use STM32CubeProgrammer). After rebooting ODrive there will be new joystic device visible in system. Start UI program from ui folder and you will see window with default settings: You need to press Wright to controller to save them. Then go to Advanced tab: Enter your encoder CPR and press Save button. Thats all. After rebooting ODrive will be functional as FFB wheel. On every start it will be performing short calibration sequence, so allow it to rotate freely. Pressing button will work as a trim, and makes current position as the center. My current task is to finish version for my custom board with magnetic encoders. There are some wierd issues I'm trying to debug and fix. Two axis ODrive with incremental encoders will be in work after it. Edited June 10, 2021 by propeler 2 2 Link to comment Share on other sites More sharing options...
robjos1 Posted June 10, 2021 Share Posted June 10, 2021 Thanks so much for all the great info, so though I'm just testing one motor at the moment I have the standard 2 channel odrive (3.6 56V) Just to check will your firmware work with this? Link to comment Share on other sites More sharing options...
Recommended Posts