Dictate the summary of this article: Your browser does not support the audio element. Digital signage can now be displayed using a web browser. The Web Player is on a view-only basis, so you can't make config changes on the screen itself. To use the web player you need to open the url link within the same server tenant. For example, on your Dashboard:However, when you switch to View:It will switch to:As you can see, it has switched from UK1B to UK1S, but you never leave your GoBright portal. In this instance, if you was to use UK1B the browser will alway show an activation code (valid for 12 months). However, when switching to UK1S the digital signage kicks in - as long as you have added the device on the GoBright portal.Please check the correct link on your GoBright portal as GoBright has several servers across different countries. In this instance, Ascentae is on UK1B, so it's UK1S. The full link for this example would be:https://uk1s.gobright.cloud/playerAscentae have tested this on the following browsers:                  Browser                        Version     Test Result     Approved?Chrome148.0.7778.179 (64-bit)👍🏻   YesEdge148.0.3967.83 (64-bit)👍🏻   YesFireFox151.0.2 (64-bit)👍🏻   YesOpera132.0.5905.11 (64-bit)👍🏻   YesSafari11.1 or higher(Tested by GoBright)   YesBrave1.90.124 (64-bit)👍🏻   YesWe tested the above in June 2026.Please ensure you are running the latest release of your browser.Lets Get StartedLogin to your GoBright portal at https://portal.gobright.cloudSelect the 4-square grid in the top-right and select 'View'Select the 'Devices' tab and look for the top level location. In this instance, there is just one. Right-click on the location and select Add > DeviceOn this page, enter a relevant name and hit saveYou will then be directed to a new page Now we need to activate your device. The activation code is shown on screenEnter your activation code & allow around 1 minute for the activation to kick-inIf you want to read the full GoBright article, it can be found here.If you have any questions, please log a support ticket.

HDL OverviewThe Nureva HDL series is the ideal solution for most medium and large meeting rooms.  Installation is quick and easy, and the built-in software automatically calibrates to the room and continuously adjusts to ensure great audio quality.To get the best out of your HDL solution, check these simple steps to ensure the room is ready.The HDL consists of 2 elements.The Connect Module 2 which can be positioned anywhere, but typically will be close to the PC in the roomThe sound bar(s) which need to be carefully positioned to provide optimal performance.The sound bar is 5' (1524mm) long with 16 downward facing microphones and dual speakers.Room SizeIt is not recommended to use HDL systems in spaces larger than the maximum size.  Doing so will reduce microphone performance and audio output levels will be reduced at the extremes of the space and people may struggle to hear.HDL310 – Maximum recommended room size    9.1m x 9.1mHDL410 – Maximum recommended room size    10.7m x 16.8mSound Bar PositioningIncorrect positioning of the sound bar will cause poor performance.  We recommend reading the Nureva guide before purchasing the system.https://support.nureva.com/docs/microphone-clearance-requirements-and-recommendations Here are the key points to checkHeight.  The bar should be positioned between 2.16 and 3.05m from floor level to ensure the microphones are focussed at sitting and standing height.  Too low reduces audio clarity when people are standing.  Too high reduces audio clarity when people are seated.Wall position.  The bar should be at least 1m from a corner to prevent echo.Sources of noiseThe sound bar should not be installed within 1m of a noise source (e.g. HVAC unit).  If the HVAC is blowing directly onto the sound bar, allow at least 1.5m clearance.Sound bar clearance.  The HDL sound bar has downward facing microphones to detect both direct audio pickup AND audio reflected from the wall behind.  It therefore imperative that the bar is positioned flush on the wall with no obstructions immediately underneath.If the sound bar is to be mounted above a screen (or other obstruction), measure the depth of the screen from the wall (Y).  To calculate the height of the bottom of the sound bar (X), multiply this by 1.5.X = Y x 1.5     So if a screens sits 10cm from the wall, the bottom of the HDL sound bar should be 15cm from the top of the screen. If the unit is mounted above an alcove (or window), there must be at least 15cm of clear wall underneath the sound bar.     Wall construction.  The HDL works best when placed on a hard, flat surface.  Avoid glass as it is overly reflective.     Acoustic panelling.  The HDL sound bar must never be mounted directly onto an acoustic panel.  Audio will be absorbed by the panel and mic pickup will be poor.  Either remove a section of acoustic panel to seat the sound bar – with sufficient clear wall underneath, or install a backboard on top of the acoustic panel Room AcousticsPrior to installation, we recommend that you test acoustic levels in the room.  Nureva have included tools for this in their iPhone App (available from  App Store).  By testing background noise and reverberation in the room, you can determine suitability of the HDL for your space.Background noise.  Normal human speech is approx. 60 – 65dBA.  The HDL priorities human voice, partly by distinguishing the different dB levels.  Therefore, recommended background noise should be 40-45dBA for optimal performance.Reverberation (echo).  The HDL includes sophisticated algorithms to eliminate echo.  However, if the room is too reverberant, the algorithms will not be able to compensate.Take a reverberation reading to determine whether echo is too high.  If Reverberation Time (RT60) levels are higher than 0.5 seconds, then acoustic treatment in the room should be considered before installing a HDL systemCable RunsThe Connect Module 2 and sound bar are connected via a Cat6 Power over Ethernet cable, so connection is easy.  However, make sure you have the ability to run the cable to the sound bar installation spot.The CM2 can be mounted anywhere in the room, typically behind the screen or in a rack, allowing for simple cabling to the rest of the AV equipment.We strongly recommend using the cables included in the box and connecting the CM2 directly to the in room computer and not using a USB hub as this can introduce latency.OverheatingThe Connect Module 2 requires good ventilation to prevent overheating.  If it is mounted behind the screen, ensure it is at the edge to provide air flow.  Do not mount it so it is receiving heat output from other devices. If there are issues with any of the items on this list, please contact Ascentae support and we will endeavour to find a solution that works for you and your customer.  By doing this prior to installation we can ensure that both you and your customer get the best possible solution and minimal downtime and inconvenience.       If in doubt, Ask Ascentae We are here to help.  If you have any questions or concerns about a solution, please contact the support team  - support@ascentae.com.

Dictate the summary of this article: Your browser does not support the audio element. Initial Configuration - Setting SSIDWhen configuring your MAXHUB host device (V-series screen or W70) for use with the WB05 wireless dongle, an SSID must be configured.  By default, the SSID will populate with the device name you have entered during the initial setup.However, whilst the device name can contain punctuation, the SSID cannot.  If the SSID contains punctuation, when you pair the dongle and attempt to use it on your computer, the dongle cannot connect to the host device.How to FixFollow these steps to resolve the issueExit from the home screen of the host device (if it is a W70, you need to break out of the MTR interface using admin credentials)Go to the Windows desktop and load 'Settings' appNavigate to 'Wireless Hotspot' menuEnsure 'Wireless Hotspot' is enabledChange 'Hotspot Name to remove any punctuationExit appReboot deviceOnce device has rebooted, insert the dongle into the USB port on the device to re-pair the dongleUsing the Wireless DongleThe effective range of the wireless dongle is 4m from the centre of the screen.Performance will be impacted at extreme range,  Symptoms may includeLoss of connection between dongle and host deviceDelayed screen refreshLagging of video / audioLoss of sync between video and audioMaximum range can be impacted if the screen is recessed, the MTR is mounted behind a screen or the is no 'line of sight' between the host device and the dongle.If any of these issues occur, relocate the sharing computer and dongle closer to the host device.

Jupiter have issued a BIOS update to support the Trusted Platform Module 2.0 to be enabled on the OPS module.TPM2.0 is a prerequisite for Windows 11.Update Process1) On the OPS PC, ensure you are logged in with administrator rights2) Download the OPS11 BIOS update from the Software Downloads page of the Jupiter support site (Jupiter.com/support)3) Run the update which will install and restart WindowsChange BIOS Settings1) Ensure a keyboard is attached to the OPS module2) Reboot OPS3) Press ‘ESC’ on keyboard on restart to enter BIOS4) When in the BIOS menu, go to ‘Security’, ‘TPM Operation’ and Enable5) You will also need to enable ‘Secure Boot’6) Hit ‘F10’ to save settingsConfirm TPM Enablement1) Exit BIOS and boot OPS back into Windows2) In the ‘Run’ dialogue box, type ‘tpm.msc’ to confirm that TPM is enabledOnce these steps are complete, you will be able to upgrade to Windows 11.If in doubt, ask AscentaeWe are here to help. If you have any questions or concerns about a solution, please contact the Support Team at support@ascentae.com.

Not sure which kit fits your space? We've put together a hardware comparison table below.Here’s the tech specs at a glance for the MAXHUB MTR family. U50 + XC-Kit Pro Bundle V50 V70 W70 XBoard MTR Platform Win11 IOT MDEP (Android 13) MDEP (Android 13) Win11 IOT Win11 IOT Space Small To Medium Small To Medium Medium To Large Medium To Large Small To Large Cam Specs 2 Lens 2 Lens 4 Lens 4 Lens 3 Lens 100 MP Total 100 MP Total 200 MP Total 200 MP Total 150 MP Total Mic Specs 12-Array 12-Array 16-Array 16-Array 16-Array Wire Ingest USB-C (console) USB-C (Console) USB-C (Console) USB-C (Console) HDMI In (Compute) HDMI (compute) HDMI In (Bar) HDMI In (Bar) HDMI In (Bar) USB-C (Console) Wire Ingest @4K (local Only) HDMI On Compute USB-C (Console) USB-C (Console) HDMI On Bar HDMI On Board HDMI In (Bar) HDMI In (Bar) Wireless Sharing (dongle) Yes Yes Yes Yes Yes Wireless Sharing (MAXHUB Share App) Yes No No BETA Yes Sharing Touchback No No No No Coming In Q2 2026 MiraCast No Yes Yes ETA: Q2 2026 Yes Airplay Yes Yes Yes Yes Yes Audio Fence Yes Yes Yes Yes Yes Video Fence Yes Yes Yes Yes Yes Speaker Tracking Yes Yes Yes Yes Yes Auto Framing Smart Gathering (portraits With Room View) Yes Yes Yes Yes No Intelligent Focus (up To 8 Portraits) Yes Yes Yes Yes Yes Multi-Speakers Tracking No No No No Yes AI Facial Enhancement 26H1 26H1 26H1 26H1 No AI EQ Adaptation No No No No Yes Wire BYOD No Yes (USB-C) Yes (USB-C) Yes (USB-C) Yes Via HDMI + USB-B (require Align Ver. 8.6 Or Above) USB-C Power Delivery No 65w (via PSU) 65w (via PSU) No No Wireless BYOD (Dongle) No Yes Yes Yes Yes (require Team Ver. 5.4 Or Above) Wireless BYOD (MAXHUB Share App) No ETA: Q2 2026 ETA: Q2 2026 ETA: Q2 2026 Yes (require Team Ver. 5.4 Or Above) Supported Expansion Mic Apr, 2026 (OTA) June, 2026 (OTA) June, 2026 (OTA) Apr, 2026 (OTA) BM45 Supported Console Main: TCP30T AP30 AP30 TCP31T TCP33T (require Team Ver 5.4 Or Above) Ext: TCP35T LAN Pairing (between Console And Compute Unit) No Yes (BYOD) Yes (BYOD) No No Max. Distance Between Console And Compute In Cat5e 40m 40m (direct Connection) 40m (direct Connection) 40m MAXHUB Pivot Mgmt. Portal Yes Yes Yes Yes Yes Edge Browser No No No No Yes (Pro License) AI Facilitator Yes (Pro License) No No Yes (Pro License) Yes (Pro License) table { font-family: Arial, Helvetica, sans-serif; border-collapse: collapse; width: 100%; } td, th { border: 1px solid #ddd; padding: 8px; } tr:nth-child(even){background-color: #f2f2f2;} tr:hover {background-color: #ddd;} th { padding-top: 12px; padding-bottom: 12px; text-align: left; background-color: #04AA6D; color: white; }

At a high level, network traffic is relatively lightweight. As a general estimate, you can expect approximately 1KB per minute per Area of Interest (AoI), depending on configuration and use case.A Quick Overview:MetricTypical MessageConservative Estimate (Recommended)Size per Message~250 Bytes~1,000 Bytes (1 KB)Usage per Hour~15 KB60 KBUsage per Day~360 KB1.44 MBUsage per Month~10.8 MB43.2 MBA few further points to help provide context...Data transmission varies depending on the type of data being captured (e.g. simple counts vs. more detailed positional data such as XY coordinates).Traffic is calculated per AoI rather than per sensor, meaning a desk-level deployment (with more granular tracking) will typically generate more data than a meeting room setup.Stitching or higher-resolution use cases (e.g. frequent XY updates) will result in slightly higher traffic volumes.During initial deployment and commissioning, network activity may be temporarily higher due to configuration, validation, and testing processes.Firmware updates occur infrequently (typically 1–2 times per year) and will generate higher traffic during those periods, but these are planned and coordinated in advance.Outside of these scenarios, sensors operate with consistent, low-bandwidth communication.In practice, message sizes can be smaller (circa 250 bytes), but we recommend using the ~1KB per minute per AoI estimate as a conservative baseline for planning purposes.