Issue WorkPlace Tech 5.8.x, 5.9.x, and 5.10x Operating System and Microsoft Visio Compatibility Product Line TAC IA Series Environment WorkPlace Tech Tool Software release 5.8.x, 5.9.x, and 5.10x Microsoft Windows and Microsoft Office Visio requirements, see the "Resolution" section, below. Cause What Microsoft Windows operating systems and what versions of Microsoft Visio are compatible with the WorkPlace Tech Tool version 5.8.x, 5.9.x, and 5.10.x? Resolution Microsoft Windows WorkPlace Tech Tool release 5.8 through 5.8.6 is certified to run on the following versions of Microsoft Windows: Microsoft Windows XP Professional with Service Pack 2 or Service Pack 3 Microsoft Windows Vista 32-bit Business, Ultimate or Enterprise Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional WorkPlace Tech Tool release 5.8.7 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool release 5.9.1 to 5.9.4 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 7   32-bit Professional Microsoft Windows 7   64-bit Professional Microsoft Windows 8.1   32-bit Pro or Enterprise Microsoft Windows 8.1   64-bit Pro or Enterprise Microsoft Windows 10    32-bit Professional Microsoft Windows 10    64-bit Professional Microsoft Windows Server 2012   64-bit WorkPlace Tech Tool release 5.10.0 to 5.10.x is certified to run on the same as WorkPlace Tech 5.9.x and the following versions of Microsoft Windows: Microsoft Windows Server 2016 64-bit Microsoft Windows Server 2019 64-bit Microsoft Visio Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8 32-bit Pro or Enterprise Microsoft Windows 8 64-bit Pro or Enterprise Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool release 5.8 through 5.8.6 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WPT 5.8.0, WPT 5.8.1, no known issues with WPT 5.8.2 through 5.8.5) Microsoft Office Visio 2007 with Service Pack 1 or Service Pack 2 Microsoft Office Visio 2010 with or without Service Pack 1 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.8.7 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2007 with Service Pack 3 Microsoft Office Visio 2010 with Service Pack 2 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.9.1 through 5.9.4 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2010 with Service Pack 2 Microsoft Office Visio 2013 with Service Pack 1 Microsoft Office Visio 2016 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool releases 5.10.0 through 5.10.x requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2016 Microsoft Office Visio 2019 Microsoft Office Visio Office 365 Subscription Plans Note: Workplace Tech Tool 5.10.0 and future releases will require .NET Framework 4.8 to support Open LDV 5.1 which is included in the installer.  .NET Framework 3.5 Sp1 is no longer required.   Follow instructions in the article link for security updates required. Workplace Tech 5.10.x and previous / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office For the Visio requirements for earlier versions of the WorkPlace Tech Tool software, see What versions of Visio are required for WorkPlace Tech?.

Issue WPT and WPTE require certain Microsoft Security updates for Visio and for Office running on the host machines. Issues currently observed: Different and various functions in the fluent ribbon do not work or the ribbon does not appear. Following error "Application compile failure during save operation" is seen when saving/compiling an application in WorkPlace Tech Editor Product Line EcoStruxure Building Operation, TAC IA Series Environment Visio 2010, 2013, 2016,(.msi install) Visio 2019 is not supported in 5.9.4 or EBO versions.  Visio 2019 is supported when using Workplace Tech 5.10 only. Visio 2013, 2016, 2019 (subscription "Click to Run", Plan 1 or 2) Office 2010, 2013, 2016 (.msi install) Office 2013, 2016, 365 (subscription "Click to Run" , Plan 1 or 2) Support for Workplace Tech 5.10 / previous and Workplace Tech Editor Cause Interoperability of Visio and Office can cause problems with Workplace Tech and Workplace Tech Editor if these MS16-70 updates are not applied.  If the Office / Visio product is "Click to Run" the software has not been updated to the latest version. Resolution Install the updates from Microsoft Security Bulletin MS-16-70 Visio 2010 32 bit KB3114872       Office 2010  KB3115198 select 32 bit  Visio 2013 32 bit KB3115020       Office 2013  KB3115173 select 32 bit  Visio 2016/2019 32 bit KB3115041       Office 2016  KB3115144 select 32 bit NOTE:  If the Visio or Office is "Click to Run" (subscription such as Office 365, Plan1 or 2) rather than from a Microsoft Office .msi, the product should be upgraded by using the Update Options feature If you try and install the KB/.msi install patches, you will get this message

Issue What versions of Visio are required for WorkPlace Tech? Product Line TAC IA Series Environment WorkPlace Tech Microsoft Office Visio (32-bit version only) Cause Software requirement - Microsoft Office Visio must be installed on the computer before beginning the installation of WorkPlace Tech. Resolution Below is a list of the WorkPlace Tech revisions and compatible Microsoft Visio versions.  The "Pro" versions are not required.  The "standard" versions of Microsoft Visio are typically recommended.  Only the 32-bit versions of Visio are supported. WPT Visio 3.1 Visio 5 Technical Plus 3.2 2000 SP1 4.0 2000 SP1 , 2002 SP1 5.0 2002 SP1 , 2003 SP1 5.1 2002 SP1 , 2003 SP1 5.2 2002 SP2 , 2003 SP1 or SP2 5.3 2002 SP2 , 2003 SP1 or SP2 5.4 2002 SP2 , 2003 SP1 or SP2 5.5 2002 SP2 , 2003 SP1 or SP2 5.6 2002 SP 2 , 2003 SP1 or  SP2 5.7 2003 SP3 , 2007 SP1 5.8.0 to 5.8.5 ** 2003 SP3 , 2007 SP1 or SP2 , 2010 SP1 5.8.6 2007 SP1 or SP2 , 2010 SP1 5.8.7 2007 SP3, 2010 SP2 5.9.1 to 5.9.4 2010 SP2, 2013 SP1, 2016 5.10.0 2016, 2019, Office (Visio) 365 Subscription Plans ** Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WorkPlace Tech 5.8.0 and 5.8.1, no known issues with 5.8.2 through 5.8.5)

Issue What are the email addresses used for I/A Series license requests? Product Line TAC IA Series Environment I/A series license Cause Request license to upgrade existing devices. Resolution All TIP and end customer WorkPlace Tech license requests and Niagara license requests are emailed to: bms.licensing@se.com

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 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 The Echelon LonTalk PCC-10 PCMCIA Network Adapter will not work with a Dell E6410 laptop. Product Line Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Echelon LonTalk PCC-10 PCMCIA Network Adapter Dell E6410 laptop Cause Dell E6400 Chipset Resolution To correct this, an entry needs to be added into the Windows registry. Option 1 Download a Windows registry import file from The Exchange. Navigate through Products > Satchwell > Sigma or MicroNet > Downloads > Hot Fix (Or you can download the file here RegedittoaddPCMCIACard.zip). Once downloaded, double click the file and the entry will automatically be added. Reboot the computer before the entry is read. Option 2 Manually add the entry into your registry. Use caution when making changes to the Windows registry. Mistakes can be fatal to the operating system. To manually add the entry, carry out the following: Go to Start > Run and use “regedit” to open the Windows registry. Navigate through to HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet Services Pcmcia Parameters Add a new DWORD entry called “IrqRouteToPciController” Modify the new entry and give it a hexadecimal value of 8 Reboot the computer before the entry is read. If option 1 or 2 do not resolve the issue, it may be necessary to perform the following:  Option 3 Open the registry editor. Go to the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2} or HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2}\0000 and look for the key name "PcmciaExclusiveIrq". Delete the key name "PcmciaExclusiveIrq" (If it exists). You may need to reboot the PC. Further information may be available in the Echelon Knowledge Base on the Echelon website. This information can be found in Solution: KB763. For more information, please refer to TPA-SACH-10-0009.00 - LON PCC-10 PCMCIA Card with Dell E6410 Laptop

Issue The xif file needs to be uploaded without LNS Management Tool All the devices on the LonWorks network needs to be searched The device mode or state needs to be changed Product Line TAC Vista Environment LonWorks Network Cause A LonWorks network test and diagnostic tool are needed. Resolution NodeUtil is a Windows console application that can be used with Echelon’s family of network interfaces (including the PCLTA-20, PCLTA-21, PCC-10, i.LON® 10, i.LON 100, i.LON 600, Loytec Devices, SmartServer, SLTA-10, U10, and U20 network interfaces) to diagnose and configure LonWorks® network interfaces, routers, and devices. NodeUtil is a test and diagnostic tool - it is not a network management tool.  It will not assign destination addresses or bind network variables. Nor will it format LonMark® interoperable device information. This tool can be used in the following conditions: The xif file needs to be uploaded without LNS Management Tool All the devices on the LonWorks network needs to be searched The device mode or state needs to be changed Other network test and diagnostic need This software can be downloaded at http://www.echelon.com/support/downloads/detail.aspx?partNum=153-0373-01A The username and password are needed. This site is opened to the public for registration, so everyone can obtain it. Once you are logged in by default "Recommended Downloads" will be selected. Select "Development Tools" instead to locate the NodeUtil software.

Issue After installation of G3 Workbench version 3.4.57 or 3.5.25, the Software Manager on the Localhost may display that the sun-jre-win-x86 VM module is out of date: Environment Niagara G3 version 3.4.57 or 3.5.25 Sun JRE VM Module Cause While this is not a fatal error condition, the module can be updated. NOTE: if the installed version is 3.5.25, replace path references to "3.4.57" in the paths with "3.5.25" Resolution Shut down Workbench Open Windows Explorer, and navigate to the C:\niagara\niagara-3.4.57 directory Rename the jre folder to jre.old Now, navigate to the C:\niagara\niagara-3.4.57\sw\1.6.0.20 directory. Using WinZip, open the sun-jre-win-x86.dist file (or the sun-jre-win-x64.dist file if using the 64-bit version of Workbench). Select all of the folders in the archive, and extract them to the C:\niagara\niagara-3.4.57 directory (see below). Make sure that the “Use folder names” (or equivalent) box is checked. After the extraction, a new jre folder is created. Run the Platform Daemon (Start > Programs > Enterprise Network Server 3.4.57 > Install Platform Daemon) Open Workbench, and then open the Software Manager in the Platform. The Sun VM will now show "Up to Date"  

Issue Define I/A Series AX/G3/N4 software compatible with a specific version of Windows Product Line TAC IA Series Environment I/A Series (Niagara) AX/G3/N4 software Windows 32-bit and 64-bit operating systems Cause Only specific releases of the I/A Series AX/G3/N4 software have been certified compliant with specific versions of the Microsoft Windows software. Resolution The following chart details the version compatibility between the releases of the I/A Series G3/N4 software and various versions of the Microsoft Windows Operating System software.   Refer to Supported Operating Systems for Niagara 3.7 and earlier (June 2016) Refer to Supported Operating Systems for Niagara 3.8 (July 2020) Refer to Supported Operating Systems for Niagara 4.1, 4.2, and 4.3 (September 2019) Refer to Supported Operating Systems for Niagara 4.4 and higher (July 2020)   For the larger Schneider Electric BMS offering please refer to Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation

Issue Are the Network 8000, DMS, and Signal manuals available in an electronic format? Environment Network 8000 DMS Signal Cause Option to view Network 8000, DMS, and Signal manuals in electronic format. Resolution The Network 8000, DMS, and Signal manuals are available from the Publication Zone via iPortal. They are, also, available on a CD. The "Legacy zip" link downloads and extract the files, if running the program from a computer or creating the CD. When running the program from a computer, launch "index.html" located in the extracted bin folder. Email legacy product documentation requests to be added to the Legacy CD, to Product Support.

Issue What is the recommended method to upgrade a Niagara R2 station to a newer version? Product Line TAC IA Series Environment I/A Series Niagara R2 Cause Unsure how to upgrade station databases. Resolution The published upgrade procedure is provided in F-27334. Below is a modified method that also works. Doing station upgrades on the server first is preferred. If there are any errors, they can be addressed without operational interruptions. Using the existing version of WorkPlace Pro (WPP), backup ALL of the UNC and Server databases into XML format. Methods of backing up and converting databases. Open the Enterprise server in WorkPlace Pro. Double click the station name. Select "Commands" and "Backup XML to save the server in XML. Then select "Backup Subordinate XML" to pull all of the UNC databases as XML into the server stations folder.   If not on site but the UNC and Server databases are available, use the DB Admin tab of the Admin tool to convert the databases locally to XML. Now install the newer Niagara revision onto the Server. Copy the stations containing the XML files to the desired WPP revision station folder. Enable and open the new revision of WPP. Use the Admin Tool to convert locally all of the stations from XML to DB. (If there are any errors, they can be addressed without affecting the running installation.) After all the databases have successfully converted to DB, convert them to SNS. (This saves time later if the UNCs need reloading) Use the Enterprise Server to upgrade the UNC. During the upgrade process of the UNC it will ask to backup the database. If the database had upgraded with no issue in the previous step, enter the username and password to proceed with this backup. This will backup the station, upgrade the UNC, and then upgrade and reinstall the station. The previous station upgrade will be needed only if there is an issue. If after following this procedure the station still fails to start, contact Product Support Services.

Issue The Momentary Start / Stop (SS) object in a MNB controller is not working. The OutStrt output property remains ON and does not pulse off. Product Line TAC IA Series Environment MNB controllers Cause Application programming Resolution The OnPulse input property is set higher than the required minimum of 2 seconds.  In order for the logical outputs to work (OutStrt & OutStp), physical hardware tags must be assigned to the physical outputs (AddrStrt & AddrStp).  This is required when using the Momentary SS object in any MNB controller. The following logic can be used in place of the Momentary SS object to generate an equivalent OnPulse.  

Issue The MNB-Vx appears in the Workplace Commissioning Tool in a read-only mode. After downloading a MNB-Vx controller, an error window appears stating "The download was completed but the application was invalid. The device is now running the factory default application". Product Line TAC IA Series Environment MNB-Vx Workplace Commissioning Tool Cause This condition is related to improper AC power provided to the MNB controller. Typically, when AC power drops below 20 Vac, the controller will fall back to a factory-installed application and switch to read-only mode in the Workplace Commissioning Tool. Resolution Fix the AC power supply so that it is within specifications for the MNB controller. Do a hardware reset using the dip switches to get it out of read only mode. Try the download again.

Issue How to display the degrees symbol (°) in WorkPlace Tech. Product Line TAC IA Series Environment WorkPlace Tech Cause Helpful to add a suffix for temperature engineering units. Instead of typing "degrees" or "deg". Resolution In the Constant Object properties (double click or right click - Set Value), click in the Suffix Text field.    Desktop PC: If you have a desktop PC with a full keyboard, press and hold the Alt key and type the number 248 on the numeric keypad. Note: The number keys above the keyboard will not work. Notebook PC: The numeric keypad on a notebook PC is overlaid on the letter keys (M, J, K, L, U, I, O, 7, 8, 9), and requires that the Fn key is held down while using this secondary purpose. The Fn key may be colored blue to match the number keypad keys. Press and hold both the Alt and Fn keys and type the number 248 (KU8). Release the Alt key (and Fn key on the laptop). A small circle ° (the symbol for degrees) should appear. Type an upper case F for Fahrenheit or C for Celsius. Click OK.   Other ASCII symbols are defined at asciitable.com or lookuptables.com.

Issue How can two Niagara G3 stations run simultaneously on a computer? Product Line TAC IA Series Environment Niagara G3 PC Cause To run two stations simultaneously on a PC, you must set up two ports to be different: The http port and the Fox port. Resolution Open the second station offline via My File System – Sys Home - Stations. Go to Services – Web Services – Properties – Http Port. Change it from 80 to 8080. In the offline station, go to Drivers – Niagara Network – Properties. Expand the Fox Service and change the Port to 1912. Be sure to save the changes and the bog file. Go to Platform – Application Director. Start the second station that you just edited offline. You should see the new ports under "Details."  Go to File - Open Station. Enter the IP address, but change the port to 1912. You should now be able to go to the Niagara Network and discover one station from the other on the same IP.

Issue How can a connection be traced in a WorkPlace Tech drawing when it is difficult to see the wire path? Product Line TAC IA Series Environment WorkPlace Tech Cause When working with objects that have numerous connection wires (perhaps an uploaded drawing), it may be difficult to see the wire routing path. The link style is too small, which may be difficult to see the wire routing path. Resolution Click on a wire to select it (green handles appear). Two clicks may be required, since the first click selects the object that the wire is from. Right click on the wire and select Format/Style. In the Line Style pull-down menu, select "Error Box" (a heavy red wire). Click OK Trace and edit the connections as needed.

Issue In Niagara G3 Workbench, how can the size of the wire sheet be adjusted? Product Line TAC IA Series Environment Niagara G3 Workbench Cause Locating the settings to configure the Wire Sheet width and height to increase or decrease the view. Resolution Wire Sheet maximum size limits Starting in NiagaraAX-3.6, you can limit the size of the wire sheet by setting size of the wire sheet in the Options dialog box. From the workbench main menu, select Tools > Options to open the dialog box. Then select the Wire Sheet option and enter a desired maximum value in the Max Width and Max Height fields, as shown, below. Click the OK button to complete the setting change. If you decrease the maximum wire sheet size, objects are repositioned to stay within the view, after the size change. Note: You may need to refresh the wire sheet view to see the changes in wire sheet size and object repositioning. Also, the wire sheet borders may not be visible until you zoom out in the wire sheet view.  

Issue In WorkPlace Tech, monitor tags can not be placed into the open application. They disappear and there is no error message. Product Line TAC IA Series Environment WorkPlace Tech Cause A layer being turned off in error and need to configure the layer setting to Visible. Resolution Below are steps to resolve the issue: Close WorkPlace Tech. Using Windows Explorer locate the VSD file, right click it, and clear the read-only and archive flags.   Open the drawing in Visio. Select "Customize" from the "Tools" drop-down menu. Highlight "Menu Bar" on the Toolbars tab of the Customize window and pick "Reset". Close the Customize window. Select "Drawing Explorer Window" from the "View" dropdown.   Expand Foreground Pages - Device Definition - Layers. Right-click RealTimes and enable Visible.   Close the "Drawing Explorer Window". Save and close the file. Insert monitor tags will now work.

Issue How can a WorkPlace Tech application be identified as created/edited with version 3.2sp1 (or older) so it can be converted by WPT 4.x or WPT 5.x? Product Line TAC IA Series Environment WorkPlace Tech Cause Jobsite with an installed base of MNL or MNB controllers but the version of WorkPlace Tech used is not known. Resolution NOTE: Do not allow the application to be converted, if so prompted. Open the application file in an appropriate version of Visio. (WorkPlace Tech not needed). While holding down the left-shift key, right click on the background of the application and select "Show ShapeSheet", holding the left-shift key down until the ShapeSheet window is displayed. Verify that the text table window that is opened shows the file name followed by "". If not, close the shapesheet window and repeat step 2. The left-shift key must be held down until the ShapeSheet table is displayed. Look for the "User-defined Cells" table in the displayed information and verify that an entry named "User.wptVersion" is shown. This field will show the version of WorkPlace Tech that created the application. If either the "User-defined Cells" section or the "User.wptVersion" field are not displayed in the shape sheet, the application was created / edited with a version of Workplace Tech prior to version 3.2sp1. Close Visio. Respond by clicking NO if Visio prompts to save the document. In Visio 2010, the ShapeSheet is located on the Developer tab, which is not displayed by default. To show the Developer tab, do the following: Click the File tab. Under Help, click Options. Click Customize Ribbon. Under Customize the Ribbon, select the Developer check box. To open the ShapeSheet, do the following: On the Developer tab, in the Shape Design group, click the arrow below Show ShapeSheet and then do one of the following: To open the ShapeSheet for a selected shape, click Shape. To open the ShapeSheet for the active page, click Page. To open the ShapeSheet for the entire drawing, click Document.