Hi,

I simulate this case with three stations. One station(Jace) has a point(NumericWritable) with a NumericInterval hisExt in a ModbusTcpNetwork. Another station(SoftJace) discovers history and point through a NiagaraNetwork from that jace station. The third staion(AX) discovers history and point through a NiagaraNetwork from the SoftJace station. I can see the history data from these three stations. And then I add NHaystackService in the AX station, add site and equip, rebuild cache, add haystack slot, everything is ok except the tz and his tag not generated in haystack slot.

I want the AX to be a server from which skyspark can sync point history. but I can't do it without tz and his tags, even if I add them manually.

I ever tried to do the same thing on the SoftJace, and it worked, it did add tz and his tag automatically, and I can sync data to skyspark.

Does the Nhaystack only support pulling data from the two layers of stations architecture? Or some extra things have to be done in three layers of stations architecture?

Thanks Hunter

When you are talking about supervisor levels of the architecture, are you trying to use proxy points in the ComponentSpace or histories in the HistorySpace? Once you get beyond the JACE, I believe your only access to history data is directly from the HistorySpace

NHaystack can actually handle proxy points and proxy histories from the NiagaraNetwork. It will glue them together for you so that the haystack point rec has a his tag.

Hunter, I think there is probably already a way to do what you are asking, but I don't quite understand the architecture you described. It would probably be easier if you just put the NHaystackService on the SoftJace, wouldn't it? Is there some reason you can't do that?

The three layer architecture should work ok, but only if the points on the third station also have corresponding imported histories.

to Brian：

Yeah, I discover histories and points of SoftJace from AX station, and add them to AX's HistorySpace and ComponentSpace. I think these points are proxy points, right? Because each of them has a proxyExt which direct to the point in my Jace station.

to Mike:

I'm sure my skyspark server can talk to AX server, but I'm not sure if there's gonna be a network limitation between skyspark and softjaces. So I just wanna prepare two solutions, and you know, we have six softjaces, each of which connects to 3-4 jace's stations. So it'll be a little easier to talk to 1 AX than 6 softjaces.

Yeah, I do import histories and points from softjace to AX. what I have done on AX is just the same as what I have done on Softjace. Softjace can add those tags corectly(as a two layer architecture), but Ax not(as a three layer architecture).

Thanks Hunter

When you say AX, I assume you mean a web supervisor, correct? And what driver are you using in the web supervisor to talk to the imported points and histories from the soft jaces? NiagaraNetwork, I assume?

Assuming that what I said above is correct, I must admit I have never actually tried what you are attempting to do here -- use the NiagaraNetwork two levels deep such that you have a three-tiered architecture. I feel like it ought to work, but if it doesn't, it might be something I'll need to look into.

Yeah, you're right. it should be a web supervisor, and this web supervisor uses NiagaraNetwork to import points and histories from softjace, and also softjace uses NiagaraNetwork to import points and histories from jace station.

Since this project is used in energy management of an industrial glasswork, which is a little more complicated than in building automation. NHaystack is much better than obix, and I love it, so I hope it will support this three or more-tiered architecture.

Thanks Hunter

I will try to duplicate this issue then, and either fix it if I find that it really doesn't work, or work with you to figure out why your setup is not working properly.

Great and thanks