Sacarino111

Hi Aunty Maybe the problem is "the latest IDE version". I'll check this on mine, but now I'm a bit out of time (""money") for a test, but I hope that shortly I'll give a try. Cheers. Saca111

Hi, Aunty. Actually, I don't remember the messages the arduino IDE gives back after upload, but I don't think it's normal. Did U changed something in the sketch itself? Looks like a " typo"error. This declaration is in the 3d line of the actual sketch, make sure the "{" has it's according "};" three lines underneath. Try downloading again the arduino sketch and upload it again. If not, try a different IDE version, or maybe is a "board uodate" (a function inside the IDE) that has to be done or undone... Anyway, I will be doing a new joystick next week, so I'll be able to check this out. Hope it helped. By. Saca111

About the "movement" you said, if you uploaded the sketch to the Arduino with the "axis" option on, you will need to short all the 8 first analog pins (the ones set for the potentiomenters) to ground (in whatever ground pin available). If you don´t plan on using axis, just upload the sketch with the last lines "commented", but with the DFU gate of yours, I would go for connecting all analogs to ground. What you describe is a"ghost effect", from the analog pins. Saca111

Hi, Bacon Glad you mannaged to resolve it! I had the same problem at first: the Mega I bought did not have that pins fo DFU mode, so I had to buy a new (original one) with that feature implemented. Second thing: the matrix you posted looks right, except the fact that the on-off-on will work better if you plug the row to the 21 to 24 pin (the 4 first lines. blue red yellow and black).Otherwise, the button will stay on all the time. These are for"rotary encoders or similar". Besides thar, I think the rest is OK! Again, if I can help, feel free to ask. Saca111

Hi, Bacon8or. I'm sorry this didn't help. If what glynd said doesn't work, I suggest U: 1 buy a new one, be sure U can put it on DFU mode 2 Upload the arduino sketch, put it on DFU mode 3 INSTALL the drivers from FLIP 3.4.7 first. On your first reply, you didn't mention that part. Unplug it 4 Plug it back 5 once it's recognised on your system, then follow the instructions glynd wrote above. 6 Unplug, plug it back. It shoud do. Saca111

Hi, Bacon8or. I checked my system, and I'm not sure, but your path doesn't look correct, at least to me and my instalation: You typed @"C:\Program Files(x86)\Atmel\usb\atmel_usb_dfu.inf", but for me it should be @"C:\Program Files(x86)\Atmel\Flip3.4.7\usb\atmel_usb_dfu.inf". I can't tell if that's the problem, but give it a try! C U, Saca111

Also,I did in win7, wich I think shouldn't be a problem, but who knows! I U have a win7 based PC, try it in it. Other tip. After each change, disconnect an connect back the Arduino. I mean, unplug and plug back, not onlu reset. Saca

Hi Bacon... I think the address for the Atmel driver you entered is wrong, or you made in an incorrect manner. Let me check how I did it "back then when"... and I 'll tell U if U did it right or not. Cheers, Sacarino111

I use two Thrustmaster F16 mfds, wich are perfect for the task, and I made a third one with "123 design", close to the shape of the center F18 MFD. I can share the model of it with U, as I 3d printed it (not at home, no 3d printer yet). It has some things that could be made different, but it was my first and only try. Cheers

The story of my life! I'll send some pictures of my rig, the moment I figure out how to get the pictures from my phone to the PC!

I was going to write the same! Little bug, bug it would be nice to see where you are taxiing

For the matrix, I found the easyest way to use those small protoboards. Connect all the "row" pins to one side of the Prot and all "columns"to the other side, and U'll have 4 pins for each row or column, that U can split later to accept more inputs.https://www.conectrolinformatica.com/arduino-accesorios/3464-placa-protoboard-mini-de-170-puntos.html: Look at this https://www.conectrolinformatica.com/arduino-accesorios/3464-placa-protoboard-mini-de-170-puntos.html

Well, yes. I also got syuck at compiling! Tryed almost everythink I could imagine, but it's like a link, or path inside a file is wrong. The only think I can imagine is yhat the Lynux version I'm using is not the same (in time) so they have some different behavior. Looking to install Ubuntu 9.10 on a raspberry Pi and isntall the compiler of the same era and do some tryouts. I'll keep U infomed. By the way, if U need any hepl on making the matrix, I already did it three times, so I can give some turnarounds or ideas. Feel free to ask me! It's an impressive solution, really, and when you'll make it work, you 'll be amazed by the results. Bye

I had the same problem, added the following lane (Ithink, 'cause I made so many changges I m finally lost) in "CVPJoystick.c" : #include "Arduino-joystick.h" #include <../../LUFA/LUFA/Drivers/USB/Core/AVR8/USBController_AVR8.c> !!!!!!!!!!THIS ONE!!!!!!! But I finally got to a different problem: ... a,-adhlns=./cvpJoystick.lst -I../../ -std=gnu99 -Wundef -MMD -MP -MF .dep/cvpJoystick.o.d cvpJoystick.c -o cvpJoystick.o In file included from cvpJoystick.c:63:0: ./../../LUFA/LUFA/Drivers/USB/Core/AVR8/USBController_AVR8.c: In function ‘USB_ResetInterface’: ./../../LUFA/LUFA/Drivers/USB/Core/AVR8/USBController_AVR8.c:164:3: warning: implicit declaration of function ‘USB_Init_Device’ [-Wimplicit-function-declaration] USB_Init_Device(); ^ ./../../LUFA/LUFA/Drivers/USB/Core/AVR8/USBController_AVR8.c: At top level: ./../../LUFA/LUFA/Drivers/USB/Core/AVR8/USBController_AVR8.c:190:13: warning: conflicting types for ‘USB_Init_Device’ static void USB_Init_Device(void) ^ ./../../LUFA/LUFA/Drivers/USB/Core/AVR8/USBController_AVR8.c:190:13: error: static declaration of ‘USB_Init_Device’ follows non-static declaration ./../../LUFA/LUFA/Drivers/USB/Core/AVR8/USBController_AVR8.c:164:3: note: previous implicit declaration of ‘USB_Init_Device’ was here USB_Init_Device(); ^ ./../../LUFA/LUFA/Drivers/USB/Core/AVR8/USBController_AVR8.c:190:13: warning: ‘USB_Init_Device’ defined but not used [-Wunused-function] static void USB_Init_Device(void) ^ make: *** [makefile:694: cvpJoystick.o] Error 1 pi@Sacarino111:~/ArduinoUSBJoystick/firmwares/cvpJoystickTest $ ^C I followed all the lines descibed but got to an end, as I canunderstand, the "static non static" issue. IF any one could help us,it would be much apreciated. Cheers, sacarino111

Well, apparently it's working OK! I still have to wait until some reboots and other bugs, but at least it's not creating any trouble, so far. Thanks again. A. "Sacarino111" Petrovic

Wow, Thanks I'll try. Right now, I'm overwhemed, and trying to fully understand this app U linked to me. Again, thanks a lot. I'll tell my tale!

Hi Overpro. Nice work of yours! I even made three setups and they all work great but.... they all are called the same, so from time to time my Pc goes mad and shuffle the joysticks around so I have to reassign or unisntall and reinstall all three and see iif they are reassigned correctly, or restart all over again until they match the previous configuration. A nightmare! So, I did try all the thinks I can imagine (no programing knowledge, whatsoever), managed to change name in "descriptors. c", and came to a stop when compiling. I did try (with the help of a relative) all the compiling tricks we could, including what Lilted86 (thread n 234 and 235 did) and nojoy! So, could you help me with some detailled instruction, or even better, can I send you the package with the changed names and you do the compiling? Thanks in advance and I ll be waiting for your answer. Sacarino111

Hi everybody. I don't know if it's here where I should post it, I don't think it's a bug so... I miss a keybinding for the ECM selector, the thing right of the Countermeasures emergency lever, behind the stick. It would be a nice addition to my cockpit. Also the Radaraltimeter right of the righthand knee, I can't find the keys, so I assume there are no keys. I kindly ask for their inclusion on the (great) model. See U abd thanks for the ard work and the module. A. Petrovic, Sacarino111

Hi. Great update!!!NO amber inputs!!! Stil haven't tryed it (my job is obstructing my DCS playing!) but can't wait to see it. Cheers P.D: Soys grandes, a ver cuándo sacáis el Mirage F1, que si es así cómo trabajáis lo compro! Saludos Saca111

Hi, I also had this impression, but I agree that it's an intermitent one. In some flys it works and on other no. unsolved misteriesof our days...

Thanks Vbora. Muchas gracias. For example, Front pannel radio on CC variant is OK, on EB not , but I can wait, no problem...

Hi everybody, and thanks for the update. Great improvement! I don't know if this is the place for my questiones but I can't find the thread for bugs... My questions is: I wanted to bind the different key to joy buttos, now that is possible (radio coms NAV etc ) and I find the entry on amber color, and the schedule for the joy button greyed out, so I can't enter the button, or there is no response in the cockpit, for some of them only. The UHF radio in the front pannel works (finaly) ok! And it's different for the CC version than for the EB version: CC is better than EB. I'm very happy with the advance, don't get me wrong, but I feel desorinted with this color stuff. Any help would be weel received. Cheer from Spain. Saca111

Hi. You can use it on CCRP mode, find, designate and lase, you won't have a release nor azimut cue but it's possible to release "by eye". If you keep trigger st1 pressed and you released ok, the bomb will track. the problem is ti find the target... I do press OVRD on MFD to stow it, then preess it again to unstow and the TGP is now boresighted. Then normal slewing to find targets and designate and lase. What I have no clue is on haow to LSS another budy lase! I things it's not yet implemented. Been searching on manual, but TMS is not able to enter LSS mode yet. Saludos. Saca111

Hi I had this same problem, and solved it just by turning the MIDS knob to the right (right hand console, all way back, past INS knob and GPS and DL levers). You should have it available. Salute. Saca111

Hello and happy 2019. I'm still on my kind of suggestions, witch are: Buttons, please!, I mean, I'm more the kind of cockpit builder, and I lack the possibility to move buttons and dials from my pannels. I know all the team is busy and working their best for other important things, but I would apreciate a lot some buttons to be properly defined and/or set, as: - Radio dials - TACAN and VOR/ILS knobs - Lights pots. There may be more , but those ones are (to me) the most used ones, so I'd reaaly apreciate a solution to them. Waiting for the F1 to be released, I salute all the team and thanks it for the great job. A. Sacarino111 Petrovic