Click here to get more information about the EP types.
If you didn’t manage to resolve or address the issue/s by following this guide, please contact [email protected] or contact the support team through the Augury platform.
Before you Begin
Check the items below before starting the EP troubleshooting process.
Caution!
Are you working in an explosive (Hazardous) environment (CI-D2, CII-D2 ATEX2)? If the answer is yes and the EP is classified and has a battery issue - replace the entire EP and not just the battery.
While working on or near an operating machine, please follow the safety precautions required by the area/plant in which you are working.
Do not attempt to fix an EP installed on any equipment while in the proximity of any exposed hazards. Remember to use appropriate personal protective equipment.
Required Tools and Parts
Required Tools | Image |
2.5mm hex key T-handle - long flat edge/ |  |
2 X 22mm Open-end Wrenches |  |
Halo EP Standard Maintenance Parts | Image |
Augury halo Battery replacement kit (KT00019)
|  |
Spare EP’s (type 1/2/HZ) |  |
EP (AC00009) replacement studs |  |
Adhesive - (Loctite 330 kit/ Epoxy EA 3483/Lord 406/19) Threadlocker – Loctite 242/3 medium strength Adhesive Dispensing Applicator (Gun)- 50ml 4:1 |  |
Android device with Halo installation app + Credentials |  |
Note! The consumable items considered standard EP maintenance parts and should be held on site, if you don’t have them, please reach out to the Augury support team.
Initial Troubleshooting steps
The IoT health tab on the web platform is the place where you can find all halo devices' IoT status, and review the different EP issues as follows:
EP “Low/ “Drained” battery
For EP “Low/“Drained” battery alerts – Replace the battery per the Halo Endpoint battery replacement guide.
EP “Invalid Data”
For EP “Invalid Data” alert – Replace the Entire EP (EP replacement guide).
*If it is accompanied with a low/drained battery alert, replace the EP battery first and not the EP
EP “Out of position”
For EP “Out of position” alert – follow Step 3 on the “Preliminary Connectivity Troubleshooting” section.
Preliminary Connectivity Troubleshooting steps
Note! EP connectivity issues may be caused by malfunctioning EPs, or by EP to Node connectivity issues.
Check the status of all the EPs on the machine
✓ View all EP statuses by filtering the EP table in the IoT health tab by the machine name.
✓ If some of the EPs are online - proceed to the “EP Connectivity Troubleshooting Steps” section
✓ If all EPs are offline – continue to the next step ⇒ 2
Check for potential Node issue
If All EPs on the machine are not sending data:
✓ Check if there is an IoT issue on the connected Node. If there is an issue with the Node address this first.
*Find the connected Node name in the information tab in the device side panel
✓ If there is no issue with the Node, continue to the next step ⇒ 3
Confirm the EP is mounted to the machine and that the SN matches.
Check the Machine and EP locations:
✓ If the machine is in place and not under maintenance, verify that the EPs are turned on and in proximity to the machine.
✓ If the EPs are not on or near the machine for any reason, please re-mount the EPs to the right location and make sure they are turned ON (see instructions in the “EP Connectivity Troubleshooting Steps” section below).
Note! If the EPs are on the machine and not switched off, please contact Support for an advanced investigation.
EP Connectivity Troubleshooting Steps
Locate the relevant EP and check for damage.
✓ The EP is mounted or in proximity to the machine
✓ The SN matches the SN on the alerted EP
✓ Inspect for physical damage (e.g. broken parts). If found damaged, have it replaced (EP replacement guide).
Verify the EP is turned “ON”
✓ Open the EP cap and check if the switch is positioned upward
✓ If not - turn it “ON” by toggling the switch upwards.
✓ Switch the EP “OFF” by toggling the switch downwards and then back “On” by toggling the switch upwards.
Verify EP Self-Test passed (LED indications)
✓ Blue light blinking twice at the end.
✓ If the test fails: try again
✓ If it fails twice, have it replaced (EP replacement guide).
* The EP must be stationary and placed on a flat surface during the Self-Test procedure.
Connectivity Validation
The “Not sending data” alert will be resolved once an updated EP data is uploaded to our servers. The two recommended options for connectivity validation are as follows:
Open the Halo installation app. Search for the EP using the top search bar by typing the EP SN. Check the last “Connected” time and verify that the EP has communicated following the action taken.
Check the EP status on the IoT Health tab over the web platform. The alert will be resolved within an hour (if there is proper connectivity with the Node).
Note! If after the following 24 hours, the “Not sending data” alert remains, and there are no new alerts on the linked Node or Router - please replace the EP
(EP replacement guide).
Document Number: AL00012
Revision: A