SpaceLogic for Niagara Forum
This forum is a place for technical users to share information and collaborate on the integration of SpaceLogic BMS controllers into Niagara BMS.
Posted: 2021-01-21 03:41 PM . Last Modified: 2023-07-18 08:28 AM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-01-21 03:41 PM . Last Modified: 2023-07-18 08:28 AM
*****************************************************************************************
Niagara-MPX modules Version #10 (Build 34) (Fixes/Issues)
*****************************************************************************************
RELEASE NOTES MENTION THESE ITEMS:
81) Fixed the issues from issue tracker in theTeams page
87,171,172,220,221,223,225,226,227
FORUM ITEMS FIXED:
1) AO/AI blocks for Voltage/Current will now allow a units choice for present value.
Problem was that the units were stuck at either Volts or Milliamps for present value
on wiresheet even if choosing "Percent" on the property sheet.
UTILITY BLOCKS PARTIALLY FIXED:
1) Latch: Output is only going to latch an analog value and are not selectable
between analog and digital. "Latch Input" will hold the block at its last
seen analog value. "Reset Input" will allow the output to track the input.
If this were a freeze stat scenario, we'd need to latch a binary output
based on a status from a binary input. Would be great to latch both analog
and digital values. UPDATE: After our weekly cadence meeting and
talking about this block, i went back to check its configurability menu
and the analog/digital selection isn't there.
2) MinOffDelay: TmRem is corrected to be a Float. Out value is corrected as a binary
ISSUE: Countdown timer is in seconds instead of minutes. A divide by 60
insertion will fix this, as seen in the Min On Delay.
BLOCK CONSISTENCY PROBLEM:
1) Equal: Default inputs are binary, while the other 5 comparison type of blocks
have integer inputs as default
PERHAPS ADDITIONAL FUNCTIONALITY NEEDED:
1) IndexOf: "Find" syntax will find case insensitive items while
"Search" syntax will find case sensitive items. May need both
these options to handle various string scenarios.
VAV OBJECT ITEMS FIXED:
1) Velocity Pressure block: Present Value no longer hidden.
SCRIPT EDITOR CHANGES/PROBLEMS:
1) All declared Public Numerics are now missing from the wiresheet block shape and
not visible/choosable from the pin slot selection screen. (ISSUE)
2) The first public numeric that is declared will show up in property sheet, but all
others aren't being shown. (ISSUE)
3) Public Numerics are still an issue. They're no longer linkable on the wiresheet object
and nearly all of them are missing on the property sheet except for the first one
declared. (ISSUE)
4) Adding FallThru triggers in the list will temporarily be shown and then disappear
on their own. While visible, i was able to get the script to trigger a couple times.
After that, the Fallthru trigger disappeared from the list. (ISSUE)
5) The value status in the Initial Values tab section always seems to remain at 0 if an
initial start value is chosen. (ISSUE)
*****************************************************************************************
EVERYTHING FROM THIS POINT DOWN LOOKS LIKE IT HAS THE SAME
PROBLEMS FROM PRIOR VERSIONS
*****************************************************************************************
FORUM ITEMS NOT FIXED:
1) BO block shows a "Property:Unknown Property" error and goes into fault from time to
time, but still functions when commanded ON/OFF
2) Temperature Input has an OutofService set to False upon import which is
inconsistent with the other inputs set to True upon import
3) BV/BO: Priority arrays still show Active/Inactive even after changing text. This is
the light blue dot section where you can override the value
4) Schedules priority level not changeable from 16
5) Event Enrollments don't have Alarm Text. (Perhaps Niagara function?)
6) String fault. Occurs when a String Value object is freshly brought into a live
controller. It'll start out with no errors, but if you wait for a bit it'll
show the error message "Property:Unknown Property" and go into fault.
If you put an actual string into the PresentValue, it will pass ok, but will go
into fault eventually as well. While in fault, the block seems to act normally.
7) Multi-State: If you first create the block and set the number of states to 4
for example and fill in the items, it will still show the original state text
for the value of the block on the wiresheet. If you then change the number of
states to any other number, the block will start to update with the correct state
text. The issue is the first time you set up the "number of states". If it is changed
to any other number, then it becomes correct.
😎 Schedules: Previous Transition Time, Next Transition Time, Following Transition Time
showing large integer number instead of Date/Time when pin slots exposed. Value is
stuck at "True" but any blocks connected to it can still properly go ON and OFF based
on time schedule. There are misleading values on property sheet for Previous Transition
Time, Next Transition Time, and Following Transition Time where it can be ahead by an hour,
or reflects a Midnight time (showing 1AM due to being ahead) when in actuality the
next transition occurs sometime during the next day.
*****************************************************************************************
UTILITY BLOCKS NOTES:
I didn't go back over any previously reviewed blocks that were successful in the past.
UTILITY BLOCK COMMON ISSUES NOT FIXED:
1) Some input type choices may not apply to the block type. All blocks
have a choice of Boolean,DateTime,Float,Integer,String.
2) Input and Output names (in/out) can be changed, but the settings value
reverts back to (in/out), while the block slot name will maintain the change.
*****************************************************************************************
VAV OBJECT ITEMS NOT FIXED:
1) An "Upload all" done at any time creates proprietary 1840 object inside the Velocity
Pressure block and causes future downloads to fail.
If the new proprietary object gets manually deleted from slot sheet, downloads
go ok after that.
2) Velocity Pressure block: Block still shows "Out of Service" after initial
Download All in the initial steps section.
3) BoxFlow block: Priority 16 is shown which will fight the internal program of
the VAV object if anything is attached.
4) DamperCommand block: Priority 16 is shown which will fight the internal
program of the VAV object if anything is attached. Perhaps Priority 15 should
be shown if outside logic needs to have control or just remove it.
5) EffectiveReheatCmd block: Needs the Priority 16 available since this is the
feedback from the hot water valve for showing on the eCommissioning Tool.
6) DischargeAirTemp block: This object needs the Priority 16 available since this
is the feedback from the duct temperature if available for showing on the
eCommissioning Tool.
*************************************************************************************
UNCONFIRMED VERIFICATION AT THIS TIME:
1) Lonworks Link appears on objects when deleting various other objects from
wiresheet
*************************************************************************************
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.