Added support for Flex-Hub/Pod and other features
New Features
- Added support for Flex-Hub/Pod.
- Added support for USB-C Switcher.
- Allow a Toolbox address book file (.xadr) set for read-only mode to be able to be opened in Toolbox.
Resolved issues
- Corrected issue where the Programmer user level did not allow debugging through SIMPL debugger.
- Corrected issue where selecting “ Fixed” in the RF Channel section of the Gateway Configuration Dialogue would cause an error message to display after closing the dialog.
Known Issues
- Serial HW Handshaking (RTS/CTS) is stricter than the Viewport was. If a device has RTS/CTS on and Toolbox does not, you will not be able to communicate.
- The Domotz agent is not compatible with all Toolbox features so some functionality cannot be supported.
- Toolbox does not support concurrent use by multiple users on a PC. In otherwords, you cannot run Toolbox under one user then use the Windows switch user function and run Toolbox under the other user as well.
- A computer going into Sleep or Hibernate mode may cause a running instance of Toolbox to enter the "Switch-To-Retry" state.
- While we are actively looking for a resolution to this problem, knowing this is a trigger may help avoid this situation.
- When naming addresses in the address book, do not start those names with "tcp", "ssl", "usb" or "rs232" as these while they will work for direct connections will not work properly if used in indirect connections.
- Transfer dialogs restrict transfers to one at a time. Use a script or multiple instances of Toolbox for simultaneous transfers.
- Regarding DM Tool for DigitalMedia. While the DM Tool is running, if the connected device (DM
- Switcher) experiences a reboot for ANY reason The DM Tool will no longer show correct status updates. In this case you should close all Toolbox tools and Apps (including SIMPL Windows, System Builder, VTPro-E) and then relaunch the DM Tool.
- All Tools: if multiple instances of a tool are opened, then one is closed, all other open instances will not work correctly. If this occurs, close down all open tool instances, then open a new tool instance to have full functionality restored.