Join us today!
Hey all, I have a training IPC with a cable that connects to different devices. I'd like to be able to use different GVLs for the different remote units, but of course you get duplicate I/O mapping errors. Is there a way to disable a GVL with %I* activation of the I/O instances programmatically, or am I going to have to make some kind of pointers to more generic I/O GVLs? I am used to AB where I can alias multiple tags to the same I/O point
@automatikai Hi, A simple solution would be having an individual GVL for each unit and when connecting to specific unit, you can right click on the GVLs you don't need, properties, select 'Exclude from build'.
@iotea thanks! I was hoping to be able to do it without re-building the solution each time, but it honestly doesn't take that long to do. Right now I am just doing separate conditional mapping routines to generic I/O.
@automatika,
I'm not sure I follow fully, but you may be able to apply either Conditional pragmas or Variant Management
@benhar-dev thanks! The Variant Management might work, right now I have just mapped I/O to generic point variables, then created additional GVLs that link to the generic variables conditionally. I'd like to basically disable the I/O linked GVLs if they aren't being used, sort of swap them out, but it looks like you can only have one variable linked to a terminal point. I have 8-10 different potential training devices that I can swap out on the cable.