[{"data":1,"prerenderedAt":931},["ShallowReactive",2],{"navigation_docs_en":3,"-en-klstr-ctrl-troubleshooting-klstr-nano-firmware-problems":353,"-en-klstr-ctrl-troubleshooting-klstr-nano-firmware-problems-surround":928},[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":335,"basedOn":355,"body":363,"description":913,"extension":914,"links":915,"meta":916,"navigation":917,"path":336,"seo":918,"sources":919,"stem":337,"verified":926,"__hash__":927},"docs_en\u002Fen\u002F2.klstr-ctrl\u002F4.troubleshooting\u002F5.klstr-nano-firmware-problems.md",[356,360],{"product":357,"version":358,"commit":359},"klstr-ctrl","1.2.0","a0df90902",{"product":361,"version":362},"klstr-nano-fw","20260505-v105",{"type":364,"value":365,"toc":901},"minimark",[366,385,413,418,431,530,540,543,547,565,572,578,587,591,603,611,642,660,664,680,688,701,705,713,721,761,764,846,850,860,871,875],[367,368,369,370,375,376,380,381,384],"p",{},"A ",[371,372,374],"a",{"href":373},"\u002Fen\u002Fklstr-ctrl\u002Freference\u002Fglossary#klstrnano","KLSTR.nano"," runs its own\nfirmware, separate from the fixture it is built into. KLSTR.ctrl reads the version each nano\nreports, compares it with the latest release in two places (the ",[377,378,379],"strong",{},"Health Check"," tab and the\n",[377,382,383],{},"Upgrade Nano Firmware"," dialog), and updates nanos over RDM. This page helps when those\nplaces disagree, or when an update doesn't do what you expect.",[386,387,388,389,392,393,396,397,400,401,405,406,409,410,412],"note",{},"The way to check a nano's firmware is the ",[377,390,391],{},"Nano Version"," column of the ",[377,394,395],{},"Upgrade Nano\nFirmware"," dialog (",[377,398,399],{},"KLSTR.nano › Nano › Upgrade firmware","). A nano on release ",[402,403,404],"code",{},"v105","\nreports a version that ends in ",[402,407,408],{},"-v105",", for example ",[402,411,362],{},". When a badge or a\nfinding says something else, trust that text.",[414,415,417],"h2",{"id":416},"firmware-findings-in-the-health-check","Firmware findings in the Health Check",[367,419,420,421,423,424,427,428,430],{},"The ",[377,422,379],{}," tab lists firmware findings under ",[377,425,426],{},"nano › firmware",", one line per\nKLSTR.nano, after RDM discovery of its port. For how to read the tab, see\n",[371,429,250],{"href":251},".",[432,433,434,450],"table",{},[435,436,437],"thead",{},[438,439,440,444,447],"tr",{},[441,442,443],"th",{},"Rule",[441,445,446],{},"What it means",[441,448,449],{},"What to do",[451,452,453,483,510],"tbody",{},[438,454,455,466,473],{},[456,457,458,461,462,465],"td",{},[377,459,460],{},"factory"," (",[377,463,464],{},"Factory firmware active",")",[456,467,468,469,472],{},"The nano runs the firmware it left the factory with: its version ends in ",[402,470,471],{},"-2"," instead of a release name",[456,474,475,476,478,479,482],{},"Update it. See ",[371,477,176],{"href":177},". The same nano is also listed under ",[377,480,481],{},"outdated",", because factory firmware is never the latest release",[438,484,485,493,498],{},[456,486,487,461,489,492],{},[377,488,481],{},[377,490,491],{},"Nano firmware not latest version(v105):"," followed by the version it runs)",[456,494,495,496],{},"The version doesn't end in ",[402,497,408],{},[456,499,500,501,503,504,506,507,509],{},"Update it. Once a release newer than ",[402,502,404],{}," is out, this check still compares with ",[402,505,404],{},", so it can disagree with the update dialog. Trust the ",[377,508,391],{}," there ",[438,511,512,520,523],{},[456,513,514,461,517,465],{},[377,515,516],{},"undetected",[377,518,519],{},"No firmware version detected for nano",[456,521,522],{},"The nano didn't report its software version during discovery",[456,524,525,526],{},"Run RDM discovery on its port again. If it stays, see ",[371,527,529],{"href":528},"#the-nano-doesnt-report-a-version","The nano doesn't report a version",[367,531,532,533,536,537,430],{},"A fourth rule, ",[377,534,535],{},"equality",", is listed but no check raises it: it always reads ",[377,538,539],{},"ok",[367,541,542],{},"The findings of a port are refreshed each time RDM discovery of that port finishes. After an\nupdate, run discovery on the port again to clear them.",[414,544,546],{"id":545},"the-badge-stays-amber-after-a-correct-update","The badge stays amber after a correct update",[367,548,549,552,553,556,557,560,561,564],{},[377,550,551],{},"What you see."," In the update dialog, or next to ",[377,554,555],{},"Software version"," on the ",[377,558,559],{},"KLSTR.nano\nInfo"," card of a fixture, the round badge next to the version is amber, although the version\nends in the latest release. ",[377,562,563],{},"Select out-of-date"," ticks that nano too.",[367,566,567],{},[568,569],"img",{"alt":570,"src":571},"The Nano Version column of the Upgrade Nano Firmware dialog, highlighted, listing the firmware version each KLSTR.nano reports with an amber badge","\u002Fimages\u002Fklstr-ctrl\u002Fupdate-klstr-nano-firmware\u002F02b-nano-version.png",[367,573,574,577],{},[377,575,576],{},"Why."," Known display issue: the badge doesn't recognise the date in front of the release\nname that a nano reports. ",[367,579,580,583,584,586],{},[377,581,582],{},"What to do."," Nothing, the nano is up to date. When you select nanos for an update, untick\nthe ones whose ",[377,585,391],{}," already ends in the latest release.",[414,588,590],{"id":589},"the-update-ends-on-done-but-a-nano-wasnt-updated","The update ends on done!, but a nano wasn't updated",[367,592,593,595,596,599,600,602],{},[377,594,551],{}," The button reads ",[377,597,598],{},"done!",", but the ",[377,601,391],{}," of one or more nanos\ndoesn't end in the new release.",[367,604,605,607,608,610],{},[377,606,576],{}," ",[377,609,598],{}," means the run is over, not that every nano took the new firmware:",[612,613,614,629],"ul",{},[615,616,617,618,621,622,624,625,628],"li",{},"A nano that hadn't answered yet when you clicked ",[377,619,620],{},"Start update"," (its ",[377,623,391],{}," or\n",[377,626,627],{},"FW State"," was still empty) is left out of the update, without a warning.",[615,630,631,632,635,636,639,640,430],{},"With ",[377,633,634],{},"Transfer mode"," set to ",[377,637,638],{},"Unicast",", a failed transfer can still end on ",[377,641,598],{},[367,643,644,646,647,649,650,653,654,656,657,659],{},[377,645,582],{}," Click ",[377,648,598],{}," to reset the dialog. Wait until every row shows a ",[377,651,652],{},"Nano\nVersion"," and a ",[377,655,627],{},", tick the nanos that weren't updated, and start again. Always\ncheck the ",[377,658,391],{}," of each nano after an update.",[414,661,663],{"id":662},"a-klstrone-update-of-its-nano-ends-on-done-but-nothing-changed","A KLSTR.one update of its nano ends on done!, but nothing changed",[367,665,666,668,669,672,673,675,676,679],{},[377,667,551],{}," You updated the nano of a fixture that has a KLSTR.one, from the\n",[377,670,671],{},"KLSTR.nano information"," card of the KLSTR.one. The button reads ",[377,674,598],{},", but the progress\nbar is still at the start, or the ",[377,677,678],{},"Nano Software version"," on the card hasn't changed.",[367,681,682,684,685,687],{},[377,683,576],{}," The KLSTR.one reports ",[377,686,598],{}," also when the flash failed or stopped halfway. The\nnano didn't take the new firmware and keeps running its previous firmware.",[367,689,690,646,692,694,695,697,698,430],{},[377,691,582],{},[377,693,598],{}," and start again. Check the ",[377,696,678],{}," after\nevery update. If it keeps failing, contact KLSTR support. See\n",[371,699,181],{"href":700},"\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ffirmware\u002Fupdate-klstr-nano-through-klstr-one#if-something-goes-wrong",[414,702,704],{"id":703},"the-update-ends-on-failed","The update ends on failed",[367,706,707,709,710,430],{},[377,708,551],{}," The button turns red and reads ",[377,711,712],{},"failed",[367,714,715,717,718,720],{},[377,716,576],{}," If it fails straight after ",[377,719,620],{},", the firmware file is not a valid\nKLSTR.nano package or the downloaded copy is damaged. If it fails at the end, at least one\nnano didn't confirm that it received the whole file, often because of a long or noisy DMX\nline.",[367,722,723,725,726,728,729,732,733,736,737,740,741,744,745,747,748,750,751,754,755,758,759,430],{},[377,724,582],{}," A nano whose update failed keeps running its previous firmware, so the\nfixture keeps working. Click ",[377,727,712],{}," to reset, and start again with ",[377,730,731],{},"Speed"," set to\n",[377,734,735],{},"Slow"," or ",[377,738,739],{},"Very Slow"," (under ",[377,742,743],{},"Show advanced","). If it keeps failing on one line, switch\n",[377,746,634],{}," to ",[377,749,638],{},". For a damaged download, delete the version in\n",[377,752,753],{},"User settings › UPDATES"," and download it again. See\n",[371,756,176],{"href":757},"\u002Fen\u002Fklstr-ctrl\u002Fhow-to\u002Ffirmware\u002Fupdate-klstr-nano-firmware#if-something-goes-wrong","\nand ",[371,760,189],{"href":190},[414,762,529],{"id":763},"the-nano-doesnt-report-a-version",[432,765,766,778],{},[435,767,768],{},[438,769,770,773,776],{},[441,771,772],{},"What you see",[441,774,775],{},"Likely cause",[441,777,449],{},[451,779,780,805,816,833],{},[438,781,782,793,796],{},[456,783,784,786,787,790,791],{},[377,785,391],{}," reads ",[377,788,789],{},"Unknown",", or the Health Check shows ",[377,792,516],{},[456,794,795],{},"The nano didn't answer the version request, often during a large discovery",[456,797,798,799,802,803],{},"Run RDM discovery on its port again. On large rigs, switch on ",[377,800,801],{},"Sequential discovery",": see ",[371,804,330],{"href":331},[438,806,807,810,813],{},[456,808,809],{},"A nano disappeared from the topology during or after an update",[456,811,812],{},"The nano restarts once its new firmware is in place",[456,814,815],{},"Wait. KLSTR.ctrl reads each nano again after the restart. If one stays missing, run RDM discovery on its port",[438,817,818,821,824],{},[456,819,820],{},"No nano answers RDM any more on lines where they are online, after using a manufacturer's tool",[456,822,823],{},"The nanos are still in LAN upgrade mode",[456,825,826,827,830,831],{},"Choose ",[377,828,829],{},"KLSTR.nano › Nano › Advanced › LAN Upgrade mode cancel",", then run RDM discovery again. See ",[371,832,185],{"href":186},[438,834,835,838,841],{},[456,836,837],{},"The update dialog lists no nano at all",[456,839,840],{},"No nano was found behind the Art-Net nodes, or the nanos are behind a KLSTR.one",[456,842,843,844],{},"Check the Art-Net interface and run RDM discovery. For a nano in a fixture with a KLSTR.one, see ",[371,845,181],{"href":182},[414,847,849],{"id":848},"lan-upgrade-mode-doesnt-reach-some-fixtures","LAN upgrade mode doesn't reach some fixtures",[367,851,852,853,856,857,859],{},"LAN upgrade mode needs KLSTR.nano firmware dated ",[402,854,855],{},"20250130"," or later: the date is the first\npart of the ",[377,858,391],{},". Nanos with older firmware ignore the command, so the\nmanufacturer's tool can't reach the fixtures behind them. Update those nanos first, then\nswitch LAN upgrade mode on again.",[367,861,862,863,556,866,868,869,430],{},"Don't confuse it with ",[377,864,865],{},"LAN transparent mode",[377,867,671],{}," card of a\nKLSTR.one fixture. That mode works on the one nano in that fixture only, and you undo it by\nrestarting the fixture. See\n",[371,870,185],{"href":186},[414,872,874],{"id":873},"related","Related",[612,876,877,881,885,889,893,897],{},[615,878,879],{},[371,880,176],{"href":177},[615,882,883],{},[371,884,181],{"href":182},[615,886,887],{},[371,888,185],{"href":186},[615,890,891],{},[371,892,189],{"href":190},[615,894,895],{},[371,896,250],{"href":251},[615,898,899],{},[371,900,295],{"href":296},{"title":902,"searchDepth":903,"depth":903,"links":904},"",2,[905,906,907,908,909,910,911,912],{"id":416,"depth":903,"text":417},{"id":545,"depth":903,"text":546},{"id":589,"depth":903,"text":590},{"id":662,"depth":903,"text":663},{"id":703,"depth":903,"text":704},{"id":763,"depth":903,"text":529},{"id":848,"depth":903,"text":849},{"id":873,"depth":903,"text":874},"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.","md",null,{},{"icon":179},{"title":335,"description":913},{"klstr-ctrl":920},[921,922,923,924,925],"src\u002Frenderer\u002Fcomponents\u002Fsetup\u002FNanoUpgradeFw.tsx","src\u002Frenderer\u002Fsagas\u002Ffirmware\u002Findex.ts","src\u002Frenderer\u002Fsagas\u002Ftopology\u002FnanoHealthCheck.ts","src\u002Frenderer\u002Fcomponents\u002Fsetup\u002FNanoFirmwareStatusLink.tsx","src\u002Frenderer\u002Fassets\u002Fdata\u002FdefaultSettings.ts","2026-10-01","cMHg5ZY_VRb6RIENANQqpY2YJlf6EkhDf8VX68VcsjY",[929,915],{"title":330,"path":331,"stem":332,"description":930,"icon":333,"children":-1},"What to do when RDM fixtures show no sensor readings, no DMX mode list or no device information after discovery.",1791294265777]