Jump to content


  • Posts

  • Joined

  • Last visited

About DanTDBV

  • Birthday 07/09/1972

Personal Information

  • Flight Simulators
    DCS A10C CA FC3 UH-1H
    GrandPrix Legends
    Richard Burns Rally
    Xwing TIE Fighter
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Hannibal Your project is just so cool. I would love to do something similar, but I don't think that i have room for it. When I am done with my current controller plans I will have 3 modified T16000m's (All buttons in grip), DIY Right hand Warthesque throttle grips on a Saitek Throttle quadrant, DIY Collective, Selfcentering CH Throttle Quadrant and more. I look very much forward to seeing Your next update. Happy Simming
  2. Thank you for the headsup rel4y. I agree on the 8 axes. The 16 axes was from a 2014 reply from mega_mozg. I am going the shift registers way. I already have some of Debolestis Shift register 8 and 16 boards and I intend to order a set of his 32 boards as well. I have also gotten some of the ALPS 5 Way switch boards. I also intend to get some of your 4021 boards. I expect it to be 10 of them, but I will have to see what economics allow. I found possible use for the MCP3208. It could be for something like a Forklift simulator- or Farming simulator functions controller. I assume that the grounding and decoupling is also equally needed for the MCP3202 and MCP3204 as well? I have read about grounding and decoupling and get the gist of why it is needed, but just know that I will not be able to create anything of practical use with that knowledge. Just as I know that I do not have the motorskills for SMD soldering. Yeah I have ruined a couple of projects learning that. Happy Simming
  3. Thank you very much Debolestis. I very much appreciate it and look forward to being able to order the resulting PCB’s. I am sorry that it has taken me this long to reply. Life have taken its share of time. My Grandmother lost a lot of weight in December. In the middle of January she was diagnosed with cancer and trouble with some of her inner organs. A first operation didn’t help and my German cousin from Australia, dropped everything and came up here to stay with Grandmother. My cousin and I hadn't seen each other for 38 years, so I went there to spend some quality time with our grandmother, my cousin and her daughter. A second operation has helped and Grandmother can eat and is feeling better and my cousin has returned to Australia. Happy simming
  4. From the descriptions at Digi-Key the CI/P MCP320X chips are 12 bit and the I/P MCP320X chips are 10 bit. One reason is to free up available pins on the Pro Micro and another is to minimize the number of wires needed from a Pro Micro board in the controller base to a MCP and one or more shiftregister boards in the button/minijoy grip on a stick or collective. If my assumption that I only need 1 ground wire and 1 VCC wire to connect the MCP and the first shiftregister is correct, then I will only need 8 wires from a Pro Micro in the base to an MCP and first of however many shiftregisters and buttons I can fit into a grip. To be more precise, what I am wishing for are boards with input connections for wires from an Arduino board and output connections for wires to the supported number of potentiometers. For my Warthogesque righthand grips on Saitek Throttle Quadrant project, I currently intend to put the Pro Micro in an external box at the base and a MCP3202 and 2 shift registers in the big grip and a shiftregister in the small grip. I am considering converting the Saitek Throttle to MMjoy2 and then I would need a MCP3204 and a shiftregister in the base. For the collective I intend to make, I am considering 2 minijoys in the grip (4 axis), dual throttle (2 axis), collective (1 axis) and zoom (1 axis). Here I would use a MCP3204 in the grip for the minijoys and another MCP3204 for the throttles, collective and zoom. As for buttons and switches I would jam up the grip with as many buttons as possible and the shiftregisters as needed. I am considering making the base into a buttonbox, so that will also get shiftregisters. I was considering the MCP3208 for the collective, but realized 2x MCP3204 would be better for that. At this point I don’t have full use for the MCP3208, but I could find it later and others could have uses for it. I also already have some of them. Mega_mozg explains the MCP possibilities better: From SimHQ mega_mozg Quote and reply’s Quote Firmware has support for up to 128 buttons + 10 axis inputs (2 axis reserved for mouse emulation, Windows Game Controllers see up to 8 axis), number of buttons use depend on Arduino board number of pins available. Possibility to use for joystick: 128 buttons + 2 HAT's (8 buttons) + 8 axis Possibility to use for mouse emulation: 3 buttons + 2 axis Possibility to use for keyboard emulation: 12 buttons (or 15 without "mouse") To maximize the MCU (Arduino board) pins use: For axis - MCP3208 external ADC, what allow use 8 channel 12 bit (this free 4 pins on Arduino and allow 8 analog axis inputs) For buttons - shift register IC 74HC165 or CD 4021B (this free 3 pins on Arduino and allow UNLIMITED button sources chaining one Shift Register IC in another, each manage 8 buttons) Reply 1 now only one difference between any board - is a available pins count. Sparkfun[promicro] - total 18 pins, and 9 can be used for internal(onboard ADC) axis. Arduino[leonardo] - total 23 pins, 11 internal axis. Arduino[micro] - total 24 pins, 12 internal axis. PJRC[Teensy 2.0] - total 25 pins, 12 internal axis. JRC[Teensy 2.0 ++] - total 46 pins, 8 internal axis. so if you want more axis, you can use SPI connected external ADC: a) "kma200" magnetic field angle sensor + 13 bit ADC; b) "MCP3201" 1 channel 12 bit ADC; c) "MCP3202" 2 channels 12 bit ADC; d) "MCP3204" 4 channels 12 bit ADC; e) "MCP3208" 8 channels 12 bit ADC; f) "MMSENS(MCP3202+KMZ60)" magnetic field angle sensor KMZ60 + MCP3202 12 bit ADC + trigonometric math at controller, my new project digital sensor; SPI is a very easy to use, just connect power and ground from controller to ADC and connect SPI lines MISO/MOSI/SCK and CS(chip select). pin "CS" are individual for ADC, other pins is common for all ADC's connected. Reply 2 Originally Posted By: tirta "so for pro micro, there are 18 pins. If I use 6 for axis, there are only 12 pins left for buttons? so 16 axis with 64 buttons are not possible for pro micro? Are these correct?" it is correct only if you want to use internal ADC. but with two "mcp3208" connected to "pro micro" you can access to 16 axis(used 2 pins to "SPI-CS"), and you have 16 pins to buttons 8*8 = 64. The reply’s and example can be found on this page at SimHQ: https://simhq.com/forum/ubbthreads.php/topics/4024754/5
  5. That sounds really great In this context I would like to use ordinary joystick potentiometers. I have a fair number of them pulled out off different controllers old and new. They have different shapes, sizes and resistances, but that shouldn’t matter as I would like for the outputs and inputs to be for wire connections. Just like you have it on your 4021 shiftregister pcb’s. It is not only the 3208 I am wishing for, it is also the 3202 and 3204. The MCP3202 has 2 outputs: CH0 and CH1 and can control 2 pots. I would use this for a mini joystick in a buttonhead added to an existing throttle like the Saitek/Logitech Throttle Quadrant. The MCP3204 has 4 outputs: CH0, CH1, CH2 and CH3 and can control 4 pots. It could be for a collective with a mini joystick, throttle and the collective axis. The MCP3208 has 8 outputs: CH0, CH1, CH2, CH3, CH4, CH5, CH6 and CH7 and can control 8 pots. I am considering using this for a collective with 2 mini joysticks, dual throttle, collective and a zoom axis.
  6. Hello Debolestis First I would like to thank you for all that you have been doing for the community. I very much appreciate it. Have you considered doing OSH Park pcb’s for the MCP3202, MCP3204 and MCP3208 IC’s for use with MMjoy2? Something in the same vein as your shiftregister pcb’s. I am not asking because I don’t want to do it my self, but because I unfortunately lack the skills, instincts and knowledge to do it. Trying to make circuits is like gibberish to me. I know what the components do by them selves, but I have absolutely no grasp of what happens when combining them. I haven’t seen them offered up anywhere. (Could be my lack of Google Fu.) I have seen rel4y’s MCP3202 pcb, but smd are beyond my eyesight and motor skills. I have a hard time believing that I am the only one that could use those kinds of pcb’s. At the moment I need them for my Warthogesque righthand grips on Saitek Throttle Quadrant, Leopard 1 A5DK gunners grip/buttonbox combination and a righthand 2x twist Throttle Collective. I already have some of your 1 and 2 chips 4021 boards and have just ordered a number of your ALPS boards for these projects. I for one would be very grateful, if you where to do this. I am pretty much convinced that there is others out there, that would be as well. Here are the pinouts for the MCP’s and a circuit example with the MCP3208 by mega_mozg. Happy Simming
  7. There is one here: https://www.digitalcombatsimulator.com/en/files/3306411/
  8. There is one: https://www.digitalcombatsimulator.com/en/files/3306424/?sphrase_id=19818156
  9. I know this is an older post but I thought that this could be beneficial for new users of opentrack. I posted this to the opentrack wiki at the date below. This is with opentrack 2.3.10 Opentrack 2.3.10/Options/Shortcuts The following commands leaves the camera and tracking on. The commands only work while tracking is active. Center Sets the current view as the “Look straight forward” point. This should be done, while being in the expected working pose. This can also be done automatically when starting the tracker, by activating the “Center at startup” option. Make sure that you are in the working pose, before starting the tracker. If the tracker is not centered when using the Start, Toggle or Restart shortcuts, then hit the Center shortcut. Toggle Pauses and locks view movements. (This is what you would hit before and after using snapviews in DCS or IL2.) Toggle while held Pauses and locks view movements while held. (This could be used to keep the view on one panel, while consulting an external checklist and flipping the needed switches.) Zero Snaps your view to “Look straight forward” and locks it. Press again to unlock. Zero while held Snaps your view to “Look straight forward”, when pressed and returns to the current pose when released. Zero and zero while held Pressing Zero then using Zero while held will invert the behavior, looking forward while the Zero while held key isn't pressed. The following commands turns the camera and tracking on or off. They're active all the time while the software is running. Start Tracking Turns on camera and begins tracking. (This can take a couple of seconds) Stop tracking Stops tracking and turns off camera. Toggle tracking Turns on camera and begins tracking. (This can take a couple of seconds), or Stops tracking and turns off camera. Restart Tracking Stops tracking and turns off camera and then Turns on camera and begins tracking. (This can take a couple of seconds) DanTDBV 15/7-2018 I hope that this is a help to someone. Happy simming
  10. And after a little more research. The answer is no. Quote from the opentrack creator: "opentrack only supports directshow cameras, not proprietary camera protocols." Track IR5 uses proprietary camera protocols.
  11. Then again, probably not. A quote from this site: http://naturalpointofview.blogspot.com/p/trackir-criticism.html The TrackIR camera is an optical capture device like any consumer camera, it is however distinguished by its monochrome sensor, infrared filter and dedicated image processing chip. The monochrome sensor affords marginally better effective resolution over a color sensor and the infrared filter makes it work as an infrared tracker out of the box. The dedicated image processing chip is its biggest distinguishing feature which removes unnecessary information from video frames before sending them to the computer to make them smaller and more manageable. When TrackIR was first released in 2001, dedicated image processing hardware was important to minimize the burden on the single core CPUs of the time but modern multi-core processors can easily manage full color video alongside even the latest TrackIR game title. As a sign of this, both the Playstation Move and Xbox Kinect optical tracking systems have opted for software image processing instead of expensive dedicated hardware. The TrackIR camera's dedicated processing is a solution for a problem that no longer exists. The Playstation 3 Eye camera is a small fraction of the price of TrackIR 5 and can match its resolution at a lower frame rate (75Hz), or exceed its frame rate (187Hz) at a lower resolution (320x240), has a much wider field of view (75° vs 51.7°) and also functions as a webcam. It well fulfills the role of an optical tracker, being designed for this purpose and used by the Playstation Move platform which has been widely praised for having no optical tracking latency or accuracy problems. The TrackIR camera increasingly serves as Digital Rights Management (DRM) for the TrackIR software, avoiding piracy by being limited to their camera instead of working with any DirectShow compatible camera. NaturalPoint's motion capture software ARENA makes this more explicit, requiring a $99 USB Hardware Key when no OptiTrack camera is available. The TrackIR camera is looking more like an elaborate USB hardware key for the software rather than a necessary piece of specialized hardware. I would still suggest that you try. In that way others can learn from your experience.
  12. I cannot say if you can, but my guess is that it should be possible. If you can chose the camera and activate it, with something like Skype, then I am fairly certain, that you can use it with opentrack. I however don’t think that you will be able to use the IR LED’s on the camera. The easiest way to find out, is to download and install opentrack and try. Remember to run opentrack as admin. Get it here: https://github.com/opentrack/opentrack/releases There is a very good opentrack guide here: https://forum.il2sturmovik.com/topic/34403-a-complete-guide-to-set-up-head-tracking-opentrack/ There is a primer on IR headtracking in general, but the main focus is on using opentrack’s PointTracker 1.1 Hope this helps. Good luck.
  13. So you are saying that because my main workscreen at 32" only leaves room for 2 x 23,6" side screens, I should not bother? How is it self defeating? Sometimes you have to work with what you got and not what you wish for. If it is that easy and simple, then why is there so many questions in this thread? Yes, if you have 3 similar screens it is simple. When you move beyond that, it is anything but. Part of that, is that it is difficult to find the current and up to date information in here. Google mojo is not with you when you don't know what words you should search for. Sorry about the rant, but sometimes it is frustrating spending 80 to 90% of my available gametime in here, trying to find a solution to a specific problem, instead of playing DCS. I have my screen setup working and are now writing on a how I did it thingie.
  14. For me the labels are working in 2.5.1 Open Beta. I use 5 screens on 2 cards. 23,6" / 32" / 23,6" on GeForce GTX 970 for worldview. 2 x 8" on GeForce GT 710 for MFCD export with TM Cougar MFD's attached. I am now working on a how I got it to work thingie.
  • Create New...