When one tank stops showing a valid level while the rest of a SAAB TankRadar STaR installation continues operating, the fault should be assessed at channel level before assuming that the complete system has failed.
A controlled restart of the Tank Gauge Electronics, or TGE, can be useful in certain circumstances. However, a reading that returns after a restart is evidence of recovery—not, by itself, proof that the underlying problem has been resolved.
Identify the status before restarting
Record the exact status shown for the affected tank. Several indications can appear similar to an operator, but they describe different conditions.
CFAIL indicates a communication failure on the link used to collect the measurement. ERROR can indicate a measurement problem, such as a missing echo or an out-of-range value. Booting identifies a TGE that is restarting.
The legacy documentation also distinguishes a TGE that is offline or not being polled from one reporting an internal system error. These conditions should not be grouped together as simply “no level.”
Where a last valid value remains visible, confirm its status before treating it as a current measurement. In the documented legacy interface, a retained value can remain displayed with a fault indication.
What a TGE restart actually does
The STaR service manual describes a TGE restart as resetting the electronics memory and restarting the measurement process. One example given is a gauge that has tracked a false echo.
The manual describes an interruption of approximately ten seconds for the documented equipment. No measurements are performed by the selected TGE function during that interval, and the workstation may temporarily show CFAIL or ERROR.
That timing is a legacy reference, not a guaranteed recovery time for every installed software or hardware revision.
Select the correct tank and function
Applicable STaR arrangements can contain separate electronic boards for level measurement, high-level alarm and overfill alarm functions.
The documented restart function acts on one selected tank and one selected system at a time. In that arrangement, restarting the level function does not restart the separate high-level or overfill boards.
Before any intervention, verify the installed architecture and identify exactly which function will be unavailable. Do not assume that every vessel has the same independent arrangement or that associated protection remains available without checking.
Coordinate the interruption with the responsible vessel personnel and follow the applicable operating procedures.
Check shared faults when communication is lost
A communication failure at one TGE does not automatically identify defective gauge electronics.
The manual’s troubleshooting approach first checks whether the associated communication modem also reports a fault. This helps distinguish an individual gauge problem from a fault affecting shared equipment.
Record whether the problem affects:
- One tank or several tanks.
- Level only, or associated pressure and temperature channels.
- The workstation display only, or the underlying system diagnostics.
- A single occurrence, or repeated interruptions.
These observations help direct further investigation toward the relevant communication, power, field-cable or gauge path. Electrical intervention and component isolation require the correct drawings, procedures and competent personnel.
Verify recovery after the reading returns
After a controlled restart, confirm more than the presence of a number on the screen.
Check that the selected function returns to its expected operating status and that the displayed measurement updates. Assess whether the value is plausible for the tank’s current condition and observe whether the original fault returns.
Review associated channels separately. A restored level indication does not establish that pressure, temperature or independent alarm functions have also been verified.
Confirm that temporary test states or interventions have been cleared. In the legacy documentation, a channel marked DISCO can continue presenting values while its alarm handling is inactive. A visible reading alone is therefore insufficient evidence of full operational readiness.
When repeated restarting is not enough
Repeated recovery followed by another failure should prompt further diagnosis.
Persistent Booting, recurring CFAIL, unstable readings, configuration warnings or antenna-contamination indications each require their own assessment. Repeated restarts can also make it harder to preserve useful as-found evidence.
Capture the status history and operating conditions before another intervention. Component replacement should follow an identified fault and compatibility review.
What the service report should record
A useful report includes:
- Affected tank and selected system function.
- Original alarm text and diagnostic status.
- Condition of other tanks and related channels.
- Hardware and software identification where available.
- Authorized action and measurement-interruption period.
- Status and reading after recovery.
- Observation period and any recurrence.
- Outstanding defects and recommended follow-up.
Distinguish clearly between measurement restored, function verified and root cause confirmed. Each describes a different level of evidence.
For related guidance, read our SAAB TankRadar troubleshooting guide, ullage comparison article and high-level and overfill alarm testing guide.
Legacy documentation and service support
This article draws on the November 2005 sixth-edition SAAB TankRadar STaR service manual. Installed hardware, software, network arrangements and later modifications may differ. Use the vessel-specific documentation and applicable procedures before carrying out service work.
For technical assessment, send the alarm screenshots, affected tank, equipment identification, fault history and vessel schedule to info@reformmarine.com.
Reform Marine is an independent marine service company. Manufacturer and product names identify installed equipment and do not imply OEM authorization.