Having a problem with some bindings in Lonmaker!

[smokies]

We are doing a job where are using some TAC 102AX (VAV controller) and TAC STR350 (Lon communicating Tstats). We bind the spacetemp and setpoint from the STR350 to the 102AX. Piece of cake - at first. We did about 12 then started having a problem. The next set of units we did the nvosetpoint is 72 from the STR350 but the nvisetpoint is reading invalid 621.86. The spacetemp binding still works. The first 12 are fine -setpoint and spacetemp.

Any ideas.

Thanks in advance.

[dapper]

How are the 'heartbeats' (MinSendTime) set? If you are 'sending on delta' that could be a problem. Try raising the setpoint at the stat and see if the nvi changes. I'm not familiar with TAC but these are general config properties.

[crab master]

Let us know if that helps. I've used numerous STR 350's and 102AX's but I don't think I've ever bound the two. Just curious why did you use the STR-350 instead of the 250? Also what bindings are you using in lonmaker (default, repeated, ...) and did you vary your send/recieve times on both the 102AX's and the 350's?

[smokies]

Crabmaster - The specs required a communication port for a laptop on the tstat. They would not except the M/Stat port. They were able to get the biddings working - not sure what was changed. I'm waiting for the details.

Thanks for the help.

[lonboy]

Smokie,
Have you connected a protocol analyzer to verify that the LonStat is sending the temperature NV? Also, check your bandwidth to make sure it's not a saturated channel.
lb

[smokies]

Lonboy-
We have not. TAC mentioned the same. We are going to purchase one - debating on the echelon or loytec.

Anyone have a preference on the protocal analyzers echelon or loytec?

Thanks

[sysint]

I like the Loytec better ---- I have both