Tested the Binary Schedule and here are comments/issues for this
initial pass through it:
1) Request: Elements have to be added from scratch for Occ/Unocc and can
be a chore to set up upon first block creation. Would be nice if the elements
themselves were pre-created and had some default times in them such as
5am to 11pm or something of the sort.
2) Request: The scheduling elements start with Monday as element #1. This seems similar
to the function blocks in the Xenta function block editor. Wondering if Sunday
should be considered as Element #1?
3) Request: There's no text values that can be set for On/Off indication. The defaults
are active/inactive with no option to change.
4) Issue: The next block in the sequence sees the On/Off command as expected, but the
present value in both the properties and block visual don't change from Inactive to Active
5) Issue: In the "Schedule Default" setting, there's no choice for an enumeration "1". The
only visible choice is "0".
6) Issue: If you choose a "Schedule Default" from it's default value of "Null", then the block
Reliability status shows a configuration error. The block will still function though.
I can comment on a couple of these items.
Requests 2 & 3 are BACnet-related.
2: The BACnet standard defines Weekly_Schedule, ArrayIndex=1 is Monday. To offset this 'under the covers' would be rather confusing to many users.
3: The BACnet Schedule does not have a corresponding Active/Inactive text properties that you would find in a binary object type. When you consider a pure BACnet schedule is not datatype specific (the concept of binary, enumerated, and analog schedule types is an EBO/MPX thing) - having a state text would not make much sense. On the bright side, the end-user would ultimately see the result in the linked object. For a binary schedule, this would be linked to a binary object which will display the corresponding Active_Text or Inactive_Text property value.
I will also note, that in issue #5, you can manually set a value there but it makes sense to ask for Active/Inactive for the binary-schedule to distinguish it from the enumerated schedule.
For item #2, since it's the bacnet default as you're mentioning... i'm pretty much
wondering if there is enough of a demand for a change or not. We're pretty much
used to Function Blocks having Monday as the start point and Script Programs
having Sunday as the start point....so since this is a new interface but using standard
bacnet...maybe it's not too much of a big deal to keep the way it is unless people would
really like it changed.
For Item #5 and #6, my focus was for how the schedule will interpret no actual scheduled items,
or what happens during a block of time outside of the time allocated to an "on" value.
When using the Bacnet schedule in Continuum b3 or EBO b3, the binary bacnet schedule
allows you to choose Null or "0" or "1" for the default value. ""Null" might not be the choice
you want to pass to the next object in the binding path. When i click on the Pulldown, the only
choices are Null and Enumerated. If the "Null" can become any choice .. Null/Active/Inactive....
then that would be good.
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!