Configuring Device-Specific Parameters for ALEOS Configurations from the AMM

The steps below describe how to use the AMM’s Gateways and Deploy screens in conjunction with ACEmanager, to update configuration parameters on a fleet of ALEOS devices. This procedure allows for parameters to be configured uniquely for each device, so that a mass configuration update can be performed where each device will have unique parameter values for individual MSCIIDs.

Note:

• This feature is available AMM 2.16 and above.
• This feature requires knowledge about creating and updating AMM CSV import files. For additional information about CSV import files see the AMM Operation and Configuration Guide: Appendix A.4 - Multiple Device Import CSV.
• Not all valid MSCIID values can be set using this feature. Only Configuration values can be set. Any non-configuration values will be ignored by this process.
• Using the CSV upload procedure to manipulate ALEOS settings as described in the steps below, is intended to be used for configuring device-specific variables and is not intended to do complete configurations.

1. Determine the MSCIID for the parameter you want to update. See below for Commonly Used MSCIIDs. Alternatively, use these steps to determine an MSCIID in ACEmanager...

   a. Open ACEmanager for an ALEOS device in a browser.

   b. Right click on the input field of the parameter that you want to update and select the browser’s menu item which allows you to inspect the element (e.g. “Inspect”).

   

   c. Locate the Name attribute in the raw HTML that is displayed. The value for this attribute is the MSCIID:

   

   The figure below shows another example of locating an MSCIID for a element, this time, from the Device Status Screen in ACEmanager:

   

2. Create or Update an AMM CSV import file for configuring multiple devices as per the options below, using the MSCIID(s) obtained in Step 1. For additional information see Multiple Device Import CSV.

   • Add up to 10 columns where each column title is the form of MSCIID=ID, then enter the value in each row for which the value is to be updated. The following example CSV snippet shows how to set the heartbeat (MSCIID 5024) and password (MSCIID 5003) values for a single ALEOS device: Example CSV with MSCIID Configurations

     ID	Name	Groups	Vehicle Type	Customer	Location	Contact	Notes	MSCIID=5024	MSCIID=5
     N12341	“Joe - MP70 II”	Mixed Bag	Default Vehicle Group>SUV	Customer1	Office	Joe	Main device	8	test1234

     Note: leaving a cell blank for a given row means that the value won’t be updated for device specified on that row.

3. Navigate to the Admin->Gateways menu in the AMM. Note that if you’re planning to update MSCIID parameters related to security (e.g. passwords), first ensure that you are logged in to the AMM using HTTPS, otherwise updates for such parameters will fail.

4. Click the Upload button:

   

5. Select the CSV file that was prepared in Step 2, select Modify for Gateways which already exist in AMM, and select Deploy configuration to gateways:

   

6. Select the Config->Deploy->Deploy menu in the AMM to display the Deploy screen.

7. Click the refresh button and verify that the State column for the device is set indicates Out of sync-local:

   

   The device will update the next time it checks in, after which the State will change to Config Confirmed:

   

   Note: * the ALEOS heartbeat field show in the AMM is not an indicator of when the device will check in next. ALEOS devices have an independent check-in frequency. * the device(s) may need to be rebooted in order for the change(s) to apply (e.g. when changing the M3DA Protocol Password).  

8. Wait until the State changes to Config Confirmed.

9. Open ACEmanager for the device and verify that the MSCIID parameter(s) have been changed on the ALEOS device:

   

Commonly Used MSCIIDs

The following table provides the ID values and descriptions for common MSCIID’s that you may want to configure. Note that these exact values must be entered as input.

Common MSCIIDs