FILE: README.TXT
***************************************************************************
* *
* GoFlight GFRemote Software *
* for use with the GF-AC Cockpit Control System *
* Software Release 1.00, Build 6 *
* *
* Release Notes and General Information *
* Doyle Nickless *
* January 28, 2003 *
* Copyright © GoFlight Inc. All rights reserved. *
* *
***************************************************************************
I. Introduction
---------------
GFRemote is a program that allows you to operate GoFlight cockpit control
hardware over a network of PCs that are communicating with Microsoft Flight
Simulator 98, 2000 or 2002. GFRemote accomplishes this by using a freeware
utility known as WideFS, which is developed by Peter Dowson.
GFRemote works with the following GoFlight products:
- GF-45 Avionics Simulation Units
- GF-45PM Display Panel Cockpit Control Modules
- GF-P8 8-Pushbutton/LED Cockpit Control Modules
- GF-T8 8-Toggle/LED Cockpit Control Modules
- One GF-MCP Advanced Autopilot.
Support for the GF-LGT and GF-166 will be added in the near future.
****************************** Please Note *******************************
GFRemote is NOT meant to be installed and used on computers where
Microsoft Flight Simulator is running. Instead, GFRemote allows you to
connect GoFlight hardware to other networked systems and operate that
hardware with Flight Simulator and other add-on programs (such as Enrico
Schiratti's Project Magenta) that are typically run on a networked system.
**************************************************************************
In this README file, the following terminology is used:
- The term "Main FS computer" is used frequently to refer to the computer
system where Flight Simulator is normally running. In a networked FS
environment with two or more computers communicating over a LAN
connection, this is also referred to in other documents as the "server
computer."
- The term "Networked computer" refers to a system that can communicate
with the Main FS computer via a LAN connection. Sophisticated home
cockpits today often use several networked computers that all communicate
with the Main FS computer.
II. Highlights of this release
-----------------------------
This is release 1.00, Build 6.
This release supports the majority of functions available in the Project
Magenta Boeing MCP/EFIS and Glass Cockpit software packages.
Most testing at GoFlight has been done using the Project Magenta MCP when
operating in the 737NG configuration, but it should operate with the other
configurations (747 and 777) as well.
The following features have been added since the last public release
of GFRemote (Build 4):
+ For users of Project Magenta Glass Cockpit: ND terrain, weather and TCAS
displays can now be turned on and off using GF-P8 pushbuttons or GF-P8
toggle switches.
+ Build number of the Project Magenta MCP is shown in the GFRemote UI
window when detected.
+ Decision Height now works properly when assigned to a GF-45 using
function PM_EFIS_DH.
Below is a list of some of the known issues with this build. I hope to
resolve these as quickly as possible. (But hey, it's still a 1.0 release,
right? And "worth every penny you paid for it"!?)
- P8 or T8 switches assigned to control display of WXR, TCAS or terrain
may have their LED indicators get out of sync if you click on the
onscreen EFIS to set them. Cycling the switches will restore the LED-
to-switch sync in this case.
- You must have the Project Magenta MCP/EFIS package running in order to
control ND Range on the Glass Cockpit. However, you can control ND modes
VOR,MAP and PLN as well as show/hide terrain, traffic and weather with only
the Glass Cockpit running.
- When using the GF-45 to control the MCP mode settings (HDG, SPD, etc.),
turning the GF-45 knob too quickly will sometimes result in a discrepancy
of values between the GF-45 display and the Magenta MCP panel. Simply
moving the knob one detent and then back again should correct the
discrepancy.
- ND map mode control function PM_EFIS_DISP_APP does not work in this
build.
- PM_EFIS_SYM_NDB, PM_EFIS_SYM_STA and PM_EFIS_SYM_VOR are not working in
this build.
- PM Glass Cockpit build number is not getting displayed properly, always
shows 0.
- Currently there is no official documentation for GFRemote, other than
this README file. Most of you guys at this level of the flight sim
hobby are keen enough to operate apps like this without needing much
written documentation. But if you would like to earn some free GF
hardware in return for creating a PDF-format manual for GFRemote,
please contact me by e-mail (BEFORE you start writing!) at
doyle@goflightinc.com . Now there's an easy way to support your flight
sim habit just by writing about something that you enjoy!
Most of these issues will likely require newer builds of Project Magenta
software components in order to be resolved.
III. How to install and use the software
----------------------------------------
To use GFRemote, do the following:
1. Make sure that you have installed WideFS (WideClient/WideServer) on your
main FS and networked computers, and that WideClient on the networked
computer(s) is able to communicate correctly with WideServer.
2. Make sure that the Project Magenta MCP/EFIS package and any other FS-related
software you are running on the networked computer(s) are operating properly.
3. Copy the GFRemote.exe file and this README file into a newly-created folder on
your networked computer.
4. Connect any supported GoFlight devices (GF-45, GF-P8, GF-T8, GF-MCP) that you
wish to operate remotely to USB ports on the networked computer.
To use GFRemote, do the following:
1. Start up Flight Sim on the main FS computer and begin a flight.
2. Run WideClient on the networked computer where GFRemote is installed,
then start the Project Magenta MCP and any other FS-related software
you want to run on the networked computer.
3. Run GFRemote. A message on the GFRemote dialog should now show that
it is connected, and the sim time will be ticking away in the GFRemote dialog.
If you wish to auto run GFRemote when you start WideClient, add a "Run="
statement to your WideClient.ini file, as explained in the documentation
for WideFS.
4. If you have not yet assigned any functions to GF-45s or GF-P8/T8 switches,
click on the Configure button on the GFRemote dialog. You can select
the module type and unit number to be configured at the top of the pop-
up configuration dialog. The "Switch <n>" pull-down listboxes are used
to assign functions to the GF-P8 and GF-T8 modules, and the "Switch 1"
box is used to assign a function to the GF-45 modules.
In this version of GFRemote there are no configurable options for the GF-MCP,
and so none are presented.
5. Once you have selected the functions you want to control, click the Done
button. GFRemote should now be operating.
6. If you find it necessary to minimize the GFRemote dialog on the networked
computer, you can click on the Minimize button at the upper right corner of
the dialog. To redisplay the GFRemote dialog, click on its icon in the
Windows taskbar.
---------------------------------------------------------------------------------
NOTE
To run GFRemote automatically when you start up WideClient, you can add a "Run="
statement to your WideClient.ini file. Please consult the WideFS and WideClient
documentation for more information about the "Run=" statement.
---------------------------------------------------------------------------------
IV. Files in this software release
----------------------------------
This release of software includes the following components:
GFRemote.exe ... The main GFRemote program.
Readme.txt ... These release notes.
V. GoFlight Hardware and USB Hubs
----------------------------------
GoFlight hardware can be connected either directly to a USB port on
your computer, or to an external hub which is connected to a USB port
on your computer. All operating power is drawn from the USB port to
which the hardware is connected.
If you are connecting one or more GF-45s or GF-AC modules to an
external hub, we suggest that you run the hub in "Self Powered" mode
if possible. When a hub is in Self-Powered mode, you supply power to
it using an external power supply, which is typically included with most
higher-quality hubs. Using the hub this way guarantees that each USB
device connected to the hub will have the maximum amount of power
needed to operate.
GoFlight hardware has been tested with the following external USB hubs:
+=================================================================+
| Hub Manufacturer/ | # | Power Supply |
| Product Name | Hub Ports | Current Capacity |
|==================================+===========+==================|
| Belkin ExpressBus Hub | 4 | 2.5 Amps |
|----------------------------------|-----------|------------------|
| Belkin Home & Office Hub | 4 | 2.5 Amps |
|----------------------------------|-----------|------------------|
| Asante' FriendlyNet-Home USB Hub | 7 | 2.5 Amps |
|----------------------------------|-----------|------------------|
| Entrega (Xircom) HUB-7U | 7 | 3.7 Amps |
|----------------------------------|-----------|------------------|
| NEC IntelliBase USB Hub | 4 | 2.5 Amps |
|----------------------------------|-----------|------------------|
| Share Plus USB-107 USB Hub | 7 | 4.0 Amps |
+=================================================================+
GoFlight hardware has been tested with the following peripherals
that contain embedded USB hubs:
+=================================================================+
| Peripheral Manufacturer/ | # | Power Supply |
| Product Name | Hub Ports | Current Capacity |
+=================================================================+
| ADi MicroScan 6P 19" Monitor | 4 | Built-in |
| Model PD-959 | | (Unknown) |
|----------------------------------|-----------|------------------|
| Microsoft Internet Keyboard Pro | 2 | (Bus-Powered) |
+=================================================================+
GoFlight hardware has been tested with the following add-in USB host
controller cards:
+=================================================================+
| Peripheral Manufacturer/ | # | Power Supply |
| Product Name | Hub Ports | Current Capacity |
+=================================================================+
| Entrega 4-Port USB Host Adapter | 4 | Powered from |
| PCI Card (OPTi Chipset) | | PCI Bus |
|----------------------------------|-----------|------------------|
| SIIG "USB DualPort PCI" #US2203 | 2 | Powered from |
| PCI Host Controller Card | | PCI Bus |
|----------------------------------|-----------|------------------|
| KOUWELL KW-2580N 6-Port USB 2.0 | 6 | Powered from |
| PCI Card (NEC Chipset) | | PCI Bus |
+=================================================================+
**********************************************************************
* *
* To all USB device, hub, and add-in card manufacturers: If you are *
* interested in having your hardware included in this compatibility *
* list, please contact GoFlight at the address/telephone number *
* provided at the end of this file. *
* *
**********************************************************************
VI. System Compatibility Issues
-------------------------------
Iomega USB Zip drive
--------------------
If you are using GoFlight hardware on a computer that has an Iomega
USB Zip drive installed, you may experience unreliable behavior
of the Zip drive, or reduced data transfer speeds. This issue
is addressed in the documentation that accompanied your Zip
drive; essentially, Iomega does not recommend sharing the bus
with ANY other USB devices or connecting the Zip drive through
a hub. However, this may change with future hardware or software
releases so please refer to Iomega's printed or online support
documentation for further details.
Motherboard Chipset USB Host Controllers
----------------------------------------
GoFlight hardware is tested with systems incorporating motherboard-
based USB host controllers from Intel, VIA, and SiS, implementing
both the UHCI and OHCI bus protocols. No host controller-related
issues have yet been found.
Add-In USB Hub Adapter Cards
----------------------------
As shown in the table above, the GF-45 has been tested with several
add-on USB adapter cards. No issues were encountered with these cards.
If you have other support or compatibility issues, please consult the
Support page on the GoFlight Web site. It will be updated regularly to
address any newly-discovered issues.
VII. Known Issues In This Software Release
-----------------------------------------
The following is a list of issues that we are aware of with this
release of software.
- GFRemote will not automatically reconnect to WideClient if the connection
is dropped while it is running. This will be fixed in a future release.
- Many extraneous data fields on the dialog, useful for debug but no longer
needed. A simplification of the UI will occur in a future release.
- The NAV and B/C buttons on the GF-MCP are unused. The GFRemote
configuration dialog will allow the user to assign one of several MCP
functions to these buttons in a future release.
VIII. Software Change History
Release Description
======= =================================================================
1.00 GFRemote.exe (12/5/2002)
---- ------------
(Build 1) First quasi-production release. Added support for GF-MCP
just in time for Randy's birthday ...
(Build 2) Fixed bugs with FSUIPC connection tracking, Approach Hold
lighting up wrong button on GF-MCP. Assigned VOR LOC to NAV button
and FLCH to B/C button. Eventually these will be configurable.
(Build 3) Added support for controlling ND mode and map range via
a GF-P8.
(Build 4) Added positive sync logic to compensate for discrepancies
in WideClient/FSUIPC and local data values due to network latency.
Added support for QNH (altimeter barometric) adjustment, and
decision height, though DH adjust still needs some improvement (and
help from Enrico.)
(Build 6) Added TCAS, WXR and terrain display control, fixed DH
adjust (Enrico to the rescue!) and now showing PM build numbers
on the UI dialog. Some stuff broke, I think as a result of some
new code in MCP Build 350. I'm checking with Enrico about the
open issues; likely will need his help to resolve all the
remaining ones.
---- ------------
0.99 GFRemote.exe
---- ------------
First public beta.
IX. Contacting GoFlight
-------------------------
If you wish to reach us, please note the following contact information:
=====================================
Worldwide Headquarters (GoFlight USA)
=====================================
Mailing Address:
11855 SW Ridgecrest Drive
Suite 205
Beaverton, Oregon 97008
USA
Order: 1-866-312-9884 toll free
Phone: 503-671-9317
Fax: 503-671-0168
E-mail: support@goflightinc.com (for technical support-related issues)
dev-support@goflightinc.com (development-related issues)
info@goflightinc.com (general questions or comments)
Also, visit our Web site; http://www.goflightinc.com .
X. Legal Stuff
----------------
This software is supplied at no charge to GoFlight customers, and has
no warranty, either expressed or implied.
That said, GoFlight welcomes your feedback regarding any issues that you
encounter using this product. Feedback and suggestions from our customers
make a big difference in helping improve the quality and the functionality
of GoFlight products.
Iomega is a registered trademark of Iomega Corporation.
Zip is a trademark of Iomega Corporation.
Windows, Windows 98, Windows 2000 Windows Me, and Windows XP are
registered trademarks of Microsoft Corporation.
All other products or product names mentioned herein are trademarks
or registered trademarks of their respective companies.
WideClient and WideServer are freeware utilities developed and maintained
by Peter L. Dowson.
Project Magenta is a collection of commercial software components developed and
copyrighted by Enrico Schiratti.
Copyright © GoFlight Inc. All rights reserved.
END OF FILE: README.TXT
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.