You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ProductionGuide.md
+9-7
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,7 @@
1
1
# impt Production Guide #
2
2
3
+
**NOTE:** The contents of this guide have **NOT** been updated with the release of v2.5.0 (support for DUT device groups), and so some of the contents may be out of date.
4
+
3
5
This additional guide is intended for those customers who use *impt* with [production processes](https://developer.electricimp.com/manufacturing). You may use scripts on top of *impt* commands to automate some of the operations.
4
6
5
7
Please read the main [Read Me file](./README.md) first as it covers all the basic *impt* usage and its common components.
@@ -44,14 +46,14 @@ Device Groups may be of different [types](./CommandsManual.md#device-group-type)
44
46
45
47
### Production Device Groups ###
46
48
47
-
Your production devices, which are utilized by end-users, are organized into one or more Device Groups of the *production* type. Different Production Device Groups within the same Product may be used to encapsulate and manage different versions or flavors of your application. Production devices are units that have been blessed; up until that point they are referred to as devices under test (DUTs).
49
+
Your production devices, which are utilized by end-users, are organized into one or more Device Groups of the *production* type. Different Production Device Groups within the same Product may be used to encapsulate and manage different versions or flavors of your application. Production devices are units that have been blessed; up until that point they are referred to as devices under test (DUTs).
48
50
49
51
You can create a Production Device Group with [`impt dg create --dg-type production`](./CommandsManual.md#device-group-create).
50
52
51
53
Production Device Groups have an attribute called *load-code-after-blessing*. This defines when your application is loaded onto production devices: in your factory after blessing, or when an end-user activates a device using BlinkUp™. When a new Production Device Group is created, this attribute always has the value `true`. To change the attribute you can use the `--load-code-after-blessing` option of the [`impt dg update`](./CommandsManual.md#device-group-update) command:
52
54
53
55
```
54
-
impt dg create --name MyProductionDG --descr "Production Device Group for application"
56
+
impt dg create --name MyProductionDG --descr "Production Device Group for application"
@@ -63,11 +65,11 @@ For your [factory setup](https://developer.electricimp.com/manufacturing/factory
63
65
You can create Factory Device Group with the [`impt dg create --dg-type factory`](./CommandsManual.md#device-group-create) command.
64
66
65
67
Each Factory Device Group references a single Production Device Group within the same Product. This is the Factory Device Group’s *target* and this the Production Device Group to which DUTs will automatically be assigned once they have been blessed and become production devices. You specify a Factory Device Group’s target by using the `--target` option during Factory Device Group creation:
66
-
68
+
67
69
```
68
-
impt dg create --name MyFactoryDG --descr "Factory Device Group for factory firmware"
70
+
impt dg create --name MyFactoryDG --descr "Factory Device Group for factory firmware"
0 commit comments