News:

Precision Simulator update 10.184 (15 September 2025) is now available.
Navburo update 13 (23 November 2022) is now available.
NG FMC and More is released.

Main Menu

PSX keyboard mapping (EPIC etc.)

Started by Hardy Heinlin, Wed, 17 Mar 2010 08:32

Hardy Heinlin

Good morning,

I have changed my plan because I wanted to get more advantages than disadvantages.



Old plan:

Make a table where users can freely map any key or key combination with any flight deck switch or pot. When starting PSX the first time, the default is set to traditional PS1.3 settings.

Advantages:

- More toys in the Instructor window

Disadvantages:

- 1 to 2 weeks developping time and testing

- The Preferences page on the Instructor would be bloated with hundreds of flight deck objects for each key and each key combination, i.e. each item would get a huge pop up menu plus entry fields for the values to be sent to that object (push, pull, turn values etc.)

- Complicated and tiresome menu clicking work for the user (text based would be better)



New plan:

Use the same fixed mapping as in PS1.3.

Advantages:

- Release date 1 to 2 weeks earlier

- Less program bloating

- EPIC users can still use existing PS1.3 settings with PSX, no reprogramming necessary (except for some minor specific things like the new Shift key functions for 3 CDUs etc.)

- Users who really want to map the entire flight deck with multiple keyboards (instead of using the internal simple TCP/IP interface directly) can still map their keys via TCP/IP software indirectly (somebody must write the software, though; but it's easy, especially if it's text based)

Disadvantages:

- Less toys in the Instructor window



Regards,

|-|ardy

Hardy Heinlin

P.S.: I could add some basic keyboard options (just some, not many), e.g.:

Keyboard for EFIS control panel and F/D switch refers to:

(o) Captain's instruments
(o) F/O's instruments
(o) Both

Jeroen Hoppenbrouwers

Since this external switch injector can easily be networked, I see just advantages as well.

J D ADAM

Hi Hardy,  Thank you for your efforts on our behalf. I am sure we all look forward to the finished product.

If I understand you correctly it would seem the keyboard inputs for PSX will match those of PS1.  If so, as an EPIC user, I will be very happy, and even I can do some basic reprogramming, for any minor changes or additions.

At the moment I use Broker to EPIC (B2E) and in this way when I load a situation the displays automatically follow those of PS1. As this program works in conjunction with EPIC, I assume ( and  hope) this will still be the case.

Regards
 
Derek Adam
NZAA

Hardy Heinlin

Hi Derek,

just to be sure, are you using the keys that are described in the PS1.3 manual on page 16, 17 and 31?

Page 31 is the most important one. I will hardcode those in PSX.


Regards,

|-|ardy

J D ADAM


J D ADAM

I have been thinking and that is dangerous! :P

Hi Hardy,
                   I have got the impression  that with the new PSX, that there will be no need for a program such as BROKER.  If this be so, then I am wondering how B2E will work. Your thoughts would be appreciated.

Regards
Derek

Jeroen Hoppenbrouwers

The conceptual equivalent of PS1 Broker is embedded in PSX. Technically, you don't need Broker.

However, we have something available that comes close. To avoid confusion we call it the Router. It can connect several PSX instances and add-ons. Technically all these could also be directly connected, but when the setup grows, there is merit in having a dedicated connection point -- the Router.

Both the Router and PSX speak the same language. Router has more network diagnostics and debugging features, but nothing should need these for normal operations.

The bad news is that the language PSX speaks is not the language that Broker speaks. B2E, and all existing PS1 add-ons, will not work straight away. We do not promise that we will develop a translator, as this would send us down the FSUIPC path, maintaining backward compatibility with a DOS program well into the 21st century.

The good news is that the basic technology of PSX/Router equals that of Broker, so rewriting B2E and other add-ons is a matter of a few hours per add-on as far as the network handling is concerned. And all data items available via Broker are also available via PSX/Router, though usually under a different name.

So, you will need to put time and effort into a translation, but it is definitely possible. It all depends on having the original B2E sources and data tables available, and having somebody available that can reprogram B2E so it becomes R2E.

If EPIC has newer base software available (ten years later), you could also consider to write R2E from scratch.  It isn't rocket science. But having a no-software-change jump from PS1/Broker to PSX/Router is unlikely.


Jeroen

PS. Any other PS1 users who plan to keep EPIC? Or are most others planning to move away from EPIC now there are better alternatives for interfacing?

PPS. I'm open to suggestions as on how to facilitate PSX joint interface development based on the Router language. Any programmers out there?

J D ADAM

Hi Jeroen,
               Thank you for your very full explanation of what is going on in the world of inter connectivity  and its relationship to B2E/EPIC etc.  It has sent a shiver down my spine because I am a complete and utter novice when it comes to programming.
I am fully aware that EPIC is old technology, but it works for me, and the thought of rewiring to incorporate better interfaces fills me with dread.

Matt has suggested to me that it is not as frightening as I think, but you are aware of my age group,  time is "now of the essence  "  Having said that I play golf up to four times a week,  help my wife look after a 21/2 acre garden,and combined with my wife we have 16 grandchildren.

Now if that hasn't brought a tear to the eye of those wonderful programmers on this forum, I do not know what will!!!!

Cheers

Derek
NZAA

Hardy Heinlin

#9
Hmmm, I don't understand why a keyboard "simulator" like EPIC needs any network stuff like Broker. I thought the advantage of a keyboard "simulator" is the fact that it generates keystrokes; keystrokes that are read by the computer's operating system. E.g. if EPIC generates a "F" keystroke, PS1's flight director switch will move, or -- if a text editor is loaded -- an "f" will occur in the text.


Cheers,

|-|ardy

John Golin

..but...but... PSX was the excuse to rip the Epic out of Matt's sim??? :)
John Golin.
www.simulatorsolutions.com.au

Michel Vandaele

Quote from: Jeroen HoppenbrouwersPS. Any other PS1 users who plan to keep EPIC? Or are most others planning to move away from EPIC now there are better alternatives for interfacing?

PPS. I'm open to suggestions as on how to facilitate PSX joint interface development based on the Router language. Any programmers out there?

Hello Jeroen,  
I think interface cards as Phidgets or the FDS-SYS3X System Interface Card from InterfaceIT (FDS) (www.flightdecksolution.com)  are much easier to use now. If a program simular to FS2Phidget (FS9/FSX)  ( http://www.mycockpit.org/forums/forumdisplay.php/123-Phidgets-Interface-amp-Alan-Dyers-FS2Phidget ) would be available then the interface work with the various types of Phidget cards can be done by practical everyone.

B. Rgds
Michel
Michel VANDAELE
Board member  FSCB
EBOS Scenery Designteam
My B744 project
http://users.telenet.be/michel.vandaele/sim1.htm

Matt Sheil

Quote from: John Golin..but...but... PSX was the excuse to rip the Epic out of Matt's sim??? :)
Yes John EPIC will go...
I am running out of old WIN98 computers to run it

Hardy Heinlin

Do you use EPIC in either direction, PS1 to hardware, and hardware to PS1?
If so, I understand. But I don't if you use it for hardware to PS1 only. I thought EPIC is directly connected to the computer like any other keyboard, without a special network in between.

|-|

J D ADAM

Hello Hardy,
                     The EPIC card is a keyboard emulator, and works well (for me) for PS13. Keystrkes are matched with PS1

The B2E program written in jscript by John Cavanaugh institutes all the lights on the switches such as cmd and warning etc on the MCP and all the 7digit readouts such as hdg,spd,v/s etc. It also reads the radio frequencies and transponder readout on the pedestal.
These are picked up through Jeroens Broker and 747IPC.

When I load a new situation every readout on the MCP and pedestal  duplicates what is in PS1 and obviously changes with switch movement..

Jeroens explanation of your router filled me with dread, and as I said I am a complete novice  in programming.

Trust this helps you to understand what seems to be a personal problem, based on old technology

Cheers
Derek

p.s. It is not a major for me to get EPIC to emulate the lights on the switches but the 7digit readouts would be far outside any expertise I may have!

J D ADAM

Hi Hardy,
                 Further to the above.  If it would be of any I could e-mail you a copy of the manual  (explanation and workings) of  B2E.
This amounts to 4 pages only.

Cheers
Derek

Hardy Heinlin

Hi Derek,

in this thread I just wanted clarify that part of the EPIC which goes from the hardware to PS1/PSX, i.e. the keystroke mapping only, not vice versa the controls of the hardware displays.

OK, keystroke mapping is clarified. It should work with PSX as well. Remapping not required.

Controlling the hardware displays with EPIC ... I don't know ... that may be something for the addon developpers next year ... (should be very easy)


Cheers,

|-|ardy

John Golin

Matt's EPIC 'goes both ways'.  The main problem though is it's ISA bus and DOS drivers....!
John Golin.
www.simulatorsolutions.com.au