[{"data":1,"prerenderedAt":777},["ShallowReactive",2],{"navigation_docs_en":3,"-en-klstr-ctrl-troubleshooting-rdm-data-or-sensors-missing":353,"-en-klstr-ctrl-troubleshooting-rdm-data-or-sensors-missing-surround":772},[4,14],{"title":5,"icon":6,"path":7,"stem":8,"children":9,"page":13},"Welcome","i-lucide-sparkles","\u002Fen\u002Fwelcome","en\u002F1.welcome",[10],{"title":5,"path":11,"stem":12},"\u002Fen\u002Fwelcome\u002Foverview","en\u002F1.welcome\u002F1.overview",false,{"title":15,"icon":16,"path":17,"stem":18,"children":19,"page":13},"KLSTR.ctrl","i-lucide-monitor-cog","\u002Fen\u002Fklstr-ctrl","en\u002F2.klstr-ctrl",[20,25,46,259,308,338],{"title":21,"path":22,"stem":23,"icon":24},"Overview","\u002Fen\u002Fklstr-ctrl\u002Foverview","en\u002F2.klstr-ctrl\u002F0.overview","i-lucide-info",{"title":26,"icon":27,"path":28,"stem":29,"children":30,"page":13},"Getting started","i-lucide-rocket","\u002Fen\u002Fklstr-ctrl\u002Fgetting-started","en\u002F2.klstr-ctrl\u002F1.getting-started",[31,36,41],{"title":32,"path":33,"stem":34,"icon":35},"Install and launch KLSTR.ctrl","\u002Fen\u002Fklstr-ctrl\u002Fgetting-started\u002Finstall-and-launch","en\u002F2.klstr-ctrl\u002F1.getting-started\u002F1.install-and-launch","i-lucide-download",{"title":37,"path":38,"stem":39,"icon":40},"Tour KLSTR.ctrl in demo mode","\u002Fen\u002Fklstr-ctrl\u002Fgetting-started\u002Ftour-in-demo-mode","en\u002F2.klstr-ctrl\u002F1.getting-started\u002F2.tour-in-demo-mode","i-lucide-compass",{"title":42,"path":43,"stem":44,"icon":45},"Connect KLSTR.ctrl to your network","\u002Fen\u002Fklstr-ctrl\u002Fgetting-started\u002Fconnect-to-your-network","en\u002F2.klstr-ctrl\u002F1.getting-started\u002F3.connect-to-your-network","i-lucide-ethernet-port",{"title":47,"icon":48,"path":49,"stem":50,"children":51,"page":13},"How-to guides","i-lucide-list-checks","\u002Fen\u002Fklstr-ctrl\u002Fhow-to","en\u002F2.klstr-ctrl\u002F2.how-to",[52,73,109,164,197,218,238],{"title":53,"icon":54,"path":55,"stem":56,"children":57,"page":13},"Setup and session","i-lucide-plug","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fsetup","en\u002F2.klstr-ctrl\u002F2.how-to\u002F1.setup",[58,63,68],{"title":59,"path":60,"stem":61,"icon":62},"Switch between Build and Live mode","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fsetup\u002Fswitch-build-and-live-mode","en\u002F2.klstr-ctrl\u002F2.how-to\u002F1.setup\u002F1.switch-build-and-live-mode","i-lucide-toggle-right",{"title":64,"path":65,"stem":66,"icon":67},"Discover devices","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fsetup\u002Fdiscover-devices","en\u002F2.klstr-ctrl\u002F2.how-to\u002F1.setup\u002F2.discover-devices","i-lucide-radar",{"title":69,"path":70,"stem":71,"icon":72},"Save and restore discovered devices","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fsetup\u002Fsave-and-restore-discovered-devices","en\u002F2.klstr-ctrl\u002F2.how-to\u002F1.setup\u002F3.save-and-restore-discovered-devices","i-lucide-save",{"title":74,"icon":75,"path":76,"stem":77,"children":78,"page":13},"Topology and selection","i-lucide-network","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ftopology","en\u002F2.klstr-ctrl\u002F2.how-to\u002F2.topology",[79,84,89,94,99,104],{"title":80,"path":81,"stem":82,"icon":83},"Navigate the topology views","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ftopology\u002Fnavigate-the-topology-views","en\u002F2.klstr-ctrl\u002F2.how-to\u002F2.topology\u002F1.navigate-the-topology-views","i-lucide-map",{"title":85,"path":86,"stem":87,"icon":88},"Select devices","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ftopology\u002Fselect-devices","en\u002F2.klstr-ctrl\u002F2.how-to\u002F2.topology\u002F2.select-devices","i-lucide-mouse-pointer-click",{"title":90,"path":91,"stem":92,"icon":93},"Identify devices","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ftopology\u002Fidentify-devices","en\u002F2.klstr-ctrl\u002F2.how-to\u002F2.topology\u002F3.identify-devices","i-lucide-lightbulb",{"title":95,"path":96,"stem":97,"icon":98},"Arrange nodes","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ftopology\u002Farrange-nodes","en\u002F2.klstr-ctrl\u002F2.how-to\u002F2.topology\u002F4.arrange-nodes","i-lucide-layout-grid",{"title":100,"path":101,"stem":102,"icon":103},"Disable and hide Art-Net nodes","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ftopology\u002Fdisable-and-hide-art-net-nodes","en\u002F2.klstr-ctrl\u002F2.how-to\u002F2.topology\u002F5.disable-and-hide-art-net-nodes","i-lucide-eye-off",{"title":105,"path":106,"stem":107,"icon":108},"Find devices with the sidebar","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ftopology\u002Ffind-devices-with-the-sidebar","en\u002F2.klstr-ctrl\u002F2.how-to\u002F2.topology\u002F6.find-devices-with-the-sidebar","i-lucide-search",{"title":110,"icon":111,"path":112,"stem":113,"children":114,"page":13},"Configuration and addressing","i-lucide-sliders-horizontal","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fconfiguration","en\u002F2.klstr-ctrl\u002F2.how-to\u002F3.configuration",[115,120,125,129,134,139,144,149,154,159],{"title":116,"path":117,"stem":118,"icon":119},"Configure a KLSTR.one","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fconfiguration\u002Fconfigure-a-klstr-one","en\u002F2.klstr-ctrl\u002F2.how-to\u002F3.configuration\u002F01.configure-a-klstr-one","i-lucide-settings",{"title":121,"path":122,"stem":123,"icon":124},"Configure a KLSTR.nano","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fconfiguration\u002Fconfigure-a-klstr-nano","en\u002F2.klstr-ctrl\u002F2.how-to\u002F3.configuration\u002F02.configure-a-klstr-nano","i-lucide-settings-2",{"title":126,"path":127,"stem":128,"icon":75},"IPv6 zeroconf networking","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fconfiguration\u002Fipv6-zeroconf-networking","en\u002F2.klstr-ctrl\u002F2.how-to\u002F3.configuration\u002F03.ipv6-zeroconf-networking",{"title":130,"path":131,"stem":132,"icon":133},"Reboot or factory-reset a KLSTR.one","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fconfiguration\u002Freboot-or-factory-reset-a-klstr-one","en\u002F2.klstr-ctrl\u002F2.how-to\u002F3.configuration\u002F05.reboot-or-factory-reset-a-klstr-one","i-lucide-power",{"title":135,"path":136,"stem":137,"icon":138},"Assign Fixture IDs","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fconfiguration\u002Fassign-fixture-ids","en\u002F2.klstr-ctrl\u002F2.how-to\u002F3.configuration\u002F06.assign-fixture-ids","i-lucide-list-ordered",{"title":140,"path":141,"stem":142,"icon":143},"Patch fixtures","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fconfiguration\u002Fpatch-fixtures","en\u002F2.klstr-ctrl\u002F2.how-to\u002F3.configuration\u002F07.patch-fixtures","i-lucide-cable",{"title":145,"path":146,"stem":147,"icon":148},"Auto-assign DMX addresses","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fconfiguration\u002Fauto-assign-dmx-addresses","en\u002F2.klstr-ctrl\u002F2.how-to\u002F3.configuration\u002F08.auto-assign-dmx-addresses","i-lucide-wand-sparkles",{"title":150,"path":151,"stem":152,"icon":153},"Bulk-configure KLSTR.one devices","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fconfiguration\u002Fbulk-configure-klstr-one-devices","en\u002F2.klstr-ctrl\u002F2.how-to\u002F3.configuration\u002F09.bulk-configure-klstr-one-devices","i-lucide-layers",{"title":155,"path":156,"stem":157,"icon":158},"Bulk-configure RDM devices","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fconfiguration\u002Fbulk-configure-rdm-devices","en\u002F2.klstr-ctrl\u002F2.how-to\u002F3.configuration\u002F10.bulk-configure-rdm-devices","i-lucide-layers-3",{"title":160,"path":161,"stem":162,"icon":163},"Reset devices to defaults","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fconfiguration\u002Freset-devices-to-defaults","en\u002F2.klstr-ctrl\u002F2.how-to\u002F3.configuration\u002F11.reset-devices-to-defaults","i-lucide-rotate-ccw",{"title":165,"icon":166,"path":167,"stem":168,"children":169,"page":13},"Firmware and updates","i-lucide-hard-drive-download","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ffirmware","en\u002F2.klstr-ctrl\u002F2.how-to\u002F4.firmware",[170,175,180,184,188,192],{"title":171,"path":172,"stem":173,"icon":174},"Update KLSTR.one firmware","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ffirmware\u002Fupdate-klstr-one-firmware","en\u002F2.klstr-ctrl\u002F2.how-to\u002F4.firmware\u002F1.update-klstr-one-firmware","i-lucide-circuit-board",{"title":176,"path":177,"stem":178,"icon":179},"Update KLSTR.nano firmware","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ffirmware\u002Fupdate-klstr-nano-firmware","en\u002F2.klstr-ctrl\u002F2.how-to\u002F4.firmware\u002F3.update-klstr-nano-firmware","i-lucide-cpu",{"title":181,"path":182,"stem":183,"icon":179},"Update a KLSTR.nano through a KLSTR.one fixture","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ffirmware\u002Fupdate-klstr-nano-through-klstr-one","en\u002F2.klstr-ctrl\u002F2.how-to\u002F4.firmware\u002F4.update-klstr-nano-through-klstr-one",{"title":185,"path":186,"stem":187,"icon":143},"Use KLSTR.nano LAN upgrade mode","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ffirmware\u002Fuse-klstr-nano-lan-upgrade-mode","en\u002F2.klstr-ctrl\u002F2.how-to\u002F4.firmware\u002F5.use-klstr-nano-lan-upgrade-mode",{"title":189,"path":190,"stem":191,"icon":166},"Manage the firmware cache","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ffirmware\u002Fmanage-the-firmware-cache","en\u002F2.klstr-ctrl\u002F2.how-to\u002F4.firmware\u002F6.manage-the-firmware-cache",{"title":193,"path":194,"stem":195,"icon":196},"Update KLSTR.ctrl","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ffirmware\u002Fupdate-klstr-ctrl","en\u002F2.klstr-ctrl\u002F2.how-to\u002F4.firmware\u002F7.update-klstr-ctrl","i-lucide-refresh-cw",{"title":198,"icon":199,"path":200,"stem":201,"children":202,"page":13},"Monitoring","i-lucide-activity","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fmonitoring","en\u002F2.klstr-ctrl\u002F2.how-to\u002F5.monitoring",[203,208,213],{"title":204,"path":205,"stem":206,"icon":207},"Monitor sensors","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fmonitoring\u002Fmonitor-sensors","en\u002F2.klstr-ctrl\u002F2.how-to\u002F5.monitoring\u002F1.monitor-sensors","i-lucide-gauge",{"title":209,"path":210,"stem":211,"icon":212},"Set sensor tolerances and roles","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fmonitoring\u002Fset-sensor-tolerances-and-roles","en\u002F2.klstr-ctrl\u002F2.how-to\u002F5.monitoring\u002F2.set-sensor-tolerances-and-roles","i-lucide-sliders-vertical",{"title":214,"path":215,"stem":216,"icon":217},"Read eDMX statistics","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fmonitoring\u002Fread-edmx-statistics","en\u002F2.klstr-ctrl\u002F2.how-to\u002F5.monitoring\u002F3.read-edmx-statistics","i-lucide-chart-no-axes-column",{"title":219,"icon":220,"path":221,"stem":222,"children":223,"page":13},"MVR and Stage View","i-lucide-box","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fmvr-stage","en\u002F2.klstr-ctrl\u002F2.how-to\u002F6.mvr-stage",[224,229,234],{"title":225,"path":226,"stem":227,"icon":228},"Import an MVR file","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fmvr-stage\u002Fimport-an-mvr-file","en\u002F2.klstr-ctrl\u002F2.how-to\u002F6.mvr-stage\u002F1.import-an-mvr-file","i-lucide-file-input",{"title":230,"path":231,"stem":232,"icon":233},"Export an MVR file","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fmvr-stage\u002Fexport-an-mvr-file","en\u002F2.klstr-ctrl\u002F2.how-to\u002F6.mvr-stage\u002F2.export-an-mvr-file","i-lucide-file-output",{"title":235,"path":236,"stem":237,"icon":220},"Position fixtures in Stage View","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fmvr-stage\u002Fposition-fixtures-in-stage-view","en\u002F2.klstr-ctrl\u002F2.how-to\u002F6.mvr-stage\u002F3.position-fixtures-in-stage-view",{"title":239,"icon":240,"path":241,"stem":242,"children":243,"page":13},"Diagnostics","i-lucide-stethoscope","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fdiagnostics","en\u002F2.klstr-ctrl\u002F2.how-to\u002F7.diagnostics",[244,249,254],{"title":245,"path":246,"stem":247,"icon":248},"Read the log","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fdiagnostics\u002Fread-the-log","en\u002F2.klstr-ctrl\u002F2.how-to\u002F7.diagnostics\u002F1.read-the-log","i-lucide-scroll-text",{"title":250,"path":251,"stem":252,"icon":253},"Run a health check","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fdiagnostics\u002Frun-a-health-check","en\u002F2.klstr-ctrl\u002F2.how-to\u002F7.diagnostics\u002F2.run-a-health-check","i-lucide-heart-pulse",{"title":255,"path":256,"stem":257,"icon":258},"Report a problem","\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Fdiagnostics\u002Freport-a-problem","en\u002F2.klstr-ctrl\u002F2.how-to\u002F7.diagnostics\u002F3.report-a-problem","i-lucide-message-square-warning",{"title":260,"icon":261,"path":262,"stem":263,"children":264,"page":13},"Reference","i-lucide-book-open","\u002Fen\u002Fklstr-ctrl\u002Freference","en\u002F2.klstr-ctrl\u002F3.reference",[265,270,275,280,285,289,294,298,303],{"title":266,"path":267,"stem":268,"icon":269},"User interface","\u002Fen\u002Fklstr-ctrl\u002Freference\u002Fuser-interface","en\u002F2.klstr-ctrl\u002F3.reference\u002F1.user-interface","i-lucide-layout-dashboard",{"title":271,"path":272,"stem":273,"icon":274},"Menus","\u002Fen\u002Fklstr-ctrl\u002Freference\u002Fmenus","en\u002F2.klstr-ctrl\u002F3.reference\u002F2.menus","i-lucide-menu",{"title":276,"path":277,"stem":278,"icon":279},"Keyboard shortcuts","\u002Fen\u002Fklstr-ctrl\u002Freference\u002Fkeyboard-shortcuts","en\u002F2.klstr-ctrl\u002F3.reference\u002F3.keyboard-shortcuts","i-lucide-keyboard",{"title":281,"path":282,"stem":283,"icon":284},"Settings: View","\u002Fen\u002Fklstr-ctrl\u002Freference\u002Fsettings-view","en\u002F2.klstr-ctrl\u002F3.reference\u002F4.settings-view","i-lucide-eye",{"title":286,"path":287,"stem":288,"icon":75},"Settings: Network","\u002Fen\u002Fklstr-ctrl\u002Freference\u002Fsettings-network","en\u002F2.klstr-ctrl\u002F3.reference\u002F5.settings-network",{"title":290,"path":291,"stem":292,"icon":293},"Settings: RDM","\u002Fen\u002Fklstr-ctrl\u002Freference\u002Fsettings-rdm","en\u002F2.klstr-ctrl\u002F3.reference\u002F6.settings-rdm","i-lucide-radio-tower",{"title":295,"path":296,"stem":297,"icon":196},"Settings: Updates","\u002Fen\u002Fklstr-ctrl\u002Freference\u002Fsettings-updates","en\u002F2.klstr-ctrl\u002F3.reference\u002F7.settings-updates",{"title":299,"path":300,"stem":301,"icon":302},"Settings: Display","\u002Fen\u002Fklstr-ctrl\u002Freference\u002Fsettings-display","en\u002F2.klstr-ctrl\u002F3.reference\u002F8.settings-display","i-lucide-layout-template",{"title":304,"path":305,"stem":306,"icon":307},"Glossary","\u002Fen\u002Fklstr-ctrl\u002Freference\u002Fglossary","en\u002F2.klstr-ctrl\u002F3.reference\u002F9.glossary","i-lucide-book-a",{"title":309,"icon":310,"path":311,"stem":312,"children":313,"page":13},"Troubleshooting","i-lucide-life-buoy","\u002Fen\u002Fklstr-ctrl\u002Ftroubleshooting","en\u002F2.klstr-ctrl\u002F4.troubleshooting",[314,319,324,329,334],{"title":315,"path":316,"stem":317,"icon":318},"Devices are not discovered","\u002Fen\u002Fklstr-ctrl\u002Ftroubleshooting\u002Fdevices-not-discovered","en\u002F2.klstr-ctrl\u002F4.troubleshooting\u002F1.devices-not-discovered","i-lucide-search-x",{"title":320,"path":321,"stem":322,"icon":323},"macOS blocks local network access","\u002Fen\u002Fklstr-ctrl\u002Ftroubleshooting\u002Fmacos-local-network-access","en\u002F2.klstr-ctrl\u002F4.troubleshooting\u002F2.macos-local-network-access","i-lucide-shield-alert",{"title":325,"path":326,"stem":327,"icon":328},"The topology view looks wrong","\u002Fen\u002Fklstr-ctrl\u002Ftroubleshooting\u002Ftopology-view-looks-wrong","en\u002F2.klstr-ctrl\u002F4.troubleshooting\u002F3.topology-view-looks-wrong","i-lucide-git-fork",{"title":330,"path":331,"stem":332,"icon":333},"RDM data or sensors are missing","\u002Fen\u002Fklstr-ctrl\u002Ftroubleshooting\u002Frdm-data-or-sensors-missing","en\u002F2.klstr-ctrl\u002F4.troubleshooting\u002F4.rdm-data-or-sensors-missing","i-lucide-file-question",{"title":335,"path":336,"stem":337,"icon":179},"KLSTR.nano firmware problems","\u002Fen\u002Fklstr-ctrl\u002Ftroubleshooting\u002Fklstr-nano-firmware-problems","en\u002F2.klstr-ctrl\u002F4.troubleshooting\u002F5.klstr-nano-firmware-problems",{"title":339,"icon":340,"path":341,"stem":342,"children":343,"page":13},"Annex","i-lucide-paperclip","\u002Fen\u002Fklstr-ctrl\u002Fannex","en\u002F2.klstr-ctrl\u002F5.annex",[344,349],{"title":345,"path":346,"stem":347,"icon":348},"Lock a device with a PIN","\u002Fen\u002Fklstr-ctrl\u002Fannex\u002Flock-a-device-with-a-pin","en\u002F2.klstr-ctrl\u002F5.annex\u002F1.lock-a-device-with-a-pin","i-lucide-lock",{"title":350,"path":351,"stem":352,"icon":75},"Change RDM IP settings","\u002Fen\u002Fklstr-ctrl\u002Fannex\u002Fchange-rdm-ip-settings","en\u002F2.klstr-ctrl\u002F5.annex\u002F2.change-rdm-ip-settings",{"id":354,"title":330,"basedOn":355,"body":360,"description":756,"extension":757,"links":758,"meta":759,"navigation":760,"path":331,"seo":761,"sources":762,"stem":332,"verified":770,"__hash__":771},"docs_en\u002Fen\u002F2.klstr-ctrl\u002F4.troubleshooting\u002F4.rdm-data-or-sensors-missing.md",[356],{"product":357,"version":358,"commit":359},"klstr-ctrl","1.2.0","a0df90902",{"type":361,"value":362,"toc":742},"minimark",[363,367,371,376,390,400,443,450,454,459,480,483,488,492,558,562,567,576,593,597,712,716],[364,365,366],"p",{},"After RDM discovery has found a fixture, KLSTR.ctrl reads its RDM information one parameter\nat a time: device info, the list of supported parameters, then everything that depends on\nthem, such as the description of every DMX personality and every sensor. On an RDM line only\none request can be answered at a time, and a request that gets no usable answer is dropped\nwithout a message. Most missing data comes down to two things: a setting that is off, or\nrequests that got lost on a busy line.",[368,369,370],"note",{},"This page is about RDM fixtures behind Art-Net nodes. KLSTR.one fixtures report their sensors\nover their own connection and don't need any of the RDM settings below.",[372,373,375],"h2",{"id":374},"no-rdm-sensor-readings","No RDM sensor readings",[364,377,378,382,383,385,386,389],{},[379,380,381],"strong",{},"What you see."," In the ",[379,384,198],{}," tab, RDM fixtures show ",[379,387,388],{},"No sensors available",", or\nsensor columns with a header but no readings. KLSTR.one fixtures in the same rig do show\nreadings.",[364,391,392,395,396,399],{},[379,393,394],{},"Why."," ",[379,397,398],{},"Poll sensor values"," is off by default. KLSTR.ctrl then knows which sensors a\nfixture has, but never asks for their values.",[364,401,402,405,406,409,410,395,414,417,418,395,421,395,424,427,428,431,432,434,435,438,439,442],{},[379,403,404],{},"What to do."," Open ",[379,407,408],{},"KLSTR › User Settings"," (press ",[411,412],"kbd",{"value":413},"Cmd",[411,415],{"value":416},","," on\nmacOS, ",[411,419],{"value":420},"Ctrl",[411,422],{"value":423},"Shift",[411,425],{"value":426},"U"," on Windows), click ",[379,429,430],{},"RDM"," and\nswitch on ",[379,433,398],{},". The first readings arrive within one ",[379,436,437],{},"Poll sensor\nfreqency (s)"," interval, 6 seconds by default. See\n",[440,441,204],"a",{"href":205},".",[364,444,445,446,449],{},"On a big rig, sensor polling adds a lot of RDM traffic. Raise ",[379,447,448],{},"Poll sensor freqency (s)","\nif other RDM requests start to time out.",[372,451,453],{"id":452},"dmx-modes-or-sensors-missing-on-some-fixtures","DMX modes or sensors missing on some fixtures",[364,455,456,458],{},[379,457,381],{}," After a discovery of a large rig, some fixtures have everything and others,\nof the same model, have nothing:",[460,461,462,470],"ul",{},[463,464,465,466,469],"li",{},"In the Device Configuration window, ",[379,467,468],{},"DMX Personality"," shows its label but no dropdown,\nso you can't pick a DMX mode.",[463,471,472,473,475,476,479],{},"In the ",[379,474,198],{}," tab, the fixture is listed under ",[379,477,478],{},"No sensors",", although the same\nmodel shows sensors elsewhere.",[364,481,482],{},"A fixture has either all its mode descriptions or none, and which fixtures are affected\nchanges from one discovery to the next. The fixtures are fine: the problem is in how the data\nwas read.",[364,484,485,487],{},[379,486,394],{}," It happens most on many fixtures with a KLSTR.nano behind one Art-Net node, where\neach nano relays RDM to its fixture. By default, KLSTR.ctrl reads the fixtures of a line in\nseveral passes that can overlap, because a long line is mapped in pieces and each piece\nstarts a new pass. Overlapping requests collide on the one shared line. The replies are lost,\nor the nano answers that it is busy, and that request is dropped. Mode descriptions are read\nwith one request per mode, so a fixture with many modes is hit first.",[364,489,490],{},[379,491,404],{},[493,494,496,501,516,520,545,549],"steps",{"level":495},"3",[497,498,500],"h3",{"id":499},"switch-on-sequential-discovery","Switch on Sequential discovery",[364,502,503,504,507,508,511,512,515],{},"In ",[379,505,506],{},"User settings › RDM",", under ",[379,509,510],{},"PERFORMANCE",", switch on ",[379,513,514],{},"Sequential discovery",". KLSTR.ctrl\nthen finishes one reading pass before it starts the next, so only one request at a time is on\nthe line and none collide. Discovery takes longer.",[497,517,519],{"id":518},"run-rdm-discovery-again","Run RDM discovery again",[364,521,522,523,526,527,409,530,532,395,534,537,538,395,540,542,544],{},"Run RDM discovery on the affected ports: click the discovery icon in the port's box in the\n",[379,524,525],{},"Device Topology",", or choose ",[379,528,529],{},"KLSTR.nano › RDM › Discover",[411,531],{"value":413},[411,533],{"value":423},[411,535],{"value":536},"D"," on macOS, ",[411,539],{"value":420},[411,541],{"value":423},[411,543],{"value":536}," on Windows) for every node.",[497,546,548],{"id":547},"check-the-fixtures","Check the fixtures",[364,550,551,552,554,555,557],{},"Open a fixture that was missing its modes. ",[379,553,468],{}," now shows a dropdown with every\nmode. Leave ",[379,556,514],{}," on for this rig.",[372,559,561],{"id":560},"wrong-dmx-modes-or-sensors-for-a-fixture","Wrong DMX modes or sensors for a fixture",[364,563,564,566],{},[379,565,381],{}," A fixture shows a mode list or sensors that don't match it, for example\nmodes of an older firmware version.",[364,568,569,571,572,575],{},[379,570,394],{}," With ",[379,573,574],{},"Use cached PIDS"," on (the default), KLSTR.ctrl reuses the descriptions it\nalready knows for a fixture model and software version, including a built-in set that can be\nolder than your fixtures.",[364,577,578,580,581,583,584,586,587,589,590,442],{},[379,579,404],{}," Switch off ",[379,582,574],{}," in ",[379,585,506],{},", under\n",[379,588,510],{},", and run RDM discovery on that port again. See\n",[440,591,290],{"href":592},"\u002Fen\u002Fklstr-ctrl\u002Freference\u002Fsettings-rdm#performance",[372,594,596],{"id":595},"other-missing-rdm-data","Other missing RDM data",[598,599,600,616],"table",{},[601,602,603],"thead",{},[604,605,606,610,613],"tr",{},[607,608,609],"th",{},"What you see",[607,611,612],{},"Likely cause",[607,614,615],{},"What to do",[617,618,619,645,662,682,697],"tbody",{},[604,620,621,632,640],{},[622,623,624,625,628,629],"td",{},"A fixture shows as ",[379,626,627],{},"Unknown",", with an orange border and no patch or mode, and the Health Check lists it under ",[379,630,631],{},"rdm › deviceInfo › missing",[622,633,634,635,639],{},"It was discovered, but never answered the ",[636,637,638],"code",{},"DEVICE_INFO"," request",[622,641,642,643],{},"Run discovery on its port again. If it stays, check the line and the fixture. See ",[440,644,250],{"href":251},[604,646,647,650,653],{},[622,648,649],{},"A manufacturer-specific parameter is missing in the Device Configuration window",[622,651,652],{},"KLSTR.ctrl reads only the standard parameters by default",[622,654,655,656,583,659,661],{},"Switch on ",[379,657,658],{},"Fetch all RDM PIDS",[379,660,506],{}," and run discovery again. Discovery takes longer",[604,663,664,667,674],{},[622,665,666],{},"Many requests time out behind slow nodes or long proxy chains",[622,668,669,670,673],{},"The answer takes longer than ",[379,671,672],{},"Packet timeout value (ms)"," (100 ms by default)",[622,675,676,677,583,679,681],{},"Raise ",[379,678,672],{},[379,680,506],{},", then restart KLSTR.ctrl",[604,683,684,687,690],{},[622,685,686],{},"Fixtures on a busy line flicker between online and offline",[622,688,689],{},"Queued-message requests go unanswered now and then",[622,691,676,692,583,695],{},[379,693,694],{},"QMSG offline timout count",[379,696,506],{},[604,698,699,702,705],{},[622,700,701],{},"The data is there after discovery, but changes made on the fixture itself don't show",[622,703,704],{},"KLSTR.ctrl learns about changes through queued messages",[622,706,707,708,711],{},"Leave ",[379,709,710],{},"Poll queued messages(QMSG)"," on, or run discovery again",[372,713,715],{"id":714},"related","Related",[460,717,718,722,726,730,734,738],{},[463,719,720],{},[440,721,204],{"href":205},[463,723,724],{},[440,725,121],{"href":122},[463,727,728],{},[440,729,64],{"href":65},[463,731,732],{},[440,733,290],{"href":291},[463,735,736],{},[440,737,250],{"href":251},[463,739,740],{},[440,741,315],{"href":316},{"title":743,"searchDepth":744,"depth":744,"links":745},"",2,[746,747,753,754,755],{"id":374,"depth":744,"text":375},{"id":452,"depth":744,"text":453,"children":748},[749,751,752],{"id":499,"depth":750,"text":500},3,{"id":518,"depth":750,"text":519},{"id":547,"depth":750,"text":548},{"id":560,"depth":744,"text":561},{"id":595,"depth":744,"text":596},{"id":714,"depth":744,"text":715},"What to do when RDM fixtures show no sensor readings, no DMX mode list or no device information after discovery.","md",null,{},{"icon":333},{"title":330,"description":756},{"klstr-ctrl":763},[764,765,766,767,768,769],"src\u002Frenderer\u002Fsagas\u002Fapp\u002Fartnet\u002Fdiscovery.ts","src\u002Frenderer\u002Fassets\u002Fdata\u002FdefaultSettings.ts","src\u002Frenderer\u002Fcomponents\u002Fmonitoring\u002Fsensor\u002Fadvanced\u002FAdvancedSensorsView.tsx","src\u002Frenderer\u002Fcomponents\u002Fgraph\u002Fcomponents\u002Fshared\u002FNodeHeader.tsx","src\u002Frenderer\u002Fsagas\u002Ftopology\u002FrdmHealthCheck.ts","src\u002Frenderer\u002Fcomponents\u002Fhealthcheck\u002Findex.tsx","2026-10-01","6ND5B43yYQd9QZlfZ8Lqxk0rZJhSZ88WounyMyhO-C8",[773,775],{"title":325,"path":326,"stem":327,"description":774,"icon":328,"children":-1},"Why fixtures show up in a group box, in the wrong order or after they were removed from the Device Topology, and how to get a correct picture of the DMX line again.",{"title":335,"path":336,"stem":337,"description":776,"icon":179,"children":-1},"Make sense of KLSTR.nano firmware findings in the Health Check, amber badges, updates that end on done! or failed, and nanos that stop answering after an update.",1791294265757]