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: 2020-10-03 04:45 PM . Last Modified: 2020-10-03 04:45 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-10-03 04:45 PM . Last Modified: 2020-10-03 04:45 PM
The current release notes appear to apply fixes from 67 thru 90
Release Note listings for items I recognize:
71) Dragging items from the palette does not create them in a live controller.
PulseWidthModulatedOutput fails (note: creation works in Config Manager).
80) During a Download All, Analog Input Present Value should not write to present
value unless outs of service is true.
85) Changed the schedule->weekly schedule->day names.
86) For script program public slots were not getting generated.
87) For most of binary objects default active inactive text was not set. Also on
upload object present value was disappearing.
89) Fixed the wiresheet positioning issue when we drag and drop the object from
palette.
90) Fixed the issue of binary values don’t register in script.
**************************************************************************************
Comments on above fixes:
71) Block appears to come in ok to live controller
80) All analog values download properly when Out of Service is True.
Issue: Digital Inputs and Multistate supervised Input are still affected.
Temperature input defaults to OutofService = False upon import unlike
all other inputs which come in "True"
85) Showing Improvement. Schedule shows Monday-Sunday instead of element 1-7
86) Issues:
1) Public Numeric not holding value at block, still needs link to external Analog
Value object. Otherwise it goes "Null"
2) Initial value from script editor is now showing up in block properties but doesn't
appear to do anything.
87) Issues:
1) BI object present value will always show Active/Inactive even after changing text.
2) BV/BO: Plugin errors still occur when changing both texts before saving block
3) BO block shows an Unknown Property error and goes into fault from time to time,
but still functions when units are made to be ON/OFF
4) BV/BO: Priority arrays still show Active/Inactive even after changing text.
89) Appears fixed, although sometimes I see a block temporarily being placed to the
upper left corner, but it then relocates on it's own to proper location.
90) BI,BV,BO objects are not freezing up script block display any more.
**************************************************************************************
Items fixed in new release, but not described in release notes:
1) Ub channel choices for controllers appear to be working better. When you delete
an object that had a channel already assigned, it will show up again for the next
object brought in.
2) Data Types in script editor.
The integer setting now holds its selection instead of reverting back to float.
The initial value also is holding, and appears in the script object properties,
but doesn't appear to do anything in the script block.
**************************************************************************************
Forum Items I didn't see a change:
Jace8000 not able to create objects in hosted controllers
Wiresheet ability to delete Object from wiresheet and database
"Save to Controller" doesn't update a live script
Auto Scaling for analogs
Multistate issues
Schedule Priority 16
VAV object
Lonworks Link appears
Loop Fallthru Setting
Event Enrollment Alarm text
**************************************************************************************
Remaining Items in release notes that I haven't seen mentioned in forum:
(Assuming they are R+D items)
67) Properties showing as "proprietary" when discovered by BACnet discovery.
68) Inconsistent object creation
69) Schedule – There is no way to bind out of Config schedule object to another
Config objects. (AKA lack of present value slot) This will be required
for the MPX to reference its own local schedules in a program etc
70) BACnet Schedule Export - Write Access Denied error when trying to set Priority
for writing. Schedule Export properties show the error is a write access denied.
72) Upload All Objects Breaks binds on the wiresheet.
73) Factory Reset
74) Erase Database
75) Trend Log -> Should we write unit conversion.
Private Transfer fails on writing unit conversion attribute because property
referenced in PT is 85 (Present_Value) but should be 1638 (Internal Value).This
is fixed
76) 1797/1810 - trigger signal is deprecated. no need to handle it. (need to look
into how to show deprecated instead of proprietary.).Now all the proprietary
properties are defined as depricated.
77) If someone sets the logDevice Property from AX Property sheet then link should
get updated.
78) Event enrollment.EventParametreList.choice should show only supported options.
Supported options - OutOfRange, ChangeOFState, ChangeOfValue, FloatingLimit,
BufferReady. Default should be out-of-range.
79) Event Enrollment.Shunt variable should be bindable from the wiresheet
Upload All breaks the binding.
81) MP-V Flow Balance Data - Needs to be treated differently than regualar object.
Flow Balance Data should not be downloaded as a part of Download All. Also,
there should be an action "download" on the Flow Balance Data that should
download all the editable properties. It already has "Upload Object" action that
uploads all properties from controller.
82) Event Enrollment object/property references created in either the wiresheet or
property sheet should be updated in the other sheet but are not
83) Unable to set event parameters for Change_Of_Value event type
84) Event Algorithm Inhibit Reg should be renamed to Shunt Variable Reference to
match the 'Shunt Variable' property. As it is, it is not obvious these two
properties are related
**************************************************************************************
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-10-04 10:44 AM
Update for item 89:
Wiresheet positioning of a new block
For my initial assessment, i was bringing the block into a live controller and seemed
to be working. Upon further examination, if you bring the block into an offline controller,
then the block placement goes into the upper left corner as before.
For some reason it's needing to see a live controller for the ability to work. This
may explain why once in a while that I see the block temporarily go into the upper
left corner before automatically moving to the place you originally dragged it to on the
wiresheet. Perhaps the process doesn't see the live controller at that exact
moment and then the process sees it a few moments later.
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.