Issue Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded here. The devices covered are Schneider-Electric's range including Andover, TAC and Satchwell and other manufacturers temperature sensors. All are detailed below. For the standard thermistor, tables click here, where the INET, I/A, and BALCO resistance tables are detailed. This is the chart for the Precon Thermistors - ACCTemp 10K Type III thermistor also known as the 10K4A1 Thermistor. For EcoStruxure I/O Module universal inputs, the type of thermistor bead is classed as a: "10k Type I (Continuum)" Satchwell T range is now known as STR600, STP660, STD600, STO600 10K3A1 with shunt Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers include: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850, TS-57011-850, TS-57031-850, and TSMN-90110-850 Series. Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature / resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor can be found here. Please note that the controller may not be able to use the full temperature range shown in the table.  

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 the 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 (http://www.connect-air.com).  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 When a user attempts to connect to the Sigma 4.08 (3.46.57) Server using a WebClient, the client connects, but the screen remains blank. Product Line Satchwell Sigma Environment Sigma WebClient 4.08 (3.46.57) Cause When Sigma 4.08 is installed, the installed version of LogonSE.swc is blank. Resolution Download the correct version of LogonSE.swc. Shutdown the Sigma client and server. Navigate to Sigma/Data/Graphics/Drawings and delete LogonSE.swc. Copy the downloaded version of LogonSE.swc to Sigma/Data/Graphics/Drawings. Restart the Sigma client and server, and then test the Web Client.

Issue I have upgraded a BAS site to Sigma, but my controllers will not return correct values when using my Lookosn.rec files. Environment Sigma Cause Lookosn.rec are not used with Sigma. Resolution All controller specific tables must be copied to the universal Lookup.rec. These should be in the range of 1000 to 1999. By the use of 'Download Lookup Tables' from System Diagnostics, a local copy of Lookup.rec is sent to the controller.

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 Can Sigma Logging Database be merged? Environment Sigma version 4.03 and 4.04 Cause There are currently no tools available on the open market suitable for merging the database as it's proprietary not "off the shelf." Resolution At Version 4.03 and 4.04 there are no means of combining Sigma Logging Databases.

Issue Can a USB connected printer be used a as a Live Alarm Printer configured for continuous printing? Environment Live Alarm Cause To provide the continuous printing function Sigma maintains a connection between the print queue and the printer, therefore keeping the port open and available at all times. Due to the way they operate, it is not possible for USB ports to remain open. Resolution It is not possible to use a USB printer for continuous printing.  The USB "Page Printing" option operates correctly. Please also refer to TPA-LOND-08-0012.00

Issue What PDAs (Personal Digital Assistants) are available for use with Sigma? Environment Sigma WINCE PDA Cause Supported PDA devices Resolution Version 4.01 WinCE (Build 3.36.24) software supported Dell Axim X51, X5, X3 PDAs which are now obsolete. The software was expected to work on other compatible PDAs providing they were running Windows Pocket PC 2002/3 or Windows Mobile Version 5. Version 4.04 WinCE software supports the following... Dell™ Axim™ X51 with Windows Mobile 5.0 iPAQ hx2490b with Windows Mobile 5.0 iPAQ 114 and the iPAQ 214 with Windows Mobile 6 Advantech TPC-30T panel mounting device with Windows CE 5.0.

Issue Sigma graphic only updates when first opened and no regular updates occur there after or only some graphic data values update. Product Line Satchwell Sigma Environment Sigma Controllers Cause A Sigma graphic update is controlled by the tolerance setting on the Sigma object and defines when the new value is transmitted from the controller to the server.  If the update does not occur, then the Tolerance value could be set to high. Resolution Reduce the tolerance value via the Sigma object editor. Download the object to the controller. Restart the graphic. Note:  Reducing the tolerance too far can lead to graphic updates dominating communications resources in the controller. For example; A temperature object can be set to 0.05 to give an update for every 0.1 degrees. A change of state programmable object should be set to 0.5 as it will returned true/false statement (equivalent to 1/0). A pressure sensor measuring Pascal’s (100's) may need the tolerance setting higher (e.g. 10) as pressure can change rapidly at higher values.  For globally changing the tolerance values for the Sigma objects, download the Sigma Tolerance Utility

Issue After making a changes to a Sigma multi-stage control loop do I have to download all the control object stages? Environment Sigma Client Object Editor. Cause Sigma Object Editor does not distinguish between the various control stages when downloading the multi-stage control object. Resolution No, Sigma Object Editor will down load all the Control object multi-stages (objects).

Issue After loading SigmaX on to a new laptop it does not run.  An error appears "The file SigInterfaceMfc.dll is not found." If accepted then another error message occurs, "The file SigShell.dll is not found." Product Line Satchwell Sigma Software Environment Sigma SigmaX Windows XP, 7, 10 Cause The Windows Environment Path "C:\sigma\bin" is not set when SigmaX was installed. Resolution Manually add the setting “c:\sigma\bin” to the Windows Environment Path. On Desk Top find the icon "My Computer". Using right hand mouse button select "Properties". Select the "Advanced" tab. Select the "Environment Variables" button. In the "System variables" window highlight the "Path" variable. Select the "Edit" button Scroll to the end of the "Variable value" text box and append the text string with “;C:\Sigma\bin\” Select "OK" buttons to close and save the changes (three times).

Issue After a Sigma Flexima has exported a CSV text file and then when opened in Windows Excel an error message occurs ‘File not loaded completely’ Environment Sigma Flexima, Microsoft Excel 2003 Cause Occurs because the Flexima export file contains more data than Windows Excel can load into one worksheet. Microsoft Excel 2003 is limited to 65665 lines of data; this is equivalent to a Flexima file size of approximately 1.5Mb. Resolution Reduce the size of the export file by running more frequent Flexima extractions from the Sigma Scheduler. Microsoft Excel 2007 or later has an increased capacity to 1,048,576 rows. Upgrade the excel version will resolve the issue.   

Issue Sigma remote client software has been added to new PC and the client will not connect to the Sigma server properly.  On some occasions the connection occurs but the Sigma Client Menu options are not available. Environment Sigma remote client (up to version 4.04), Windows XP, Windows 2000. Cause Sigma Software up to version 4.04 uses the Windows Share to allow the Sigma Remote Client to connect to the Sigma server.  The Windows share is not working correctly. Resolution 1.  Upgrade to Sigma 4.05 or above as this no longer uses the Windows Share to connect remote clients to the server. 2.1  If the software can't be upgraded then enable file Sigma file sharing between the PC’s by using a common Windows username and password on all the Sigma server/client PC’s. 2.2  Check the firewall/network will allow TCP port 3614 to be passed, unblock if necessary. 2.3 If the PC’s are on a client network then you may have to discuss this with the sites IT people to allow TCP port 3614 to pass through their routers/firewalls. 2.4 If the Sigma communications needs to pass through a firewall then port UPD 49152 will need to be unblocked.

Issue Advice on the configuration of a Sigma UNC 632, UNC 696 or UNC 796 controller, when connecting it to a "Flat" Ethernet network. Environment All Sigma controllers connected to flat ethernet network. Cause General advice. Resolution A "Flat" Ethernet network is a network that does not contain any subnets, for instance a network who's address is 10.158.0.0 Mask 255.255.0.0 will contain network addresses 10.158.0.1 to 10.158.255.254. On this type of network the Sigma device will only require an IP address and Subnet Mask to be entered. This information and details of the controllers "Default Server" are added to the controller using the SDCU (Sigma Device Configuration Utility).

Issue Advice on the configuration of a Sigma DNN (Distributed Network Node) when connecting it to a "Flat" Ethernet network. The DNN provides a communications route to Sigma controllers connected to an Ethernet or ARCnet sublan. Product Line Satchwell Sigma Environment Sigma Ethernet network Ethernet or ARCnet subnets Cause General configuration advice. Resolution A "Flat" Ethernet network is a network that does not contain any subnets, for instance a network who's address is 10.158.0.0 Mask 255.255.0.0 will contain network addresses 10.158.0.1 to 10.158.255.254. On this type of network the DNN will only require an IP address and Subnet Mask to be entered. This information and details of the DNN's "Default Server" are added to the device using the SDCU (Sigma Device Configuration Utility). If the DNN has RIP (Routing Information Protocol) enabled then it will broadcast the route to the sublan onto the network, if RIP is not enabled, then a persistent route must be added to the Sigma server. Please refer to Persistent routing on the Sigma server for more information.  To modify the DNN RIP settings, use the Pocket Terminal programme. RIP is enabled by default. To disable RIP on port 5 of the DNN. Start the Pocket Terminal programme. Enter RIPD 5 and select send. To enable RIP on port 5 of the DNN. Start the Pocket Terminal programme. Enter RIPE 5 and select send. To review the status of RIP Enter RIPS and select send

Issue Advice on the configuration of a Sigma UNC 632, UNC 696 or UNC 796 controller, when connecting it to a "Subnetted" Ethernet network. Environment All Sigma controllers connected to flat ethernet network. Cause General advice. Resolution A "Subnetted" Ethernet network is a network that contains a number of subnets, for instance a network who's address is 10.158.1.0 Mask 255.255.255.0 will contain network addresses 10.158.1.1 to 10.158.1.254. The IP address 10.158.2.1 will be connected to another subnet of that network. On this type of network the Sigma controller will require an IP address, Subnet Mask and the subnet Default Gateway to be entered. This information and details of the controller's "Default Server" are added to the controller using the SDCU (Sigma Device Configuration Utility).  

Issue Advice on the configuration of a Sigma DNN (Distributed Network Node) when connecting it to a "Subnetted" Ethernet network. The DNN provides a communications route to Sigma controllers connected to an Ethernet or ARCnet sublan. Environment Sigma Ethernet network Ethernet or ARCnet subnets Cause General configuration advice Resolution A "Subnetted" Ethernet network is a network that contains a number of subnets, for instance a network who's address is 10.158.1.0 Mask 255.255.255.0 will contain network addresses 10.158.1.1 to 10.158.1.254. The IP address 10.158.2.1 will be connected to another subnet of that network. On this type of network the Sigma DNN will require an IP address, Subnet Mask and a Static Route to be entered. The Static Route is entered using the Pocket Terminal programme and is entered as follows. SR+ 0.0.0.0/0 Default Gateway of subnet Ethernet  and the Ethernet port number, so, if the default gateway for this subnet was 10.158.1.254 and the Ethernet port number was 5, then the following would be entered using the Pocket Terminal programme.   SR+ 0.0.0.0/0 10.158.1.254 5 In this type of configuration it is generally necessary to disable RIP on the DNN, which is enabled by default. To disable RIP on port 5 of the DNN. Start the Pocket Terminal programme. Enter RIPD 5 and select send. As RIP is disabled, the sublan route is not broadcast to the network, and therefore  this routing must be added to the network routers. This requirement must be pointed out to the IT network administrators.

Issue Advice on adding a persistent route to the Sigma server PC. Product Line Satchwell Sigma Environment Sigma Server PC Cause General advice Resolution On a Sigma server connected to a "Flat" Ethernet network, where the system is using Ethernet or Arcnet communications via DNN's, and where it is not possible to run RIP on the DNN's, then it will be necessary to add a persistent route or routes to the Sigma server. A "Flat" Ethernet network, is a network that does not contain any subnets, for instance a network who's address is 10.158.0.0 Mask 255.255.0.0 will contain network addresses 10.158.0.1 to 10.158.255.254. To add a persistent route you must go to the Windows command prompt. This is achieved by selecting the Windows "Start" button, then the "Run" command and enter "CMD", a DOS window is now opened. At the DOS prompt type ROUTE ADD -P "Subnet address" "Mask" "DNN Ethernet IP address". So if the DNN Subnet was 192.168.1.0 mask 255.255.255.0 and the Ethernet IP was 10.158.1.6 then the persistent route would be added as below ROUTE ADD -P 192.168.1.0 MASK 255.255.255.0 10.158.1.6 To check that this has been correctly added enter "Route Print" at the command prompt, the route should have been added at the bottom of the list. Add a route for each DNN.

Issue Is Sigma IC-Gen DDE release 3.10 compatible with Sigma 4.04? Environment Sigma IC-Gen DDE release 3.10 Sigma 4.04 Cause The release note for IC-Gen V3.10 states: "This product has now been rebranded to reflect TAC ownership and reissued as release 3.17 (Build 3.34.14). All functionality is the same and this release note is applicable to both Invensys and TAC versions" Resolution Version V3.10 is in fact V3.17 and is compatible.

Issue After installing SigmaX version 5.0 or later, when running the software an error message reports a missing DLL. Environment SigmaX version 5.0, 5.2, 6.01, and 6.02 Cause System Path variable is missing C:\Sigma\Bin Resolution Make the following modification to the PC's System Properties. Note: This addition is only required on machines running SigmaX. Right click the My Computer icon on the desktop and select Properties Choose the Advanced tab and select the Environment Variables button From the System Variables section, highlight Path and select Edit The statement ‘;C:\Sigma\Bin’ must be added to the end of the Variable value line