Latest Version: 2.2.0
The utilities integrated into this library are provided to simplify building and maintaining factory firmware.
You can view the library’s source code on GitHub. Click here to see information on the available versions of this library.
To add this library to your project, add
#require "FactoryTools.lib.nut:2.2.0"
to the top of your agent and/or device code
If your factory firmware puts production devices under test (DUT) into deep sleep, when the devices awake (ie. perform a warm start) they will immediately begin re-running the factory firmware. This is standard imp wake-from-sleep behavior. Unfortunately, this also means that you factory firmware may call the Factory Tools methods before the device has received the information from the server it needs to be able to return valid data via the Factory Tools methods. The factory firmware will erroneously believe that it is not running in a factory environment.
To avoid this issue, you should make use of Factory Tools 2.2.0’s support for asynchronous operation. The methods isFactoryFirmware(), isFactoryFixture() and isDeviceUnderTest() can now take an optional callback function with a single parameter, result, into which the boolean answer is placed. For example a callback registered with isFactoryFixture() will receive true if the device is a BlinkUp fixture, or false if it is a device under test.
In each case, embed your BlinkUp fixture set-up flow and DUT test flow within the callbacks to ensure these flows are actioned correctly. Examples are given in the method descriptions below. It also demonstrated in the accompanying example, FactoryExampleAsync.device.nut.
You only need employ asynchronous operation on the first call to one of Factory Tools’ methods. Once the first callback has been executed, you can be sure the status information is present, and all other calls can be made synchronously without penalty.
Important Note Factory devices may warm-start outside of factory firmware control as outlined above. If fresh factory firmware is deployed during production, devices will receive the new code and automatically restart to run the new code. We strongly recommend all users of Factory Tools take advantage of the asynchronous methods to manage this situation.
Asynchronous functionality does not impact synchronous operation, so existing code can continue to make use of the library without requiring updates.
FactoryTools.lib.nutSupported on the device and agent.
If no callback is provided, the method returns true if firmware is running in the factory environment, false otherwise. Both factory BlinkUp™ fixtures and devices under test (configured via factory BlinkUp from a BlinkUp fixture) will return true.
if (FactoryTools.isFactoryFirmware()) {
// Running in the Factory Environment
} else {
server.log("This firmware is not running in the Factory Environment");
}
If a callback is provided, the function will be called when the device has received the required status information. The callback takes a single parameter, result, which will be true if firmware is running in the factory environment, otherwise false.
The callback can also be used in your factory agent; it will simply be invoked immediately.
Supported on the device and agent. This method is intended to make it easy to determine whether to follow the factory fixture flow or device under test flow in your factory firmware.
If no callback is provided, this method returns true if the imp is designated as a BlinkUp fixture, false otherwise.
If a callback is provided, the function will be called when the device has received the required status information and is able to verify the host device’s type. The callback takes a single parameter, result, which will be true if the device is a BlinkUp fixture, otherwise false.
The callback can also be used in your factory agent; it will simply be invoked immediately.
FactoryTools.isFactoryFixture(function(isBlinkUpBox) {
if (isBlinkUpBox) {
// Device is a factory imp
configureFactoryImp();
} else {
// The next call need not be asynchronous since we can be sure
// at this point (we're executing in a callback) that the status
// data has been acquired
if (FactoryTools.isDeviceUnderTest()) {
// Device is a production unit - test it
testDeviceUnderTest();
} else {
server.log("Not running in Factory Environment");
}
}
});
Supported on the device and agent. This method is intended to make it easy to determine whether to follow the factory fixture flow or device under test flow in your factory firmware.
If no callback is provided, this method returns true if the imp is not configured as the BlinkUp fixture, false otherwise.
If a callback is provided, the function will be called when the device has received the required status information and is able to verify the host device’s type. The callback takes a single parameter, result, which will be true if the unit is a device under test, otherwise false.
The callback can also be used in your agent; it will simply be invoked immediately.
FactoryTools.isFactoryFixture(function(isBlinkUpBox) {
if (isBlinkUpBox) {
// Device is a factory imp - configure it
configureFactoryImp();
} else {
if (FactoryTools.isDeviceUnderTest()) {
// Device is a production unit - test it
testDeviceUnderTest();
} else {
server.log("Not running in Factory Environment");
}
}
});
Supported on the agent only. If called on the device this method will return null.
If the firmware is running as an agent within the factory environment, this method returns the BlinkUp fixture’s agent URL. Otherwise it returns null. You can use this agent URL to send information about the device under test to the BlinkUp fixture using an HTTP request. There is no asynchronous operation option.
device.on("testresult", function(result) {
local fixtureAgentURL = FactoryTools.getFactoryFixtureURL();
if (FactoryTools.isDeviceUnderTest() && fixtureAgentURL) {
local headers = {"Content-Type" : "application/json"};
local body = http.jsonencode(result.deviceInfo);
local request = http.post(fixtureAgentURL, headers, body);
local response = request.sendsync();
if (response.statuscode != 200) {
server.error("Problem contacting Factory Fixture.");
} else {
server.log("Factory Fixture confirmed receipt of device info.");
}
}
});
The Electric Imp Dev Center documents the latest version of the library. For past versions, please see the Electric Imp public GitHub repos listed below.
| Version | Source Code | Notes |
|---|---|---|
| 1.0.0 | GitHub | Initial release |
| 1.1.1 | GitHub | Adds getFactoryFixtureURL() method; adds support for factory agents |
| 2.0.0 | GitHub | Improve getFactoryFixtureURL() behavior in agent code |
| 2.1.0 | GitHub | Add asynchronous operation to handle DUT warm-start issues |
| 2.2.0 | GitHub | Support cellular by infering MAC address based on the device ID for all imps except the 001; switch to non-deprecated imp API methods; add new method isFactoryFixture() to match new impCentral™ terminology; new library name |
The Factory Tools library is licensed under the MIT License.