Building Automation Knowledge Base

Issue Modbus XDriver for BCX1-9640/4040 (ModbusRTU_bCX_xxxxxxx.xdr) on comm2 for RS-485 does not work even when the comm2 port says that the driver is installed, no errors and the comm parameters match the Modbus protocol device (ie, 19.2k, n, 8, -). Product Line Andover Continuum Environment bCX1-9640/4040 Controller Modbus XDriver Cause Check the Communication Configuration Point (Function Code 99) of the XDriver. Resolution Function Code 99 is used to select between RS-485 and RS-232 when using a bCX1-9640/4040 controller with Modbus XDriver installed in Comm2 port. Unlike the Modbus XDriver for CX ModbusRTU_2xxxxxx.xdr), the Modbus XDriver for bCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) requires user to set correct value to the FileNumber attribute of Function Code 99 (Communication Configuration Point ). If the FileNumber attribute of the Communication Configuration Point is not set to "1", the Modbus XDriver for bCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) uses the default value, which is "0". When the FileNumber attribute is set to "0", the Modbus XDriver for BCX1-96404040(ModbusRTU_bCX_xxxxxxx.xdr) considers the interface as RS-232. When the FileNumber attribute is set to "1", the Modbus XDriver for BCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) considers the interface as RS-485. For detailed information, refer to the Modbus RTU XDriver User Guide on page15: Function Code 99 – Communication Configuration Point.

Issue After an install of webclient 1.80/1.81 on Windows Server 2003 you receive the following error opening webpinpoint graphics: Could not find pin file at specified URL. Please contact your system administrator. Environment webpinpoint 1.80/1.81 Cause .PIN and .EMF file extensions have not been registered in the IIS MIME Types (for webClient Pinpoint graphics). Also, an IP conflict with another PC can cause this.   Resolution Webpinpoint is installed properly when first opening a graphic, you can browse to the NewGraphicsFiles folder through Internet Explorer and the web folder tab in Cyberstation pinpoint options resolves properly without Red Xs. To fix this, follow the instructions on Pg 32 in the Webclient 1.80/1.81 Installation Guide as follows Registering File Extensions for Server 2003 after IIS Installation: If you have a Windows Server 2003 system, you must also register the .PIN and .EMF file extensions in the IIS MIME Types (for webClient Pinpoint graphics). After IIS installation, follow this procedure: From the Control Panel, double click and open Administrative Tools. The Administrative Tools dialog appears. Double click and open Internet Information Services (IIS) Manager. The Internet Information Services (IIS) Manager dialog appears. In the tree, right click on the machine name, and select Properties from the popup menu. Click the MIME Types button. The MIME Types dialog appears. Click the NEW button. The MIME Types dialog appears with 2 empty fields In the Extension field, enter: .pin and in the MIME type field, enter: pinfiles/plain. Click Ok Click the NEW button again, but in the Extension field, enter: .emf and in the MIME type field, enter: image/emf Click OK three times back through the dialogs. Restart your machine and open webpinpoint

Issue When opening a pinpoint graphic on Cyberstation, Continuum displays the error "Can't Create Empty Document." Environment CyberStation Cause This error may be displayed when trying to create or open a graphic file. May indicate that either the XML parser or the Pinpoint.INI file has been corrupted.  Resolution The fix is to reinstall the XML parser. On the workstation displaying the error, exit Continuum gracefully. Open  Windows Explorer Browse to the C:\Windows Folder Find and delete Pinpoint.ini  (Continuum will rebuild this file on startup). Try to edit or create a graphic file. If the problem persists, the fix is to reinstall the XML parser. On the workstation displaying the error, exit Continuum gracefully. Open  Windows Explorer Browse to the Program Files > Continuum > Install folder Run msxml3.msi Run msxml4.msi If you have an older version of Continuum you may only find msxml3.msi. You should not have to reboot the workstation after the install has completed successfully. Start Continuum You may need to Uninstall Continuun, reboot, Reinstall Continuum If the above doesn't correct the issue, go to a restore point prior to the problem or reformat the hard drive and reinstall Windows and Cyberstation

Issue How to remove, from a Niagara R2 Enterprise Server station, data for all logs prior to a specific date with one command. Product Line TAC IA Series Environment I/A Series R2 Enterprise Server Cause Cloudscape database management Resolution There is a utility that will allow deleting of records before a certain date of all or specific tables in the cloudscape database. The space from deleted records can also be recovered after deleted. This utility is called CloudscapeAdmin and is downloadable from The Exchange Download Center. Download cloudscapeAdmin.jar and place in the x:\niagara\[NiagaraRevision]\nre\lib directory (for Builds 431 and higher). To run this utility the station will need to be stopped. Once the station is stopped, open the console from either the created short cut or x:\niagara\[NiagaraRevision]\nre\bin\console.exe. From here type ‘nre CloudscapeAdmin’ and hit enter to view the commands to use it.  There are two functions that cloudscapeAdmin can do: Delete; The delete command deletes records before a certain date but does not reduce the size used on the disk. The empty area of the database will be filled with new archived data. Compact; The compact command deletes records before a certain date and recovers the space from the disk. This process is slower. Command: nre CloudscapeAdmin x:\niagara\[Niagara Revision]\stations\[Station Name] [User Name] [Password] [delete or compact] [tablename or all] [date] Sample Delete commands: nre CloudscapeAdmin c:\niagara\r2.301.522a\stations\StationName admin admin delete all 2007-07-01 Sample Compact commands: nre CloudscapeAdmin c:\niagara\r2.301.522a\stations\StationName admin admin compact all 2007-07-01

Issue TS-57XX and TS-67XX 10 K thermistor (no 11 K shunt) sensor resistance table Environment Site with thermistor sensor Cause TS-57XX and TS-67XX 10 K thermistor (no 11 K shunt) sensor resistance table Resolution   Temp (°C) Temp (°F)  Sensor Ohms  -40.0° -40.0° 239,700 -39.0° -38.2° 226,000 -38.0° -36.4° 213,100 -37.0° -34.6° 201,100 -36.0° -32.8° 189,800 -35.0° -31.0° 179,200 -34.0° -29.2° 169,300 -33.0° -27.4° 159,900 -32.0° -25.6° 151,200 -31.0° -23.8° 142,900 -30.0° -22.0° 135,200 -29.0° -20.2° 127,900 -28.0° -18.4° 121,100 -27.0° -16.6° 114,600 -26.0° -14.8° 108,600 -25.0° -13.0° 102,900 -24.0° -11.2° 97,490 -23.0° -9.4° 92,420 -22.0° -7.6° 87,650 -21.0° -5.8° 83,150 -20.0° -4.0° 78,910 -19.0° -2.2° 74,910 -18.0° -0.4° 71,130 -17.0° 1.4° 67,570 -16.0° 3.2° 64,200 -15.0° 5.0° 61,020 -14.0° 6.8° 58,010 -13.0° 8.6° 55,170 -12.0° 10.4° 52,490 -11.0° 12.2° 49,950 -10.0° 14.0° 47,540 -9.0° 15.8° 45,270 -8.0° 17.6° 43,110 -7.0° 19.4° 41,080 -6.0° 21.2° 39,140 -5.0° 23.0° 37,310 -4.0° 24.8° 35,580 -3.0° 26.6° 33,930 -2.0° 28.4° 32,370 -1.0° 30.2° 30,890 0.0° 32.0° 29,490 1.0° 33.8° 28,160 2.0° 35.6° 26,890 3.0° 37.4° 25,690 4.0° 39.2° 24,540 5.0° 41.0° 23,460 6.0° 42.8° 22,430 7.0° 44.6° 21,440 8.0° 46.4° 20,510 9.0° 48.2° 19,620 10.0° 50.0° 18,780 11.0° 51.8° 17,980 12.0° 53.6° 17,210 13.0° 55.4° 16,480 14.0° 57.2° 15,790 15.0° 59.0° 15,130 16.0° 60.8° 14,500 17.0° 62.6° 13,900 18.0° 64.4° 13,330 19.0° 66.2° 12,780 20.0° 68.0° 12,260 21.0° 69.8° 11,770 22.0° 71.6° 11,290 23.0° 73.4° 10,840 24.0° 75.2° 10,410 25.0° 77.0° 10,000 26.0° 78.8° 9,602 27.0° 80.6° 9,226 28.0° 82.4° 8,866 29.0° 84.2° 8,522 30.0° 86.0° 8,194 31.0° 87.8° 7,879 32.0° 89.6° 7,579 33.0° 91.4° 7,291 34.0° 93.2° 7,016 35.0° 95.0° 6,752 36.0° 96.8° 6,500 37.0° 98.6° 6,258 38.0° 100.4° 6,027 39.0° 102.2° 5,805 40.0° 104.0° 5,592 41.0° 105.8° 5,389 42.0° 107.6° 5,194 43.0° 109.4° 5,007 44.0° 111.2° 4,827 45.0° 113.0° 4,655 46.0° 114.8° 4,490 47.0° 116.6° 4,331 48.0° 118.4° 4,179 49.0° 120.2° 4,033 50.0° 122.0° 3,893 51.0° 123.8° 3,758 52.0° 125.6° 3,629 53.0° 127.4° 3,505 54.0° 129.2° 3,385 55.0° 131.0° 3,271 56.0° 132.8° 3,160 57.0° 134.6° 3,054 58.0° 136.4° 2,952 59.0° 138.2° 2,854 60.0° 140.0° 2,760 61.0° 141.8° 2,669 62.0° 143.6° 2,582 63.0° 145.4° 2,498 64.0° 147.2° 2,417 65.0° 149.0° 2,339 66.0° 150.8° 2,264 67.0° 152.6° 2,191 68.0° 154.4° 2,122 69.0° 156.2° 2,055 70.0° 158.0° 1,990 71.0° 159.8° 1,928 72.0° 161.6° 1,868 73.0° 163.4° 1,810 74.0° 165.2° 1,754 75.0° 167.0° 1,700 76.0° 168.8° 1,648 77.0° 170.6° 1,598 78.0° 172.4° 1,550 79.0° 174.2° 1,503 80.0° 176.0° 1,458 81.0° 177.8° 1,414 82.0° 179.6° 1,372 83.0° 181.4° 1,332 84.0° 183.2° 1,293 85.0° 185.0° 1,255 86.0° 186.8° 1,218 87.0° 188.6° 1,183 88.0° 190.4° 1,149 89.0° 192.2° 1,116 90.0° 194.0° 1,084 91.0° 195.8° 1,053 92.0° 197.6° 1,023 93.0° 199.4° 994 94.0° 201.2° 966 95.0° 203.0° 939 96.0° 204.8° 913 97.0° 206.6° 887 98.0° 208.4° 863 99.0° 210.2° 839 100.0° 212.0° 816 101.0° 213.8° 794 102.0° 215.6° 773 103.0° 217.4° 752 104.0° 219.2° 732 105.0° 221.0° 713 106.0° 222.8° 694 107.0° 224.6° 675 108.0° 226.4° 658 109.0° 228.2° 640 110.0° 230.0° 624 111.0° 231.8° 607 112.0° 233.6° 592 113.0° 235.4° 576 114.0° 237.2° 562 115.0° 239.0° 547 116.0° 240.8° 533 117.0° 242.6° 520 118.0° 244.4° 507 119.0° 246.2° 494 120.0° 248.0° 482 121.0° 249.8° 470

Issue Which CD Keys can be used with which version of I/NET Seven Software? Product Line TAC INET Environment I/NET Seven - all revisions. Cause Need to know which CD Key can be used with which version of I/NET CD Resolution The I/NET CD Key is comprised of User Name Site Name Key; provided in the format XXXX-XXXX-XXXX-XXXX-XXXX. The key provided above is a 20 character key, segregated into five 4 character sets.  The second set of four characters (shown in bold and underlined above) and using the table below, will help identify which version of I/NET Seven Software works with which CD-Key:   I/NET Seven Version CD Key I/NET Seven 1.xx XXXX-D71R-XXXX-XXXX-XXXX I/NET Seven 2.00 to 2.31 (Excluding 2.30) XXXX-E71R-XXXX-XXXX-XXXX I/NET Seven 2.30 (Only) XXXX-F71R-XXXX-XXXX-XXXX I/NET Seven 2.4x XXXX-F71R-XXXX-XXXX-XXXX

Issue Sites need guidance on how to setup custom ABA cards in Continuum. Environment CyberStation NetController I (CX99xx) NetController II (CX9680) AC1Plus IOU Module ACX57xx Cause The implementation of ABA cards in Continuum access control systems was designed to comply with the ISO 7811 ABA standard for magnetic stripe card. Because of this, the system only reads  one field (the PAN or Primary Account Number) from the ABA card, this field contains a number of up to 19 digits which is used as the card number. Continuum Custom ABA feature provides for maximum flexibility by allowing the 19 digit PAN field on track 2 of the mag stripe to be organized in sub fields such as site code etc. Resolution A summary of the steps to configure Custom ABA cards in Continuum is available through the CyberStation Online Help.  Open the help on the Continuum workstation and search for "Defining a Custom ABA String Format"          

Issue Using a 4-20 mA sensor on a Xenta 451A or 452A Product Line TAC Vista Environment Xenta 451A Xenta 452A Cause There is only enough power onboard a Xenta 451A or 452A for one 4-20mA.  Resolution Wire each sensor, using an external power supply for cases where there is more than 1 4-20mA sensor. Create an AI in the Menta file Bind the object to the 451A Select the correct Terminal Ref Choose the 4..20mA sensor If using this device as a stand alone LON module chose the 4-20 mA option for the nci NOTE: only Xenta devices ending in "A" have truly Universal Inputs.  For complete details on input configuration, see Configuring inputs on Xenta 421A or Xenta 451A when using the controller as a stand alone Lonworks node.

Issue When attempting to use Serial Tunneling through an I/A Series (Niagara) G3 system ENC, the following error message is displayed in the Application Director window: ERROR [....][Serial Helper] Denied Opening comm port 'COM1' javax.baja.serial.PortDeniedException: COM1 is already owned by dbgjmpr Environment I/A Series (Niagara) G3 ENC-520, ENC-410. Cause This error is reported when the operating system console enable jumper is installed on the front two pins of the MODE connector in the upper right corner of the ENC circuit board.  NOTE: This jumper is installed only when using a serial terminal running at 57600 baud and connected to serial port COM1 to troubleshoot ENC operating system startup / IP address issues. Resolution Remove the jumper and reboot the ENC.

Issue Need the Part Number for a Xenta 527 or 527-NPR Environment I/NET Vista Cause There are 2 Varieties of the Xenta 527 available: The Xenta 527 and the Xenta 527 NPR. While these devices share some similarities, there are some key differences. Resolution There are 2 Varieties of the Xenta 527 available. The Xenta 527 and the Xenta 527 NPR. The Xenta 527 is sometimes referred to as the Xenta 527 - Web Server.  This part can be used on I/NET systems, or I/NET systems that integrate with Vista.  The Xenta 527-NPR is use on I/NET systems.  It is a scaled down version of the standard Xenta 527 that will only provide the functions needed for I/NET.  This serves as a direct replacement for existing NPR devices. The Part numbers for these devices are as follows: Xenta 527 (Web Server) - 007308200 Xenta 527 (Web Server) Package of 3 - 007390130 Xenta 527-NPR - 007308210

Issue Require details on how to setup two inputs to pop up a camera window when both inputs are True. Product Line Security Expert Environment Security Expert Cause Unsure how to setup programming for two inputs to display video from one camera when both inputs are set to true. Resolution Need to create: 3x Virtual Outputs 1x Programmable Function 1x Input Type 1x Area 2x Inputs 1x Event Filter 1x Action   Instructions: Virtual Outputs Under Programming | Outputs create three (3) new outputs. Set Module Type to "Output (PX)" Set module address to "31" or greater. Set Module Output to "1", "2" and "3" respectively. Save the changes.   Programmable Function Under Automation | Programmable Functions create a new Programmable Function. On General tab select Type "Logic Control". On "Logic Control" tab select Logic Function Mode "7 - Follow Logic AND". First Output To Check, your first created output. Second Output To Check, your second created output. Output To Control, your third created output. Save the changes. Right click the new Programmable Function you just created and select "Start".   Input Type Under Programming | Input Type create a new Input Type. On Options (1) tab select Generate Alarms, Generate 24HR Alarms. On Options (3) tab select Activate Inout Control Output On Alarm, Deactivate Input Control Output On Restore. Save the changes.   Area Under Programming | Areas create a new Area. Important: Ensure this Area is always armed. Save the changes.   Inputs Under Programming | Inputs create your two inputs (or edit two existing inputs). On General tab set the Control Output of your first input to the first virtual output you created earlier, the second input to the second virtual output. On First Assigned Area, Areas and Input Types tab set Area to the area created previously, Input Type to the Input type created previously. Save the changes.   Event Filter Under Events | Event Filters create an Event Filter. On Event Types tab unselect "Include All Event Types" and add "Output On By Programmable Function" (both of the options) that show under All Output Events. On Record tab Add a new record. Select Device Type to be "Output", Controller to your controller, then select the third virtual output you created and press "Add". Save the changes.   Action Under Events | Actions create a new Action. Set Type to "Popup Camera Window". Set Event Filter to the event filter you created earlier. Set Popup Camera to "Select Camera from List". Set Camera to the camera you want to show video from. Save the changes.

Issue DBCreate database restore fails with error message: "The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally." Product Line TAC INET Environment I/NET Seven SQL Server 2000 all editions and SQL 2005 all editions Cause It is not possible to restore a SQL Database which was backed up using SQL 2005 back into a SQL 2000 database. Resolution The simplest method to rectify this problem would be to uninstall I/NET and SQL (Refer to Procedure for uninstalling I/NET Seven on a stand-alone host on how to do this) and then re-install I/NET using SQL 2005. The second method would be to upgrade the installed MSDE Default instance to SQL 2005 Express. There is a published white paper from Microsoft on this and is attached here: MSDEtoSQLExpress.doc.  Refer to the steps on page 11 to 14. The SQLExpress installation file is available on the I/NET CD under the folder SQLExpress\.SQLEXPR32.EXE. After performing these steps its advisable to run up DBCreate and upgrade the SQL database.

Issue Running SevenReports a C++ Run Time error. Happens either in Archive data reports or database reports yyyy-mm-dd hh:mm:ss Environment I/NET Seven version 2.16 to current Cause Scope of Data yyyy-mm-dd hh:mm:ss Resolution    The C++ Runtime error or crash of SevenReports is due to a timeout problem because the archived data is so much information. What you will need to do is a couple of things listed below: Run the archive file SevenReport or ArchiveSevenReport file with the following steps in mind 1. If using Archived reports, mount the archive file with the desired dates to search 2. when the date range comes up on the screen, offering to search with date, hour, minutes, and seconds yyyy-mm-dd hh:mm:ss limit the time range. The whole key here is to limit the time range. Example of range is below.   In other words, search for only 2 minutes on just one day. Do not put in three days, or three hours. Only search within a very limited search window. The crash occurs because there are huge archive or database entries with thousands of transactions that have to be sorted and searched through. The crash was due to the report program attempting to generate a report with to much data to sort through. Be patient. Even on old computers, with XP, 500MB or RAM, and limited resources, the reports will be produced.  Time and time again, this issue comes across. Using my old computer in the lab, the database from the customer is loaded, the archive files are loaded and still it works every time. The C++ Run Time error appears when expanding the search to more data and crashed the report. But limiting the amount of time to minutes or perhaps one hour, produces a report. (For an example of unusual examples: there have been 2 minutes of time for the search criteria, and 38,000 pages of report produced.)     2010-08-16 09:00:00 until 2010-08-16 09:02:00   One thing you may want to look into at your site if you are experiencing large amounts of data for reports is Scan Interval. Read TCON300 for more info. Information on Scan Interval and how this information is collected in the database. This is important because the more data you collect, the faster the scan rate interval, the more data will be in the reports. Input and Output Points Point Database Parameters   The Scan Interval field is used with all point types. Enter a number between 1 and 255. This is the length of time in seconds that elapses between point scans.   If the point is an external input point, the controller scans the point at the interval you specify here, and updates its state/value in RAM memory of the DCU.   If the point is an external output point, or an internal input or output point, the scan interval determines how often a calculated point equation controlling the point (if applicable) is processed.   If the point is an indirect input or output point, the scan interval governs the time it will take to go to the “old data” state.   The default scan interval is 10 seconds for input points and 60 seconds for output points. All points can have their own unique scan intervals. All external discrete input points are scanned for discrete contact changes at 100 millisecond intervals.   Note: Defining an individual scan interval reduces available RAM memory in the DCU by approximately four bytes. You can conserve DCU memory by using the same scan interval for multiple points.

Issue When using a USB to RS-232 adapter and an MN-CIM, cannot connect to MicroNet 2000 controllers. Receive an ERROR = -510. The problem has also been seen on laptops with an integral serial port. Environment Laptop computer running the MN-CI or MN-FLO-BAL software tools,  any version MN-CIM Controller interface Module Cause One cause of ERROR = -510 is that the serial port or USB to RS-232 adapter does not supply enough power to the "port-powered" MN-CIM. When the CI software is running, but not communicating on the U-LINK, it requires only 12 mA at 5 VDC. To communicate on the U-LINK, the MN-CIM requires 14 mA at 5 VDC from the DTR control line of the port.  Some computers have a mechanism to sense the increased current draw and shut down the DTR line. This loss of power causes the MN-CIM to reset, and after 3 attempts to communicate the MN-CI software issues the ERROR= -510 message. Resolution See Technical Bulletin 01-104 for information  on the Patton Electronics power supply adapter, model 3PMF9-BC.

Issue A replacement for VisiView is required. Environment Satchnet VisiView Cause The VisiView software is now obsolete. Resolution VisiView can be replaced using a SmartStruxure Automation Server or TAC Xenta 555 Web server. Both the SmartStruxure Automation Server and the Xenta 555 provide web interfaces so that the customer can view their HVAC equipment graphically using an appropriate Web browser. Both the SmartStruxure Automation Server and TAC Xenta 555 Web server communicates with either IAC or Micronet controllers. Further information on the Micronet Transition to SmartStruxure can be found in PA-00228 The Xenta 555 is programmed using TAC Xbuilder, which allows data to be presented in a graphical format. Further information on the Xenta 555 can be found here.

Issue When starting Vista software (other than Vista Server) an error appears stating that the license has expired. lc_checkout failed: Feature has expired. Feature: Menta.View Expire date: 31-May-2011 License path: C:\Program Files\Schneider Electric\License Files\Demo_5_1_31_may_2011.lic FLEXnet Licensing error:-10,32 For further information, refer to the FLEXnet Licensing documentation, available at "acresso.com". Product Line TAC Vista Environment Vista Workstation Menta TGML Editor Vista Webstation Cause The temporary trial license for Vista has an expiration. If Vista returns an error stating that the license is expired this may be due to one or more of the following reasons: The temporary license file being used has indeed expired Vista was pointed to a temporary license file that has now expired rather than being pointed to the license files folder The computer date is set incorrectly Resolution Start by checking to see that the computer date is set correctly. If it is set to a future date beyond the expiration date of the temporary license file this will prevent Vista from starting up. Check to verify that the temporary license file being used has not expired by opening Windows Explorer and browsing to the following folder: C:\Program Files\Schneider Electric\License Files or C:\Program Files\TAC\License Files if this is an older installation. The expiration date of the file is part of name of the file. For example, Demo_5_1_31_aug_2011 expires on the 31st of August, 2011. The terminal services licenses need to be updated every two weeks and the expiration date can also be found in the file name in a week-of-the-year format. The easiest way to find the exact date is to open the license file in a text editor  and the expiration date can be found in the first line. For example, the first line of the license file Demo+TS_OK_5_1_valid_through_week32_2011 is: "FEATURE Vista.Workstation taclic 5.1 14-aug-2011 uncounted \" therefore this license expires on the 14th of August 2011. If the exact license file rather than the license location was specified during installation, Vista may not be able to find a new temporary license file once the old one expires. The location where Vista looks for the license should be cleared out by following the steps in the resolution of Switching from the Demo license to the site License in Vista 5.1.7 or older. Once the registry value has been cleared Vista will ask where the license is found the next time it is started up.

Issue Method to load controller dump file (.DMP) or Personnel import file (.CSV) into Continuum from a DOS command line.  (LOAD CMDLINE.EXE PE) Environment Continuum Cyberstation Cause Need to import data into Continuum automatically on a regular basis. Resolution This will be a two stage process, a program in the Cyberstation (Workstation) that uses the "Load" command and a trigger from outside Continuum using CMDLINE.EXE.   1. Workstation Program Use a variation of the following Fall thru program to import your dump file into Continuum. ===== Start Code ============== 'Fallthru Program created in Cyberstation. 'Called manually from command line "run LoadDumpFile" line 1 print "Line 1 - got here, going to line 2 - ", date goto 2 line 2 print "Line 2 - got here, attempting to load file" load "c:\CntrlDump.dmp" -o -x print "Line 2 - end - check distribution properties for status" ===== End Code ================   2. Trigger to run program. As for the CMDLINE.EXE options, options used for the ReportCmdLine.exe program and have successfully run the CSV import program from an MSDOS command line. At the DOS prompt type the below. This produces the same result as performing "run LoadDumpFile" at the Continuum command line: "C:\Program Files\Continuum>cmdline.exe" /o Root\FoderForWks253\LoadDumpFile /u acc /o switch is the location of the object in Continuum. /u is the Continuum user that has access.

Issue When trying to log into Workstation you get "Access is denied". Environment Vista Workstation Windows 10 (not supported) Cause First verify that the licensing is installed and working properly on the machine. If running Vista on a Windows 10 machine and the message "Access is denied" still appears when logging in to Workstation then there may have been Windows updates applied to the PC causing the issue. Microsoft has identified an issue with their updates and have plans to correct them in future updates.  Note: Windows 10 is not a supported operating system for TAC Vista.  Resolution If using Windows 10 with TAC Vista, then check to make sure that the following updates have not been installed (updates depend on the Windows 10 build being used).  If one of these builds have been identified then remove the Windows Update and restart the PC. After the reboot, the operator should now be able to log in to Workstation.   Windows 10 1709: KB4056892 Windows 10 1703: KB4056891 Windows 10 1607: KB4056890 Windows 10 1511: KB4056888 Windows 10 1507: KB4056893   Note: There has been a couple of instances where the Windows Upload and blocked access on a Window 8 PC as well.  If the same error is seen in Windows 8 then check for recent Windows updates. Click Here if you are having issues with the updates coming back.

Issue Liebert CRAC units will store multiple binary alarm points in one 8 bit Modbus register. How can I read each bit and set values for each alarm point in Continuum? Environment CyberStation Modbus RTU Xdriver Liebert CRAC Units bCX and CX controllers Cause Liebert CRAC units will store multiple binary alarm points in one 8 bit Modbus register. How can I read each bit and set values for each alarm point in Continuum? Resolution Using a PE program you can efficiently poll one register and update multiple alarm points in Continuum. The attached program polls the Modbus Xdriver to get the value of an xdriver point just once and then sets the value to the local numeric ReadRegister###.  The individual bits of the ReadRegister### are then written to the alarm points. This reduces the number of polling requests to the xDriver for the same point A dump file for the points referenced in the program is also included in the attachment.

Issue Display options now the DCX250 is no longer available Product Line Andover Continuum Environment Continuum DCX250 Touch Screen Display part number 01-0008-300 Cause The DCX250 is not available from January 2012: Discontinuation of Infinity 01-0008-300 (DCX 250) - PA-00184 Resolution There is no direct replacement for the DCX250 and there is no other display that works directly on Infinet.   The Continuum display options are- Netcontroller IO Bus - Infistat or LD-1 Direct connection to some controllers - Smart sensor or xP-Display A Continuum Cyberstation could be used if more information and input is required. Another option would be a Bacnet or Lon display. Or, the L-VIS from Loytec using bacnet MSTP may be such an option (LonWorks and BACnet Touch Panels Release - PA-00106). http://www.loytec.com/products/lvis (LON via NC2-F- port16 would also be an option, see Can LONMark Devices be used with Continuum?) NOTE - All support for this product is via Loytec. The EMX170 was a small display and keyboard available for some older Infinity Controllers (i1) This unit is obsolete, although it may be possible to repair one. There is no replacement for this unit. If the i1 controller is being replaced with an i2 unit then either a smart sensor or an xP Display plus room sensor could be used