Jump to content

MetalGear_Honk

Members
  • Posts

    129
  • Joined

  • Last visited

Everything posted by MetalGear_Honk

  1. Hi I am stuck at the same Point the first Car is shoot down by the Armed Hous at the entrance of the Farp. I tryed killing the second aswell, but that does not help aswell. oh and Thanks for the Campaign MetalGear_Honk EDIT: i took a look at the mission. seems like the second Car is missing the invisible status.
  2. Hi I was having some great time flying the Campaign from Baltic Dragon once more. But while I like the Mirage quite a lot, I was not able to find any Key binds for the Radios. Maybe it is just me but I could not find any reference to switch Radio Chanel up/down. MetalGear_Honk
  3. Hi For my Test Versions: The Inputs are disabled so I can use my normal stick while testing. If I remember correct I deleted the request trigger from the USB side. I shelfed this Project. So not much more will happen from my side. MetalGear_Honk
  4. Hello It is still raining inside the Armored Glass. Is there some info’s when or if it will be fixed? MetalGear_Honk
  5. Hi I found a little error in the Briefing of mission 6. On the Right side where you get the mission descriptions normally. I am fling the Sabre, and task to fly with the A10s. But in the Description stand that I shall meet up with two SU25t. Looking back at how the mission turns out it is quite funny Great Campaign. Greetings MetalGear_Honk
  6. Hi Yes i know that it is the last one. but i can not finish it. after Landing/ exiting mission i get a Crash to Desktop. MetalGear_Honk
  7. Hi Yes in my case I have to move the normal Cross Courser 10cm above the Menu and a bit to the right. Then I can see a white arrow like Courser that comes into view and I can use it. Another way could be the mouse wheel button. It centers the courser in the middle of your view. So looking at the text and clicking the button should bring the hidden courser at the right position. MetalGear_Honk
  8. Hi all I just got back to the Viggen, and I wanted to review my Hotas settings. There are plenty of Axes “missing” so I thought I ask if it is plant to add them later on? Radar Brightness is the one I miss the most. But other Cockpit illuminations as well. As a side question: I played the mini Campaign but could not get past mission 5 as it keeps CTD.
  9. Hi I use a Lenovo Explorer to Fly in VR. And in the October update Windows introduced the Flashlight feature. It is basically a Pass-through from the front sensors. It is not the best View but it is helpful. (At least for me) But I can't figure a way to use it without controllers. My intension is to map that function to my Hotas. To use it from there to find my Beer. I know about the voice activation but I prefer to not tell my Flightcomander that I want to use a flashlight in broad daylight. Had someone more luck? I heard about the new SteamVR feature to remap buttons but I couldn't find a way to use it with my Hotas. MetalGear_Honk
  10. Hi When you open the coms menu in VR you get a second Courser. It is normally a bit below the normal one. And it will only appear when over the menu texts. At last that is how it works for me MetalGear_Honk
  11. Hi That device is exactly what I was looking for. Wonderful idea. As a side note I see you are using standard LED have you thought about using flat top LED? For wider Angle? And for my personal curiosity: is that a Pixart sensor? Where did you get these? Greetings MetalGear_Honk
  12. Hi As for using the Analog input in Arduino. { int Rotary1; int RotaryPosition; Rotary1= analogRead(A0); RotaryPosition = round ( Rotary1 / (1024/11)); } I don't have the Arduino IDE here. So it might not be spelled correctly, and I cannot test it at all. The Idea is to split the Input Voltage between the pins so the Analog Value is separated. MetalGear_Honk
  13. Hi Interesting idea. Can you give some details on how you implement these two functions? I know how to setup an HID Device or Multi HID's on one pro Micro. But I never tried two different Functions on one Device. Sounds very interesting. as for my take on such a problem (besides the open source FFB ) would be to send Axis/Button Data to the Lua and use this way to input "Joystick" functions into DCS. MetalGear_Honk
  14. Hi I don't think that you can send this information to a HID. But I am not sure. I know that PID-HID devices have a very strict Protocol how to send and receive Why do you want to use a HID? Wouldn’t it be easier to use an Arduino Serial protocol? MetalGear_Honk
  15. Hi I haven't used these specific ones. But it looks like you need to connect the common pin to ground (the one that goes on the inner ring) and each of the other pins to a corresponding input. MetalGear_Honk Edit: the version that you are building needs to connect to a ADC input. and you need to check the Value that you get.
  16. Hi The Raspi has a build in USB hub so it cannot become a Slave Device. But you can use it as it is (a full working Computer) and connect it to your Gaming PC over Network. MetalGear_Honk
  17. Hi The print is only for testing. I am Planning to cast it in Aluminum went I am satisfied. I have a second version build out of Aluminum Profiles. (Paleti) but it is too heavy for my small testing Motors. The printed version is more like a desktop mount. I have not studied all of your code but it looks like it is at the same point as the one I did. It is much more readable (looks like you work in a bigger Team more often) For working together: happy to be part in your Project. Now for the problems: As I said some posts before I don't think the 32U4 can handle sin or Direction calculations. So there will be need for alternatives. LUT comes in mind but that would require more space in the MCU. That would mean to get les Effects stored in the first place. I think I need to take a closer look in your version. Maybe we can work it out together. For the start I managed to add some more Effects in on my version that should be easy to port to your side. Next would be inputs: do you plan on using the Internal ADC? As it is only 10bit. I was thinking on using an ADS1115 for its 16bit MetalGear_Honk
  18. Hi It is not my Thread but I think I High jacked it at some point. I know of the FFB Adapter as it was part of my initial idea. And I think the code I put together as still some parts from your sources. The mechanical design is only a basic idea and a STL file that I put up here in this thread. For the Circuit I use a STK600 with a ATMEGA32U4 for testing but a Arduino micro is good as well (same MCU) The plan is to add an ADS1115 for precision and some Daisy Chained Shift registers for Buttons/Rotaries. The output is as you said an H-Bridge so a PWM and two directional Pins for each Motor. My test Version is in this thread as well ... somewhere. 20171123_203833.jpg JOYSTICK_Test.zip MetalGear_Honk
  19. Hi all Now that summer is reaching its end I have more time to work on the Software again. And here the problems start: First I am still not happy with the effects. The sin function is my main problem at that point. I cannot figure out how this is defined. Next problem is to calculate the Forces /PWMs without using floating-point operations. These are too time consuming for the MCU Second is the Motors. DC Motors have a nonlinear Power/ PWM curve and we need to find a solution to make it changeable easier. I was thinking about a lookup table but the ATMega is lacing the space to add it. As we need to store the predefined effects as well. And last I am running into Timing problems again. Whenever I try to add some functions to the Inputs (ADC or shift registers) the Device gets unstable. Baseline of most of these problems is the MCU so I am starting to think about an Alternative. First would be the stay with the ATMEGA32u4 and try to keep it slim and fast. Next in line would be an Atmel SAM3 or SAM D10. But I haven’t used any 32bit controller. These come on the Arduino due. So they are easy to get. Here I am not sure if it would be possible to boot it as a HID Then we have the Raspberry Zero but that would need a lot work to be recognized as Device. Then there are the PIC / PIC32 MCU's but I think there will be some problems with the Compilers. These become quite expensive when we need more internal space. Last Idea comes from my Working Colleges (thanks for that) Implementing a Virtual USB Device and passing ready processed Data to a Physical device (UDP/USB-serial something completely different. But here we would need a Person with more experience in Driver Development (not my best region) EDIT: Another idea is to use multiple MCUs but the communication would be difficult Maybe someone has some more ideas? Or can help in making a decision? MetalGear_Honk
  20. Hi For testing your setup you can use mostly every DC Motor you can find. From toy cars to the opening Motor of an old CD-drive. All you need is an H-Bridge that can handle the current. If you go for high power Motors the Sabretooth boards are the ones you are looking for. For tests you can use the cheap l298 chips. For the problems about Stepper / Servos / DC Motors: Steppers use impulses to move a distance Servos use PWM to move to a Position DC motors are simply on off. To set a tork value to a DC we reduce the power to it by using a PWM signal. And the H-Bridge is only necessary for direction control. Steppers and Servos use all there tork to get to a fixed position. MetalGear_Honk
  21. ReHi I think i found a few more things. here is the new Einlesen Function: void einlesen(void) { ADMUX = (ADMUX & 0xF8)|(1<<MUX0)| (1<<MUX1)| (1<<MUX2); // ADMUX =(1<<MUX0)| (1<<MUX1)| (1<<MUX2) ; ADCSRA |= (1<<ADSC); while (ADCSRA & (1<<ADSC) ) { } // ADMUX =(1<<MUX0)| (1<<MUX1)| (1<<MUX2) ; ADCSRA |= (1<<ADSC); while (ADCSRA & (1<<ADSC) ) { } // XAchse = ADCH; XAchse = ADCW; ADMUX = (ADMUX & 0xF8)|(1<<MUX1)| (1<<MUX2) ; // ADMUX = (1<<MUX1)| (1<<MUX2) ; ADCSRA |= (1<<ADSC); while (ADCSRA & (1<<ADSC) ) { } // ADMUX = (1<<MUX1)| (1<<MUX2) ; ADCSRA |= (1<<ADSC); while (ADCSRA & (1<<ADSC) ) { } YAchse = ADCW; } and a new SetupHardware: void SetupHardware(void) { MCUSR &= ~(1 << WDRF); wdt_disable(); clock_prescale_set(clock_div_1); ADMUX = 0b01100000; ADCSRA = 0b11000110; // ADCSRA |= (1<<ADSC); // eine ADC-Wandlung while (ADCSRA & (1<<ADSC) ) { } (void) ADCW; TCCR4A = 0b10100011; TCCR4B = 0b00000011; TCCR1A = 0b00000000; TCCR1B = 0b00001010; TIFR1 = 0b00000010; TCNT1 = 0; OCR1A = 2100; //vergleichs wert 1400 //OCR1A = F_CPU / 1000/8; TIMSK1 = 0b00000010; // Joystick_Init(); // Buttons_Init(); USB_Init(); } I am in a Hurry so you need to insert them in your Version Manualy. MetalGear_Honk
  22. Hi I am not able to reproduce this behavior. I have added a new version. For testing. You should be able to use the Data Pin to trigger the first Button. For the axes: I can set them manually in the source. So the HID Descriptor is OK But there must be a Bug in the conversation somewhere. The Motors are driven correctly in relation to Axis. But the Axis are not send to the PC. I will keep searching for it. MetalGear_Honk JOYSTICK_Test.zip JOYSTICK_Test.zip
  23. Hi The Numbers in the comments are mostly as a reminder for me how many Buttons/Axis I have in my Hardware setup. Sorry for that. The RepID is simple the Number of the Device on that controller. We can declare more Devices in one ATMega. But for now it is simple an 8Bit with the Value 1 written in it. As far as I can see there is nothing wrong with the Descriptor or the Report. Can you try to load the Hex file that I uploaded last time? It was included in the Sources. That version was running on my test setup. I am setting up some Test Rig now but I have only very basic equipment where I am at the time. MetalGear_Honk P.S.: I think I found the Problem. The Daisy Chain part is not working Properly. To test it you need to delete the part between" //---Read Daisy Chain " to "return InputChanged;"
  24. Hi No problem. I will try to help as good as possible. The Struct is the correct one. And for counting the Bits: Simple take a Variable int8 for 8Bit int16 for 16 Bit And multiply by the number of Declared Variables. int8_t repID; = 8 Bit int16_t axis[8]; = 128 Bit int8_t Buttons[4]; = 32 Bit int8_t Hat[2]; = 16 Bit Gives a total of 184 Bit That is the number of bits that our Program sends to the PC Now we need to find out how many Bits we have Declared in the Descriptor The Descriptor is in the Descriptors.c USB_Descriptor_Report_Data_t if I remember correctly It is a list of Hex Values We need the count and the Size Normally I have it written after the // there are always two Hex Values separated by a "," First Value is the description (0x75 for Size and 0x95 for count) The second Hex is the Value we are looking for (0x01 for one or 0x10 for 16) So there should be a line like 0x75, 0x20, // Report Count 0x95, 0x01, // Report SIZE That is the Value for the Buttons 32 Buttons with the size of one Bit (on/off) For the axis it should be 0x10 for Size as it is a 16 Bit that I was aiming for. The Head switches are 4Bit (0x04) as they have four Directions. As a fast test of your code simply set one bit in the ReportData part Like ReportData->Buttons[1] = 0b00000100; This needs to go at the end of the GetNextReport function. MetalGear_Honk
  25. Hi Still working from memory here. But it looks like a mismatch between Descriptor and RepertData. In the Joystick.h is a struct for JoystickReport_Data You need to count the Bits. And compare them to the Descriptor Bits declared. Report sizes * report count. Of all integrated functions (Axis, Buttons...) If you have a mismatch here the PC will not get any data. MetalGear_Honk
×
×
  • Create New...