Tekkx

Is there anyone surprised about that? ;) I am looking forward to your code. I have all(!) required hardware on hand. But don't be disappointed, if I replace it later with DCS-BIOS 2.0 :)

Thank you Ian. That's a pitty - not a problem :) So I put these lights to the pantry (hope, not to forget them). Later is soon enough. Cause there are so many other things to screw and solder :)

Hello, everyone. I hope (some of) you survived X'mas :) Yesterday I did a short flight. Just one hour in the air. While some looking around I got a plan: Few weeks ago I found some good old signalling lamps from an old broadcast station (known as "Red Light"). I think it would be nice to use some of them to build the external lights of the A10. As ambient lighting in my cabinet :) So I encountered a little problem: I can't find a solution to export Anticollision Flashlights. OK. Reading and exporting switch's position is easy (thanks to prebuilt code of DCS-BIOS) and I could easily code some blinking or flashing. But this isn't the intention. It would be nice, if my flashlights would flash synchron to the flashes at the wingtips (while dusty wheather or at night good to be seen from the cockpit). Am I blind and so can't find the solution or is there no way? Can someone give some advice?

Hello, dear Community and Admins. Maybe it's my own fault, but I'm running out of options. I received the last notification of new Posts on 1st of Decembre. I double checked if Subscription is ON. Also I took a look at my Spam-Folder. Could anyone give some advice? Thank You.

Dear Ian. I'm on my knees and bag your pardon. I am so sorry wasting your time. PLS PM me with your Bank Account. You should have some beers (or sth. else) on me. There is no problem with "my" code. There is no bouncing. There is no cross-talk. Today, while pretending to do my work what I'll payed for, I did some thinking. First thing at home was to change (just in the code) the PIN of the Test-Button (I use the push-button of the Encoder): No Test-Function (as intended), but also no strange side-effect while turning. So (after some tinkering with a Multimeter) came out my Encoder was broken. Everytime the Rorary did a "klick", the Push-Button gave also a very short impulse. Brandnew and clean soldered (without cruelty while soldering). Just cheap chinese scrap (Thow I know: Everything comes from there). So I replaced it (broke my PCB this way) and after reconstructing circuit paths with thin copper wire it works fine.

Hallo Ian. Thank you for your concern :) Live Data I never brought into business :/ Have to give that a closer look. But this is, what connect-serial-port window shows: FQIS_TEST 0 FQIS_TEST 1 < 2015/12/20 23:03:34.584844 length=12 from=1612 to=1623 FQIS_TEST 0 < 2015/12/20 23:03:34.616846 length=13 from=1624 to=1636 FQIS_SELECT D< 2015/12/20 23:03:34.617846 length=3 from=1637 to=1639 EC < 2015/12/20 23:03:43.169335 length=36 from=1640 to=1675 FQIS_TEST 1 FQIS_TEST 0 FQIS_TEST 1 < 2015/12/20 23:03:43.243340 length=12 from=1676 to=1687 FQIS_TEST 0 < 2015/12/20 23:03:43.274341 length=16 from=1688 to=1703 FQIS_SELECT DEC < 2015/12/20 23:03:44.865432 length=33 from=1704 to=1736 FQIS_TEST 1 FQIS_TEST 0 FQIS_TEST< 2015/12/20 23:03:44.867432 length=3 from=1737 to=1739 1 < 2015/12/20 23:03:44.870433 length=12 from=1740 to=1751 FQIS_TEST 0 < 2015/12/20 23:03:44.892434 length=36 from=1752 to=1787 FQIS_TEST 1 FQIS_TEST 0 FQIS_TEST 1 < 2015/12/20 23:03:44.986439 length=28 from=1788 to=1815 FQIS_TEST 0 FQIS_SELECT INC < 2015/12/20 23:03:45.838488 length=8 from=1816 to=1823 FQIS_TES< 2015/12/20 23:03:45.841488 length=4 from=1824 to=1827 T 1 < 2015/12/20 23:03:45.972496 length=12 from=1828 to=1839 FQIS_TEST 0 < 2015/12/20 23:03:46.063501 length=16 from=1840 to=1855 FQIS_SELECT DEC < 2015/12/20 23:03:47.214567 length=12 from=1856 to=1867 FQIS_TEST 1 < 2015/12/20 23:03:47.295571 length=36 from=1868 to=1903 FQIS_TEST 0 FQIS_TEST 1 FQIS_TEST 0 < 2015/12/20 23:03:47.328573 length=16 from=1904 to=1919 FQIS_SELECT DEC < 2015/12/20 23:03:48.219624 length=12 from=1920 to=1931 FQIS_TEST 1 < 2015/12/20 23:03:48.221624 length=12 from=1932 to=1943 FQIS_TEST 0 < 2015/12/20 23:03:48.225625 length=12 from=1944 to=1955 FQIS_TEST 1 < 2015/12/20 23:03:48.336631 length=12 from=1956 to=1967 FQIS_TEST 0 < 2015/12/20 23:03:48.357632 length=16 from=1968 to=1983 FQIS_SELECT DEC < 2015/12/20 23:03:50.028728 length=12 from=1984 to=1995 FQIS_TEST 1 < 2015/12/20 23:03:50.069730 length=28 from=1996 to=2023 FQIS_TEST 0 FQIS_SELECT INC < 2015/12/20 23:03:50.840774 length=12 from=2024 to=2035 I just turned the Encoder to get this picture. The "strange behavior" is explained by the FQIS_TEST 1 and FQIS_TEST 0 messages. The pointers of the gauge snaps (or twich) unexpected. As I wrote in my Edit (post before), bouncing issue seems to be obsolet. It looks like I had another issue built in :doh: PS: Datasheet: NO.

Today I nailed my (not modeled this way in the Sim) FQIS-Panel together and there is a little issue left: Using a Rotary Encoder (I explain the reason in the "original" post) the Switch in the simulated Cockpit do a strange jump every time I move the rotary. Please rail against me if this issue is already discussed or even solved at other place. I would like to insert some debouncing code at the right place. I don't dare to write into the DcsBios.cpp without consulting the great artificer of DCS-BIOS or other members of this community :) Would it be OK (didn't any testing yet) if I insert a small delay into DcsBios.cpp at line 220??? void RotaryEncoder::pollInput() { char state = readState(); switch(lastState_) { case 0: if (state == 2) delta_--; if (state == 1) delta_++; break; case 1: if (state == 0) delta_--; if (state == 3) delta_++; break; case 2: if (state == 3) delta_--; if (state == 0) delta_++; break; case 3: if (state == 1) delta_--; if (state == 2) delta_++; break; } lastState_ = state; [color="Red"]delay(20);[/color] // or some other value if (delta_ == 4) { sendDcsBiosMessage(msg_, incArg_); delta_ = 0; } if (delta_ == -4) { sendDcsBiosMessage(msg_, decArg_); delta_ = 0; } } Maybe there is a better place or methode to solve this issue. Thank you very much. Edit: (two hours later) I did some tests meanwhile. Maybe it's not an issue of BOUNCING, rather a kind of cross-talk. Reading the stream data (while pause the Sim) showed occuring the code of the "Test" button if just the INC or DEC data have to occure. The Test-Button its self works as expected. That could declare the strange behavior of the Fuel-Quantity-Gauge. My FQIS panel is connected to the MEGA by a 50 cm ribbon cable. I have no equipment to measure the cable its self. I could replace the Encoder by a less cheap one but I'm worried to destroy the PCB. (it's a little bit tied there) So my speculative question (before I destroy sth.): Did you ever encountered such cross-talk phenomens?

Here is the new - thanks to Spelmann - faultless code. I tested it in a improvised Sim-Pit-Environment. ... int fqisPin[] = {53, 51, 49, 47}; // all used OUTPUTS for FQIS int lastFqisValue = 0; // intitial data - last or actual value ... DcsBios::RotaryEncoder fqisSelect("FQIS_SELECT", "DEC", "INC", 39, 41); DcsBios::Switch2Pos fqisTest("FQIS_TEST", 43); // Push-Button of Rotary ... void setup() { ... for (int x = 0; x < 5; x++){ // that's, what I've learned, IS important :) pinMode(fqisPin[x], OUTPUT); } ... } ... void onDcsBiosWrite(unsigned int address, unsigned int value) { ... // FuelQuantityIndicatorSelector by Encoder and 4 LEDs as feedback /* 0: (all)INT - Main and Wings - 0 and 1 are HIGH 1: MAIN - MAIN Tank - 0 is HIGH 2: WING - l/r WINGS - 1 is HIGH 3: EXT WING - l/r EXT Wing Tanks - 2 is HIGH 4: EXT CTR - EXT CENTER Tank - 3 is HIGH */ if (address == 0x1106) { // FuelQuantityIndicatorSelector unsigned int fqisSelectValue = (value & 0x1c00) >> 10; // gives 0...4 if (fqisSelectValue != lastFqisValue){ // check for changed value for (int x = 0; x < 5; x++){ // loops all values if (x != fqisSelectValue){ // search for unused digitalWrite(fqisPin[x-1], LOW); // set unused Pins LOW } // x-1 cause of exception 0 else { digitalWrite(fqisPin[x-1], HIGH); // set used Pin HIGH } } if (fqisSelectValue == 0){ // exception 0: 2 Tanks are notified digitalWrite(fqisPin[0], HIGH); // MAIN digitalWrite(fqisPin[1], HIGH); // WINGS } } lastFqisValue = fqisSelectValue; // set new old Value } } // end void onDcsBiosWrite

Welcome Spelmann. Thank you for attentive reading my bullshit ;) I'm right now not in the opportunity to check this out at the live object. But practically it seems you are right. That means, this line isn't really required. Cause it works very good as it is. Althow a change could take some load off the DCS-BIOS data stream... I'll check this later. PS (edit): I wonder if I don't get a notification of your Post. Subscription is ON... Edit 2: To be more consistent, I changed variable name lastFqisPin into lastFqisValue. This way it makes a lot more sense and my fault is easy to recognize (especially to a beginner like me).

This is the second time I answer my own question :) After thinking and tinkering almost two days I found the solution. My code above is OK. Cause I am meanwhile a little spoiled of using Ian's (almost) ready-to-go solutions I forgot an important fact: My digitalWrite(fqisPin[xx], HIGH); commands avoiding prebuilt DCS-BIOS functions. So I forgot to make-up my OUTPUTs with void setup() { ... pinMode(fqisPin[xx], OUTPUT); ... } Each Output one line and everything is fine. :) Thanx for watching :D

Hello Friends. I did an amazing progress in adopting and also understanding DCS-BIOS. My MFDs (still a construction area) work like hell - including DCS-remote backlite). Today I "cracked" the Fuel Quantity Selector. Due to lack of space I decided to take a rotary encoder. Drawback of an encoder is, you have no feedback, where you are. Means, which state you have switched. So I "invented" a feedback system wich uses 4 LEDs representing MAIN, WING, EXT WING and EXT CENTER tanks. Later will be there a small silhouette of the A10 were the LEDs placed at different Tanks positions. By the way I found an error in german DCS A10C Manual on page 132. Function of Positions MAIN and INT are inverted. This made a little issue while coding my project. My code works fine with a setback: The LEDs are not full fired. They smolder just at around 30 percent. I think it's a matter of unclean C-coding. Cause the matter is so close to DCS-BIOS I place my problem here. I would be so happy if one of you guys could risk an eye on my code. Here it is. I commented almost every line. So it should be self explanating. int fqisPin[] = {53, 51, 49, 47}; // all used OUTPUTS int lastFqisPin = 0; // intitial data - last or actual value ... // FuelQuantityIndicatorSelector by Encoder and 4 LEDs as feedback /* 0: (all)INT - Main and Wings - 0 and 1 are HIGH 1: MAIN - MAIN Tank - 0 is HIGH 2: WING - l/r WINGS - 1 is HIGH 3: EXT WING - l/r EXT Wing Tanks - 2 is HIGH 4: EXT CTR - EXT CENTER Tank - 3 is HIGH */ if (address == 0x1106) { // FuelQuantityIndicatorSelector unsigned int fqisSelectValue = (value & 0x1c00) >> 10; // gives 0...4 if (fqisSelectValue != lastFqisPin){ // check for changed value for (int x = 0; x < 4; x++){ // loops all values if (x != fqisSelectValue){ // search for unused digitalWrite(fqisPin[x-1], LOW); // set unused Pins LOW } // x-1 cause of exception 0 else { digitalWrite(fqisPin[x-1], HIGH); // set used Pin HIGH } } if (fqisSelectValue == 0){ // exception 0: 2 Tanks are notified digitalWrite(fqisPin[0], HIGH); // MAIN digitalWrite(fqisPin[1], HIGH); // WINGS } } lastFqisPin = fqisPin[fqisSelectValue]; // set new old Value } As an extra gift for Newcomers here my code for Backliting MFDs: // Backlighting if (address == 0x114c) { unsigned int lcpAuxInstValue = (value & 0xffff) >> 0; analogWrite(PWM_Pin, lcpAuxInstValue/512); // adopt Output to Arduino-PWM-Scale } // end if Note: I don't want to make the false impression, this code is made just by me!!! That all is based on Ian's great work. I can't stop say Thank You for that. Thank You.

@ fixen and all I did a run with DDU. Everything ran fine. FPS still down. With HELIOS about 20, without about 40 to 60. Gadroc says (googled that): "... activate Windows Aero ..." Now FPS with HELIOS around 50. :) But Windows looks like wet sticky candy. You can't get a thing without loose another :(

Hello. I'm back with my just installed, brandnew GTX 970. (Asus Nvidia GeForce Strix GTX970-DC2OC-4GD5) I am very disappointed. Framerate is still at around 20. This is 5 more than before. If I look into the sky it increases up to 30. My bird stood just at the RWY cause she has no clearence for Take Off at the moment (too much instruments under service condition) :) Two (or three) reasons could be responsible: - I put my GTX580 into the second slot for pluging my third Screen on it (no SLI!) - I have two USB2VGA-Converters for HELIOS- and CDU-screen. - My CPU can't deliver enough data to feed the 970 HELIOS itself consumes about 2 Frames per sec (difference between started or stopped profile) I have ordered some HDMI2DVI and DP2DVI adapters. Maybe this will improve (by replacing the USB-Adapters and plug the screens direct to the 970) systems performance. If not, I have no idea whats next. The good thing is, 970s fans don't move. Temperature stay below 60 centigrades. GTX580 went up to 80 (as it has to do the main work before installing GTX970)

Hello. Should have red this Thread yesterday. I ordered yesterday an Asus Geforce GTX 970 Strix DC2OC cause my FPS are less than 20 and some money came in. They (some different testers) say, that is almost as good as the GTX 980 but much less money is called for. :) If they (DHL) bring that thing tomorrow I'll post my experiences over the weekend. (If my wife gives permission to mount it ;)

I did a small cosmetic to my code (relative to Post #19) ... void loop() { char OSB = MFD.getKey(); // weist OSB den Wert der gedrückten Taste zu while (Serial.available()) { // feed incoming data to the parser parser.processChar(Serial.read()); } DcsBios::PollingInput::pollInputs(); } /// --------------------------- void keypadEvent(KeypadEvent OSB){ switch (MFD.getState()) { case PRESSED: switch(OSB) { // case '1': sendDcsBiosMessage("LMFD_01", "1"); break; case '2': sendDcsBiosMessage("LMFD_02", "1"); break; case '3': sendDcsBiosMessage("LMFD_03", "1"); break; //.... other 65 cases will follow here }} switch (MFD.getState()){ // gives PRESSED, HOLD or RELEASED case RELEASED: switch(OSB) { case '1': sendDcsBiosMessage("LMFD_01", "0"); break; case '2': sendDcsBiosMessage("LMFD_02", "0"); break; case '3': sendDcsBiosMessage("LMFD_03", "0"); break; //.... }} } ; ... This works like hell :) If I could put the "message" in the matrix it would be more easy. This afternoon I spent with crimping 0.1 connectors... :crazy:

At the first look I thought this was my cockpit :) My CDU Screen is also on VGA. I'll keep it that way also. But since the first day I don't want to go by Touchscreen. Too expensive. Meanwhile I have so much money spent to parts and tools that I would be able to afford 3 Touchscreens instead of that. My LeftSideController (inspired by the original UFC) is driven by an Arduino Leonardo with MMJoy2. It works very well, but just in one direction. There is no Backlight e.g. Thats why I'm so happy with and grateful for this priceless tool named DCS-BIOS :) Right now I have more Flight-Equipment as I ever wanted. If I remember: A little more than one year ago it was a good experience to fly arround with Helikopters in BC4... That's history. Now I finish my 18" with MFD and some Knobs to manipulate shown instruments as Clock, VVI, Fuel Indicator and some others. The most important gimmick is, I can remove the whole flight-stuff with two hand movements :) Then will follow just(!) an AAP and an Electric and an Laste and an Comm and an... I CAN'T SEE AN END (sorry for screaming) :D ... and a new GPU. My FPS are less than 20 :(

So, my Friends. Sometimes is it enough to know that there is someone with you. I found a solution. And it works. The code based on an example at Arduino Playground and DCS-BIOS tempate sketch. // an attempt to realize ButtonMatrix in DCS-BIOS by Tekkx :) #include <Keypad2.h> #include <DcsBios.h> #include <Servo.h> /**** Make your changes after this line ****/ const byte ROWS = 3; // quantity of rows (later 8) const byte COLS = 3; // quantity of columns (later 9) int PWM_Pin = 12; // Backlighting AUX (Buttons of MFCDs int MCB = A5; // all other Non-Matrix-Buttons and rotarys follows here char OSB[ROWS][COLS] = { // Define the Keymap {'1','2','3'}, {'4','5','6'}, {'7','8','9'}, //{'0','a','b'}, Still under construction //{'c','d','e'}, //{'f','g','h'}, //{'i','j','k'}, //{'l','m','n'} }; // Connect MFD Rows and Columns to these Arduino pins. byte rowPins[ROWS] = { A8, A9, A10 }; byte colPins[COLS] = { 7, 6, 5 }; // Create the Keypad, initialize an instance of class NewKeypad Keypad MFD = Keypad( makeKeymap(OSB), rowPins, colPins, ROWS, COLS ); /* Instantiate a ProtocolParser object to parse the DCS-BIOS export stream */ DcsBios::ProtocolParser parser; DcsBios::Switch2Pos masterCautionBtn("UFC_MASTER_CAUTION", MCB); DcsBios::LED masterCaution(0x1012, 0x0800, 10); /**** In most cases, you do not have to change anything below this line ****/ /* Instantiate a ProtocolParser object to parse the DCS-BIOS export stream */ //DcsBios::ProtocolParser parser; void setup() { MFD.addEventListener(keypadEvent); //add an event listener for this leftMFD Serial.begin(115200); MFD.setDebounceTime(50); // maybe needless } // end setup /* Your main loop needs to pass data from the DCS-BIOS export stream to the parser object you instantiated above. It also needs to call DcsBios::PollingInput::pollInputs() to detect changes in the state of connected controls and pass them on to DCS. */ void loop() { char OSB = MFD.getKey(); // feed incoming data to the parser while (Serial.available()) { parser.processChar(Serial.read()); } // poll inputs DcsBios::PollingInput::pollInputs(); //if (OSB) { //Serial.println(OSB); //} } /// --------------------------- void keypadEvent(KeypadEvent OSB){ switch(OSB) { case '1': sendDcsBiosMessage("LMFD_01", "1"); break; case '2': sendDcsBiosMessage("LMFD_02", "1"); break; case '3': sendDcsBiosMessage("LMFD_03", "1"); break; } switch (MFD.getState()){ case RELEASED: switch(OSB) { case '1': sendDcsBiosMessage("LMFD_01", "0"); break; case '2': sendDcsBiosMessage("LMFD_02", "0"); break; case '3': sendDcsBiosMessage("LMFD_03", "0"); break; } // end switch } } ; // end void /// ---------------------------- /* You need to define void sendDcsBiosMessage(const char* msg, const char* arg) so that the string msg, followed by a space, the string arg and a newline gets sent to the DCS-BIOS import stream. In this example we send it to the serial port, so you need to run socat to read the data from the serial port and send it over UDP to DCS-BIOS. If you are using an Ethernet Shield, you would probably want to send a UDP packet from this subroutine. */ void sendDcsBiosMessage(const char* msg, const char* arg) { Serial.write(msg); Serial.write(' '); Serial.write(arg); Serial.write('\n'); } /* This subroutine gets called every time a message is received from the export stream (you need to define it even if it does nothing). Use this to handle outputs which are not covered by the DcsBios Arduino library (e.g. displays). */ void onDcsBiosWrite(unsigned int address, unsigned int value) { } There maybe some unnecessary code inside. E.G. it sends tho ON-Signal twice on button press before it sends the OFF-Signal when button is released. But this is the closest approach my brain is able to :) Please give me a hand if you find something to improve. If not: Use and adopt it to your own matters.

Hey John. As I wrote at #14 I want to bring a button matrix to run. This should become 2 MFCDs and some other stuff. At the pic at #14 is my 18" to be seen where all these stuff should be screwed on. This all will be connected to a Mega 2560 which is partially configured as a button matrix by keypad.h (one of the latest Arduino Librarys). The Mega is already running and communicating with DCS like a charm. The goal (and also the biggest problem) is to find the interface between output of the matrix and the functions of DCS-BIOS. At post #14 is a very short part of my code to be seen. Just as an example, how far and in which direction I already went. This code isn't a beauty but it works in some degree. Meanwhile I found the function Eventlistener (part of keypad.h) as a better way. (this brings other issues with it... I think this is to diskuss at Arduino Forum) Otherwise that all doesn't makes me happy cause its just a workaround. Not clean DCS-BIOS. It's not DCS-BIOS where the fault is! It's me cause I can't understand so much of this :(

Dear weeb. This was a missunderstanding. :D The "sad view" arises from the 18" (center dash) still without any working knobs and other gismos. And no idea in sight how to get this into business. And I know what you're saying. I do not sleep very well with unsolved "problems" in mind. There is also the paractically working, but still unfinished magnetic switch at my workbench... So I pray for the key to the secrets of The World of DCS-BIOS.

Hello Friends* After tinkering arround for almost two weeks and reading (though reading - not understanding) user and developer guide (Google says "You visited this page 295 times" :) I brought my Keypad to send messages to DCS. This is my construct inside the DCS-BIOS template sketch. It's just a skeletton, later will be there more than 70 buttons in a 8x9 matrix and several rotarys and LEDs (all to mount on my 18"). I think all here know how to make a keypad using Arduino's keypad library. So I cut this part of the code. void loop() { /// --------------------------- char leftKey = MFDL.getKey(); if (leftKey) { switch (leftKey){ case '1': sendDcsBiosMessage("LMFD_01", "1"); // button pressed delay(50); sendDcsBiosMessage("LMFD_01", "0"); // button released after 50 ms break; case '2': sendDcsBiosMessage("LMFD_02", "1"); delay(50); sendDcsBiosMessage("LMFD_02", "0"); break; case '3': sendDcsBiosMessage("LMFD_03", "1"); delay(50); sendDcsBiosMessage("LMFD_03", "0"); break; // and so on } // end switch (leftKey) } // end if (leftKey) Some of you high skilled programmer pros will smile after seeing that. I found no other way to bring the output of the keypad into the holy DCS-BIOS-Mashine. So I can't hold a button ATM (important to reload DSMS e.g) And a 65 switch-case construction doesn't look like a good solution. And it makes me a stomachache cause I know I worked arround the intention of DCS-BIOS. But I'm happy that moves sth. ;) Could some (or one) of you bring me on the right lane? I think there is just a small step to go (but the wall seems to be very high to me) * I count on that PS: Take a look at the pic. It's a sad view. Isn't it? (I mean the central 18" TFT still without any controls) (The LeftSideController works with a Leonardo under MMJoy2)

Wow. It works. That simple. Now I understand why I can't find that file somewhere at WWW :) Thank You very much.

Hello Friends. Please don't beat me... While tinkering around with facetrack (it was a very flat learning curve) I smashed my snapviews somehow. AND - I don't know how and when - I deleted or overwrote my original SnapViews.lua Could you upload a untouched version of this? Please! I promise to do it never again.

Ich danke auch :) ... und ich mache mir jetzt eine Startup-Checkliste, auf der nicht nur die Flugzeug-Instrumente sondern auch SÄMTLICHE Geräte und Hilfsprogramme meines "Sim-Pits" stehen. Und NOCH Eine extra für solche Sachen wie z.B. Export.lua :book: Neulich hat bei mir HELIOS nicht mehr funktioniert. Nach langer Suche und Neu-Konfig fand ich heraus, es war einfach nicht mehr in den Code der export.lua eingebunden. Wieso auch immer. Danke für den Tip. Wenn Sachen zu lange zu gut funktionieren, vergesse ich, wie es gemacht wird :D

That's exactly what I mean :) I know this. And it wasn't my intention to push him (or it). As I wrote: I just want to be prepared :) Right now (means: at my grade of knowledge) I can't share your opinion reg RJ-45. This system is (mis- or ab-)used at many applications. I serv to a broadcast station and see it more and more. 0.1"-connectors ( If you ment that) are circumstantial to use. BTW (not further to diskuss here): To improve my results in soldering SMT I ordered some equipment to do it with some kind of reflow oven. (If you watch my progress at the [thread=146392]Magnetic Actuated Switch Project[/thread] (called: MagicSwitch) you'll know what I mean)

Ah. Damned. I confused Freetrack with FaceTrack... My fault. My attempts with Freetrack aren't successful. So I concentrate my forces to Facetrack (as I wrote earlier in this Thread).