[{"data":1,"prerenderedAt":1049},["ShallowReactive",2],{"navigation_docs_en":3,"-en-klstr-ctrl-reference-glossary":353,"-en-klstr-ctrl-reference-glossary-surround":1046},[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":304,"basedOn":355,"body":360,"description":1038,"extension":1039,"links":1040,"meta":1041,"navigation":1042,"path":305,"seo":1043,"sources":1040,"stem":306,"verified":1044,"__hash__":1045},"docs_en\u002Fen\u002F2.klstr-ctrl\u002F3.reference\u002F9.glossary.md",[356],{"product":357,"version":358,"commit":359},"klstr-ctrl","1.2.0","a0df90902",{"type":361,"value":362,"toc":986},"minimark",[363,367,372,376,383,387,414,418,436,439,446,476,489,493,496,500,519,523,541,545,559,563,572,576,580,585,589,609,613,622,626,629,639,643,658,661,667,671,678,681,688,692,713,717,727,731,746,750,753,765,769,781,785,793,797,811,815,829,833,838,842,846,854,858,866,870,894,898,902,907,911,923,927,936,939,949,953,968,972],[364,365,366],"p",{},"The terms KLSTR.ctrl uses, and that this guide uses, grouped by subject. DMX, RDM, Art-Net and\nsACN themselves are not explained here.",[368,369,371],"h2",{"id":370},"devices-and-the-app","Devices and the app",[373,374,15],"h3",{"id":375},"klstrctrl",[364,377,378,379,382],{},"The desktop app for macOS and Windows that finds the devices of a KLSTR lighting network,\ndraws them as a live topology, and lets you configure them, update their firmware, watch their\nsensors and diagnose problems. See the\n",[380,381,21],"a",{"href":22},".",[373,384,386],{"id":385},"klstrone","KLSTR.one",[364,388,389,390,394,395,399,400,404,405,409,410,413],{},"A network module built into a fixture or a pixel controller. It contains a small managed\nnetwork switch, so the fixture gets two or three Ethernet ports and fixtures can be cabled to\neach other in lines, rings or stars. A KLSTR.one receives ",[380,391,393],{"href":392},"#edmx","eDMX",", drives the fixture through\nits output ",[380,396,398],{"href":397},"#port","ports",", and is selected by its\n",[380,401,403],{"href":402},"#fixture-id","Fixture ID",". It talks to KLSTR.ctrl over the KLSTR protocol on ",[380,406,408],{"href":407},"#ipv6-link-local","IPv6 link-local",",\nand announces itself, so it shows up as soon as you pick the right network interface. In the\nheader, the ",[411,412,386],"strong",{}," status shows this connection.",[373,415,417],{"id":416},"klstrnano","KLSTR.nano",[364,419,420,421,423,424,428,429,433,434,382],{},"A small RDM module built into a fixture. It sits in the DMX line, passes DMX on to the next\nfixture, and answers RDM for itself and for the fixture behind it. It also stores KLSTR data\nsuch as the fixture's ",[380,422,403],{"href":402}," and positions (see\n",[380,425,427],{"href":426},"#stored-in-the-fixture","Stored in the fixture","), and runs its own firmware. A\nKLSTR.nano's RDM UID always starts with ",[430,431,432],"code",{},"00c8",". KLSTR.ctrl reaches it with RDM over Art-Net,\nthrough the Art-Net node its DMX line is connected to; that is why the header calls the\nArt-Net connection ",[411,435,417],{},[373,437,427],{"id":438},"stored-in-the-fixture",[364,440,441,442,445],{},"KLSTR data that KLSTR.ctrl writes into the fixture itself instead of keeping it on your\ncomputer. On a fixture with a ",[380,443,417],{"href":444},"#klstrnano",", these are:",[447,448,449,456,467],"ul",{},[450,451,452,453,455],"li",{},"the ",[380,454,403],{"href":402}," (a fixture with its own RDM unit number keeps the FID there\ninstead);",[450,457,458,459,462,463,466],{},"the 2D position of its box in the topology, written by ",[411,460,461],{},"Save positions"," in the\n",[411,464,465],{},"2D Positions"," group;",[450,468,469,470,462,472,475],{},"the 3D position and orientation in Stage View, written by ",[411,471,461],{},[411,473,474],{},"3D Positions"," group or by an MVR import.",[364,477,478,479,482,483,486,487,382],{},"The KLSTR.nano keeps them when the fixture is switched off, and KLSTR.ctrl reads them back at\nevery RDM discovery. So the data travels with the fixture: it survives power cycles, a new\nlaptop, a replaced Art-Net node or controller, and a move to another show, and any copy of\nKLSTR.ctrl that discovers the rig shows the same numbering and layout. A\n",[380,480,386],{"href":481},"#klstrone"," keeps the same data in its own configuration. The DMX address,\npersonality and label are standard RDM settings of the fixture itself. A ",[430,484,485],{},".klstr.ctrl"," file\nonly holds a copy of what KLSTR.ctrl had read; see\n",[380,488,69],{"href":70},[373,490,492],{"id":491},"art-net-node","Art-Net node",[364,494,495],{},"A device that turns Art-Net into DMX lines, and passes RDM between KLSTR.ctrl and the\nfixtures on those lines. KLSTR.ctrl finds Art-Net nodes with ArtPoll over IPv4.",[373,497,499],{"id":498},"root-device","Root device",[364,501,502,503,505,506,509,510,514,515,518],{},"A device KLSTR.ctrl finds directly on the network: a ",[380,504,386],{"href":481}," fixture or an\n",[380,507,492],{"href":508},"#art-net-node",". The fixtures KLSTR.ctrl reaches through an Art-Net node are\nits ",[380,511,513],{"href":512},"#subdevice","subdevices",". The ",[411,516,517],{},"Devices"," tree of the sidebar lists the root devices at\nthe top level.",[373,520,522],{"id":521},"subdevice","Subdevice",[364,524,525,526,530,531,533,534,537,538,540],{},"A fixture that KLSTR.ctrl reaches through a ",[380,527,529],{"href":528},"#root-device","root device"," instead of finding it\non the network itself: the RDM fixtures on the DMX ports of an\n",[380,532,492],{"href":508},". This guide mostly calls them the fixtures behind the node, or\nthe connected fixtures. The ",[411,535,536],{},"Device Topology"," shows them behind the root device's ports, and\nthe ",[411,539,517],{}," tree of the sidebar lists them under it.",[373,542,544],{"id":543},"port","Port",[364,546,547,548,550,551,554,555,558],{},"A connection point of a device. In the ",[411,549,536],{}," a port is a DMX port of an\nArt-Net node, drawn as a box with the fixtures behind it. A KLSTR.one has output ports too:\nits Device Configuration window has a tab for each, such as ",[411,552,553],{},"PORT 1",". In the\n",[411,556,557],{},"Network Topology"," the lines join the Ethernet ports of the networked devices.",[373,560,562],{"id":561},"klstrcloud","KLSTR.cloud",[364,564,565,566,382],{},"KLSTR's online service. Fixture manufacturers log in to it to factory-activate KLSTR modules.\nDay-to-day work with KLSTR.ctrl needs no account. See\n",[380,567,571],{"href":568,"rel":569},"https:\u002F\u002Fdocs.klstr.cloud\u002Fen\u002Fklstr-ctrl-manufacturers\u002Flog-in-to-klstr-cloud",[570],"nofollow","Log in to KLSTR.cloud",[368,573,575],{"id":574},"modes","Modes",[373,577,579],{"id":578},"build-mode","Build mode",[364,581,582,583,382],{},"The mode for setting up a rig: every action is available. KLSTR.ctrl starts in Build mode. See\n",[380,584,59],{"href":60},[373,586,588],{"id":587},"live-mode","Live mode",[364,590,591,592,595,596,595,599,602,603,606,607,382],{},"The mode for running a show. It locks the actions that could disturb a running rig\n(",[411,593,594],{},"Assign Fixture ID's",", ",[411,597,598],{},"Patch Fixtures",[411,600,601],{},"Hold to reset"," in ",[411,604,605],{},"Reset devices to\ndefaults",", and the IP settings of RDM devices), and it shows warnings about devices going\noffline and sensor alerts as messages that stay until you close them. Menu commands, the bulk\nconfigure dialogs and the rest of the Device Configuration window are not locked. See\n",[380,608,59],{"href":60},[373,610,612],{"id":611},"demo-mode","Demo mode",[364,614,615,616,619,620,382],{},"A mode in which KLSTR.ctrl shows a ready-made demo rig of KLSTR.one fixtures, Art-Net nodes or\nboth, so you can learn the app without hardware. The mode switch then reads ",[411,617,618],{},"Demo Mode",";\nleaving demo mode clears the topology and returns to Build mode. See\n",[380,621,37],{"href":38},[368,623,625],{"id":624},"addressing-and-patching","Addressing and patching",[373,627,403],{"id":628},"fixture-id",[364,630,631,632,636,637,382],{},"A number that names a fixture in the rig, so you can find and select it without knowing its\nDMX address. Fixture IDs don't have to be unique: several devices can share one. Fixture ID 0\nmeans the device has none yet. Type Fixture IDs on the FID command line (press\n",[633,634],"kbd",{"value":635},":"," in a topology view) to select devices. See\n",[380,638,135],{"href":136},[373,640,642],{"id":641},"universe","Universe",[364,644,645,646,649,650,653,654,657],{},"A block of 512 DMX channels. KLSTR.ctrl writes a start address that runs across universes as\n",[430,647,648],{},"universe.address",": ",[430,651,652],{},"1.1"," is universe 1, address 1, and ",[430,655,656],{},"3.101"," is universe 3, address 101.",[373,659,393],{"id":660},"edmx",[364,662,663,664,666],{},"DMX carried over Ethernet: Art-Net and sACN (E1.31). A ",[380,665,386],{"href":481}," receives its DMX\nthis way.",[373,668,670],{"id":669},"personality","Personality",[364,672,673,674,382],{},"The DMX mode of a fixture: which channels it uses and what they do. Changing the personality\ncan change the ",[380,675,677],{"href":676},"#footprint","footprint",[373,679,680],{"id":677},"Footprint",[364,682,683,684,687],{},"The number of DMX channels a fixture's current ",[380,685,669],{"href":686},"#personality"," uses. KLSTR.ctrl\nuses it to place fixtures back to back when it patches them.",[373,689,691],{"id":690},"patching-mode","Patching mode",[364,693,694,695,698,699,702,703,706,707,710,711,382],{},"In the ",[411,696,697],{},"Auto-assign address"," dialog, the rule for how much room each KLSTR.one gets:\n",[411,700,701],{},"Per Universe"," (a universe of its own), ",[411,704,705],{},"Current footprint"," (right after the previous\nfixture, by its current footprint) or ",[411,708,709],{},"Largest footprint"," (by the footprint of its largest\npersonality). See\n",[380,712,145],{"href":146},[373,714,716],{"id":715},"pinned-port","Pinned port",[364,718,719,720,723,724,726],{},"A KLSTR.one output whose start universe you fixed by hand, with ",[411,721,722],{},"Start universe override"," on\nthe port's tab in the Device Configuration window. ",[411,725,697],{}," leaves pinned ports\nalone unless you tell it otherwise.",[373,728,730],{"id":729},"selection-order","Selection order",[364,732,733,734,737,738,740,741,743,744,382],{},"The order in which the selected devices are numbered: the blue badge next to each selected\nnode shows its place. It follows the order you clicked them, the direction you dragged, or the\norder you typed on the FID command line, and you can change it with ",[411,735,736],{},"Selection Orientation",".\nAssigning Fixture IDs follows it, and so does the ",[411,739,730],{}," patch order of\n",[411,742,697],{},". See\n",[380,745,85],{"href":86},[368,747,749],{"id":748},"discovery-and-communication","Discovery and communication",[373,751,408],{"id":752},"ipv6-link-local",[364,754,755,756,759,760,762,763,382],{},"An IPv6 address that starts with ",[430,757,758],{},"fe80::"," and that every interface with IPv6 switched on\ngives itself, without a DHCP server or any setting. It is valid on one Ethernet network only\nand never passes a router. KLSTR.ctrl finds and controls every ",[380,761,386],{"href":481}," over\nits link-local address, on the interface you select for KLSTR.one. See\n",[380,764,126],{"href":127},[373,766,768],{"id":767},"zeroconf","Zeroconf",[364,770,771,772,774,775,777,778,780],{},"Networking without configuration: devices give themselves an address and announce\nthemselves, with no IP plan and no DHCP server. In this guide it usually means the\n",[380,773,408],{"href":407}," addressing of KLSTR.one fixtures. The ",[411,776,768],{}," switch\nin the RDM IP settings of some fixtures is something else: the IPv4 fallback to a 169.254.x.x\naddress (see ",[380,779,350],{"href":351},").",[373,782,784],{"id":783},"rdm-discovery","RDM discovery",[364,786,787,788,790,791,382],{},"Finding the RDM devices on the DMX ports of Art-Net nodes. KLSTR.ctrl runs the standard RDM\ndiscovery and, when the line has ",[380,789,417],{"href":444}," modules, asks them first which\nfixture sits behind which nano and in what order, so the Device Topology can draw the line\nfixture by fixture. See\n",[380,792,64],{"href":65},[373,794,796],{"id":795},"vendorcast","Vendorcast",[364,798,799,800,802,803,806,807,810],{},"An RDM message addressed to all devices of one manufacturer at once. KLSTR.ctrl uses it to\nreach all ",[380,801,417],{"href":444}," modules on a port together, for example to send firmware\nto all of them at the same time (",[411,804,805],{},"Vendorcast (multiple)"," in the ",[411,808,809],{},"Upgrade Nano Firmware","\ndialog).",[373,812,814],{"id":813},"unicast","Unicast",[364,816,817,818,820,821,824,825,828],{},"An RDM message addressed to one device. In the ",[411,819,809],{}," dialog,\n",[411,822,823],{},"Unicast (one-by-one)"," sends the firmware to each KLSTR.nano in turn: slower than\n",[380,826,795],{"href":827},"#vendorcast",", but more robust on a difficult line.",[373,830,832],{"id":831},"identify","Identify",[364,834,835,836,382],{},"Making a device show itself in the rig, usually by flashing, so you can find it. You can\nidentify devices from the topology, while you hover them, or by Fixture ID. See\n",[380,837,90],{"href":91},[368,839,841],{"id":840},"firmware","Firmware",[373,843,845],{"id":844},"ab-partition","A\u002FB partition",[364,847,848,849,851,852,382],{},"A ",[380,850,417],{"href":444}," holds two firmware partitions, A and B. It runs from one and is\nalways updated into the other, so a failed update leaves the running firmware in place. See\n",[380,853,176],{"href":177},[373,855,857],{"id":856},"firmware-cache","Firmware cache",[364,859,860,861,743,864,382],{},"The firmware files KLSTR.ctrl has downloaded and keeps on this computer, so you can update\ndevices without internet access. Manage it in ",[411,862,863],{},"User settings › UPDATES",[380,865,189],{"href":190},[373,867,869],{"id":868},"lan-upgrade-mode","LAN upgrade mode",[364,871,872,873,875,876,879,880,883,884,887,888,891,892,382],{},"A state in which every ",[380,874,417],{"href":444}," becomes fully transparent: its IN\u002FOUT relay\ncloses and all traffic on the line passes through to the fixture behind it. Start it with\n",[411,877,878],{},"KLSTR.nano › Nano › Advanced › LAN Upgrade mode","; end it with ",[411,881,882],{},"LAN Upgrade mode cancel"," or\nby restarting the nanos. It is not the same as ",[411,885,886],{},"LAN transparent mode"," on the ",[411,889,890],{},"KLSTR"," tab of a\nKLSTR.one, which affects only that fixture's built-in nano. See\n",[380,893,185],{"href":186},[368,895,897],{"id":896},"monitoring-and-diagnostics","Monitoring and diagnostics",[373,899,901],{"id":900},"health-check","Health Check",[364,903,904,905,382],{},"The tab that lists problems KLSTR.ctrl found in the rig, such as nano firmware that is out of\ndate or blocked network access. Its title shows ⚠️ while there are any. See\n",[380,906,250],{"href":251},[373,908,910],{"id":909},"advanced-sensors","Advanced Sensors",[364,912,913,914,916,917,743,921,382],{},"The view in the ",[411,915,198],{}," tab that shows the sensor readings of many devices side by side,\nas a grid of tiles with gauges, and compares them against ",[380,918,920],{"href":919},"#tolerance","tolerances",[380,922,204],{"href":205},[373,924,926],{"id":925},"tolerance","Tolerance",[364,928,929,930,743,934,382],{},"How far a sensor reading may move away from its nominal value before Advanced Sensors marks\nit. There are two limits, both a percentage of the nominal value: within the inner limit the\nreading is fine, between the inner and the outer limit it is a warning, and beyond the outer\nlimit it is a fault. A tolerance can apply on both sides of the nominal value or on one side\nonly. You set tolerances for all fixtures, per fixture type and per ",[380,931,933],{"href":932},"#role","role",[380,935,209],{"href":210},[373,937,938],{"id":933},"Role",[364,940,941,942,945,946,948],{},"A named group within one sensor category of a fixture type, for example the voltage sensors\ncalled ",[411,943,944],{},"Lamp",", so they get their own ",[380,947,920],{"href":919}," apart from the other sensors of\nthat category.",[373,950,952],{"id":951},"mute-vs-disable","Mute vs disable",[364,954,955,956,959,960,963,964,967],{},"Two ways to quiet one sensor reading of one device in Advanced Sensors. ",[411,957,958],{},"Mute"," stops its\nalerts only: the reading stays visible and keeps updating, with a muted mark. ",[411,961,962],{},"Disable"," takes\nthe reading out of use: it is greyed out or hidden, and for an RDM fixture KLSTR.ctrl stops\nasking for its value. Both apply to that one device only. You mute or disable a reading by\nclicking its tile while ",[411,965,966],{},"Disabling Mode"," is on, or from the reading's detail window.",[368,969,971],{"id":970},"related","Related",[447,973,974,978,982],{},[450,975,976],{},[380,977,21],{"href":22},[450,979,980],{},[380,981,266],{"href":267},[450,983,984],{},[380,985,271],{"href":272},{"title":987,"searchDepth":988,"depth":988,"links":989},"",2,[990,1002,1007,1017,1025,1030,1037],{"id":370,"depth":988,"text":371,"children":991},[992,994,995,996,997,998,999,1000,1001],{"id":375,"depth":993,"text":15},3,{"id":385,"depth":993,"text":386},{"id":416,"depth":993,"text":417},{"id":438,"depth":993,"text":427},{"id":491,"depth":993,"text":492},{"id":498,"depth":993,"text":499},{"id":521,"depth":993,"text":522},{"id":543,"depth":993,"text":544},{"id":561,"depth":993,"text":562},{"id":574,"depth":988,"text":575,"children":1003},[1004,1005,1006],{"id":578,"depth":993,"text":579},{"id":587,"depth":993,"text":588},{"id":611,"depth":993,"text":612},{"id":624,"depth":988,"text":625,"children":1008},[1009,1010,1011,1012,1013,1014,1015,1016],{"id":628,"depth":993,"text":403},{"id":641,"depth":993,"text":642},{"id":660,"depth":993,"text":393},{"id":669,"depth":993,"text":670},{"id":677,"depth":993,"text":680},{"id":690,"depth":993,"text":691},{"id":715,"depth":993,"text":716},{"id":729,"depth":993,"text":730},{"id":748,"depth":988,"text":749,"children":1018},[1019,1020,1021,1022,1023,1024],{"id":752,"depth":993,"text":408},{"id":767,"depth":993,"text":768},{"id":783,"depth":993,"text":784},{"id":795,"depth":993,"text":796},{"id":813,"depth":993,"text":814},{"id":831,"depth":993,"text":832},{"id":840,"depth":988,"text":841,"children":1026},[1027,1028,1029],{"id":844,"depth":993,"text":845},{"id":856,"depth":993,"text":857},{"id":868,"depth":993,"text":869},{"id":896,"depth":988,"text":897,"children":1031},[1032,1033,1034,1035,1036],{"id":900,"depth":993,"text":901},{"id":909,"depth":993,"text":910},{"id":925,"depth":993,"text":926},{"id":933,"depth":993,"text":938},{"id":951,"depth":993,"text":952},{"id":970,"depth":988,"text":971},"The KLSTR terms used in KLSTR.ctrl and in this guide, from KLSTR.one and Fixture ID to Live mode, vendorcast and tolerance.","md",null,{},{"icon":307},{"title":304,"description":1038},"2026-10-01","mex9UA5zh09B4BnqP9J-_RELe4JyP65EGhQJtPwBcKU",[1047,1040],{"title":299,"path":300,"stem":301,"description":1048,"icon":302,"children":-1},"The DISPLAY tab of User settings, where you choose what the device and port boxes show, with the shipped defaults, template placeholders and custom RDM PIDs.",1791294265646]