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-09-11 08:51 AM . Last Modified: 2020-09-14 08:52 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-09-11 08:51 AM . Last Modified: 2020-09-14 08:52 PM
For engineering offline, it appears that the Binary Input
doesn't reflect your change made for Active/Inactive text
in the present value, but the BV and BO does.
For instance:
Inactive to become OFF
Active to become ON
When refreshing the point, the BV and BO values show proper
text. BI still stays as inactive/active.
When working on the BI at first, I chalked it up to needing to have
a live controller to make the present value change to proper
text, but after seeing the BV and BO work as expected, it
makes me wonder about the BI.
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-09-23 07:30 AM
Hi Jim, Thanks for the feedback.
For Problem #1, I logged a defect with Tridium addressing the inconsistency with default values for Active/Inactive Text. The fact that we don't see Present_Value on the input variety is by design so that an attempt is not made to write this when pushed to the controller.
For Problem #2, Definitely a defect and it's been logged with Tridium.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-09-11 11:37 AM . Last Modified: 2020-09-11 11:40 AM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2020-09-11 11:37 AM . Last Modified: 2020-09-11 11:40 AM
Update to original post: Problem #2 and Problem #3
Problem2
Another problem that is occurring is that if you bring in a fresh BV,BO block and
change both the Inactive and Active values and then save, you'll get a "Can't save
plugin" error having the diagnostics listed below.
If you instead change one of the items and then save, then change the other item
and then save,.. then everything is ok from that point forward even if you later
change both parameters at the same time and save. It's like something falls into
place and is ok after that.
The BI block doesn't seem to be suffering from this particular issue.
So between the 2 posts... the BI has one issue that the others don't have ....and the
others have a problem that the DI doesn't have.
java.lang.IllegalStateException: Missing property slotFacets_
at javax.baja.sync.SetOp.getTarget(SetOp.java:101)
at javax.baja.sync.SyncBuffer.appendSet(SyncBuffer.java:568)
at javax.baja.sync.SyncBuffer.add(SyncBuffer.java:472)
at javax.baja.sync.SyncBuffer.decode(SyncBuffer.java:150)
at com.tridium.fox.sys.broker.BBrokerChannel.syncFromMaster(BBrokerChannel.java:2476)
at com.tridium.fox.sys.broker.BBrokerChannel.syncToMaster(BBrokerChannel.java:2385)
at com.tridium.fox.sys.broker.BFoxComponentSpace$1.commit(BFoxComponentSpace.java:392)
at javax.baja.sync.Transaction.end(Transaction.java:76)
at com.tridium.workbench.propsheet.BFieldEditorSheet.doSaveValue(BFieldEditorSheet.java:127)
at javax.baja.workbench.BWbEditor.saveValue(BWbEditor.java:352)
at javax.baja.workbench.BWbEditor.saveValue(BWbEditor.java:384)
at com.tridium.workbench.propsheet.BPropertySheet.doSaveValue(BPropertySheet.java:106)
at javax.baja.workbench.BWbEditor.saveValue(BWbEditor.java:352)
at javax.baja.workbench.BWbEditor.saveValue(BWbEditor.java:393)
at com.tridium.workbench.shell.BNiagaraWbShell.save(BNiagaraWbShell.java:863)
at com.tridium.workbench.shell.WbCommands$SaveCommand.doInvoke(WbCommands.java:1409)
at javax.baja.ui.Command.doInvoke(Command.java:311)
at javax.baja.ui.Command.invoke(Command.java:281)
at javax.baja.ui.BButton.doInvokeAction(BButton.java:149)
Maybe Problem 3?
It looks like you can change the block's parameters in the palette and they'll be changed from that point
forward. Don't know if this is an issue or not, but it might actually be a good thing for your own default
settings when you bring in a block. The reason i'm bringing it up is that it's changing the Schneider
palette and don't know if that was the intent.
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-09-23 07:30 AM
Hi Jim, Thanks for the feedback.
For Problem #1, I logged a defect with Tridium addressing the inconsistency with default values for Active/Inactive Text. The fact that we don't see Present_Value on the input variety is by design so that an attempt is not made to write this when pushed to the controller.
For Problem #2, Definitely a defect and it's been logged with Tridium.
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-30 11:39 AM
I'm still seeing the "Cannot save plugin" error in iteration 22.
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.