Version 8.1 Build 79 1. In some cases changing the room name of a device could cause UPStart to terminate after the programming of the device was completed. Now fixed. Version 8.1 Build 76 1. In the schedule verify operation that happens when you export to the Gateway any differences between the stored schedule and the schedule in the file are noted. The differences were supposed to be color coded and weren't. Now fixed. 2. If the schedule stored in the file had no entries then regardless of the schedule stored in the Gateway, no differences were reported. Now fixed. Version 8.1 Build 75 1. Updated the Gateway schedule save operation to detect if the user has not yet set the gateway location or done an export to the Gateway at least once. Export stores tables to the Gateway needed by schedule execution. Version 8.1 Build 73 1. Added export support to the Web Mountain RUC version 2 product. This is now in the application "Export" sub-menu. If UPStart is currently connected to the RUC then UPStart can export directly into that unit. See the RUC Export dialog "Export to Local RUC" section. It is also possible to export into a RUC at a different location. See the RUC Export dialog "Export to Remote RUC" section. Version 8.1 Build 71 1. Improved support for the Simply Automated product id 52 device type: "UCQ-F 4-Button Fan Speed and Light Controller with 4 status LEDs". New right-click menu options enable control of the fan and light. Also added a "Test" tab and UPStart can now retrieve and display its status. 2. Bug fixes and general improvements for program stability. Version 8.1 Build 69 1. Continuation of the changes in build 66 for virtual keypads. There were still some places in UPStart where programing and verify of virtual keypads was attempted. Now, hopefully, fully resolved. Version 8.1 Build 66 1. Virtual keypads, because they don't exist of course, can't be programmed or verified like a normal keypad. Unfortunately UPStart would allow attempts to do just that. Now those actions are disabled. 2. The tables that the Gateway uses to keep track of device state were produced incorrectly for the US2-40 and US22 SAI deice type. Now corrected. 3. The "Remote Access" tab in the device properties was unclear and now has been improved as to its utility. 4. Bug fixes and general improvements for program stability and 3rd party software integration. Version 8.1 Build 65 1. Changed support for the KPC7/KPLD7/KPLR7 to allow using the bottom button as Dim/Bright or as a 6th scene button. This required changes to: a. Device Add online and offline b. Inspector c. Visual Scene Editor d. Dialog Scene Editor e. Log f. Keypad properties dialog pages g. Export h. Get-Status dialog i. Printing j. KPC Worksheet k. System Designer In addition, the buttons for these keypads are now designated as B1 – B6 when in the 6-button configuration or B1 – B5, UP, DN when in the 5-button configuration. Version 8.0 Build 64 1. The web link in the keypad button ordering dialog was incorrect. Now fixed. Version 8.0 Build 63 1. Bug fixes. Version 8.0 Build 62 1. Improved the message received when the "Find the Gateway" operation is attempted and fails. 2. Changes in support of future software that reads the UPB file. All existing files will still operate exactly as before with UPStart. 3. Previously there was a tool that helped 3rd party developers determine the proper format for UPB commands when sent to the PIM. That tool has now been incorporated into UPStart. In the "Tools" ribbon category, "Network" panel, "Command Wizard" button starts it. It has no use except for those users writing software that interfaces to the PIM. 4. Changes in support of out-of-date UPStart version detection and reporting in the Alliance builds. Version 8.0 Build 57 1. The icons for some PulseWorx device types were not correctly reflecting the current state of the device. Version 8.0 Build 56 1. Direct messages from a controller to a receiver are received and processed. The state was updated internal to UPStart and if the display was refreshed the new state would show. Now the refresh is not required. 2. If UPStart was started by double-clicking on a file in the Windows Explorer the startup verify operation and repeater detection wasn't always performed. Now it is. Version 8.0 Build 53 1. Changes in support of Windows 10. 2. In some cases when UPStart received a link command from a UPB transmitter in the network it wouldn't update the visible state of any devices that received that scene. The state was updated internal to UPStart and if the display was refreshed the new state would show. Now the refresh is not required. 3. When UPStart is first started and with no file loaded the file save and file save-as menu operations were enabled. If a file save was performed at this time it would create a file with a network id of zero which is invalid. Now when UPStart is started and no file is loaded the file save and file save-as operations are disabled until a network is created. 4. If UPStart was disconnected and reconnected using the ribbon buttons the signal/noise meter in the status bar would stop working. Now the disconnect and reconnect will keep the signal meter working. 5. Added support for HAI product id 81. Version 8.0 Build 47 1. UPStart considered some HAI switches to be no dim capable but, while they are shipped from the factory in a non-dim configuration, they are dimmable if the dim option was set in the device properties. UPStart correctly handled this in some places but not in all. Now resolved. Version 8.0 Build 45/46 1. The PCS WS1R switch supports blinking using the receive components table. In previous builds setting the blink rate didn't work correctly. Now does. 2. Improved the dialog that displays when editing a schedule or exporting to the Gateway when the schedule in the Gateway and the schedule in the file don't match. Now shows the differences. Also implemented the same verify and display for the calendar if in calendar scheduling mode. Version 8.0 Build 43/44 1. New keypad icons used for the PulseWorx 6, 7, and 8 button keypads. 2. For the UPB Alliance installation a check is now made at startup to see if there is a more recent version of UPStart available for download. if there is then it reports that to the user. This can be disabled from UPStart Options on the startup tab. 3. Out of date firmware detection added for the PulseWorx Gateway. Version 8.0 Build 41 1. Gateway export has been updated to let you specify if a schedule should be stored during export. There are three options: a. Always store the schedule b. Never store the schedule c. Check if the schedule in the gateway is different than the schedule in the UPB file and ask if it should be stored or not Version 8.0 Build 38 1. A problem with the export file creation for the SAI product id 50, 51, 52 (UCQ keypads) was resolved. Version 8.0 Build 35/36/37 1. File export when done using the "Export on file save" option (See UPStart options) was not adding the new "Remote Access" data from the device properties and the room icon selections. Now changed to do that. 2. Changed the text in the PulseWorx Gateway user setup dialog for clarity. 3. When a SAI product id 26 (UCQ / UCQT Quad Output Module) or product id 36 (UCQTX Quad Output Module) were added offline, changes to the settings on the "Keypad Tx" tab were not captured after an edit. Version 8.0 Build 33/34 1. An issue with the UPStart export file and the SAI US2 devices was corrected. The transmit enables for the rockers/buttons wasn't being properly used when the export for the rockers and buttons was exported. 2. Gateway schedule entry creation wasn't correctly displaying newly created schedule entries that were a based off of a delta from sunrise or sunset. Now fixed. 3. For schedule entries that use sunrise/sunset plus/minus there was a mismatch between how UPStart stored the schedule and how the Gateway firmware interpreted it. This has been corrected. If you have a schedule that uses sun time entries you must change any entry that was based from sunrise or sunset as the plus and minus will have been switched from your intent. Then re-exported to the Gateway to function correctly. Version 8.0 Build 31/32 1. The SAI US22 device was exported incorrectly to the UPE file. Now resolved. 2. The SAI UCQT-40 device was exported incorrectly to the UPE file. Now resolved. Version 8.0 Build 30 1. Changed the "Network Settings" dialog for the PulseWorx Gateway to clarify the settings needed to assign the Gateway a static address. Version 8.0 Build 29 1. Added to the Help menu (the "?" icon at the right end of the ribbon) a "Readme file" menu pick to display the installation readme file in notepad. 2. Made keyboard actions work to select indicator choices in the "Indicators" tab for keypads. Version 8.0 Build 28 1. A problem that seemed to only happen on slower computers was fixed. The problem occurred when one file was open and a file-open or selection from the recent file list was made It also appeared to happen more often when the two files have vastly different number of devices in them. 2. A problem with the PIM Watch feature was resolved. When attempting to reconnect it sometimes immediately reported a new disconnection. 3. The dialog that provides help for placing a device into setup mode has been reworked to be clearer. 4. A warning was added when attempting to assign a static address to the Gateway. Version 8.0 Build 24 1. A problem in the tool to assign a static IP address to the PulseWorx Gateway has been fixed. 2. A problem when updating the location table with incorrectly programmed Gateways has been fixed. Version 8.0 Build 22 Initial public release of UPStart version 8. The following are the major changes from UPStart version 7. 1. Support for PCS PulseWorx Gateway Model PGW. The key changes in support of this are: a. For the ALLIANCE build a new “PulseWorx Gateway” ribbon category is now available. This doesn’t display in the SAI build unless the PulseWorx Gateway interface type is selected and connected to. Once connected, then the ribbon category will be displayed. b. In the properties dialog for devices there is now a “Remote Access” tab. An icon and icon label are chosen to represent the device in remote applications when displaying the design. This information is saved in the Gateway memory. 2. Improved visual presentation when running on devices with high resolution DPI (dots-per-inch) displays. During this process a number of visual display elements were also improved. a. The status bar meter display improved b. The interface setup checklist and the checklist that is used for UPB device operations now have visually improved icons c. The keypad LED indicator tab (used for PulseWorx keypads and the SAI UCQ/UCQT devices) selections display improved d. The keypad LED indicator help dialog was upgraded e. The List View erify status icons visually improved f. The Log Viewer Entry send and receive icons visually improved g. The Network Verify/Discover dialog upgraded for high resolution displays h. Multi-Operation dialog upgraded for high resolution displays i. The UPB logo in the “Starting UPB Interface” and “About” dialog size was standardized j. All of the dialogs that display tabular data now have the column widths saved from session to session k. The text displayed in the UPB Interface Setup, Interface Type select dialog was enlarged for high DPI devices l. The text displayed in the SAI Quick Start Wizard was enlarged for high DPI devices m. The “key” graphic in the links builder dialog displays appropriately on high DPI devices 3. Changed the word "link" in a few last places with the now preferred word "scene". 4. Added a ribbon icon in the “Network” category, “Network Operations” panel labeled “Status All”. This operation gets the status of all the devices in the design. Also if you multiply select more than one device and choose “Get Status” from the right-click popup menu a vastly improved dialog now displays the results. 5. Resolved a bug in the Visual Scene Editor. UPStart would hang if a scene had no transmitters and the UPStart window wasn’t large enough to show the full display of the scene.