Micro Documentation

10 Troubleshooting

10.1 Strategy

In the case of an issue with the Micro Modular system, an alarm is usually triggered. For more information on how to handle alarms, see section Alarm list. This chapter is a complement to the Alarm list and is used for issues that do not have an alarm connected to them.

  1. Check the troubleshooting table and follow the instructions for suggested actions.
  2. Document your actions.
  3. If any issue still occurs, contact first line support.

10.2 Troubleshooting List

10.2.1 Connectivity

SymptomsCommentsCause and actions
No connection established with LAN cable.Connection to local web interface (Rune) is possible through LAN.

1. Verify that the IP of your laptop is set a static IP address 192.168.20.20.

2. Verify that the laptop network card is enabled.

3. Check that the LEDs next to the Ethernet port flashes. If not, try with another cable or laptop.

10.2.2 Solar

SymptomsCommentsCause and actions
Solar array voltage but no output current is reported on local web interface (Rune)If any solar related alarms are active, the solar converter powers down, resets itself and tries to clear the alarm before starting to convert again. After reconnecting the solar array it can take up to 10 min before the array is detected and starts to produce power.

1. Check for any alarm on local web interface (Rune) and look up them up in the alarm list.

2. Verify that the solar panels and arrays are electrically floating and not connected to ground. The solar stand must be grounded separately.

3. Verify that the polarity is correct and not mixed up with neighbouring solar converters.

No Solar array voltage and no output current is reported on local web interface (Rune).

1. Verify that the polarity is correct.

2. Check if there is array voltage on the input to the converters. Use a multimeter.

Output power from converter is lower than expected.Cloudy weather, shade or dirty panels may cause poor performance.

1. Clean panels if necessary and/or remove objects that shade the panels.

2. Check solar array for damages. Even small damages might have a large impact on performance.

10.2.3 Other

SymptomsCommentsCause and actions
Fuel sensor error.Usually, large fluctuations indicate a broken sensor, bad connection or bad grounding. Some inaccuracy is expected due to uncertainties with tank dimensions, fuel density, fuel sensor etc.

1. Verify that the Fuel Sensor installation is done as instructed in the Fuel Sensor Installation manual.

2. Clean the air hose.

3. Clean the sensor.

4. Check for damages on the cable. Repair or replace if the cable is bent, squeezed or damaged in any other way.

5. Verify that the ground resistance is low.

No synchronization with Illumience.GSM or 3G coverage is required on site. The Micro Modular system continues to operate without synchronization and buffers data until connection is established. Only GSM modules supplied by Clear Blue Technologies are allowed.

1. Check signal strength and possible error codes under the About menu on local web interface (Rune).

2. Restart the modem under the Shutdown / Restart menu in local web interface (Rune).

3. Verify configurations under the Settings in local web interface (Rune).

4. Verify that there is sufficient credit on the SIM card.

5. Test inserting the SIM card in a smartphone to verify that the PIN code is disabled.