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!️
Version 16 - Duplicating or Copying Inputs and Outputs
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-04-1407:49 AM. Last Modified: 2023-07-1808:27 AM
Version 16 - Duplicating or Copying Inputs and Outputs
Duplicating or copying an input/output with an assigned terminal reference is no longer allowed in an online controller. This functionality can be useful when you have an input/output already setup and you need another like one. It appears like item 277 on the issue tracker has requested this. I'm wondering if the operation could still be allowed but the duplicated point could be created with an unassigned terminal reference?
There was a bug that allowed more than one point to reference the same terminal. This was creating corrupted databases so the MP deleted all objects on a power cycle to prevent the controller from totally locking up. The "partial" fix was to prevent duplication of points which is not what we want at all.
The first goal is to have the Terminal stripped when performing a duplicate on a point, while keeping all the rest of the properties. A copy/paste within the same controller would behave the same as a duplicate.
The other goal is to have the terminal stripped on a copy/paste from one controller to another if the terminal is already in use or is invalid in the target location. If the terminal is valid and unused in the target location then the terminal should be preserved on a copy/paste between controllers.