FieldServer 1.1 user manual Appendix A.2. File Download

Page 36

Ruinet Utility User Manual

Page 36 of 46

Appendix A. Troubleshooting

Appendix A.1. Connection to a FieldServer

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

Appendix A.2. File Download

•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.

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

Page 35 Page 37
Image 36
Page 35 Page 37
Contents Ruinet Version RevTable of Contents Appendix C Advanced Topics Installation and Setup General OverviewPC Requirements Hardware SoftwareRemote User Interface RuiNet Connecting to a FieldServer FieldServer Information Settings Aspect FieldServer InformationFieldServer Information Settings Aspect Parameter DescriptionFieldServer Information Status Aspect Connection Overview Connection Overview ScreenConnection Overview Settings aspect Connection Overview Settings Aspect Reference source not found. for further informationConnection Overview Status Aspect Connection Overview Statistics Aspect Descriptor. See Error! Reference source not found Parameter Description Connection Overview Error Statistics Aspect NAKConnection Overview API Aspect Parameter Description Node Overview Node Overview ScreenNode Overview Settings Aspect Node Overview Status Aspect Node Overview Operating Statistics AspectParameter Description Node Overview Error Statistics Aspect Map Descriptor Overview Map Descriptor Overview ScreenMap Descriptor Overview Settings Aspect Map Descriptor Overview Status AspectMap Descriptor Overview Operating Statistics Aspect Map Descriptor Overview Error Statistics Aspect Data Array Overview Data Array Detail ScreenError Messages Driver MessagesDownload Configuration to FieldServer Procedure for Downloading a File from a PC to a FieldServerUpload Configuration from FieldServer Procedure to Upload a File from a FieldServer to a PCProcedure to Change a FieldServer’s IP Address Obtain the IP address using the Dhcp ClientChange IP Address Obtain the IP address using the FieldServer’s Dhcp Server Change UI Display Mode Restart FieldServerPage Appendix A.2. File Download Appendix B.2. Connecting to a FieldServer using Name -y Appendix B.3. Broadcast Mode -ibAppendix B.5. Disable Auto Connect Mode -m0 Appendix B.4. The Most Recently Connected FieldServer -pAppendix B.6. Restart a FieldServer -b Appendix B.7. Startup ScreenAppendix B.8. Transferring files -l, -f Appendix B.9. Downloading Files -u0 Appendix B.10. Uploading Files -u1Appendix B.11. Forcing a Download -o Appendix B.12. Number of File Transfer Tries -nAppendix B.14. Set Local File Name for a Transfer -l Appendix B.15. Help -h Appendix B.16. Create a Log File -aAppendix B.17. Version Information -v, -ve Appendix B.18. Skip date and time check on connect -m1Appendix B.21. Set Timeout -k Appendix B.22. Run in Test ModeAppendix B.19. Delete a File -z Appendix C.2. FieldServer Tiers Appendix C.3. Connecting to a FieldServer over the Internet Diagram below shows how this is typically doneAppendix D. Default settings for parameters Parameter Default Setting
Top Page Image Contents