Home products FAQ support partners about us contact us
 
Sierra Technology - Hardware FAQ
 
 
 

 

 

Hardware Frequently Ask Questions : <%if Request("type")="ST8k" then%> ST8000 <%elseif Request("type")="StarTime" then%> StarTime <%end if%> Case <%=Request("index")%>


 

<%if Request("type")="ST8k" then%> <% if Request("index") = "1" then%> Case1. Communications down - entire network or one bus.

Possible Causes and Solutions:
1. Reason :- Communications port and software settings may not be right.
  Action :- Check the settings for the communications port, bus number to comm. port assignment, Controller address assignment in the ST8000 Application software.
2. Reason :- PCI is not powered up.
  Action :- Check incoming PCI 12 volt DC supply.
3. Reason :- PCI communications line driver has burnt out - IC SN75176
  Action :- Check incoming PCI 12 volt DC supply.
4. Reason :- 4W/2W jumper settings on the PCI are wrong.
  Action :- Check the jumper insertion is correct.
5. Reason :- One unit is pulling the entire bus line down
  Action :- Disconnect all controllers from the bus and start by inserting each one back onto the bus one by one. In this way the problematic unit can be isolated as the units are inserted back onto the bus.
6. Reason :- Addresses of controllers not set
  Action :- Check or set the addresses of each individual controller.
7. Reason :- The communications cable may have a short circuit.
  Action :- Trace and rectify the short circuit.


<% elseif Request("index") = "2" then%> Case2. Communications down or not stable - one or several readers on the network.

Possible Causes and Solutions:
1. Reason :- Software settings may not be right
  Action :- Check the settings for the bus number assignment, Controller address assignment in the ST8000 Application software.
2. Reason :- Address conflicts may be occurring
  Action :- Check the Proxstation addresses.
3. Reason :- SN75176 RS485 communications line driver may be faulty
  Action :- Change the line driver. Power down the unit before changing the IC.
4. Reason :- Communications cable termination into 'C+' and 'C-' terminal may be in reverse.
  Action :- Check the termination.
5. Reason :- There is no continuity from the 'C+' and 'C-' terminals on the ST8000 PCU to terminals 2 and 3 on the Proxstation
  Action :- Terminals 2 and 3 (8 core screen termination terminal blocks) of the ST8000 PCU are internally connected to the C+ and C- terminals. Do a continuity test with a multimeter to confirm the continuity from C+ to terminal 2 and from C- to terminal 3. If there is no continuity on either of the described above the connection from C+ to terminal 2 and from C- to terminal 3 is broken. A temporary solution would be to terminate the communications cable directly into terminals 2 and 3 with the 8 core screened cable.
6. Reason :- Communications cable/ network is long.
  Action :- Insert the 100 ohm watt termination resistor.
7. Reason :- The Proxstation unit may be faulty.
  Action :- Replace the unit.
<% elseif Request("index") = "3" then%> Case3. Lock fails to release or is not powered up

Possible Causes and Solutions:
1. Reason :- The raeder may be in the 'Security off' or the 'Auto lock release time zone' may be active.
  Action :- Check the ST8000 application software for these settings. Check the reader via its keypad and LCD for these settings.
2. Reason :- The 'Lock release time' is set to 0 seconds causing the Proxstation to immediately rearm the lock.
  Action :- Check ST8000 application software . Check the Proxstation via its keypad and LCD.
3. Reason :- Lock contact jumper setting is not correct.
  Action :- Check the normally open or normally closed contact of the lock relay. This will depend on the type of locking device used.
4. Reason :- The door sensor is faulty or is always closed causing the Proxstation to rearm the lock immediately.
  Action :- Check door sensor loop, wiring and continuity on the ST8000 PCU.
5. Reason :- Break glass or by pass key switch unit may not be wired up in the normally closed position.
  Action :- Check cabling.
6. Reason :- Lock fuse has burnt out.
  Action :- Replace the fuse. 3 ampere only.
7. Reason :- There is no output from the lock output
  Action :- Check the output voltage from the lock output terminals with a meter. When doing this, a load will have to be inserted into the terminals. Insert an LED with a 1 k ohm 2 watt resistor soldered to it . A load is necessary because there is a 10uF capacitor across the lock output terminals. This capacitor will fool meter readings without the presence of the load.
8. Reason :- One of the 8 core screened cables are not terminated properly.
  Action :- Check that there is a continuity from the Proxstation to the PCU.
Note: If this is the possible problem then, all the other inputs like the alarm inputs, door sensor as well as the outputs - lock will not work.
9. Reason :- Lock is faulty.
  Action :- Change the lock.
10. Reason :- PCU is faulty.
  Action :- Change the PCU.
<% elseif Request("index") = "4" then%> Case4. Push button not working.

Possible Causes and Solutions:
1. Reason :- The push button is not in an active time zone or the push button settings of the Proxstation is not enabled.
  Action :- Check the ST8000 application software. Check the Proxstation via its keypad and LCD
2. Reason :- The push button wire loop is broken or always open
  Action :- Check wiring from the PCU to the push button.
3. Reason :- The push button input on the ST8000 PCU is faulty.
  Action :- Test the push button input. To do this, try by shorting/closing the push button loop. If there is a response then it could be the cabling else change the PCU.
4. Reason :- The 8 core screened cable is not terminated properly.
  Action :- Check the continuity of the 8 core screened cable from the Proxstation to the PCU.
Note: If this is the possible problem then, all the other inputs like the alarm inputs, door sensor as well as the outputs - lock, will not work.
<% elseif Request("index") = "5" then%> Case5. Door sensor not working - the Proxststaion is continuously beeping indicating that the door is open.

Possible Causes and Solutions:
1. Reason :- The door sensor wire loop is broken or always open.
  Action :- Check wiring from the PCU to the door sensor
2. Reason :- The 8 core screened cable is not terminated properly
  Action :- Check the continuity of the 8 core screened cable from the Proxstation to the PCU.
Note: If this is the possible problem then, all the other inputs like the alarm inputs, door sensor as well as the outputs - lock, will not work.
3. Reason :- The door sensor input on the ST8000 PCU is faulty
  Action :- Test the door sensor input. To do this, try by shorting/closing the door sensor loop. If there is a response then it could be the cabling else change the PCU.
<% elseif Request("index") = "6" then%> Case6. Alarm input not working - the Proxststaion is not responding when the alarm zone is tripped or triggered.

Possible Causes and Solutions:
1. Reason :- The alarm input is not in an active time zone or the settings of the Proxstation is not enabled.
  Action :- Check the ST8000 application software. Check the Proxstation via its keypad and LCD.
2. Reason :- The alarm sensor wire loop is broken or always open.
  Action :- Check wiring from the PCU to the alarm device.
3. Reason :- The 8 core screened cable is not terminated properly
  Action :- Check the continuity of the 8 core screened cable from the Proxstation to the PCU.
Note: If this is the possible problem then, all the other inputs like the alarm inputs, door sensor as well as the outputs - lock, will not work.
4. Reason :- The alarm input on the ST8000 PCU is faulty.
  Action :- Test the alarm input. To do this, close the alarm input loop of the suspected loop. Arm the Proxstation alarm system (refer to software manual). Trigger the alarm by opening the loop. If there is a response then it could be the cabling else change the PCU.
<% elseif Request("index") = "7" then%> Case7. Alarm does not trigger even though alarm has been tripped in the ST8000 application.

Possible Causes and Solutions:
1. Reason :- Software settings for the alarm system not correct for the Proxstation in question.
  Action :- Check the ST8000 application for these settings. The wrong Proxstation may have received the arm alarm command.
2. Reason :- Alarm relay 2 contact settings not in the correct operating position
  Action :- Check the relay 2 contact jumpers settings
3. Reason :- Relay 2 may be faulty.
  Action :- Check the relay 2 contact for continuity. Using a meter set on a continuance test mode check for the normally open and normally closed contact. If test fails, replace the PCU.
<% elseif Request("index") = "8" then%> Case8. 'Time out' LED consistently on and 'load' LED is off - Proxstation not running.

Possible Causes and Solutions:
1. Reason :- The Proxstation is not terminated to the PCU properly.
  Action :- Check connections between the ST8000 PCU and the Proxstation - 8 core screened cable.
2. Reason :- Proxstation fuse has blown. 1 Ampere fuse on the ST-BC3 I/O logic PCB.
  Action :- Replace the fuse.
3. Reason :- Proxstation unit is faulty.
  Action :- Replace the proxstation.
4. Reason :- PCU is faulty.
  Action :- Replace the PCU.
<% elseif Request("index") = "9" then%> Case9. 'Time out' LED consistently on and 'load' LED is off - Proxstation is running.

Possible Causes and Solutions:
1. Reason :- PCU is faulty.
  Action :- Replace the PCU.
Note: There is the possibility that if bot the 'time out' and 'load' LED's don't work, them the 'AC fail' and 'low batt' LED's will also not work.
<% elseif Request("index") = "10" then%> Case10. No back up battery output.

Possible Causes and Solutions:
1. Reason :- Battery is weak and the PCU has disconnected it.
  Action :- Allow the battery to charge up or replace with a fully charged unit. Note that 'low batt' indicator should be on.
2. Reason :- Battery fuse has blown.
  Action :- Replace the battery fuse.
3. Reason :- Battery relay is faulty.
  Action :- Replace the PCU.
4. Reason :- PCU battery charge circuitry has failed.
  Action :- Replace the PCU.
<% elseif Request("index") = "11" then%> Case11. No DC output from the 'Dc out' terminals.

Possible Causes and Solutions:
1. Reason :- PCU is undergoing current limiting.
  Action :- Check the of current drawn by all equipment connected to the PCU. Load the PCU with less equipment. Make sure that no short circuits are occurring.
2. Reason :- PCU is faulty
  Action :- Replace the PCU.
<% elseif Request("index") = "12" then%> Case12. The ST8000 PCU does not power up.

Possible Causes and Solutions:
1. Reason :- 13 Ampere fuse in the supplied 13 ampere 3 pin plug has blown.
  Action :- Check and replace if necessary.
2. Reason :- 240 Volt AC to 15 volt AC step down power transformer is faulty.
  Action :- Replace the transformer else replace the PCU.
<% elseif Request("index") = "13" then%> Case13. PCU output is less than 12 volts DC

Possible Causes and Solutions:
1. Reason :- PCU under calibrated.
  Action :- Replace the PCU.
<% elseif Request("index") = "14" then%> Case14. PCU output is more than 14 volts DC

Possible Causes and Solutions:
1. Reason :- PCU over calibrated.
  Action :- Replace the PCU.
<% elseif Request("index") = "15" then%> Case15. The ST8000 Proxstation does not power up.

Possible Causes and Solutions:
1. Reason :- Proxstation reader fuse has blown.
  Action :- Check the 1 ampere fuse on the ST8000 PCU on the ST-BC3 I/O logic PCB and replace if necessary.
2. Reason :- 8 core screened wire termination to the PCU is wrong.
  Action :- Confirm termination.
3. Reason :- Proxstation unit is faulty.
  Action :- Replace the Proxstation unit.
<% elseif Request("index") = "16" then%> Case16. The Proxstation powers up but there is no display.

Possible Causes and Solutions:
1. Reason :- LCD contrast not calibrated
  Action :- Using a philips screwdriver turn the contrast trimpot clockwise until LCD characters appear on the screen.
<% elseif Request("index") = "17" then%> Case17. The proxstation powers up but does not run - 'time out' LED on and 'load' LED is off

Possible Causes and Solutions:
1. Reason :- 8 core screened wire termination to the PCU is wrong
  Action :- Confirm termination
2. Reason :- Wrong firmware, or firmware chip is not secure.
  Action :- Check that the firmware chip is secure and in the right place as well as the firmware is correct.
3. Reason :- RAM chip is not in place or wrongly inserted.
  Action :- Check that the RAM chip is secure.
4. Reason :- Proxstation is faulty.
  Action :- Replace the Proxstation.
<% elseif Request("index") = "18" then%> Case18. Transmit LED does not blink but receive LED blinks.

Possible Causes and Solutions:
1. Reason :- Proxstation unit may not be setup in the ST8000 application software.
  Action :- Check that the proxstation is setup.
2. Reason :- Proxstation address may be wrong.
  Action :- Check the Proxstation address setting.
3. Reason :- Transmit LED is faulty.
  Action :- Replace the Proxstation unit.
<% elseif Request("index") = "19" then%> Case19. Transmit and receive LED's do not blink or either one not working but ST8000 application detects the Proxstation

Possible Causes and Solutions:
1. Reason :- Proxstation is faulty.
  Action :- Replace the Proxstation.
Note: If this is the problem, then other indicators like the LDC and keypad back light will also not work.
<% elseif Request("index") = "20" then%> Case20. Buzzer does not work or sound level inconsistent.

Possible Causes and Solutions:
1. Reason :- Proxstation is faulty
  Action :- Replace the Proxstation.
<% elseif Request("index") = "21" then%> Case21. Some address settings cannot be used or detected by the ST8000 application.

Possible Causes and Solutions:
1. Reason :- Proxstation is faulty
  Action :- Replace the Proxstation.
<% elseif Request("index") = "22" then%> Case22. After a complete download of data, valid cards still do not work - no data retention.

Possible Causes and Solutions:
1. Reason :- RAM 3.6 volt battery may be broken or loose.
  Action :- Replace the Proxstation.
2. Reason :- RAM chip may be faulty.
  Action :- Replace the RAM chip or the Proxstation.
<% elseif Request("index") = "23" then%> Case23. Tamper switch does not work.

Possible Causes and Solutions:
1. Reason :- Tamper switch for the proxstation not enabled in the ST8000 application.
  Action :- Check the tamper switch settings in the ST8000 application.
2. Reason :- The tamper switch is faulty.
  Action :- Replace the Proxstation.
<% elseif Request("index") = "24" then%> Case24. Cards cannot be read.

Possible Causes and Solutions:
1. Reason :- Card may be faulty.
  Action :- Replace or try with another card.
2. Reason :- Proxstation is faulty.
  Action :- Replace the Proxstation.
<% elseif Request("index") = "25" then%> Case25. Card cannot be read by the ST-PR100

Possible Causes and Solutions:
1. Reason :- Card may be faulty.
  Action :- Replace or try with another card.
2. Reason :- Connections may be wrong.
  Action :- Check the connections into the Proxstation.
3. Reason :- ST-PR100 unit may be faulty.
  Action :- Replace the unit.
4. Reason :- The Proxstation unit connected to the ST-PR100 unit may be faulty.
  Action :- Replace the Proxstation.
<% elseif Request("index") = "26" then%> Case26. Buzzer does not work or sound level inconsistent.

Possible Causes and Solutions:
1. Reason :- Connections may be wrong.
  Action :- Check the connections into the Proxstation.
2. Reason :- ST-PR100 unit is faulty.
  Action :- Replace then unit.
<% elseif Request("index") = "27" then%> Case27. PCI does not power up (ver.1 and ver.3).

Possible Causes and Solutions:
1. Reason :- PCI power source is not correct.
  Action :- Check the power supply so that it is 12 volts DC.
2. Reason :- PCI is faulty.
  Action :- Replace the PCI.
<% elseif Request("index") = "28" then%> Case28. 'DTR' LED does not turn on (ver.3).

Possible Causes and Solutions:
1. Reason :- PCI is not plugged into PC communications port.
  Action :- Check that it is inserted.
<% elseif Request("index") = "29" then%> Case29. LED's, 'Tx' and 'Rx' do not work or only the 'Tx' is working (ver.3).

Possible Causes and Solutions:
1. Reason :- Communications port assignment in the ST8000 application is incorrect or the PCI is connected to the wrong communications port.
  Action :- Check application for settings, check that the PCI is plugged to the right communications port.
2. Reason :- Jumper setting, 4-wire is inserted.
  Action :- Remove the shunt.
3. Reason :- PCI is faulty.
  Action :- Replace the PCI.
<% elseif Request("index") = "30" then%> Case30. No communications detected (ver.1)

Possible Causes and Solutions:
1. Reason :- Jumper settings not correct.
  Action :- Check that the jumpers are inserted correctly.
2. Reason :- PCI is faulty
  Action :- Replace the PCI.
<% elseif Request("index") = "31" then%> Case31. No communications and power supply when lightning/surge card is inserted into the communications bus.

Possible Causes and Solutions:
1. Reason :- Wire connections may be wrong,
  Action :- Check that the wire connections, V+,V- and C+, C- are correct. Only use the V+,V- for power supply and the C+, C- for communications.
2. Reason :- Lightning/surge card is faulty.
  Action :- Replace the unit.
<% end if %> <% end if %>



 

 

Copyright 1993-2002 Sierra Technology (M) Sdn Bhd. All Rights Reserved. Last Update: 23/07/2002