Tekkx

I have ordered some of these amazing new NANO every. In China. So they will run a while. If these arrived, I'll do a test with that. Everys have a faster CPU... It's a small chance, but a chance. Stay tuned. Gesendet von meinem TA-1020 mit Tapatalk

Press to unlock the lever? Gesendet von meinem TA-1020 mit Tapatalk

Your problem is not related to DCS-BIOS. Please solve it by choosing the right drivers. Gesendet von meinem TA-1020 mit Tapatalk

Now I'm some confused. Tapatalk seems to be a little bit slow. (my last post isn't arrived here yet) PS (edit): Found out, I'm too dumb to divide a common post from a PM at Tapatalk. So I copy the original Text out of the PM here. So can everyone can see the context: Hi. No. We didn't found neither a solution nor the source of this misbehave. My CDU -- even it's inactive for months now -- works at some what hybrid mode: keys and backlight are driven by RS485 while the screen works on a separate UNO by serial. So there is still a chance to earn the Nobel price by solving this phenomena. Cheers Tekkx Gesendet von meinem TA-1020 mit Tapatalk Yeah I thought so, didn't think it was a circut issue with the max chips. I had a feeling we would have to drive the cdu display via serial. Not a bid deal but when I was having the same issue and read your post I had to ask. Thank you sir! I played with the sketch a lot and couldn't figure it out. The interface or character bleed may just no jive with a 485 net. May have to hit the arduino boards and ask around. It may need a custom circuit. @Tulsa-A10: I think, it's a DCS-BIOS-specific RS485-issue. DCS-BIOS sends just altered data along the bus. So any kind of disruption or jamming (or what-ever) has enough time to change screen's content. This do not solve the mystery, because - at my knowledge this is never observed and reported before - states of LEDs and switches are not affected. Where those strange values - showed on the screen - come from... this is a little bit spooky. Meanwhile I tried several methods of shielding with absolutely no effect. The only solution - at the actual design (Sorry Ian. This is NOT a critism of your amazing work!) - could be to send the whole screen's content every few seconds. But this potentially block the bus and prevent other data's smooth flow. Conclusion: (just at my state of knowledge!) DCS-BIOS with RS-485 isn't applicative to feed screens continuously with data.

ASI? (Air Speed Indicator) Do you mean IAS? (Indicated Air Speed) - What a mess with words... A-10C has no ASI inside the code. I think (I am not an Aviator) ASI is just the device while IAS denotes the value. And IAS works fine with Helios (so I think it does with Ikarus too). But this is far away from your initial question. The answer here is: No. It can't be exported by MonitorSetup.lua.

This is made with monitorsetup.lua and Helios. RWR and MFCDs are exported bei monitorsetup.lua. I don't know Ikarus. But I remember it was a "little bit" tricky to get Helios working. Also the downside of Helios: The instruments become some blurry if zoom factor is less than 100%. Good to be seen at the engine's section.

I try to avoid such typos as I use an advanced editing program. My favorit here is notepad+ It shows (just for instance) if brackets arn't closed or too much. BTW: It's free. :)

This is hard to trouble shoot without further info. If the problem has occured suddenly it looks like a very small hickup. I encountered similar phenomena sometimes. It could be everything. Gesendet von meinem TA-1020 mit Tapatalk

Ahh. I was wondering how to defend your home with a ball-pen and a cola-can.

From my experiences I can tell you: It doesn't make sense to save money on controls. I started (just counting post millenium) with a X52. Then I replaced this with a X55 for getting more axes on the Thrust-section. Finally I took the Thrustmaster Warthog HOTAS. And I tell you: I found out all my problems during flight were "control induced". The purchase itself was a "little bit" hurting. But it's worth every single of those 400 bucks. Same is with pedals: Unfortunately meanwhile I ran out of money. So I still have to wait to replace these scratchy creaky ugly Saitek plastic scrap (purchased it as a set with the X55). (Oh! If I spent the money for some good pedals instead for the X52 and X55....) As Warhog already told: If you need it (rudder), you'll really need it. The Spitfire (e.g.) is completely unmaneuverable without rudder. Just using a twist-stick you'll catch a tenosynovitis. Take-Off and Landing under crosswind is impossible without rudder. Strafing a target is impossible without accurate(!) rudder control. .... This list is incomplete ;)

We (the students, as I was young) got a bad (worst) grade if something goes pop or a fuse was blown. No matter for what reason. No negotiations! No merci!

Once upon the time I played Battlefield. We've been 4 friends and we had an appointment for BF4 (or BF3? I don't remember). I ran home from work and planned to spend this weekend with these friends (real friends in real life, no facebook or sth). I started the PC and as soon as everything was loaded (it took a while, SSD was still unknown - or unaffordable) there was a really loud BAMM (similar to a gun shot). All fuses in my flat were blown. I sat there inside a (small) cloud, looking pale (I think). PSU was blown by unknown reason. Not a cheap one, generously sized. Situation: Friday night, friends are waiting at Battlefield, local dealers are preparing for weekend. I think this has been the fastest ride by bike I ever did. I was that lucky and caught the last well sized PSU at the local shop. At the inspection later I found a broken (blocked) fan as cause for this incident.

This is what a real airplane looks like: Sorry, Keith, for borrowing this picture. Thank you for sharing and for not prosecuting. :)

Some pics look like as mum does the cleaning job.

Hallo friends. I also risked an eye to Mole's installation: There are two remarks (from my own experiences): 1. the whole installation (if I see that right) runs on 5V provided just by the USB on the MEGA. Maybe(!) this is some kind of weak. If the voltage drops too far, the Max (also: maybe) can't interprete logical level safe. Try to add somewhat of 7V to 12V to the Vin-Pin there (or to the Vin-Plug). 2. Sometimes (I never examined the reason) it depends on the order which DCS and socat have been started. One day works nothing, other day communication just runs in one direction... Good luck!