FS Bus

[Spyy]

Hallo FS Bus Fans,

ich experimentiere gerade son bischen mit FS Bus rum. Es sind nun 2 Fragen aufgetaucht:

1. Überlauf

Wenn man mit nem Rotary z.B. den OBS oder die Frequenz ändern will gibs ja irgendwann nen Überlauf (359 Grad auf 0 oder 108.00 auf 117.75) da es ja keinen Anschlag für Rotarys gibt. Im Moment, wenn ich min und max begrenze bleiben die Werte an min oder max stehen und man muss in die andere Richtung drehen.Weiterhin hat der FS beim OBS wohl nen Problem mit 0 und 360 Grad ??!!

2. Gear oder Flaps in transit

Wie kann ich z.B. eine LED angehen lassen, solange sich die Flaps oder das Fahrwerk bewegt ?

Es würde mich sehr interessieren, ob jemand für das Lösungen hat bzw. ein sog. "Lösungsarchiv" vorhanden ist??

Gibt es ein FS Bus Forum wo nur FS Bus Themen diskutiert werden ??

Sonst muss ich ja sagen: Gute Arbeit Dirk und weiter so

Vielen Dank für eure Hinweise

Torsten

[dirkan]

Hi Thorsten,

das mit dem Überlauf wird in der nächsten Version des Routers automatisch gehen.

Ich hatte selbst nach der Entwicklung der FSBUS Module mit dem Bau des MCP und des Throttle Quadranten begonnen. Dabei fallen dann die kniffligen Dinge auf, die einfach noch fehlen.

Bei der Version 2 des Routers werden deutlich mehr Parameter intern berechnet, so dass der Einstellungsaufwand des Routers einfach wird.

Warte bitte noch etwas.

Gruss Dirk

P.S: bitte keine Fragen, wann die Version fertig ist!!!

[Spyy]

nein werde ich nicht fragen, neben dem Simbau gibt es ja leider noch den Beruf....

Danke für die Antwort

Torsten

[tuomas]

Original geschrieben von dirkan
Hi Thorsten,

das mit dem Überlauf wird in der nächsten Version des Routers automatisch gehen.

(zap)

Bei der Version 2 des Routers werden deutlich mehr Parameter intern berechnet, so dass der Einstellungsaufwand des Routers einfach wird.

Moin Dirk, and thanks for the hacking

As a workaround you can make the rotaries generate keystrokes (eg, "a" on left turn, "b" on right turn) and make those keystrokes do things via FSUIPC configuration dialog. This works and FSUIPC does the "rotation" of things automatically.

This is a bit hard to maintain since you get a configuration in two places that needs to stay in sync, but it works.

Now, with the 36-step rotaries I found I am having a slight worrying discovery: Whenever I rotate something very fast (VOR1 radial for example) it loses pulses. I know this is because of the anti-chatter protection in the PIC code. This is understandable and not really that bad. But there is another side effect - I seem to get random signals from other switches while doing fast rotations. Like I switch the VOR radial quickly around, my flaps extract one notch all of a sudden. So looks like something is getting messed up..?

Anyone else experiencing anything like this? My friend Joni apparently has seem similar things too.

Again, it is quite rare and usually does not happen that much, but just got my attention. It's not fun though, like all of a sudden you realize your squawk code is something else what it should be..

Any ideas?

And sorry for the english, Mein Deutsch ist nicht so Gut, so entschuldigen Sie bitte..

Tuomas

[Spyy]

The phenomen you discribe is also happening if you choose display test (where digits are changing very fast) and you have a servo on the servo board. It is "jerking" around. It looks like that a quick change has an infuence on other CIDs.

Bye

Torsten

[dirkan]

Hi Tuomas,

i was wondering, how you could read this german speaking forum.
If i look at your finish forum, i simply understand nothing.

I will have to look for that problem. The display test together with servo movement could be a good test to reproduce the problem.

kind regards Dirk

[tuomas]

Original geschrieben von dirkan
Hi Tuomas,

i was wondering, how you could read this german speaking forum.
If i look at your finish forum, i simply understand nothing.

Ich habe 6 Jahren Deutsch in der Schule gelernt.

But it's rusty, and I use Google translator to read, it helps on stuff I dont understand otherwise

http://www.google.com/language_tools?hl=en

It's great - makes a lot of grammar errors, but makes it possible to understand what stuff is about.

I am not surprised it doesnt translate finnish though

I will have to look for that problem. The display test together with servo movement could be a good test to reproduce the problem.

kind regards Dirk [/b]

Yep. I also wonder what kind of input the "knitter"-type switch config expects. The rotaries I found are some ALPS ones with separated output, but they work a bit strange. The rotation-direction pin gives you pulse, but the other pin gives you "1" all the time. It also has a peculiar thing that when you change direction it first outputs one more pulse on the "wrong" direction before changing to the new direction. They are still quite nice anyway. Using them now for VOR and ADF and QNH etc knobs on the panel:



I did a VFR flight from EFHF to EFMI on vatsim today, using map, some vor radials and did some old fashioned map-and-heading navigation. It's great when I can twist the knob on the panel - everything works now without the mouse. I just need a good yoke and pedals. Plus at some point I want to do an alternate throttle that is king air -style with dual handles for throttle, prop and mixture. But that means more gauges too so it needs some planning anyway..

Anyway, back to the rotaries, I use "inverted, positive_edge" if I remember correctly and use them as two separate switches as far as FSBUS is concerned. Works great but the jitter protection hurts it a bit if I turn very fast. So I am wondering if there is a way to wire that thing as a knitter? What kind of pulses does it expect? I tried but got simply nothing from it.

Tuomas

[PA7RM]

Hi Tuomas,
Just a quick note on the Finnish Forum. I understand nothing, but i get many ideas of the many pictures on that board of ideas how to build a cockpit. I saw also your cockpit build. And of course from Jari.
Great idea's and building. I'm happy now i can flash the PIC. So i can go further with my project.
Goodluck and i will keep an eye on both Forums.
At the moment busy with all the FsUIPC commands. Is there no shorter list. ?

[Mathew]

Hi Tuomas,

As a workaround you can make the rotaries generate keystrokes (eg, "a" on left turn, "b" on right turn) and make those keystrokes do things via FSUIPC configuration dialog. This works and FSUIPC does the "rotation" of things automatically.

Hoe did you get this part done ??? I am stuck with the same problem and have nearly got my head of from messing around with all kind of things but have not found a solution yet...i would really appreciate if you had an idea.

thanks

Mathias

[tuomas]

Original geschrieben von Mathew
Hoe did you get this part done ??? I am stuck with the same problem and have nearly got my head of from messing around with all kind of things but have not found a solution yet...i would really appreciate if you had an idea.

thanks

Mathias

Hi.

You define a switch to output a keystroke. You do this on the KEY/Mouse tab (or whatever it was called, typing this on Linux right now..)

Keyboard thingy works just like FSWrite - you can "route" switches there. But instead of doing some FSUIPC stuff one gets the keyboard event or a mouse click.

The FSBUS folder where you installed it contains a key event "finder" application where you can see mouse pointer coords and also the keyboard events, but it is actually not compled - just a lot of work to type them in.

So you define something like this:

Name a line "GYROKey" and have the key event be: "K+VK_SHIFT;K+N;d40;K-N;K-VK_SHIFT|K+VK_SHIFT;K+M;d40;K-M;K-VK_SHIFT"

This looks *horrible* but lets try to break it up:

K+KEY = press key "KEY" down. So:

K+VK_SHIFT = press shift down.
K+N = press down n
d40 = delay 40 milliseconds
K-N = release key n
K-VK_SHIFT = release shift.

Now you understand this just does a "Shift-N"

Then there's the "pipe" character | that separates rotaries - when a switch becomes "1" it does the event *on the right side* of the pipe, and when a switch becomes -1 (or was it 0? Cant remember now) then it does the sequence on the left side.

These are good to test in Notepad. Rotating the rotary will then do "NNNNNNNNNMMMMMMMMNNNNNNN".

Then in FSUIPC you define key "shift-N" to do "GYRO_DRIFT_DEC" or whatever it was, and shift-M to "GYRO_DRIFT_INC".

The annoying part is to keep stuff in sync betwen FSBUS and FSUIPC, and that you need to have keyboard focus on the FS2002 (otherwise you'll be typing NNMMMMNNNMMM on Squawkbox or somethi
ng )

But it's a workaround until we get 2.0.

Get my config from http://tigert.gimp.org/vatsim/cockpit-stuff/fsbus.fbc for some examples. It's best to load it up in FSBUS router and see how things are defined, the text file itself is not very informative

Tuomas