FSBUS Router 2
 

Hallo Leute,

das war viiiiiel Arbeit, aber nun ist die Version 2 (fast) fertig.
Sie steht im Downloadbereich (www.fsbus.de).
Bitte unbedingt die Readme lesen!
Diskussionen und Vorschläge bitte in diesem Thread führen.

Ich schalte mich für ca 2,5Wochen aus (Urlaub) und wünsche ein
erfolgreiches Testen.

Gruss Dirk

When trying to start the fsbus.exe, I am informed that "This application has failed to start because rtl60.bpl was not found".

How do I install this file without installing the intire Borland Delphi ?

Best regards

Ich wünsche Dir einen wunderbaren Urlaub!
 

Ein schöneres "Mitbringsel" als die neue FSBus Version hättest du uns gar nicht machen können! :p :p
Sie ist so schön wie in den Screenshots!!

Vielen Dank lieber Dirk!

Wie gesagt einen schönen, erholsamen (vor allem von uns) Urlaub!
;) ;) ;)

Gruss Peter :) :)

Hi Volante,

i'll add that rtl60.bpl into setup. I hope i can do that today, so try another setup tonight.

regards Dirk

For the impatient: http://www.lexically.net/downloads/version4/base1a.zip

Google found this, those are apparently the Delphi runtime libraries etc, so this other program seems to use the same. Dumping those to my FSBUS2 installation directory seemed to work.

However, as with any software found on the net, you use those with your own risk. They worked for me though.

Thanks, Dirk! And enjoy the holiday!

Tuomas

Good work, Tuomas. FSBUS2 obviously needs both rtl60.bpl and vcl60.bpl.

Thank you Dirk for a wonderful piece of software!

Hi Dirk,

also ich muss schon sagen, da hat sich der Meister selbst übertroffen - und zwar gleich um ein Vielfaches :)

Was Du da auf die Beine gestellt hast ist schlichtweg genial - Die Bedienung ist total einfach, die ganzen Details dermassen durchdacht - alleine die Sache mit dem Autosense hat schon so viel Zeit erspart ....
Die Zusammenfassung in Gruppen macht alles durchschaubar - auch die PM Dinge (die ich bisher getestet habe) haben alle funktioniert.
Sogar die LED´s lassen sich jetzt alle ansteuern, man braucht keine Klimmzüge mehr zu machen...
Jetzt brauchen wir nur noch die Implementierung für die tollen Drehgeber von beatmaster Alex (Conrad Drehimpulsgeber)

Nach so viel Lob aber noch ein kleiner Fehler:
Bei mir funktioniert das Testemodul für FSLED nicht - optisch taucht es auf - von der Logik her auch wieder absolut duchdacht - nur leuchten keine LED´s auf...aus der Anwendung heraus ist es jedoch kein Problem.
Und das zurückrouten der LED Anzeigen an das PM MCP klappt nicht so recht...Die displays lassen sich zwar sowohl vom PM MCP als auch von den rotarys ansteuern (alle 6 liefen in 2 Minuten - kopfschüttel...) - die angezeigten Werte werden aber - trotz offensichtlich richtigem routen nicht bzw. falsch zurückgeschrieben.

Vielleicht kannst Du da noch mal nachsehen.

VIELEN DANK DIRK

Das ist echt ein vorgezogenes Weihnachtsgeschenk

Viele Grüsse

Mathias Röhr

Hi Dirk,

noch eine Anregung ... In der B737 (ich denke auch in anderen Mustern) gibt es einen "Lights Test" Schalter - mit dem werden sämtliche verfügbare Lampen angeschaltet - das sieht dann genauso aus wie wenn Du dem Comcontroller der Saft abstellst und wieder anklemmst - dann leuchtet auch erst einmal alles ...das kannst Du vielleicht auch softwareseitig bewerkstelligen ???

Danke

Mathias

Hello Dirk

I have now made my first prototype of an instrument for N1 and fuel.

When you are using the servo controller from FSBUS, the servo can only turn 1/4 round, but ther is space for the servo to turn 1/2 round.
Is it possible to make the servo controller so it can turn the servo, more then 1/4 round?

If it is so, it will be very easy and cheap to build a instrument.

I will relase some picture later on my homesite from the prototype.

It toke me about 1½ hour to make the prototype.

Regards
Finn

Hi Finn,

different servo types will move over a different range.
Next time, i will check how wide my servos turn.

If it makes sense, to modify the timing, i will do that.

regards Dirk

Hi Dirk!

At least with the Simkits stuff (we have the instruments on our aviation club sim project) - I noticed a difference: They recommend HiTec servos, and indeed: I got Futaba ones, and they do not have that big of an angle for the travel. They simply do not rotate to the end with the same pulse as Hitecs do. There is still some movement available (if you turn by hand) before the end limiter, but the servo itself will not turn, it just vibrates.

So it looks that different servos have different characteristics for pulse response I think. You should probably try with a Hitec and Futaba as a testing pair, those really show the difference - at least here.

I originally had trouble calibrating some simkits instruments that depend on the full travel of the servo, and I had to swap in some Hitec servos from my RC plane in order to make them work. The Futabas work great on the plane anyway, so I was lucky to have those around. Hitecs worked OK eventually. So that is a tip for you others out there until a solution is found: try if Hitec servos respond better to FSBUS. They should be slightly cheaper too I think, otherwise the basic servos should be of equal quality anyway, and in RC use there is no difference since you can adjust the linkages to control surfaces..

Best,

Tuomas

Hello Tuomas,

it seems, there is finetuning needed for servo module. I supppose to do the following.

Current pulse range in servo is limited to that servo, which i used during development. I expected, other servos will be compatible to that range.
I will double this range, so i hope any servo will fit into.
The width of range and startoffset will then be calibrated in fsbus for each servo object.

But before i will make the second beta available.
Any other suggestions ?

kind regards Dirk

Hi Dirk

It will be a good thing to have a "mark" to revers the servo.

Regards
Finn

For other suggestions, I have these strange old ALPS rotary encoders here that are much like the Knitters in that the pulses are separated. But it acts a bit strangely, since it keeps the connections "up" all the time, and when you rotate, it cuts the rotation side connection to zero when you rotate. A bit hard to explain, but I hope a pic helps.

So instead of:

A ____________________________
B -___-___-___-___-___-___-___

It does

A ----------------------------
B _---_---_---_---_---_---_---

So it is a bit strange :-)

The problem is, those are nifty, and also contain an integrated pushbutton and I got those for one euro a piece, but they had just a small batch of those they found somewhere.

Anyway, wiht FSBUS1 I wired those as two different switches, which works. But the chatter-killer algorithm makes life hard - I use those for the gauge knobs like for VOR1 etc, and those tend to be rotated fast.

Now I know I am probably the only person in existence with this kind of weird switches (no way to get Knitters from here with reasonable effort) - but would it be possible to either add the chatter-fix adjustment stuff to plain swithces as well, or alternatively would it be possible to detect this kind of a switch as "knitter"-type and support it too?

It is a bit sucky since I know it is a lot of work for such a small userbase :-/

Tuomas

Hi Tuomas

Have you tried inverting the readout for the rotary?

Yea, but the problem is, it does nothing. Either as "up/down" or "type2 rotary"..

How should one wire a knitter-type switch? Like 2 "regular switches", with common "ground" wire?

Tuomas

I definitely think you wire them as two switches with common ground, but I am not able to check it out now.

Also the Row ID and Sub ID of the Rotary2 has to reflect what inputs you are using on the FSKEY.

Good luck
Vidar

Hi Tuomas,

the Knitter rotary is to be treated like 2 switches with 1 common contact (middle post).
However there seems to be a little problem in FSBus2 as according to the readme of version 1.4 one could use 4 knitter on 1 row. If you do like this, the knitter will only show reaction for one direction (up or down.
It´s been reported that if you use only 1 knitter per row it then would work ok.
I´m sure Dirk will correct this with the next release.

Regards

Peter

Eek!

I was converting my cockpit to FSBUS2 eventually, and I have two important issues:

* Is it possible to do 2-rotary radio tuning? With the new auto-wrap-around stuff I can do radios without key events, but if I have stuff like this:

RadioWholeMHz - value +-1000 on notch

RadioFrac - value +-25 on notch,
frac only

Those work, but when I turn the "whole" rotary, it resets the fractional part to zero..?

* Another issue is: was "add_value" dropped? I cannot find it on switches, and it was useful at least for my flap switch which is just a 3-position toggle that returns to center ("more flaps" and "less flaps" - nice for different aircraft types which each have different number of flap stops)

Also the C172 I fly contains a "step-less" flap where it has just the 3-position lever which I need to hold "down" to add flaps, and "up" when I want to take up flaps. It just runs the flap motor drive as long as I keep the switch pressed. This would be also nice to have, I am thinking of doing it with the "repeat" option.

Tuomas

Hello Tuomas,

what means Eek!

The decimal rotary problem needs to be tested by me.
The add flag is no longer part of the fsbus objects, but defined in fsif.ini. There is a option columns which may contain a + . This is the new add flag.
To keep this file compatible, i will add an alternative flaps entry with add. If you do it, the next update will cause headache.

The internal logic has changed a lot from version 1 to version 2. The aim is to make all the fsbus1 features available in 2.

regards Dirk

Hi Dirk!

"Eek" means "uh oh" or "aiee!" something like that :-)

I was looking into the data files, it looked interesting and good that it was ASCII, so adding stuff is easy if needed.

Is it possible to add things like the bits already in the file? The example case was the radio "swap" button which needs the bit (8) anyway to toggle COM1. It might be a good idea to make the "swap" a group which contains the different radios (COM1, NAV1, COM2, NAV2) already, so one does not need to look in the FSUIPC SDK for the bit number, since the hex addresses are already contained in FSBUS.

Do you want to have a bunch of those ALPS rotaries for testing? If you email me your posting address I can send you a bunch, they are pretty nifty and could be useful in your project as well :-)

I know we have many of us finns using those in FSBus 1.3 currently. One option would be to have a normal switch object that has the possibility to turn off the chatter filtering, so one can use it as two separate "normal" switches where one does the "add 1" and the other direction just adds "-1". I do that currently, with "negative_edge" and "inverted" it works like I want. Talk about kludges :D But the chatter filter makes it choke when I turn the knob very fast. Otherwise it works great.

I think it is a good idea to move the different options from the switch objects to the actual FS objects btw, it simplifies the configuration a lot when most things are already set up like you would want anyway.

Tuomas

Hi Tuomas,

The ascii format indeed can be used to modify a lot of things.
But keep in mind, that you will lose compatibility.

The bits for example are still implemented.
During my testings with the standard Boeing MCP i found so many stunning effects which i had to modify by C-code, that I strongly recommend in this early stage of the beta to make the nifty details
first fixed by me.
Later we can make a private section in the file, which allows you to add what you want.

I hope you agree. I will send you my postal address by email, it makes sense to have original switches for testing.

regards Dirk

Sure I agree. It's always good to "send the patches upstream" so they get added to the released software. So if I figure out something I'll send you examples so they will be in the official version. and that benefits everyone.

I'll try to send the switches soon, they are pretty cool since they have 36 detents, handy for stuff like course setting etc which require a lot of turning .

Tuomas

Howdy.

I tried to set lights to my cockpit switches and I couldnt get landing or other lights to work. Pitot heat worked *once* and then it stopped working, so something weird is going on in there.

Also "Avionics master" was missing from the list.

Just a few bug reports from today :-)

Best,

Tuomas

DREHIMPULSGEBER ?
 

Hi,

ich hab mir mal einen CONRAD Drehimpulsgeber gekauft zu testen.

Wenn ich den anschliesse sehe ich im FSBUS auch die LED leuchten wenn ich den Geber drehe. Eine Veränderung des Wertes erfolgt jedoch nicht.

Ich bin mir sicher, daß Problem liegt bei mir zwischen den Ohren, aber wer kann mir dennoch weiterhelfen.

Wo muss der mittlere ran, wo die beiden äusseren. (Obwohl autosense den erkannt hat, aber sicher ist sicher).
Die Gegenüberliegenden Anschlüsse sind ja wohl für den Drucktaster der mit drin ist (funzt auch).

Und was muss ich im FSBUS noch machen damit ich z.B. die NAV" Freq damit ändern kann ?

Danke

Wolfgang

War ein wenig voreilig.

Der Wert ändert sich nun, aber der zählt nur hoch !

Egal was ich einstelle. Es geht immer nur aufwärts mit der Frequenz.

Müsste doch evtl. an den ANschlüssen liegen. Naja evtl. kann mir damit ja einer weiterhelfen.

Danke

Wolle

Hi Dirk

I am putting more offset adress in FSIF.INI, but now i have a problem, i got to id no. 512, and then get an error " out of id range", how many "id" is allow to put in?

Regards

Finn

Re: DREHIMPULSGEBER ?
 

I think it might be a good thing to reserve a few ID's for "private use" where we can do our own custom things (that will occasionally be necessary) without fear of conflicting with the "official" ones.

Maybe if the ID range is from 0 to 1024 or something, maybe 900-1000 or such could be "user defined" id's?

Also maybe it makes sense to have "USER.ini" for those. I think it is important to have a way to define your own things, since FSUIPC has a lot of stuff - like the adventure weather stuff etc.

I have been thinking of a "weather control panel" for the aviation club simulator we are building - so one can just twist knobs to get ".. hmm.. BROKEN clouds.. hm.. 2500ft and ... Visibility 6 kilometers and.. wind 240 degrees and 8 knots.." - all from FSBUS-controllable rotaries :-)

Thanks for hacking on this, Dirk! :-)

Tuomas

Hi Wolle,

das mit den Drehimpulsgebern geht leider nicht ganz so einfach - Du benötigst noch eine weitere Schaltung die zwischen Geber und FSKEY kommt.
Seh mal im Forum nach, der "Beatmaster Alex" hat da mal was geposted, wenn Du nicht klar kommst melde Dich.

Mathias

FSBUS DO
 

Hi Dirk

So far i can see, there is no function in min. and max. when the invert is selected, is that correct?

Regards

Finn

Hello,

to speed up the process of routing, i have some internal tables which i have made fixed size (512). I never thought, there will be more.
I think i have to make it dynamic sized.

A user individual range of params in ini file makes sense and will be available in an upcoming version.

The min max with inverted should work. I will test it.

regards Dirk