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-08 12:31 PM . Last Modified: 2021-01-08 12:41 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-01-08 12:31 PM . Last Modified: 2021-01-08 12:41 PM
*****************************************************************************************
Niagara-MPX modules Version #8 (Build 32) (Fixes/Issues)
*****************************************************************************************
<<<<< SOMETHING EXTREMELY IMPORTANT TO KEEP IN MIND >>>>>>>
This version only has 2 jar files instead of 6 files due to the consolidation of the
bacnet interface. In my case, i deleted all 6 files in the N4 Supervisor before
working with the 2 new files. For the Jace8000, make sure to deal with the 4
orphaned jar files when you update it with the 2 new jar files. The Jace8000 will
still think the 4 old files are still "up to date"
RELEASE NOTES MENTION THESE ITEMS:
72) Supports the duplicate functionality for Script Program and Script Function in the same controller.
73) Hosted the device as soon as it is added into database as well as on station startup.
74) Added "Clear Hosting" action on device.
75) Prevented following objects during upload all and download all.
- Room Bus
- App Menu
- Room Bus Monitor Alerts
76) Added the name of the failed property in download all job log.
77) Added RP controllers in the palette.
78) Removed MPX network from module.
79) Fixed the issues 164,165,166,167 from issue tracker in the Teams page.
MY OBSERVATIONS:
1) SchneiderBacnetNetwork consolidated into BacnetNetwork. So far in
navigating around and reviewing the current items in my forum list,
it appears that the functionality is still working as expected from
what i've come across so far. I think in the long run that this will be a huge
improvement for integrating with existing systems.
2) Uninitialized Device View New Update:
Existing problem was that the Unitialized Device View can contain old
information that never disappears until that controller is initialized.
If controller not initialized, it will remain displayed forever even if
controller is physically disconnected from the ethernet or the station
is restarted. If there is a second N4 Supervisor, this server will still
show all the uninitialized devices from before, even though the first N4
Supervisor initialized some devices.
In this module version a station reboot will now clear out the Unitialized
view and allow it to freshly start over detecting devices. This appears
to be similar in ideology to what we had to deal with for an AS-P when old
Bacnet devices would remain in the cache until the AS-P was rebooted.
Eventually we got a button in the Bacnet discover window that would clear out
the cache.
What is needed is either a seconds timeout to clear out old devices that don't
exist anymore as well as update the current state of controllers and/or a button
to clear out this screen so that it can start out fresh again. But at least we
now have a workaround that we didn't have before.
UTILITY BLOCKS PARTIALLY FIXED:
1) Sub String: Output type was changed to string instead of numeric, which is
now correct. The script format is also correct. Problem is that the verbage
of "Number" and "Offset" in the block property descriptions are flip-flopped.
If the verbage gets corrected, the block would then be 100% functional.
Example of correct format: Mid(InputString,Offset,Number)
*****************************************************************************************
EVERYTHING FROM THIS POINT DOWN LOOKS LIKE IT HAS THE SAME
PROBLEMS FROM PRIOR VERSIONS
*****************************************************************************************
FORUM ITEMS NOT FIXED:
1) 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
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) Not able to download objects into Jace8000 hosted controllers
😎AO/AI for Voltage/Current: Units are fixed to either Volts or current for
present value on wiresheet even if choosing "Percent" on the property sheet.
9) 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.
10) Schedules: Previous Transition Time, Next Transition Time, Following Transition Time
showing large integer number instead of Date/Time when pin slots exposed. On property
sheet, Next Transition Value is blank and Following Transition Value is "Null". 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.
*****************************************************************************************
SCRIPT ITEMS NOT FIXED:
1) Script Program flow type setting for Loop/Fallthru not changeable.
2) The initial value in script editor is showing up in the block properties
as "Start Value" but doesn't appear to function in the script block.
3) Public Numerics are not holding values at the script block. They still
need a link to an external Analog Value object. Otherwise it goes "Null"
4) Public Numerics are hidden until you expose the pin slots
*****************************************************************************************
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.
UTILITY BLOCKS ITEMS NOT FIXED:
1) Output is set as an Integer and not changeable for:
GreaterThan
GreaterThan/Equal
LessThan
LessThan/Equal
Not Equal
2) IndexOf: Output needs to be numeric instead of string
Example usage: Find(abcde,bc)
Result: 2
3) IndexOf: "Find" syntax will find case insensitive items while
"Search syntax will find case sensitive items. May need more
options to handle both scenarios.
4) DifTime: Syntax is incorrect
DifTime (Wrong): Utility1_out00 = DIFFTIME("MINUTE" , DateTimeInput1 , DateTimeInput2)
DifTime (Right): Utility1_out00 = DIFFTIME(MINUTE,DateTimeInput1,DateTimeInput2
5) Min Off Delay: Countdown timer is in seconds instead of minutes. A divide by 60
insertion will fix this, as seen in the Min On Delay
6) Count Up: Input count max is showing as Boolean
7) Count Down: Input count start is showing as Boolean
😎Latch: Output is only digital with the Sample+Hold output missing.
This may be a selectable feature that was omitted from the pull-down.
*****************************************************************************************
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) Velocity Pressure block: Present Value is hidden, but can make visible again
by activating the pin slot
4) BoxFlow block: Priority 16 is shown which will fight the internal program of
the VAV object if anything is attached.
5) 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.
6) EffectiveReheatCmd block: Needs the Priority 16 available since this is the
feedback from the hot water valve for showing on the eCommissioning Tool.
7) 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.