As a high number of appends are related to CONNECTION and INTERFACE problems,
I suggest to list here techniques and tools that can help in case of connection and usage problems.
First of all, know (and write in your posts) your environment:
PC hardware
Windows version
drivers...
Other software used (DLL ?): smartpropo, PPJoy,..
FMS version
Input device: transmitter or joystick make, model, type,...
PPM or PCM ?
Connection(from a HW point of view): USB, serial, parallel, game
from a signal point of view: simple (resistor, transistor), or coded (PIC ,)
and code if known
..........................................
Then describe the problem...
..........................................
with these elements you can start a SEARCH on forums to see if the problem is known
..........................................
Or you may first do deeper diagnostics with some tools:
here a first list.
You will be able to see if you do have an input signal, if your system is viewing the connection, which channels are present and where, how they react to the stick movements, a.s.o
....................................................................................
TOOLS
The virtual scope (input on PC mike input) to view the signal:
or
[url=http://mywebpages.comcast.net/fel4u/oscope/winscope.htm]http://mywebpages.comcast.net/fel4u/oscope/winscope.htm
[/url]
A serial signal analyser:
select the COMx, speed, a.s.o, then do start
The default setting is for FMS PIC serial 19200 x'FF' on COM1
A PPM signal analyser
from the menu select interface=audio, do MONITOR
See the joysticks in your system:
This soft also generates a PCM signal ((simple)PCM code) on the COM port from the joystick input, that can be used elsewhere, with a null modem cable, e.g. to FMS, or to another soft, to record, analyse, etc...
And, as a reminder, Olivier's document about RC transmitters connections:
....................................................................
If you used other diagnostic tools, please append here, for the benefits of all.
Philippe