FS-8700-41 Simplex 4100 Driver Manual
Page 38 of 48
FieldServer Technologies
1991 Tarob Court Milpitas, California 95035 USA
Web
: www.fieldserver.com
Tel
: (408) 262 2299
Fax
: (408) 262 2269
Toll Free
: (888) 509 1970
Error Message
Description
To correct this problem, edit the CSV, make the correction, download the
corrected CSV file and reset the FieldServer.
Sim4100:#61 Err. PLC_Type=4100u rqd for
'values'/'earths'
If you have a Map Descritor which has the sim4100_func parameter set to
‘earths’ or to ‘values’ then you must set the PLC_Type parameter on the
node to 4100U. (See section 0
Client Side Node ). It is only appropriate to do so if the firmware version
of your panel is 10.x or later. You can create a map descriptor to read the
version information if you are not sure. You can also use the menu
system on the Panel to read the version number.
To correct this problem, edit the CSV, make the correction, download the
corrected CSV file and reset the FieldServer.
Sim4100:#62 Err. Input Buffer Overflow.
This message is printed when the input buffer overflows. This usually
occurs when the panel sends lots of messages and they are not being
processed by the driver fast enough. A panic is printed immediate after
this message.
The driver will clear the buffer and start capturing new bytes as they
arrive. Messages may have been lost. We advise that you re-synch the
panel.
This error has only been seen once. It occurred when a panel was
connected to the driver with the wrong connection settings.
Appendix C.3.
Driver Stats
Appendix C.3.1.
How the Dri ver counts bytes and messag es received a nd transmitt ed.
"Ack" messages sent/received by the driver in response to read/write messages are NOT counted as messages.
However, the single byte produced by these messages is included in the byte count.
The driver does not count DLL layer messages as messages.
The driver counts bytes at the DLL layer. The byte count includes the bytes that wrap application layer messages,
acks and the port supervision and responses messages.
The driver counts messages at the application layer.. This means that if you use RUINET to monitor the FieldServer
and you view the Map Descriptor’s the byte count stats will always be zero.
Some Map Descriptors require data in the Data Arrays to trigger a write command. An example is the "Ack"
command. The driver does not count one of these messages as being sent until the array actually triggers a poll to
be sent.
