The Status LEDs on the rear of iSTAR Pulsar give feedback to the user on what is happening at any given time. There are two LEDs:
- The Upper LED indicates WiFi activity
- The Lower LED indicates System activity
Start Up
During the Start Up procedure, the LED sequence will be:
| Wi-Fi LED | Off | Off | Pulsing Green | Solid Green |
| System LED | Solid Red |
LED changing gradually between red and yellow |
Solid Green | Solid Green |
Once both status LEDs turn solid Green, the device is at "Ready" status, and is ready for use.
Right mode
When switching from Left mode to Right mode, the Wi-Fi LED will briefly pulse Green before the device returns to "Ready" status (both LEDs solid Green):
Capturing Data
When iSTAR Pulsar is capturing data (mode switch set to the Right), both status LEDs will pulse Blue alternatingly:
Stopping capture will result in both status LEDs returning to solid Green ("Ready" status).
Left mode
When switching from Right mode to Left mode, the Wi-Fi LED will briefly pulse Green before the device again goes to "Ready" status (both LEDs solid Green):
If when moving the mode switch to the Left the Wi-Fi status LED continues pulsing indefinitely, then the device has not been able to connect to a network. In such a case, users should switch back to Right mode and try again to register a network to connect to.
Updating firmware
Once connected to a Wi-Fi network, iSTAR Pulsar will always check for available firmware updates. If a new version of firmware is available, it will automatically be applied, during which time the system LED will pulse Yellow:
If no captures are queued for upload, the status LEDs will both return to solid Green once the update has been applied, users should then restart the unit to finalise the update. For more information around updating firmware, see this article.
If there are captures queued for upload, then this will commence after any firmware update has been applied.
Downloading Data
Whilst iSTAR Pulsar is downloading data to an external SSD the Wi-Fi LED will pulse Blue, while the system LED remains solid Green:
Once all queued data has uploaded, the device will once again return to "Ready" status, with both status LEDs solid Green.
Synchronisation in process
When attempting to initiate data capture immediately after powering on iSTAR Pulsar, users may note that capture does not start, instead they see the lower status LED light yellow briefly and capture does not immediately start:
It can take up to 40 seconds for the camera after the LED-s have turned green to reach full synchronisation. The above behaviour indicates that the synchronisation process has not yet been completed - once the process has finished, capture will be initialised as usual.
Note: to avoid this from happening we recommend to wait 40 seconds after the LED-s turn green and only start capture then.
Shutdown
During the Shutdown procedure, the LED sequence will be:
| Wi-Fi | Solid Green | Off | Off |
| Status | Solid Green | LED changing gradually between red and yellow |
Off |
System Error
The only time that users should see a Red LED is when initially power up the device, as shown in the Startup section above - any other occurrence of a Red LED indicates a system error of some kind.
In the first instance, users should power the device down and back up again, this will resolve the majority of issues. If a Red LED persists, please raise a support request, providing full details of the situation that resulted in the error, and our Support team will be happy to assist.
Network Error
When iSTAR Pulsar encounters a critical problem, while trying to connect to a network, the top LED will be a solid pink. The most likely cause of this issue is when the password saved for the wireless network is incorrect: switching back to right mode, connecting to the camera and reconfiguring the network connection again should address this issue.
When attempting to initiate data capture immediately after powering on iSTAR Pulsar, users may note that capture does not start, instead they see the lower status LED light yellow briefly and capture does not immediately start: