Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

 Power Center Communication Troubleshooting 

Configuration for the Holykell fuel sensor is done through the services tab at the top left section of the Power Center. 

...

No communication  

...

The fuel sensor is receiving power, but the unit is not connected to Elara or K2 

...

Connect your serial converter to the ports for RS 485 B and pin 4 for RS485 A 

...

Read all configurations communication protocol  should be set at  

Device ID :15 

Baudrate :19200 

...

 

...

Open the Holykell configuration Tab Set Baudrate at 19200 

...

Id Scan the fuel sensor and if it lands on a different ID from 15. Click on next Icon and set the default ID and Baudrate as 15 and 19200 respectively.  

If no communication is present 

...

 

...

Open the Holykell configuration Tab Set Baudrate at 9600 

...

Id Scan the fuel sensor and if it lands on a different ID from 15. Click on next icon and set the default ID and Baudrate as 15 and 19200 respectively.  

 

...

 

...

The device is communicating but giving the wrong data 

The Fuel sensor should be taken out of the fuel tank and held straight on a flat surface. 

...

No Communication 

...

When the Fuel sensor is connected to the communication Terminal block, it does not communicate with the Elara unit 

...

  1. Check the cables have continuity at both ends. 

  2. Make sure the power supply is 12 volts. 

  3. Check termination of the RS485 communication is properly done. 

 

Table of Contents
minLevel1
maxLevel1
outlinefalse
typelist
printablefalse

Power Troubleshooting

What is the fault and how can it be detected?

Troubleshooting Steps









Despite being connected to a power source,
the fuel sensor does not receive any power

The issue will be identified during the check that the technician should perform with the electronic test tool (FLUKE).

  1. Ensure that the incoming wires from the power source are properly secured at both ends. A power source can be an external source or a Galooli internal connection, such as an Elara cabinet tray/Elara metal box.

    Image Added

  2. Ensure that the power supply is between 10 and 30 volts DC.

 


Hardware Connectivity Troubleshooting

What is the fault and how can it be detected?

Troubleshooting Steps

 When the fuel sensor is connected to the communication terminal block but is unable to communicate with the Elara device 

Image Added
  • Connect the fuel sensor cables to the terminal block properly.

  • Ensure that the terminal block's power supply is 12 volts. 

  • The RS485 connection cables should be connected according to the pinout diagram:

    • On the fuel sensor side

      Image Added
    • On the terminal block side - refer to the wiring diagram provided by Galooli



Power Center Troubleshooting

...

  1. Verify that the Network APN is correct.

  2. Verify that the server URL is correct.

    Image Removed
  3. Check with the technical support team that the SIM card has been activated.

  4. If you are using a local SIM card, ensure it is an internet-ready SIM card. Subscribe to an active data package or insert an internet-ready SIM card.

  5. Make sure the SIM card you are using is active and country-profiled if you are using a roaming SIM card. Contact the service provider for more information.

  6. Confirm that the server URL/IP address is whitelisted for the SIM if there are restrictions for RMS SIMs in your country. Consult your local

SIM provider for more information.

...

 

 

 

 

  1. Confirm the modem is properly connected. If not unscrew the modem connector and properly screw it back in a clockwise direction.

  2. Reposition the modem, and try multiple locations to improve the network reception. Also, ensure crosslink foam is intact

  3. If you are using a local SIM card, confirm there is an internet-ready SIM card present.

...

  1. Ensure the GPS time stamp is accurate, if it is not, proceed to the next step

  2. Enhance the connection between the Elara and the antenna

    Image Removed

...

ELARA Unit Not Upgrading

...

  1. Confirm that the Configuration files in the SD card are in the proper order (Expected Files: ELARA.GIB and a folder called "VERSIONS" containing the ELARA.BIN file only). It is recommended to delete all existing files & recopy new Elara files to the SD card

https://galooli.atlassian.net/l/cp/2wYS19PJ

...

 

 

At least one of the MODBUS devices is connected, but others are disconnected

...

  1. Confirm the Elara is on the latest version, if not, upgrade the Elara Unit

  2. Confirm the ID and Baudrate configured on the device are correct and match the ID and baud rate assigned on the power center. if not log in to the device and configure the correct ID and baud rate

  3. If the device uses different physical and virtual IDs, confirm both IDs are correctly configured. Refer to respective device documentation on the knowledge portal

  4. If there are multiple hardware or software versions of the same device, confirm the right one is selected on the power center. Check the device tag or log in to the physical device to confirm the versions

  5. Confirm the Device power and communication cable are properly terminated, Rewire the device according to specifications. Refer to respective device documentation on the knowledge portal

  6. Confirm Device is configured on the Port-1 Device section. Reconfigure the device as a Port-1 device

...

Confirm the RS485 connection between the terminal block and the Elara RS485 green connector. Check continuity between the RS485 terminal blocks and Elara RS485 Port-1 pins (Do same for A & B).

  1. Check the

“Server URL”, and “Network APN” and the modes in both Port 1+2 (Port 1 must be the host and Port 2 binary).

...

ZonMax Troubleshooting

 

...

How to Detect the Fault?

...

Troubleshooting Steps

...

Elara Configuration is OK on the Power center, all LEDs are green, but not reporting on ZON

...

  1. Confirm the Unit ID on the Power Center matches the Unit ID on the Elara labels. If not, replace the Elara and sent the Elara with the wrong ID for reconfiguration of the ID

  2. If the Elara is installed the same day, you may use the clear Internal log button on the power center. Note that data stored locally in the unit will be lost.

    Image Removed

    3. Make sure that the time stamp is accurate. Otherwise, follow the troubleshooting steps for the wrong timestamp

...

 

...

  1. Ensure that the two cables connected to the sensor in the Tray/Metal Box are secured on both sides.

    Image Removed

 

 

...

What is the fault and how can it be detected?

Troubleshooting Steps






Despite receiving power and being properly connected, the Galooli gateways in Power Center are not connected to the fuel sensor

Image Added
  1. Ensure that the fuel sensor ID is configured with the correct baud rate of 19200 and the device ID by the wiring diagram.

    Image Added
  2. Be sure to select the correct fuel sensor parameters when adding the fuel sensor to the Elara gateway, including: "Device", "ID", and "Device Baudrate” according to the wiring diagram provided by Galooli.

    Image Added



Fuel sensors are communicating properly, but the data they provide is incorrect.

Image Added
  1. Remove the fuel sensor from the fuel tank and place it straight on a flat surface. Ensure the tip of the fuel sensor is

2cm
  1. 2 cm away from the base of the

fuel’s
  1. fuel's sensor securing

rod 
  1. rod.

  2. Read all configurations from the

Holykell
  1. fuel sensor calibration tab on the

Services center. 
  1. “Services center”.

    Image Added
  2. Once done perform the

Zero calibration
  1. “Zero calibration” on the fuel sensor

 

איזה סנסור?

 

Power Troubleshooting

 

...

How to Detect the Fault?

...

Troubleshooting Steps

...

No Power 

When the Fuel sensor is connected to the power source, it does not receive any power 

...

  1. Check that incoming wires from the Power source are properly secured both at the connector harness and at the Galooli DB. 

  2. Check if the cables have continuity at both ends. 

  3. Make sure the power supply is 12 volts DC. 

 

 

 

Connectivity

...

How to Detect the Fault?

...

Troubleshooting Steps

...

 

 

Make sure that the SD card is properly inserted. Push the SD card to release and push it again to lock. if not still working, replace the SD card.
https://galooli.atlassian.net/l/cp/SVsrK0vf

...

 

The status 2 LED is blinking slowly red
or
Red error in the Power Center

...

 

 

 

The SD card should be written with the correct files. Always recommended to delete all existing files & recopy new Elara files to the SD card.
https://galooli.atlassian.net/l/cp/2wYS19PJ  

...

 


  1. Image Added

Fuel Readings Troubleshooting

What is the fault and how can it be detected?

Troubleshooting Steps











The fuel reading is stuck

Several platforms can be used to identify the problem:

  • Pro application detailed report.

  • Power Center.

  • Galooli Mobile App.

In order to confirm that the fuel reading is indeed stuck, follow these steps:

  1. Find a day when the generator was certainly in use. Generate a detailed report on that day using the Pro application, containing two fields: "Generator X Total used" and "Generator_X.Engine_Hours". In the event that the working hours of the generator change and the fuel consumption does not change accordingly, then the reading is indeed stuck and you should proceed to the next step.

  2. Using one of the Galooli platforms, create a detailed report and determine when the fuel reading last changed . If you have determined the time and date at which the readings of the fuel stopped, proceed to the next step.

  3. Check whether the fuel calibration table has been modified in accordance with the previous section and make sure that a calibration table has been applied properly.

  4. Check via the Power Center if the sensor's open-air value exceeds the OA value of +7 or -7, it may indicate a fault.

  5. Verify that the fuel sensor pores are not blocked at the diaphragm.

  6. Make sure that there is no sludge in the fuel tank.

  7. Make sure the fuel is of good quality.

  8. Make sure that the fuel sensor is properly secured to the sensor securing rod.

  9. Check for signs of wear and tear.

  10. Recalibrate the sensor.






The fuel readings indicate a wave pattern

Use the detailed report provided by the Pro application to identify the issue.

  1. Create a detailed report using Galooli Pro application in order to determine when the fuel readings begin to behave in a wave pattern. Proceed to the next step if you have determined the time and date.

  2. Check whether the fuel calibration table has been modified in accordance with the previous section and make sure that a calibration table has been applied properly.

  3. Check via the Power Center if the sensor's open-air value exceeds the OA value of +7 or -7, it may indicate a fault.

  4. Verify that the fuel sensor pores are not blocked at the diaphragm.

  5. Make sure that there is no sludge in the fuel tank.

  6. Make sure the fuel is of good quality.

  7. Make sure that the fuel sensor is properly secured to the sensor securing rod.

  8. Check for signs of wear and tear.

  9. Recalibrate the sensor.

The fuel readings contain “noise”

An example of noise would be a deviation from how the Galooli system interprets the fuel trend from a particular site.
The following factors may be contributing to this noise, either individually or in combination:

  • The presence of sludge in the tank

  • A large amount of water has been mixed with the fuel in the tank.

  • Fuel sensor malfunction

  • An improperly installed fuel sensor in which the rod of the sensor is not firmly fastened to prevent vibration.

Image Added

First you need to identify the noise readings:

Step 1: Build a summary report with the following fields:

•unit id
•Refuels
•Numeric Calculated field"(IF(('Refuels'>8)||('Drops'>8);1;0).
The assumption is that a norml functioning sensor should not experience refuel or drop count of more than 8 in a day.
The count can vary depending on the client and their mode of operation.

Step 2: Under data Aggregation use "Daily"

Step 3: Run the report and under Calculated field (Named "1 equals irregular fuel")

Step 4: Filter out 1, this represents the sensors with irregular fuel/noise.

How to resolve noise issues?

Resolution approach depends on the cause of the noise. To know the exact cause of the noise, a site visit for physical inspection is recommended. Below, a list of action for different root cause is highlighted.

Presence of sludge in the tank

  1. Evacuate sludge from the tank.

  2. Clean the fuel sensor by removing sludge deposits from the diaphragm.

  3. Wash the sensor with fuel but be careful to ensure fuel does not penetrate the cable or internal circuitry of the sensor.

  4. Power up the sensor and observe for normal functionality. If sensor reading is OK, then sensor can be re-used otherwise a replacement is advised.

  5. Re-install the sensor and calibrate as per standard operating procedure.


Presence of water in the tank

  1. Evacuate fuel contaminated with water from the tank.

  2. Inspect the sensor to be sure there is no water ingress in the cable or sensor internal circuitry.

  3. Wash the sensor with fuel but be careful to ensure fuel does not penetrate the cable or internal circuitry of the sensor.

  4. Power up the sensor and observe for normal functionality. If sensor reading is OK, then sensor can be re-used otherwise a replacement is advised.

  5. Re-install the sensor and calibrate as per standard operating procedure.

  6. Identify potential points of water ingress to the tank and seal it off.

Faulty fuel sensor

Once confirmed faulty, replacement is recommended.

Installation issue (Lack of rigidity)
When identified as the cause of the noise, re-install the sensor, and make sure the sensor rod is securely fastened to the tank to prevent excess vibration when generator is running.