|
NOVAR-NET:
10/28/96 Subject: Access Code Log on Novar-net systems.
Currently, you cannot gain access to the
Access Code Log while on a Novar-net PC/ESS workstation. This capability will be added in the
future.
8/20/96
Subject: Troubleshooting
problems with Novar-net.
When we assist
someone in troubleshooting a Novar-net communications problem, we usually follow
this procedure. We recommend you
try the following before calling technical support:
1) Verify LAN wiring - make sure there are
no shorts, grounds or opens.
2) Verify RS-485 adapter set-up - refer to
the Operator’s Manual for jumper settings and proper wiring.
3) Verify proper software setup in the
autoexec.bat file, per the Operator’s Manual, especially:
·
The essnode command in autoexec.
·
The commdrvr command in autoexec -
check spelling of “COMMDRVR” and make sure you are specifying the proper
comm port (1 or 2). If necessary,
try both comm ports.
·
After checking and adjusting the
set statements, re-boot the computer.
Exit to DOS, type “set” and hit Enter. If all your set statements
were properly executed and accepted, they should be listed on the screen
for you. If they did not execute
properly, they will not be on the list, and you must find out why.
4)
Make sure there is not another device (like a serial mouse or internal
modem) using the comm port or interrupt needed for the novar-net
board. If you are using COM 1, DOS
assigns it (and COM 3) to interrupt 4 (IRQ4). If you are using COM 2, DOS assigns it (and COM 4) to
interrupt 3 (IRQ3). When using a
mouse, make sure it is not on a comm. port that shares your interrupt.
5) Verify memory requirements - at a DOS
prompt, type “MEM”. The largest
executable program size should by 605K for graphics versions and 590 when
not using graphics. If it is less
than that, refer to the tech. tip in the PC/ESS section labeled “Freeing up
memory in a PC”.
6)
Check the voltage at the LAN terminals of the EP/2. From + to shield and from - to shield
you should read approximately 2.5 VDC (+/- 1 volt), fluctuating.
7) At the keypad of EP/2, go into “Tools”,
then “EP/2 Configuration”. The LAN
setup should be set for Novar-net at 9600 baud. If there is no keypad, call the system and check it via
Communication Parameters. If the
system is not downloaded yet, and there is no keypad, put dip switch #6 in
the Off position to set it for novar-net communications.
8)
If you use an adapter on the RS-232 port to go from 9 pins to 25
pins, make sure it is a “straight thru” adapter, and not a mouse adapter or
a cable that does not pass all the pins according to the RS-232 standard.
9) At the Novar-net adapter module, there
are 2 LED’s, “TD” and “RD”. TD
blinks when it receives a signal from the computer. RD blinks when it
receives a signal from other devices on the LAN, like an EP/2. If one of the LED’s is not blinking,
then it is not getting a signal from it’s device.
10)
Once on-line, at the EP directory screen, press the F1 key and set all the
Monitoring Station nodes to Inactive.
This will eliminate nuisance Slave-Net Failure alarms when the Monitoring
Stations are turned off or when they exit the PC/ESS program.
04/03/97 Subject: Novar-net Compatibility of new & old EP/2’s
EP/2’s with PROM version 17.xx work
differently on Novar-net than ones with 18.xx version PROM’s. If you must mix them, then you can get
it to work by downloading the 18.xx EP with 17.xx download files to make it
match the level of the older EP.
This is most easily done with a disk drive (archive) download to the
newer EP (the one with the 18.xx PROM’s).
When it asks you to user define the PROM version of the EP, type in “17.46”. If your EP/2 does not have a disk drive,
call NCC Tech. Support for instructions.
This should only be a temporary solution; the best thing to do is to upgrade the older EP to the newer
PROM level. Tech. Support can
provide more information on this.
|
