Hi all,Can someone help with the following problem.I find with the above version that any keyinput or Analogue input there is a delay if you have not used anything.Its almost like FSbus has gone to sleep and it takes about 1 to 2 seconds to wake up.I have reloaded fsbus but no luck.I have removed FSbus 2.0.5 and installed 1.3 and this works fine.If i run FSkey test this also responds in the same way.Once it is working it is fine untill you leave it for 1 minute or so.Consequently i have to operate switches twice to get a response.In fs it seemed to be more of a problem with the keys.The anologe inputs did not seem to suffer so much.I fly a 177.Thanks Guys.RgdsLes

Les, Just a thought!Check your power options in control panel in windows just in case the PC itself is powering some of you hardware off when not in use.Set all your power options to NEVER.Glenn.

Hi Glenn,Thanks for the quick reply,i think they are all as u stated,cause i hate power saving devices.But will double check again.I rechecked and the next time it took 18seconds to respond.Having not used anything for about 15minutes.Quite bizare Eh.When it goes it Great.Thanks Again.Les

Hi,Further to the above,when FSkey or Analogue inputs are slow the led test is ok.It looks like when input devices are being read is the problem.Just thought i would add this,it may help.Any suggestions welcolmeGlenn,checked your suggestions but no power saving options enabled.ThanksLes

Les, have you got any other serial devices attached to the PC, like modems on com3 & stuff that may be sharing an IRQ with your FSbus serial port, as this can cause undesirable results.You can check this under device manager & have a look at the recources tab for your serial ports.Glenn.

Hi Glenn,No the irq for com1 is only used for com1.Does one need to flash the pics for use under FSbus 2.0.5.My pics were done under 1.3.I tried to flash them under 2.0.5 but they wont.Not even erase.What are your thoughts.ThanksLesP.S did you read that i can operate the led test ok.

Can you try your Com2 port?What sort of PC are you using?If you can't flash it sounds like a comms problem, make sure when flashing that your BUS cable is less than 10cm & have only one board connected, also try doing it with a clean boot...i.e. shut down all resident software, best thing to do that with is to run MSCONFIG, click on the startup tab & untick all the items that load on windows startup, you can come back there later & tick them all on again to startup like normal after testing.Cheers Glenn.

Hi EverybodyI have the same problem with the latest version of FSBUS.I discovered, the first time i load the 2.0.5, if i go back to 2.0.3, there is no problem.Dirk is informed about the problem, so i think he wil come back with a solution.RegardsFinnDenmark

Ah OK Thanks Finn, I have not loaded up 2.0.5 to play with it yet so thats why I have not seen the problem here.Glenn.

Hi Finn,Thanks for the feedback,i was hoping that,i dont have 2.0.3 to try.Will wait for Dirk.Im in no hurry.Glenn,thanks for your reply,i got 2.0.5 to flash.I was using to long a cable.RgdsLes

Hey there!What do you mean by slow? You mean that FSBUS is slow to produce the impulse (little green dot on the software), or that it takes in Flight Sim a little time for the event to happen?I'm asking because I found that the radios don't work very well with version 2.0.5 and FS2004. In previous versions it worked fine with FS2002, but I don't have 202 installed now to check it.Regards,Rafa.

Hi,There appears to be a bug in 2.0.5.If you select keytest the keys respond but if you leave them for a minute or two, then they will not show as being operated.The same happens in fs and router.The previous version was ok.RgdsLes