Tracker BMTK does not communicate to ZN510s/ZN511s

Issue:

Tracker BMTK does not communicate to ZN510s/ZN511s

Resolution:

 

Tracer ZN510/ZN511 controller data will not display if the ZN510/ZN511 is not configured correctly or if the ZN510/ZN511 has software prior to version 2.04. The software version can be viewed in Rover on the general tab in the self-documentation string.

The Tracer ZN510/ZN511 controller must be configured with the unit type set to heat pump. The setup can be confirmed with the Rover service tool and is found on the unit tab under the configuration button. The Tracker controller will not recognize a ZN510/ZN511 configured as blower coil or 1 heat/1 cool.

All versions of the Tracer ZN510 controller configured as heat pumps will communicate with Tracker. However, screens at both the Tracker PC workstation and the Tracker controller are optimized for ZN510 software versions 2.04 or greater. On older board versions, some data may not be available for display as expected. This is not a defect and must be considered when adding Tracker controllers to existing systems. It may be necessary to physically upgrade the ZN510 boards to meet performance expectations. Examples of data not displayed include cooling, heat, preheat and economizer type as well as heat output.

 

 

 

 

 

Tracker needs ZN510/ZN511s configured as WSHPs to discover them. The IMAX Imports job inTulsahad ZN511s configured as 1heat/1cool fan coils. Although Trackers communicated to all the ZN511s, Trackers can not discover them unless they were originally configured as WSHP units. Once discovered, the connected ZN511s were reconfigured using Rover as fan coil 1heat/1cool devices. Tracker then continued to communicate to the reconfigured ZN511s. If someone reset the Tracker to factory defaults, for example a Tracker upgrade upgrade will force a rediscovery of the Comm5 link and the ZN511s (now configured as fan coils) would not display.The techs at theTulsasite upgraded the CCP and Tracker because of a nuisance diagnostic reported from a Reliatel controlled RTU to the Tracker. 

The workaround necessary to talk to ZN511s configured as fan coils (1heat/1cool) was:

1  Backup Tracker DB and reimage Tracker to newest image.

2 - Reconfigure all ZN511s on the Comm5 link to WSHP configurations using Rover

3  Reset Tracker to its factory defaults and rediscover the Comm5 link.

4  Once all Comm5 devices display at Tracker, reconfigure ZN511s as Fan. Coil 1heat/1cool configurations using Rover.

5  Restore DB to Tracker.

 

Notes:

Changes:

Other Question/Problem/Cause Statements:

• Tracker 24 upgraded to latest version (SP3). ZN511s cannot talk and is not recognized by Tracker
• ZN510 / ZN511 does not talk to tracker
• 1H1C Zn510 / Zn511 does not communicate to tracker
• Tracker does not control Zn510 /Zn511
• WSHP Tracker and Zn510 / Zn511

Facts:

• TRACKER BMTK - ZN510/ZN511s must be configured as WSHPs to communicate with Trackers
• Tracer ZN510/511

Original wave: wave3373