Building Automation Knowledge Base

Issue Contact info for Schneider Electric Buildings Business Order Entry in the UK Environment Purchasing UK Price and Delivery information Cause For all questions from end users, pricing and delivery information. Resolution UK CCC in Telford: Phone 0870 608 8608 Email OrderEntry.UK@Schneider-Electric.com

Issue Does the ENC maximum number of LON bindings recommendation also apply to the JACE-6, JACE-6E, and JACE-7 platforms as well?  The recommendation is not to exceed a total of 1200 bindings on the FTT-10 bus. Environment I/A Series G3, ENC and JACE controllers Cause LonWorks FTT-10 bus operation Resolution The number of bindings on an FTT-10 bus does not change regardless of the platform (e.g. ENC vs. JACE-6/7). The number of LON devices and overall number of bindings is somewhat arbitrary as the actual number is related to bandwidth limitations of the 78K FTT-10 bus.  The 1200 binding number is a general rule of thumb. This is the statement from an R2 engineering note that summarizes the basic issue. --- A JACE controller provides a LonWorks FTT-10 port. Electrically, an FTT-10 segment supports up to 63 total nodes (addressable devices). Using repeater(s), a single LonWorks subnet can span multiple segments and have a total of 127 nodes.  However, in almost all cases, it is unrealistic to think that a JACE controller can “fully support” anywhere near 126 devices, because of bandwidth limitations.  The 78K baud FTT-10 bus can easily become “saturated” with too many messages (as a result of bindings). Generally, most LON installations reach network saturation at around 1200 bindings (with average messaging). This can easily occur with far fewer than 126 devices. If connections are set to “poll-only," then the network could be sized to agree with the resource count limit of the JACE.  However, this configuration puts the JACE in the same category as most other LON interfaces, which poll for values (making for slow updates). --- In summary, the actual number of bindings directly correlates to bandwidth, tuning, and acceptable data update rates.  An FTT-10 network can exhibit high bandwidth with less bindings or can be successfully operated at a higher number of bindings.  A good rule of thumb is that the average sustained bandwidth on the bus (as measured with a Lon Protocol Analyzer) should not exceed 25 to 28%.  This allows for message bursts to be successfully processed when needed.  In addition, care must be used when targeting a particular LON node with messages as the Neuron or host processor may not be able to process incoming messages causing lost and missed messages.  This includes the ENC or JACE which is why tuning of the individual LON devices is very important. One alternative is to install two FTT-10 LON cards in the JACE-6E or JACE-7 and run two trunks. The LON network interfaces are configured as LON1 and LON2.  Purchase two cards and one driver. Remember to not overload the JACE (e.g. maintain good CPU and memory usage) which is good practice regardless of the communication interface.

Issue In a Niagara R2 / DMS integration, some points in the station are not updating.  Some points were deleted in the DMS panel. Environment Niagara R2 (all versions) DMS (all versions) Cause Controllers were deleted and DMS points were no longer required.  As a housekeeping step, they were deleted. Resolution Anytime DMS points are deleted, added, re-ordered or the DMS database is downloaded via OPRIF, 're-learn' the DMS panel from the R2 station. Right-click a DMS container, select Go > PointListManager. Click the GetPointListFromDevice button. The above steps will upload the current DMS database into the station.  The steps will NOT affect existing objects under the specific DMS container. For more information, read the I/A Series Niagara DMS Serial Driver Engineering Guide (F-27071).  Specifically, read the section titled 'Re-learning The DMS Panel'.

Issue A point in a MicroSmart controller is receiving its input value from the global broadcast table and it's fluctuating every few seconds by roughly 20 degrees. Environment DMS Niagara R2 Niagara G3 Cause Two MicroSmart points are broadcasting on the same global channel.  The two points can be from the same controller or from different controllers on the bus.  One is broadcasting a value around 50°F and the other around 70°F.  This is causing the 20 degree fluctuation every few seconds. Resolution The two points must be identified and then given unique broadcast channel numbers.  This will prevent the fluctuation. The global table will identify one point but not the other one.  The process of manually checking each controller's global table and points database may be required.  The point configuration screen will identify the broadcast channel assigned.  Once the duplicate is found, assign it an unused channel number.

Issue An owner customer has purchased a non-expiring copy of WorkPlace Tech.  It is installed on a 64-bit Windows 7 computer within the XP 'mode' virtual machine.  Can it be copied to other Windows 7 computers and work or does the WorkPlace Tech license prevent it from working? Environment Windows 7 WorkPlace Tech 5 Cause Loss of potential sales Resolution WorkPlace Tech licensing is not designed to identify a virtual 'hard drive' from an actual hard drive.  As a result, an installed copy of WorkPlace Tech will work in the virtual machine no matter how many Windows 7 computers into which it is installed.

Issue Purchasing a MNL-13RF controller in the UK. Environment Purchasing Sales Micronet I/A series Cause Part number not recognized. Resolution The ordering system does not recognize MNL-13FRx which is shown in a lot of documentation. The required part number is MNL-13RF3, where 3 is the current version number.

Issue Cannot open history in the station, error  as follows: ERROR [13:02:33 25-Apr-13 PDT][sys.service] Service start failed: History Service java.lang.IllegalArgumentException: duplicate name history    at javax.baja.nav.BNavContainer.addNavChild(BNavContainer.java)    at javax.baja.naming.BHost.addNavChild(BHost.java)    at javax.baja.history.BHistoryService.initDataRecoverySource(BHistoryService.java) .................. Environment I/A Series G3 station Cause Duplicate name of history. Resolution Using Workbench: Connect to the station and go to the property sheet view of the root config of the station. Hit ctrl + L, which opens the current ord dialog Paste in the below text to the end of the current ord. |bql:select slotPath,name from history:HistoryService It should display a table and show the slot path of each of the history service components. Locate and delete the extra service.

Issue The STR800 sensor is a replacement for the TSMN-57011-850.  What is the thermistor's accuracy?  The datasheet (F-27739) does not provide this information. Environment Temperature sensors Cause Missing data in the spec sheet Resolution Sensing Element:  Thermistor resistance, 10,000 ohms at 77°F (25°C) shunted with an 11K ohms 0.1% resistor. Within operating temperature limits of 32 to 158°F (0 to 70°C): Error ±0.36°F (0.2°C) maximum Drift/Year 0.045°F (0.025°C) maximum Over Operating Temperature Limits: Error ±0.76°F (0.42°C) maximum Drift/Year 0.09°F (0.05°C) maximum

Issue Import/ Export functions of Tree Tech 3.2 on Windows XP SP3 were disabled by recent Microsoft update. No .GDF file exported, no error message displayed. Environment Tree Tech revision 3.2 installed on Windows XP SP3 computer Cause Believed to have been caused by a recent Microsoft update.  Resolution There are two work-around options: Run Tree Tech 3.2 on Windows 7 , 32-bit machine If the project database is backed up from the Windows XP computer, it can be reloaded on the Windows 7 computer. The project database path on the Windows XP computer is: c:\Documents and Settings\All Users\Schneider Electric\TreeTech\Jobs\Projects\  On a Windows 7 computer, the file path for the TreeTech database is c:\Program Data\Schneider Electric\TreeTech\Jobs\Projects\    Un-install Tree Tech 3.2, install Tree Tech 3.1 on Win XP SP3 machine if no Win 7 machine available. Tree Tech 3.1.exe is available on The Exchange Download Center Run the WIBs purchase, generate license request for IV-DEMO-CDE, send file to us to create a license. OK to export GCM database already uploaded in 3.2 

Issue Unable to Login into Webpage after java update 7_21 Environment R2, G3 Cause Java's latest update  7_21 (and later) includes a new option to keep temporary internet files.  This is creating issues with the user login and with displaying some graphics. Resolution A.  Configure Java so that it does not cache the applet files. Go to Windows Control Panel (\via the Start menu Open Java Console General tab --  Temporary Internet Files Click [Settings] Uncheck "Keep temporary files on my computer" Click [Delete Files] Check  "Cached Applications and Applets" then click [OK] Close Java Console B. Clear the browser's cache. Clear the temporary internet files, cookies and history. NOTE: Each browser is cleared differently. Use the browser's help for information on clearing its cache. C.  Manually clear the cached application and applets for specific applications: Delete all the files in the 'wbapplet' cache. Windows, clicking Start > Run... and entering %userProfile% will open the local Windows user directory.  \niagara\wbapplet\modules   Delete everything in the 'Secondary Applet' cache, also located under the current %userProfile% folder. Windows 7: \AppData\LocalLow\Sun\Java\Deployment\cache Windows XP: \Application data\sun\java\deployment\cache        

Issue What Ethernet speed and duplex is supported by the MNB-1000? Environment MNB-1000 Cause Specifications for IT infrastructure Resolution The MNB-1000 controller has auto-sensing Ethernet port (10/100 MB, half / full duplex) capabilities and are dependent on the network / switch to which they are connected.  The MNB-1000 has the ability to auto negotiate with the Ethernet network on startup.

Issue Can the I/A Series R2 ModbusAsync driver be configured to control minimum send time between Modbus messages to the bus? Environment I/A Series R2, Modbus Cause The Modbus device under control is unable to process messages at normal rates and requires a delay between messages received. Resolution The minimum send time between Modbus messages can be controlled by adding a parameter into the drivers.properties file. Note: Requires modbusAsync-2.302.514.v1 or higher. Open the UNC with the admin tool and go to the Installation tab. Edit the drivers.properties file. Add the property (shown below) on its own line within the file. Set the value the number of mSec of delay between messages. Save the file and reboot the station (remember to backup the station when requested). modbusAsync.minSendInterval=1000

Issue I/A Series G3 Software Drivers Returns Environment I/A Series G3 software drivers Examples: ENC-DRV-MOD, ENC-DRV-MOD-T etc.  Cause The wrong software driver was purchased for an ENC-520 and the ENC-520 has been shipped to the customer.  Resolution There are no returns on software drivers. A purchase would have to be made for the software driver that is required.  The existing driver that was wrongly purchased can be re-license for use on another G3 device by purchasing an I/A Series license change (IA-LIC-CHG). 

Issue Customer did a full backup of a SIGNAL 4.4.1 installation.  A full backup is data, bitmaps, and executable files.  The computer hardware was replaced along with the operating system to Windows XP 32-bit.  The customer has SIGNAL version 5.0.0. Environment SIGNAL Cause Computer hardware replacement Resolution There are a couple of ways to restore the database.  Here is a simple method: - Install SIGNAL 5.0.0 - Restore the full backup from version 4.4.1 (this step overwrites all the executable files of 5.0.0) - Re-install SIGNAL 5.0.0 (this last step will update all the executables back to version 5.0.0) The license file, signal.dcf, may need to be checked to ensure it is for version 5.0.0.

Issue Information on how the MNB-Vx determines damper position after a power cycle. Environment MNB-V1 and MNB-V2 Cause Understanding damper behavior after a power cycle Resolution After a power cycle, the damper does not know exactly where it is and it is NOT stored in non-volatile memory. So, it must drive open or drive closed to re-synch the hall effect sensors embedded in one of the gears that provides positional feedback. There are two Hall-Effect sensors that detect a magnet, embedded in one of the drive gears, as it spins. Each sensor sends a pulse to an internal counter each time it detects the passing magnet. The two Hall-Effect sensors help with identifying clockwise and counter-clockwise rotation. The accumulated pulse count and the gear ratio help in calculating the damper position. Right-click the VAV Actuator object in WorkPlace Tech and go to its Properties, there is a setting called 'Position Initialization Mode'. Select open or closed as the choice when initializing after a power cycle.  

Issue A newly added Microzone II does not appear in the Node List in PSI.  The ASD trunk contains existing controllers connected to a UNC-520.  All existing ASD controllers appear in the Node List.  Environment Niagara R2 ASD Cause The new ASD controller must be 'learned' into the R2 station in order for it to appear in the Node List in PSI. Resolution Access the R2 station and use Device Manager to find and learn the new controller into the station. 

Issue After copying sections of logic from one application to another the pointers from that logic won't connect to other objects and therefore show up as red lines. Environment WorkPlace Tech Cause Copying sections of logic from an older application has been known to cause this. Resolution To recover the application remove all objects and reference tags that exhibit the connection issue, compile the application and then re-create the deleted logic by pulling objects from the Shapes window.

Issue What is the difference between the MNL-V3RV3 and the MNL-V3RV3-A? Environment  MNL-V3RV3 MNL-V3RV3-A Cause MNL-V3RV3-A is a new part number, and it isn't clear how it differs from the existing  MNL-V3RV3. Resolution The MNL-V3RV3-A meets the requirements of the Buy American Act (BAA).

Issue What is the part number & price for a SmartStruxure/Network 8000 driver or a SmartStruxure/Signal driver? Environment SmartStruxure Network 8000 Signal Cause Job estimating Resolution There is no Network 8000 driver or Signal as there is with I/A Series Niagara. The conversion process is performed at no cost when converting an I/A Series R2 database,  Network 8000 GCM or Signal to SmartStruxure via the "TAC I/A Series Conversions Projects" link on the iPortal2 web site.

Issue The BDelay object from the LonWorks jar conversion library intermittently shows very large "remaining time" causing logic issues. Environment R2, UNC's Cause The BDelay object does not initialize the time remaining properly under some conditions. Resolution In the Lib jar - programObjects - hvac folder there is a program called DelayedOutput.sns.  This program can do the delayed on and off function but will need to be enhanced if the time remaining output is required.