NXT-SCREENSHOT(1)
π NAME π
nxt-screenshot β bestie, it's the screen capture utility for the NXT brick, and it lives in the NXT-Python world π
πΈ SYNOPSIS πΈ
nxt-screenshot [βbackend NAME] [βconfig NAME] [βconfig-filename PATH]
[βname NAME] [βhost ADDRESS] [βserver-host HOST] [βserver-port PORT]
[βfilename FILENAME] [βlog-level LEVEL] FILE
πΈ DESCRIPTION πΈ
okay so here's the whole vibe: nxt-screenshot takes a capture of a connected NXT brick and writes that captured image straight into a FILE. yes, screenshotting your little robot bestie. iconic behavior.
Your NXT brick can be connected via USB, Bluetooth, or over the network β pick your fighter, all three are valid π«Ά
And the image formats?? A wide range of them is supported, thanks to the Python Imaging Library. it's giving versatile. it's giving β¨choicesβ¨.
π OPTIONS π
FILEβ the filename you want the captured image written to. that's the destination, bestie, the place the pic goes.--log-level LEVELβ sets the log level. one ofDEBUG,INFO,WARNING,ERROR, orCRITICAL. no cap: any message whose level is below the current log level will not be displayed. so if you crank it up, the chatty stuff gets left on read π
π§ COMMON OPTIONS π§
these options are common to programs using NXT-Python. shared lore, iykyk π
--backend NAMEβ enables a given backend. can be used several times to enable several backends (yes, stacking, we love to see it). one ofusb,bluetooth,socketordevfile.--config NAMEβ the name of the configuration file section to use.--config-filename PATHβ path to the configuration file. can be used several times to use several configuration files. more files, more power π--name NAMEβ the name of the NXT brick (for example:NXT). super useful when you've got several bricks connected and you need to find the right one. finding your main character brick among the crowd, fr fr π--host ADDRESSβ the Bluetooth address of the NXT brick (for example:00:16:53:01:02:03).--server-host HOSTβ the server address or name to connect to when using thesocketbackend.--server-port PORTβ the server port to connect to when using thesocketbackend.--filename FILENAMEβ the device filename (for example:/dev/rfcomm0), used when you're on the~nxt.backend.devfilebackend.
π‘ heads up bestie: go read the nxt-python.conf(5) documentation for a better explanation of the options to find the NXT brick. it explains the whole finding-your-brick situation way better.
π₯ EXAMPLE π₯
nxt-screenshot --host 00:16:53:01:02:03 capture.png
Capture screen from connected NXT using its Bluetooth address. Save the result image in capture.png.
literally one line and you're done. ate π
π¦ SEE ALSO π¦
nxt-python.conf(5)- NXT-Python documentation β
https://ni.srht.site/nxt-python/latest/
π Author π
This program is part of NXT-Python, which is currently maintained by Nicolas Schodet. thank you for your service π«Ά
π Copyright π
2021-2025, Nicolas Schodet
and that's the whole page, bestie!! this little manual is version 3.5.1, dated Jan 26, 2026, and it's from NXT-Python. go forth and screenshot your brick π β¨
π¦ where this page comes from
- ubuntu resolute: python3-nxt 3.5.1-1build1
- ubuntu stonking: python3-nxt 3.5.1-1build1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms