cDAQ Error - 200220

[Mitch_Peplow]

Morning all,

I need some help with a vi I’m trying to run as it keeps on throwing up an error as soon as I try to run the code; the error code is 200220. The error appears to be with the physical channels that I am specifying to look at or the name of the path but I have re-initialized the names to the default and it will still not work. I have looked on the FAQ and forums but none of the resolutions
have worked.

Please see the attached images; one is of the error code that comes up, another is of the module as it appears in MAX, another is of the channel setup code, one of the DAQ timing and another of the overall code. It would be better to open them up in paint as the normal picture viewer appears to compress the images (on my pc anyway). On the overall code picture, the SubVI named
DAQ CONF contains the channel setup code and the SubVI named DAQ TIMING contains the timing code.

The code allowed me to save and compile it into an .exe so I don’t believe anything is missing. I did try renaming the devices originally to something more meaningful but the error started on channel 1 whereas it now starts on channel 3 which is the first channel I’m trying to look at so there is definitely something strange going on.

Cheers for looking, much appreciated

Regards

Mitch

[RCampbell]

Hi Mitch85,

It looks like the problem is with the physical channels input to the 3rd Create Channel VI.  You have input "cDAQMod5" where I assume you meant "cDAQ1Mod5".  I hope this helps.

[Mitch_Peplow]

Hi RCampbell,

Many thanks for the reply, worked a treat.

I should elaborate a little more as this will lead onto another question.

I ended up re-setting all the device names after trying to re-name them to something more suitable for the rig. I wanted to change the chassis name from 'cDAQ1' to 'ZFG' and the module from 'cDAQ1Mod5' to 'Analogue_Inputs'

However when I tried this, it complained with the same error but started on channel 1 and no matter what I did, it would not run.

Is it possible to rename the chassis and module and if so, is there a specific name layout that has to be followed or certain information that must be included such as the module number? So say I wanted to rename the chassis and module as ZFG and Analogue_Inputs respectively, would I need to point to path ZFGAnalogue_Inputs on the channel setup VI?

Cheers

Mitch

[RCampbell]

Hi Mitch,

There is no naming convention necessary for renaming your chassis and modules.  In your example, if you change the module name to "Analogue_Inputs", you should be able to change your physical channel inputs to "Analogue_Inputs/ai3", "Analogue_Inputs/ai7", and "Analogue_Inputs/ai5".

[Mitch_Peplow]

Do I not need to specify the chassis it is on?

Cheers

Mitch

[RCampbell]

No, you do not need to specify which chassis the module is on.

[Mitch_Peplow]

So when to specify a name, does it actually write that name to the module or does it simply assign that name to the slot?

So say I rename the Module in slot 5 to Lizard, then I move the module physically to slot 6, will the name transfer along with the module or will the slot need to be re-named to Lizard?

Cheers

[RCampbell]

If you rename a module in slot 5 to "Lizard", then move that module to another slot, you will have rename the module again.  If you were then to insert a different module into slot 5, that module name would be [chassisName]Mod5.

[Mitch_Peplow]

So as soon as you pull a module out (if hot swapping), you loose all naming convention then when another module, or even the one you just pulled out, gets re-inserted, the default name is applied.

So this is only true if no module is present when power is on as it obviousley keeps the current module name if the chassis is powered up with a module in that slot?

[Seth_B.]

Basically, the name is tied to a combination of chassis, module, and slot.  If you change any of the above, the naming convention is lost.  However, power cycling will still maintain the name.