Newbie PAC questions

1. not sure what the expected messages are
2. OK - it displays OK on t/screen in real time just not PICED
3. Yes

Seems like PICED cant access the system IO as it is not the 'system' controller???

Cheers

Grant

 

You should see messages like:
04/01/2010 11:54:12 AM C-Gate : Rx "# aircon zone_hvac_plant_status //_COM2/254/172 1 0 6 8 0 #sourceunit=7 OID="
04/01/2010 11:54:12 AM C-Bus Rx : HVAC Application : Zone Group 1, Zone 0 Cooling disabled Heating disabled Fan disabled Damper enabled Busy : no Error : no
04/01/2010 11:54:12 AM C-Gate : Rx "# aircon zone_hvac_plant_status //_COM2/254/172 1 1,2,3,4 6 0 0 #sourceunit=7 OID="
04/01/2010 11:54:12 AM C-Bus Rx : HVAC Application : Zone Group 1, Zone 1,2,3,4 Cooling disabled Heating disabled Fan disabled Damper disabled Busy : no Error : no

Do you have the exact same project in the Touch Screen and PICED?

Yes what? Is there valid data displayed? Is it the same as what you are seeing on the touch screen?

It doesn't work that way. The HVAC messages are broadcast to all units.

 

how does this happen then??? (piced is definately connected to c-bus)

might be something that was not picked up...

Cheers

Grant

 

Sorry Grant, but I am not sure what you are asking here. What is it exactly you want to know?

 

Both PICED and the screen grab were taken within the same minute, piced is definately connected to c-bus but yet the status shown is different. Which goes back to an earlier thread

"I have had some instances where i have been using the in-built system IO of HVAC, whilst 'connected' to c-bus these system bits in piced do not accurately (if at all) reflect the status in PICED."..."Might be worth looking into."

Cheers

Grant

 

I have just tried this out myself and can not see any problems.

There are a few things to consider:
1. C-Bus needs to not only be "connected", but also have the C-Bus networks in the OK state.
2. It may take a minute or two after first connecting to C-Bus before all of the HVAC messages are seen. They only get broadcast by the thermostat from time to time. You can also use a "HVAC refresh" Special Function to get the thermostat to broadcast all of its data, but this should happen automatically when the C-Bus Networks first goes into the OK state.
3. Check the HVAC manager to see what data is displayed there (you never told us whether this shows the right data or not).
4. If you aren't seeing the data in the HVAC manager, look in the C-Bus log to see whether any messages are being received.
5. If the data is correct in the HVAC Manager, but not on the components, check that the component properties (particularly the zones selected) are correct.

The source code for PICED and HomeGate (in Colour C-Touch) is mostly the same, so if one works, the other should work. The main difference is in the way they connect to C-Bus. This is a potential source of bugs, but has been tested very thoroughly for the HVAC features.

 

Now with latest PICED 4.8.0, Change #18129 Updates to Power Failure Recovery it is stated for PAC that all the GA's levels are stored on the PAC for power failure recovery.

Will this affect the 1000 cycles? Is this saved at GA change/every minute/ every hour?

 

I'm not sure how you're drawing the conclusion that because of #18129 that all GA's levels are stored on the PAC for power failure recovery.

From the PICED help file:
"Note that the C-Touch / PAC unit itself will recover the level of all Group Addresses it uses automatically."

From the "What's New" in PICED:

18129 Updates to Power Failure Recovery:

• Store graph data
• Store power meter data
• Monitored Groups now saved in project file
• Don't save PFR file for templates

The storing of GA levels is not related to the 1000 write limitation as a different memory device is used for storing those parameters.

 

From the Help file. Okay, I might have left out the words it uses. Thanks Newman.

Good. When does PAC actually save the GA level, at level change?

 

Levels get written at the moment the PAC detects that a power failure has occurred.

 

Thanks for answering my many questions.