...
...
...
No Communication
...
When the Fuel sensor is connected to the communication Terminal block, it does not communicate with the Elara unit
...
Check the cables have continuity at both ends.
Make sure the power supply is 12 volts.
Check termination of the RS485 communication is properly done.
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.
Ensure the tip of the fuel sensor is 2cm from the base of the fuel’s sensor securing rod
Read all configurations from the Holykell fuel sensor calibration tab on the Services center.
Once done perform the Zero calibration on the fuel sensor.
איזה סנסור?
Power Troubleshooting
...
...
How to Detect the Fault? | Troubleshooting Steps |
|---|---|
No Power When the Fuel sensor isDespite being connected tothea power source,it
Check that |
|
Connectivity
|
Hardware Connectivity Troubleshooting
How to Detect the Fault? | Troubleshooting Steps |
|---|
or
Red error in the Power Center
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
or
The connection status will be stuck at a certain point
Verify that the Network APN is correct.
Verify that the server URL is correct.
Check with the technical support team that the SIM card has been activated.
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.
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.
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.
Confirm the modem is properly connected. If not unscrew the modem connector and properly screw it back in a clockwise direction.
Reposition the modem, and try multiple locations to improve the network reception. Also, ensure crosslink foam is intact
If you are using a local SIM card, confirm there is an internet-ready SIM card present.
Ensure the GPS time stamp is accurate, if it is not, proceed to the next step
Enhance the connection between the Elara and the antenna
ELARA Unit Not Upgrading
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
At least one of the MODBUS devices is connected, but others are disconnected
Confirm the Elara is on the latest version, if not, upgrade the Elara Unit
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
If the device uses different physical and virtual IDs, confirm both IDs are correctly configured. Refer to respective device documentation on the knowledge portal
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
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
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).
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
...
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
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.
3. Make sure that the time stamp is accurate. Otherwise, follow the troubleshooting steps for the wrong timestamp
...
...
Ensure that the two cables connected to the sensor in the Tray/Metal Box are secured on both sides.
...
When the fuel sensor is connected to the communication terminal block but is unable to communicate with the Elara device |
|
Power Center Troubleshooting
How to Detect the Fault? | Troubleshooting Steps |
|---|---|
|
|
Fuel sensors are communicating properly, but the data they provide is incorrect. |
|
