News:

Precision Simulator update 10.189 (5 August 2026) is now available.
Navburo update 13 (23 November 2022) is now available.
NG FMC and More is released.

Main Menu

PSX interfaceIT, FDS SYS 1

Started by noo, Tue, 27 Nov 2018 17:16

noo

Hello,
always problem with output.

ReceiverSelL#indicator/03EA00000D7E,249
and
ReceiverSelL#indicator/03EA00000D7E,250

output 249 for ACP left, VHF L
and
output 250 for ACP left VHF C
Confli, bug. It's not possible.

Add an output, an item with the same key has already been added.

What is the problem?
Thank you for one reponse :)

jb747

I believe the way Gary programmed PSXinterfaceIT you can only assign a variable once.

noo

#2
Thank you,
No DEL for all communication panels. BAD for my simulator.

Chris Kilroy

Quote from: noo on Wed, 28 Nov 2018 15:16
Thank you,
it's no good this software. No DEL for all communication panels. BAD BAD BAD

Seems like a lot of complaining considering the software was provided to you absolutely free of charge.

Hardy Heinlin

Noo, there are 3 ACPs on the flight deck. Why do you want to assign multiple selectors to one single ACP? It makes no sense.

noo

thank you for all informations ;)

emerydc8

I am grateful that Gary has been kind enough to make his own software available for free, so there is definitely no room to complain.

What may be happening to the OP is that you can inadvertently attempt to assign a switch to the same input twice, and once you do it, the program locks you out with an unclosable pop-up, so you have to completely remove and reload the software. For instance, you move a switch you are trying to configure thinking that it didn't take the first time when it actually did, then you try it again. This caused the program to display a popup that couldn't be closed unless I reset my computer -- turned the power off and then on) -- Ctrl+Alt+Del wouldn't even close it. Then, I had to re-install InterfaceIT or I'd still get the same pop-up the next time I opened the program..

On my i7 Windows 7 machine, it eventually got to the point where I couldn't even erase the program and reinstall because I kept getting an MS framework message. Rather than re-install Windows 7, which might have worked, I had planned to configure my overhead to my networked i5, but have been so tired on my days off that I just haven't had the motivation to mess with it (e.g., too burnt out from flying to install a program for flying :) ).

Jon

GodAtum

Quote from: emerydc8 on Thu, 29 Nov 2018 09:40
I am grateful that Gary has been kind enough to make his own software available for free, so there is definitely no room to complain.

What may be happening to the OP is that you can inadvertently attempt to assign a switch to the same input twice, and once you do it, the program locks you out with an unclosable pop-up, so you have to completely remove and reload the software. For instance, you move a switch you are trying to configure thinking that it didn't take the first time when it actually did, then you try it again. This caused the program to display a popup that couldn't be closed unless I reset my computer -- turned the power off and then on) -- Ctrl+Alt+Del wouldn't even close it. Then, I had to re-install InterfaceIT or I'd still get the same pop-up the next time I opened the program..

On my i7 Windows 7 machine, it eventually got to the point where I couldn't even erase the program and reinstall because I kept getting an MS framework message. Rather than re-install Windows 7, which might have worked, I had planned to configure my overhead to my networked i5, but have been so tired on my days off that I just haven't had the motivation to mess with it (e.g., too burnt out from flying to install a program for flying :) ).

Jon

Interesting, I'll have to bear this in mind. Is there a better workaround then reinstalling Windows or using a different PC?

Gary Oliver

#8
Noo,

Yes I think if you try to assign the same variable twice bad things will happen.

I will try and get time to have a look at how we would do those switches on the ACPs and if needbe make an update as soon as I find some time.

Unfortunately my ACP's in the simulator go through a Mark Barnes conversion board so I don't use PSXInterfaceIT for this purpose and so wouldn't have seen any issues.

I think I can vaguely remember Jon B or Chris got this working, are you sure you are using the correct variables?

Cheers
Gary

Gary Oliver

Regarding 'Reinstalling Windows'....  WTF???!?

PSX InterfaceIT is a standalone Application that stores everything within the c:\psxinterfaceIT (or whatever folder you install it in) it doesn't use any registry entries or affect anything outside of that folder.

My suggestion would be that after 'uninstalling' there was an INPUTS.TXT or OUTPUTS.TXT file inside the install folder which stayed there after you 'reinstalled' it.

The upshot is everything is within that single folder and deleting that and rerunning the installer would have resolved the issue.

Incase that file does get corrupt there is a backup file I think it creates on startup so you can roll back, however I havn't touched the code for PSXInterFaceIT in about 3 years so I couldn't be sure about that.

emerydc8

QuoteThe upshot is everything is within that single folder and deleting that and rerunning the installer would have resolved the issue.

Believe me, I tried. I went into the inputs and outputs text files and deleted everything that was previously stored there and then uninstalled and re-installed the program. It still gave me the MSframework popup when I tried to assign inputs and outputs. It is obviously a Windows 7 issue, but I don't know enough about it to troubleshoot, so I think I'll try to get it to work on a different computer.

b744erf

Jon
However, I think you should reinstall your Windows. It really seems to be the issue ftom your OS then from the software, while I really can't find any problem. Hope you can use the overhead ASAP. Do remember send me some pics once it come back to live! :p

Gary
Nice to see your reply to this software. Recently, I just bought some old FDS panels wired to the FDS boards already. They are made for a full sim. I used InterfaceIT for 3 years and don't have any big issues except for some interfacing problems.
1. Once I use the fire protection handles, the software will crash totally, though they are successful to assign.
2. The Korry ON lights are always on even when you turn off all the electricity. Hope the outputs are connected with the bus.
3. The indicator yellow lights don't work with the IND LTS TEST switch. They work when they really in "system fault" situation, though.
4. We can't assign more then one inputs to the same var. and we can't assign the same vir to multiple outputs lights.

If these are fixed, I am sure the FDS boards will be one of the best choice for PSX cockpit builders.

Ohh, Just more question ask. I saw the SOLENOID option to choose in the output type. Dose it for the var like ENG START, PARKING BRK, etc? How to assign them and how does it work? Dose it only work with something like a solenoid board from FDS or just works like a general led output with my SYS1 board?

Thanks
Regards
Jack

emerydc8

QuoteJon
However, I think you should reinstall your Windows. It really seems to be the issue from your OS then from the software, while I really can't find any problem. Hope you can use the overhead ASAP. Do remember send me some pics once it come back to live! :p

There's no question that it's a Windows 7 issue. I'll try to configure the overhead using my networked i5 and see how it goes. Reinstalling Windows and downloading all the updates doesn't sound too fun.

Gary Oliver

Jack,

As I don't use the FDS board outputs for anything other than a couple of MIP panel Lights I didn't see these issues.

I will try and work through the list when I find some time, if not maybe a trip to ZGGG with my development laptop and we can fix them live in your sim in a few hours :-)

Cheers
Gary