How to define "commands"

33 views
Skip to first unread message

Oisín Grehan

unread,
Feb 2, 2022, 5:02:55 PMFeb 2
to Brick User Forum (Unified Building Metadata Schema)
Hey all,

I'm trying to get my head around how commands (output points) are used to define an operation to actuate. The simplest example might be a thermostat that has a temperature point (input) and a setpoint point (input), but it can also be commanded with a new setpoint (output) -- am I thinking about this right?

So, is brick:Command meant to represent a type definition of a device _can_ be commanded (i.e. this is a owl:class/rdfs:type definition), or is it meant to represent a command _in flight_ (i.e. this is telemetry/an instance of a command that is being sent to actuate a target)

Yours confusedly.

-Oisin 

Erik Paulson

unread,
Feb 10, 2022, 4:32:18 PMFeb 10
to Oisín Grehan, Brick User Forum (Unified Building Metadata Schema)
Hi 

--
You received this message because you are subscribed to the Google Groups "Brick User Forum (Unified Building Metadata Schema)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brickschema...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/brickschema/db6fecf8-fd9e-4ff6-8641-5e6c9c53d752n%40googlegroups.com.

Erik Paulson

unread,
Feb 10, 2022, 4:42:50 PMFeb 10
to Oisín Grehan, Brick User Forum (Unified Building Metadata Schema)
(Sorry, I hit the trackpad with a very unlucky series of taps on the previous message and it went out way too early)

Anyway, Hi Oisín - 

It's the first definition - a brick:Command is a representation of a point that can be commanded. It is not about a message in transit. 

-Erik

Oisín Grehan

unread,
Feb 10, 2022, 6:09:13 PMFeb 10
to Erik Paulson, Brick User Forum (Unified Building Metadata Schema)
Cool, thanks! 
Reply all
Reply to author
Forward
0 new messages