HI guys,Just to let you know that Dirk has updated the Fsbus.exe to 1.0.5 (Beta).This fixes up the Bit command that used when configuring light switches.Those who havnt updated from 1.0.3,it also corrects Fsadmin Analogue probs along with the analogue correct operation inFsim.See the readme file. Thanks DirkLes

Thank you, Les, for your post. I've been anxiously awaiting this release and I just tried it out with success; my lights now all work with out interfering with each other. Hope all is well with you.Regards,Eric

Hi Eric,I tried to reply to your email but had it rejected.So i havnt been ignoring you.Yes im still with FSbus and hope it will be plain sailing from now on.Good to see you are ok now.Take CareLes

Hi Les,Couldn't find your email and didn't think I should start another thread for this. Have you played with CDK and the Radio frequencies? I'm using a 12 pole switch wired as a rotary (per I/O manual). I have the standby working sort of: my whole numbers work but the fractions do not and I can't seem to figure out how to step .025. I'm using a 5-digit display and it does step on the ones and hundredths place by +/- 1, but no increment. Here is what I have:F, FRad1stby, 0, 0x311a, BCD4T, 1, 1, 2, 0 RWC, CRad1stby, DISPLAY, 3, 0,, 5, 1, 3C, CRad1Int, ROTARY, 8, 36,, 0, 0C, CRad1Frac, ROTARY, 8, 32,, 0, 0A, ARad1, 1800, 3697, WRAPAROUNDR,, CRad1Int, ARad1, 100, 1, 0, ADDVAL' This is where I think is the issue: I've tried' *5 /2 and /40 and neither worked. Also tried .5 but' it rounded the answer upR,, CRad1Frac, ARad1, 1, 1, 0, ADDVALR,, ARad1, CRad1stby, 1, 1, 10000R,, ARad1, FRad1stby, 1, 1, 0R,, FRad1stby, CRad1stby, 1, 1, 0Please don't put a lot of thought into it; I'm done with my school summer session now and have a few minutes to mess with this again. Hope your sim is working/developing great.Regards,Eric

Here you see my code for the Comm1 radio (2 displays, 1 swap button, 2 rotary encoders). You'll see the differences with your code.The Accumulator line looks strange to me.You should add 50 for the fractals, I think.F, FCom1, 0, 0x034e, BCD4T, 1, 1, 4, 0, RW F, FCom1Stb, 0, 0x311a, BCD4T, 1, 1, 4, 0, RW F, FCom1Swap, 0, 0x3123, U8, 1, 1, 4, 0, W C, CDCom1, DISPLAY, CID, 0, , 5, 1, 2 C, CDCom1Stb, DISPLAY, CID, 0, , 5, 1, 2 C, CRCom1Int, ROTARY, CID, RID, C, CRCom1Fract, ROTARY, CID, RID, C, CSCom1Swap, SWITCH, CID, RID, A, ACom1Stb, 118000, 136000, R, Com1, FCom1Stb, ACom1Stb, 1, 1, 0, R, , ACom1Stb, FCom1Stb, 1, 1, 0, R, , ACom1Stb, CDCom1Stb, 1, 1, 0, R, , CRCom1Int, ACom1Stb, 1000, 1, 0, ADDVAL R, , CRCom1Fract, ACom1Stb, 25, 1, 0, ADDVAL R, , FCom1, CDCom1, 1, 1, 0, R, , CSCom1Swap, FRadioSwap, 8, 1, 0, regardsNorbert

You should add 25 for the fractals, (I wrote 50 earlier, thats for NAV offcourse)

Norbert,Thank you so much for the response. I modified my code and added a 'wordwrap' tag to the accumulator. I still needed to place my decimal point at 3 places (I am using 5- 7seg displays). And, I changed my multiplier on the integer to 1000 as you said and the multiplier on the fraction portion to 25. I'm seeing improved results, however, I'm having a problem with the rounding. I haven't, as of yet, found the constant, but it switches from incrementing the .025 to a rounded value which changes the increment - however, now flight sim does read/write the value.(Example Down: .76, .73, .70, .67, .64, .61)(Example Up: .59, .61, .63, .65 , .67 , .69 , .71)They're close but not quite on yet. Any ideas? Thank you again for your response. Eric

Eric,Post your code and I will have a look at it

-radios.iniF, FRad1, 0, 0x034e, BCD4T, 1, 1, 2, 0, RWF, FRad1stby, 0, 0x311a, BCD4T, 1, 1, 2, 0, RWC, CRad1, DISPLAY, 2, 0,,5, 1, 3C, CRad1stby, DISPLAY, 3, 0,,5, 1, 3C, CRad1Int, ROTARY, 8, 36, 0, 0C, CRad1Frac, ROTARY, 8, 32, 0, 0A, ARad1, 118000, 136000, WRAPAROUNDR,,FRad1stby, ARad1, 1, 1, 0R,,ARad1, FRad1stby, 1, 1, 0R,,ARad1, CRad1stby, 1, 1, 0R,,CRad1Int, ARad1, 1000, 1, 0 ADDVALR,,CRad1Frac, ARad1, 25, 1, 0, ADDVALR,, FRad1, CRad1, 1, 1, 0It seems to be working now, but I'm not entirely convinced yet. Let me know if you see any thing out of order and thanks again.Eric

I do not see any faults in your code. Do you see 00, 02,05,07,10 now?With the wrong code you can get values into FS that are normally impossible. For example 118,01When you correct your code (with a value of 118,01 in FS), you will get wrong values, although your code is OK. At first you have to get a normal value into FS.----------------------------- The last 3 looks strange. C, CRad1stby, DISPLAY, 3, 0,,5, 1, 3I have a 2 there. In fact it says where the decimal point has to be put.In 118.00, the decimal point is at he 3td position (from the right)So with a 2 you would see 1180.0Another comment in general.I followed a cdk wokshop given by Dirk Andrseck and he suggested a naming convention.Offcourse it is not necesary but as your code increases, and after a few years it is difficult to read your code.CD..... is a cockpitobject and a displayCR..... is a cockpitobject and a rotaryCS..... is a cockpitobject and a switchIt is better not to use Rad1 as a name , it is not specific enough. Use Com1, or Nav1 instead.Norbert

Norbert,Thank you for your reply - I wanted to research before I responded. I have renamed all my variables with the suggested convention; thank you. As for the decimal, I can only get my five-position, seven-segment displays to show xxx.xx if I assign P3 at 3. My only guesses are: 1, it is follows the same reasoning as P2 (offset from left); 2, I have something hosed up. Anyhow it does mostly work, though there is something weird in the order of loading FS and CDK where I don't get the correct results with the frequency fractals. I haven't yet found a consistent pattern but it works most of the time.One more question for the guru. I am attempting Mike Powell's air core airspeed gauge (very beginning stage). I am wondering you have integrated any of his projects to FSBUS? I have two air cores started and will finish, but, as of now, I am unsure of how I am going to marry his code into CDK or if it goes straight to FSUIPC. Thanks again for all the input!Best Regards,Eric

Eric,Anyway, it works. Thats most important.Perhaps the P3=3 issue is a bugin the virtual cockpit of cdk (there are more). I need a 2 to get the point on the right spot in the virtual cockpit.My hardware is still on FSBUSNG. I am almost finished with the CDK code (I use the virtual cockpit as a reference to see wheter the code is fine). When thats finished I put CDK to the sim machine.I made the servo board that was published recently. I can get a little servo motor to work using admin.I did not use it with cdk yet.I do not have any analog meters is my pit. The servo only has a movement of about 180 degress I believe. For altimeter that is useless. Could be used for flapsgauge.In the near future a fsstepper board will be released too.Norbert

Norbert,Not to prolong this thread more than I have, however, I just compared the virtual controls (VC) with flight sim. I agree that the VC does display what you described while the flight simulator (MSFS04) does read correct and the 5 pos 7seg display does as well.Thanks again for all the help.Eric