Signal Conditioning

cancel
Showing results for 
Search instead for 
Did you mean: 

error 10007

Hi Hedgehog123,
 
Is this a new problem?  Were you ever able to use VI logger to test all 11 transducers?  I find it peculiar that this applications works fine in LabVIEW but not in VI Logger.  But this information does let us know that the hardware is not actually damaged.  Is there a reason you do not want to use LabVIEW? 
 
Unfortunately the AT-16E-4 is a legacy device that I do not have access to for testing.  My only other recommendation is to ensure you are using the latest Traditional NI-DAQ driver version 7.4.4  and VI Logger Full.
 
 
Regards,

Ima
Applications Engineer
National Instruments
LabVIEW Introduction Course - Six Hours
Getting Started with NI-DAQmx
0 Kudos
Message 11 of 19
(2,944 Views)
Hi Ima,
 
We have been trying to use this software for the past year, but due to elongated forum conversations and work inbetween, we haven't managed to get it to work.  We upgraded to the VI logger as it has all the requirements that are needed for our work and also works with our upgraded XP system on the new computer.  I can only get 4 of the transducers to work... all the same transducers.  The rest will not work at all, combined with the other 4 or by themselves. 
 
I have attached a photo of the error message that we get (we get a 10007 AI config error) when trying to run the tasks in VI logger and the 10007 error that I get in MAX when trying to configure my transducers....Error 10007 occurred at AI group config.
NI-DAQ LV: A channel, port, or counter is out of range for the device type or device configuration, or the combination of the channels is not allowed, or the scan order must be reversed (0) first.
 
We uninstalled everything yesterday, reinstalled with the Traditional Legacy 7.4.4 software, we have the full VI Logger so I am now at a bit of a loss as to what to do.  I have tried to change the scan order but there is no reference on any of the help groups as to what is specifically required from start to finish to do that!  I am a complete novice at this so need an almost step by step thing in order to check it all!
 
None of the channels seem to be out of range (where can I definitely check for this?)
How can the combination of channels not work?
How do I know in what order the scan is being done and how do I go about reversing it to check it?
I have changed the channel names in MAX whcih seems to directly affect the stuff in VI Logger.  I have changed them so they are individually named 0-11.  The are all referenced single ended. All running in Analog.  This still doesn't work!
 
Still bashing my head against a wall - help please!!
Download All
0 Kudos
Message 12 of 19
(2,917 Views)

Hi Hedgehod123,

I understand your frustration.  I am also having difficulties understanding the source of the error.  So let us step back and try to narrow it down to either the version of VI Logger, the NI-DAQ card or the transducers. 

To test the DAQ card, I would like you to send in DC voltages (1 per channel) of the DAQ card to make sure the DAQ card works.  Make sure to use a voltage with-in the specifications for the DAQ card.  Read the voltages using VI logger to ensure that your AT-16E-4 is functioning properly. 

What version of VI logger do you have? 

Regards,

Ima
Applications Engineer
National Instruments
LabVIEW Introduction Course - Six Hours
Getting Started with NI-DAQmx
0 Kudos
Message 13 of 19
(2,891 Views)

Hi Ima

Sorry for the frustration... it just takes a day to relearn everything about the programme and then I still come up against a brick wall!

I was wondering, since we use the same voltage/DC input as we do in Labview, is it likely that we would have to change it for VI Logger?  We are using VI Logger version 2.0.1.

I will have a check to see if there is a difference in the manual.

Thanks again for your help... hopefully we will ge there soon!

Alexis

0 Kudos
Message 14 of 19
(2,885 Views)

Hi Ima

Sorry for the frustration... it just takes a day to relearn everything about the programme and then I still come up against a brick wall!

I was wondering, since we use the same voltage/DC input as we do in Labview, is it likely that we would have to change it for VI Logger?  We are using VI Logger version 2.0.1.

I will have a check to see if there is a difference in the manual.

Thanks again for your help... hopefully we will get there soon!

Alexis

0 Kudos
Message 15 of 19
(2,885 Views)

Hi Ima

Sorry for the frustration... it just takes a day to relearn everything about the programme and then I still come up against a brick wall!

I was wondering, since we use the same voltage/DC input as we do in Labview, is it likely that we would have to change it for VI Logger?  We are using VI Logger version 2.0.1.

I will have a check to see if there is a difference in the manual.

Thanks again for your help... hopefully we will get there soon!

Alexis

0 Kudos
Message 16 of 19
(2,885 Views)

Hi Alexis,

Upon your email request, I've read through your forum post. Let me try and explain a few of the areas where there appears to be confusion.

First of all, both VI Logger and LabVIEW are application development environments which use the NI DAQ software layer to control the AT-16E-4 board which you are using to log data. While they are two different environments, in the background they are accessing and controlling the hardware in the same way so if your hardware is working in one environment but not the other, then you are accessing the driver software differently in them. You need to look at how you are configuring your tasks in both environments and figure out the differences.

Secondly, from your posts, you appear to consider the transducers to be intelligent components of your system. This is not the case. The transducers are simply providing the AT-16E-4 data acquisition board with a voltage which it converts to a digital signal to be interpreted by the NI DAQ driver, and in turn the application software (whether it be LabVIEW or VI Logger).

I need you to clarify the issue you're having. Early on in the post, you describe an issue where 1-4 of your transducers work when connected to the adaptor you have for the DAQ board but as soon as you plug any of the other 7 into the board you don't get a reading.

Is this the point where you get error 10007?

Do you change anything in your VI Logger task configuration when you plug a different transducer in?

We could really do with more information on how you're configuring the VI Logger task. Have you created a Virtual Channel for all your transducers? Do you always set the physical channel to be one of the 4 DAQ board channels that your transducer adaptor is connected to?

In VI Logger, the scan list will be the order in which your virtual channels are listed in VI Logger. If the adaptor that connects your transducers to the DAQ board is connected to CH0-3, then you should try and put your virtual channels in that order.

If any of this isn't clear or if you have a specific question then please let me know, but really there isn't much I can do to help without more information on your system.

Sarah

Applications Engineer | National Instruments | UK & Ireland
0 Kudos
Message 17 of 19
(2,857 Views)

Hi Sarah,

Having checked all the connections with the system, parts etc and the fact that the system we already have set up seems to work in Labview, I think it is something that I am missing in VI Logger that I haven't changed.  In reply to your questions see the highlighted bits. 

OK point number 1 - Can you tell me the difference between the virtual channels and the physical channels and how they relate to the scanning process that I seem to see a lot on the discussion forums?

Early on in the post, you describe an issue where 1-4 of your transducers work when connected to the adaptor you have for the DAQ board but as soon as you plug any of the other 7 into the board you don't get a reading. This is correct.  These 7 do not work at all, individually or combined but when plugged in alongside of the other 7 transducers, they stop the 4 working ones from providing any readings .  I get an error message when I run a test on the individual transducers (the 10007 ones).

Is this the point where you get error 10007? Yes.

Do you change anything in your VI Logger task configuration when you plug a different transducer in?  I change the individual channels through which the transducers are logged... each has its own i.e. ch0 - 1, ch1 - 2, ch3 - 3. 

We could really do with more information on how you're configuring the VI Logger task. Have you created a Virtual Channel for all your transducers? When you say virtual channel what do you mean?  Are the virtual channels relating to the actual physical channel... where it is plugged in i.e. channel 0, channel 1 etc?  How can I change the virtual channel if this is not the case?    Can you send me a screen print of where it is on the programme, please? Each transducer had its own name i.e t1, t2, t3, etc, own scale and each transducer has a different scale already set up on VI Logger. When we reloaded the VI Logger, I noticed that the transducer scales were all the same (I haven't changed them) as they were before we took VI Logger off the computer.

Do you always set the physical channel to be one of the 4 DAQ board channels that your transducer adaptor is connected to? Yes ie. ch0 - 1, ch1 - 2, ch3 - 3.  We only have 4 available channels.  I have noticed that the physical channels may refer to the same one as another.  ie i plug in T1 to ch0, T2 to ch1 but the other remaining transducers are not plugged in but may refer to ch0 or ch1.  will this create a problem?

In VI Logger, the scan list will be the order in which your virtual channels are listed in VI Logger. If the adaptor that connects your transducers to the DAQ board is connected to CH0-3, then you should try and put your virtual channels in that order. How do I change the virtual channel and what is the way to change it correctly when all the other channels may point to the same one (that is if ch0, ch1, ch2 etc are chosen).  Does every single one need to have an individual channel?  Can you send me a screen print of where it is on the programme, please?

Sorry to ask what are probably quite basic questions, but the manuals are difficult to decipher unless you have been using the system for a long time.
Thanks again for trying to decipher our problem!
0 Kudos
Message 18 of 19
(2,854 Views)

Please find attached a guide of the process that we go through in order to get our VI Logger to work.  This is the whole process that we got through in order to ensure that one of the 4 transducers that work, work.  Where we are going wrong with the other 7, I do not know.

 

0 Kudos
Message 19 of 19
(2,809 Views)