RDM_RESPONDER_TEST.PY(1)

πŸŽ€ rdm_responder_test.py β€” the vibe check your RDM gear never asked for πŸŽ€

okay bestie, so this is a page from the User Commands section of the manual, and it's all about rdm_responder_test.py. Buckle up, because this lil script is gonna drag your RDM responders and make sure they actually follow the standards. πŸ’…


✨ NAME ✨

rdm_responder_test.py β€” Test RDM responders for adherence to the standards

no cap, that's literally the whole job. it tests responders. to make sure they're standards-compliant. πŸ¦‹


🌸 SYNOPSIS 🌸

rdm_responder_test.py [options] <uid>

you give it some [options] and a <uid>, and it goes off. simple as that. πŸ‘‘


πŸ’– DESCRIPTION πŸ’–

So what actually happens here? You run a whole series of tests on a RDM responder to check the behaviour. Iconic. But before any of that can pop off, two things gotta be true:

  • the OLA server needs to be running, and
  • the RDM device needs to have been detected.

Wanna confirm both? Run ola_rdm_discover -u UNIVERSE and see what it says. That's your vibe check. πŸ”

⚠️ BESTIE. HEAR ME. THIS PART MATTERS. This script sends SET commands to the broadcast UIDs, which means the start address, device label, etc. will be changed for all devices connected to the responder. So if you're thinking about running this on your production lighting rig… think twice. Actually, think like five times. Not me casually rewriting your entire rig's addresses 😭 πŸ’€

πŸ’… OPTIONS πŸ’…

Here's the full menu, no skips, no skimming, we do not gatekeep:

  • -h, --help β€” show this help message and exit. the classic "what does this even do" button 🫢
  • -c SLOT_COUNT, --slot-count=SLOT_COUNT β€” Number of slots to send when sending DMX.
  • -d, --debug β€” Print debug information to assist in diagnosing failures. your little magnifying glass when things go sideways πŸ”Ž
  • -f DMX_FRAME_RATE, --dmx-frame-rate=DMX_FRAME_RATE β€” Send DMX frames at this rate in the background. she's multitasking πŸ’…
  • -l FILE, --log=FILE β€” Also log to the file named FILE.uid.timestamp. yes, literally that name β€” the uid and a timestamp get appended on. πŸ“
  • --list-tests β€” Display a list of all tests. peek the menu before you order ✨
  • -p DIR, --pid-location=DIR β€” The location of the PID definitions.
  • -s, --skip-check β€” Skip the check for multiple devices.
  • -t TEST1,TEST2, --tests=TEST1,TEST2 β€” A comma separated list of tests to run. pick your fighters πŸ₯Š
  • --timestamp β€” Add timestamps to each test. for the girlies who love receipts ⏰
  • --no-factory-defaults β€” Don't run the SET factory defaults tests.
  • -w BROADCAST_WRITE_DELAY, --broadcast-write-delay=BROADCAST_WRITE_DELAY β€” The time in ms to wait after sending broadcast setcommands.
  • -u UNIVERSE, --universe=UNIVERSE β€” The universe number to use, default is universe 0.
  • --inter-test-delay=INTER_TEST_DELAY β€” The delay in ms to wait between tests, defaults to 0.

and that's the whole page, bestie. every flag, every default, every dramatic warning β€” all accounted for, fr fr. 🌈

later, legend πŸ’œ β€” this was rdm_responder_test.py from the User Commands manual, dated October 2015. mwah, periodt. πŸ’‹