MetalGear_Honk

Hi sorry but only the Hex file. i don't like the Arduino IDE as it is a c derivat and i prever c++ so Atmel Studio is more to my liking. but you can use one Arduino as ISP Programmer. and burn the Hex into another.

Hi Good to know. I am not used to legalrights. So I take it as is. Jpdesvals, can you share some pic of the disassembledparts? MetalGear_Honk

Hi @Bixio: I am not entirely sure what you are asking. if I get you right: Direct input is the DirectX command set for using the DX build in interface to communicate with PID devices(FFB for example). As I am trying to get the firmware PID conform it will natively be able to receive Direct input signals send through DX. (as long as DX supports it). pedestals: I don't think it is necessary to scan the parts (what might be a violation in Legal terms) but to get to know how exactly it is working. I am studying the Pics from Abburo at the moment. the G940 Gimbal looks exactly like my last try. only that mine is locking when going diagonal. so I must have missed something. I am under the impression that one Axis connection must be flexible in "distance" can someone confirm this idea? @VO101_MMaister: sorry missed you post. the best gear ratio-> RPM is still not cleared, and open for discussion. MetalGear_Honk

Hi Thanks abburo got them. MetalGear_Honk

Hi A quick reference for the Hardware 1. I use Small Brushless DC Motors. (I hadthem around) for testing. 2. I use 3d printed Gear (1:25 stepdown)for strength 3. The Motors are 12V powered by an ATXPower Supply. 4. Motors are controlled through anH-Bridge (L298 ) The L298 has 2 H-Bridges so you can wire both Motors to it For the Gimbal: I am still working on that part. I don'thave any FFB device so I cannot simply replicate something. And my test Gimbalsare not working very well. Maybe someone with a working FFB can sendsome pic’s from the mechanics? For the Force effects: Spring, Damper, friction, constant, Rampand Square are implemented and hopefully working properly. Sin, triangle, saw up, saw down and customare set in the HID but not working. If no FFB Signal is send from the PCinternal spring should be active. I am still working on the effects but at the moment the Gimbal is more in focus. For optical tests ii use some LED andPotis: 4Red for Direction of Motor two foreach. And two green for strength. (PWM Visual on LED is Nonlinear) That way I can test without always usingthe not so functional Gimbal. MetalGear_Honk

Hi The Test Firmware is turning an ArduinoPro Micro into a FFB Joystick already. But not all Force Effects are implemented.Sinewave form is missing for example. For the Hack: I would not recommend doing that withoutenough knowledge and Routine in soldering PCB. For getting the PWM signals (Motor Directionand strength): Looks possible but I am not sure. Could be that the Controller shuts itselfdown when it recognizes that the Motors are missing or not responding withthe expected current. In that case you would need to feed it withamplified Current readings from your new Motors. MetalGear_Honk

Hi the first problem is that the protocol for ffb will send a direction where the force is going to go. so somehow we would need to determine how much force witch wheel should get. and when we have that sorted the rest is not much more of a problem. the second problem would be to get both axis synchronised. for example to build a square wave form in 20° direction. and not one in0° and one 90° with different strength. and last we would have two devices in the configuration but ffb will send only one protocol for both where we are back for the first problem. at the end we will need to write a new firmware to sort out these problems. or we can write a new one from scratch. (witch I am doing at the moment) I uploaded a test version if you feel in for some experimenting. Greetings MetalGear_Honk

Hi Not in a wrong place but missing: Eu and Le Treport. Both were fortifiedwith Bunkers at coast and facing inwards. MetalGear_Honk

Hi For the Controller: yes I use anATMega32U4 that is the one from a Pro Micro Or teensy. I have a STK600 Board so therecan be some differences. forthe Code: I hope it is not to chaotic. As I am usedto work alone. I have used great parts from FFB Adapterso all credits to them. JOYSTICK_Test.zip

Hi I have some News for this Project. First of all I think I found a wayto fix my Timing Problem. I simply split the calculations to getmore time for the USB calls. That costs only a few cycles more and itseems to work as planned. (I will see if I can upload a new Hex nextweek, for everybody to test) Having that sorted I have some Problems First I Need a Better test board. So Istarted to build a Demo stick. I am experimenting with different Gimbaldesigns, but I am not very happy with the results. So I am open for ideas. Second I can't get my brain to come up with aformula to get this Sinus Function to work. So if someone is good at math and hassome spare time I will be thankful. MetalGear_Honk

Hi here is my second generation for a Hotas system. Stick: all Metal-Gimbals with Hall sensor and 16bit resolution (ads1115) 2stage Trigger index button 5times 5way Switches (25buttons) Pinky switch paddle Thump axis 10bit x/y Hund1.jpg Throttle: 2 Throttle axis with Hall sensor and 16bit resolution (ads1115) 2 Pots 10bit 6 3stage trigger on base 1 2way button on Base 3 thump buttons 2 5way on thump 2 5way on index and ring 1 5way on second axis grip schnuffel.jpg MetalGear_Honk

Hi all I have a Raspi here but it is natively aUSB-host not a USB-device. I have no idea if it can be changed. An alternative would be a CortexController like the SAM series from Atmel. But I don't have one around. @Sokol1 Do you have any info about thatStick? MetalGear_Honk

Hi I am still working on the FFB. For a Centering I also found that themost difficult part. For the Project: I am working on a 3D Printed Version forthe Gears and Motor Mounts. So it is easier for everybody to replicateand test. I am not an 3d-Artist so it is painfulslow in Progress. The MC is still the STK600 from Atmel but Ialso started to use a ProMicro clone. I am not very happy with the ArduinoBootloader and so I might switch it in favor of the Lufa Bootloader. But all that depends on the ability to getthe Angle calculation speeded up. Or at least split up between USB send Cycles. Greeting MetalGear_Honk

Hi Just want to say Thank you. That is really an outstanding Campaign. Thanks to the Voice Actors as well. I found myself more than once talking an responseto some communications. MetalGear_Honk

Hi I restarted the FFB Source again. First I am hoping for some help inoptimizing the code. But as it is very chaotic I would need toclean it up first, and ad comments (now my code is documentation for me :-) Is there someone with some mc knowledgeand willing to help? Otherwise I see no Need to order my code and can work onit as it is. MetalGear_Honk

Hi I had to put my FFB Stick on hold oncemore. I deeded a new Hotas so I was busybuilding one myself. (Will Show pics when I have all Setup and ready) My code is not very public friendly andeven parts of it are not my own work. So I would need to ask around first if Ican post it. On another note I started on a test environmentfor the FFB. I use DC Motors and Hall sensors it is working out quit well. AlsoI currently use very weak DC's. As I got still Problems on Timings I wasthinking of changing to the much stronger asm Chips. But that would mean torestart from scratch. MetalGeaar_Honk

Hi Same for me crashes on start Mission 00072.040 DEBUG LuaGUI: ----onSimulationResume--- 00072.062 INFO DCS: invalid input at index 0 in ed_fm_add_local_force 00072.062 INFO DCS: invalid input at index 0 in ed_fm_add_local_moment 00072.067 INFO DCS: invalid input at index 0 in ed_fm_add_local_force 00072.067 INFO DCS: invalid input at index 0 in ed_fm_add_local_moment any info what is causing the Crash? i have done the cleanup and repair. also VC14 is installed on my maschine. greatings MetalGear_Honk

Hi when diming down the brightness of the gun sight and Setting it back to full brightness it stays a bit darker than max. That can be repeated until the sight stays out. greatings MetalGear_Honk

Hi Looks very promising. Plenty of stuff to burn. :-) I was a bit busy building a new conventional Joystick. So I have did not work much on the Firmware. But I will try to Setup plans for some Controller. So I can test the Software in more Detail.

Hello I made a Little Progress with the Software. The Device is not losing connection anymore. And I can trigger different Forces with FEdit (or any other test Program) My new main Problem is that it seems that the Attack Timings are no longer correct, and I still have some Forces not working. I can upload the new Version if someone will test is as well. MetalGear_Honk

Hi Any Idea is welcome. For Buttons I normally use Shift in (HC165D). 4 in daisy and a second set for parallel reading the second chain. That way I get 64 Inputs. And you do not need denouncing. The load pin takes care of it. As you only set load active for 2-4 Cycles. Thru that can result in a few millis delay in triggering a button. Reading the shifters in main will allow the MCU to send Status even if a Chain is not fully read in. For analog Inputs I normally use an ADS1115 for 16bit ADC it communicates thru I2C and is set to constant reading. And it Needs 3Byte per Port. So it takes 12 Byte for all ports to Transfer. That Setup is working on my actual Setup. And it will be implemented in my MK2 (if I ever get it done). MetalGear_Honk

Hi all I was also thinking about using a 32bit MCU but as I am/was not active working on FFB I skipped the idea. I was programming 8bit MCU at Work so I stuck with them. I was thinking about exporting the USB communication inside an Interrupt Routine. With fixed Timings. And let the FFB calculation run in main. So I will not lose connection. And the FFB Timings are not as critical. MetalGear_Honk

Hi @Dracoz Yes I use some Floating-point Calculations and of course sin/cos for Directions I tried to use Lookups for Directions but getting Problems with Memory space as I have to save most Memory space for preloading the Forces. (the ATMega16u4 can Only save 15 Forces in my Code) As for Interrupts I only use one timer-interrupt for counting up to get milliseconds since force start. MetalGear_Honk

Hi No Sketch will be the same. Only the Pins for Direction left will stay unconnected

Hi My Timing Problems are that I can't get the Timings for USB communication/Force calculation / force Duration / reading Axis and Buttons The Version I provided is that for unstable. And tends to lose contact with the PC (USB is very picky on Response Timings) MetalGear_Honk