Follow along for an enriching discussion with our CEO, Peter Herweck, and industry leaders for a captivating Global Keynote at #InnovationSummit Paris 2024. Watch recording and join the #ImpactMaker movement!️
Niagara-MPX modules Version #15 (Build 41) (Fixes/Issues)
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.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-03-2509:39 PM. Last Modified: 2023-07-1808:28 AM
Niagara-MPX modules Version #15 (Build 41) (Fixes/Issues)
***************************************************************************************** Niagara-MPX modules Version #15 (Build 41) (Fixes/Issues)
***************************************************************************************** RELEASE NOTES FROM TRIDIUM MENTION THESE ITEMS:
88) Fixed the issues from issue tracker in the Teams page 276,279,280
***************************************************************************************** FORUM ITEMS FIXED:
N4 Supervisor and Jace8000 hosting MPX controllers on ethernet port #2: Both N4 Supervisor and the Jace8000 can now properly host MPX controllers
located on the 2nd ethernet port of the Jace. History of problem was that the
N4 Supervisor could host MPX controllers on the 2nd port of the Jace, but the Jace itself couldn't host them. Then the problem flip flopped in a later release where the Jace could host the MPX controllers, but the N4 Supervisor couldn't. Now both scenarios can host the MPX controllers.
***************************************************************************************** EVERYTHING FROM THIS POINT DOWN LOOKS LIKE IT HAS THE SAME PROBLEMS FROM PRIOR VERSIONS: ***************************************************************************************** FORUM ITEMS NOT FIXED:
1) Schedule: Minutes to Following Changes reflects a midnight time instead of what would be occurring the next morning. Example...showing midnight instead of 7am 2) Schedule: Previous Change Time, Next Change Time, and Following Change Time are showing incorrect times. 3) BO block shows a "Property:Unknown Property" error and goes into fault from time to time, but still functions when commanded ON/OFF 4) Temperature Input has an OutofService set to False upon import which is inconsistent with the other inputs set to True upon import 5) 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 6) Schedules priority level not changeable from 16 7) Event Enrollments don't have Alarm Text. (Perhaps Niagara function?) 😎 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. 9) Lonworks Link appears on objects when deleting various other objects from wiresheet
***************************************************************************************** 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.
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 NOT FIXED: 1) Velocity Pressure block: Block still shows "Out of Service" after initial Download All 2) 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.