Wrong controller numbers transmitted

[Demious]

I got used to my controllers (Saitek pro flight yoke, rudder, trim and VRInsight T&T) giving the wrong controller number at the first input when in FSUIPC, but rescanning the same input a second time gave me the right number and it was fine.

But I had to reinstal my system and now I still do get the right number on the second scan, but back in the simenvironment, the wrong numbers are transmitted again: My right brake controls the elevator and the left brake turns the yoke to the left. Even by rescanning the controls, I cant seem to fix this problem.

The yoke itself does give the right numbers and works, but gets comprimised by the brakes, every time I use those.

I do see that the rudder controls are mentioned as controller 1 and the yoke as controller 0, so they shouldnt be on the same channel, but stil they are...

What can I do to get the right input from my controllers?

[aua668]

Hi,

Copyright Pete from another thread:

Please check the section in the FSUIPC user guidle about Joy Letters. If you change to using the Letters for joystick identifiers rather than numbers then FSUIPC will take care of matching the assignments for you
[/CODE]

Check the excellent documentation and you will find the solution.

Rgds

Reinhard

[Demious]

When searching the user guide for the phrase 'Joy Letters' (CTRL-F), nothing was found, also when searching it manually I didnt come accros any topic with a title that could correspond to that phrase.

I asume that 'joystick Identifiers' are the Y- and X-axis, for example, am I right? What numbers should I change to letters to avoid FSUIPC recognising the Y-axis for the X- or Z-axis? I've been looking for numbers behind the axis-controllers, but I cant find anything that would point me in that direction. The only numbers I see there are the input and output vallues and the 256 under de Delta-button, which stays the same with every controller function...

I menaged to solve the problem in the sim environment by reinstalling everything, but still, when in the FSUIPC-interface, when moving the Y-axis, the first reading from FSUIPC is an X-axis response or a Z-axis response, for instance and when rescanning once or twice, it recognises the Y-axis. Also when pushing the rescan button, I first get another axis-input, say the V-axis, without any controller being touched and only the second or third time I push rescan, I get empty fields and I can enter a new input.

[Gypsy Baron]

The reason you need to rescan is probably due to a noisy axis. That is what FSUIPC4 will see. I have an unused

axis on an old joystick that is connected just to allow my old analog rudder pedals to be connected. I have to tell

FSUIPC4 to 'ignore' that axis and then re-scan for the axis I am trying to work with.

The joy names (letters) is an FSUIPC4.ini file entry that automatically assigns letters to your controllers

instead of using the numbers, which are the default method. By using the letters, which are paired with the

GUID of the controller, even if Windows reports a different number for a previously programmed controler

(due to unpluging a controller or reinstalling FSX or Windows) the letters remain the same and all your

programming will continue to work.

In the FSUIPC4.ini file find the "JoyNames" sectionand insert the line below as shown:

[JoyNames]
AutoAssignLetters=Yes
[/CODE]

See page 26 of the FSUIPC4 User Guide.pdf that should be in your Modules\FSUIPC Documents folder. That will explain the

whole operation and the Windows issues it corrects.

Paul

[Demious]

Thanks for the location of that second manual, I hadnt seen there was one in that location, so I've been looking in the wrong one all this time. :mrgreen:

I see there are special requirements for VRInsight modules, as is one of my controllers, so I'm gonna check this out.

Thanks for the help, guys! :razz:

[Demious]

I'm running into some problems with editing the FSUIPC.ini file when setting up VSPE.

I have to add:

[VRInsight]

1=<device>, <driver>

2=<device>, <driver>

and have to replace <device> and <driver> for the serial port names. How do I know which serial ports those are and what they're called?

Just following the example, I see that the created COM5<=>COM6 ends up as COM6 at the <driver> possition of the first line. My created ports show as COM1<=>COM2, so I guess that so far my entry will come to this:

[VRInsight]

1=<device>, COM2

And this is how far I get from the explination. How do I know which actual port the device is connected to?

[Pete Dowson]

And this is how far I get from the explination. How do I know which actual port the device is connected to?

Where does VRI's own driver see it? That's how I always knew. Or look in the Windows device manager and see which port 'disappears' from the list when you pull the plug out

Pete

[Demious]

Thanks for the fast reply, Pete. :)

I wouldnt know where to look for where the driver would see the controller... I know how to use the programs I work with, or at least, the parts that I regularly use, but I'm just a simple user, not programmer, or a computer expert, or anything like that.

But in the list of 'Human Interface Devices' I found a 'USB input device' that disappears when I unplug the controller, but the 'number' isnt a COM-number, it reads: Port_#0002.Hub_#0006

Does this mean that port is called COM2?

[Pete Dowson]

I wouldnt know where to look for where the driver would see the controller.

When I was dealing with VRI devices they came with a program, a driver, to use them. When it ran and discovered the VRI devices it displayed the COM port number. Maybe they don't provide that program any more?

I know how to use the programs I work with, or at least, the parts that I regularly use, but I'm just a simple user, not programmer, or a computer expert, or anything like that.

I wouldn't have thought VRI expected their users to be so in any case.

But in the list of 'Human Interface Devices' I found a 'USB input device' that disappears when I unplug the controller, but the 'number' isnt a COM-number, it reads: Port_#0002.Hub_#0006

Does this mean that port is called COM2?

No, you probably need to look into the part entitled "Ports (COM & LPT)". It seems you are looking in the USB section, not ports?

Regards

Pete

[Demious]

My VRInsight installs a standard driver when I plug it in, it looks the same as when you plug in a new external harddisk and it doesnt show any ports.

I know from a former computer the section 'Com & LPT', but my current one doesnt have that section. I've already googled to find the COM-number and I indeed found a post that directed people to that section, but its not there.

Maybe because my computer doesnt have serial ports at all?

And another question, I'm not sure if I'm doing this the right way. The next part I have to enter in the ini-file, this one:

[Programs]

Run1=READY,CLOSE,d:\VRInsight\SerialFP2\SerialFP2.exe

For one device, I have to enter it like this? And does it have any spaces in the string? I'm not sure if I can see it right.

[Pete Dowson]

My VRInsight installs a standard driver when I plug it in, it looks the same as when you plug in a new external harddisk and it doesnt show any ports.

Hmmm. They've changed things then. No documentation telling you how to find out?

I know from a former computer the section 'Com & LPT', but my current one doesnt have that section. I've already googled to find the COM-number and I indeed found a post that directed people to that section, but its not there.Maybe because my computer doesnt have serial ports at all?

It will if your unit is plugged it.

And another question, I'm not sure if I'm doing this the right way. The next part I have to enter in the ini-file, this one:

[Programs]

Run1=READY,CLOSE,d:\VRInsight\SerialFP2\SerialFP2.exe

That's to run the VRI driver which I thought you said you didn't have?

For one device, I have to enter it like this? And does it have any spaces in the string? I'm not sure if I can see it right.

If that the proper path to the VRInsight driver called "SerialFP2.exe"? If so, then it is correct, if not it is incorrect. Sorry, I cannot see your PC from here, I cannot find your files for you.

I think you might be better off asking these things in the VRI support forum. I've not handled any VRI devices for several years now. I think they've changed things quite a bit.

Regards

Pete

[Demious]

Hmmmm, I bought a second hand VRI T&T and I got the controller only, so I'm not sure what has been in the package originally. If you say the serialFP2.exe is the driver that comes with the controller I guess that line isnt meant for the way I setup my controller.

When I got the controller plugged in, no section called COM & LPT appears...

I'll have a look at VRI drivers on their site, see what I can find out and I'll get back to you when I know more.

Thanks, Pete

[Pete Dowson]

Hmmmm, I bought a second hand VRI T&T and I got the controller only, so I'm not sure what has been in the package originally. If you say the serialFP2.exe is the driver that comes with the controller I guess that line isnt meant for the way I setup my controller.

VRI have a website, which is where you can download documentation and drivers. That's where I got mine.

When I got the controller plugged in, no section called COM & LPT appears...

Hmm. Strange. quite honestly I don't know how you find the correct port number then. I'm sure VRI's own stuff can help though, or better the Support forum.

BTW I just noticed from your first message that your device is a VRI "T & T". Would you mind telling me what a "T & T" is? Are you sure it is really a serial port device, not a plain USB controller? I know most of VRI's recent products haven't needed or used FSUIPC. The facilities you are trying to use are for these devices, the only ones I know:

"MCP Combi", "M-Panel", "CDU 2", "CDU", "Micro Prop Pit", "Micro Jet Pit", "Radio Stack", "Prop Pit", "Jet Pit", "Flight Monitor", "MFD", "GPS5", "MCP2 Boeing", "MCP2 Airbus"

[LATER]

I went to VRInsight's website. Your "T & T" appears to be this:

The Tack & Toggle Switch panel by VRinsight enables a user control all functions of most flight & fighter software.

15 push buttons, 6 On/Off switches and 11 toggle switches are all programmable for your software in order to ensure maximum controls.

With simple USB connection, backlit blue LED will illuminate leading a efficient flying in the nighttime

As far as I can see it is a basic USB joystick-type controller. You should be able to assign the switches and buttons in the FSUIPC switches and buttons assifgfnments page. I don't know why you are messing with the facilities for VRI's serial port range.

Regards

Pete

[Demious]

T&T is the tack and toggle switchboard: http://www.fspilotsh...nel-p-2856.html

What I found is that VRInsight T&T is recognised by windows as a 'proper USB joystick device', as it is explained and I see that for several controllers there's a download for serialFP2, but the T&T has a manual only.

According to the manual the T&T is recognised as a Human-interface Device and nothing is written about FSUIPC, or VSPE, only basic information about the standard way to setup the controller through the sims own controller setup.

And I found something on the VRinsight forum about writing a LUA-script for T&T, when working with FSUIPC, but they send the writer of the post they answer to this forum to ask about that:

"What you need to do is ask this question over at the FSUIPC support forum, you will need to write a LUA script to sync the switches at start up."

That's about it, everything else that came up when searching for VRinsight T&T/FSUIPC/VSPE came up with other modules than the T&T.

So in short: No serialFP2 for T&T panel and Pete Dowson knows how to fix it. :P

The FSUIPC advanced manual was talking about VRInsight modules in general, without any exceptions mentioned, so I guessed the T&T should be handeled the same.

I can indeed connect the switches to the functions in the sim, only FSUIPC recognises the numbers wrong on the first input and assigns a wrong controller number to them. This means that when I, for example, use the switch that is programmed for the prop sync, on the first input it turns the master avionics off and on the second input, it switches on the prop sync...

[Pete Dowson]

T&T is the tack and toggle switchboard: http://www.fspilotsh...nel-p-2856.html

Please re-read my last message. I did look it up!

The FSUIPC advanced manual was talking about VRInsight modules in general, without any exceptions mentioned, so I guessed the T&T should be handeled the same.

Sorry, but when that was all done the only VRI devices were all serial port devices and I was adding support for them as they came out. They've not contacted me abut any others. Next time I make an update for the manual I'll list the supported devices and be done with it. But that might be some time yet.

I can indeed connect the switches to the functions in the sim, only FSUIPC recognises the numbers wrong on the first input and assigns a wrong controller number to them.

FSUIPC recognises devices by the numbers supplied by Windows. they are not "wrong". If you have something also connected which is giving inputs all of the time then it will see that first. Please read the first answers you got in this thread from another user. He seemed to give the correct advice way back then!

you will need to write a LUA script to sync the switches at start up."

Synching switches at start up is rarely a necessity, it is just a nicety. You can do it in any case, best by always leaving the switches in the same state on close down and loading the aircraft in the same state on start-up. Or else simply use the screen rendition of the switches to match the hardware condition.

This means that when I, for example, use the switch that is programmed for the prop sync, on the first input it turns the master avionics off and on the second input, it switches on the prop sync...

What's that got to do with the controller number? How many "controllers" do you have? Is the T&T more than one HID device?

I'm sorry, I don't understand your problem at all. And really, unless VRI supplies me with a device to test (which is unliley as they don't really need FSUIPC), I cannot diagnose their problems. I only provide FSUIPC as a tool for all normal devices. If the VRI ones play differnt games then VRI will need to advise on support. There must surely be other users who can help you too? On the VRI forum?

Did you ever try assigning the switches in FS itself instead? Why exactly are you using FSUIPC for this?

Pete

[Andydigital]

This means that when I, for example, use the switch that is programmed for the prop sync, on the first input it turns the master avionics off and on the second input, it switches on the prop sync...

To me that sounds like you have some messed up assignments, probably two different ones assigned to the same switch. Maybe one assigned in FSX directly via its control assignment system and another assigned in FSUIPC. Either that or you have something assigned to the press function and something else assigned to the release function in FSUIPC.

[Demious]

I've got the controller numbers changed to letters now and this indeed fixes that problem for the axisses and switches from the Saitek controllers, but not for the VRI controller, even though this one is also recognised by a letter now.

I've checked for double programmed buttons a dozen times already, but I cant find anything, there... In P3D the controllers are turned off and I even deleted all controllers from key-assignment list.

I can also see in the buttons programming window from FSUIPC what happens.

For example, the first time when I push the button with controller #21, FSUIPC reads controller #18 in the readout, with the commands listed, programmed for controller #18.

This picture is taken after using the switch with controller #21 the first time:

A simple second click on the same button and the readout says #21 with the commands listed for controller #21 as can be seen on this picture, taken after the second click of the same switch:

I uninstalled and reinstalled everything, multiple times, created new setting-files, changed numbers that adress which controller is sending the commands to letters, as can be seen in the pictures, which had the right effect on the saitek controllers, but nothing has any effect on the VRI T&T.

[Pete Dowson]

I uninstalled and reinstalled everything, multiple times, created new setting-files, changed numbers that adress which controller is sending the commands to letters, as can be seen in the pictures, which had the right effect on the saitek controllers, but nothing has any effect on the VRI T&T.

Uninstalling and reinstalling usually causes more problems that it solves.

If the one switch you are using gives a different button number, alternately, the either it is meant to do that )which I'll explain in a moment) or it is faulty. I can't tell you which, you'd need to ask VRI, or use a test program which shows you exactly what is going on.

In the serial port VRI devices, every button gave two different signals, alternately. In order to program a button to do one action then you had to program both of those to the same action. Or you could treat it like an on/off toggle switch and have one of the pair of inmputs turning something on, and the other turning it off. I suspect that was VRIs intentions.

If your one switch/button gives both 18 and 21, alternately, then either it is because those are the set values for that switch, or there's a fault someplace -- perhaps in the hardware or the connection.

Regards

Pete

[Demious]

The way you explain it now, wouldnt that mean that the same switch gives two constant vallues? I mean, that the #21 will always switch with #18? Because that is not what happens, it is completely random. I took 21 and 18 for the example, because that was the one that came up when I took the pictures. And it also doesnt happen everytime, its about half of the time that another number is recognised on the first input.

The 18/21 from the example are both indeed a 2-way switches, but from what I see in FSUIPC, the off-possition doesnt give a controller-signal. If the switch is in the on-possition when I enter the FSUIPC-menu and I turn it off, FSUIPC doesnt register any input. I havent seen anything that looks like two steady control numbers for one switch or button. It's the actual control number as shown in the manual, switched with a random control number, this time it was #18, but next time it might as well be #24.

I'll show you the control-setup as it is shown in the manual, maybe that tells you someting.

Maybe I'm interpreting the chard wrong, but to me it looks like every button or switch has just one control number. (The actual number changes 1 possition, though, the A1 is controller #0, A2 is #1 etc. and the C2-C5 buttons are #34/#36/#38/#32)

And I did ask at the VRI forums, but there I got send back here...

[Pete Dowson]

The way you explain it now, wouldnt that mean that the same switch gives two constant vallues?

Only if it wasn't a fault, but a designed feature.

I mean, that the #21 will always switch with #18? Because that is not what happens, it is completely random. I took 21 and 18 for the example, because that was the one that came up when I took the pictures.

The 18/21 from the example are both indeed a 2-way switches, but from what I see in FSUIPC, the off-possition doesnt give a controller-signal. If the switch is in the on-possition when I enter the FSUIPC-menu and I turn it off, FSUIPC doesnt register any input. I havent seen anything that looks like two steady control numbers for one switch or button. It's the actual control number as shown in the manual, switched with a random control number, this time it was #18, but next time it might as well be #24.

It most certainly sounds faulty then. Either the switch indications are "flickering" (i,e. giving spurious indications) each time you cause an input by operating one, or the interface is adding the spurious indications.

I'll show you the control-setup as it is shown in the manual, maybe that tells you someting.

Well, it implies that they are separate switches for each button, certainly. Doesn't tell me why it's misbehaving.

Pete

[Andydigital]

It does indeed sound strange and it doesn't do that on my panel. If you had explained the situation more clearly at the VRi forum months ago I probably wouldn't have sent you elsewhere for assistance. The way it was explained to me back then had me convinced 100% it was a assignment problem.

Best thing to do is email tech support and explain to them in the same sort of detail that one particular button on you TT panel is intermittently registering a different button id number when pressed.

Can you confirm it does the same thing in the Windows joystick calibration/settings app?

[Demious]

Ah well, at least we managed to come to a conclusion. :)

I'm gonna see what I can do to get the unit repaired and this week I heard that my new custom controllers are ready, so when they arrive the T&T will be a less prominent item in my setup. I'm sure everything will turn out well.

Thanks a whole lot for your help, guys! :D

Cheers!