Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Class: AIO
#1
General Description

This thread is for discussion of the AIO device class. Drivers that implement this device class will provide one or more analog inputs and/or outputs.

Fields Provided

[INDENT]It is assumed that, in the general case, the fields will likely be nameable by the user, therefore there are no naming convention limitations on the fields of this device class, other than that they MUST use the appropriate prefix indicator, i.e. that all of them be in one of the forms:

AIO#In_fieldname
AIO#Out_fieldname

AIO#sub~In_fieldname
AIO#sub~Out_fieldname


This indicates that the fields are implementing the AIO device class. They will be prefixed with In_ or Out_ to indicate the direction of the field, followed by an arbitrary fieldname part. As long as the 'fieldname' portion follows the standard CQC field name conventions, that is all that is required from a field naming point of view.

If initial default names are assigned until the user can/does rename them, then it is SUGGESTED that those names in some way refer back to device specific values, so that it is obvious which input or output each field refers to.[/INDENT]


Multi-Unit Considerations

[INDENT]Though it is generally assumed that these fields will be user nameable to reflect their function and therefore all on an equal footing, if the device provides banks of identical sets of inputs and outputs with a specific purpose, the driver MAY use sub-unit naming conventions. In that case the fieldname parts become fixed, and the sub-unit part becomes the user or device provided name. Each sub-unit must provide an identical set of fields.[/INDENT]

Semantic Requirements

[INDENT]All such fields should be semantically marked with the AnalogIO semantic field type, and follow the conventions indicated by that semantic field type. Outputs are not required to be readable. They MAY be, but customization that is intended for generality shouldn't depend on readability of outputs.[/INDENT]

Backdoor Commands/Queries

[INDENT]None are required at this time.[/INDENT]
Dean Roddey
Explorans limites defectum
Reply
#2
(reserved for expansion)
Dean Roddey
Explorans limites defectum
Reply
#3
(reserved for expansion 2)
Dean Roddey
Explorans limites defectum
Reply
#4
Another one that's similar to DIO, so pretty simple to define. Does this make reasonable sense?
Dean Roddey
Explorans limites defectum
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Class: Security Dean Roddey 34 35,407 01-02-2019, 12:26 PM
Last Post: Dean Roddey
  Class: Weather Dean Roddey 6 6,683 10-11-2018, 11:09 AM
Last Post: Dean Roddey
  Class: Thermostat Dean Roddey 17 26,453 01-29-2016, 10:15 AM
Last Post: Dean Roddey
  Class: SceneCtrl Dean Roddey 20 20,819 03-31-2015, 12:38 PM
Last Post: Dean Roddey
  Class: Irrigation Dean Roddey 8 9,526 01-28-2015, 12:09 PM
Last Post: Dean Roddey
  Class: NowPlaying Dean Roddey 8 9,778 09-23-2014, 02:01 PM
Last Post: Dean Roddey
  Class: Switcher Dean Roddey 9 10,613 08-20-2014, 08:17 AM
Last Post: Dean Roddey
  Class: Projector Dean Roddey 29 26,988 08-11-2014, 08:56 AM
Last Post: Dean Roddey
  Class: Lock Dean Roddey 5 7,185 07-31-2014, 01:24 PM
Last Post: Dean Roddey
  Class: ContactClosure Dean Roddey 7 8,737 07-31-2014, 10:14 AM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)