Issue Where Sigma utilizes the site Ethernet network, and that network consists of multiple subnets, Link Addressing is used to route global messages. Product Line Sigma Environment Ethernet networks containing subnets. Cause Global Values not being passed from controller to controller on different subnets. General advice on the configuration of Link Addressing. Resolution PIB 05 105 Link Addressing explains how to configure Link Addressing on a Sigma system utilizing a customers Ethernet network,

Issue BAS terminal receives system messages from a PIU with no explanation and is asked to contact Product Support. For example "Message No. 19920 not available. Please contact Product Support" Product Line Other, Satchwell Sigma Environment BAS PIU  and Sigma Pre-release 4 System Messages BAS (1 - 10499) SNP Gateway ( 10500-10999 ) CHUBB Remote Access Management ( 11000-11499 ) CEGELEC ( 11500-11999 ) OTIS   ( 12000-12499 ) CCURE ( 12500-12999 ) WORMALD ( 13000-13499 ) ASIC ( 13500-14999 ) SIMPLEX ( 14000-14499 ) CARRIER DATAPORT  ( 14500-14499 ) EXPRESS LIFT ( 15000-15499 ) CARDKEY ( 15500-15999 ) Mitsubishi ( 16000-16499 ) Liebert ( 16500-16999 ) IMPACC ( 17000-17499 ) YORK ( 18000-18499 ) AUTOFLAME (19000 - 19100) AUTOMETERS (19100-19199) MITSUBISHI PLC (19200 - 19299) SIEBE MICRONET (19400 - 19499) CROWCON (19500 - 19599) MNI (MicroNet Interface) ( 19700-19799 ) Colt OPV ( 19800-19899 ) MODBUS ( 19900-19999 ) MCQUAY (20000 - 20199) FIDELIO (20200 - 20299) ATLAS COPCO ( 20301-20399 ) UNIFACT PRO ( 20500-20599 ) Cause Due to a size limit (64Kb) not all the PIU error messages are included in the Messages.ini file. Resolution A more complete list of the of BAS error messages can be found here. Copy the appropriate section Paste into the C:\Bas\Data\Messages.ini file into the correct sequence as by message number The maximum size of the message.ini file must not exceed 64Kb Example:

Issue Every time the computer reboots, LMGRD errors are shown at startup. LMGRD encountered a problem and needed to close. lmgrd.exe - Application Error The instruction at "0x0012e854" referenced memory at "0xffffff91". The memory could not be "written". Product Line Other, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Vista Server 5.0 FlexNet Licensing Remote Alarm Manager Sigma BAS2800+ Micronet Errors Cause There is a known issue with the new license server from Flexnet. The LMGRD.exe is actually crashing during shut down of the PC. Resolution This is nothing dangerous. What happens is that when you turn off the PC, something is happening with the license server during the shutdown phase. Since LMGRD runs as service, it can not display this error message during this shut down. The error message is shown the next time the PC is started. It will not affect anything since the error messages is queued from the last shutdown sequence, NOT during the startup. We think it has something to do with having a license server installed and not using only an entitlement license. In some situations, placing a customer license file from any project into the license folder along with the monthly demo license stops the LMGRD error. The license server may read the customer license, note that it is invalid, then use the monthly license. Flexnet is looking into this issue. Look for a fix in upcoming versions. On Sigma, BAS2800+, and Micronet systems where Remote Alarm Manager is installed, the TAC license server can be uninstalled as it is not used.

Issue Epson LQ-300+ II Printer does not work correctly in Windows 7 when used as an Alarm printer. Epson LQ-300+ II fails to print. Product Line Satchwell Sigma Environment Epson LQ-300+ II Sigma Windows 7 64-bit Cause When the printer is set to Continuous Print, alarms are spooled but the printer fails to print. The printer only prints if a change is made within Sigma > Alarm Manager > Configure > Live Printers. Resolution In this example the Epson LQ-300+ II printer was used. Remove the printer from the Devices and Printers window. Re-install the printer by "Add Printer." Use the CD that came with the printer and load the Windows XP 32-bit driver. Do not use the Windows 7 driver. Note: the printer name will be slightly different! Set the Printer Properties > Advanced tab > Print Processor to "Raw [FF auto]" Set the Printer to "Spool directly to the printer" Set the paper, fanfold or A4. Shut down the Sigma Client and Sigma Server, delete the printerconfigsnn.rec file in C:\sigma\data folder. (This will remove the old printer name in Sigma with the Windows 7 driver and avoid any confusion) Start Sigma Server and the Sigma Client, in Alarm Manager, highlight and re-assign the printer, set to continuous, tick LF and CR boxes.

Issue ARCNET Cable Requirements. Product Line Satchwell Sigma Environment Sigma 4.05 and earlier versions V53 and ARM7 Processor Boards Cause Sigma ARCNET Network cabling advice. Resolution The following Sigma Cabling Guide should be followed when installing an ARCNET network for Sigma:  Sigma Cabling Guide 2.2 Network biasing and earthing arrangements will be required and further information about cabling can be found in the following guides: For V53 Processor Boards (UNC496, 596, UNC532, DNN and IC integration controllers): Sigma Configuration Guide - Chapter 26a For ARM7 Processor Boards (UNC696, 796 & UNC632): Sigma Configuration Guide - Chapter 32; Sigma Configuration Guide - Chapter 31 For ARM7 Processor Boards (DNN3 Decentralised Network Node): Sigma Configuration Guide - Chapter 33 For ARM7 Processor Boards (IC3 Integration Controller): Sigma Configuration Guide - Chapter 34

Issue Doctor and SigmaX Index edit password Doctor and SigmaX Binary file edit password Environment BAS Doctor Sigma SigmaX Doctor Cause Need a password that allows access to edit an index or binary file. Resolution IE is the password for index edit. BE is the password for binary file edit. These passwords are not case sensitive. Either IE/BE or ie/be can be used.

Issue What batteries and PSU cards can be used in a x96 Controller? Product Line Other, Satchwell Sigma Environment S-x96-STD S-x96-BAT Sigma BAS Cause What batteries and PSU cards can be used in a x96 Controller or BAS controller? Resolution See TPA-LOND-08-0017.02 S-ARM7-BAT is the Sigma UNC PCB Battery Spare for the ARM7 CPU Board. The battery itself is a Ni-MH 2-Button Cell, 2.4v, 80mAh. S-V53-BAT is the Sigma UNC PCB Battery Spare for the V53/V25 CPU Board. The battery itself is a Ni-MH 3-Button Cell, 3.6v, 150mAh. S-X96-BAT is the Sigma UNCx96 Hi-Capacity Battery for the x96 products. The battery itself is a Ni-MH D-Cell pack, 10.8v, 5Ah (12-Hour). S-X96-STD is the Sigma UNCx96 Standard Capacity Battery for the x96 products. The battery itself is Ni-MH AA-Cell pack, 10.8v, 1500mAh (1.2-Hour) Due to UK legislation in 2006 NiCad batteries could not be used and changes were made where NiMh batteries are used instead 2016-01-22: - Confirmed both the S-X96-STD and the S-X96-BAT battery packs are currently available. Note: Schneider sales do not understand dashes, so when asking for price and availability you need to remove the dashes or they will not find the parts. Specification Sales need Price provided by sales S-X96-STD SX96STD £ 198.05 S-X96-BAT SX96BAT £ 541.19 General Rules for battery replacement and PSU card replacement/modification are: 11/2008 to present - The controller was originally shipped with the NIMH battery and PSU card suitable for charging the NiMH battery. These PSU cards are suitable for charging both NiMH and NiCad batteries. 04/2004 to 10/2008 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. 1999 to 03/2004 x96 BAS/V53 PSU cards - The PSU card have to be replaced to fully charge NiMH batteries. Pre 1999 BAS PSU cards - 2 resistors are required, the TPA explains how. The resistors are shipped with the NiMh battery. Note: If upgrading to Sigma then the Upgrade kit S-x96-UPKIT should be used which includes a new PSU card.

Issue How to be redundant with your intelligent Building Management System (iBMS) Product Line Andover Continuum,EcoStruxure Building Operation,Field Devices,Other,Satchwell Sigma,Security Expert,TAC INET Environment Existing intelligent Building Management System Open Mind High Avalibility Solutions everRun MX Cause In engineering, redundancy is the duplication of critical components of a system with the intention of increasing reliability of the system. To be redundant with an intelligent Building Management System (iBMS) would take on two possibilities. 1. Have an alarm on critical points alerting personnel who move into action quickly replacing control boards or devices in the event of failure. 2. Have secondary backup controllers which upon failure, which are used to control devices resuming functionality. This is accomplished through programming the BAS with event sequences triggered from alarms or flags noting the failure. Redundancy capabilities and feasibility is site specific. Ascertaining failure in boards, points, or devices is crucial to creating secondary measure to keep seamless processes going and resume with functions.   Error detection and correction with maintenance is often the best practice for preventing failure. Worn components is the leading cause of failure, followed by lack of planning and consideration in the protection of electrical components through power surges or failures.   For the database, backups including automated backups for MSDE, SQL Express, and Full SQL are available. For further information on database backups and options, take a look at Microsoft SQL Management Studio. For Host Computer backups, look at adding a secondary computer which replicates the database and can capture transactions and messages should a failure with the primary host computer take place. Also work with the local IT department to keep machines up to date, safe, and clean of 3rd party applications which may interfere with integrity.   Schneider Electric’s building management systems are designed such that building control continues even when controller to server communication is disrupted. The BMS server is home to a database of alarm and historical data, as well as system parameters and programs. When a server or its network connection fails, the collection of data from building controllers halts until the problem is resolved. For data critical applications, this solution provides an environment capable of preventing the data loss that results from these types of failures.  Although we do support its use with StruxureWare Building Operation, Security Expert, Continuum, I/NET, Vista, Sigma, and I/A Series as a disaster recovery solution, we do not provide direct support for EverRun. Resolution For Open Mind High Availability Solutions guide please look at the following link; Open Mind High Availability Solution guide For everRun MX solution guide please look at the following link; everRun MX guide  

Issue How to correctly configure the Live Alarm Printer filtering in Sigma Product Line Satchwell Sigma Environment Sigma release 4.05 SP1, SP2 and SEB Cause General configuration advice Resolution The Sigma Live Alarm Printer filters provide the option of which alarms to print, and which to print immediately. It is only possible to select one filter, per function per printer. In the Sigma Alarm Manager select the "Configure" option, and then select "Printer Filters" Create a maximum of two printer filters, one to "Filter Alarms to Printer" and the second to "Filter Alarms to print now". In reality only one filter might be necessary, but this will depend on site printing requirements. In the Sigma Alarm Manager select the "Configure" option, and then select "Live Printers" Select a "Live Alarm Printer" from printer list. Select a filter in the "Filter Alarms to Printer" option. Select a filter in the "Filter Alarms to print now" option. This is the configuration completed for this printer. If another printer is also required to print "Live Alarms" then repeat the above process again, making sure that the printer is highlighted first.

Issue The Remote Alarm Manager sends a message to the recipient indicating that an alarm has been inactivated. The screen shot below shows how a typical message will appear on the receiving mobile phone. Product Line Other, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Remote Alarm Manager version 1.2 Cause An alarm message is generated, and the Remote Alarm Manager processes it in the normal way. After three days and at midnight, the Remote Alarm Manager will send a inactivation message to the on-call recipient, indicating that this alarm has been inactivated. Resolution This is not a fault with the system, it is operating as designed. When a new alarm is received by the Remote Alarm Manager, it is acted on in the way the configuration dictates. If the alarm remains on the system, without being retransmitted, then after three days the inactivation takes place. The 3 days is the default setting and can be changed if required.

Issue When SigUpgrade is run at Release 4.08, a DeviceCnf.rec file that was created at Release 4.04  (as opposed to being the result from a SigUpgrade from Release 4.03) fails to upgrade to 4.08 correctly, and leaves the file unchanged in the 4.04 format. Product Line Satchwell Sigma Environment Sigma Cause Occasionally, at Release 4.04 when a new DeviceCnf.rec file is created it is tagged "Version 0" instead of the correct "Version 1" Resolution The DeviceCnf.rec file can be still be upgraded to Release 4.08 but by completing an intermediate upgrade from Release 4.04 by any one of following releases: Sigma Release Build Number Release 4.05 3.42.34 Release 4.05 SP1 3.42.43 Release 4.05 SP2 3.42.48 Release 4.05 SEB 3.43.18 Release 4.06 3.44.14 Release 4.06 SP1 3.44.16 Release 4.06 SP1 3.44.18 Release 4.07 3 45 48 Release 4.07 SP1 3 45 51 Release 4.07 SP2 3 45 58   Then finally upgrade again to Release 4.08.57 before continuing with the upgrade..

Issue What web browsers are compatible with Sigma Web ActiveX interface Product Line Satchwell Sigma Environment Sigma 4.3 and later Cause Later versions of Internet Explorer do not display the Sigma ActiveX web pages. Resolution Sigma 4.3 introduced the ActiveX web client, this interface is only compatible with Microsoft Internet Explorer. The table below details the versions of Internet Explorer that are compatible with the various Sigma Web ActiveX releases. Operating System/Sigma Version 4.08 4.07 4.06 4.05 4.04 4.03 Microsoft ® Windows 2000         IE6 IE7 IE6 IE7 Microsoft ®Windows XP IE7 IE8 IE7 IE8 IE7 IE8 IE6 SP3 IE7 IE8 IE6 IE7 IE6 IE7 Microsoft ® Windows Server 2003 IE7 IE8 IE7 IE8 IE7 IE8 IE6 SP3 IE7 IE8 IE6 IE7 IE6 IE7 Microsoft ® Windows 7 IE8 IE9 IE8 IE8 IE8     Microsoft ® Server 2008 N/A N/A N/A N/A     Later versions of Internet Explorer than those listed above may be supported in Compatibility View

Issue When trying to connect to a Sigma system from SmartStruxure an "Unable to load SigXmlExport.dll" error message is displayed. Product Line EcoStruxure Building Operation, Satchwell Sigma Environment SmartStruxure Enterprise Server version 1.5 Sigma 4.08 Cause The Sigma to StruxureWare Support files have not been installed to the Sigma installation. Resolution Download the Sigma To StruxureWare Building Operation Support Program from the Exchange Download Center. This additional software allows a Sigma Release 4.08 installation to respond to data import requests from SBO 1.5 and takes Release 4.08 to Build 3.46.66 On the existing Sigma 4.08 Sigma server PC, run SigmaSBOSupportSetup.exe and install the software to completion. There is no need to stop Sigma clients or the server.

Issue Cannot commission an IC3 LON controller in LonMaker. It has become applicationless and the red service LED is flashing or is permanently lit.  Product Line Satchwell Sigma Environment Satchwell Sigma Controller IC3 IC LON FTT-10 NodeUtil Cause The Echelon chip has become 'locked' and requires resetting.  This can be caused by corrupted controller files, very high LON traffic (> 50% Bandwidth), or the controller has started from "start-up mode" or cold start.   Resolution The Echelon chip can be reset using NodeUtil.exe  .  This is a DOS-based program that can be loaded onto a laptop with an FTT-10 Echelon adaptor. A clean working set of controller files will be downloaded to the device. In the case of a flashing red LED - Download 'clean' files to the controller Start NodeUtil on the laptop and plug LON cable into the controller Reset controller (via onboard reset button) Activate the plug-in LON card service pin and the Neuron Id should appear on the laptop. Note: If further controller resets and service pin activations fail to generate the service pin echo then discard the plug-in card and replace with a new one. From the NodeUtil menu select 'R' and enter the Node Id number Confirm the reset of 3150 Node The service LED should stop flashing and the controller should now be 'Configured' that is not 'applicationless' In the red LED is permanently lit - Download 'clean' files to the controller, the Echelon chip will become locked again. Repeat the reset procedure using NodeUtil.exe, this will allow the controller to work, but the plug-in card will need to be replaced. Example of NodeUtil process; NODEUTIL> (H)elp with commands A -- (A)dd node to list. D -- Set the (D)omain of the network interface. E -- (E)xit this application and return to DOS. F -- (F)ind nodes in the current domain. G -- (G)o to node menu............. H -- (H)elp with commands. L -- Display node (L)ist. M -- Change node (M)ode or state. O -- Redirect (O)utput to a file. P -- Send a service (P)in message. R -- (R)eboot 3150 node. S -- Report node (S)tatus and statistics. T -- (T)ransceiver parameters. V -- Control (V)erbose modes. W -- (W)ink a node. Z -- Shell out to DOS. NODEUTIL> Received an ID message from node 2. Program ID is ICLON1a NODEUTIL> Received an ID message from node 2. NODEUTIL> (R)eboot 3150 node Enter node id for reboot (0-2) [2] :2 *** Neuron 3150: Rebooting will reset comm. params, node state on-chip EEPROM variables and buffer configuration Are you sure you really want to do this? (Y/[N]): Successfully rebooted node NODEUTIL> A second solution has been provided by a customer and could be considered if the above suggestions does not provide a solution. Alternative reset procedure provided by a customer is as follows: - 1. Removed the IC LON from both the LON and the Sigma network. 2. I used SCDU tool to re-node the ICLON to a random IP address, which I believe cleared the database and the files etc. 3. I removed the power form the ICLON and then removed the LON daughterboard card from the ICLON mainboard. 4. Re-instated power and re-installed the LON daughterboard card. 5. Connected with NODE Utility as per the product data-sheet below. And cleared the LON comms buffers as the suggested method. 6. Checked that the red constant service light ceased from the constant illumination. And witnessed that the Green LON heartbeat LED was operational. 7. Re-Node the ICLON to the original IP and check operation. * The Sigma IC-LON plug-in card can be purchased using the part number S-LON. The S-LON has been discontinued as of 29th December 2017 and it is now in the service period (limited quantities available for purchase). Refer to PA-00528 for details.

Issue When starting SigmaX, an error is reported, the error is: - This application failed to start because side-by-side-configuration is incorrect. Reinstalling SigmaX does not help. Product Line Satchwell Sigma Software Environment SigmaX Windows 7 Windows 10 Cause SigmaX error when trying to run on a Windows 7 or Windows 10 machine. Resolution Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file. To do this, follow these steps: Open an elevated command prompt. Click Start > All Programs > Accessories Right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for a confirmation, type the password, or click Allow. Type the following command, and then press ENTER: sfc /scannow The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions. More Information about SFC scan can be found in this document: http://support.microsoft.com/kb/929833 At the command prompt, type the following command, and then press ENTER: sfc /scannow The sfc /scannow command will scan all protected system files, and replace corrupted files with a cached copy that is located in a compressed folder at %WinDir%\System32\dllcache. The %WinDir% placeholder represents the Windows operating system folder. For example, C:\Windows. Note: Do not close this Command Prompt window until the verification is 100% complete. The scan results will be shown after this process is finished. However Microsoft Visual C++ Redistributable may not be installed sfc /scannow will not detect this, the Visual C++ Redistributable will need installing. Please see Error when trying to run SigmaX.exe and RegSigmaX.exe for further information regarding this.

Issue The Sigma Client reports a "HTTP connection failed" error" when an attempt is made to start it. Product Line Satchwell Sigma Software Environment Satchwell Sigma release 4.05 and later Cause When the Sigma Client is started, attempts are made to make a connection to the Sigma Server, this connection fails and the Client cannot be started. Resolution There are a number of reasons why this error might occur, suggestions are listed below. 1.  Windows XP operating system - ensure that service pack 3 has been installed, and that all the Windows updates have been applied. 2. Windows 7 operating system - only Ultimate and Professional are supported. 3. Sigma Client/Server software must be installed by a Windows user with "Admin" privileges. 4. Windows Firewall must either have been switched off, or has "Exceptions" configured as explained in the Sigma 4.05 SP1 release note. 5. Check that the "SigmaSVR" service has been started. If this service cannot be seen, then this is an indication that the Sigma software has not been install by an "Admin" user, and the software must be reinstalled. 6. Corruption of the Windows "User" files has taken place. Create a new Windows user with "Admin" privileges. Log on to Windows as the new user and test the Sigma Client again. 7. If using a VMware image try rebooting the image. 8. SMART is being used and has a modem connected to the PC for uploading data. Ensure that the modem is fully functional. If not, the HTTP error can be caused. This was seen at Sigma: R4   Release 3.44.14. and Smart Task Manager  3.0.2.20. Added 26-07-2012 9. This may be because a proxy server is being used, eg on school networks. Log on to your PC computer with an administrator account. Open the "Start" menu and click on "Control Panel." Double-click on the icon labeled "Internet Options." Go to the "Connections" tab at the top of the window and then click on "LAN Settings." Make sure the box next to "Bypass proxy server for local addresses" is checked. Hit "OK" twice to confirm the new proxy port settings. Make sure the box next to "Bypass proxy server for local addresses" is checked. Hit "OK" twice to confirm the new proxy port settings. Added 25-09-2012. 10. This issue was reported from a School where Sigma 4.05 SP1 had been operating correctly for several weeks. The issue was traced to the Anti-virus software Sophos, which had received an update prior to the failure. Sophos had quarantined two Sigma dll files. To correct this issue both Sophos and Sigma were uninstalled. A later version of Sophos was installed, and then Sigma was reinstalled, this corrected the problem. Added 01-08-2013 11 - Sigma software installed when connected to a wireless network. The Sigma client will only connect to the server when the wireless connection is made. Uninstall Sigma, disable the wireless, enable the network card, and then reinstall the Sigma software. Added 03-10-2013 12. DELL PC, with firewalls and antivirus disabled and no wireless card fitted. There may be a service or an application running in the background as part of the vendors Windows platform makeup.Restore the same version of Windows, but without (where possible) any of the Vendors applications. Re-install Sigma. Added 16-05-2014 13. Check the port number in c:\sigma\bin\setupsvr.exe, the default is 8080. Added 19-05-2014 14. Flexera license software has been reported as a cause for receiving this error. Flexera license software uses port 8080, (IMADMIN.EXE). Stop Flexera and retry Sigma. Changing Sigma from port 8080 to 8081 could also provide a solution. Added 27-08-2014 15. The SBO PCS (StruxureWare Building Operation Project Configuration Server) also uses port 8080.This needs to be stopped or will conflict with Sigma and produce the HTTP error. Added 02-09-2014 16. Make sure any data is backed up from the installed Sigma system. Uninstall Sigma using Add/remove programs (Win XP) or Programs and features (Win 7). Wait for the Sigma un-install process has completely finish. Delete or rename the C:\Sigma folder to.......for example Sigma1. Re-install Sigma by using a right mouse click on the "SigmaSetup.exe" file and select  A new clean Sigma folder will be created during the install. Once completed reboot the computer. Check the SIgma server is running and run up SIgma. Added 2014/10/24 17. The HTTP error can also caused if the computer name contains extended ASCII or Unicode. For example a computer named "P á st" may fail, if the computer name is changed to "Past" this may correct the HTTP problem.

Issue Many LonWorks network installation problems can be avoided if the appropriate network design rules are followed when the network is being designed. Product Line Satchwell Sigma, TAC IA Series, TAC Vista Environment I/A Series MicroNet (LON) Controllers Sigma MicroNet series LON Controllers Vista Xenta Cause The I/A Series MicroNet System Engineering Guide (F-26507) was written as a resource of information for installation of the I/A Series MNL-100, 200 & VAV controllers as well as  the Sigma MicroNet 440 and 620 controllers.  This document is no longer in print.  The Resolution, below, is a summary of the LON design rules presented in that document. Resolution FTT-10 LON network wiring must be installed using Echelon approved wire.  The most common type of wire used is described as Category 4  cable.  This wire is normally unshielded stranded twisted pair 22AWG (0.65mm).  An example of this wire is the W221P or W222P series cable from Connect-Air International.  This type of cable is normally available both in plenum rated and non-plenum rated types.  Consult the job specifications to determine if plenum rated or shielded cable is required. The LON network can be wired using "Free Topology" or "Bus Topology" wiring segments.   A.  BUS Topology Guidelines BUS Topology LonWorks wiring extends from device to device (daisy chain format) with no branches or stubs. A LON-TERM-2 terminator must be installed at each end of the LON bus. When using standard Category 4 LON cable with the recommended terminators, the bus may be up to 4593 feet (1400 meters) in length. When extending LON wire to the MN-Sx sensor base in a bus topology network, the sensor base must be wired as part of the daisy-chain and not as a stub connection. B. FREE Topology Guidelines Free Topology imposes essentially no restrictions on the layout of the network -- some controllers may be wired point to point and others branching from a common point.  The free-topology LON network must be terminated at one point with a LON-TERM-1 terminator. When using standard Category 4 LON cable, the total wire length in a free topology LON network may not exceed 1641 feet (500 meters).  In addition, the longest wire path between any two controllers on a free topology LON network may not exceed 1312 feet (400 meters). C. Common LON Network Wiring Guidelines LON wiring can not be part of an active bundled telephone trunk even if the telephone trunk is wired with Category 4 wire. Shielded Category 4 wire may be used in high EMI/RFI environments.  The shield must be wired continuously and grounded through a 470 Kohm resistor at one end. LON wiring must not be bundled with or housed in the same conduit as controller I/O and power wiring.  D. LonWorks Network Wiring and Addressing Guidelines When the number of controllers on a LonWorks network exceeds 60, the network must be split into segments with not more than 64 controllers or devices per segment using LonWorks Repeaters or Routers.  When counting the controllers and devices on a LonWorks network segment, a LonWorks Network Interface Device and the repeater itself must be included in the device count in each segment. In a LonWorks network containing repeaters or routers, each LonWorks network segment must be properly terminated, as described above. Domain / Subnet / Node addressing is used when configuring the LON controllers. A LonWorks Subnet consists of a series of LonWorks controllers all configured within the same LON Subnet number. A single LonWorks Subnet can have a maximum of 127 device and controller Node addresses.  This Node address count includes the LonWorks Network Interface, all controllers on the subnet and repeater and / or router node addresses.  An allowance is typically made for additional addresses to be used by LonWorks tools connected to the Subnet.

Issue Sigma object registration is not removed after the HTML page is shut down. Product Line Satchwell Sigma Environment Sigma Server (all) HTML Cause The Sigma HTML applet can not send a de-register indication when the HTML page is closed down. Resolution When the HTML page is closed down the registered objects are de-registered after about 5 minutes.   The process for the HTML applet is different to a normal graphic update as it relies on the applet to poll the Sigma server.  The poll interval (ms) is determined by the applet parameter   <PARAM NAME="refresh" VALUE="5000">  Once this stops then the Sigma server will time out and de-register the objects in the controller.

Issue Can more than one Modbus device be mapped to the same IP Address? Product Line Satchwell Sigma Environment IC3 Modbus TCP502 Cause Configuration not documented in release note Resolution More than one device can be mapped via the same IP Address.  For example the gateway.txt file can be: 1,1,3,1,1,0x0001,0,0,1  ;Modsim1 40001 2,1,3,2,1,0x0001,0,0,1  ;Modsim1 40002 3,2,3,1,1,0x0001,0,0,1  ;Modsim2 40001 4,2,3,2,1,0x0001,0,0,1  ;Modsim2 40002 5,3,3,1,1,0x0001,0,0,1  ;Modsim3 40001 6,3,3,2,1,0x0001,0,0,1  ;Modsim3 40002 7,4,3,1,1,0x0001,0,0,1  ;Modsim4 40001 8,4,3,2,1,0x0001,0,0,1  ;Modsim4 40002 OUTPUT ; IP_ADDRESS_TABLE 1,10.158.72.254 2,10.158.72.254 3,10.158.72.254 4,10.158.72.254 ;Do not write below this line   Note: The IC3 Modbus can only be mapped to a single IP Gateway or PC application, and it is not possible to map to two applications on the same PC.

Issue How to calculate the input value for a Lookup table for a resistive AI device. Product Line Satchwell Sigma Software Environment Lookup Tables Cause A lookup table needs to be created for an additional resistive AI device. An existing lookup table does not exist. Resolution The following parameters are needed, the device's datasheet will normally provide this information. The resistance of the device at a known value e.g temperature or a feedback potentiometer. The following calculation is then used. lookup table input value = R1*250 / R1+14700    (Where R1 is the resistance value) The output value in the lookup table will be the known value (e.g temperature or a feedback potentiometer) for the resistance used in the calculation above. Example: Resistance = 5905 ohms at 17'C Table input = 5905*250 / 5905+14700 = 71.6452 and Table output = 17.0 The more samples taken, greater the accuracy. Input values need to be entered with at least 3 decimal figures.