Digital Acoustics ESBx-110 Especificaciones Pagina 380

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 466
  • Tabla de contenidos
  • SOLUCIÓN DE PROBLEMAS
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 379
IEEE 802.3 Ethernet Communication
ADDvantage-32 PLUS
8-24
UDP Good Receive: counter containing the number of valid UDP frames that have been
received by the drive. In order for the UDP frame to be valid, it must have a valid footprint.
UDP Invalid Type: counter containing the number of UDP frames that were not valid. A
frame will be considered invalid if it does not have a valid footprint. The probable cause of this
type error will be a programming error in the device transmitting the UDP frame.
UDP Null frame: counter containing the number of UDP frames received that had a zero data
length. The probable cause of this type error will be a programming error in the device
transmitting the UDP frame.
UDP Invalid Serv: counter containing the number of UDP frames received that had a valid
footprint but did not indicate a valid service. The probable cause of this type error will be a
programming error in the device transmitting the UDP frame.
PPR Cmd Buf Busy: counter containing the number of PEER PRIMITIVE commands that
were aborted due to the buffer between the ESBX and the drive being busy. This counter
incrementing indicates a communication error between the ESBX module and the drive and
should be reported to Engineering.
PPR Cmd Buf Rclm: counter containing the number of times that the ESBX had to reclaim the
PEER PRIMITIVE buffer from the ADD-32 PLUS. If this counter is incrementing, it indicates
a communication error between the ESBX module and the drive and should be reported to
Engineering.
PPR Respnse Time: number of 5 millisecond time ticks that the ESBX module waited for a
PEER PRIM response from the ADD-32 PLUS. Values of 1-3 are to be expected. Values in
excess of 10 should be reported to Engineering.
PPR Reply: number of valid PEER PRIM replies received from the ADD-32 PLUS. This
diagnostic incrementing indicates PEER PRIM communications activity to the ESBX.
PPR Overrun: counter containing the number of PEER PRIM commands that were discarded
due to an overflow of the PEER PRIM command queue. Increments of this counter indicate
that excessive volumes of PEER PRIM commands are being received by the ESBX module.
This indicates an application problem.
PPR Send Fail: counter containing the number of failures returned by the PEER PRIM socket
send operation. Increments of this counter indicate a probable network configuration problem,
most likely related to the drive IP address, subnet mask, or gateway address.
PPR Xmit Fail: counter containing the number of PEER PRIM RESPONSE frame transmit
failures. Increments of this counter could indicate a possible network configuration problem,
(possibly related to the drive IP address, subnet mask, or gateway address) or a software related
problem.
Vista de pagina 379
1 2 ... 375 376 377 378 379 380 381 382 383 384 385 ... 465 466

Comentarios a estos manuales

Sin comentarios