Ronnie,
Intesis is listening and has tried several times to resolve the issue.
Back to your shortly.
Regards
Ken Smyers
All,
I’ve tried my best to figure out what setpoint is controlling the Daikin unit via the IntesisBox. It seems that I’m getting no help from IntesisBox factory support. Why? It take days between answers. I still have no answer from the last email.
If anyone is listening, I thought the problem may be that the iTouch manager set to “Master.” We set it to “Slave” yesterday. No change. This morning, I logged into the system and it still was doing its own thing again. The point that is in control is most definitely “Setpoint_command.” That is the setpoint that the unit is maintaining. Every time I log in – no matter occupied or unoccupied – it is maintaining the Setpoint_command value. Why?
Furthermore, yesterday, I saw the Setpoint_status change to the unoccupied value. This was the first time I ever saw it do that – probably due to making the iTouch a “Slave” – is my estimation. That lasted 30 minutes and then the Setpoint_status reverted back to the Setpoint_command value? Why???
How do I take the Setpoint_command out of service where the unit will operate at the normal occupied and unoccupied setpoints? I tried taking it “Out of Service” but I received an error when trying to write to that.
Ronnie Rice
Controls Group Service Manager
Josep,
I verified all the UnoccupiedDeadandAction points were set to OFF. Below, I have a pic of all the points pulled in from the IntesisBox.
Here are the fan status’s at the same time I took the pic of the points from the Intesisbox. 3 of the units the fans were running, yet the zone temperature is above the unoccupied heating setpoint.
[/uploads/default/original/2X/f/f56e96da9a689c04ba089637b9cb85f5b0130e88.jpeg]
[/uploads/default/original/2X/4/48c61b11675d3f67db5312919c5c45fff55ea4d5.jpeg]
[/uploads/default/original/2X/d/de9f428e505279cf61426d76fc3402e5fa6df6db.jpeg]
[/uploads/default/original/2X/f/f3ccb4f7661cca8ecb4fe5a435305bd99bb35484.jpeg]
[/uploads/default/original/2X/6/6288453a00bafefcb029d7b36e74323f847cd10e.jpeg]
Ronnie Rice
Controls Group Service Manager
Hello Ronnie,
There is the object UnoccupiedDeadbandAction, to control if you want the unit to switch off by itself when room temp within bounds.
Now, what I don’t make sense here is of the setpoint going to that particular value, which is not UCS or UHS. It means that this value comes from either any change on the unit from local panel, or from direct control of cmd setpoint in our device - this object always overrides any automated setpoint that would come from occupancy/unoccupancy functionality.
Josep Jorba
Technical Support Team / IntesisBox
– end_issue_response
Ken,
I have not heard a response to the last question posed about the IntesisBox not controlling to unoccupied setpoints.
Ronnie Rice
Controls Group Service Manager
Josep Jorba
Technical Support Team / IntesisBoxINTESIS SOFTWARE, SL - www.intesis.comhttp://www.intesis.comhttp://www.intesis.com/
Phone: +34/938047134 (SPAIN)Josep,
Please read Ronnie’s comments and advise.
Regards,
Ken Smyers
---------- Forwarded message ---------
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com