Supported browsers and connection troubleshooting
For direct hardware access, we recommend the latest Chrome or Edge on a PC connected to the device by USB.
On this page
Which browser should I use?
This table describes Web Serial API support. Hardware-tested NMRLink configurations are listed separately below.
| OS | Browsers for direct connection | Notes |
|---|---|---|
| macOS | Latest Chrome or Edge; Firefox 151 or later | Safari cannot connect directly. |
| Windows | Latest Chrome or Edge; Firefox 151 or later | Organization policies may restrict access. |
| Linux | Latest Chrome or Edge; Firefox 151 or later | Check port permissions and browser packaging. |
Firefox may prompt you to install an add-on when first authorizing device access. For older releases or ESR, check that your version supports the API.
Phones, tablets, and Safari can display documentation and simulated graphs, and view or analyze saved data. Use a PC with a supported browser for direct hardware access.
Hardware-tested configurations
- Standard NMRLink Web UI: measurement, frequency tuning, pulse calibration, and T1 and T2 measurements have been tested with Chrome on macOS.
- Other configurations: browser API support does not mean every combination has been tested with NMRLink hardware.
The successful report for Firefox on Debian 13 concerns the earlier browser control program, before it became this library.
Connection checklist
- Check the browser and URL. Use a supported browser over HTTPS or localhost on the PC connected to the device. Direct access is unavailable from a file: URL or an ordinary HTTP LAN address.
- Check the USB connection. Check device power and the USB data cable, then confirm that the OS recognizes a serial port.
- Check whether another app or tab is using the port. Wait for any measurement to finish, then disconnect Python control programs, serial monitors, and other measurement screens.
- Click Connect, select the device port, and grant access. If the port is missing, check OS permissions and packaging restrictions. If permission is denied, check browser site settings and organization policies.
In a custom UI, request port access directly from the Connect button click. See Control measurements for API details.
Linux-specific checks
OS serial port permissions
The user running the browser needs read and write access to the device port. On Debian-based systems, the port may belong to the dialout group. After adding group membership, log out of the desktop and log in again.
Replace /dev/ttyACM0 with the actual port. Check its group and the current user’s group membership.
ls -l /dev/ttyACM0
id -nGIf the port belongs to dialout and your user is not a member, ask the administrator to add you. An administrator can add their own account with the following command. Log out of the desktop and back in afterwards.
sudo usermod -aG dialout "$USER"Snap and other packaging restrictions
Snap-packaged Chromium may require connecting its raw-usb interface in addition to OS permissions.
Snap-packaged Firefox has a known issue where ports do not appear. Do not apply Chromium commands by simply replacing its name with Firefox. Check the official Mozilla guide for non-Snap installation options.
snap list chromium
snap connections chromiumIf raw-usb is listed with “-” in the Slot column, it is disconnected. An administrator can grant Chromium USB access with:
sudo snap connect chromium:raw-usbFully quit and reopen Chromium. This permission is not limited to the NMR instrument, and OS port permissions are still needed. It does not apply to packages without a raw-usb plug and does not guarantee a successful connection. See the Snap raw-usb specification.
If the issue persists
Collect these details to help narrow down the cause:
- OS and browser names and versions. On Linux, include how the browser was installed.
- Whether the port picker opens, whether the device appears, and whether connection succeeds after selecting it.
- The error message shown on screen.
References: MDN Web Serial API compatibility and Mozilla’s Firefox announcement.