Oakes

Nope, I use the Opencockpits interface + a custom Autohotkey script to generate keyboard inputs to the sim (the script reads the SIOC parameter changes and send appropriate keys to the sim). Currently I get no data from the sim.......wish I could:cry: Just tell me what you need:) Here are the drawings for the collective head (note: the measurements placements etc are not exactly up to the "standard", but since I know which edge etc to start from when I do the milling I simply placed measurements where I knew I needed them, cuts down on the calculating during fabrication ) /Oakes collective_head_001.zip

Instead of having a bunch of threads for my little cockpit build I though I'd make a combined one to post updates in etc Here are the two previous threads: http://forums.eagle.ru/showthread.php?t=32054 http://forums.eagle.ru/showthread.php?t=32392 Update: I've been working on the targeting panel and the collective head during Christmas, both are now fully functional. The collective plate + thumbjoy etc will be painted black (or maybe I should just let the bare aluminum show and just paint the plate). I use the analog thumbjoy to slew the Skvhal sensor, makes it much easier to be precise with the senor. Below are some pictures of the collective head and the targeting panel + links to some youtube videos. Some new vids on the targeting panel and the collective head. /Oakes

Correct. /Oakes

Hi Hannibal Yes, I've tried it. You can assign joystick axes to the skvhal. They are assigned as relative i.e the more you move the stick to the left the faster the skvhal will move to the left until you hit the pan limit for the skvhal. /Oakes

I was planning to do this in software with AutoHotkey if possible. Working example for joystick buttons below: ; ; AutoHotkey Version: 1.x ; Language: English ; Platform: Win9x/NT ; Author: A.N.Other <myemail@nowhere.com> ; ; Script Function: ; Template script (you can customize this template by editing "ShellNew\Template.ahk" in your Windows folder) ; #NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases. SendMode Input ; Recommended for new scripts due to its superior speed and reliability. SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory. 1Joy1:: Send, 1d ; Sends 1d to the application SetTimer, WaitForButtonUp1, 10 return WaitForButtonUp1: if GetKeyState("1Joy1") ; The button is still, down, so keep waiting. return ; Otherwise, the button has been released. Send, 1u ; Sends 1u to the appliation SetTimer, WaitForButtonUp1, off return 1Joy2:: Send, 2d ; Sends 2d to the application SetTimer, WaitForButtonUp2, 10 return WaitForButtonUp2: if GetKeyState("1Joy2") ; The button is still, down, so keep waiting. return ; Otherwise, the button has been released. Send, 2u ; Sends 2u to the appliation SetTimer, WaitForButtonUp2, off return :book:/Oakes

Mumble servern är uppe på 83.233.5.103 om någon vill köra med voice Lösen är nubbe

WELL, FIRST I START BY SCREAMING A LITTLE.....:cry: Here is a good write up on how to connect several encoders to the BU0836 (with diodes):book: http://www.737ng.co.uk/EFIS_BU0836_HOWTO.pdf You can connect up to 6 encoders to the card without using any diodes (which is what I did to test). For an encoder with center axle push there are three pins on one side and two pins on the other. The three pins are for the encoder part and the two pins are for the pushbutton. To do this connect the middle pin of the encoder to one of the analog ground (GND) pins. Then connect the outer pins of the encoder to Column 1 (C1) and Column 2 (C2) respectively. See image here for location of GND, Columns and Rows http://www.lbodnar.dsl.pipex.com/joystick/BU0836pot.png Also, you will need this software to configure the card for encoders. http://www.leobodnar.com/products/BU0836/BU0836_encoders.exe Set the "1-2" type to x1, x2, or x4 transitions (1:1, 1:2 or 1:4) per detent until you get 1 joy input per detent. Use DIView to check this -> http://www.aqza37.dsl.pipex.com/joystick/DIView.zip Now, when you turn the encoder you will get Joy 1 inputs if you turn it one way and Joy 2 if you turn it the other. If you want to reverse this, simply exchange the outer pins with each other. --------------------------------------------- To connect more encoders. Connect the middle pin to any GND (or the same GND as in the example above), then connect the outer pins of the encoder to C3 and C4. Then for Encoder 3 it's GND, C5 and C6 Encoder 4 it's GND, Row 1 (R1) and Row 2 (R2) Encoder 5 it's GND, R3 and R4 Encoder 6 it's GND, R5 and R6 Always remember that an encoder must be connected to consecutive inputs (C1 and C3 wont work for instance). ------------------------- To connect the center axle pushbutton Connect one pin to GND and the other pin to any Column or Row pin not occupied by any encoder (again this is without diodes). /Oakes

http://www.lbodnar.dsl.pipex.com/ http://www.leobodnar.com/forum/viewtopic.php?f=4&t=27 /oakes

Yep, 1 BU0836, two rotaries (one with pushbutton) and 5 buttons and you are done. I've tested it and it works as intended. /Oakes

Murmur är uppe på 83.233.5.103 Pass är nubbe, username är valfritt. Logga in och flytta till general chat kanalen

Ok, jag är med. Även om du inte har någon mick så kan vi kolla att det går att koppla sig mot servern, och du kan ju höra mig åtminstone.

Fixade lite med en mumble/murmur server igår (VOIP - som teamspeak typ). Tror att jag fick igång allt, funkade internt att connecta till mit externa ip nummer iallafall så port forwarden verkar funka iallafall. Kanon ljud var det minsann. Är det någon som är pigg på att testa detta ikväll? så kanske vi kan köra med voice coms när vi lattjar runt i BS nästa gång. Mumble finns här http://mumble.sourceforge.net/ (mumble är clienten, murmur är servern btw)

No keys. You will only get joystick buttons out of the BU0836, nothing fancy. You can of course map these joybuttons to actions within DCS BS (like any normal joystick). I use one BU0836 for my homebuilt rudder pedals, one axis for the twist and two buttons (one for each foot). The foot buttons I use to recenter the TRACK IR and one is mapped to a cockpit down view (to see the schkval) within DCS BS. If you want to use this for keypresses etc you can use Autohotkey to detect the Joybuttons and send keypresses, delays, repeating etc.... /Oakes

The OC mastercard has built-in support for rotary encoders and this works very well IMO. You can map a value to this encoder and as soon as you turn the encoder the value goes up or down depending on the direction you turn. However, when I tried mapping the brightness to an encoder via the built in Keyboard Emulator in the OC/SIOC software it did not work with DCS BS. It worked fine in Notepad so this is something between OC/SIOC/KeyEmulator and DCS BS. Note: I use the KeyEmulator for other commands (like master arm etc) and this works fine. I've used a BU0836 from http://www.lbodnar.dsl.pipex.com/joystick/ for the rotaries for the ABRIS and it works fine. The BU0836 will as an example output Joy1 if you turn left and Joy2 if you turn right. I think the BU0836 has support for up to 16 encoders if you use diodes but you need to check with Leo to be sure. I've only tested with two encoders so far. /Oakes

Ok, so let's see if I got this correct, since water content only depends on the temperature of the air independent of the presence of clouds or rain, icing will form from about 0 deg C to -40 deg C OAT with 0 being the worst in terms of icing and -40 not so bad, clouds or no clouds. Another question while we're at it, is the OAT is implemented as a perfect standard atmosphere? --> meaning a 1000 feet increase in altitude means about -2 deg C in temp. No funny inversion layers in other words:smilewink: /Oakes

How is icing conditions modeled in DCS BS btw? High altitude doesn't normally automatically equal icing nor does a low temperature (as far as I know the colder the air gets the less the risk of icing because the moisture has already condensed into rain i.e cold air = dry air) For icing to form don't you need moisture either in the form of clouds or as rain (freezing rain or drizzle being the killer here)? As an example in Cumulus clouds with a temperature of 0 to -20 degrees C the risk for icing is high, in the same type of cloud but with the temperature at -15 to -40 the risk is medium and below -40 the risk is low. In rain or drizzle at 0 degrees or below get the h**l out of dodge before you are turned into an icicle:helpsmilie: So clear cold air no problem with icing in DCS BS...or are there other factors for rotor aircrafts? /oakes

I use the OC cards, the support for Keyemulation is very basic. It will work for simple commands (like "m" for master warning button). There is for instance no way to send left/right shift or ctrl only shift and ctrl are available. However if the PCIP delivers direct access to the sim then the OC cards will likely be a good solution. /oakes

Sorry, no I do not think Autohotkey can separate between two keyboards (key inputs probably happens at a lower level in the OS). However, Autohotkey can separate between different joysticks. Perhaps that will help If you want a simple switch to keyboard emulator I recommend the Xkeys Matrix .http://www.xkeys.com/custom/xkmatrix.php. With this product you can send different keystrokes for press and release, repeats etc /oakes

Finemangs, då provar vi det ikväll istället. Fanns/finns det någon TS eller Mumble server eller liknande?

Yep, currently I have no feedback from the sim. I just wanted to show that when we get the PCIP I can get the info up on the displays etc. /Oakes

Hittade sporadisk servern igår när jag kollade. Kunde inte connecta dock + visades ingen info om namn, antal spelare etc i listan (Refresh hjälpe inte) utan bara ip numret. "Connect to IP" funkade inte heller. Någon som har några ideer? (har kört lite på andra servrar och då funkar det fint)

25 USD = 200 sek = självklart köp :-) direkt från ED t.o.m.

Hi Takamba Yep, that might be a problem. However, you can use a program called AutoHotkey to fix this. In theory, Autohotkey can catch Joystick buttons (use Keywait or Keystate command) and then resend them to the sim. 1. Catch the statechange for Joy1 from off to on. 2. Send Joy2 impulse to the sim. 3. Catch the statechange for Joy1 from on to off. 4. Send Joy2 impulse to the sim. and so on... The reason fro using different Joy buttons is that Autohotkey cannot prevent the sim from also seeing the joybutton statechanges. /Oakes

M90 finns, bara att välja i ME (följer alltså med BS från början)

Hi Swede here as well. Just name the place and the time. /oakes