Building Automation Knowledge Base

Issue Prior to configuring and setting up an Access Expert system, it is imperative that the designated ports required be tested to ensure communications can be established. Product Line Access Expert Environment Premise Install Hosted Server 2012 Cause When configuring an Access Expert system to communicate to either a Hosted or Premise Instance, there are several ports that needs to be opened to establish communications to the server wherever it may be. If these are not opened then the system and the controller's statuses would not be able to be seen when opened from a web browser. Resolution To verify the port settings, please follow these steps: Download the Feenics Network Utility tester from Feenics Download. Note: You must be a registered subscriber of the Feenics website to access the files: https://www.feenics.com/training/lesson/v2-downloads/feenics-network-utility-firewall-port-tester/ Save and run the utility from respective media *** IMPORTANT Run the utility from a PC located in the same network as the AX-SSC, remember, we are trying to see if ports are open for communication between the AX-SSC and its server. Insert the Server address into the location and click on the Test button The results will indicate which ports are opened and which ones are not At least ports 3001 and 4502 need to be opened to get your AX-SSC online with the server. Notes for on premise setup: In the Server Address enter the name or IP address of the on premise server If the tool indicates the port is not opened, check that the Mercury Service is up and running at the server.

Issue Trying to install SSL certificate via Web browser but the 'Install Certificate' button is missing. Product Line EcoStruxure Building Operation Environment Building Operation Webstation SSL Cause User logged into the machine needs to have administrative privileges to install the certificate. Resolution When running the browser, right click on the browser's icon then select 'Run as administrator'

Issue Requirement for a number of users to be able to access Security Expert using Web Client at the same time. Product Line EcoStruxure Security Expert Environment Security Expert Web Client Cause Unsure how many Web Client users are licensed with the standard license or how to add additional user licenses. Resolution Included with the base SX-SRVR license is an allowance for having three (3) concurrent Web Client operators.  Additional operator licenses (SX-WEB-OPR) must be purchased to allow Web Client logins beyond the licensed amount of three, purchase as many of these as is required.

Issue Windows Application logs may be requested by Technical Support to assist with a reported issue. Product Line All Product Lines Environment All Microsoft Windows Operating Systems Cause Unspecified cause. Resolution Press WINDOWS + R on keyboard of the Windows system that the report is to be from. The Windows key is usually located between the CTRL and ALT keys and has a picture of a flag on it. Type Eventvwr.exe and click OK Event Viewer will now start. Expand Windows Logs and then right click on Application. Click on Save All Events As... When prompted save the file as an *.evtx file to an accessible location. Email the *.evtx file to your support representative.

Issue The Modbus IP X Driver can operate in 2 modes Client & Server, can it poll multiple servers in "Client mode", or serve to multiple clients in "Server mode"? Environment Modbus TCP/IP X Driver XDriver IP X-Driver, X Driver, Client Server Cause Clarification required on the functionality of Modbus IP interfaces. Resolution A Continuum controller can only support 1 IP level X Driver. The Modbus IP X Driver can be configured in Client or Server mode but not both (that would require 2 Controllers)  In Server mode the Modbus IP X Driver can serve data out to multiple clients on the same network. In Client mode the Continuum Modbus IP X Driver can co-exist with another IP Modbus client on the same network/ device. It can also poll multiple servers. When polling a 3rd party Modbus IP Server that can also be polled from a second Modbus IP Client, you will need to determine from the supplier if it supports multiple simultaneous sessions. In both Client and Server configurations the number of different sockets (different IP addresses it can talk to) is dependent on the controller used. A bCX1 has a total of 128 IP sockets, but a number of these are used by the regular workstation comms, others can be used for add on options like SNMP alarming, so I would not recommend on communicating with more than around 80 different devices from 1 controller. Currently the NCII only has around 30 available sockets (although this is planned to be increased in a future firmware revision).  

Issue Error displayed: "Extended logging time synchronization problem. The time on the workstation is less than the time of one or more controller log entries," when Workstation tries to download ExtendedLog data from controllers. Product Line Andover Continuum Environment Continuum Workstation (LAN & SU) NetController (CX99xx , BCX9640, BCX4xxx, ACX57xx) InfinetController (i2xxx & First Generation InfinetControllers) Cause Time setting is different between Workstation and Controllers or the time setting is same but the UTC Offset (Time Zone) is wrongfully set between the WS and the Continuum Network object of the controller. Resolution Set the correct UTC offset (time zone) in all of the below locations: Confirm Cyberstation(s) PC time zone (UTC offset) and Windows regional settings are correct. Confirm the SQL Server PC time zone (GMT settings) and Windows regional settings are correct. In Continuum, the Workstations Device objects Time tab has the correct time zone setting (be aware this is in minutes, ex. GMT+10 = +600 minutes). In Continuum, the Network folder has a setting for the time zone, this needs to be configured to the time zone the controllers are located. If GMT+10 then this gets set to +600. Note: See Configure Time Zone and UTC Offset settings so that time is synchronized across your system for more detail on the various locations for UTC settings and what these are required for. Setup Workstation and Controller Time Synchronization: Synchronize the time on all Workstations to a common source. See instructions in Cyberstation Installation Guide under "Workstation Time Synchronization." Synchronize controller time by creating a Program in one of your Cyberstations (only create on one Cyber). This synchronizes the controllers time to the Workstations time once every hour. There are detailed instructions on this in the Cyberstation Installation Guide (with a sample program) under "Controller Time Synchronization." (Also see Time sync controllers to workstations)

Issue TGML graphic uses the NAM Standards component to display a SmartX Sensor Device with a dynamic cover model. The graphic always shows a blank faceplate instead of the correct face - 3 buttons, LCD, or Touchscreen. Product Line EcoStruxure Building Operation Environment SmartX Sensor Device (Living Space Sensor/Room Unit Device) NAM Standards Team Components TGML Library TGML Graphic Thermostat - SmartX Living Space Sensor - Dynamic AppRev1.02.05 Cause A script running inside the graphic component is expecting a well-formatted string representing the cover model on the cover model input binding. If that data is not delivered properly, the component defaults to a blank cover. Resolution Verify that the proper component is being used based on Sensor Firmware. Verify the proper IP controller firmware is installed to meet compatibility with the Host Server and also contain desired features. Once a controller is upgraded and the sensor has had time to upgrade, check the Sensor - Properties - Basic Tab - Application Software version. If greater than or equal to 1.02.05, then use Thermostat - SmartX Living Space Sensor - Dynamic AppRev1.02.05 Otherwise use Thermostat - SmartX Living Space Sensor - Dynamic   The TGML component should work as expected, but factors outside of the graphic can make it not work right. Click on the SmartX Sensor Device and look at Properties > Basic > Status Information > Cover model. Does that show a valid cover model (ex: SXWSCBXSELXX) or does it show ASCII gibberish? If showing nonsensical ASCII string, hotfix firmware is available to address this. Install firmware at or higher than 3.02.03.02109, which includes fix for Defect# 46054 and 47266 affecting the Cover Model SmartX IP Controller v3.02.03.02109 - Firmware Package File Release Date: 2021-Dec-19 https://ecoxpert.se.com/search?documentUUID=6b61d413-5cf8-47c0-ac4d-135391d375bf&title=SmartX%20IP%20Controller%20v3.02.03.02109%20-%20Firmware%20Package%20File Release Notes v3.02.03 - SmartX IP Controller Firmware Release Date: 2021-Dec-19 https://ecoxpert.se.com/search?documentUUID=1e29da8d-cf49-418d-92e5-e022bc4f33c7&title=Release%20Notes%20v3.02.03%20-%20SmartX%20IP%20Controller%20Firmware If the Cover Model is populated with a proper value, a previous firmware upgrade may have caused string values to stop writing properly through the TGML binding. There are two different resolutions to try in this order: Restart the AS-P Delete the SmartX Sensor Device (be sure to select "Keep references") and add it back as a new object with the same name and address.   The binding controlling the dynamic display of different cover models on the graphic can be overridden. Inside the TGML component are 3 groups named "3 Button," "LCD", and "Touchscreen." All are hidden. Find the proper face and change it to default to Visible. Find the Bind named "CoverModel" and delete the binding and script beneath it. This is what is responsible for auto-changing the cover and is no longer needed.

Issue The WorkPlace Tech and WorkPlace Editor add-in for the VisioRibbon is available in the toolbar of Visio but all or some of the functions are unavailable. Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech 5.9.x, 5.10.4 Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio 2010, 2013, 2016, 2019 (WorkPlace Tech 5.10.4 only) Cause There may be one or several of these situations causing this behavior depending on a combination of products installed. The Visio installed is an unlicensed product or in its evaluation period and not registered  The Visio installed is not properly updated There is an error in the WPDispatcher.msi Resolution Review the proper area for the Visio you are using to assure the product is registered; Visio 2010 Visio 2013/2016/2019 If the Visio is part of a subscription-based product, it will be noted as such rather than saying the product is activated. Thoroughly read this Knowledge Base Article for the information required to assure your Visio is properly updated. Workplace Tech 5.9.3 / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office  To correct any possible WorkPlace Tech or Editor (SBO/EBO) dispatcher problems, Follow the path C:\Program Files (x86)\WorkPlace Tech to the WPDispatcher.msi and "right click / Uninstall" Do this for each version of SBO or EBO installed that has Workstation with WorkPlace Tech Editor.  Here is the path C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation X.Y\WorkStation or C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.Y\WorkStation (X.Y will be the version installed i.e 3.1).  Perform the same Uninstall of the WPDispatcher.msi.  The picture below is what will appear if the dispatcher has been removed or was not previously installed.  This message is expected. Open the WorkPlace Tech or the WorkPlaceTech Editor.  The WPDispatcher.msi will run the correct version.

Issue Upgrading Digital Sentry breaks the Video Server connection or cameras won't learn or video streams do not work Product Line Andover Continuum, Pelco Environment Pelco Digital Sentry 7.9 or greater Continuum Video Integration 1.94 SP1 up to 2.01 Windows 7 Windows Server 2008 Windows Server 2012 Cause Pelco released a newer version of Control Point that is used in Digital Sentries Video Recorders 7.9 and above. This newer API is not currently supported in any version Continuum, up to version 2.01. Resolution Available as of July 2017, install version 2.02 of Continuum, it is a full install. R&D has worked on revising the Continuum Video Integration to work with the newer versions of Control Point 7.15 and above. The only work around prior to this to get the video Integration to function was to downgrade the Digital Sentry to Control point 7.8 Uninstall the DS ControlPoint software using Add/Remove programs (MS Windows XP) or Programs and Features (MS Windows 7). Install: How to install the DS ControlPoint client software Note: Upgrading the Continuum Security Key to an Endura Key will not allow the newer API to be used with a Digital Sentry with Continuum. A copy of the latest Video Compatibility Matrix can be downloaded from the Download Center in PA-00568.

Warning COMPLEX PROCEDURE REQUIRED. The resolution of this article has many complex steps that may result in unforeseen results if not performed correctly. If you are at all unfamiliar with the requirements, please contact Product Support Services for assistance. Issue In some situations, when doing a learn on the CX/BCX controller, the learn process aborts and an error prompt pops up, "Can not learn this controller, it contains an unknown model number." Product Line Andover Continuum Environment Cyberstation CX/BCX I2/B3 Cause Learn process has been executed more than once and at least one has not completed. Some controllers that reside in the CX/BCX have not been cleared and have a duplicate infinetID with some controller in the database. Reloading the CX/BCX controller will indicate which controller has the duplicate InfinetID. Resolution It is recommended to create I2/B3 controllers manually (not by learn) to avoid this problem. If this problem happens: Open the BCX/CX controller and click "reset" Reload BCX/CX controller, from the distribution properties window to find out which controller has the duplicated InfinetID Go to the Continuum Explorer, right click the i2/B3 controller which has the duplicated InfinetID and then select "send to text file" Open the text file, change the infinetID for this controller to another number that does not exist in the database. Delete the i2/B3 controller which has the duplicated ID and import the text file. Reload the CX/BCX controller, there will be no more error. Do learn again on the commport of BCX/CX controller, that should execute successfully. For any other installation issues that also result in this error, please refer to Unknown model number error when learning I2/b3 device

Issue Information not available in product documentation. Product Line Satchwell Sigma Environment Windows versions Cause Documentation not updated to show additional operating systems now supported. Resolution Sigma 4.0.8.57, as a front-end user interface, is supported on the following operating systems: Windows XP Pro Service Pack 3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Sigma 4.0.8 (build 80 – 89), as an engineering tool for Sigma when transitioned into SBO/EBO Sigma is supported on: Windows XP Pro Service Pack 3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Sigma 4.0.8 (build 104 onwards), as an engineering tool for Sigma when transitioned into SBO/EBO system Sigma is supported on: Windows XP Pro Service Pack 3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 **1 Windows 10 **1 Windows Server 2012 **1 The additional operating systems support is only applicable when Sigma is part of a SBO/EBO installation. (This confirmation was provided to PSS by R and D).  

Issue On a working system, valid access events no longer show in the active event view and are no longer visible in the accessevent table within the Database.   However, invalid events continue to work normally.  Product Line Andover Continuum Environment Access Events Logging Cause An incomplete object may have been added to the Continuum Database recently that is interfering with queries running against that database. Resolution Try the following steps to troubleshoot the issue Does the issue happen on multiple CyberStations? Ensure all the event types are selected in the active event view that is being used on the door(s). Perform a CyberStation Teach It is best to contact PSS and work with them at this point with the following procedures.   Verify that access events are being sent from the controller to the CyberStation using Wireshark. Verify that the issue follows the Database by loading the database in a test environment to see if the issue still happens.  On the TEST database, use SQL Management Studio:  SQL Query: set acdbversion=0  (execute the query)  Update database: launch Database Initialization Server/Stand Alone Enter sa password and update database Restore database or locate incomplete object The quickest fix would be to revert to a known good database. Once restored, the events in the controllers would be downloaded to the database. Finding the object in the database that has caused the issue can be very challenging. Check to see if there was a controller recently added and if the issue began to happen after that. If for some reason a controller had been added and it wasn't completed normally then it could cause this issue. Check to see if there is a controller in the InfinityController table with an objectidhi or objectidlo with a zero value. If so, delete that controller and see if the valid access events start coming in. It may also be necessary to use the SQL profiler to view the entries that are being made into the database. See the following link  below for  more information. http://msdn.microsoft.com/en-us/library/ms181091.aspx   NOTE: Turning off the Primary and Secondary Access Server will cause the access events to buffer in the controllers, so that these events will be inserted into the database once valid access event logging has been restored. After turning off the primary and secondary, check the Access Log infinity system variable on the controllers. If they are non zero values, then events are buffering. There is a limited amount of access events that can be stored in the controllers before loss of data occurs.

Issue Product specifications and application details for the SE 7000 or SE 8000 range of room controllers are required. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment • Building Operation Workstation • Building Operation Automation Server • SSL SE8000 • SSL SE7000 Cause Full details of the products are required. Resolution The best source of information is in the online Product Selection: Room Controller Selector Tool This tool will allow you to select the correct unit for your application, then from the different tabs you will be able to see: Product Overview, Spec's, Dimensions, related accessories and to download the required documentation from the Links tab. Note: The installation guide can be downloaded from the Links tab and contains detailed application setup, product specification and dimensions. For BACnet versions of the controllers the PIC's statements can currently be downloaded from the Viconics section of the BTL official site using the corresponding VT7xxx part number, see link: BTL Listings for Room controllers Note: The SE8000 and SE8300 Series BTL Certification Listing is anticipated for late 2015.

Issue When starting Continuum version 1.94 (64-bit OS), the main screen is blank.   Product Line Andover Continuum   Environment CyberStation 1.94 (64-bit OS) WebClient 1.94 (64-bit OS) Cause When Continuum is installed on a 64-bit OS, the Main.bmp file is stored in: C:\Program Files (x86)\Continuum\UserProfile  However the application is looking for the file in C:\Program Files\Continuum\UserProfile.   Resolution Configure the Main Menu to search for the Main.bmp file in the correct directory: In the "blank" Main menu, right-click in the white space, and select Edit Right click in the white space again, and select Page Properties In the Background File field, press the "..." button.  In the "Open" window, navigate to the  C:\Program Files (x86)\Continuum\UserProfile directory Select the Main.bmp file.  Press Open Click OK on the Page Edit window In the Edit window, press the Run Page button (looks like a Lightning Bolt) to close the Edit window Re-start Continuum (if necessary)

Issue Information on the features that Video Monitor supports and details on how to configure it on a Continuum Workstation. Product Line Andover Continuum Environment Continuum v1.90 and above. Cause There does not seem to be a specific manual for Video Monitor. Resolution What Is Video Monitor? Video Monitor is CyberStation's powerful video-surveillance tool. Video Monitor, available in CyberStation Version 1.9 and higher, allows you to view live and recorded video images from cameras assigned to doors or points that trigger alarm events. It allows you to monitor doors, immediately capture video images from doors, unlock a door, monitor door status, monitor a person's access to doors, and get alarm information as soon as it happens. You customize the way Video Monitor operates using its powerful configuration tool, Video Administrator. Using Video Administrator, you can attach up to 16 cameras to a door or point. Video Monitor is launched when an event associated with the door or point triggers an alarm. Another video surveillance monitoring tool, VideoLayout, is also available for video matrix-frame viewing. The system may be configured to use either Video Monitor or Video Layouts as your primary video interface to alarms. Also see reference to supported features in the Feature Blast for v1.90 when Video Monitor was first added to Continuum. Configuration There is a large amount of information in the Continuum on-line help files that discuss how to configure Video Monitor in detail. See the Continuum online help contents and search for "Video Monitor."   Note: The Video Monitor option must be enabled on the Continuum Security Key to able to set this up and use it. This comes standard in v1.90 and above and can be enabled on your Key if it is not already.

Issue When trying to save a program in the Plain English editor, you receive the message "Infinity controller error: File took too long to open" Environment Plain English editor Cause This is typically caused because the program in the controller is busy executing a command that cannot be interrupted. Resolution A workaround for this issue is: Right-click within the PE panel of the editor Clicking "Configuration..." Set the program state to Disabled, click OK Save your program Repeat the steps above but select Enabled and then click OK

Issue How do you configure the I/A Series R2 LON Tunnel for operation with the WorkPlace Tech Tool software? Environment I/A Series (Niagara) R2 software, release 4.31 or later WorkPlace Tech Tool Software release 5.x Cause Need information on the entire process of configuring the I/A Series R2 LON tunnel software to work with the WorkPlace Tech Tool software running on Windows XP. Resolution There are four parts to configuring LON Tunneling. A. UNC configuration The UNC must be licensed for vlon (in the features line) Install the VLON jar file into the UNC using the Configure Modules function within the Admin tool Installation Wizard. There are no configuration requirements for the VLonService in the UNC. B. Check for an available LON port in WorkPlace Tech Open WorkPlace Tech but do not open a project. From the "Tools" menu, select "Configure Communications" Select the Lonworks radio button then click [Change] Click the pulldown arrow in the "Select a network interface device driver" selection box. Make a note of the LON ports currently defined.  This list will be used when configuring the tunnel on the PC. Click [Cancel] to close the communications configuration process then close WorkPlace Tech. C. Niagara LON Tunnel configuration on PC Download the "NiagaraLonTunnel.exe" module from The Exchange Install the NiagaraLonTunnel service on the Windows XP PC by running the downloaded NiagaraLonTunnel.exe program. From the Windows Control Panel, open the "Niagara App Tunnel" applet and select the LON tab if more than one tab is displayed. In the LON port name field, select a value not identified in step B.5, above. In the Host Address field, enter the IP address of the UNC. You may enter a UNC station User Name and Password in the two fields or those fields may be left blank. If you have entered a User Name and Password, the Silent Mode checkbox may be checked to prevent the LON Tunnel connection window from being displayed each time the connection is established. Click [OK] to close the Niagara Application Tunneling window. In the Windows Control Panel, double-click on Administrative Tools then double-click on "services". In the displayed list, locate "Niagara LON Tunnel", right click on that entry and click "Restart" in the displayed list. Wait for the Service to restart.  If Windows reports that it cannot restart the service, it will be necessary to close all application windows and restart Windows.  After restarting Windows, continue with part D, below. After the service restarts, close the Services window and close the Windows Control Panel. D. Configure WorkPlace Tech Communications. With the WPT application open,  select the "Tools" menu, then select "Configure Communications". Select the Lonworks radio button then click [Change]. Click the pulldown arrow in the "Select a network interface device driver" selection box Select the LON# port name entered in step C.4, above. Check the "This is a VLon device" checkbox. Click [OK] to save the settings. When you attempt to establish communications with the LON network, the "Niagara Lon Tunneling Logon" window will be displayed if "Silent Mode" was not selected in step C.7. If "Silent Mode" was selected in step C.7 and the UNC login failed, the "Niagara Lon Tunneling Logon" window will be displayed to allow entry of a different user name & password. The connection via the LON tunnel is available for use. 

Issue When a DELR or DELI block is used with a comparison operator to detect a change of value in the output of a function block, the output of the comparison operator should go ON for one scan when the source output value changes. If the source function block is a PVR or PVI this does not occur. For example: This code does not work This code works Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation version 1.3.0 or earlier Function Block Editor Cause There is a defect in StruxureWare Building Operation version 1.3.0 or earlier that causes this behaviour when writing to a public PVR or PVI block in a Function Block Program in the ES or AS directly from the Workstation. Resolution This defect has been logged with Quality Center and will be fixed in SmartStruxure version 1.4.0 Meanwhile, the workaround is to insert any compatible block immediately after the PVR or PVI.  For example: The inserted block could be an operator, an expression block or even another DELR. Although the workaround works, the preferred practice for new applications would be to replace the PVR with a RI and bind the RI to an Analog Value in the ES or AS. This defect does not occur in Menta programs in Xenta controllers, including those written in the SmartStruxure Menta Editor.

Issue In the event of a hardware failure on a Xenta controller you may need to perform a proper replacement procedure in the TAC Plug-In to install the new device. Product Line TAC Vista Environment Vista Xenta Programmable Controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause Hardware failure in an LNS network Resolution In the event you have a piece of hardware fail on your LNS network you will want to follow the steps below to properly replace the device. Remove the bad controller and Install the new controller in its place Open your LNS network in LonMaker or NL220 Select to open the TAC System Plug-In in your network management tool In the Plug-In, locate the bad controller in the tree under the LNS Network pane and right click Select Replace... (the Replace TAC Xenta Device Wizard will open) Click Next Select the service pin button and press the service pin on the new controller Then click Next In the next window, click Next to update your Vista Database (NOTE: If you receive a warning during this process, see Warning about application file replacing a programmable controller in Vista System Plug-In) Once this process of updating your Vista Database is complete you will see the screen below confirming that the update was completed successfully Close the TAC Vista Load window Return to the Replace TAC Device Wizard and click Finish. This will complete the replacement process for your new device In some rare cases not all I/O modules will come online after this procedure. If this occurs a power cycle of the Xenta 400/300 will solve this issue.

Issue How to connect 2-10 Vdc position output signal of an actuator to an analog input of LON or BACnet controllers. Controller’s Analog Inputs are limited to 0-5 Vdc input. Environment WorkPlace Tech I/A Series Lon (MNL) controllers I/A Series BACnet (MNB) controllers Cause Controller’s Analog Inputs are limited to 0-5 Vdc input. Resolution See the WorkPlace Tech Tool Engineering Guide (F-27254-3) Analog Input object discussion (page 129) for reference. Setting up a 2 to 10 VDC feedback voltage divider, use a 120 K (120,000) Ohm in series with a 100 K (100,000) Ohm resistor; connect the UI across the 100K Ohm resistor. As long as the signal never exceed 10 VDC, the voltage across the 100 K Ohm will never exceed 5.0 VDC. Based on the above test results, 10Vdc [actuator output] = 4.545 Vdc [after voltage divider] 2 Vdc [actuator output] = .909 Vdc [after voltage divider] Set-up the Analog Input Object Linput= 0.909 Vdc LScale= 0 Hinput= 4.545 Vdc HScale= 100 Your values maybe different based on the resistor accuracy.