Don't dive in to OOP until after you've been using LabVIEW for a while. It's never really needed for anything, but it makes some stuff easier and more modular once you know what you're doing.
You could solve what you're doing by just using an Enum that includes an item for each piece of hardware that you want to use. Have a case structture somewhere that runs the corresponding code when that enum value is changed.
The OOP version of this is to use a parent "Motion Hardware" class that has child classes for the different hardware types ad uses dynamic dispatch VIs to control which piece of hardware code to use. But like I said, this is for developers who know more what they're doing with LV and have the time to experiment a bit before coding at least.
