Specifications

IEEE 802.3 Ethernet Communication
ADDvantage-32 PLUS
8-11
X***: WEB passWrd: <<<<< FUTURE USE TO ENABLE ACCESS TO DRIVE’S WEB
PAGE>>>>>>
Drive Configure Menu – “Y” Parameters
Y***: ETHRNET COM: DISABLE, ENABLE, AUTO-ENABLE, default = AUTO-ENABLE
This parameter determines if the drive will communicate via ETHERNET. If this parameter is
set to DISABLE or AUTO-ENABLE, then an ESBX Ethernet board is not required on the
drive for correct operation. If the parameter is set to ENABLE, then an ESBX Ethernet board
must be installed for the drive to operate. If there is no ESBX Ethernet board installed but the
ETHRNET COM parameter is set to ENABLE, the drive may operate erratically and/or reset
unexpectedly.
If ETHRNET COM is set to AUTO-ENABLE, then the drive will attempt to determine if the
ESBX Ethernet board is installed as part of the power-up sequence. If the ESBX Ethernet board
is detected and correctly initialized, its presence will be indicated under the DIAGNOSTICS
menu of the drive keyboard/display. The drive LCD display will show:
DRIVE COM ID:
xx (ETH)
where xx = Drive ID # and ETH indicates presence of ESBX Ethernet board.
Y083: ETH AUT-RST: DISABLE, ENABLE, default = DISABLE
MUST BE SET TO DISABLE
8.4 ESBX ZAP – DOWNLOADING FIRMWARE TO ESBX ETHERNET BOARDS
The ESBX Ethernet board firmware is stored in Flash Memory. Although not normally a field
requirement, this firmware can be Field upgraded via Ethernet using Avtron’s ESBX_Zap
program (PN 682937) from the source computer, usually the ADDAPT 2000 PC. Normal
operation of the ESBX Ethernet board will cease upon start of ESBX ZAP which will take up
to 3 minutes to complete. The ESBX board will provide indication of completion of the ZAP
program by an alternating flash of CR2 and CR3 LED’s. Use caution as a power cycle or drive
reset during the ZAP operation or before the ZAP is complete will render the ESBX board
inoperable and will require factory reprogramming at Avtron.
Zapping an ESBX board on a running drive is not totally risk free. However, there should not
be a problem unless the drive is configured to generate a fault on a COM LOSS, or you have
other ETHERNET devices attempting to communicate to the drive during and after the ZAP. If