As I commenced my first tests with the FSBUS basics I came across to a strange problem.I use FSBUS 2 and this may be the cause so I'm posting this to see ifothers have the same problem and if so that Dirk is notified.Setup consists of the following:Single PC : PIV 2.4G, 512 DDR/333 RAM, WinXP Pro, FS2002, FSUIPC 2.975FSCOM connected to COM2 via standard Serial Cable.1 KEY with just one rotary encoder connected to Row 2, 0(1) via REDEC.1 DISPLAY with 5Digits 7Segment displays.Supply is my own construction regulated 9V (actual output 8.87V).7805 output measured to be 4.87V. REDEC supplied by the 7805 output.Setup works fine and the Rotary is recognized as Rotary2 with no problems. I have assigned the input to HDG, ALT and IAS and got the same problem (as described below) to all.Output directed to FS standard variables and FSBUS display.On startup FSBUS2 works fine and I can change the values quite rapidly with almost no lag at all.The problem is that after a while (about 1-2mins) the rotary seems tha is not recognized any more (like I unplugged it). Changing the values from within FS however does change the FSBUS display, although now the lag is noticeable. Seems like FSBUS has gone into a loop and does not check for the input anymore (?).If I exit and restart FSBUS2 Router all will be fine again for a while. Time when the problem occurs vary from 1min to several minutes.I doubt it to be a problem in the electronics because it seems that the router still communicates with the electronics but somehow the input is ignored. Even if I cut the power to the REDEC and KEY boards and reconnect them the rotary still doesn't work. If I exit and restart FSBUS2 Router, it works again. I emphasize on that.My guess is that I should use FSBUS 1.3 until V2 is completely done.Is v1.3 more stable? And what are the differences between v1.3 and v2?Does v1.3 work with Rotary Encoders (via REDEC) ?Does anyone else noticed this behaviour?Thanks for your help.George DorkofikisAthens, Greece

Hi George,i am sorry to say so but my rotarys are working fine (i am having other problems but these are ones of my own)...I sometimes even leave my setup on over nicht and it still works.What happens if you quit FlightSimultaor and restart it ? That should reset a lot aof parameters...Are you using a network ? WideFS ? PM ???I have had something similar - caused by a faulty USB device - everything got sort of laggy....cheersMathias

HiYea, could be many reasons, but I have also noticed that FSBUS2 beta does indeed have quite a few bugs (that I have reported to Dirk) so I dont use it for real yet. The new version is an improvement for configuration simplicity though, so it will be very nice, once the bugs are fixed.But try using the 1.3 for now, if that also has the same problem then it is in the hardware or something else than fsbus I'd think.Tuomas

As you can see in Fsbus's site, Dirk plans to release within next days, an itermediate version before the final new 2 version.Eddie ArmaosAthens-Greece

Hi George, Well I finally got around to etching & building the FSkey controller & have been fiddling with FSBus2 for past few nights, mainly with the Com & Nav radio's, I am using Knitter switches for the rotaries which are defined as Rotary type 2, I have not experienced the fault you are describing but there is a slight lag when tuning the radio with fast rotations of the knitters but it's always a constant lag that you could live with.I am running it on PC over WideFS here.I think version 2 has quite a few little bugs in it so I would also suggest testing with 1.3 & see how you go, that should help work out whether it's software or hardware.Regards Glenn.

Hi Mathias,I don't think the problem are the rotaries. As I said if I exit FSBUS and restart it, it will work again without doing anything else.I haven't yet tried to restart FS, but during a flight, that would not be an option. I still prefer to reset/restart FSBUS than FS.I don't use WideFS or PM. Simple default FS a/c. Single PC.I did notice something last night though.As I said I have connected FSBUS COM to the COM2 port. COM1 port is connected to my ISDN modem.When I started FSBUS while not connected to the Internet all well.Then when I tried to connect to the Internet I received an error from the dialer that could not communicate with the host. Remember... COM1 the modem, COM2 setup for FSBUS.When I exited FSBUS and tried to connect again, the connection was made without any errors.When I restarted FSBUS again, it worked fine and did not fail on me!There is something that troubles me. Maybe a conflict between the 2 COM ports? Nothing irregular found in my system.I haven't tried yet to connect FSBUS to COM1 and the modem to COM2 but I will test that configuration too.It's not the electronics because the display is updated when I change the value from within FS using the mouse. Only the input from the rotary is ignored, or so much delayed that it gets lost (can that be?)When this happens, the update of the display is soooo sloooowwww like the router has fallen into a loop and not polling FS or the COM port in the normal interval (I have set it to 81ms).I'm saying all this in order to try and locate the error. I'm pretty sure (99%) that it's not a hardware problem. I'll try ver 1.3 and see what goes. I really love the simple setup of Ver 2 though!!!It's a great software (and hardware) and my big thanks to Dirk for his continuing efforts!I can't wait to move forward and have real knobs to play with ;-)George DorkofikisAthens, Greece

>There is something that troubles me. Maybe a conflict between>the 2 COM ports? Nothing irregular found in my system.>>I haven't tried yet to connect FSBUS to COM1 and the modem to>COM2 but I will test that configuration too.Also check that those two ports use different IRQ's and whether there are other conflicts between them.Tuomas

Roger Wilco... (ooops!)Thanks TuomasGeorge DorkofikisAthens, Greece