NXT-TEST(1)

πŸ“¦
version 3.5.1 Β· 2 versions
, in ubuntu resolute, ubuntu stonking

✨ NAME ✨

nxt-test β€” the lil' vibe-check tool that tests your NXT-Python setup πŸ’– (it's part of the NXT-Python fam, and it's here to check that everything actually connects, bestie)


πŸŽ€ SYNOPSIS πŸŽ€

nxt-test [--backend NAME] [--config NAME] [--config-filename PATH] [--name
NAME] [--host ADDRESS] [--server-host HOST] [--server-port PORT] [--filename
FILENAME] [--no-sound] [--log-level LEVEL]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so, nxt-test tests the connection with a NXT brick. Literally its whole job. It's the tool you run when you wanna debug your NXT-Python setup and figure out why things are being weird. πŸ™ˆ

And the NXT brick can be connected using USB, Bluetooth or over the network. Three options, all valid, all iconic. ✨


🌸 OPTIONS 🌸

  • --no-sound β€” be quiet bestie, this disables the sound test πŸ”‡
  • --log-level LEVEL β€” set the log level. One of DEBUG, INFO, WARNING, ERROR, or CRITICAL. Messages whose level is below the current log level will not be displayed. (so like, if you set it higher, the chatty lil' low-level messages get left on read πŸ’…)

πŸ’œ COMMON OPTIONS πŸ’œ

These ones are common to programs using NXT-Python, so you'll see them around a lot. periodt.

  • --backend NAME β€” enable given backend. Can be used several times to enable several backends. One of usb, bluetooth, socket or devfile. 🫢
  • --config NAME β€” name of configuration file section to use.
  • --config-filename PATH β€” path to configuration file. Can be used several times to use several configuration files. (yes queen, stack 'em up)
  • --name NAME β€” name of NXT brick (for example: NXT). Useful to find the right brick if several bricks are connected. so clutch when you got a whole squad of bricks and need yours πŸ‘‘
  • --host ADDRESS β€” Bluetooth address of the NXT brick (for example: 00:16:53:01:02:03).
  • --server-host HOST β€” server address or name to connect to when using socket backend.
  • --server-port PORT β€” server port to connect to when using socket backend.
  • --filename FILENAME β€” device filename (for example: /dev/rfcomm0), when using ~nxt.backend.devfile backend.
fr fr, go read the nxt-python.conf(5) documentation for a better explanation of the options to find the NXT brick. it's giving "required reading" πŸ“š

⭐ EXAMPLES ⭐

Running for a NXT brick connected using USB:

$ nxt-test
Finding brick...
NXT brick name: NXT
Host address: 00:16:53:01:02:03
Bluetooth signal strengths: (0, 0, 0, 0)
Free user flash: 48480
Protocol version 1.124
Firmware version 1.29
Battery level 8433 mV
Play test sound...done

To report problems, please enable debug logs:

$ nxt-test --log-level DEBUG

When debugging Bluetooth connection problems, try to give the address explicitly:

$ nxt-test --log-level DEBUG --host 00:16:53:01:02:03

The address can be found in the "Settings" menu, under "NXT Version" screen, it is the last line labeled "ID". Add the colon to separate each pair of digits. 🧚 (iykyk, 00165301 0203 becomes 00:16:53:01:02:03, slay)


🌈 SEE ALSO 🌈


πŸ’– Author

This program is part of NXT-Python which is currently maintained by Nicolas Schodet. 🫢

2021-2025, Nicolas Schodet


and that's the whole page bestie!! this lil' queen is version 3.5.1, dated Jan 26, 2026, and it's out here living in the NXT-Python manual section 1. go test ur brick, u got this πŸ‘‘βœ¨

πŸ“¦ where this page comes from