You can use CalAmp IO (input/output) profiles to display custom labels for the digital inputs generated by your devices on the Tracking screen (such as a Plow Up and Plow Down label for the active and inactive status of a plow input).


Note: Be aware that IO profiles don't do anything by themselves; they must be assigned to an asset that has its designated inputs (on the Admin - Assets screen) in order to have your custom input labels appear on the CalAmp map.


To view your IO profiles, follow these steps:


  1. In the sidebar menu on the left, click .
     
  2. Click IO Profiles on the flyout menu that appears.
     
    The Admin - IO Profiles screen will appear.
      
    By default, your IO profiles are listed by name in ascending order (from A to Z for words).
     
  3. If you want to see IO profiles in subgroups of the one you have selected in the Group Chooser, make sure that View Subgroups is toggled on at the bottom of the screen.
     
  4. You can scroll down the grid to see all the IO profiles you have available to assign to your assets.
     
  5. You can export the grid data to a CSV (comma-separated value) file by clicking  at the top right.
     
  6. You can add or remove columns by clicking at the top right of the grid and following the steps in Customizing Displayed Columns.
     
  7. If you don't have CalAmp save grid modifications you make automatically for all the application's screens (if the Automatically Save Grid Settings toggle in the Preferences area of My Profile is deselected — see Viewing Your Profile and Setting Your Preferences), you can save any layout changes you've made to the Admin - IO Profiles screen by clicking . (If you haven't made any layout updates you can save, will be above the grid instead.) See Saving Grid Changes for an Individual Screen for more details.
     
    Here is an explanation of the column headers:
     
    • Group: The name of the fleet group the IO profile belongs to.
       
    • Name: The IO profile identifier, which is often the type of vehicle, device, and/or inputs the installation includes.
       
    • Inheritable: Whether the IO profile can also be applied to assets in subgroups of the group it is assigned to (so the subgroups, or child groups, can inherit the profile from the parent group).
       
    • Status: The IO profile's current state in the database, such as Enabled.
      Note: Future plans include being able to set an IO profile to Disabled or Suspended and then not allow it to be associated with an asset; however, this feature isn't currently working.
  8. Just below the grid are icons that enable you to navigate through the pages of data, if needed. See Paging Options for an explanation of these.