Handling same MAX aliases

[1984]

Hi community,

I have created two cDAQ based measurement devices. Both are completly identical in terms of the modules, wiring etc as they must do exactly the same job. Each one of these systems has its own PC and on the PC I use the same MAX aliases and global virtual channels associated to the modules.

Now imagine the scenario that I unplug system#1 from PC#1. In this case the chassis and the modules in MAX are still visible although they are showed as "not present". Now if I plug system#2 the PC#1 this system will get the default name for the modules. To make everything work I have to delete the "not present" unit and rename each one of the modules from the default to the right aliases. This is an error prone and quite annoying activity.

How can I make MAX working in a way that if I plug the same hardware configuration then it assigns the same name to that so it can be used immediately instead of tweaking?

thanks!

[Eric-E]

Hello 1984,

I reproduced the behavior, and after thinking about the issue for a while, if you delete your first chassis from MAX before attaching the 2nd chassis and if the names of the modules are default, then the 2nd chassis will be identified with the same aliases as the first chassis originally was. 

I recommend creating the tasks from the first chassis using the default alias names. Then disconnect the chassis and delete the unconnected chassis from MAX. Reconnect the 2nd chassis. Connect the 2nd chassis and you should have the default names populated that apply to the original tasks.

I hope this helps. Best regards,

Eric-E

[1984]

Thanks mate, I appreciate your idea and I understand that it would work. But it kills flexibility on a level what I cant accept. I am not gonna call my modules something like cDAQ1mod1, because mod1 can mean anything. Thats why I call them DI, DO, RLY, AI etc, because thats identify them. Moreover with this notation I can store the modules in any slot while mod1 defines that its in the first slot.