 |
This guide will help you troubleshoot set-up and operational problems for the following tracking product:
Click on the tracker product in the table to enter its troubleshooting page
Tracker Product |
Tracker Technology |
| Flock of Birds |
DC Magnetic |
| laserBIRD |
Scanning laser |
| miniBIRD (800 and 500) |
DC Magnetic |
| MotionSTAR (Tethered Model) |
DC Magnetic |
| MotionSTAR Wireless |
DC Magnetic |
| pciBIRD |
DC Magnetic |
| ReActor 2 |
Active Optical |
| SpacePad |
AC Magnetic |
Direct contact to Ascension tech support experts:
In addition to the information provided here, you can also reach us directly:
Flock of Birds - Troubleshooting Guide
| Poor accuracy |
Metal in tracking
environment.
Damaged equipment.
Poor connection.
Applications software error.
Finite size error. |
Check all around the transmitter
to the farthest distance from
the center of the transmitter
to the maximum distance the
sensor is used. Move or replace
metal, or reposition Flock
system.
Check for damage.
Sensor or transmitter connector
not properly inserted. Correct
by unplugging and plugging
the components back into the
board.
Verify formulas and scale
factors.
Check relative sensor position.
Does separating the sensors
improve accuracy? Move sensors
farther apart. |
| Noise in data |
Sensor
is close to electrically noisy
device.
Filter off or set too low.
Line frequency value set incorrectly.
|
Turn
off electrically noisy device
or reposition transmitter
to decrease distance from
sensor.
Turn on filters or increase
filter control value.
Determine correct frequency
(50 Hz in Europe, 60 Hz in
North America) and set to
correct value. |
| Front panel LED blinks continuously |
You are in the test mode,
and the system is not actually
functioning. |
Check dipswitch #8. It should
be in the OFF position (pointing
up) for normal system operation. |
| The front panel light does
not come on |
The power cable may appear
to be plugged into the supply
but may be loose. |
Verify that the power supply
cable is plugged into the
power supply and wall.
Disconnect the RS232 interface
cable at the Bird's back panel
and toggle the FLY/STDBY switch.
If the light now comes on,
it means that your RS232 interface
cable has a wire attached
to pin 7 of the Bird's RS232
connector and that your host
computer is holding the Request
to Send line high.
Either disconnect the wire
to pin 7 or reprogram your
RS232 UART to de-assert the
RTS line. |
| Bird does not function or
runs erratically |
Improperly connected cables. |
Make sure that all cables
are screwed into their front and back panel
connectors. |
| Bird will not communicate
with your host computer |
Serial interface may not be
working properly or the baud
rate may not be correct for
your address mode. |
Try using the Bird Output
test and the Bird Echo test
to verify the host serial
link.
Verify that all Birds are
either in the Normal Addressing
mode, Expanded Addressing
mode, or Super-Expanded Addressing
mode by counting the light
blinks on the power-up.
Verify that you are using
the correct baud rate switch
setting for the address mode
being used. |
| Serial communication is not
working in RS232 mode |
Bird may not be sending data. |
Check if pin 4 of the serial
port (Data Terminal Ready) is
being held high. If your computer
brings it low, the Bird will
not send data. If in doubt,
disconnect the pin at the cable
where it connects to the Bird. |
| If you can not communicate
with the Bird... |
Sensor and transmitter may
not be properly connected before
power-up. |
Check that the transmitter
and sensor are plugged into
their panel connectors. The
transmitter and sensor must
be plugged in during power-up. |
| Upon starting your software
to control multiple Birds in
the Flock, the light goes out
or the data output does not
correspond to reality |
Software interrupt problem
between Bird and host application
software. |
Verify that your software
delays for at least 600 milliseconds
before and after sending the
Flock the FBB AUTO-CONFIGURATION,
FBB ARM, or FBB CONFIGURATION
commands. |
| System hangs for no apparent
reason |
You may have sent command
bytes without their proper command
data bytes. |
Toggling the FLY/STDBY switch
should return you to normal
operation. |
| One or more of the position
outputs stops changing at longer
separation distances |
You are attempting to make
measurements beyond the default
range limitation. |
Use the CHANGE VALUE/POSITION
SCALING command to change the
full-scale output from 36 to
72 inches. Your software will
also need to change its output
scaling to correspond to the
Bird's change. |
| The signs of the X, Y or Z
position outputs suddenly change |
You may have crossed a hemisphere
boundary. |
Use the HEMISPHERE command
to fix this problem. |
| Once you have established
proper communication with the
Bird, the tracker hangs |
Unknown. |
Toggle the FLY/STDBY switch
or , if necessary, restart your
host computer. |
| The host computer seems to
be missing data from the Bird |
The host’s operating system
may be removing some bytes from
the Bird’s data stream that
represent host system control
commands. |
Verify that the host can read
all binary characters from the
serial port using the Host Read
Data test and the Host Read
Data Read Block test. |
| The Flock with the Extended
Range Transmitter (ERT) option
is returning fixed position
data and zero orientation data |
A sensor may not be connected
to the tracker. |
Use the RS232 to FBB command
to direct your data request
to a Flock unit with a sensor. |
| You are in standalone mode
and on power-up, the light blinks
twice then goes out. |
You are in the Expanded Addressing
mode. |
Restore the Normal Addressing
mode by following the instructions
in Chapter 6 of the User’s Manual. |
Back
to Top
laserBIRD
- Troubleshooting Guide
|
| No audible sound when Scanner
plugged in |
No Power.
System in SLEEP mode.
System in REST.
|
Check AC connections to
power supply. Check that
d-sub connector is fully
seated. Reset hardware by
cycling AC power.
Check BIRD STATUS for SLEEP
mode; issue RUN command.
Run the laserBIRD utility
and check for status of
the 'reset on CTS' setting.
If enabled and you are running
Windows, either disable
it or ensure that your application
takes control of the COM
port.
|
| Utility doesn't run |
No serial communication.
Software installation unsuccessful.
|
Check the suggestions outlined
in 'Not able to communicate'
below.
Re-initialize the HOST
PC and run the installation
again.
|
| Power-up defaults did not
change after configuring with
the utility |
Configuration
download interrupted.
laserBIRD did not reset (restart)
after burning the Flash settings. |
Restart the
laserBIRD and the utility
and set the defaults again.
Be sure to click APPLY to
send the settings to the Scanner.
Cycle Power to the laserBIRD,
and re-check the settings. |
| Not able to communicate with
the system |
Baud rate
incorrect.
COM port incorrect.
RS232 cable disconnected. |
Default Baud
rate for the laserBIRD is
38,400. Start the laserBIRD
utility using this setting,
and configure the default
for your needs. See Chapter
3 of user's manual for details.
Specify to your HOST PC the
COM port that the tracker
is connected to.
Check that the serial connections
at both ends of the cable
are fully seated. |
| Can communicate with the system,
but data not changing |
Detectors
occluded.
Detectors saturated.
Sensor connection faulty.
|
Use the utility
to check for valid data from
each detector.
Sensor may be too close to
the scanner; increase distance.
Also check for the presence
of high intensity light sources
in the operating region.
Check that sensor connector
is correctly installed and
locked. Inspect coaxial pins
for wear or damage. |
| Data is too noisy (jittery) |
Filters OFF.
DC Filter not optimized.
Reflective surfaces in the
operating region.
Interference from another
laserBIRD.
|
Check FILTER
STATUS for present state of
filter configuration. Enable
AVG and Adaptive filters as
necessary.
Check settings of VM and
Alpha_Min. Adjust until data
acceptable. See command reference
in Chapter 4 for details.
Remove object or surface
causing reflection, or adjust
Scanner mounting to minimize
effect.
If running dual scanners,
check the configuration of
the 'laserBIRD ID' setting.
Configure as detailed in the DUAL SCANNER OPERATION section in Chapter
3 of user's manual.
If configured correctly,
adjust Scanner mounting such
that the 'Performance Motion
Boxes' do not overlap. See DUAL SCANNER OPERATION in Chapter 3 of user's manual. |
laserBIRD
also contains a built-in troubleshooting
utility.
It provides a fast
and easy way to evaluate how each
of the three detectors in your sensor
is performing throughout the operating
region.
For example, if you
were experiencing interruptions
(static or noisy data) during your
tracking application, you can run
the utility and determine which
of the detectors is returning invalid
data. An occluded detector or a
saturated detector most often causes
invalid data. The utility refers
to the three detectors as Sensor
1, Sensor 2, and Sensor 3. Note
that to compute a correct measurement,
laserBIRD must receive valid data
from all three detectors in the
sensor triad.
See your User’s Manual
for further information on using
this utility.
Back
to Top
miniBIRD
(800 & 500) - Troubleshooting
Guide
|
| Front panel lamp
blinks continuously |
You are in the
test mode; tracker is not functioning. |
Check dipswitch #8. It
should be in the OFF position
(up) for normal system operation. |
| Front panel light does not
come on |
The power cable may appear
to be plugged into the supply
but may be loose.
|
Verify that the power supply
cable is plugged into the
power supply and wall.
|
| Front panel light does not
come on |
If the
light comes on after you disconnect
the RS232 interface cable
on the back panel and toggle
the FLY/STANDBY switch then
your RS232 interface cable
has a wire attached to pin
7 of the miniBIRD's RS232
connector. Your host computer
is holding this Request to
Send line high. |
Either disconnect the wire
to pin 7 or reprogram your
RS232 UART to de-assert
the RTS line.
|
| miniBIRD does not function
or runs erratically |
Loose connectors. |
Make sure that all cables
are screwed into their front
and back panel connectors. |
| Cannot get the miniBIRD to
communicate with your computer |
Host serial link may not be
working. |
Try using the BIRD Output
test and the BIRD Echo test
to verify the host serial link.
Verify all Birds are either
in the Normal Address Mode,
Expanded Address Mode or the
Super-Expanded Address Mode
by counting the light blinks
on power up. Verify you are
using the correct baud rate
switch setting for the address
mode being used. |
| The serial communication is
not working in RS232 mode |
Pin 4 of the serial port (data
terminal ready) may be held
low . |
Check to ensure that pin 4
of the serial port (Data Terminal
Ready) is being held high. If
your computer brings it low,
the miniBIRD will not send data.
If in doubt, disconnect the
pin at the cable where it connects
to the miniBIRD. |
| Cannot communicate with the
miniBIRD |
Transmitter and sensor may
not be properly plugged into
their panel connectors. |
The transmitter and sensor
must be plugged in during power-up. |
| Upon starting your software
to control multiple Birds in
the flock, the light goes out
or the data output does not
correspond to reality |
Host software violating Bird
protocol. |
Verify that your software
delays for at least 600 milliseconds
before and after sending the
flock the FBB AUTO-CONFIGURATION
or FBB CONFIGURATION commands. |
| Tracker hangs |
May have sent Command Bytes
without their proper Command
Data bytes. |
Toggling the FLY/STDBY switch
should return you to normal
operation. |
| Position/orientation outputs
from the tracker are noisy (jittery). |
Sensor cable may be picking
up noise from external source. |
Be sure that the sensor is
not located near the miniBIRD's
power supply or other electronic
devices or cables. |
| One or more of the position
outputs stops changing at longer
separation ranges |
Range exceeds factory set
range limit. |
Use the CHANGE VALUE/POSITION
SCALING command to change the
full-scale output from 36 to
72 inches. Your software will
also need to change its output
scaling to correspond to the
miniBIRD change. |
| Signs of the X, Y or Z position
outputs suddenly change |
May have crossed a hemisphere
boundary. |
Use the HEMISPHERE command
to fix. |
| The host computer seems to
be missing data from the miniBIRD |
The host's operating system
may be removing from the miniBIRD's
data stream some bytes that
represent host system control
commands. |
Verify that the host can read
all binary characters from the
serial port using the Host Data
Read test and the Host Data
Read Block test. |
| You want to track in the standalone
mode. On power up the light
blinks then goes out |
Really in Expanded Address
Mode. |
Restore the Normal Address
Mode by following the instructions
in Section 7.8 of your User's
Manual. |
| Front-panel lamp
does not come on (or blink)
when the RS232 cable is disconnected |
The unit is not getting power. |
Apply Power.
Note: there are no fuses
or other user-serviceable
parts inside the miniBIRD's
cabinet. |
Back
to Top
MotionSTAR
(Tethered Model) - Troubleshooting
Guide
|
| Poor accuracy |
Metal in tracking
environment.
Damaged equipment.
Sensor or transmitter connector
not properly inserted.
A software application error. |
Check all
around the transmitter to
the furthest distance from
the center of the transmitter
to the maximum distance the
sensor is used. Move or replace
metal, or reposition system.
Run Environmental
Analyzer to find
good space for tracker use.
Check for damage.
Correct by unplugging and
plugging the components back
into the board.
Verify formulas and scale
factors.
|
| Noise in data |
Sensor is
close to electrically noisy
device.
Filter off or set too low.
Line frequency value set incorrectly.
|
Turn off electrically
noisy device or reposition
transmitter to decrease distance
from sensor.
Turn on filters or increase
filter control value.
Determine correct frequency
(50 Hz in Europe, 60 Hz in
North America) and set to
correct value. |
| Lights blink continuously
and the tracker is not actually
functioning |
You are in the
test mode. |
Check dipswitch
#8. It should be in the OFF
position (pointing up) for normal
system operation. |
| The tracker does not function
or runs erratically |
The system will
not run unless all sensor cables
are plugged in. |
Make sure that
all cables are screwed into
their connectors. |
| The Tracker hangs |
You may be sending
command bytes without their
command data bytes. |
Toggling the
power switch should return you
to normal operation. |
| If the signs of the X, Y or
Z position outputs suddenly
change |
You may have
crossed a hemisphere boundary. |
Use the HEMISPHERE
command to rectify. |
Back
to Top
MotionSTAR
Wireless LITE - Troubleshooting Guide
Backpack
Trouble Shooting:
| None |
No power. Battery could be
completely drained or not connected.
Power switch is off or backpack
timed out and shut itself off. |
| Blinking Red/Orange 2 blinks
per second |
Normal start up. Backpack
has successfully passed Power
On Self Test and is waiting
for download from the Base Station. |
| Blinking Orange 1 blink per
second |
Backpack reset sequence. During
a normal startup, the backpack
resets the internal modem. |
| Blinking Orange 2 blinks per
second |
Backpack download. Info is
being downloaded from the Base
Station into the backpack. The
download to the backpack happens
very fast, so you might miss
seeing this state. |
| Solid Green light |
Backpack data. Backpack is
functioning normally and sending
data to the Base Station. |
| Blinking Green 2 blinks per
second |
Backpack lost its sync. Backpack
cannot detect ERT. Backpack
must be within 18 feet of the
ERT. |
| Slow blinking Red 2 blinks
per second |
POST Failure. Backpack failed
Power On Self Test. |
| Fast blinking Red 5 blinks
per second |
Low battery. Change battery. |
Base Station
Trouble Shooting:
| Running |
Normal Operation. The MotionSTAR
has successfully started and
is receiving data from the backpack. |
| RCV DATA |
Normal Operation. Data is
being sent from the backpack
and being processed by the Base
Station. |
| WAITING FOR BACKPACK |
Base Station is waiting for
the backpack. System has successfully
initialized. Cannot find backpack.
Check backpack (see backpack
Trouble Shooting). Verify Serial
Number displayed matches Serial
Number of backpack. Check both antenna connections.
Modem card should have upper
light green, lower light blinking. |
| Not Present |
The backpack has been found,
but is not currently present.
Check to make sure that the
backpack is turned on. |
| DOWNLOAD |
Backpack download. Backpack
firmware is being downloaded
from the Base Station. |
| Init ERC |
ERC Initialization. The MotionSTAR
is initializing the ERC. |
| Download ERC |
ERC download. ERC firmware
is being downloaded. |
| READ EEPROM |
Read backpack EEPROM. Calibration
data is being read from backpack. |
| Exiting |
A key on the keyboard has
been hit and the program is
‘Exiting’ to DOS. |
| SYNCING |
Backpack syncing. Backpack
is attempting to 'sync' with
the ERT. If the backpack cannot
sync, check the measurement
rate (must be lower than 100
Hz), make sure that the sensors
are not directly on metal or
within 2 feet of the ERT. |
| Check ERC |
ERC error. Unable to initialize
ERC. Check the ERC power and
the RS232 cable. If ERC resets
(audible click) when Base Station
starts, then cabling is OK.
Cycle ERC power (off for 6 seconds).
You should get either 1 blink
(Super-Expanded addressing mode)
or 2 blinks (Expanded addressing
mode). If not, change the addressing
mode. Check dip switch settings.
For Super-Expanded addressing,
all dip switches should be up
except number 1. For Expanded
addressing, dip switches 1,
2, and 7 should be down. Repeated
blinking indicates the ERC detected
an error. Check ERT cabling. |
Check MultiChassis
-or-
Check MultiChassis Port |
MultiChassis Error. Secondary
Base Station has lost communication.
Check RS232 cabling and functionality
of the connected Base Station. |
| Check Antenna |
Communication errors. Data
packets from the backpack are
being lost. Check antenna connection.
Check for RF noise (microwave
oven) in vicinity of MotionSTAR. |
| Check for Metal |
Bad Sync Error. Unable to
cleanly detect ERT waveform.
Check for metal in the environment.
Backpack must be within 18 feet
of the ERT. Check for sensors
close to strong electrical or
magnetic fields (computer monitors,
high voltage electric lines,
etc.). |
| Could not find ERC.FRM |
Missing Firmware. The ERC
firmware file is missing. |
| ERC Download Error |
ERC Error. The MotionSTAR
cannot download the firmware
file to the ERC. Cycle ERC power
(off for 6 seconds). |
| ERC Memory Error |
ERC Error. The ERC does not
have enough memory to accept
the firmware download. |
| ERC PROMs Incorrect |
ERC EPROMs. ERC EPROMs must
be upgraded to be used with
this system. |
| ERC not in super or extended
address mode |
ERC addressing mode. Change
addressing mode to either Expanded
or Super-Expanded. See Section
4.0 of user's manual. |
| XMTR.INI not found |
XMTR Error. There are two
transmitters attached to the
ERC, but the XMTR.EXE program
has not been run. Scaling may
be different than the host computer
expects. Run the XMTR.EXE program
to create the file XMTR.INI. |
| XMTR.INI corrupt |
XMTR Error. The XMTR.INI file
has become damaged. Scaling
may be different than the host
computer expects. Run the XMTR.EXE
program to correct the problem. |
| Init ISA Cards |
ISA Card Initialization. The
MotionSTAR is initializing any
MotionSTAR cards that might
be in the system. |
| Download ISA |
ISA download. The MotionSTAR
card firmware is being downloaded. |
| Could not find ISA.FRM |
Missing Firmware. The MotionSTAR
card firmware file is missing. |
| ISA timeout at XXX |
ISA Card Error. The MotionSTAR
card at Base Address XXX did
not respond. |
| ISA card at xxx - reconfig |
The ISA card at Base Address
XXX is being reconfigured. |
| ISA Memory Error at XXX |
ISA Card Error. The ISA Card
at Base Address XXX does not
have enough memory to accept
the firmware download. |
| ISA Download Error at XXX |
ISA Card Error. Couldn’t download
the firmware data to the MotionSTAR
card. |
| Unable to open WIRELESS.FRM |
Missing firmware. Backpack
firmware file is missing. |
| Invalid RS232 Data |
Data received from RS232 port
is invalid. This often happens
when power is removed from whatever
the RS232 is connected to. |
| RS232 Receive Overrun Error |
RS232 overrun. Data was sent
to the Base Station faster than
it could accept it. |
| Memory Allocation Error OR
Malloc Error |
Memory allocation. Unable
to allocate memory. |
| Timer Board Not Found |
Timer board missing. Reset
timer board. |
| Unable to open XXX.CFG |
Missing Config File. The serial
port configuration file is missing. |
| Unable to open XXX.DRV |
Missing Driver File. The serial
port driver file is missing. |
| Unable to open XXX.FMT |
Missing Format File. The serial
port format file is missing. |
| Config file missing value
for XXX |
The serial port configuration
file is missing a needed value. |
| Illegal value in CFG file
XXX |
The value in the CFG file
in not valid. |
| Illegal format XXX |
The value in the CFG file
is not a valid format. |
Sound Trouble
Shooting Signals:
| 5 note trill |
System running normally. |
| Single note every 3 seconds |
No Connection Active. The
system is running normally but
no interface is active. This
sound stops when either an Ethernet
connection is made or connection
via the MultiChassis RS232 is
detected. If no Ethernet connection
can be made, check the Ethernet
Connection troubleshooting section.
This sound can be disabled in
the file Base.ini. |
| 3 note trill every 5 seconds |
Error message. System was
unable to properly initialize.
If possible, attach a VGA monitor
to the system to view the error
messages. If no monitor is available,
check all the probable causes
listed in the Base Station Trouble
Shooting section. |
Back
to Top
pciBird
- Troubleshooting Guide
|
| The operating
system doesn’t start after installing
the pciBIRD card |
Your card is
not installed properly. |
Turn off power to the
PC, remove the card, reseat
it firmly, and reboot the
system. If problem persists,
turn off power, remove the
card completely, and reboot.
If your operating system starts,
contact Technical Support
for assistance. |
| The pciBIRD
Cubes program does not
start after installation is
completed |
The
power splitter is not plugged
in on the card.
DIP switches on the card are
not correctly positioned.
|
Turn of power
to the PC. Open the cover
and plug in the power splitter
according tot he instructions
under the Installing the
tracking hardware section
of the user's manual.
Consult the Technical Reference
Guide on CD for proper DIP
switch positions, or contact
Technical Support for assistance. |
| The pciBIRD
Cubes program starts, but
data is not changing or sensor
information is missing |
The
sensor is too close to the
transmitter.
The transmitter or sensor
is not completely plugged
in.
Your system is too close
to metal.
The Multi-card SYNC cable
is not attached.
|
Move the sensor
away from the transmitter.
Check connections from the
sensor and transmitter to
the pciBIRD card. Remove and
reconnect if necessary.
Remove metal objects close
to your work area or relocate
the tracker sensor or transmitter.
When using multiple cards,
you must attach the SYNC cable
between the cards. See the Installing the tracking
hardware section of the
user's manual. |
| Poor accuracy |
Metal in tracking environment.
Damaged equipment.
Sensor or transmitter connector
not properly inserted.
Application error.
Sensors are too close together. |
Check all
around the transmitter to
the furthest distance from
the center of the transmitter
to the maximum distance the
sensor is used. Move or replace
metal, or reposition pciBIRD
system.
Check for damage.
Correct by unplugging and
plugging the components back
into the board.
Verify formulas and scale
factors
Check relative sensor position.
Does separating the sensors
improve accuracy? Move sensor
further apart. |
| Noise (jitter)
in data |
Sensor
is close to electrically noisy
device.
Filter off or set too low.
Line frequency value set incorrectly.
|
Turn off electrically
noisy device or reposition
transmitter to decrease distance
from sensor.
Turn on filters or increase
filter control value.
Determine correct frequency
(50 Hz in Europe, 60 Hz in
North America) and set to
correct value. |
| Computer won't
boot while pciBIRD card is in
chassis |
Hardware
failure. |
Contact Ascension
technical support. |
Back to Top
ReActor
2 - Troubleshooting Guide
|
| No LED on the
Suitpack |
On/Off
slider switch not fully set.
Battery problems.
|
Check switch
operation.
Check connections - both at
the battery and at the suitpack.
Re-install the suitpack connection,
ensuring that the connector
is fully inserted before engaging
the lock;
Install spare batteries. |
| FusionCore doesn't
start/run Error: Couldn't access
GivelO device or GivelO must
be loaded |
I/O card in ReActor PC
not seated correctly.
GivelO.sys not running.
|
Check the I/O card (bottom
slot in CPU) and reseat
if necessary.
Run the Inst.bat file in
the ReActor/Sys directory
to load the IO driver.
|
| Error when trying to start
System test: Error: Bar #, Pic# |
Sensor
Bar(s) or modules(s) not responding. |
If several bars listed,
check power supply connections.If
PIC #= all PICs on a single
bar , check data and power
connections to that sensor
bar.If PIC # ¹1, check
data and power connections
between the sensor modules
in that bar.
|
| System test: Sensor bar graph
does not move sequentially across
the bar (jumps) |
Sensor modules
in wrong order. |
Check sequence
of modules. Should always be
1,2,3,4,etc. |
| System test: Can't get a sensor
bar to pass |
Sensor occluded.
Light has not been passed
over all sensors.
No Marker Data.
|
Check for
wires or other misc. objects
covering the sensor slots.
Marker must pass across all
sensors for the bar to pass.
This may be difficult for
3.0 m verticals. NOTE: The
System Test is not a calibration,
and thus the system will operate
properly even if all the bars
to not pass.
See 'No marker data' symptom
below. |
No Marker Data
All zeros reported for each
bar |
Battery problems.
Radio problems.
|
Check battery
connections at AMP connector
and at Suitpack. If properly
connected, replace with charged
battery.
Check antennas, and connections
for both receive and transmit
cables. Note that receiver
cable is directional. If using
429 or 434 MHz version of
radio (wire antennas), make
sure the dip switch settings
are the same on both modules. |
| Markers are linked (rigid
or soft) incorrectly |
Marker link sets
are configured incorrectly. |
Check the Link
assignments, under the Edit
Markers tab in FusionCORE. |
| Data Quality Indicator regularly
turns Yellow. |
Antenna loose.
Radio problems.
Battery weak.
Marker connections loose.
|
Check antenna
connection on radio modules,
and re-tighten if necessary.
Check for LED on radio modules.
Make sure miniDIN connections
are correct (receiver cable
is directional) and fully
inserted. If using 429 or
434 MHz versions of radio
(wire antennas) make sure
dipswitch settings are the
same on both modules. If still
showing yellow, try another
switch configuration (different
channel).
Replace with fully charged
battery pack.
Check all marker connections
at the Suitpack and reseat
as necessary. |
| Some markers are not displayed |
Poor marker
connection.
Marker occluded. |
Check that
plugs at suitpack are fully
seated. Pull out and reseat
as necessary.
Check that marker wires or
other suit objects are not
obstructing the markers. |
| Capture frame rate is much
less than 30 frames/sec |
F-Curves being
displayed resulting in long
draw times. |
Disable the graph
view (under Capture tab) during
a capture sequence, or maximize
the 3D (OpenGL) window by pressing
F6. May also click the 'Maximize
Open GL' icon at the top of
the screen. |
| Marker data seems noisy (jittery) |
Marker partially
occluded.
High frequency lighting in
use. |
Check that
marker wires or other objects
are not obstructing the markers.
Light sources with a high
frequency component should
be avoided during a capture. |
Back
to Top
SpacePad
- Troubleshooting Guide
|
| Cannot talk to
the SpacePad with the ISA interface |
Card may not be properly
seated.
Base address dip switch may
be improperly set.
Jumpers may be set wrong.
|
With the
power off to the host computer,
verify that the SpacePad card
is seated into the host computer's
ISA bus connectors.
Check that the base address
dip switch is set to the correct
value.
Verify that no other cards
in your chassis use base address
+0, +1, +2 or +3. Check that
the IRQ jumpers are set correctly.
There should be no jumpers
if you are using SpacePad
in a polled mode. |
| You can communicate
with SpacePad but the data is
bad |
Cables
may not be properly connected.
You may have made an error
in laying out and constructing
your flat transmitter.
An external noise source may
be corrupting data.
|
Make sure
all cables are plugged into
the correct connectors.
If the angles and or position
have the wrong polarities
or are greatly in error use
the program XMTRTEST.EXE to
analyze if the transmitter
is constructed correctly and
wired correctly into the transmitter
interface card.
If the data is 'noisy' use
the EXAMINE VALUE NOISE STATISTICS
command in conjunction with
the CHANGE VALUE FREQUENCY
command to locate and set
a 'quiet' operating frequency. |
Back to Top
|
