AnsweredAssumed Answered

Programming Lists on N3300A DC Electronic Load

Question asked by ruben on Apr 5, 2011
Latest reply on Jul 11, 2011 by MattC

Like • Show 0 Likes0
Comment • 8

Hi,

I am programming a measurement from a list through the Linux-GPIB package and Python, below you will see the code. My problem comes when I try to read the buffer. If I use 'FETC:ARR:VOLT?', it just deliver an instantaneus measurement but if I use 'FETC:CURR:ARR ARRAY1' the electronic load shows: ERR -113, Undefined header [operation not allowed for this device]. How could I read back the voltage values corresponding to the nine points showed in the list?

Thanks a lot in advance,
Regards,
Rubén

import gpib
from time import sleep

def lista():
     self = gpib.find('eload')
     #LIST
     gpib.write(self,'CURR:MODE LIST')
     gpib.write(self,'LIST:CURR 1,0.9,0.8,0.7,0.6,0.5,0.4,0.3,0.2')
     gpib.write(self,'LIST:CURR:SLEW 1E+6')
     gpib.write(self,'LIST:CURR:RANG 10')
     gpib.write(self,'LIST:CURR:TLEV 0')
     gpib.write(self,'LIST:DWEL 0.1,0.1,0.1,0.1,0.1,0.1,0.1,0.1,0.1')
     #
     gpib.write(self,'SENS:SWE:POIN 1')
     gpib.write(self,'SENS:SWE:TINT 0.05')
     gpib.write(self,'SENS:SWE:OFFS 0')
     gpib.write(self,'LIST:STEP ONCE')
     #Inicializacion
     gpib.write(self,'INIT:NAME LIST')
     gpib.write(self,'INIT:NAME ACQ')
     #Sincronizado
     gpib.write(self,'TRIG:SEQ2:COUN 9')
     gpib.write(self,'TRIG:TIM 2')
     gpib.write(self,'TRIG:SOUR TIM')
     print 'Pausa para realizar la adquisicion'
     sleep(20)
     #Medida
     gpib.write(self,'FETC:ARR:VOLT?')
     res = gpib.read(self,512)
        print res

No one else has this question

Outcomes

ruben Apr 7, 2011 2:52 AM

Sorry, I have realised that I was specifying the number of triggered measurements, 'TRIG:SEQ2:COUN 9', after the initiation of the list and the trigger system so that the instrument was just performing one measurement. However, if I specify it before (please, see code below) when initiating the acquisition the error 601 (too many sweep points) occur. I have also check it by using four or less acquisition triggers and it is working properly. Any idea why I could not measure more than four data points, what is wrong?

Thanks in advance,
Rubén

import gpib
from time import sleep
def lista():
   self = gpib.find('eload')
   #LIST
   gpib.write(self,'CURR:MODE LIST')
   gpib.write(self,'LIST:CURR 1,0.9,0.8,0.7,0.6,0.5,0.4,0.3,0.2')
   gpib.write(self,'LIST:CURR:SLEW 1E+6')
   gpib.write(self,'LIST:CURR:RANG 10')
   gpib.write(self,'LIST:CURR:TLEV 0')
   gpib.write(self,'LIST:DWEL 0.1')

   gpib.write(self,'TRIG:SEQ2:COUN 9')

   gpib.write(self,'SENS:SWE:POIN 1')
   gpib.write(self,'SENS:SWE:TINT 0.05')
   gpib.write(self,'SENS:SWE:OFFS 0')
   gpib.write(self,'LIST:STEP ONCE')
   #Inicializacion
   gpib.write(self,'INIT:NAME LIST')
   gpib.write(self,'INIT:NAME ACQ')
   #Sincronizado
   gpib.write(self,'TRIG:TIM 2')
   gpib.write(self,'TRIG:SOUR TIM')
   print 'Pausa para realizar la adquisicion'
   sleep(20)
   #Medida
   gpib.write(self,'FETC:ARR:VOLT?')
   res = gpib.read(self,512)
        print res

Actions

StevenLee

Apr 15, 2011 1:59 PM

Hi,

Let me try get a unit to try out the code and get back to you on this.

Steven

Actions

ruben Apr 18, 2011 5:45 AM

Thanks a lot!

Rubén

Actions

StevenLee

Apr 29, 2011 7:21 AM

Hi Ruben,

I had a chance to try out your code today. After taking a good look at it, I realize that I don't quite understand it. I see the first portion is where you set up a current list with 9 points with a dwell time of 0.1 seconds. After that I see you try to setup some sort of measurement system and that's where I am confused. Are you just trying to get a voltage reading at each step of the list? Instead of me working off your code, it might be more convenient for me to try generate my own code and send it to you. Does my description above accurate capture what you want to do?

Steven

Actions

ruben Apr 29, 2011 8:09 AM

Hi Steven,

Exactly, I was trying to measure the voltage reading at each step of the current list. If you are so kind to generate the code, I would be so thankful.

Best regads,
Rubén

Actions

maura84 Jul 7, 2011 1:06 AM

Hi,
I have the same problem. I am trying to program a measurement with a triggered list but the error 601 (too many sweep points)everytime stops my acquisition. The acquisition works with four or less steps but if I increase steps number the program fails.
Rubén, did you find any solution for this problem? Any idea how I could fix it?

Thanks in advance for your help,
Maura

Actions

ruben Jul 9, 2011 5:32 AM

Hi Maura,

Sorry, I still do not understand what was missing with these trigger model. However, if you would not mind the list to be executed secuentially after one starting trigger, then you can use the STEP AUTO model. I tried and it works fine.

Regards,
Rubén

Actions

MattC

Jul 11, 2011 10:56 AM

Hi, I think I can help here:

What you are running into here is the fact that the Trigger count command is for the entire mainframe. If you have more than one load channel installed, you will get this error if you do not change the number of measurement points on the channels that you are not doing the triggered measurement on. The default number of measurement points is 1000 The maximum number of points that can be set for a single module is 4096. Doing the math:

4 * 1000 = 4000 which is OK
5 * 1000 = 5000 which is greater than the 4096 maximum.

The way around this error is to change the points in the channels that you are not doing triggered measurements on to a number that would result in a total number of points less than 4096. For example if you want to do 5 sweeps, it needs to be 4096/5= 819 points.

Actions

8 Replies

ruben Apr 7, 2011 2:52 AM
Mark Correct
Correct Answer
Sorry, I have realised that I was specifying the number of triggered measurements, 'TRIG:SEQ2:COUN 9', after the initiation of the list and the trigger system so that the instrument was just performing one measurement. However, if I specify it before (please, see code below) when initiating the acquisition the error 601 (too many sweep points) occur. I have also check it by using four or less acquisition triggers and it is working properly. Any idea why I could not measure more than four data points, what is wrong?

Thanks in advance,
Rubén

import gpib
from time import sleep
def lista():
   self = gpib.find('eload')
   #LIST
   gpib.write(self,'CURR:MODE LIST')
   gpib.write(self,'LIST:CURR 1,0.9,0.8,0.7,0.6,0.5,0.4,0.3,0.2')
   gpib.write(self,'LIST:CURR:SLEW 1E+6')
   gpib.write(self,'LIST:CURR:RANG 10')
   gpib.write(self,'LIST:CURR:TLEV 0')
   gpib.write(self,'LIST:DWEL 0.1')

   gpib.write(self,'TRIG:SEQ2:COUN 9')

   gpib.write(self,'SENS:SWE:POIN 1')
   gpib.write(self,'SENS:SWE:TINT 0.05')
   gpib.write(self,'SENS:SWE:OFFS 0')
   gpib.write(self,'LIST:STEP ONCE')
   #Inicializacion
   gpib.write(self,'INIT:NAME LIST')
   gpib.write(self,'INIT:NAME ACQ')
   #Sincronizado
   gpib.write(self,'TRIG:TIM 2')
   gpib.write(self,'TRIG:SOUR TIM')
   print 'Pausa para realizar la adquisicion'
   sleep(20)
   #Medida
   gpib.write(self,'FETC:ARR:VOLT?')
   res = gpib.read(self,512)
        print res
Like • Show 0 Likes0
Actions
StevenLee Apr 15, 2011 1:59 PM
Mark Correct
Correct Answer
Hi,

Let me try get a unit to try out the code and get back to you on this.

Steven
Like • Show 0 Likes0
Actions
ruben Apr 18, 2011 5:45 AM
Mark Correct
Correct Answer
Thanks a lot!

Rubén
Like • Show 0 Likes0
Actions
StevenLee Apr 29, 2011 7:21 AM
Mark Correct
Correct Answer
Hi Ruben,

I had a chance to try out your code today. After taking a good look at it, I realize that I don't quite understand it. I see the first portion is where you set up a current list with 9 points with a dwell time of 0.1 seconds. After that I see you try to setup some sort of measurement system and that's where I am confused. Are you just trying to get a voltage reading at each step of the list? Instead of me working off your code, it might be more convenient for me to try generate my own code and send it to you. Does my description above accurate capture what you want to do?

Steven
Like • Show 0 Likes0
Actions
ruben Apr 29, 2011 8:09 AM
Mark Correct
Correct Answer
Hi Steven,

Exactly, I was trying to measure the voltage reading at each step of the current list. If you are so kind to generate the code, I would be so thankful.

Best regads,
Rubén
Like • Show 0 Likes0
Actions
maura84 Jul 7, 2011 1:06 AM
Mark Correct
Correct Answer
Hi,
I have the same problem. I am trying to program a measurement with a triggered list but the error 601 (too many sweep points)everytime stops my acquisition. The acquisition works with four or less steps but if I increase steps number the program fails.
Rubén, did you find any solution for this problem? Any idea how I could fix it?

Thanks in advance for your help,
Maura
Like • Show 0 Likes0
Actions
ruben Jul 9, 2011 5:32 AM
Mark Correct
Correct Answer
Hi Maura,

Sorry, I still do not understand what was missing with these trigger model. However, if you would not mind the list to be executed secuentially after one starting trigger, then you can use the STEP AUTO model. I tried and it works fine.

Regards,
Rubén
Like • Show 0 Likes0
Actions
MattC Jul 11, 2011 10:56 AM
Mark Correct
Correct Answer
Hi, I think I can help here:

What you are running into here is the fact that the Trigger count command is for the entire mainframe. If you have more than one load channel installed, you will get this error if you do not change the number of measurement points on the channels that you are not doing the triggered measurement on. The default number of measurement points is 1000 The maximum number of points that can be set for a single module is 4096. Doing the math:

4 * 1000 = 4000 which is OK
5 * 1000 = 5000 which is greater than the 4096 maximum.

The way around this error is to change the points in the channels that you are not doing triggered measurements on to a number that would result in a total number of points less than 4096. For example if you want to do 5 sweeps, it needs to be 4096/5= 819 points.
Like • Show 0 Likes0
Actions

Programming Lists on N3300A DC Electronic Load

Outcomes

Related Content

Recommended Content