From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

Digital Multimeters (DMMs) and Precision DC Sources

cancel
Showing results for 
Search instead for 
Did you mean: 

NI4130 SMU Current Range

Solved!
Go to solution

I am using a PXI 4130 SMU to test a 3V Battery powered RF Transmitter. The Unit goes thru a power on sequence which requires up to 20mA of current then goes into a sleep mode which should draw current in the low uA range. The problem I am having is downranging the 4130 to the lowest range available. The idea is to power up the unit with the SMU set to the 200mA range. After the unit goes thru its power on cycle I need to change the range down to the 200uA range and measure the off current. It appears the SMU is only changing the range on the initial setup. Attached is a snip of my code, any help is greatly appreciated.

0 Kudos
Message 1 of 6
(8,712 Views)

Hi Phil_T,

 

There is a subtle difference between the niDCPower Configure Current Limit VI and the niDCPower Configure Current Limit Range VI.  I've attached the help files for both of these VI's below for your reference:

niDCPower Configure Current Limit VI - NI DC Power Supplies and SMUs 1.4 Help

niDCPower Configure Current Limit Range VI - NI DC Power Supplies and SMUs 1.4 Help

 In your code it looks like you are changing the setting for the current limit range, which really just chooses which current limits you can select but doesn't actually change the current limit.  Try replacing the niDCPower Configure Current Limit Range VI's with niDCPower Configure Current Limit VI's and see if it fixes your issue.

 

Good luck with everything!

Regards,

Jared R.
Precision DC Product Support Engineer
National Instruments
0 Kudos
Message 2 of 6
(8,684 Views)

Thanks for the info, After reviewing the 2 links I did notice that I was using the I Level and I level Range located under the source/DC Current pallete. After swapping to the vi's under the source/DC Voltage pallete, I now get this error.

 

Error -1074118627 occurred at niDCPower Configure Current Limit Range.vi

Possible reason(s):
The range you requested is incompatible with the selected level/limit.  Change both the Range attribute/property and the corresponding level/limit attribute/property when the session is in the Uncommitted state.  For more information, refer to the NI-DCPower documentation.

Conflicting Properties: Current Limit Range, Current Limit
Property: Current Limit Range
Requested Value:  200.0e-6
Supported Ranges:  200.0e-6,  2.0e-3,  20.0e-3,  200.0e-3,  2.000000

Property: Current Limit
Corresponding Value:  100.0e-3
Specified Range Minimum:  4.0e-6
Specified Range Maximum:  200.0e-6

Channel Name: 1

Status Code: -225151

 

I find it odd that my Requested Value of 200.0e-6 should be a supported range however the error is telling me otherwise. I also noticed the error code states I input 100.0e-3 as my current limit however that is not the case as I put 100.0e-6 as my current limit. I then went and changed my Current Limit range value to 100e-6 and the error still states my requested value is 200e-6. It seems to me there is an error with the DLL converting the numbers. I am attaching my condensed code with the updates made according to the previous post.

0 Kudos
Message 3 of 6
(8,673 Views)
Solution
Accepted by topic author Phil_T.

Hi Phil,

 

I rebuilt your code and was able to recreate the error you were experiencing.  I believe I have an answer for you.

 

You will need to replace the niDCPower Initialize VI with the niDCPower Initialize With Channels VI.  The difference is that the Initialize VI places the session with the SMU in the committed state, while the Initialize With Options VI does not.  Because of this you will also need to place an niDCPower Initiate VI before your niDCPower Configure Output Enabled VI.  The programming states of an NI-DCPower session are described in the link below:

Programming States - NI DC Power Supplies and SMUs 1.4 Help
http://zone.ni.com/reference/en-XX/help/370736F-01/ni_dc_power_supplies_help/programmingstates/



I have also attached links going over the details of various functions involved in the code:

 

niDCPower Initialize With Channels VI - NI DC Power Supplies and SMUs 1.4 Help
http://zone.ni.com/reference/en-XX/help/370736F-01/nidcpowerviref/nidcpower_initialize_with_channels...

 

niDCPower Initialize VI - NI DC Power Supplies and SMUs 1.4 Help
http://zone.ni.com/reference/en-XX/help/370736F-01/nidcpowerviref/nidcpower_initialize/

niDCPower Initiate VI - NI DC Power Supplies and SMUs 1.4 Help
http://zone.ni.com/reference/en-XX/help/370736F-01/nidcpowerviref/nidcpower_initiate/



After making the changes I described above, I was able to run the code without generating any errors.

Regards,

Jared R.
Precision DC Product Support Engineer
National Instruments
0 Kudos
Message 4 of 6
(8,665 Views)

Phil,

 

You are running into that error because the session is in the Running state. When in the running state, configuration changes are applied immediately, and you are changing the Current Limit Range to be 200 uA, but the Current Limit is set to 100 mA. You need to either change the Current Limit first to a value that is valid for both the  200 uA range and the 100 mA range, or you can first Abort, then reconfigure both Current Limit Range and Current Limit, then Initialize again.

 

Additionally, keep in mind that you should be changing the Current Limit Range, not the Current Level Range, because you are in DC Voltage Output Function. Changing the Current Level/Current Level Range only take effect when you are in DC Current Output Function.

 

Jared's suggestion of using Initialize with Channels is a good one, as the Initialize method you are using works, but is deprecated.

 

Please let us know if you have any further questions.

 

Tobias Gordon

Staff Software Engineer

Precision DC / Modular Instruments

National Instruments

Tobias
Principal Software Engineer
Driver Software
National Instruments
Message 5 of 6
(8,653 Views)

Thanks Jared and Tobias for your feedback. I was able to fix my problem by using the initialize with options and using the abort and initiate to change ranges.

Phil

0 Kudos
Message 6 of 6
(8,628 Views)