For those who were present for the cadence call today, it was mentioned that the OSS block won't be
part of the next wave of blocks, and Brad had a funny comment about it. To help Brad out, i'm sending
over to his castle some reinforcements to help fortify the OSS turrets.
This is an OSS script that i created for some simple OSS applications in Continuum when it didn't really
need a full scale self-learning OSS block, as compared to the world class NW8000 version. It's based
on a moderate temperature gain that could be possibly achieved over a period of time depending on
the outside air temp and space/return temp. The setting value of temperature per minute is adjustable
internally in the script. This script also works in EBO....but in that system it had needed a factor of
14400 seconds added to the date calculations. For Niagara, I found out just now that i could eliminate
that value once again. So keep that in mind if testing between Tridium and EBO.
In the picture, the reason i'm showing a binary value in place of the Binary Schedule Value and a
Date/Time Next Transition in place of the Binary Schedule Next Transition has to do with a problem
i'm seeing in hooking up my block to the Binary Schedule from the Config palette. It worked with a direct
hookup in EBO.
The Binary Schedule Date/Time is some huge number that the Date/Time of the script can't recognize. The
Value out of the Binary Schedule is also freezing up the Script block. So basically, i'm just showing what
"should" happen if working properly since it works in EBO. It works if connected up, as in the picture.
Brad, you can thank me later on with a treasure chest full of gold coins.
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!