FieldServer 1.1 user manual Connection Overview Error Statistics Aspect, Nak

Page 16

Ruinet Utility User Manual

Page 16 of 46

2.3.4.Connection Overview - Error Statistics Aspect

Parameter

Description

 

 

Connection

The current connection being displayed out of the total number.

PEX No slave

Pex mode tried to create a cache block and failed - normally a

failed write-through. See Driver Manual for further information

 

Server Overruns

A message arrived from the upstream device while the server port

was on hold. Increase the timeout setting in the external device.

 

Server Hold Timeouts

If an upstream device requests data from a cache where the data

is too old then the data will be refreshed by polling from the

 

downstream device. The response was not received in time.

 

A remote device never responded to the FieldServer poll. Either

 

the device is not responding, or one of the timeout parameters is

Timeouts

set too low.

Ensure that the device is online and addressed

 

correctly and if necessary increase the relevant timeout parameter

 

in the CSV file.

 

Checksum Errors

External influences e.g. electrical noise corrupted the data.

Check that communication cables are shielded, not too long and

 

do not run past power cables.

 

Protocol Errors

An external

device responded with unexpected or

unknown

messages. Consult the relevant driver manual.

 

 

 

Noise

Corrupted or garbage bytes on a communications line.

 

Bad Length

A message that looks Ok, but is of the incorrect length.

 

Bad Node

A no-response/error response from an addressable

external

device.

 

 

 

 

 

Bad Function

E.g. an external device is written to that does not support writes.

No Start

Communications to an external device could not be started.

PLC exception

A variation of a NAK message produced by some protocols.

NAK

A NAK message is received in response to a poll.

 

 

Data seems to be continuously arriving from an external device.

 

This could be due to a mismatch in baud rates.

 

 

Streaming errors are typically produced when:

 

Streaming

1) The transmitter sends more data than the FieldServer can

process.

 

 

 

2) An unexpectedly long message is received or messages have

 

been corrupted so that the end of a previous message cannot be

 

detected.

 

 

 

3) A message longer than the driver expects has been received.

 

A response from an external device arrived before it was

 

expected, implying that it is not the response for the poll the

Premature

FieldServer has just sent. This could occur when there are time

delays in communication networks which contain bridges and

 

routers which may delay messages for longer than expected.

 

Increase the timeout parameter for the connection to eliminate

 

these errors.

 

 

Preamble

Characters preceding a message were dropped.

 

IC Timeouts

Too much time between receiving successive bytes in a message.

Address Errors

A driver tried to address a wrong device or a wrong block of data

within an external device.

 

 

 

Data Object offline

A poll was received for a node that is offline.

 

Node Offline

An external

device node is offline in response to a

driver or

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

Image 16
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 PCObtain the IP address using the Dhcp Client Procedure to Change a FieldServer’s IP AddressChange 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.7. Startup Screen Appendix B.6. Restart a FieldServer -bAppendix B.8. Transferring files -l, -f Appendix B.9. Downloading Files -u0 Appendix B.10. Uploading Files -u1Appendix B.12. Number of File Transfer Tries -n Appendix B.11. Forcing a Download -oAppendix 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.22. Run in Test Mode Appendix B.21. Set Timeout -kAppendix 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