The manufacturer Cisco has not yet set up its devicebase profile. Content such as updates, compatibilities and support may only be maintained with a delay.
Update

Easier deployment of AirPlay

Improvements

  • Extended shape library and text-in-shapes when using Whiteboard
    Introduced new features that allow for the insertion of text into shapes and added a square shape with rounded corners.
  • Custom buttons in Control Panel
    This update enhances the UI Extensions by allowing custom buttons to be added to the side panel (on touch screen devices) or the control panel of the Cisco Room Navigator. Configuration of these buttons is managed within the UI extensions editor, where their placement can be specified. These custom buttons function identically to standard ones, supporting interaction with macros.
  • Support for third-party touch screens
    Support is now available for selected third-party touch screens, compatible with the Room Bar, Room Bar Pro, Room Kit EQ, and Codec Pro devices.

To activate third-party touch screen functionality, adjust the settings as follows:

Enable the feature by setting xConfiguration UserInterface ExternalTouchScreen Enabled to True. The xConfiguration Peripherals Profile TouchPanels now includes 'Auto' in its value space for easier configuration. Activating this feature provides support for third-party touch screens, similar to the Board experience, and introduces whiteboard for devices previously lacking these capabilities.

Connect the touch-enabled display to the first HDMI connector and attach a USB cable for touch functionality. The process is automatic once the feature is enabled.

Currently, support is limited to one touch screen per device. If a device supports multiple screens, additional screens cannot be connected alongside the touch screen. Future updates may allow for both a touch and a passive screen simultaneously.

Officially supported touch screen models include:

Dell C and P Series Samsung WAC-series

  • Dual screen support (HDMI OUT) for Desk Pro
    We are excited to announce the new HDMI output feature for the Desk Pro and Board Pro devices, enabling the connection of a second monitor to create a dynamic dual-screen video system. This enhancement allows users to extend their workspace, increasing productivity and interaction during meetings.

With the HDMI out feature, users can now leverage the power of a second monitor to display additional content, visuals, or reference materials, providing a more immersive and comprehensive meeting experience. This functionality is ideal for facilitating extended discussions, conducting training sessions, and collaborating more effectively on projects.

The dual-screen setup promotes better engagement and collaboration by allowing participants to view shared content simultaneously on both the primary device and the secondary monitor. This extended display capability improves visibility and ensures that all participants have a clear view of the presentation or discussion, enhancing the overall communication and understanding.

Moreover, the HDMI output on the Desk Pro and Board Pro supports easy connection to external displays or projectors, offering flexibility and ensuring compatibility with a broad range of display devices. This feature simplifies the setup process and enhances the meeting environment, making it more versatile and productive.

Embrace the full potential of your meetings with the Desk Pro and Board Pro's HDMI output capability, designed to deliver impactful, engaging, and efficiently communicated sessions to all participants.

To activate the HDMI Out feature, users can navigate to the side menu and device settings to turn it on. This action requires a one-time device restart to implement the change. After rebooting, the device will automatically recognize signals from the HDMI port. Should the HDMI connection be removed later, the device will seamlessly transition back to a single screen setup without needing further actions from the user.

  • Support for USB serial outbound connections
    This new feature enables you to establish outbound serial connections, allowing you to send commands directly to third-party equipment. In the past, only external devices could connect to our serial interface to issue commands.

The outbound serial port control in the system operates on a connectionless model, where the serial port connection between the codec and the peripheral is not constant. Instead, the connection is established only when a command is issued through xCommand SerialPort PeripheralControl Send and terminates once the command execution is complete. This transient connection approach facilitates direct command communication with peripherals like projectors and monitors.

In terms of configuration, the outbound serial port control feature encompasses several adjustable parameters under xConfiguration SerialPort Outbound. These include the mode, which toggles the outbound control feature on or off, and the Port[1], which signifies the current support for a single serial port with an anticipation of future expansion to multiple ports. The BaudRate parameter allows the user to set the speed of data transmission, while the Description field provides a means to describe the connected peripheral device (cosmetic). Additionally, the Parity setting adjusts the parity bit to ensure the accuracy of the transmitted data. Please refer to the third-party equipment documentation to see their command and connectivity specifications.

The core command for outbound serial data transmission, xCommand SerialPort PeripheralControl Send, incorporates several parameters such as PortId, which is set to 1 by default, ResponseTerminator, and ResponseTimeout, which define how the codec processes the response from the peripheral. The Text parameter specifies the actual data to be sent, with functionality to include special characters.

Response handling in the codec is refined through the ResponseTerminator and ResponseTimeout settings. The ResponseTerminator enables the codec to buffer the response until a specified delimiter is met, filtering the data effectively. For instance, if set to "\\n", the codec captures the response up to this character, ignoring any further data. This mechanism works in tandem with ResponseTimeout, dictating the duration the codec waits for a peripheral's response, capped at 5000 milliseconds. Absence of a ResponseTimeout setting results in the immediate conclusion of the command post-data transmission, bypassing the response phase. This intricate setup enhances the efficiency and flexibility of managing serial communications with third-party peripherals.

  • Management of paired Room Navigators
    RoomOS 11.14.2 enables the management of a remotely paired Room Navigator. Previously, pairing a Room Navigator prohibited access to the CLI and Web UI on the Room Navigator itself. Now, it's possible to create a new user directly on the Room Navigator using the device xAPI.

To start, find the ID of the navigator you want to manage in the xStatus section under Peripherals. Then, enable device management with the command xCommand Peripherals DeviceManagement Enable ID: XX:XX:XX:XX:XX:XX.

Next, you can create a new user on the Room Navigator with the command xCommand Peripherals UserManagement User Add Username: touchuser Passphrase: "" YourPassphrase: "" Active: True Role: Admin ID: XX:XX:XX:XX:XX:XX. Note that the username "admin" is reserved and should not be altered.

Once enabled, you can access the Room Navigator using its IP address through SSH or HTTPS (Web UI) for additional management.

If you disable device management using xCommand Peripherals DeviceManagement Disable ID: XX:XX:XX:XX:XX:XX, it will delete all the accounts created and block access to the CLI and Web UI.

Managing the Room Navigator is useful for updating 802.1x Certificates or when other management or integration needs arise.

  • Support for controlling multiple lenses in the camera control menu
    With the standard camera controls, you can now choose specific lenses to set up presets or check various views in self-view. This selection feature is available if your camera, like the Cisco Quad Camera, has multiple lenses.

Other

  • Macro Engine update
    We've updated the Macro Framework to utilize QuickJS as its default engine, replacing Ducktape. This change should not affect your workflow, but there is an important note to consider. If you use the CLI to save macros, specifically through the xCommand Macros Macro Save command, ensure that the Transpile parameter is set to False. Additionally, you must configure xConfiguration Macros EvaluateTranspiled to False. We plan to fix this in an upcoming release. Note that saving macros via the browser (UI) does not encounter this problem.
  • Easier deployment of AirPlay
    Administrators no longer have to set the xConfiguration Bluetooth Enabled to "True" for emitting Airplay BLE beacons. This simplifies the configuration process for deploying Airplay.
  • Added new diagnostics for Web Views when facing out of memory issues
    This feature is solely for diagnostics purposes and aids in pinpointing situations where the web app consumes excessive memory, leading to crashes in the integrated web engine. Given the web engine's limited resource allocation, it may crash if the web app demands more memory than available. Previously, the cause of such crashes was not clearly conveyed to users. Now, a dismissible diagnostic message will appear when this occurs.

Bug fixes

  • Click here for a list of resolved defects in RoomOS 11.14.2.3
Version: 11.14.2.3 Link
Receive Important Update Messages Stay tuned for upcoming Cisco Room Bar updates

Was the content helpful to you?

Advertisement Advertise here?
Banner Logitech