[{"data":1,"prerenderedAt":879},["ShallowReactive",2],{"navigation_docs_en":3,"-en-cloud-klstr-rdm-special-firmware":317,"-en-cloud-klstr-rdm-special-firmware-surround":874},[4,19,74],{"title":5,"path":6,"stem":7,"children":8,"page":18},"Public","\u002Fen\u002Fpublic","en\u002F1.public",[9],{"title":10,"icon":11,"path":12,"stem":13,"children":14,"page":18},"Welcome","i-lucide-sparkles","\u002Fen\u002Fpublic\u002Fwelcome","en\u002F1.public\u002F1.welcome",[15],{"title":10,"path":16,"stem":17},"\u002Fen\u002Fpublic\u002Fwelcome\u002Foverview","en\u002F1.public\u002F1.welcome\u002F1.overview",false,{"title":20,"path":21,"stem":22,"children":23,"page":18},"Cloud","\u002Fen\u002Fcloud","en\u002F2.cloud",[24,33,48],{"title":10,"icon":25,"path":26,"stem":27,"children":28,"page":18},"i-lucide-lock","\u002Fen\u002Fcloud\u002Fwelcome","en\u002F2.cloud\u002F1.welcome",[29],{"title":30,"path":31,"stem":32},"Cloud Docs","\u002Fen\u002Fcloud\u002Fwelcome\u002Foverview","en\u002F2.cloud\u002F1.welcome\u002F1.overview",{"title":34,"icon":35,"path":36,"stem":37,"children":38,"page":18},"Firmware over RDM","i-lucide-radio-tower","\u002Fen\u002Fcloud\u002Ffirmware-over-rdm","en\u002F2.cloud\u002F2.firmware-over-rdm",[39,43],{"title":40,"path":41,"stem":42,"icon":35},"Firmware Update over RDM","\u002Fen\u002Fcloud\u002Ffirmware-over-rdm\u002Foverview","en\u002F2.cloud\u002F2.firmware-over-rdm\u002F1.overview",{"title":44,"path":45,"stem":46,"icon":47},"Implementation Guide","\u002Fen\u002Fcloud\u002Ffirmware-over-rdm\u002Fimplementation-guide","en\u002F2.cloud\u002F2.firmware-over-rdm\u002F2.implementation-guide","i-lucide-list-checks",{"title":49,"icon":50,"path":51,"stem":52,"children":53,"page":18},"KLSTR.rdm","i-lucide-cable","\u002Fen\u002Fcloud\u002Fklstr-rdm","en\u002F2.cloud\u002F3.klstr-rdm",[54,59,64,69],{"title":55,"path":56,"stem":57,"icon":58},"Introduction","\u002Fen\u002Fcloud\u002Fklstr-rdm\u002Fintroduction","en\u002F2.cloud\u002F3.klstr-rdm\u002F1.introduction","i-lucide-circuit-board",{"title":60,"path":61,"stem":62,"icon":63},"Use KLSTR.dev hardware","\u002Fen\u002Fcloud\u002Fklstr-rdm\u002Fuse-klstr-dev-hardware","en\u002F2.cloud\u002F3.klstr-rdm\u002F2.use-klstr-dev-hardware","i-lucide-wrench",{"title":65,"path":66,"stem":67,"icon":68},"Special firmware","\u002Fen\u002Fcloud\u002Fklstr-rdm\u002Fspecial-firmware","en\u002F2.cloud\u002F3.klstr-rdm\u002F3.special-firmware","i-lucide-download",{"title":70,"path":71,"stem":72,"icon":73},"RDM-Compliance Testing","\u002Fen\u002Fcloud\u002Fklstr-rdm\u002Frdm-compliance-testing","en\u002F2.cloud\u002F3.klstr-rdm\u002F4.rdm-compliance-testing","i-lucide-clipboard-check",{"title":75,"path":76,"stem":77,"children":78,"page":18},"Internal","\u002Fen\u002Finternal","en\u002F3.internal",[79,250,264,278],{"title":80,"icon":81,"path":82,"stem":83,"children":84,"page":18},"Review (ex-public)","i-lucide-inbox","\u002Fen\u002Finternal\u002Freview","en\u002F3.internal\u002F0.review",[85,102,120,138,187,205],{"title":86,"icon":87,"path":88,"stem":89,"children":90,"page":18},"Getting Started","i-lucide-rocket","\u002Fen\u002Finternal\u002Freview\u002Ftutorials","en\u002F3.internal\u002F0.review\u002F1.tutorials",[91,94,98],{"title":86,"path":92,"stem":93},"\u002Fen\u002Finternal\u002Freview\u002Ftutorials\u002Fgetting-started","en\u002F3.internal\u002F0.review\u002F1.tutorials\u002F1.getting-started",{"title":95,"path":96,"stem":97},"Setup KLSTR.one","\u002Fen\u002Finternal\u002Freview\u002Ftutorials\u002Fsetup-klstr-one","en\u002F3.internal\u002F0.review\u002F1.tutorials\u002F2.setup-klstr-one",{"title":99,"path":100,"stem":101},"Setup KLSTR.nano","\u002Fen\u002Finternal\u002Freview\u002Ftutorials\u002Fsetup-klstr-nano","en\u002F3.internal\u002F0.review\u002F1.tutorials\u002F3.setup-klstr-nano",{"title":103,"icon":104,"path":105,"stem":106,"children":107,"page":18},"KLSTR.one","i-lucide-cpu","\u002Fen\u002Finternal\u002Freview\u002Fklstr-one","en\u002F3.internal\u002F0.review\u002F2.klstr-one",[108,112,116],{"title":109,"path":110,"stem":111},"KLSTR.one Overview","\u002Fen\u002Finternal\u002Freview\u002Fklstr-one\u002Foverview","en\u002F3.internal\u002F0.review\u002F2.klstr-one\u002F1.overview",{"title":113,"path":114,"stem":115},"KLSTR.one Installation","\u002Fen\u002Finternal\u002Freview\u002Fklstr-one\u002Finstallation","en\u002F3.internal\u002F0.review\u002F2.klstr-one\u002F2.installation",{"title":117,"path":118,"stem":119},"KLSTR.one Specifications","\u002Fen\u002Finternal\u002Freview\u002Fklstr-one\u002Fspecifications","en\u002F3.internal\u002F0.review\u002F2.klstr-one\u002F3.specifications",{"title":121,"icon":122,"path":123,"stem":124,"children":125,"page":18},"KLSTR.nano","i-lucide-microchip","\u002Fen\u002Finternal\u002Freview\u002Fklstr-nano","en\u002F3.internal\u002F0.review\u002F4.klstr-nano",[126,130,134],{"title":127,"path":128,"stem":129},"KLSTR.nano Overview","\u002Fen\u002Finternal\u002Freview\u002Fklstr-nano\u002Foverview","en\u002F3.internal\u002F0.review\u002F4.klstr-nano\u002F1.overview",{"title":131,"path":132,"stem":133},"KLSTR.nano Installation","\u002Fen\u002Finternal\u002Freview\u002Fklstr-nano\u002Finstallation","en\u002F3.internal\u002F0.review\u002F4.klstr-nano\u002F2.installation",{"title":135,"path":136,"stem":137},"KLSTR.nano Specifications","\u002Fen\u002Finternal\u002Freview\u002Fklstr-nano\u002Fspecifications","en\u002F3.internal\u002F0.review\u002F4.klstr-nano\u002F3.specifications",{"title":139,"icon":140,"path":141,"stem":142,"children":143,"page":18},"Developer Guide","i-lucide-code","\u002Fen\u002Finternal\u002Freview\u002Fdeveloper","en\u002F3.internal\u002F0.review\u002F5.developer",[144,147,151,155,159,175],{"title":139,"path":145,"stem":146},"\u002Fen\u002Finternal\u002Freview\u002Fdeveloper\u002Foverview","en\u002F3.internal\u002F0.review\u002F5.developer\u002F0.overview",{"title":148,"path":149,"stem":150},"Choosing a Module","\u002Fen\u002Finternal\u002Freview\u002Fdeveloper\u002Fchoosing-a-module","en\u002F3.internal\u002F0.review\u002F5.developer\u002F1.choosing-a-module",{"title":152,"path":153,"stem":154},"Dual-Mode Operation","\u002Fen\u002Finternal\u002Freview\u002Fdeveloper\u002Fdual-mode","en\u002F3.internal\u002F0.review\u002F5.developer\u002F2.dual-mode",{"title":156,"path":157,"stem":158},"Fleet Management","\u002Fen\u002Finternal\u002Freview\u002Fdeveloper\u002Ffleet-management","en\u002F3.internal\u002F0.review\u002F5.developer\u002F3.fleet-management",{"title":103,"path":160,"stem":161,"children":162,"page":18},"\u002Fen\u002Finternal\u002Freview\u002Fdeveloper\u002Fklstr-one","en\u002F3.internal\u002F0.review\u002F5.developer\u002F4.klstr-one",[163,167,171],{"title":164,"path":165,"stem":166},"KLSTR.one: Hardware Integration","\u002Fen\u002Finternal\u002Freview\u002Fdeveloper\u002Fklstr-one\u002Fhardware-integration","en\u002F3.internal\u002F0.review\u002F5.developer\u002F4.klstr-one\u002F1.hardware-integration",{"title":168,"path":169,"stem":170},"KLSTR.one: Provisioning","\u002Fen\u002Finternal\u002Freview\u002Fdeveloper\u002Fklstr-one\u002Fprovisioning","en\u002F3.internal\u002F0.review\u002F5.developer\u002F4.klstr-one\u002F2.provisioning",{"title":172,"path":173,"stem":174},"KLSTR.one: RDM Protocol","\u002Fen\u002Finternal\u002Freview\u002Fdeveloper\u002Fklstr-one\u002Frdm-protocol","en\u002F3.internal\u002F0.review\u002F5.developer\u002F4.klstr-one\u002F3.rdm-protocol",{"title":121,"path":176,"stem":177,"children":178,"page":18},"\u002Fen\u002Finternal\u002Freview\u002Fdeveloper\u002Fklstr-nano","en\u002F3.internal\u002F0.review\u002F5.developer\u002F5.klstr-nano",[179,183],{"title":180,"path":181,"stem":182},"KLSTR.nano: Hardware Integration","\u002Fen\u002Finternal\u002Freview\u002Fdeveloper\u002Fklstr-nano\u002Fhardware-integration","en\u002F3.internal\u002F0.review\u002F5.developer\u002F5.klstr-nano\u002F1.hardware-integration",{"title":184,"path":185,"stem":186},"KLSTR.nano: Provisioning","\u002Fen\u002Finternal\u002Freview\u002Fdeveloper\u002Fklstr-nano\u002Fprovisioning","en\u002F3.internal\u002F0.review\u002F5.developer\u002F5.klstr-nano\u002F2.provisioning",{"title":188,"icon":189,"path":190,"stem":191,"children":192,"page":18},"FAQ","i-lucide-circle-help","\u002Fen\u002Finternal\u002Freview\u002Ffaq","en\u002F3.internal\u002F0.review\u002F6.faq",[193,197,201],{"title":194,"path":195,"stem":196},"General Questions","\u002Fen\u002Finternal\u002Freview\u002Ffaq\u002Fgeneral","en\u002F3.internal\u002F0.review\u002F6.faq\u002F1.general",{"title":198,"path":199,"stem":200},"Connectivity","\u002Fen\u002Finternal\u002Freview\u002Ffaq\u002Fconnectivity","en\u002F3.internal\u002F0.review\u002F6.faq\u002F2.connectivity",{"title":202,"path":203,"stem":204},"Troubleshooting","\u002Fen\u002Finternal\u002Freview\u002Ffaq\u002Ftroubleshooting","en\u002F3.internal\u002F0.review\u002F6.faq\u002F3.troubleshooting",{"title":206,"icon":207,"path":208,"stem":209,"children":210,"page":18},"Articles","i-lucide-newspaper","\u002Fen\u002Finternal\u002Freview\u002Farticles","en\u002F3.internal\u002F0.review\u002F7.articles",[211,215,219,223,227,231,235,239,243,247],{"title":212,"path":213,"stem":214},"Overview","\u002Fen\u002Finternal\u002Freview\u002Farticles\u002Foverview","en\u002F3.internal\u002F0.review\u002F7.articles\u002F0.overview",{"title":216,"path":217,"stem":218},"KLSTR Integration Guide for Fixture Manufacturers","\u002Fen\u002Finternal\u002Freview\u002Farticles\u002Fintegration-guide","en\u002F3.internal\u002F0.review\u002F7.articles\u002F1.integration-guide",{"title":220,"path":221,"stem":222},"RDM Protocol Reference for KLSTR.one","\u002Fen\u002Finternal\u002Freview\u002Farticles\u002Frdm-protocol","en\u002F3.internal\u002F0.review\u002F7.articles\u002F2.rdm-protocol",{"title":224,"path":225,"stem":226},"KLSTR.one Provisioning Guide","\u002Fen\u002Finternal\u002Freview\u002Farticles\u002Fklstr-one-provisioning","en\u002F3.internal\u002F0.review\u002F7.articles\u002F3.klstr-one-provisioning",{"title":228,"path":229,"stem":230},"KLSTR.one Integration Guide","\u002Fen\u002Finternal\u002Freview\u002Farticles\u002Fklstr-one-plug-in-integration","en\u002F3.internal\u002F0.review\u002F7.articles\u002F4.klstr-one-plug-in-integration",{"title":232,"path":233,"stem":234},"KLSTR.nano Provisioning Guide","\u002Fen\u002Finternal\u002Freview\u002Farticles\u002Fklstr-nano-provisioning","en\u002F3.internal\u002F0.review\u002F7.articles\u002F5.klstr-nano-provisioning",{"title":236,"path":237,"stem":238},"KLSTR.nano Plug-In Integration","\u002Fen\u002Finternal\u002Freview\u002Farticles\u002Fklstr-nano-plug-in-integration","en\u002F3.internal\u002F0.review\u002F7.articles\u002F6.klstr-nano-plug-in-integration",{"title":240,"path":241,"stem":242},"Hello","\u002Fen\u002Finternal\u002Freview\u002Farticles\u002Fhello","en\u002F3.internal\u002F0.review\u002F7.articles\u002F7.hello",{"title":244,"path":245,"stem":246},"TestNew file","\u002Fen\u002Finternal\u002Freview\u002Farticles\u002Fiwantmd","en\u002F3.internal\u002F0.review\u002F7.articles\u002Fiwantmd",{"title":244,"path":248,"stem":249},"\u002Fen\u002Finternal\u002Freview\u002Farticles\u002Ftestnew","en\u002F3.internal\u002F0.review\u002F7.articles\u002Ftestnew",{"title":251,"icon":252,"path":253,"stem":254,"children":255,"page":18},"Admin","i-lucide-shield-check","\u002Fen\u002Finternal\u002Fadmin","en\u002F3.internal\u002F3.admin",[256,260],{"title":257,"path":258,"stem":259},"Admin Dashboard","\u002Fen\u002Finternal\u002Fadmin\u002Fdashboard","en\u002F3.internal\u002F3.admin\u002F1.dashboard",{"title":261,"path":262,"stem":263},"Internal Release Notes","\u002Fen\u002Finternal\u002Fadmin\u002Frelease-notes","en\u002F3.internal\u002F3.admin\u002F2.release-notes",{"title":265,"path":266,"stem":267,"children":268,"page":18},"Developer","\u002Fen\u002Finternal\u002Fdeveloper","en\u002F3.internal\u002F5.developer",[269],{"title":270,"path":271,"stem":272,"children":273,"page":18},"Klstr One","\u002Fen\u002Finternal\u002Fdeveloper\u002Fklstr-one","en\u002F3.internal\u002F5.developer\u002F4.klstr-one",[274],{"title":275,"path":276,"stem":277},"Internal (Partner Only)","\u002Fen\u002Finternal\u002Fdeveloper\u002Fklstr-one\u002Finternal","en\u002F3.internal\u002F5.developer\u002F4.klstr-one\u002F4.internal",{"title":279,"icon":280,"path":281,"stem":282,"children":283,"page":18},"Authoring Guide","i-lucide-pen-line","\u002Fen\u002Finternal\u002Fauthoring","en\u002F3.internal\u002F9.authoring",[284,288,293,297,302,307,312],{"title":285,"path":286,"stem":287,"icon":11},"Overview & MDC Basics","\u002Fen\u002Finternal\u002Fauthoring\u002Foverview","en\u002F3.internal\u002F9.authoring\u002F1.overview",{"title":289,"path":290,"stem":291,"icon":292},"Text & Prose","\u002Fen\u002Finternal\u002Fauthoring\u002Ftext-and-prose","en\u002F3.internal\u002F9.authoring\u002F2.text-and-prose","i-lucide-type",{"title":294,"path":295,"stem":296,"icon":140},"Code Blocks","\u002Fen\u002Finternal\u002Fauthoring\u002Fcode","en\u002F3.internal\u002F9.authoring\u002F3.code",{"title":298,"path":299,"stem":300,"icon":301},"Callouts & Cards","\u002Fen\u002Finternal\u002Fauthoring\u002Fcallouts-and-cards","en\u002F3.internal\u002F9.authoring\u002F4.callouts-and-cards","i-lucide-message-square-warning",{"title":303,"path":304,"stem":305,"icon":306},"Layout & Interactivity","\u002Fen\u002Finternal\u002Fauthoring\u002Flayout-and-interactivity","en\u002F3.internal\u002F9.authoring\u002F5.layout-and-interactivity","i-lucide-layout-panel-left",{"title":308,"path":309,"stem":310,"icon":311},"Visuals — Images, Icons & Diagrams","\u002Fen\u002Finternal\u002Fauthoring\u002Fvisuals","en\u002F3.internal\u002F9.authoring\u002F6.visuals","i-lucide-image",{"title":313,"path":314,"stem":315,"icon":316},"Design System & Configuration","\u002Fen\u002Finternal\u002Fauthoring\u002Fdesign-system","en\u002F3.internal\u002F9.authoring\u002F7.design-system","i-lucide-palette",{"id":318,"title":65,"body":319,"description":867,"extension":868,"links":869,"meta":870,"navigation":871,"path":66,"seo":872,"stem":67,"__hash__":873},"docs_en\u002Fen\u002F2.cloud\u002F3.klstr-rdm\u002F3.special-firmware.md",{"type":320,"value":321,"toc":847},"minimark",[322,331,359,366,383,388,391,437,441,466,470,502,506,754,758,761,784,788,792,795],[323,324,325,326,330],"p",{},"KLSTR.rdm needs a special build at ",[327,328,329],"strong",{},"both ends of the USB cable",", and this page is\nwhere you get both:",[332,333,334,350],"ul",{},[335,336,337,340,341,344,345,349],"li",{},[327,338,339],{},"On the nano",", the ",[327,342,343],{},"sniffer"," firmware, ",[346,347,348],"code",{},"sniffer.klstr.nano",". This is not the\nstandard fixture firmware. Without it the nano never presents itself to KLSTR.ctrl as\na connectable USB device, no matter how it is cabled.",[335,351,352,340,355,358],{},[327,353,354],{},"On the PC",[327,356,357],{},"usbNano build"," of KLSTR.ctrl. The standard build does not expose\nUSB connected nanos, so the device never shows up at all.",[323,360,361,362,365],{},"Neither one is optional and neither is any use on its own. The flash itself happens\n",[327,363,364],{},"over RDM, not over USB",", using an ordinary RDM node and the normal firmware upgrade\nflow.",[367,368,370,373,374,378,379,382],"warning",{"icon":369},"i-lucide-construction",[327,371,372],{},"Draft."," Both downloads and the update window are in place. A photo of the nano's\nupdate button is still ",[375,376,377],"em",{},"Image pending",", the KLSTR.ctrl screenshots for the USB\nconnection steps are still pending, and the usbNano build is currently a ",[327,380,381],{},"development\nbuild for Windows only",".",[384,385,387],"h2",{"id":386},"who-needs-this-page","Who needs this page",[323,389,390],{},"Everyone. Both routes into KLSTR.rdm need both special builds:",[392,393,394,407],"table",{},[395,396,397],"thead",{},[398,399,400,404],"tr",{},[401,402,403],"th",{},"Your hardware",[401,405,406],{},"Hardware modification first",[408,409,410,422],"tbody",{},[398,411,412,419],{},[413,414,415,418],"td",{},[327,416,417],{},"KLSTR.rdm box"," (bonano)",[413,420,421],{},"No, its USB is already broken out",[398,423,424,430],{},[413,425,426,429],{},[327,427,428],{},"KLSTR.dev"," board",[413,431,432,433],{},"Yes, see ",[434,435,60],"a",{"href":436},"\u002Fen\u002Fklstr-rdm\u002Fuse-klstr-dev-hardware",[384,438,440],{"id":439},"the-two-special-builds","The two special builds",[442,443,444,455],"card-group",{},[445,446,447,450,451,382],"card",{"icon":104,"title":348},[327,448,449],{},"On the nano."," Makes the nano offer itself over USB. Downloaded and flashed over RDM\nin ",[434,452,454],{"href":453},"#flash-the-firmware","step 1",[445,456,459,462,463,382],{"icon":457,"title":458},"i-lucide-monitor","usbNano build of KLSTR.ctrl",[327,460,461],{},"On the PC."," Makes KLSTR.ctrl able to see and connect to a USB nano at all.\nDownloaded in ",[434,464,465],{"href":453},"step 5",[384,467,469],{"id":468},"what-you-need","What you need",[332,471,472,475,483,488,495],{},[335,473,474],{},"A KLSTR.nano, either in a KLSTR.rdm box or on a modified KLSTR.dev board",[335,476,477,478,482],{},"The ",[327,479,480],{},[346,481,348],{}," binary file",[335,484,477,485,487],{},[327,486,357],{}," of KLSTR.ctrl, to connect to the nano once it is flashed\n(Windows, about 261 MB)",[335,489,490,491,494],{},"A ",[327,492,493],{},"normal RDM node"," cabled to the nano's DMX IN or DMX OUT port.",[335,496,497,498,501],{},"A PC running ",[327,499,500],{},"KLSTR.ctrl",", any build is enough for the flash itself",[384,503,505],{"id":504},"flash-the-firmware","Flash the firmware",[507,508,510,515,518,525,532,536,547,555,559,566,576,580,590,597,600,653,661,665,668,679,690,696,711,715,719,722,732,736,742],"steps",{"level":509},"3",[511,512,514],"h3",{"id":513},"get-the-snifferklstrnano-binary","Get the sniffer.klstr.nano binary",[323,516,517],{},"Download the firmware and keep it somewhere KLSTR.ctrl can reach during the upgrade.",[519,520],"u-button",{":external":521,"icon":68,"label":522,"size":523,"to":524,"download":348},"true","Download sniffer.klstr.nano","lg","\u002Ffirmware\u002Fsniffer.klstr.nano",[323,526,527,528,531],{},"136 KB. ",[327,529,530],{},"Keep the filename exactly as it is",", KLSTR.ctrl matches on it.",[511,533,535],{"id":534},"cable-an-rdm-node-to-the-nano","Cable an RDM node to the nano",[323,537,538,539,542,543,546],{},"Wire a normal RDM node to the ",[327,540,541],{},"DMX IN"," or ",[327,544,545],{},"DMX OUT"," port of the nano, exactly as you\nwould for any other firmware update over RDM.",[332,548,549,552],{},[335,550,551],{},"Confirm the nano appears in your device list before continuing.",[335,553,554],{},"The USB connection plays no part in this step.",[511,556,558],{"id":557},"put-the-nano-into-firmware-update-mode","Put the nano into firmware update mode",[323,560,561,562,565],{},"Press the ",[327,563,564],{},"firmware update button"," on the nano.",[567,568,569,572,573,382],"note",{"icon":311},[375,570,571],{},"Image pending:"," a photo of the nano's firmware update button.\nSuggested path: ",[346,574,575],{},"\u002Fimages\u002Fklstr-rdm\u002Fnano-update-button.png",[511,577,579],{"id":578},"run-the-update-with-the-sniffer-binary","Run the update with the sniffer binary",[323,581,582,583,586,587,589],{},"In KLSTR.ctrl, open ",[327,584,585],{},"Upgrade Nano Firmware",". The panel at the top shows the selected\nimage, so confirm it reads ",[346,588,348],{}," before going further.",[323,591,592],{},[593,594],"img",{"alt":595,"src":596},"The Upgrade Nano Firmware window in KLSTR.ctrl with sniffer.klstr.nano selected, the Vendorcast and Unicast options, the transfer speed choice, and the device table","\u002Fimages\u002Fklstr-rdm\u002Fnano-update-window.png",[323,598,599],{},"Then work left to right through the window:",[332,601,602,611,628,646],{},[335,603,604,542,607,610],{},[327,605,606],{},"Vendorcast (multiple)",[327,608,609],{},"Unicast (one-by-one)",". Vendorcast updates every\nmatching device at once, unicast walks them individually.",[335,612,613,616,617,620,621,542,624,627],{},[327,614,615],{},"Transfer speed",", one of ",[327,618,619],{},"Fast",", ",[327,622,623],{},"Slow",[327,625,626],{},"Very Slow",".\nTODO: confirm when the slower rates are needed.",[335,629,630,633,634,637,638,641,642,645],{},[327,631,632],{},"Tick the nano"," you are flashing in the device table. The row shows its ",[346,635,636],{},"Nano Uid","\nand current ",[346,639,640],{},"Nano Version",", which is the quickest way to be sure you have the right\none. ",[346,643,644],{},"All \u002F None"," selects the whole list.",[335,647,648,649,652],{},"Press ",[327,650,651],{},"execute",", and let it finish and reboot. That is the whole flash.",[654,655,656,657,660],"tip",{},"The mechanics of firmware delivery over the DMX cable are documented separately in\n",[434,658,40],{"href":659},"\u002Fen\u002Ffirmware-over-rdm\u002Foverview"," if you want to know\nwhat is happening on the bus during this step.",[511,662,664],{"id":663},"get-the-usbnano-build-of-klstrctrl","Get the usbNano build of KLSTR.ctrl",[323,666,667],{},"The other half of the pair, this one on the PC. The standard build does not expose USB\nconnected nanos, so without this build the nano simply never appears.",[567,669,671,674,675,678],{"icon":670},"i-lucide-info",[327,672,673],{},"You did not need this build for the steps above."," The sniffer firmware goes over RDM\nthrough an ordinary RDM node, so any KLSTR.ctrl build can drive that upgrade. The\nusbNano build is what lets you ",[327,676,677],{},"connect to the nano over USB",", which is what the rest\nof this page does.",[323,680,681,682,685,686,689],{},"The build is a ",[327,683,684],{},"Windows"," package of roughly ",[327,687,688],{},"261 MB",", too large to serve from this\nsite, so it is hosted on Google Drive.",[519,691],{":external":521,"icon":692,"label":693,"size":523,"to":694,"target":695},"i-lucide-external-link","Download the usbNano build","https:\u002F\u002Fdrive.google.com\u002Fdrive\u002Ffolders\u002F1s7UpwxNprwp2s4HvSG94pvkODwlM_9sq?usp=share_link","_blank",[323,697,698,699,702,703,706,707,710],{},"The link opens a Drive folder holding a single file,\n",[346,700,701],{},"DEV-klstr-ctrl-windowsBuildDev-…-feat-rdmtester-ui-0f497edf….zip",". Note that this is a\n",[327,704,705],{},"development build"," off the ",[346,708,709],{},"feat-rdmtester-ui"," branch, not a tagged release.",[712,713,714],"caution",{"icon":369},"TODO: confirm what the zip contains, an installer or a run-in-place build.\nTODO: confirm whether a macOS or Linux usbNano build exists, this page assumes Windows.",[511,716,718],{"id":717},"connect-the-nano-to-the-pc-over-usb","Connect the nano to the PC over USB",[323,720,721],{},"Plug the nano into the PC: the box's USB port for a KLSTR.rdm, or the USB-C\nreceptacle for a modified KLSTR.dev board. Make sure you are running the usbNano build\nfrom the previous step.",[323,723,724,725,727,728,731],{},"Running the ",[327,726,357],{},", KLSTR.ctrl now shows the nano as a ",[327,729,730],{},"connectable USB\ndevice",". This is the step where the second special build stops being optional: on the\nstandard build the nano does not appear here at all.",[511,733,735],{"id":734},"connect-and-let-the-nano-become-an-rdm-controller","Connect, and let the nano become an RDM controller",[323,737,738,739,382],{},"Connect to the device in KLSTR.ctrl. It is promoted from a plain device to a full\n",[327,740,741],{},"RDM controller",[567,743,744,746,747,750,751,382],{"icon":311},[375,745,571],{}," the connectable nano as it appears in KLSTR.ctrl, and the same nano\nafter promotion to an RDM controller. Suggested paths:\n",[346,748,749],{},"\u002Fimages\u002Fklstr-rdm\u002Fctrl-nano-connectable.png"," and\n",[346,752,753],{},"\u002Fimages\u002Fklstr-rdm\u002Fctrl-nano-as-rdm-controller.png",[384,755,757],{"id":756},"verify-it-worked","Verify it worked",[323,759,760],{},"The nano is correctly flashed and connected when all of the following are true:",[332,762,763,769,776,781],{},[335,764,765,766,768],{},"KLSTR.ctrl is the ",[327,767,357],{},", otherwise none of the rest can happen",[335,770,771,772,775],{},"It appears in KLSTR.ctrl as a connectable ",[327,773,774],{},"USB"," device, not only as a DMX device",[335,777,778,779],{},"Connecting to it presents it as an ",[327,780,741],{},[335,782,783],{},"Discovery, queries and sniffing are available from the controller view",[384,785,787],{"id":786},"what-next","What next",[445,789,791],{"icon":73,"title":70,"to":790},"\u002Fen\u002Fklstr-rdm\u002Frdm-compliance-testing","Run a structured RDM compliance test against a device under test and read the result.",[384,793,202],{"id":794},"troubleshooting",[392,796,797,807],{},[395,798,799],{},[398,800,801,804],{},[401,802,803],{},"Symptom",[401,805,806],{},"Most likely cause",[408,808,809,817,828,836],{},[398,810,811,814],{},[413,812,813],{},"Nano is visible in KLSTR.ctrl but never offered as a connectable USB device",[413,815,816],{},"Sniffer firmware not flashed, or the flash did not complete. Repeat the update",[398,818,819,822],{},[413,820,821],{},"Nano does not appear in KLSTR.ctrl at all, even though the PC enumerated it",[413,823,824,825,827],{},"Wrong KLSTR.ctrl build. The ",[327,826,357],{}," is required, the standard build never lists USB nanos",[398,829,830,833],{},[413,831,832],{},"Firmware update never starts",[413,834,835],{},"The RDM node cannot reach the nano on DMX IN or DMX OUT. Recheck the cabling",[398,837,838,841],{},[413,839,840],{},"Nothing appears over USB on a modified KLSTR.dev",[413,842,843,844],{},"The hardware modification is wrong, most often D+ \u002F D- not crossed. See ",[434,845,846],{"href":436},"the hardware page",{"title":848,"searchDepth":849,"depth":849,"links":850},"",2,[851,852,853,854,864,865,866],{"id":386,"depth":849,"text":387},{"id":439,"depth":849,"text":440},{"id":468,"depth":849,"text":469},{"id":504,"depth":849,"text":505,"children":855},[856,858,859,860,861,862,863],{"id":513,"depth":857,"text":514},3,{"id":534,"depth":857,"text":535},{"id":557,"depth":857,"text":558},{"id":578,"depth":857,"text":579},{"id":663,"depth":857,"text":664},{"id":717,"depth":857,"text":718},{"id":734,"depth":857,"text":735},{"id":756,"depth":849,"text":757},{"id":786,"depth":849,"text":787},{"id":794,"depth":849,"text":202},"Flash the sniffer firmware onto a KLSTR.nano over RDM so it can operate as a KLSTR.rdm development tool over USB.","md",null,{},{"icon":68},{"title":65,"description":867},"KM8M5UrMEgvTh9tB0fXf1H98od7oXvTDjdWwHCM1BZk",[875,877],{"title":60,"path":61,"stem":62,"description":876,"icon":63,"children":-1},"Modify a KLSTR.dev board so the KLSTR.nano's USB lines reach the USB-C receptacle, turning the board into a KLSTR.rdm development dongle.",{"title":70,"path":71,"stem":72,"description":878,"icon":73,"children":-1},"Start and conduct an RDM compliance test with a KLSTR.rdm connected to KLSTR.ctrl, and read the result.",1787149428897]