Some devices signal issues on their LED at start-up. Please see Device-Specific Codes if you are seeing unexpected patterns before BlinkUp.
Make sure you understand which impCloud™ your device is intended to be used with. There are now two impClouds: AWS and Azure. Unless your device was sold as ‘for Microsoft Azure’ (or equivalent), it will operate with the AWS impCloud (the original impCloud), which is the default selection in the Electric Imp mobile app. If in doubt, make sure you have selected the AWS impCloud. Note This only applies to development devices.
When configuring your device with BlinkUp, please ensure the following:
Please refer to the imp LED color codes, below.
The following table should help you identify the color patterns your device’s BlinkUp status LED may signal. The smallest marked time unit is one quarter of a second.
Note Connections can proceed rapidly, so you may not see all of the patterns your imp can generate. For example, once a WiFi-using imp has successfully connected to WiFi, you may see only a few red and/or orange flashes before the LED steadily flashes green to indicate it is online. What matters for debugging is the pattern being flashed at the point of failure, ie. the last pattern to flash before the LED is powered down.
|Pre-BlinkUp and BlinkUp Patterns|
|No network settings or
|imp005 waiting for Ethernet||500ms||500ms||250ms||250ms||Repeat|
|BlinkUp Successful||For three seconds|
|WiFi-only Connection Patterns|
|WPS in progress
(press WPS button on router)
|Searching for WiFi network||500ms||500ms||500ms||250ms||250ms||250ms||Repeat|
|Joining WiFi network||500ms||500ms||500ms||250ms||250ms||250ms||250ms||250ms||Repeat|
|WiFi and Ethernet Connection Patterns|
|Getting IP address||500ms||250ms||250ms||Repeat|
|Resolving server name||500ms||250ms||250ms||Repeat|
|Connecting to server||500ms||500ms||500ms||250ms||Repeat|
|Connected to server||500ms||500ms||Repeat|
|Proxy address or port incorrect||500ms||500ms||250ms||250ms||250ms||250ms||Repeat|
|Proxy credentials rejected||500ms||500ms||250ms||250ms||250ms||250ms||250ms||Repeat|
|Cellular Connection Patterns|
|Waiting for modem||500ms||500ms||500ms||250ms||Repeat|
|Waiting for SIM||500ms||500ms||500ms||250ms||500ms||250ms||500ms||250ms||Repeat|
|Registering with a cell||500ms||500ms||500ms||250ms||250ms||250ms||500ms||Repeat|
|Cell Registration Denied||500ms||500ms||500ms||500ms||500ms||500ms||Repeat|
|Connecting via PPP||500ms||500ms||500ms||250ms||Repeat|
|Checking PPP connection||500ms||500ms||500ms||250ms||250ms||250ms||250ms||250ms||500ms||Repeat|
|Generic Connection Patterns|
|Device lost connection||500ms||500ms||Repeat|
|Device deliberately offline||500ms||250ms||250ms||250ms||Repeat|
|Updating impOS™||Continuous for duration of update|
|Normal operation||LED not illuminated|
A solid red or rapidly flashing red LED indicates a power supply issue.
The imp003, imp004m and imp005 have a number of unique LED codes which signal problems with the SPI flash unit that must be connected to the module. These are displayed when these modules start up and do not relate to BlinkUp. If you are encountering unexpected LED light sequences on a device based on one of these imps, please see the respective Hardware Design Guide:
Once it has been enrolled, an imp005-based device will show the ‘Waiting on Ethernet’ pattern while it is attempting to connect by Ethernet. This is identical to the ‘No WiFi Settings’ pattern indicated by other imps. The imp005 does not support WPS, so will never show the ‘WPS in Progress’ pattern.
The following codes are no longer used by modern versions of impOS. They are documented here for users working with imps that may have not been used (and therefore not upgraded) for some time.
|No WiFi settings
(to impOS™ 32)
(to impOS 30)
|250ms||250ms||Repeat for three seconds|
(to impOS 30)
(to impOS 30)
(to impOS 30)
|Continuous for duration of installation|
All imp-enabled devices — which includes your development hardware, factory BlinkUp fixtures and production devices — are configured using BlinkUp. However, not all of these devices are configured using the same BlinkUp implementation. The following table shows the different ways different devices are sent the BlinkUp configuration signal.
|BlinkUp...||Use...||Appears in impCentral ‘My Devices’ List?||Device Type|
|...Your prototype hardware||...The Electric Imp app||Yes||Developer|
|...Factory BlinkUp fixture||...The Electric Imp app||Yes||Developer|
|...Your product in assembly||...Factory BlinkUp fixture||No||Production|
|...Your product in use||...Your BlinkUp app||No||Production|
Note This table covers devices that will connect to Electric Imp’s Public impCloud, whether in its AWS or Azure form. Devices which will connect to a Private impCloud are configured by the customer’s own BlinkUp app in either development or production mode, as appropriate. Only production devices on the assembly line are configured using another means: a factory BlinkUp fixture.
Recent versions of impOS contain many major improvements to BlinkUp on Android devices. Older imps running earlier versions of impOS will not benefit from these improvements until they are updated, a process which can’t take place until your device’s imp has first connected to the Internet after being configured by BlinkUp. If you are having problems configuring a device with an Android phone or tablet, the following may help you get the device to the stage where it can update itself. Ensure:
These adjustments shouldn’t be necessary when the imp-based device has updated to the latest version of impOS, which will take place when the device first connects successfully. If you are still having problems connecting a device for the first time, try configuring it with an iOS device if you can. This will allow the device update, making future, Android-mediated BlinkUps successful.
For a list of Android devices confirmed by Electric Imp and its customers to work well with BlinkUp, see the BlinkUp Mobile Device Compatibility Guide. Many other devices also work will with BlinkUp but have yet not been formally tested. If your device is not listed, following the advice above will ensure your device is prepared for BlinkUp.
For detailed information on imps’ wireless and wired networking requirements, and on issues which may arise during an imp’s attempt to connect to a network, see ‘Network Requirements for imp-enabled Devices’.
Note The imp005 does not support Wireless configuration using WiFi Protected Setup (WPS).
A device’s embedded imp is designed to be driven by a 3.3V DC power supply, commonly derived from a 5V USB feed or from connected batteries. The imp’s operational power range is 1.8-3.6V, but WiFi requires at least 2.5V. If the supply voltage drops below 2.5V, the imp will continue to process Squirrel code (provided the supply is 1.8V or greater) but WiFi will be disabled.
A common source of BlinkUp configuration and connection problems is insufficient power to maintain WiFi while the device makes its initial connection to the Electric Imp impCloud. It is during this process that the device is authorized to connect to the server now and in the future.
Insufficient power at this point can be caused by low batteries, a power supply with insufficient current capacity, or a supply with insufficient voltage. If the power supply can’t support the imp, the imp will attempt to connect, run out of power, reset itself and repeat. This can appear as a fast red blink pattern as the imp quickly reboots over and over again. This LED pattern is a sure message to check your device’s power feed.
The Electric Imp mobile app shows the device’s progress from configuration to connection is presented on the screen of the phone or tablet you are using to set up the device. When the process completes successfully, the app displays the device’s ID and the URL of its agent. The URL can be shared by SMS or email.