In labs and test setups, the same instrument can often be accessed through multiple VISA vendors. Each vendor may differ slightly in features and performance, which makes picking the right one important. Not every device works with every vendor — some rely on one in particular.
Nodevisa Affinity allows to make that choice. By introducing vendor-aware mappings, Nodevisa can tranparently select the most suitable match for each device — whether broad (e.g., ni) or specific (e.g., ni_25_3). This means instruments are bound to the vendor that serves them best, while you keep full compatibility with existing VISA code.
Why it matters: mixed environments and driver versions are a reality. Affinity reduces friction by keeping your configs readable and resilient without breaking compatibility with VISA code. It’s one more step toward a developer-first experience—clean, predictable, and ready for real-world labs.
Have thoughts on matching strategies or edge cases we should cover? Jump into Slack and help us tune the defaults.
If you’d like early access and are ready to explore the alpha, hop into our Slack channel and let us know — we’re opening invites in small batches.