Release Notes

Transcription

1 ScreenBeam Firmware re Release Notes Notes: Release Date: F/W Version: Applicable Product (Catalog #): o ScreenBeam 960 (SBWD960A) Applicable Hardware: Model #SBWD960A and #SBWD950A - Latest version of CMS management utility is available on - Quick Setup Guide, User Manual and Support are available on CHANGES SINCE New features and enhancements o Allow Force Disconnection When feature is enabled, ScreenBeam receiver allows a second Windows 0 Miracast client to connect by kicking off the existing session. This feature is disabled by default. o Wireless display over LAN support Exciting new feature for Non-Miracast clients to connect and project wirelessly over the local network. ScreenBeam receiver must be connected to the same network as the client using Ethernet (recommended) or Wireless. The streaming quality depends on the infrastructure network and WiFi connection quality. See requirements in the below section Improvements and fixes o Fixed PP transmit power value setting keeps defaulting to HIGH. o Fixed cannot perform a firmware update over Local Management web console. o Fixed receiver may freeze when switches between different HDMI inputs and using touchscreen display. Tested against ClearTouch and CleverTouch displays. o Improves initial PP connection success rate. o Modified time-range of the Auto-reboot receiver when idle for to 6/8/0// hours. o Mitigates the chance receiver might get stuck in an un-discoverable state and not seen on Windows Connect menu. UI updates o Appended Receiver name: text in front of ScreenBeam receiver s information o Moved the ScreenBeam logo to the bottom right corner CHANGES SINCE Features and improvements o Autonomous Group Owner (AGO) is set as the default mode for the Peer--Peer (PP) connection. This mode improves the performance of the Miracast PP session. Refer to the Best Practices for AGO Mode section below for recommendations. Channel 65 is the default for N America, Australia, New Zealand, China, Taiwan, and Brazil. Channel 6 is the default for EU, EUTA, HK, and Japan. Force PIN on Each Connection is not supported in Windows 0 build Use ScreenBeam Secure Connect

2 Notes: If you ve updated to this firmware version by the normal method (i.e. CMS Utility, USB Autorun, or Web Interface), the PP Connection mode for the receiver shall remain as before. You can manually set the receiver to AGO mode from the Feature settings menu or restore the receiver to the factory default setting. o Option to auto-restart receiver when idling for X-Hour since last Miracast connection. The default setting is disable. o Optimized PP wireless transmit power value to -0 dbm per level down. Lowering the transmit power reduces the broadcast range. In open air testing, the result with ScreenBeam receiver on channel meter apart using wireless scanner utility: High = -58 dbm Medium = -68 dbm Low = -79 dbm Notes: Lowering the wireless transmit power may impact the Miracast performance depending on distance between the Client device and ScreenBeam receiver. Our recommended value is: Low for small conference or huddle room Medium for a typical class room or meeting or board room High for an auditorium or gym o Maintain Japan s default settings: JP language, Static PIN, and NGO mode o Enhanced User Input Backchannel (UIBC) compatibility with various HID touch displays Up to 0-point touch (Recommended 0-point for optimal performance) Passive Pen is supported with up to pens simultaneously. Bug Fixes o Fixed wireless transmit power value returns to high upon establishing PP connection o Fixed CMS wireless occasionally cannot reconnect to wireless network o Fixed CMS wireless sometimes drops off from wireless network o Fixed Miracast connection can be disrupted by a different system that has previously connected to the same receiver (AGO mode only) o Fixed cannot modify static IP address o Fixed occasionally receiver cannot be discovered by client device(s) o Fixed random disconnection o Fixed rare system crash causes receiver to repeatedly restart and display the Actiontec logo o Applied patch to WPA supplicant to address KRACK Attacks concerns Notes o Version is withdrawn due know connectivity related issues o Version ,.0,.0, and 6.0 are beta or private releases SUPPORTED LANGUAGE English, Japanese, French, Dutch, Nederland, Korean, Spanish, Italian, Russian, Traditional and Simplified Chinese SUPPORTED OS & DEVICE Miracast PP o Windows 0 and 8. devices with native Wi-Fi Miracast wireless display Force PIN on Each Connection is not supported in Windows 0 build Use ScreenBeam Secure Connect

3 o Android devices with native Wi-Fi Miracast wireless display o Windows 7/8 devices without native Wi-Fi Miracast wireless display (Check out the ScreenBeam USB Transmitter solution) Wireless display over LAN o Supported OS Windows 0 build 70 (or later) uses the native Connect feature. ScreenBeam software is required for: o Mac OS 0.0 (or later) o Windows 7 The ScreenBeam software (beta) is available on the 960 s support page. o Minimum System Requirements Intel Core i-series xxx or AMD equivalent (or better) RAM: GB (or more) Wi-Fi: 80.n/ac o Network Ethernet connection is required for ScreenBeam receiver 80.n/ac 5 GHz is recommended for client device Allow Port: 855: TCP 5507: TCP 00: UDP Learn how to connect at: SUPPORT RESOLUTION Up to 080p0 resolution and.0 channels audio Aspect ratio 6:9 and : (Default is 6:9) SUPPORTED FEATURE Wi-Fi Miracast mirror and extended screen Compatible with most HDMI/VGA Projectors and TV displays Configurable secured connection o No PIN o Force PIN One time Each time o PIN type Random (ideal for conference room or shared display) Static and hidden (ideal for classroom or personal display) HDMI/VGA output power management o Wake on Connect or Scan Configurable PP wireless transmit power Force PIN on Each Connection is not supported in Windows 0 build Use ScreenBeam Secure Connect

4 o Note that the wireless transmission range also depends on the client device s WiFi adapter. Some brand/model has better transmission range (i.e. Intel s 7xx/8xx wireless adapter should be better than Marvell Avastar Wireless adapter). Configurable background and screensaver image Remote Managed by ScreenBeam Central Management System (CMS) o Non-cloud. Single administrator o Monitor, configure, update firmware, reboot, and restore to factory o Download CMS utility here: o Compatible with Windows 7/0/Server 0x and VM SUPPORTED TOUCH DISPLAY Touch support via wireless display is natively to Windows 0 Miracast starting from version 607. The Windows 0 device must be at least a th Generation Intel Core xxx-cpu or equivalent AMD processor (or better) to use this feature. Touch is not supported for MacOS, Android, and Windows 7/8. Below is the list of supported interactive touch display and projector. Bold font indicates the display has been verified by Actiontec or by Customer/Partner /Partner. Acer 7" T7HL CleverTouch Interactive Displays 70 ClearTouch Interactive Display 70 Dell C558QT and S0T Epson Projector 585-WI Microsoft Surface Hub 55" and 80 NEC V6-TM and VTM Planar PCT5 Sharp Aquos PN-L series 0, 60, 70, and 80" Viewsonic TD0, TD70, TD0 Habilience IR frame (tested CommBox 60") FlatFrog In-Glass technology is also available in the following brand/size: o Dell 55, 86 o Avocor 65 VTF650 TF650, 75, 8 o LG 86TRE o MMT,, 55, 65 o NEC 55, 65, 8 o Newline X5, X9 o Promethean 70, 75, 86 o Optika, 55, 65, 8 o Utouch, 55, 65 o Viewsonic IFP60 Series 65, 75, 86 o Volanti,, 55, 65, 8 Force PIN on Each Connection is not supported in Windows 0 build Use ScreenBeam Secure Connect

5 Flatfrog In-glass Supported Features Up to 0-point multitouch write/draw Up to passive pen simultaneous write/draw Up to Fingers + PEN simultaneous write/draw Fist Erase gesture Force PIN on Each Connection is not supported in Windows 0 build Use ScreenBeam Secure Connect

6 Best Practices for AGO Mode Brief Introduction to AGO Autonomous Group Owner (AGO) mode allows the Client device to connect with ScreenBeam receiver on a known clean wireless channel set by the IT. This allows organization to map the wireless channel on the Wi-Fi network accordingly to avoid conflict with other devices Wi-Fi usage. System and Network Adapter Requirements AGO mode requires Client device to have newer wireless network adapter and wireless driver. Various OEM systems (Dell/Lenovo/HP/Toshiba/Other) o OS: Windows 0 Build 607 (or newer) o Wireless NIC: Intel Dual-Band Wireless N/AC model xx, 7xx, or 8xx Qualcomm-Atheros Wireless Network Adapter model QCA6xA or QCA AR96x Microsoft Surface device (, Pro,, Pro, Pro, and Book) o OS: Windows 0 Build 70 (or newer) o Wireless NIC: Marvell Avastar Wireless-AC Network Controller with driver (or newer) Note: Latest Surface s wireless driver package can be obtained from Microsoft Update Catalog: Wireless Channel Mapping ScreenBeam supports both.ghz and 5GHz (UNII- and UNII-) bands. However,.GHz spectrum is often congested and likely to experience interference. We recommend reserving at least () Non-DFS 5GHz wireless channel for the Miracast PP connection. The number of channel to be reserved may depend on the separation between rooms where ScreenBeam receivers are deployed. You may need to consult with the wireless network admin for this procedure. On the Wireless Access Point (APs) Controller or Management Server o Disable the Wi-Fi channel(s) selected for PP connection from broadcasting. o Enable UNII- or UNII- Extended DFS channels for Wi-Fi client devices if necessary. For receivers deployed in nearby rooms, we recommend staggering to different channels in adjacent rooms to avoid congestion. This is necessary if HD video streaming is often used HALLWAY Wireless Network Permissions Force PIN on Each Connection is not supported in Windows 0 build Use ScreenBeam Secure Connect

7 In AGO mode, the PP connection might get blocked in certain domain wireless network Group Policy. If the connection attempts fail repeatedly, this is like the case and you will need to configure the GPO setting to allow Wi-Fi direct communication. Check the Microsoft Active Directory Group Policy settings and allow Wi-Fi direct communications o The option for Don t Allow Wi-Fi Direct Groups must be unchecked o This should be under Group Policy Management Editor > Policies > Windows Settings > Wireless Network (IEEE 80.) Policies LIMITATION & KNOWN ISSUE LIMITATION and EXPECTED BEHAVIOR CMS/Infrastructure wireless connectivity does not support DFS wireless channel Receiver automatically disable the access to Local Management Interface upon connecting to CMS management utility In AGO mode o The method to access ScreenBeam's local web console for management is different The new method to connect is via Miracast connection (Win+K and connect to receiver) The IP address is The default credential is the same (Administrator/Actiontec) o Force PIN Pairing on Each Connection is not supported in Windows 0 Build 607, 70, and 709. This will be available in the next Windows 0 RS build per Microsoft. To address this issue, we recommend using ScreenBeam Secure Connect software. It is available for download on the ScreenBeam support website. o ScreenBeam receiver broadcasts PP wireless beacon (like a printer) Force PIN on Each Connection is not supported in Windows 0 build Use ScreenBeam Secure Connect

8 Client device Wi-Fi network may detect this SSID KNOWN ISSUE It is secured and should not be accessible It should not interfere the wireless environment o Some corporate or enterprise-grade Wireless APs Controller might treat ScreenBeam receiver as a rogue access point and place it to a contain list. When this occurs, the Miracast PP connection might get interrupted with deauthorization requests from the Wireless APs or the system wireless network policy. We recommend marking ScreenBeam receivers as friendly rogue AP. Client cannot connect or has trouble connecting to the receiver after it s changed to AGO mode Symptom: If the Windows device has previously connected to a receiver in NGO mode, a profile is generated and gets stored in the Windows device management. This profile contains the security handshake and will be used on the next connection. This profile needs to be reset upon after the change to AGO mode. Resolution: Remove the existing receiver profile in Windows and try connecting again. o Go to Windows > Settings o Select Bluetooth & other devices o Select the ScreenBeam receiver profile Actiontec XXXX o Select the Remove option and select Yes to confirm See tech tip :0 marker Wireless environment with Aerohive IDS (HiveOS 6.x) or similar IDS safeguard tool may prevent client device connecting to ScreenBeam receiver. Symptom: Client device wireless display cannot connect to ScreenBeam receiver as it s being recognized as a rd party wireless SSID. The client and receiver could initiate the session, but would not be able to proceed due to being de-authorized. Resolution: Include ScreenBeam receiver s MAC address or MAC range to the IDS whitelist. ScreenBeam receiver s MAC should be :9F:A9:X:X:X for NGO PP mode, and 0:9F:A9:X:X:X for AGO PP mode. Some Firewall and Intrusion Prevention Settings may block the Miracast ast connection specifically to Windows 8. clients Resolution: Include WUDFhost.exe to the firewall whitelist. In addition, the TCP port 76 might need to be configure for communication if the problem persists. In NGO mode - Microsoft Surface with Marvell Avastar Wireless-AC Adapter cannot connect to ScreenBeam when Surface is connected to wireless channel 65. Force PIN on Each Connection is not supported in Windows 0 build Use ScreenBeam Secure Connect

9 Microsoft Surface device (with Marvell Avastar Wireless-AC Adapter) requires updated wireless driver or newer for best Miracast performance. Microsoft Surface device may encounter connection drop at a shorter range if Transmit Power is set to lower than High. Upon a disconnection, the Surface device and receiver may attempt to reconnect on its own and fail. Touch display coordinate might be off if there s an overscan issue. Adjust the overscan setting in the receiver. Flatfrog In-glass Touch Display o When writing with pen on the upper left + or more fingers on the upper right of the display, a random line may streak across the screen. This is a known bug. o Pen or finger draw will stop working when there s fist-erase gesture. This is expected behavior. Force PIN on Each Connection is not supported in Windows 0 build Use ScreenBeam Secure Connect