FieldServer Technologies Video Game Controller 1.1 Benutzerhandbuch

 
 

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA  Web:www.fieldserver.com 

Tel: (408) 262-2299   Fax: (408) 262-9042   Toll_Free: 888-509-1970   email: support@fieldserver.com

 

The following situations can prevent Ruinet from connecting to a FieldServer: 

•  Bad or incorrect Ethernet cable. In this case the connection lights on the FieldServer 

and/or PC will not be illuminated either 

•  Incorrect Ethernet card and/or protocol setup. In this case Ruiping probably won’t work 

either. Contact the Systems Administrator to have an Ethernet port set up correctly. 

•  If two FieldServers with different names have the same IP address then these are 

shown in red in the list of FieldServers.  Ruinet cannot be used with these FieldServers 
except to restart them.  Disconnect one FieldServer from the network and change the 
other FieldServer’s IP address to a different value using Ruinet which will connect now 
that there is only one FieldServer. 

•  If a FieldServer is not on the same subnet as the PC, and there is more than one 

FieldServer on the network, then it will not be possible to use broadcast mode to cross 
subnets. Disconnect the other FieldServers and use broadcast mode, or change the IP 
address of the “orphan” FieldServer to put it in the same subnet and then reconnect the 
other FieldServers. 

•  Ruinet uses UDP port 1024. Ensure that the firewall or router is not blocking this port. 

•  If the FieldServer is connected to the host computer’s network on adapter N2 then the 

SMT protocol must be defined for the N2 adapter in the config.csv file. Add the following 
lines to the file only if it is not possible to connect to N1 instead: 
 

Adapters 

 

Adapter, 

Protocol 

N2, 

SMT 

 

•  Unless a path is specified for the local file name then Ruinet expects to find the local file 

in the same folder as that in which Ruinet was launched or in the folder set as the 
working directory (as specified in the Windows shortcut). If the file cannot be found then 
an error is reported. 

•  The local and remote file names must meet the DOS 8.3 file name format requirements. 

•  There must be sufficient flash disk space on the FieldServer. 

•  If the download of files like fserver.img (the firmware file) or config.csv (the configuration 

file ) fails before completion then the next time the FieldServer is restarted the 
FieldServer will try and run with corrupt firmware or a corrupt configuration. If the 
firmware is corrupt then future downloads may not work at all and the user may need to 
follow a recovery procedure. The procedure is available on the FieldServer website as 
an application note.