Building Automation Knowledge Base

Issue When using the STR-350/351 as an I/O module in Menta (Options > Device Specification > IO Expansion and Wall Module Table) some programming consideration must be made to keep the occupancy and setpoint in sync between the stat and the program. Both STRIN and STROUT Menta simple blocks should be used for the most robust synchronization. Environment STR-350/351 as an I/O Module Menta Cause The STR-350 takes roughly 30 seconds to recover from a power failure. The Xenta is much faster than that resulting in reading an invalid setpoint from the STR-350 on a power cycle. By storing the last known setpoint in a DELR block with the "backup" option set, the setpoint will be restored (provided the power has not been off longer than 3 days, in which case it would default back to the initial value of the backed up value). Resolution Click the pictures of the Menta macro below to download the source file. Occupancy To control occupancy from the programmable controller time schedule, the occupancy must be sent to the STR-350. In order to allow for local override commands from the stat, the occupancy must be read in from the STR-350. By allowing the programmable controller to control both the schedule and the override, the stat stays in synch with the program. Setpoint The setpoint requires a little bit of extra programming to account for a power failure. The stat will report invalid setpoints for the first 30 seconds, which will cause it to come back in an undesired state. By letting the programmable hold onto the last known setpoint, and write it back to the stat on power up, there is no change in the setpoint after a power loss. Looping the setpoint in/out from the stat keeps everything in synch with the program, including stat adjustments. Note: This code protects against unwanted behavior following a power failure. A download the Xenta base unit will not trigger the Reset block protection and will cause the stat to go outside the bounds of, and then be limited by, either the high or low setpoint limit. Precaution should be taken following a download to manually reset the setpoint to the desired value. Additional logic for controlling the setpoint remotely could be incorporated into this code. If these macros are going to be used with a STR-350/351 set in degrees Celsius; make sure to change all initial values within the setpoint range. If the initial values are outside of the setpoint range, then the setpoint will always default back to the last known value.

Issue Is a license required for the S4 BACnet to N2 Routers? Environment S4 BACnet to N2 Router-16 S4 BACnet to N2 Router-32 S4 BACnet to N2 Router-64 S4 BACnet to N2 Router-128 S4 BACnet to N2 Router-256 I/A Niagara R2 I/A Niagara G3 I/A BACnet Metasys N2 network Cause Additional information on 3rd party router Resolution No license is required. But you will need to fill out the S4_Group_Order_Form and send it to CCC at the time of ordering. Link to S4 BACnet to N2 Routers for additional information

Issue The requirement to have an enthalpy value, rather than a digital on or off state via the existing object. Environment MicroNet VisiSat Bubbleland Enthalpy logic Cause VisiSat's Bubbleland programming area stencil contains an enthalpy object. This object provide a digital state dependant on comparison. Depending on the controller type depends on the amount or objects the controller supports.   There is not a standard object to provide the enthalpy value. Resolution 1. A simple bubbleland scheme can be created to provide an approximate value for enthalpy. In the following example only changing temperature and humidity values are used, for other factors used to calculate true enthalpy use a fixed value. For example the value for pressure used is 1 bar. A custom object that outputs an enthalpy value can be downloaded below. For example: OR 2. Click here to down load this custom object. The file Enthalpy Custom Object.zip unzips to a folder Satchwell with the necessary files. Copy the Satchwell folder created to your C:\ drive then the files will be placed  in the correct folders in your VisiSat installation ready to use. If preferred download the relevant controller type configuration file, and then load the configured scheme with the enthalpy objects into the specific controller. MN300      MN350 MN440      MN450 MN500      MN550 MN620      MN650 OR 3. A VisiSat project containing each controller type with the enthalpy scheme and the configuration saved under a Configs folder within the project. Click here to download the compressed file containing the project. (4.2 MB)

Issue How to Retrieve Log values from TAC Vista MSSQL Database Environment TAC Vista and MSSQL Database Cause Requires third party access to retrieve Log Values from TAC Vista MSSQL Database Resolution 1. Refer to the attached PDF document for the procedure 2. Note: You’re limited to retrieve only one log object at a time

Issue PageGate allows for network paging or network wide SMS messaging from any combination of the following modules: web, email, commandline/ascii, serial, TAP-in and (GUI) windows workstations. SMS or text messages can be sent to alphanumeric pagers, numeric pagers, cell phones, PIMs, billboards or pcmcia pager cards. For capturing and paging I/NET Seven alarms and messages the “Get Serial” module from PageGate is used. Environment I/NET Seven PageGate Cause Network paging or network wide SMS messaging required. Resolution Click here to download this document as a PDF Configuring I/NET to send a message Open up the IO Server. Choose your configuration profile. Maybe direct connect. Click Modify. Under Peripherals, change Text Output Port to a COM port that is not being used, COM3 for example. I/NET will most probably be using COM1. See screen cap below. Set Baud Rate to 9600. Click OK to close out the Configuration Profile Screen. Restart I/NET and I/O Server for changes to take affect. Open up Alarms, Messages, & Transactions. Go to the Edit drop down menu and select Text Library. Here you will need to know the address for the point that you want to generate a message for when it goes into alarm. Choose add to enter point address and desired text message. As you can see above you can enter any text message you want. I/NET is now configured to send a text message to PageGate. Hardware Connections for PageGate-I/NET interface Three Com Ports are required to send the message from I/NET to PageGate Server. One for the I/NET port, a second for the Text Output Port so AMT can send the message, and the third COM port for PageGate to catch the message. Physically connect the Text Output Port to the PageGate COM port that will be catching the message. See Illustration below. Note:   If you run out of COM ports you can go to Radio Shack and purchase a USB to serial cable. It comes with the software to create another COM port. Be aware that it is not plug in play. The software/PC will refer to that USB port as your new COM port. In other words, if you take the USB plug out and insert it into another USB port you will have to repeat the installation to create another new COM port and it will have a different number then you will have to go back into  I/NET or PageGate to point to the right COM port. I found this out because my customer decide he wanted to move his USB cables around and then PageGate quit working. Configuring PageGate PageGate consists of PageGate server, PageGate Admin, & PageGate Monitor. From now on I will refer to PageGate as PG. PG Server is an e-mail server and will create an e-mail domain such as inet@villadematel.com. PG Server can be ran as a Windows NT application so the customer does not have to worry about starting PG when he boots his machine up. PG Monitor will show I/NET generate the alarm, PG catches that alarm, and PG Server e-mails the message out. It is not necessary to run PG monitor unless you are setting up the software or trouble shooting a problem. Follow these steps to assist you in setting up PG to send your message to a cell phone or pager. Go to http://www.notepage.net/ to download the trial version.  Install the software and then open up PG Admin to begin configuration. The PG software file system is organized in a tree structure. Open up Settings under, Program, and PageGate. From this point on reference tree structure on screen caps to navigate through PG. Under settings choose Run PG as an application and check the box next to scheduler, GetSerial and Dialer 1. Remember to go back and change to NT service once you get customer set up. Set the capture serial port for PG, baud rate, parity, data bits, stop bits, handshaking, & init string as you see below. These are the settings that I/NET uses when it transmits a message out the Text Output Port. Go to the GetSerial drop down to Record and enter the Start Pattern and End Pattern you see below. This tells PG how to determine what the message is. Under Recipient choose static recipient and give whatever name you want. The person or group that will be receiving the message. Now name your Static Sender. The application (In our case I/NET) that is sending the message.  Select Message and choose Dynamic Message since our text alarms from I/NET will be different most of the time. Put START offset at 6 so PG will know when our message starts and –4 so it will know when the message ends. 6 being the length of “START “ plus a space and –4 being a space plus the length of “END”. We have now configured PG Get Serial to capture the I/NET message. Connectors. PG will always require at least 1 dialer running and if you are sending a message on the internet you will need to set up the Global settings as well. Under SMTP create a Local Domain. When your customer receives a message it will be from “static.sender.name@localdomain.com”. For example Villa De Matel receives a text message from inet@villadematel.com. Then enter your customers DNS server addresses. You only need one but enter both if you have them. Obtain from their IT department or internet provider. Dialer set up. Even though we are not dialing with a modem PG uses a dialer to send all messages. Serial Port in this case is for an external dedicated modem. Just make sure you have Dialer 1 running (See step 4). Carrier creation. Here we create the cell phone/pager provider that our customer will be using to receive messages and pages. In my customers case it was T-Mobile. To do this, right click on carrier and select Add. Select the drop down box under protocol and select SMTP or the appropriate protocol you need. TAP, GSM, SNPP, etc. Recipient creation. Here we enter the contact data for the individual’s cell phone, pager, fax number, e-mail address, etc. Fill in name of recipient and check the box for enabled service. It is possible to send messages to multiple devices such as an e-mail and text message at the same time. Just check the service you are using but remember you need a dialer for each service. Refer to cell phone provider for e-mail address format. For T-Mobile it was phone number@tmomail.net. Also check the box for Alpha and Drop non-printable characters. Group creation. You can create a Group and PG will send messages to every recipient in that group for the appropriate enabled service. Right click on group and select add. Check box to enable appropriate service. Select recipients you want to add and move them across into your new group. Select apply and PG will now send messages to all recipients in that group. This write up is intended to be a general guide in setting up PageGate for your customer. Most likely your customer’s setting will differ from the settings in this write up. To download the software here is the link to the website: http://www.notepage.net/ Once you get the trial software working you have about 10 days to pay for it because the trial version will shut the scheduler down every so often until you pay for the software. Good luck!

Issue Configuring and monitoring the Xenta 102-AX is traditionally done through the LNS Xenta 102-AX Plug-In, but how can it be done in a Vista Classic Network where no LNS plug-ins are available? Environment Vista 5 Classic Network TGML Xenta 102-AX Vista Workstation ONLY -- This plug-in is not compatible with Webstation or XBuilder graphics at this time. Cause LNS Plug-ins are not available in a Vista Classic Network. Resolution All of the values that are written to by the LNS Plug-In are public and available through the Vista front end. So if only one or two signals need to be set for each box, this can be accomplished by locating them in the Vista network and writing the desired values to them.  This does require some fairly intimate knowledge of the Xenta 102-AX and Plug-In. The alternative is: Download the Xenta 102-AX TGML Plug-in by clicking the image below.  Unzip the contents to the hard drive. Open the TGML file. Select File > Save As > Vista Database Object Navigate to the first Xenta 102-AX in the network. Drill down into the 102-AX on the same level with Node_Object and VAV_Controller modules. Give the plug-in graphic a name and save. Right click on the Graphic object in Vista Workstation and select Copy Navigate to the next Xenta 102-AX and select Paste Shortcut. Since all bindings are automatically populated with relative bindings, copying and pasting shortcuts will automatically display data for the associated Xenta 102-AX. Repeat Step 8 for all Xenta 102-AXs in the network.

Issue Netcontroller power supply is not working as expected. Environment NC1 NC2 CX9900 CX9680 PS120 UPS Cause Problems with Netcontroller power supply. Resolution UPS not working Replace failed 5 Amp pico fuse (located on PC board adjacent to the UPS cable connector) UPS cable or connector has failed or is defective. Insufficient UPS battery capacity is attached to the UPS connector.  UPS requires two 12 VDC batteries). UPS Batteries are not sufficiently charged or have failed. No Power to NetController 3 Amp Slow-Blow fuse has failed.  (located on PC board adjacent to 120 volt power connector). Power switch is shut off. Insufficient supply voltage. General Mode switch is in the wrong position (See manual) Click here to download the PS manual

Issue Replacements for Satchwell sensors Product Line Satchwell MicroNet, Satchwell Sigma, Field Devices Environment DR DR3253 DRT DRT3451 DRT3453 DRT4453 DRT3651 DRT3652 DRT3801 DRT3851 DU DU4301 DUS DUS4302 DUSF DUSF4351 DUSF4352 DRTE DRTE2201 DRTE2801 DRTE2851 DRH DRH7702 DRH7703 DRTH DRTH7712 DRTH7713 DOT DOT0001 DOT0002 DOS DOS0002 DDT DDT1701 Cause Replacements for Satchwell Room sensors Resolution DOT0001/0002 Outside temperature sensor For CSC, KMC, MMC, IAC, MNN New part number: STO600/5126060000 DOS0002 Outside solar sensor For CSC, KMC, MMC, IAC, MNN New part number:  SSO600/5126050000 DR3253 Room sensor non-adjustable For SVT New part number: STR614/004604900 DRT3451 Room sensor exposed adjustment For CZU, CSC New part number: STR612/004604700 DRT3452 Room sensor concealed adjustment For CZU, CSC New part number: STR611/004604600 DRT3453 Room sensor non-adjustable CZU, CSC, CXR, CZT, KMC, MMC, IAC, MNN New part number: STR600/004604100 DRT4451 Room sensor non-adjustable As DRT 3453 in S-Link housing Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3651 Room temperature sensor exposed adjustment For CXR, CZT, KMC, MMC, IAC, MNN New part number: STR602/004604300 DRT3652 Room temperature sensor exposed + LED For MMC, IAC, MNN Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3801 Room temperature sensor fan switch On/off for CZU, MNN, IAC Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRT3851 Room temperature sensor fan speed switches As above plus medium and high Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DU4301 Room sensor temperature For MNN & URC New part number: STR601/004604200 DUS4302 Room sensor temperature setpoint advanced basic sensor New part number: STR613/004604800 DUSF4351 Room sensor temperature setpoint adjustable fan auto/on/off fan override New part number: STR609/004604400 DUSF4352 Room sensor temperature setpoint advanced fan Auto/1/2/3 fan override New part number: STR610/004604500 DRTE2201 Active room detector Basic sensor Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRTE2801 Active room detector On/off Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRTE2851 Active room detector Off/low/medium/high Obsolete with no Schneider Electric replacement Suggestions: Try Titan Products or Sontay DRH7702 2% 0-10V DC humidity only For KMC, MMC, IAC, MNN New part number: SHR100/006902340 DRH7703 3% 0-10V DC humidity only For KMC, MMC, IAC, MNN New part number: SHR100/006902340 DRTH7712 2% 0-10V DC humidity with Satchwell NTC TEMP OUTPUT For KMC, MMC, IAC, MNN New part number: SHR100-T6/006902420 DRTH7713 3% 0-10V DC humidity with Satchwell NTC temperature output For KMC, MMC, IAC, MNN New part number: SHR100-T6/006902420 DDT DDT1701, DDT1702 and DDT0001 Duct sensor non-adjustable New part number: STD660 5126030000 Contact Details: Titan Controls: http://www.titancontrols.net/ Sontay Controls https://www.sontay.com

Issue SNP I/O server and NCP I/O server dongleless software download location. Where can I download SNP I/O server and NCP I/O server dongleless software as advised in: PA-00145 - Satchwell MicroNet Range Rationalisation Product Line Satchwell MicroNet Environment MicroNet View. SNP I/O server dongleless software NCP I/O server dongleless software Cause SNP I/O server software can no longer be ordered, it is available as a free download. Resolution Download the software from The Exchange or Click here to be linked to the Monitor tool.(This link will open a new page) Click here to be linked to the SNP I/O server. .(This link will open a new page) Click here to be linked to the NCP/ARCnet I/O server. .(This link will open a new page).  

Issue Software download location. Where can I download "MicroNet View's Monitor Tool" dongleless software as advised in: PA-00145 - Satchwell MicroNet Range Rationalisation Product Line Satchwell MicroNet Environment MicroNet View Monitor Tool   Cause The MicroNet View dongleless Monitor Tool, software can no longer be ordered, it is available as a free download. Resolution Download the software from The Exchange or Click here to be linked to the Monitor tool. (This link will open a new page) Click here to be linked to the SNP I/O server. (This link will open a new page) Click here to be linked to the NCP/ARCnet I/O server. (This link will open a new page). Click here  to be linked to the USB dongle driver for MicroNet View, that may be required with faster PC's (This link will open a new page).  

Issue The Sigma IC3-Modbus reports that the Modbus devices are offline. Product Line Satchwell Sigma Environment Sigma IC3 Modbus IC Modbus Cause Communications with the Modbus devices has failed, or cannot be achieved. Resolution Testing of the IC3-Modbus must be carried out in a systematic way; the points listed below are only as a general guide: Confirm that the communications type, (2-wire or 4-wire) is correct for all devices connected to the Modbus 485 communications LAN. The IC3-Modbus only uses a 2-wire RS 485 LAN configuration. Ensure that the communications LAN to the Modbus devices is correctly connected. Confirm that the overall LAN length does not exceed the RS 485 maximum of 1200M. Ensure that the cable has been installed maintaining the 300mm segregation from other electrical services. Ensure that the communications cable is a Belden 8762 or similar, and that the cable screening is connected to a good earth at one end only. The other end of the screen should be isolated. (Note: In instances where high frequency noise is present, a 1uF filter can be connected between the isolated screen end and a good earth). Configure the Gateway.txt file, ensuring that the comms parameters match those of the Modbus devices. Add one object for the Modbus device nearest to the IC3-Modbus. Download the Gateway.txt to the IC3-Modbus and then warm-start it. Observe the IC3-Modbus RS 485 communications TXD/RXD LED's and confirm that the TXD is seen to flash on a regular basis. This will indicate that the Gateway.txt file is configured correctly. If the TXD and RXD LED's flash alternatively, then this suggests that normal communications is taking place. If the TXD LED does not flash, then this indicates a problem with Gateway.txt file configuration, and it will be necessary to check the "Low level Alarms" on the Sigma Default/Backup server for more information about the problem. If the TXD LED is seen to flash on a regular basis, but the RXD does not, then there are four possible conclusions: The communications cable between the two points is not continuous, or the cores are crossed. The Modbus device number does not match that set in the Gateway.txt. The register being requested is not a valid register. The Modbus device is faulty. Testing a Modbus device using a Modbus simulator. Download a Modbus simulator, there are several freeware/shareware products available on the internet. Using an RS232/RS485 converter connect directly from the PC/Laptop to the Modbus device. Review the appropriate registers to confirm if the device is working correctly. Testing that the IC3-Modbus is sending appropriate Modbus messages. Using an RS232/RS485 converter, connect from the PC/Laptop to the IC3 Modbus in parallel with the existing Modbus RS485 comms. Start PocketTerminal32.exe, select “Setup/Communication Ports” and set the comms port to match the Modbus parameters, then select “Display” and select to "Display Hex".     The trace programme will display blocks of Hex, as shown below. The message shown below is addressed to Modbus device 11 (Decimal 17), it uses function code 3, the register address is 66 (Decimal 96), only this address is required, and the message has an error check. The message will be shown as 110300660001992BFD which can be split into sections. If the controller replies, the complete Request and Reply will appear as: 110300660001992BFD110302142B3698 Request = 110300660001992BFD Reply = 110302142B3698 Again this message can be split up. 11 = controller address, 03 = Function code, 02 = Number of bytes of data, 142B = Data, and 3698 = Error check. To download a copy of PocketTerminal32.exe please Click Here.

Issue Control HVAC or especially lighting based on the sunrise and sunset times for a given location on a given date, even though this functionality does not exist in Vista like it does in I/NET. Environment Menta Cause Menta/Vista time schedules have no built-in sunrise/sunset capability.  If this is required, it will need to be programmed into a Menta file. Resolution The attached Menta Macro calculates the sunrise and sunset for a given location. Click the picture to download.       Inputs - Menta Simple Blocks Month Date Hour Minute Configurable Parameters Year = Current year.  As Menta has no "Year" block, it must be calculated in the controller and should be set initially for the current year. DST = Does this location participate in Daylight Savings Time?  1=Yes, 0=No. TimeZone = Location's offset in hours from GMT Latitude = Location's latitude in degrees. North is a positive value, south is a negative value. Longitude = Location's longitude in degrees. West is a positive value, east is a negative value. Outputs - Available Data Current minutes past midnight Sunset minutes past midnight Sunset hour Sunset minutes Sunrise minutes past midnight Sunrise hour Sunrise minutes Output integer represents minutes until next transition.  Mimics a Menta time schedule.  Positive values count down minutes until sunrise.  Negative values count down minutes until sunset.

Issue Sigma Web Graphics must be installed as an Administrator, but most users do not have these rights. Environment Sigma Sigma Web Server Cause As most network users do not have Admin rights, there is a need to install Sigma Web Graphics across the network. Resolution The following text has been provided by the Sigma programmers and should be understood by the IT professionals. First you need to create a response (answer) file Then play back the response (answer) file  in silent mode To review the InstallShield Setup Parameters.pdf, please Click Here.

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 How is Continuum configured to validate FIPS 201 PIV card credentials? Environment CyberStation CX9680 ACX5740 ACX5720 Cause Questions on how to configure a Continuum physical access control system to validate FIPS 201 PIV credentials at the door. Resolution Configuring Continuum for FIPS PIV card credentials Click here for instructions on creating a custom FIPS-PIV card format Versions needed for FIPS-201

Issue LDAP (Lightweight Directory Access Protocol) Integration of G3 (Niagara) Users with Active Directory Environment I/A Series G3 (Niagara) LDAP Cause None Resolution The Enterprise server or ENC must be part of the site domain before setting up LDAP.  If DNS has been configured proceed to LDAP Configuration Steps.  For further information consult docLdap_3_1.pdf

Issue Sigma 4 05 Sigma Compact Edition supports the following hand-held devices: iPAQ 114, iPAQ 214, iPAQ 2490b, Dell Axim X51 These devices are no longer available, so what can be used? Environment Sigma WinCE Hand-held devices Compact Edition Cause Supported hand-held CE devices, such as the iPAQ 114, iPAQ 214, iPAQ 2490b, Dell Axim X51 are no longer available. Resolution The ever-changing PDA market has continuously caused problems, by obsoleting devices and creating new ones. This led to us always trying to catch up. With Sigma 4 05 Sigma Compact Edition, it was decided that a method to future proof must be found. This release does not support any additional devices, but it now supports the use of a "Mini PC", Netbook, Notebook etc. To review the release note for the Sigma Compact Edition 4.05 Click Here. To review the User guide for the Sigma Compact Edition 4.05 Click Here.

Issue As of December 2010, Microsoft® Windows XP is no longer available, preinstalled on new computers. Is there a valid, legal and legitimate workaround for running our software products that will not run on Microsoft® Windows 7? Environment New computer that was purchased pre-loaded with Microsoft® Windows 7 Professional or Microsoft® Windows 7 Ultimate I/A Series software that runs only on Microsoft® Windows XP such as: I/A Series (Niagara) R2 - all releases I/A Series (Niagara) G3 - all releases prior to 3.6.x  Signal XP WorkPlace Tech Tool 3.2sp1 Cause Microsoft® Windows XP is no longer available on new computers. Resolution Downgrade the Microsoft® Windows 7 Professional / Ultimate installation to Microsoft® Windows XP. According to the Microsoft® Windows 7 Professional / Ultimate EULA (End User License Agreement) that the computer user must read when starting up a new computer, the following Operating System downgrade rights are available: Downgrade rights for Windows 7 are an end-user right, documented in the Software License Terms that customers accept upon first running Windows software. Windows 7 end user downgrade rights will be available through the sales lifecycle of Windows 7 which is up to two years after the launch date of a new version.  UPDATE:  As of November 2012, Microsoft has upgraded their Windows Lifecycle information, indicating that this upgrade right expires in February, 2014. More information is available from the Microsoft Windows web site and from the attached document.

Issue What Oil can be used for the DWT0001 pocket sensor to prevent problems with condensation? Condensation causes the temperature sensor to corrode. Environment Pocket sensor DWT0001 STP660 Cooling Condensation Cause If a pipe sensor pocket is mounted incorrectly on a cooling system condensation can build up in the pocket and corrode the sensor. Resolution Cooling system sensor pockets should be mounted at an angle to prevent condensation building up in the pocket.  See datasheet for the DWT0001, click here.  For the STP660 click here. The recommended oil to use is either  ‘Fina 'Solco' AC43 or Shell 'Dialo Oil B'.

Issue MicroNet controller objects have a maximum allowable value of 10.000 Environment   MicroNet Meters VisiSat Xbuilder Vista 5 Cause MicroNet controller objects have a maximum allowable value of 10.000 some meter readings require a greater value. Resolution 1. In VisiSat add two counter objects. Link the Rollover pulse output of the first counter to the Count input of the second Counter object. Fig 1. Counter Object 1 is used for the 0 - 999 part of the meter count. Counter Object 2 is used for the 1000 - 1,000,000 part of the meter count. 2. In the Xenta 731 add a Menta object and program shown below in fig 2 is one example. Fig 2. This Menta code multiplies counter object instance 2 by one thousand and adds the sum with counter object instance 1 giving an output for total meter reading of up to 9,999,999. 3. This then can be added to value, graphic ETC pages.    4.  If you would like to download an example click on your preferred option below. Click here for the VisiSat project. Click here for the Xbuilder project.  Click here for the Vista database. Click here for All three.