Program Memory Failed. Return CPU for
RAM Battery Failed. T1: Parameter file
or Both: Master Reset performed.
For either processor, parameters are reset to factoy defaults. In other respects, operation will be normal.
If you rely on soft calibrations, you should review them after getting this error.
For the 001 processor, if this error recurrs, return
processor for maintainance when convenient.
Keyboard Command. If you are doing
Keyboard operations, this error could mean what it says. You may
also get it once when you plug or unplug something from the Ockam bus.
However if you get this error all the time, it means that the
bus Cable (the coax and Tees) has deteriorated. The
coax may be
intermittently shorted, or has water in it.
Evaluation Stack. This is a programming
error. Notify Ockam.
output buffer full. Too much output for
the display channel. Disable unused outputs (see Disabling Tags).
buffer overflow. Too many commands.
Either a PC is outputting
to the system at too high a rate, or the RS232 interface plug is in the
or more tags are disabled. See Disabling Tags.
falling behind. Calculation loop
full. Disable unused outputs (see Disabling Tags).
Interface response. An interface is not
communicating correctly. If this error persists, contact Ockam.
Interface has dropped out. The
Boatspeed interface used to
be there, but is not anymore. All functions involving
true wind, logs, DR etc) will stop. Check Ockam Bus and transducer
Interface Error. The A/D chip in the
interface is not working correctly. Return the Interface for service.
sensor input with Transducer Switch set to 1. The
interface is receiving signals from the starboard transducer
connector with the selector switch set to one
transducer. Possible causes of this error are:
- You are using only one transducer, but it is
connected to the starboard transducer connector.
Re-connect the transducer to the port connector.
- You have two transducers connected, but the
selector switch is set to 1 transducer. You should set the selector to
2 transducers (to the right).
- You are missing the masthead interface which is
needed to select between the two boatspeed transducers. See
error 24 below.
boatspeed transducers without heel. In order to use two
boatspeed transducers, the system needs a heel input, which is a part
of the masthead or 3D compass interfaces. If you have
no heel input, you can only have one transducer. It should be connected
to the port transducer connector, and the selector should be set to 1
transducer (to the left).
between Port & Starboard Boatspeed Excessive.
On two transducer installations, the boatspeed reading of the
two transducers differ from each other by an excessive amount.
This error can be caused by:
- The windward transducer coming out of the
water. This situation is fairly common in windy
conditions, and can cause the windward transducer to read
either low, or high, depending on what the wave tips are doing
to the impellor. There is no fix for this condition.
- A fouled impellor on one of the transducers.
The boat speed on one tack should be low or zero. On the tack with low
boatspeed, the lee transducer is the one needing cleaning.
- A damaged cable from one of the transducers.
Detect which one by the same procedure as (2) and repair it.
& Wind Interface Revisions Incompatible. On older
systems, the leeway calibration was on the wind interface
instead of the boatspeed. If you have a combination of new and old
interfaces in the same system, you will have either two or zero
Leeway calibrations. If you have two Leeway
calibrations, the system will use the one on the BOATSPEED. If you have
none, the trimmer just above the Upwash cal on the MASTHEAD will be
used for Leeway.
SOG for boatspeed. See Option 16.
Interface has dropped out. The wind interface used to be
there, but is not anymore. All functions involving wind and heel
(boatspeed tack-to-tack calibration, VMG, True Wind, Laylines etc) will
stop. On dual boatspeed transducer installations,
this trouble will also cause error 24.
Interface Error. The A/D chip in the interface is not
working correctly. Return the Interface for service.
angle signals. The signals from the masthead angle sensor
to the interface do not fall within acceptable tolerance. If the mast
cable is damaged, these signal lines could be shorted together
or shorted to the mast, causing this error. If the cable is damaged, it
could cause possible damage to the masthead.
Compare the Windangle Apparent display against the wind vane. If they
compare well, then these errors can be ignored. Otherwise, the mast
cable or masthead should be checked.
of Heel and Wind Angle do not agree. The CPU has checked
heel angle during a beam-reach condition and found that the heel angle
is backwards. Change the heel sense switch on the Wind interface.
Rotation error. The Mast Rotation Interface reports an
error. Refer to the trouble light inside the interface for a more
detailed description of the problem.
rotation missing. The mast rotation interface has dropped
out. Wind information will no longer correct for mast rotation.
masthead with no heel. Sonic masthead interface without
heel sensor requires 3D heading interface.
Interface has dropped out. The Compass interface
used to be there, but is not anymore. Functions involving
heading (DR, laylines) will stop.
Interface Error. The Interface is not getting a signal
from the sensor. HEADING display will show a 0 or non-changing value.
Check that power is turned on to the sensor (if applicable), and check
the wiring between the sensor and the interface. Some sensors send data
at less than a 1/4 second rate, so this error may be "normal" for them.
sensor in CALIBRATION mode. While the heading sensor is
calibrating, the Heading output is the “quality of
||(T1 only) Getting
direct NMEA heading with Heading interface attached. The
T1 processor is receiving heading input on its NMEA port, and a Heading
interface is also providing heading. The direct input is being ignored.
COG for heading+leeway. See Option 16.
Interface has dropped out. The Depth interface
used to be there, but is not anymore.
Interface Error. The Interface is not getting a signal
from the depth sounder. DEPTH displays will show non-changing values.
Check that power is turned on to the depth sounder, and check the
wiring between the sounder and the interface.
||(T1 only) Direct
depth – No Depth Keel. Older revisions of the T1
have no transducer or keel depth adjustments. Depth Sufrace displays
the number being received, and there is no Depth Keel.
Upgrade to the latest T1 software.
||(T1 only) Getting
direct NMEA depth with Depth interface attached. The T1
processor is receiving depth input on its NMEA port, and a depth
interface is also providing depth. The direct input is being ignored.
||(001 only) Polar
Module has dropped out. The Polar Module used to be there,
but is not anymore.
||(001 only) Polar Module reports trouble.
The requested polar ROM has bad header data.
||(001 only) Polar
Number is Missing. The polar number (switch or Option 3) is
set to a polar number which can not be found in any polar ROMs in the
Module. If you do not have multiple polars, the polar number will
normally have been set to 1. Reset the Polar number switch to 1, and do
a Master Reset.
||GPS Interface has dropped out. Functions
involving waypoints (waypoint, laylines and current) will gradually
degrade due to accumulation of errors by dead-reckoning.
||GPS Interface reports trouble. The
not receiving properly. Either the GPS is off, the cabling is
messed up, or the baud rate or type switches on the interface are
||(T1, 001>A15) No Waypoint from GPS. The
GPS is not
outputting Waypoint Range & Bearing. Some GPS’s do
waypoint range & bearing unless they are executing a route.
(001<A16) Waypoint moved more than 1/2 mile. This is
not an error. You will see this reported when the Loran
destination is changed from one waypoint to the next.
||(T1, 001>A15) No Current. Current is out
of date because COG/SOG is not being received AND no manual current has
(001<A16) Loran Failed to Update for more than 2 Minutes. The
has failed to communicate with the interface for more than 2 minutes.
In some Lorans, you may have to instruct the Loran to output data
to the output port for the interface to use. This instruction may
have to be reissued to the Loran. Communications trouble like
error 72 may also cause this error.
||(T1, 001>A15) No Lat/Lon. GPS is not
(001<A16) Loran Automatic Current Calculation is Disabled. This
error is a reminder, not an indication that something is wrong.
Automatic current calculation (CURRENT SET & DRIFT) has been
disabled by setting Option 4 to 0.
||(T1, 001>A15) No COG/SOG. GPS is not
(001<A16) Range & Bearing Frozen. The Loran
position has not changed within the last minute. This may
indicate that the Loran has lost track, or that the waypoint range
is too far away for adequate resolution of its position (in
bearing), or there is no progress toward the waypoint (no
boatspeed). Thus, this error will occur if the boat is stopped.
The waypoint is maintained by DR (for those systems with
boatspeed and compass) until the Loran changes its range and
bearing output. The difference between this error and error
74 is that this one reports on the values as opposed to physical
||(T1, 001>A15) Current is Manual. Current
has been manually input (see Manual Current).
(001<A16) Waypoint Update Disabled. This is not an error. It is
reminder that the input from the Loran has been disabled (see Options), and the Ockam Waypoint is being updated
by Dead Reckoning only.
||(T1, 001>A15) Manual Waypoint. Waypoint
Bearing is being input manually, overriding data from the GPS (see
||(T1, 001>A15) No Differential GPS. The GPS
is signaling that differential correction has been lost.
||(T1, 001>A15) GPS error. The GPS is
signaling an error.
||Rudder Interface has dropped out. The Rudder
interface used to be there, but is not anymore.
||Rudder Interface Error. The A/D chip in the
interface is not working correctly. Return the interface for service.
||Temperature Interface has dropped out. The
Temperature Interface used to be there, but is not anymore.
||Temperature Interface reports trouble. The A/D
the interface is not working correctly. Return the Interface for
||A Q Interface has dropped out. One of the Q
interfaces (e.g. Loadcell) used to be there, but is not anymore.
||Q Interface Slot error. Two Q interfaces are
set to the same slot.
||Bad characters from Q interface. One of the
Q interfaces has sent bad characters.
||Bad Initialization from Q Interface. One of
the Q interfaces has a bad header. The interface will not be recognized.
||No room in Buffer Pool for Q Interface.
no more room in the buffer for more Q interfaces. This is caused by
having more Q interfaces than the system can handle. The
system allocates space for interfaces as it encounters them, and
never deallocates it. Therefore, if you turn the slot switch on an
interface, you will allocate buffers for interfaces you do not have.
Try turning the power off and back on.
||(T1 only) Correction tables disabled. See Option 31.
||(T1 only) Autocal tables disabled. See Option 31.
||(T1 only) Sensor correction table was loaded for Wind angle apparent. See SensorCorrection.PDF.
||(T1 only) Sensor correction table was loaded for Windspeed apparent
||(T1 only) Sensor correction table was loaded for Boatspeed
||(T1 only) Sensor correction table was loaded for Heading
||(T1 only) No AutoCal. An AutoCal control command
has been received for a missing or disabled AutoCal table.
||(T1 only) Default Settings Saved. A SAVE DEFAULT
command was executed successfully.
||(T1 only) Load Polar Requested. A polar file
change has been requested. If unsuccessful, error 117 will be posted.
||(T1 only) Load Polar Failed. The Load Polar
||(T1 only) The RS232 port has changed its
settings. See T1 Command Port.
||(T1 only) The startup commands file "commands.txt" was executed.
||(T1 only) Changes Saved. When the T1 saves its
settings to the flash card, it throws this advisory.
||(T1 only) NMEA port not 4800. The T1 NMEA port is
outputting at 9600 baud.
||(T1 only) ZDA disabled. The T1 clock is not being
updated from ZDA (see Option 21).
||(T1 only) Retro-apparent is enabled. Apparent
wind is being back-calculated from true (see Option 21).
||(T1 only) Sonic wind interface error. Message
sent by the sonic masthead interface.
||(T1 AHRS build only) AHRS missing.
||(T1 AHRS build only) AHRS bad data.
||(T1 AHRS build only) AHRS calibration error.
||(T1 only) Error reading CF card.
||(T1 only) Error writing CF card.
||(T1 only) Error during Fcommand parsing. See Fcommand.PDF for details.
||(T1 only) AutoCommand file loaded.
||(T1 only) AutoCommand issued.
||(T1 only) No Lynx file. Issued when a metaLynx interface is attached and there is no definition file for it.
||(T1 only) Failed to create log file. Insufficient
system resources available to create and open the log file.
||(T1 only) Log file shut down. Free space on the
compact flash fell below 2MB. Logging has been terminated.
||(T1 only) Logging disabled. Logging requires a
compact flash size greater than 20 MB.
||(T1 only) Logging write error. There was an error
writing the current data block.
||(T1 only) Logging updated. The log was
||(T1 only) Next logging file opened. The previous
file was closed and the next in sequence has been opened.
||(T1 only) Apparent wind speed AutoCal table active.
||(T1 only) Upwash AutoCal table active.
||(T1 only) Leeway AutoCal table active.
||(T1 only) Boatspeed AutoCal table active.
||(T1 only) True wind angle AutoCal table active.
||(T1 only) True wind speed AutoCal table active.
||(T1 only) Apparent angle AutoCal table active.
||(T1 only) GPS port is running at other than 4800 baud (see Status1 function GB)
||(T1 only) NMEA port is running at other than 4800 baud (see Status1 function NE)
||(T1 only) Stats function - Not enough data. See stats.html for details on this group of errors.
||(T1 only) Stats function - Bad conditions e.g. Boatspeed=0
||(T1 only) Stats function - No tacks. Most statistics require some tacking/gybing to generate their outputs.
||(T1 only) Low buffer pool. Report this error to
|(T1 only) Full mailbox. There is too much
being generated as input to one of the processing queues. Error 309
indicates that the GPS is producing so much output that the NMEA tap
channel is overflowing. If this error occurs, cut down on the GPS
output via its setup function.
|(T1 only) Low stack alarm. One of the tasks is
reporting a stack overflow error. Report this error to Ockam.