.comment-link {margin-left:.6em;}

Wednesday, February 22, 2006

 

Distech FCU controller in Tridium

Tridium Niagara version: r2.301.515
Lonworks Jar file version: lonworks-2.301.515f.v1
Distech Jar file version: lonDistech10-2.301.515a.v1/ lonDistech-2.305.515q.v1/ lonDistechWizards-2.304.515.v106

I like Distech Free programmable controller. It's very flexible in terms of working with Tridium, although it can only be programmed in a LNS plug-in. This is the first time I play with its FCU Lonmark controller and program it in Tridium.

Distech provides a wizard for the user to config the fan coil Lonmark controller. The first page allows you to choose the measurement system, "metric" or "Imperial". It gives some people convenience as well as an annoying bug.

It's about the temperature. Besides "metric" or "Imperial", user can choose "fahrenheit" or "celsius" in the properties of Lonworks service. And it looks like when "fahrenheit" + "Imperial", the temperature reading is 32F lower than the actual measurement. This 32F will be put in "offset" to make a temperature input work.

The other issue occurs when a typical controller shadow object is duplicated. The new shadow object will not inherit all the original configurations. The SNVT type of all hardware inputs will ignore all the changes and keep in SNVT_TEMP_F (It's a changable NVO), even when these NVOs are linked to other objecgts. So, you will not be happy if there are 100 controllers to be duplicated.

Distech Jar files had a recent upgrade (lonDistech10-2.301.515a.v1/ lonDistech-2.305.515s.v1/ lonDistechWizards-2.304.515.v110). And I have not tested to see if these bugs are fixed.

This page is powered by Blogger. Isn't yours?