Replace NiagaraNetwork in a Jace - Server configuration ?
Or allow to define tags inside each Jaces then share the results on a server ?
I'm not sure I understand
Mike JarmyWed 9 Jul 2014
The main use case for the NHaystack driver is if you have a haystack "device", similar to e.g. a bacnet controller, and you want to bring in its points the standard AX way into either a jace or a web supervisor. The idea is that you can use the driver to have an AX station sit "above" a device that speaks the haystack protocol.
You could use the driver to have a web supervisor and a jace communicate with each other, but I'm not sure why you'd actually want to. Clearly NiagaraNetwork is the best tool for that.
Christian TremblayWed 9 Jul 2014
Great I understand.
In a Jaces + Web Supervisor architecture, how do you make global query over different sites ?
Mike JarmyWed 9 Jul 2014
Are you still speaking about the nhaystack driver, or are you referring to having an nhaystack servlet running on a bunch of jaces?
Christian TremblayWed 9 Jul 2014
Yeah I guess I should start a different topic. I'm wondering what is the best way to deal with nHaystack in an architecture with multiple Jaces and a Web Supervisor.
At first, I thought the nHaystack driver was for that...
Mike JarmyWed 9 Jul 2014
Yeah start a new thread and I'll explain the various approaches there. That way people can find it more easily later.
Jason BriggsWed 9 Jul 2014
The driver in NIagara for Haystack is really built for options. If you are a Niagara server or a JACE, and you want to bring in other Haystack data you can. Products like Sky Spark, FIN Stack, InferStack, and others can now be brought into NIagara too.
Like Jarmy said I would still use the Niagara Network to go between JACEs, as that's a proprietary driver that Tridium created and has more features.
Christian Tremblay Tue 8 Jul 2014
What is the main goal of the driver ?
Replace NiagaraNetwork in a Jace - Server configuration ?
Or allow to define tags inside each Jaces then share the results on a server ?
I'm not sure I understand
Mike Jarmy Wed 9 Jul 2014
The main use case for the NHaystack driver is if you have a haystack "device", similar to e.g. a bacnet controller, and you want to bring in its points the standard AX way into either a jace or a web supervisor. The idea is that you can use the driver to have an AX station sit "above" a device that speaks the haystack protocol.
You could use the driver to have a web supervisor and a jace communicate with each other, but I'm not sure why you'd actually want to. Clearly NiagaraNetwork is the best tool for that.
Christian Tremblay Wed 9 Jul 2014
Great I understand.
In a Jaces + Web Supervisor architecture, how do you make global query over different sites ?
Mike Jarmy Wed 9 Jul 2014
Are you still speaking about the nhaystack driver, or are you referring to having an nhaystack servlet running on a bunch of jaces?
Christian Tremblay Wed 9 Jul 2014
Yeah I guess I should start a different topic. I'm wondering what is the best way to deal with nHaystack in an architecture with multiple Jaces and a Web Supervisor.
At first, I thought the nHaystack driver was for that...
Mike Jarmy Wed 9 Jul 2014
Yeah start a new thread and I'll explain the various approaches there. That way people can find it more easily later.
Jason Briggs Wed 9 Jul 2014
The driver in NIagara for Haystack is really built for options. If you are a Niagara server or a JACE, and you want to bring in other Haystack data you can. Products like Sky Spark, FIN Stack, InferStack, and others can now be brought into NIagara too.
Like Jarmy said I would still use the Niagara Network to go between JACEs, as that's a proprietary driver that Tridium created and has more features.