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

This thread is for discussion of the Relay device class. Drivers that implement this device class will provide one or more relays which can be opened or closed via external control, and their current open/close state sensed.

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:

RELY#fieldname
RELY#sub~fieldname


This indicates that the fields are implementing the Relay device class. 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 the default names be in some way related back to device specific characteristics so that which relay is controlled is obvious.

Relays may be readable, but they may not. Some devices will not support it. If you are creating portable content, don't depend on being able to read them.
[/INDENT]

Multi-Unit Considerations

[INDENT]Though generally it is assumed that all relay fields will just be nameable by the user to reflect their usage, if a device provides identical banks of relays, the driver MAY use the sub-unit naming convention, though that means that each sub-unit must provide an identical set of fields. In this case, the user or device provided name will be the sub-unit name.[/INDENT]

Semantic Requirements

[INDENT]All such fields should be semantically marked with the Relay semantic field type, and follow the conventions indicated by that semantic field type[/INDENT]

Backdoor Commands/Queries

[INDENT]None are required at this time.[/INDENT]
Dean Roddey
Software Geek Extraordinaire
Reply
#2
(reserved for expansion)
Dean Roddey
Software Geek Extraordinaire
Reply
#3
(reserved for expansion 2)
Dean Roddey
Software Geek Extraordinaire
Reply
#4
Very similar to the DIO and AIO ones basically. Does that all make sense?
Dean Roddey
Software Geek Extraordinaire
Reply
#5
Tightened up to require readability, and to clarify multi-unit naming. At first on these types of things I said that there wouldn't be multi-unit requirements, but that's overly broad. In some cases it might be useful, so it's been expanded to discuss that.
Dean Roddey
Software Geek Extraordinaire
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Class: Thermostat Dean Roddey 17 4,042 01-29-2016, 10:15 AM
Last Post: Dean Roddey
  Class: SceneCtrl Dean Roddey 20 2,515 03-31-2015, 12:38 PM
Last Post: Dean Roddey
  Class: Irrigation Dean Roddey 8 1,317 01-28-2015, 12:09 PM
Last Post: Dean Roddey
  Class: NowPlaying Dean Roddey 8 1,300 09-23-2014, 02:01 PM
Last Post: Dean Roddey
  Class: Switcher Dean Roddey 9 1,428 08-20-2014, 08:17 AM
Last Post: Dean Roddey
  Class: Security Dean Roddey 33 4,189 08-13-2014, 03:02 PM
Last Post: Dean Roddey
  Class: Projector Dean Roddey 29 3,085 08-11-2014, 08:56 AM
Last Post: Dean Roddey
  Class: Lock Dean Roddey 5 937 07-31-2014, 01:24 PM
Last Post: Dean Roddey
  Class: ContactClosure Dean Roddey 7 1,074 07-31-2014, 10:14 AM
Last Post: Dean Roddey
  Class: DIO Dean Roddey 7 1,295 07-31-2014, 10:08 AM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)