LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

16 analog input signals NI 9209

The previous programmer had created one task and added 16 different scales to the task.

Is this the right way to be going about this?

I am getting error 5003. I Google'd this error, but I did not find anything.

 

DAQ isn't my strong suit.

0 Kudos
Message 1 of 5
(2,696 Views)

@nyc_(is_out_of_here) wrote:

The previous programmer had created one task and added 16 different scales to the task.

Is this the right way to be going about this?

It probably is if the 16 channels, in fact, have different Calibration curves (on which the scaling factors are built).

I am getting error 5003. I Google'd this error, but I did not find anything.

Did you try LabVIEW's Explain Error?

Error 5003 occurred at an unidentified location

This error code is undefined. Undefined errors might occur for a number of reasons. For example, no one has provided a description for the code, or you might have wired a number that is not an error code to the error code input.

Additionally, undefined error codes might occur because the error relates to a third-party object, such as the operating system or ActiveX. For these third-party errors, you might be able to obtain a description of the error by searching the Web for the error code (5003) or for its hexadecimal representation (0x0000138B).

 Of course, it's not just the Error #, but also the other Error Information, which often includes the name of the VI in which the Error occurred that can also be a valuable clue.

DAQ isn't my strong suit.


I've got a routine that takes readings from a triaxial accelerometer.  Each channel is linear, with an offset of 1.5±0.15 v, and a sensitivity of 0.3±0.03 v/g.  Needless to say, with a 10% "uncertainty" in the Scale Factors, the prudent thing to do is to "Calibrate First, Acquire Second" (there's a very quick and simple way to calibrate a triaxial accelerometer, takes no equipment and about 15 seconds).  Once calibrated, we derive the DAQmx Scale Factors for these three channels and use them when configuring the DAQ Task.

 

If they are relatively constant, so you can Calibrate Once, Acquire Often, then you may be able to create a Task (in MAX) and embed the Scale Factors in the Task definition.

 

If you need further help, please attach your VI (do not attach a picture of the Block Diagram -- we need to "see the details").

 

Bob Schor

0 Kudos
Message 2 of 5
(2,686 Views)

@nyc_(is_out_of_here) wrote: I am getting error 5003. I Google'd this error, but I did not find anything.

That is because that error code is in the range of error codes NI allocated for "custom error codes".  Whoever wrote that code did something to create that error.  Time to start searching in the code.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 3 of 5
(2,679 Views)

It turns out that

1.  he never starts the Task he created

2.  the slope and intercept he was using did not match with the Min/Max values

 

I am learning as I go along.

 

 

0 Kudos
Message 4 of 5
(2,660 Views)

@Bob_Schor wrote:

@nyc_(is_out_of_here) wrote:

The previous programmer had created one task and added 16 different scales to the task.

Is this the right way to be going about this?

It probably is if the 16 channels, in fact, have different Calibration curves (on which the scaling factors are built).

I am getting error 5003. I Google'd this error, but I did not find anything.

Did you try LabVIEW's Explain Error?

Error 5003 occurred at an unidentified location

This error code is undefined. Undefined errors might occur for a number of reasons. For example, no one has provided a description for the code, or you might have wired a number that is not an error code to the error code input.

Additionally, undefined error codes might occur because the error relates to a third-party object, such as the operating system or ActiveX. For these third-party errors, you might be able to obtain a description of the error by searching the Web for the error code (5003) or for its hexadecimal representation (0x0000138B).

 Of course, it's not just the Error #, but also the other Error Information, which often includes the name of the VI in which the Error occurred that can also be a valuable clue.

DAQ isn't my strong suit.


I've got a routine that takes readings from a triaxial accelerometer.  Each channel is linear, with an offset of 1.5±0.15 v, and a sensitivity of 0.3±0.03 v/g.  Needless to say, with a 10% "uncertainty" in the Scale Factors, the prudent thing to do is to "Calibrate First, Acquire Second" (there's a very quick and simple way to calibrate a triaxial accelerometer, takes no equipment and about 15 seconds).  Once calibrated, we derive the DAQmx Scale Factors for these three channels and use them when configuring the DAQ Task.

 

If they are relatively constant, so you can Calibrate Once, Acquire Often, then you may be able to create a Task (in MAX) and embed the Scale Factors in the Task definition.

 

If you need further help, please attach your VI (do not attach a picture of the Block Diagram -- we need to "see the details").

 

Bob Schor


excellent points for a newbie like me

will definitely keep in mind

 

 

.

0 Kudos
Message 5 of 5
(2,659 Views)