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!️
Points Wiresheet (Enabling objects overwrites Ipr16 in MPX)
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: 2020-10-0909:21 AM
I am seeing the same issue. If the local logic is writing to priority input 16 the controller should block the external write request. The MNB's function this way. This doesn't solve the issue of how Niagara checks if a point is writeable by writing null to priority 16. If the message is blocked, such as it does with the MNB's, then the point will show a fault in Niagara. We have been programming MNBs to use priority input 15 to avoid both issues and I think MP's should be programmed the same.