Error -10401 occurred at AI Group Config

[Kevin_Price]

Note: more discussion generated from repost over here.  Let's all move over to that thread.

-Kevin P

[vadim.santos]

Yeah, Kevin is right, should have posted here since the begining.

Here's the link: https://www.dropbox.com/s/75dvlpqpcb88aaw/Prog.vi?dl=0

[JÞB]

Picking up from Ben & Kevin's hints....

The new motherboard has a new PCI bus and there is likely a registry entry reserving the device enumeration. 

Power down, Pull the boards, reboot, clear the MAX config (reset MAX database)

Reboot

Power down 

Reinstall the device1

Power up

Power down

Reinstall device 2

Power up

In that order exactly.   You should be golden then.

[Ben]

That drop box link is malformed and useless for me.

Zip up the code and attach it to this thread.

The code may give us a clue as to why things have gone south after the mother board was replaced.

Ben

[Kevin_Price]

Memory's fuzzy, but here's what else I see in the code that may require some work in MAX:

The calls to "AI Group Config" have both a hardcoded device # *and* a hardcoded set of virtual channels with names like T_1_10, T_1_11, etc. for device #1 and T_2_10, T_2_11, etc. for device #2.

1. It will be necessary that these are defined and configured correctly in MAX.  Hopefully that part's still intact through the motherboard change.

2. I notice consecutive commas in the list of virtual channels for device #2.  It starts "T_2_10,,T_2_11,T_2_12".  Maybe you need to delete the extra one?  (But if that clears things up, then the same code should have been throwing the error with the old motherboard.  Which suggests that the source code may have been changed.)

-Kevin P

[Kevin_Price]

Wait!!!  Don't follow Jeff's advice to reset the MAX database, at least not *yet*!

As I just mentioned in my last msg, the code depends on a bunch of virtual channels whose definitions would be lost with a MAX database reset.  At the moment, it's not yet clear to me that you *need* a MAX database reset and it may well be harmful.

(Note: such a reset is often good advice.  Maybe not this time though).

-Kevin P

[vadim.santos]

Ben...

[Ben]

---

@Kevin_Price wrote:

Memory's fuzzy, but here's what else I see in the code that may require some work in MAX:

The calls to "AI Group Config" have both a hardcoded device # *and* a hardcoded set of virtual channels with names like T_1_10, T_1_11, etc. for device #1 and T_2_10, T_2_11, etc. for device #2.

1. It will be necessary that these are defined and configured correctly in MAX.  Hopefully that part's still intact through the motherboard change.

2. I notice consecutive commas in the list of virtual channels for device #2.  It starts "T_2_10,,T_2_11,T_2_12".  Maybe you need to delete the extra one?  (But if that clears things up, then the same code should have been throwing the error with the old motherboard.  Which suggests that the source code may have been changed.)

-Kevin P

---

I have been burned by Virtual channels in MAX that either were lost or not supported with LV upgrades. I avoid them like the plague now and do most of my IO config using fist principles and never mess with setting thing up in MAX. Much too fragile.

We could be fiddling with MAX for a long time until it is all set-up correctly.

Bad Joke time!

Spoiler

Configurations in MAX and unreliable third party hardware device sooner or latter we have to fiddle with thing to get it working. I have a code term I use when reporting to my better half;

Fe Fi Fiddly IO

(my apologies to Stephan Foster)

Groans are expected.

Ben

[vadim.santos]

Speaking of channels...

[Ben]

Yes, Kevin is correct about hard-coded virtual channels.

The device ID's of those two boards should be 1 and 2 (not 15).

The syntax is weird but it looks like only two channels used on each device.

Ben