Hi, i have Fsbus system (hardware & software) and i use it to read & write in Fsuipc offsets for Fs2004 & PM. So, i made my pedestal and trying to setup the ADF2 i found that even if i was using the correct offset (02d4) i was receiving the ADF1 freq. I tryed to setup the ADF2 in the same way as Dirk has the ADF1 in std FsBus setup. I know that there are 2 offsets for ADFs, if there is not Fs or Fsuipc problem maybe there is something wrong in Fsbus. I'm just asking if anyone else had the same problem, or if the ADF2 is not working 100%. Thanks Eddie Armaos Athens - Greece

Hi EddieI experience exact the same problem setting up my adf 1 and 2 panels with fsbus. It is mentioned by another builder (Themis). see here:http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchIn the original FSIF.INI is written:1, "Radio" 2, "ADF", 20, 1, 0x034c, I16, 0,RW+, 10,1,1, 2, "ADFStandby", 510, 27, 1, I16, 0,RW+, 10,1,1, When I use that I can turn my dual rotaries and see the ADF2 display (my hardware) turning between 100.0 and 1799.9. But when I look into the ADF2 offset 0x02D4 with fsinterrogator I see a different frequency. ALthough this is a nice setup for a fake ADF2 hardware panel , it does not communicate with the FSADF2 frequency.Besides that, there is no adfstandby offset, only a adf2 offset.Does anybody know what the meaning is of the mode parameter in the fsif.ini? (it is the first 1 in the second line and the 27 in the third line)Then I started experimenting and come to these lines:1, "Radio" 2, "ADF1", 20, 1, 0x034c, I16, 0,RW+, 10,1,1, 2, "ADF2", 510, 1, 0x02d4, I16, 0,RW+, 10,1,1, Now I get the same results as Eddie and Themis. It does not matter wheter I turn at the adf1 or 2 rotaries, both adf displays will change (and the real adf2 offset still has another value as seen with fsinterrogator). I adjusted the aircraft.cfg file and added an adf2 radio, but that made no difference.Did anybody find a solution for this?regardsNorbert Boschhttp://home.wanadoo.nl/norbert.bosch/

Hi!2,"ADF2", 609, 4, 0x02d4, U16, 0,RW+, 10,1,1Regards!

Thanks for your answer Totom.Unfortunately , it does not work.-----------------------------------------Resuming:The originale FSIF.INI line2, "ADFStandby", 510, 27, 1, I16, 0,RW+, 10,1,1, Turning tyheTurning the rotaries gives a display between 100.0 and 1799.9(but adf2 doesnot change in fsinterrogator)------------------------------------------2, "ADF2", 510, 1, 0x02d4, I16, 0,RW+, 10,1,1, Turning at the rotaries of adf1 or adf2 gives in both cases a change of adf1 and adf2 display at the same time------------------------------------------line of Totom:2,"ADF2", 510, 4, 0x02d4, U16, 0,RW+, 10,1,1At first I thought it would give the same result as the last line. But it was different. The display showd 100,0. When I turned it immediately came back to 100,0regardsNorberthttp://home.wanadoo.nl/norbert.bosch/

After further trial and error I found out that the difference I describe above is only made by the modus parameter2, "ADFStandby", 510, 27, 1, I16, 0,RW+, 10,1,1, 2, "ADFStandby", 510, 27, 0x02d4, I16, 0,RW+, 10,1,1, both line give on the display 100.0 - 1699.9 (it does not go to 1799.9, although that is set as max in the router, the display does show >17xx.x when set with the mouse directly in fs, perhaps a bug in the se , just as was with the com radio's). Looking at offset------------------------------2, "ADFStandby", 510, 4, 0x02d4, U16, 0,RW+, 10,1,1as proposed here on the forum, gives only 100,0; after turning the display switches immediately back to 100.0------------------------------2, "ADFStandby", 510, 1, 0x02d4, I16, 0,RW+, 10,1,1give the strange behaviour(affirmed by others here on the forum)that adf1 and adf2 display give the same value, whether I turn the adf1 or th adf2 knobs is irrellevant.-------------------------------The only difference in these lines is caused by the modus parameter (1,4,27) I tried all kinds of other settings, but the modus parameter decides which of the 3 behaviours I got.I did a thorough search here on the forum, and I read several times that the modus parameter (see first lines of fsif.ini)is not used. Well, after my experimenting I do not think thats the case. Look at the fsif.ini . the modus parameter can take a lot of values.I also wrote to Dirk Anderseck to shed some light on this. I will post further results here.regardsNorbert

The modus parameter 27 indicates a special processing inside the router. So there is probably a bug in this one.Dirk mailed me he will look at this. So I stop experimenting on this one and letts wait for the nezt update.RegardsNorbert