Why use Terminal?

This is a fault finding tool. Use this application to establish wether a fault lies in the hardware or software.

Since Terminal is a Windows application, if it fails to communicate correctly with the door controllers you can be fairly certain that the problem lies either

  • in the controller
  • the cable
  • the protocol convertor
  • or in the PCs serial port
  • and not in the software or software settings.

Download Windows Terminal and Smartnet_Tester

Quick Guide

It is simple to use Windows Terminal to test the communications with each controller. The network test facility is a utility for examining the operation of a Smart network. It displays numerical information back on screen indicating correct operation. The utility is launched by selecting 'Smart Net Tester' from the Windows Start Menu.

  • Double click Terminal.exe from the SMART directory (C:\SMART\Terminal.exe). Further information about.
  • When Terminal.exe launches go to the File Menu and select the file Network_Test.trm also in the C:\SMART folder.
    • Often this file name is displayed as networ~1.trm instead of the full name.
  • You will be presented with a screen with a number of buttons HELLO 1, HELLO 2 etc.
    • HELLO 1 calls door 1
    • HELLO 2 calls door 2 etc..
  • CHECK - All of the data returned should be numeric characters only.
  • If you receive ANY non numeric characters you probably have a fault in the wiring or the protocol convertor settings. See earthing below.
  • If you get a response, you now need to establish wether the response is valid.
  • See below for more information.
  • If you don't get valid (numeric only responses) then you need to make you network more simple (ie. Only 1 door controller - see below) to help fault find.

Step 1

After launching the application the Windows Terminal screen should look like this...

The screen above will have a small blinking cursor in the top left hand side of the window. This indicates that the utility is ready to receive data.

It is important to understand that when data is displayed (in the form of numbers) on this window it is data being received from the network and not sent.

At the bottom of the window are buttons Hello 1 etc. These buttons represent the respective electronic address of the smart door nodes. If you have a 3 door system then only buttons 1 to 3 are relevant to you. If however, you have a system of greater than eight doors then clicking on the level button will take you to more hello buttons.

When using these buttons you must only click another button when the received data has stoped scrolling in the window.

Step 2

Understanding the data

With the Smart network connected connected click once on button HELLO 1.

Any data returned by the controller (in this case 001) will be displayed on screen. Data will vary but it should return at least the following:

This indicates that smart door node addressed as number 1 (001) is on-line with no event transactions to send.

The data displayed is coming from the network. If you were to type anything it would NOT show on screen.

Step 3

The data may look like the following:

This information is also correct. I will explain the meaning of this returned data.

Line 1

  • Door controller address (001)
  • Has some event transactions to send (00),
  • The quantity of event transactions it is sending (003).

Line 2, 3, 4

  • Data for the events (event type, time, date & card number etc.)

Line 5

  • Indicates the door node address (001)
  • Has just sent event transactions (01)
  • The quantity of event transactions it has sent (003).

The amount of data sent may be as much as 457 event lines complete with the start and end statements.

The golden rule in data reception is that it must always be numeric data received, strange characters and letters indicate poorly functioning networks.
Problem Cause Remedy
In all cases. If you are struggling to get the network to respond, disconnect all doors past door 1 and work with this simplified network. This will make fault finding much easier and faster. If door 1 responds correctly, then adding further doors should be relatively straight forward.
Data is not returned from door controller Protocol convertor is not connected to the correct port (COM1). Insert in the correct port of the PC
Break in the network cable. Check the network cable
The door node address DIP switch is set to the wrong number or not at all Check the DIP switches at the controller
Power is not connected at the door node(s) Switch on power to the door node(s)
Check that the LEDs on the Protocol convertor flicker. Tx LED should light when transmitting (very brief flicker)

If Tx LED does not light then the PC is not send to the network. Check COM1 is connected to the Protocol convertor. Make sure ALL protocol convertor DIP switches are off
Rx LED should light when receiving (may stay on for up to 40 seconds - no longer) If you can see the TX LED flicker, but the RX LED never responds, then check your network connections.
Data from some door nodes is being returned corrupted (ie. non-numeric) Incorrect network connections Inspect network connections
Incorrect cable. Check the cable type and colour code being used.
End of line termination Remove all end of line resistors.
Earthing and / or screening is incorrect Inspect and remedy earthing and screening. Make sure that 0V is NOT connected to earth at any door controller



© Door Entry Direct Ltd