Proliphix Driver Support

Forum to discuss HVAC (Heating, Ventilation and Cooling) related hardware support.
jespeed
New Member
New Member
Posts: 47
Joined: Mon Sep 18, 2006 11:45 pm
Contact:

Proliphix Driver Support

Postby jespeed » Mon Jan 04, 2010 10:02 am

Hello all,

Happy new year!!

I recently installed two Proliphix NT20-E thermostats and I am using the latest MLServer, Proliphix driver and the thermostat plugin. When looking at the State data there are some strange status indications that make no sense to me. These are :

Fan State : When the fan is in Auto and off it always says "initializing". When the system actually turns on the Fan State indicates "Off".
Fan Mode : This seems to always indicate "On" when the fan is in auto and it does not seem to matter if the fan is actually running or not.
HVAC State : This seems to work partially. When the system is in heat mode and off it does indicate off. When the system is in heat mode and running it indicates "Heat". But when the system is in heat mode and the system comes on and then turns on the Aux Heater strips the HVAC State indicates "Cool".
Setpoint State : This seems to always indicate "Hold" when the system is actually following the programmed schedules.

I currently use the remote web interface with these thermostats and it indicates all of the status items correctly.

Is there any way to integrate the equipment run times that are available in the remote web interface into the MLServer plugins. These run time values are very useful in monitoring equipment performance.

Please let me know if these items can be fixed and whether or not I can expect any support or updates to this driver that I just purchased. With the current state of the driver and plugin it will be difficult to accurately display the HVAC system status on my MainLobby screens.

Thank you for any help or information you can provide.

Jim Spence
Take care,

Jim Spence

jespeed
New Member
New Member
Posts: 47
Joined: Mon Sep 18, 2006 11:45 pm
Contact:

Re: Proliphix Driver Support

Postby jespeed » Mon Jan 04, 2010 4:01 pm

Hello All,

I have some more information that could help the Proliphix driver developers.

There is a yahoo users group for this thermostat and they have developed an excel spreadsheet that will grab all of the thermostat data at an interval specified by the user. It will also automatically graph the temperature data for trending purposes. The reason I bring this up is that they have managed to get all of the data correct and with the correct states. This might prove helpful in getting the Proliphix driver state data correct.

Let me know if you need more information so we can get this driver corrected for the people who have purchased it.

Take care,

Jim Spence
Take care,



Jim Spence

jespeed
New Member
New Member
Posts: 47
Joined: Mon Sep 18, 2006 11:45 pm
Contact:

Re: Proliphix Driver Support

Postby jespeed » Thu Jan 21, 2010 7:42 pm

Hello All,


I just wanted to let everyone know that Dave went above and beyond to help me get this driver working correctly.

Thank you Dave and thank you cinemar.


Take care,

Jim Spence
Take care,



Jim Spence

User avatar
CinemarDave
Site Admin
Site Admin
Posts: 10535
Joined: Fri Feb 07, 2003 8:56 am
Location: Planet Earth
Contact:

Re: Proliphix Driver Support

Postby CinemarDave » Thu Jan 21, 2010 9:07 pm

I just wanted all users of the Proliphix driver for MLThermostat to know that a new version of the plugin is available for immediate download. You should download and install the latest 3.0.x versions of the MLThermostat family plugin and Proliphix driver.

This version fixes numerous issues with external sensors, fan and hvac controls. New server variables are also available for tracking heat and cool usage and thermostat uptime.

MurrayW
Is there life beyond Cinemar?
Is there life beyond Cinemar?
Posts: 1198
Joined: Sun Mar 07, 2004 1:05 pm
Location: Austin, TX
Contact:

Re: Proliphix Driver Support

Postby MurrayW » Fri Jan 22, 2010 1:34 am

CinemarDave wrote:I just wanted all users of the Proliphix driver for MLThermostat to know that a new version of the plugin is available for immediate download. You should download and install the latest 3.0.x versions of the MLThermostat family plugin and Proliphix driver.

This version fixes numerous issues with external sensors, fan and hvac controls. New server variables are also available for tracking heat and cool usage and thermostat uptime.

Any chance of getting setback server variables?
You do not have the required permissions to view the files attached to this post.

User avatar
CinemarDave
Site Admin
Site Admin
Posts: 10535
Joined: Fri Feb 07, 2003 8:56 am
Location: Planet Earth
Contact:

Re: Proliphix Driver Support

Postby CinemarDave » Fri Jan 22, 2010 12:43 pm

Version 3.0.24 of the driver adds the SetBack variables. You'll have to test and report back if it is working or not. I do not have local thermostats to test with.

MurrayW
Is there life beyond Cinemar?
Is there life beyond Cinemar?
Posts: 1198
Joined: Sun Mar 07, 2004 1:05 pm
Location: Austin, TX
Contact:

Re: Proliphix Driver Support

Postby MurrayW » Fri Jan 22, 2010 1:29 pm

CinemarDave wrote:Version 3.0.24 of the driver adds the SetBack variables. You'll have to test and report back if it is working or not. I do not have local thermostats to test with.
Dave, That's GREAT news!!! =D>

I'll check it out tonight when I get home. This will make it much easier for me to compare the actual setpoint to what it is supposed to be and take action to automatically set it back to the correct level if someone jacks the heat up or AC down too much.

thanks,
Murray

MurrayW
Is there life beyond Cinemar?
Is there life beyond Cinemar?
Posts: 1198
Joined: Sun Mar 07, 2004 1:05 pm
Location: Austin, TX
Contact:

Re: Proliphix Driver Support

Postby MurrayW » Fri Jan 22, 2010 8:25 pm

Dave,
It looks like it is creating all the variables for the setbacks. However, the event log shows errors being logged 5 times per second.
You do not have the required permissions to view the files attached to this post.

MurrayW
Is there life beyond Cinemar?
Is there life beyond Cinemar?
Posts: 1198
Joined: Sun Mar 07, 2004 1:05 pm
Location: Austin, TX
Contact:

Re: Proliphix Driver Support

Postby MurrayW » Fri Jan 22, 2010 8:55 pm

MurrayW wrote:Dave,
It looks like it is creating all the variables for the setbacks. However, the event log shows errors being logged 5 times per second.

It is fixed now -- no more erros in the event log. When I was initially adding the thermostats into the plugin (I had to redo this after updating to the new version) MLServer crashed. When I started it back up, I wasn't able to access Thermostat1 settings. When I right clicked (or chose settings from the menu) the only thing that would happen is that thermostat1 would no longer be highlighted. One of these two things fixed it.

1. I opened the proliphix.mdb file in access and noticed that the isNT10e field was different on thermostat1 than on thermostat2. I changed thermostat1 to match thermostat2.

2. When I tried to reopen MLServer, it would not open. I used task manager and saw that there was an active mlserver process, so I closed it via task manager, then it re-opened normally.

I have one more request while you are working on the plugin. Can we get a command to change the contrast on the display? SEe my previous post here: http://forum.cinemaronline.com/viewtopic.php?f=123&t=15196

thanks,
Murray

User avatar
CinemarDave
Site Admin
Site Admin
Posts: 10535
Joined: Fri Feb 07, 2003 8:56 am
Location: Planet Earth
Contact:

Re: Proliphix Driver Support

Postby CinemarDave » Fri Jan 22, 2010 9:39 pm

Version 3.0.25 fixes the event log message permanently.

I cannot find anything in the API documentation that tells me how to dim the display. Can you tell what the OID commands are by looking at the web interface?

MurrayW
Is there life beyond Cinemar?
Is there life beyond Cinemar?
Posts: 1198
Joined: Sun Mar 07, 2004 1:05 pm
Location: Austin, TX
Contact:

Re: Proliphix Driver Support

Postby MurrayW » Sat Jan 23, 2010 12:59 am

CinemarDave wrote:Version 3.0.25 fixes the event log message permanently.

I cannot find anything in the API documentation that tells me how to dim the display. Can you tell what the OID commands are by looking at the web interface?
I am not sure what I am looking for. I "viewed the source" when looking at the web page and these are some of the lines in/after the contrast section:

Code: Select all

n = "OID2.2.3"
v = parseInt("40");
printFSC("Display Contrast", v, makeSelect(n,null))
var el = document.settings.elements[n]
var zindex=0;
for (var x=20; x <= 40; x+=2)
el.options[zindex++] = new Option(x,x,(x)==v,(x)==v)

el.value = v


I have attached the entire webpage as a txt file in case that helps. I'll send you an email with my logon information for the proliphix site that you can use to access the remote web interface for my thermostats.

Let me know if there is anything else from my end I can do to help you with this.

thanks,
Murray
You do not have the required permissions to view the files attached to this post.

User avatar
mcascio
Founder
Founder
Posts: 8270
Joined: Tue Jan 28, 2003 4:03 pm
Location: Kenosha, Wi
Contact:

Re: Proliphix Driver Support

Postby mcascio » Tue Feb 02, 2010 9:28 pm

Murray,

Have all your Proliphix bug issues been resolved?
Mario Cascio
Cinemar, Inc.
http://www.cinemaronline.com

MurrayW
Is there life beyond Cinemar?
Is there life beyond Cinemar?
Posts: 1198
Joined: Sun Mar 07, 2004 1:05 pm
Location: Austin, TX
Contact:

Re: Proliphix Driver Support

Postby MurrayW » Tue Feb 02, 2010 9:58 pm

mcascio wrote:Murray,

Have all your Proliphix bug issues been resolved?
Dave and I traded emails back and forth. The new variables will help a lot. There was just one problem with setting the contrast level. I could do it with an MLCommand (using “SetContrast~<<contrast>>” Where contrast is a value between 20 and 40) but not from within the plugin. After adjusting the contrast, I found that it might not be that useful. I guess what I was really interested in doing was adjusting the back lighting which you can't do on these thermostats. Here's the last email I sent him:

Hi Dave,

3.0.26 works for contrast when sent from the command line. In fact, you can set the contrast to numbers outside of 20- 40. I went as low as 0 and as high as 100. This isn’t actually going to be as useful as I thought. It looks like the backlight (green) stays at the same level and it is just text (black) that is affected by the contrast setting. I’ll probably use it anyway, just because “I can”.

I wasn’t able to change the contrast from within the plugin. No matter what level between 20 and 40 I selected, nothing happened. When I looked at the log file, there was no indication that the command was sent or received either like I see if I change the Heat or Cool point from within the plugin.
You do not have the required permissions to view the files attached to this post.

User avatar
mcascio
Founder
Founder
Posts: 8270
Joined: Tue Jan 28, 2003 4:03 pm
Location: Kenosha, Wi
Contact:

Re: Proliphix Driver Support

Postby mcascio » Tue Feb 02, 2010 10:11 pm

Murray,

So aside from an issue with adjusting the contrast on the lcd :) - you can actually control and view all the important variables?
Mario Cascio

Cinemar, Inc.

http://www.cinemaronline.com

MurrayW
Is there life beyond Cinemar?
Is there life beyond Cinemar?
Posts: 1198
Joined: Sun Mar 07, 2004 1:05 pm
Location: Austin, TX
Contact:

Re: Proliphix Driver Support

Postby MurrayW » Tue Feb 02, 2010 10:59 pm

mcascio wrote:Murray,

So aside from an issue with adjusting the contrast on the lcd :) - you can actually control and view all the important variables?
76 variables per thermostat...Now I need to set my automation rules to not allow drastic temperature changes like I have been posting about for a couple of months! :oops: Here are the variables:

    mlthermostat_1_active_period = Evening
    mlthermostat_1_avg_temp_act = 71.0
    mlthermostat_1_avg_temp_rnd = 71
    mlthermostat_1_cool_point_act = 75.0
    mlthermostat_1_cool_point_rnd = 75
    mlthermostat_1_cool_setback_away_1 = 82
    mlthermostat_1_cool_setback_away_2 = 82
    mlthermostat_1_cool_setback_away_3 = 82
    mlthermostat_1_cool_setback_away_4 = 82
    mlthermostat_1_cool_setback_in_1 = 77
    mlthermostat_1_cool_setback_in_2 = 76
    mlthermostat_1_cool_setback_in_3 = 75
    mlthermostat_1_cool_setback_in_4 = 80
    mlthermostat_1_cool_setback_out_1 = 75
    mlthermostat_1_cool_setback_out_2 = 82
    mlthermostat_1_cool_setback_out_3 = 75
    mlthermostat_1_cool_setback_out_4 = 80
    mlthermostat_1_cool2usage = 0
    mlthermostat_1_current_class = Unoccupied
    mlthermostat_1_current_period = Evening
    mlthermostat_1_displaycontrast = 40
    mlthermostat_1_fan_mode = Auto
    mlthermostat_1_fan_setback_away_1 = Disabled
    mlthermostat_1_fan_setback_away_2 = Disabled
    mlthermostat_1_fan_setback_away_3 = Disabled
    mlthermostat_1_fan_setback_away_4 = Disabled
    mlthermostat_1_fan_setback_in_1 = Disabled
    mlthermostat_1_fan_setback_in_2 = Disabled
    mlthermostat_1_fan_setback_in_3 = Disabled
    mlthermostat_1_fan_setback_in_4 = Disabled
    mlthermostat_1_fan_setback_out_1 = Disabled
    mlthermostat_1_fan_setback_out_2 = Disabled
    mlthermostat_1_fan_setback_out_3 = Disabled
    mlthermostat_1_fan_setback_out_4 = Disabled
    mlthermostat_1_fan_state = Off
    mlthermostat_1_fanusage = 2198
    mlthermostat_1_filter_alarm = No Alarm
    mlthermostat_1_heat_point_act = 71.0
    mlthermostat_1_heat_point_rnd = 71
    mlthermostat_1_heat_setback_away_1 = 60
    mlthermostat_1_heat_setback_away_2 = 60
    mlthermostat_1_heat_setback_away_3 = 60
    mlthermostat_1_heat_setback_away_4 = 60
    mlthermostat_1_heat_setback_in_1 = 71
    mlthermostat_1_heat_setback_in_2 = 67
    mlthermostat_1_heat_setback_in_3 = 71
    mlthermostat_1_heat_setback_in_4 = 60
    mlthermostat_1_heat_setback_out_1 = 71
    mlthermostat_1_heat_setback_out_2 = 60
    mlthermostat_1_heat_setback_out_3 = 71
    mlthermostat_1_heat_setback_out_4 = 60
    mlthermostat_1_heat1usage = 14463
    mlthermostat_1_heat2usage = 0
    mlthermostat_1_high_temp_alarm = No Alarm
    mlthermostat_1_hvac_mode = Heat
    mlthermostat_1_hvac_state = Off
    mlthermostat_1_low_temp_alarm = No Alarm
    mlthermostat_1_relative_humidity = 0 %
    mlthermostat_1_set_point_state = Normal
    mlthermostat_1_setback_start_away_1 = 6:00 am
    mlthermostat_1_setback_start_away_2 = 8:00 am
    mlthermostat_1_setback_start_away_3 = 5:00 pm
    mlthermostat_1_setback_start_away_4 = 10:00 pm
    mlthermostat_1_setback_start_in_1 = 7:30 am
    mlthermostat_1_setback_start_in_2 = 10:00 am
    mlthermostat_1_setback_start_in_3 = 6:00 pm
    mlthermostat_1_setback_start_in_4 = 11:45 pm
    mlthermostat_1_setback_start_out_1 = 6:00 am
    mlthermostat_1_setback_start_out_2 = 8:30 am
    mlthermostat_1_setback_start_out_3 = 4:30 pm
    mlthermostat_1_setback_start_out_4 = 11:45 pm
    mlthermostat_1_systemtime = 3/7/2050 7:34:04 PM
    mlthermostat_1_temp_display = Farenheit
    mlthermostat_1_uptime = 248:20:22
    mlthermostat_1_zone_temp_act = 71.0
    mlthermostat_1_zone_temp_rnd = 71
    mlthermostat_2_active_period = Evening
    mlthermostat_2_avg_temp_act = 73.1
    mlthermostat_2_avg_temp_rnd = 73
    mlthermostat_2_cool_point_act = 77.0
    mlthermostat_2_cool_point_rnd = 77
    mlthermostat_2_cool_setback_away_1 = 82
    mlthermostat_2_cool_setback_away_2 = 82
    mlthermostat_2_cool_setback_away_3 = 82
    mlthermostat_2_cool_setback_away_4 = 82
    mlthermostat_2_cool_setback_in_1 = 75
    mlthermostat_2_cool_setback_in_2 = 78
    mlthermostat_2_cool_setback_in_3 = 77
    mlthermostat_2_cool_setback_in_4 = 76
    mlthermostat_2_cool_setback_out_1 = 75
    mlthermostat_2_cool_setback_out_2 = 84
    mlthermostat_2_cool_setback_out_3 = 77
    mlthermostat_2_cool_setback_out_4 = 76
    mlthermostat_2_cool2usage = 0
    mlthermostat_2_current_class = Unoccupied
    mlthermostat_2_current_period = Evening
    mlthermostat_2_displaycontrast = 40
    mlthermostat_2_fan_mode = Auto
    mlthermostat_2_fan_setback_away_1 = Disabled
    mlthermostat_2_fan_setback_away_2 = Disabled
    mlthermostat_2_fan_setback_away_3 = Disabled
    mlthermostat_2_fan_setback_away_4 = Disabled
    mlthermostat_2_fan_setback_in_1 = Disabled
    mlthermostat_2_fan_setback_in_2 = Disabled
    mlthermostat_2_fan_setback_in_3 = Disabled
    mlthermostat_2_fan_setback_in_4 = Disabled
    mlthermostat_2_fan_setback_out_1 = Disabled
    mlthermostat_2_fan_setback_out_2 = Disabled
    mlthermostat_2_fan_setback_out_3 = Disabled
    mlthermostat_2_fan_setback_out_4 = Disabled
    mlthermostat_2_fan_state = Off
    mlthermostat_2_fanusage = 270
    mlthermostat_2_filter_alarm = No Alarm
    mlthermostat_2_heat_point_act = 70.0
    mlthermostat_2_heat_point_rnd = 70
    mlthermostat_2_heat_setback_away_1 = 60
    mlthermostat_2_heat_setback_away_2 = 60
    mlthermostat_2_heat_setback_away_3 = 60
    mlthermostat_2_heat_setback_away_4 = 60
    mlthermostat_2_heat_setback_in_1 = 71
    mlthermostat_2_heat_setback_in_2 = 66
    mlthermostat_2_heat_setback_in_3 = 72
    mlthermostat_2_heat_setback_in_4 = 68
    mlthermostat_2_heat_setback_out_1 = 71
    mlthermostat_2_heat_setback_out_2 = 60
    mlthermostat_2_heat_setback_out_3 = 70
    mlthermostat_2_heat_setback_out_4 = 68
    mlthermostat_2_heat1usage = 2979
    mlthermostat_2_heat2usage = 80
    mlthermostat_2_high_temp_alarm = No Alarm
    mlthermostat_2_hvac_mode = Auto
    mlthermostat_2_hvac_state = Off
    mlthermostat_2_low_temp_alarm = No Alarm
    mlthermostat_2_relative_humidity = 0 %
    mlthermostat_2_set_point_state = Normal
    mlthermostat_2_setback_start_away_1 = 6:00 am
    mlthermostat_2_setback_start_away_2 = 8:00 am
    mlthermostat_2_setback_start_away_3 = 5:00 pm
    mlthermostat_2_setback_start_away_4 = 10:00 pm
    mlthermostat_2_setback_start_in_1 = 9:00 am
    mlthermostat_2_setback_start_in_2 = 10:00 am
    mlthermostat_2_setback_start_in_3 = 9:00 pm
    mlthermostat_2_setback_start_in_4 = 11:45 pm
    mlthermostat_2_setback_start_out_1 = 6:00 am
    mlthermostat_2_setback_start_out_2 = 8:30 am
    mlthermostat_2_setback_start_out_3 = 5:00 pm
    mlthermostat_2_setback_start_out_4 = 11:45 pm
    mlthermostat_2_systemtime = 3/7/2050 7:31:27 PM
    mlthermostat_2_temp_display = Farenheit
    mlthermostat_2_uptime = 248:20:20
    mlthermostat_2_zone_temp_act = 73.1
    mlthermostat_2_zone_temp_rnd = 73


Return to “HVAC Support”

Who is online

Users browsing this forum: No registered users and 1 guest