to activate or cancel the filter
# option.
# The default value is: YES.
# This tag requires that the tag GENERATE_HTML is set to YES.
SEARCHENGINE = YES
# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
# implemented using a web server instead of a web client using Javascript. There
# are two flavors of web server based searching depending on the EXTERNAL_SEARCH
# setting. When disabled, doxygen will generate a PHP script for searching and
# an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
# and searching needs to be provided by external tools. See the section
# "External Indexing and Searching" for details.
# The default value is: NO.
# This tag requires that the tag SEARCHENGINE is set to YES.
SERVER_BASED_SEARCH = NO
# When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
# script for searching. Instead the search results are written to an XML file
# which needs to be processed by an external indexer. Doxygen will invoke an
# external search engine pointed to by the SEARCHENGINE_URL option to obtain the
# search results.
#
# Doxygen ships with an example indexer (doxyindexer) and search engine
# (doxysearch.cgi) which are based on the open source search engine library
# Xapian (see: http://xapian.org/).
#
# See the section "External Indexing and Searching" for details.
# The default value is: NO.
# This tag requires that the tag SEARCHENGINE is set to YES.
EXTERNAL_SEARCH = NO
# The SEARCHENGINE_URL should point to a search engine hosted by a web server
# which will return the search results when EXTERNAL_SEARCH is enabled.
#
# Doxygen ships with an example indexer (doxyindexer) and search engine
# (doxysearch.cgi) which are based on the open source search engine library
# Xapian (see: http://xapian.org/). See the section "External Indexing and
# Searching" for details.
# This tag requires that the tag SEARCHENGINE is set to YES.
SEARCHENGINE_URL =
# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
# search data is written to a file for indexing by an external tool. With the
# SEARCHDATA_FILE tag the name of this file can be specified.
# The default file is: searchdata.xml.
# This tag requires that the tag SEARCHENGINE is set to YES.
SEARCHDATA_FILE = searchdata.xml
# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
# EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
# useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
# projects and redirect the results back to the right project.
# This tag requires that the tag SEARCHENGINE is set to YES.
EXTERNAL_SEARCH_ID =
# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
# projects other than the one defined by this configuration file, but that are
# all added to the same external search index. Each project needs to have a
# unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
# to a relative location where the documentation can be found. The format is:
# EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
# This tag requires that the tag SEARCHENGINE is set to YES.
EXTRA_SEARCH_MAPPINGS =
#---------------------------------------------------------------------------
# Configuration options related to the LaTeX output
#---------------------------------------------------------------------------
# If the GENERATE_LATEX tag is set to YES, doxygen will generate LaTeX output.
# The default value is: YES.
GENERATE_LATEX = NO
# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
# it.
# The default directory is: latex.
# This tag requires that the tag GENERATE_LATEX is set to YES.
LATEX_OUTPUT = latex
# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
# invoked.
#
# Note that when enabling USE_PDFLATEX this option is only used for generating
# bitmaps for formulas in the HTML output, but not in the Makefile that is
# written to the output directory.
# The default file is: latex.
# This tag requires that the tag GENERATE_LATEX is set to YES.
LATEX_CMD_NAME = latex
# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
# index for LaTeX.
# The default file is: makeindex.
# This tag requires that the tag GENERATE_LATEX is set to YES.
MAKEINDEX_CMD_NAME = makeindex
# If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX
# documents. This may be useful for small projects and may help to save some
# trees in general.
# The default value is: NO.
# This tag requires that the tag GENERATE_LATEX is set to YES.
COMPACT_LATEX = NO
# The PAPER_TYPE tag can be used to set the paper type that is used by the
# printer.
# Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
# 14 inches) and executive (7.25 x 10.5 inches).
# The default value is: a4.
# This tag requires that the tag GENERATE_LATEX is set to YES.
PAPER_TYPE = a4
# The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
# that should be included in the LaTeX output. The package can be specified just
# by its name or with the correct syntax as to be used with the LaTeX
# \usepackage command. To get the times font for instance you can specify :
# EXTRA_PACKAGES=times or EXTRA_PACKAGES={times}
# To use the option intlimits with the amsmath package you can specify:
# EXTRA_PACKAGES=[intlimits]{amsmath}
# If left blank no extra packages will be included.
# This tag requires that the tag GENERATE_LATEX is set to YES.
EXTRA_PACKAGES =
# The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
# generated LaTeX document. The header should contain everything until the first
# chapter. If it is left blank doxygen will generate a standard header. See
# section "Doxygen usage" for information on how to let doxygen write the
# default header to a separate file.
#
# Note: Only use a user-defined header if you know what you are doing! The
# following commands have a special meaning inside the header: $title,
# $datetime, $date, $doxygenversion, $projectname, $projectnumber,
# $projectbrief, $projectlogo. Doxygen will replace $title with the empty
# string, for the replacement values of the other commands the user is referred
# to HTML_HEADER.
# This tag requires that the tag GENERATE_LATEX is set to YES.
LATEX_HEADER =
# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
# generated LaTeX document. The footer should contain everything after the last
# chapter. If it is left blank doxygen will generate a standard footer. See
# LATEX_HEADER for more information on how to generate a default footer and what
# special commands can be used inside the footer.
#
# Note: Only use a user-defined footer if you know what you are doing!
# This tag requires that the tag GENERATE_LATEX is set to YES.
LATEX_FOOTER =
# The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
# LaTeX style sheets that are included after the standard style sheets created
# by doxygen. Using this option one can overrule certain style aspects. Doxygen
# will copy the style sheet files to the output directory.
# Note: The order of the extra style sheet files is of importance (e.g. the last
# style sheet in the list overrules the setting of the previous ones in the
# list).
# This tag requires that the tag GENERATE_LATEX is set to YES.
LATEX_EXTRA_STYLESHEET =
# The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
# other source files which should be copied to the LATEX_OUTPUT output
# directory. Note that the files will be copied as-is; there are no commands or
# markers available.
# This tag requires that the tag GENERATE_LATEX is set to YES.
LATEX_EXTRA_FILES =
# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
# prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
# contain links (just like the HTML output) instead of page references. This
# makes the output suitable for online browsing using a PDF viewer.
# The default value is: YES.
# This tag requires that the tag GENERATE_LATEX is set to YES.
PDF_HYPERLINKS = YES
# If the USE_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
# the PDF file directly from the LaTeX files. Set this option to YES, to get a
# higher quality PDF documentation.
# The default value is: YES.
# This tag requires that the tag GENERATE_LATEX is set to YES.
USE_PDFLATEX = YES
# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
# command to the generated LaTeX files. This will instruct LaTeX to keep running
# if errors occur, instead of asking the user for help. This option is also used
# when generating formulas in HTML.
# The default value is: NO.
# This tag requires that the tag GENERATE_LATEX is set to YES.
LATEX_BATCHMODE = NO
# If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
# index chapters (such as File Index, Compound Index, etc.) in the output.
# The default value is: NO.
# This tag requires that the tag GENERATE_LATEX is set to YES.
LATEX_HIDE_INDICES = NO
# If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
# code with syntax highlighting in the LaTeX output.
#
# Note that which sources are shown also depends on other settings such as
# SOURCE_BROWSER.
# The default value is: NO.
# This tag requires that the tag GENERATE_LATEX is set to YES.
LATEX_SOURCE_CODE = NO
# The LATEX_BIB_STYLE tag can be used to specify the style to use for the
# bibliography, e.g. plainnat, or ieeetr. See
# http://en.wikipedia.org/wiki/BibTeX and \cite for more info.
# The default value is: plain.
# This tag requires that the tag GENERATE_LATEX is set to YES.
LATEX_BIB_STYLE = plain
#---------------------------------------------------------------------------
# Configuration options related to the RTF output
#---------------------------------------------------------------------------
# If the GENERATE_RTF tag is set to YES, doxygen will generate RTF output. The
# RTF output is optimized for Word 97 and may not look too pretty with other RTF
# readers/editors.
# The default value is: NO.
GENERATE_RTF = NO
# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
# it.
# The default directory is: rtf.
# This tag requires that the tag GENERATE_RTF is set to YES.
RTF_OUTPUT = rtf
# If the COMPACT_RTF tag is set to YES, doxygen generates more compact RTF
# documents. This may be useful for small projects and may help to save some
# trees in general.
# The default value is: NO.
# This tag requires that the tag GENERATE_RTF is set to YES.
COMPACT_RTF = NO
# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
# contain hyperlink fields. The RTF file will contain links (just like the HTML
# output) instead of page references. This makes the output suitable for online
# browsing using Word or some other Word compatible readers that support those
# fields.
#
# Note: WordPad (write) and others do not support links.
# The default value is: NO.
# This tag requires that the tag GENERATE_RTF is set to YES.
RTF_HYPERLINKS = NO
# Load stylesheet definitions from file. Syntax is similar to doxygen's config
# file, i.e. a series of assignments. You only have to provide replacements,
# missing definitions are set to their default value.
#
# See also section "Doxygen usage" for information on how to generate the
# default style sheet that doxygen normally uses.
# This tag requires that the tag GENERATE_RTF is set to YES.
RTF_STYLESHEET_FILE =
# Set optional variables used in the generation of an RTF document. Syntax is
# similar to doxygen's config file. A template extensions file can be generated
# using doxygen -e rtf extensionFile.
# This tag requires that the tag GENERATE_RTF is set to YES.
RTF_EXTENSIONS_FILE =
# If the RTF_SOURCE_CODE tag is set to YES then doxygen will include source code
# with syntax highlighting in the RTF output.
#
# Note that which sources are shown also depends on other settings such as
# SOURCE_BROWSER.
# The default value is: NO.
# This tag requires that the tag GENERATE_RTF is set to YES.
RTF_SOURCE_CODE = NO
#---------------------------------------------------------------------------
# Configuration options related to the man page output
#---------------------------------------------------------------------------
# If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for
# classes and files.
# The default value is: NO.
GENERATE_MAN = NO
# The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
# it. A directory man3 will be created inside the directory specified by
# MAN_OUTPUT.
# The default directory is: man.
# This tag requires that the tag GENERATE_MAN is set to YES.
MAN_OUTPUT = man
# The MAN_EXTENSION tag determines the extension that is added to the generated
# man pages. In case the manual section does not start with a number, the number
# 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
# optional.
# The default value is: .3.
# This tag requires that the tag GENERATE_MAN is set to YES.
MAN_EXTENSION = .3
# The MAN_SUBDIR tag determines the name of the directory created within
# MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
# MAN_EXTENSION with the initial . removed.
# This tag requires that the tag GENERATE_MAN is set to YES.
MAN_SUBDIR =
# If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
# will generate one additional man file for each entity documented in the real
# man page(s). These additional files only source the real man page, but without
# them the man command would be unable to find the correct page.
# The default value is: NO.
# This tag requires that the tag GENERATE_MAN is set to YES.
MAN_LINKS = NO
#---------------------------------------------------------------------------
# Configuration options related to the XML output
#---------------------------------------------------------------------------
# If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that
# captures the structure of the code including all documentation.
# The default value is: NO.
GENERATE_XML = NO
# The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
# it.
# The default directory is: xml.
# This tag requires that the tag GENERATE_XML is set to YES.
XML_OUTPUT = xml
# If the XML_PROGRAMLISTING tag is set to YES, doxygen will dump the program
# listings (including syntax highlighting and cross-referencing information) to
# the XML output. Note that enabling this will significantly increase the size
# of the XML output.
# The default value is: YES.
# This tag requires that the tag GENERATE_XML is set to YES.
XML_PROGRAMLISTING = YES
#---------------------------------------------------------------------------
# Configuration options related to the DOCBOOK output
#---------------------------------------------------------------------------
# If the GENERATE_DOCBOOK tag is set to YES, doxygen will generate Docbook files
# that can be used to generate PDF.
# The default value is: NO.
GENERATE_DOCBOOK = NO
# The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
# If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
# front of it.
# The default directory is: docbook.
# This tag requires that the tag GENERATE_DOCBOOK is set to YES.
DOCBOOK_OUTPUT = docbook
# If the DOCBOOK_PROGRAMLISTING tag is set to YES, doxygen will include the
# program listings (including syntax highlighting and cross-referencing
# information) to the DOCBOOK output. Note that enabling this will significantly
# increase the size of the DOCBOOK output.
# The default value is: NO.
# This tag requires that the tag GENERATE_DOCBOOK is set to YES.
DOCBOOK_PROGRAMLISTING = NO
#---------------------------------------------------------------------------
# Configuration options for the AutoGen Definitions output
#---------------------------------------------------------------------------
# If the GENERATE_AUTOGEN_DEF tag is set to YES, doxygen will generate an
# AutoGen Definitions (see http://autogen.sf.net) file that captures the
# structure of the code including all documentation. Note that this feature is
# still experimental and incomplete at the moment.
# The default value is: NO.
GENERATE_AUTOGEN_DEF = NO
#---------------------------------------------------------------------------
# Configuration options related to the Perl module output
#---------------------------------------------------------------------------
# If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module
# file that captures the structure of the code including all documentation.
#
# Note that this feature is still experimental and incomplete at the moment.
# The default value is: NO.
GENERATE_PERLMOD = NO
# If the PERLMOD_LATEX tag is set to YES, doxygen will generate the necessary
# Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
# output from the Perl module output.
# The default value is: NO.
# This tag requires that the tag GENERATE_PERLMOD is set to YES.
PERLMOD_LATEX = NO
# If the PERLMOD_PRETTY tag is set to YES, the Perl module output will be nicely
# formatted so it can be parsed by a human reader. This is useful if you want to
# understand what is going on. On the other hand, if this tag is set to NO, the
# size of the Perl module output will be much smaller and Perl will parse it
# just the same.
# The default value is: YES.
# This tag requires that the tag GENERATE_PERLMOD is set to YES.
PERLMOD_PRETTY = YES
# The names of the make variables in the generated doxyrules.make file are
# prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
# so different doxyrules.make files included by the same Makefile don't
# overwrite each other's variables.
# This tag requires that the tag GENERATE_PERLMOD is set to YES.
PERLMOD_MAKEVAR_PREFIX =
#---------------------------------------------------------------------------
# Configuration options related to the preprocessor
#---------------------------------------------------------------------------
# If the ENABLE_PREPROCESSING tag is set to YES, doxygen will evaluate all
# C-preprocessor directives found in the sources and include files.
# The default value is: YES.
ENABLE_PREPROCESSING = YES
# If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names
# in the source code. If set to NO, only conditional compilation will be
# performed. Macro expansion can be done in a controlled way by setting
# EXPAND_ONLY_PREDEF to YES.
# The default value is: NO.
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
MACRO_EXPANSION = NO
# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
# the macro expansion is limited to the macros specified with the PREDEFINED and
# EXPAND_AS_DEFINED tags.
# The default value is: NO.
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
EXPAND_ONLY_PREDEF = NO
# If the SEARCH_INCLUDES tag is set to YES, the include files in the
# INCLUDE_PATH will be searched if a #include is found.
# The default value is: YES.
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
SEARCH_INCLUDES = YES
# The INCLUDE_PATH tag can be used to specify one or more directories that
# contain include files that are not input files but should be processed by the
# preprocessor.
# This tag requires that the tag SEARCH_INCLUDES is set to YES.
INCLUDE_PATH =
# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
# patterns (like *.h and *.hpp) to filter out the header-files in the
# directories. If left blank, the patterns specified with FILE_PATTERNS will be
# used.
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
INCLUDE_FILE_PATTERNS =
# The PREDEFINED tag can be used to specify one or more macro names that are
# defined before the preprocessor is started (similar to the -D option of e.g.
# gcc). The argument of the tag is a list of macros of the form: name or
# name=definition (no spaces). If the definition and the "=" are omitted, "=1"
# is assumed. To prevent a macro definition from being undefined via #undef or
# recursively expanded use the := operator instead of the = operator.
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
PREDEFINED = CONF_DEBUG \
EEZ_PSU_ARDUINO \
EEZ_PSU_SIMULATOR
# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
# tag can be used to specify a list of macro names that should be expanded. The
# macro definition that is found in the sources will be used. Use the PREDEFINED
# tag if you want to use a different macro definition that overrules the
# definition found in the source code.
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
EXPAND_AS_DEFINED =
# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
# remove all references to function-like macros that are alone on a line, have
# an all uppercase name, and do not end with a semicolon. Such function macros
# are typically used for boiler-plate code, and will confuse the parser if not
# removed.
# The default value is: YES.
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
SKIP_FUNCTION_MACROS = YES
#---------------------------------------------------------------------------
# Configuration options related to external references
#---------------------------------------------------------------------------
# The TAGFILES tag can be used to specify one or more tag files. For each tag
# file the location of the external documentation should be added. The format of
# a tag file without this location is as follows:
# TAGFILES = file1 file2 ...
# Adding location for the tag files is done as follows:
# TAGFILES = file1=loc1 "file2 = loc2" ...
# where loc1 and loc2 can be relative or absolute paths or URLs. See the
# section "Linking to external documentation" for more information about the use
# of tag files.
# Note: Each tag file must have a unique name (where the name does NOT include
# the path). If a tag file is not located in the directory in which doxygen is
# run, you must also specify the path to the tagfile here.
TAGFILES =
# When a file name is specified after GENERATE_TAGFILE, doxygen will create a
# tag file that is based on the input files it reads. See section "Linking to
# external documentation" for more information about the usage of tag files.
GENERATE_TAGFILE =
# If the ALLEXTERNALS tag is set to YES, all external class will be listed in
# the class index. If set to NO, only the inherited external classes will be
# listed.
# The default value is: NO.
ALLEXTERNALS = NO
# If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed
# in the modules index. If set to NO, only the current project's groups will be
# listed.
# The default value is: YES.
EXTERNAL_GROUPS = YES
# If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
# the related pages index. If set to NO, only the current project's pages will
# be listed.
# The default value is: YES.
EXTERNAL_PAGES = YES
# The PERL_PATH should be the absolute path and name of the perl script
# interpreter (i.e. the result of 'which perl').
# The default file (with absolute path) is: /usr/bin/perl.
PERL_PATH = /usr/bin/perl
#---------------------------------------------------------------------------
# Configuration options related to the dot tool
#---------------------------------------------------------------------------
# If the CLASS_DIAGRAMS tag is set to YES, doxygen will generate a class diagram
# (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
# NO turns the diagrams off. Note that this option also works with HAVE_DOT
# disabled, but it is recommended to install and use dot, since it yields more
# powerful graphs.
# The default value is: YES.
CLASS_DIAGRAMS = YES
# You can define message sequence charts within doxygen comments using the \msc
# command. Doxygen will then run the mscgen tool (see:
# http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
# documentation. The MSCGEN_PATH tag allows you to specify the directory where
# the mscgen tool resides. If left empty the tool is assumed to be found in the
# default search path.
MSCGEN_PATH =
# You can include diagrams made with dia in doxygen documentation. Doxygen will
# then run dia to produce the diagram and insert it in the documentation. The
# DIA_PATH tag allows you to specify the directory where the dia binary resides.
# If left empty dia is assumed to be found in the default search path.
DIA_PATH =
# If set to YES the inheritance and collaboration graphs will hide inheritance
# and usage relations if the target is undocumented or is not a class.
# The default value is: YES.
HIDE_UNDOC_RELATIONS = YES
# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
# available from the path. This tool is part of Graphviz (see:
# http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
# Bell Labs. The other options in this section have no effect if this option is
# set to NO
# The default value is: NO.
HAVE_DOT = YES
# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
# to run in parallel. When set to 0 doxygen will base this on the number of
# processors available in the system. You can set it explicitly to a value
# larger than 0 to get control over the balance between CPU load and processing
# speed.
# Minimum value: 0, maximum value: 32, default value: 0.
# This tag requires that the tag HAVE_DOT is set to YES.
DOT_NUM_THREADS = 0
# When you want a differently looking font in the dot files that doxygen
# generates you can specify the font name using DOT_FONTNAME. You need to make
# sure dot is able to find the font, which can be done by putting it in a
# standard location or by setting the DOTFONTPATH environment variable or by
# setting DOT_FONTPATH to the directory containing the font.
# The default value is: Helvetica.
# This tag requires that the tag HAVE_DOT is set to YES.
DOT_FONTNAME = Helvetica
# The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
# dot graphs.
# Minimum value: 4, maximum value: 24, default value: 10.
# This tag requires that the tag HAVE_DOT is set to YES.
DOT_FONTSIZE = 10
# By default doxygen will tell dot to use the default font as specified with
# DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
# the path where dot can find it using this tag.
# This tag requires that the tag HAVE_DOT is set to YES.
DOT_FONTPATH =
# If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
# each documented class showing the direct and indirect inheritance relations.
# Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.
# The default value is: YES.
# This tag requires that the tag HAVE_DOT is set to YES.
CLASS_GRAPH = YES
# If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
# graph for each documented class showing the direct and indirect implementation
# dependencies (inheritance, containment, and class references variables) of the
# class with other documented classes.
# The default value is: YES.
# This tag requires that the tag HAVE_DOT is set to YES.
COLLABORATION_GRAPH = YES
# If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
# groups, showing the direct groups dependencies.
# The default value is: YES.
# This tag requires that the tag HAVE_DOT is set to YES.
GROUP_GRAPHS = YES
# If the UML_LOOK tag is set to YES, doxygen will generate inheritance and
# collaboration diagrams in a style similar to the OMG's Unified Modeling
# Language.
# The default value is: NO.
# This tag requires that the tag HAVE_DOT is set to YES.
UML_LOOK = NO
# If the UML_LOOK tag is enabled, the fields and methods are shown inside the
# class node. If there are many fields or methods and many nodes the graph may
# become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
# number of items for each type to make the size more manageable. Set this to 0
# for no limit. Note that the threshold may be exceeded by 50% before the limit
# is enforced. So when you set the threshold to 10, up to 15 fields may appear,
# but if the number exceeds 15, the total amount of fields shown is limited to
# 10.
# Minimum value: 0, maximum value: 100, default value: 10.
# This tag requires that the tag HAVE_DOT is set to YES.
UML_LIMIT_NUM_FIELDS = 10
# If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
# collaboration graphs will show the relations between templates and their
# instances.
# The default value is: NO.
# This tag requires that the tag HAVE_DOT is set to YES.
TEMPLATE_RELATIONS = NO
# If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
# YES then doxygen will generate a graph for each documented file showing the
# direct and indirect include dependencies of the file with other documented
# files.
# The default value is: YES.
# This tag requires that the tag HAVE_DOT is set to YES.
INCLUDE_GRAPH = YES
# If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
# set to YES then doxygen will generate a graph for each documented file showing
# the direct and indirect include dependencies of the file with other documented
# files.
# The default value is: YES.
# This tag requires that the tag HAVE_DOT is set to YES.
INCLUDED_BY_GRAPH = YES
# If the CALL_GRAPH tag is set to YES then doxygen will generate a call
# dependency graph for every global function or class method.
#
# Note that enabling this option will significantly increase the time of a run.
# So in most cases it will be better to enable call graphs for selected
# functions only using the \callgraph command. Disabling a call graph can be
# accomplished by means of the command \hidecallgraph.
# The default value is: NO.
# This tag requires that the tag HAVE_DOT is set to YES.
CALL_GRAPH = YES
# If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
# dependency graph for every global function or class method.
#
# Note that enabling this option will significantly increase the time of a run.
# So in most cases it will be better to enable caller graphs for selected
# functions only using the \callergraph command. Disabling a caller graph can be
# accomplished by means of the command \hidecallergraph.
# The default value is: NO.
# This tag requires that the tag HAVE_DOT is set to YES.
CALLER_GRAPH = YES
# If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
# hierarchy of all classes instead of a textual one.
# The default value is: YES.
# This tag requires that the tag HAVE_DOT is set to YES.
GRAPHICAL_HIERARCHY = YES
# If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
# dependencies a directory has on other directories in a graphical way. The
# dependency relations are determined by the #include relations between the
# files in the directories.
# The default value is: YES.
# This tag requires that the tag HAVE_DOT is set to YES.
DIRECTORY_GRAPH = YES
# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
# generated by dot. For an explanation of the image formats see the section
# output formats in the documentation of the dot tool (Graphviz (see:
# http://www.graphviz.org/)).
# Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
# to make the SVG files visible in IE 9+ (other browsers do not have this
# requirement).
# Possible values are: png, jpg, gif, svg, png:gd, png:gd:gd, png:cairo,
# png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus and
# png:gdiplus:gdiplus.
# The default value is: png.
# This tag requires that the tag HAVE_DOT is set to YES.
DOT_IMAGE_FORMAT = png
# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
# enable generation of interactive SVG images that allow zooming and panning.
#
# Note that this requires a modern browser other than Internet Explorer. Tested
# and working are Firefox, Chrome, Safari, and Opera.
# Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
# the SVG files visible. Older versions of IE do not have SVG support.
# The default value is: NO.
# This tag requires that the tag HAVE_DOT is set to YES.
INTERACTIVE_SVG = NO
# The DOT_PATH tag can be used to specify the path where the dot tool can be
# found. If left blank, it is assumed the dot tool can be found in the path.
# This tag requires that the tag HAVE_DOT is set to YES.
DOT_PATH =
# The DOTFILE_DIRS tag can be used to specify one or more directories that
# contain dot files that are included in the documentation (see the \dotfile
# command).
# This tag requires that the tag HAVE_DOT is set to YES.
DOTFILE_DIRS =
# The MSCFILE_DIRS tag can be used to specify one or more directories that
# contain msc files that are included in the documentation (see the \mscfile
# command).
MSCFILE_DIRS =
# The DIAFILE_DIRS tag can be used to specify one or more directories that
# contain dia files that are included in the documentation (see the \diafile
# command).
DIAFILE_DIRS =
# When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the
# path where java can find the plantuml.jar file. If left blank, it is assumed
# PlantUML is not used or called during a preprocessing step. Doxygen will
# generate a warning when it encounters a \startuml command in this case and
# will not generate output for the diagram.
PLANTUML_JAR_PATH =
# When using plantuml, the specified paths are searched for files specified by
# the !include statement in a plantuml block.
PLANTUML_INCLUDE_PATH =
# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
# that will be shown in the graph. If the number of nodes in a graph becomes
# larger than this value, doxygen will truncate the graph, which is visualized
# by representing a node as a red box. Note that doxygen if the number of direct
# children of the root node in a graph is already larger than
# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
# the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
# Minimum value: 0, maximum value: 10000, default value: 50.
# This tag requires that the tag HAVE_DOT is set to YES.
DOT_GRAPH_MAX_NODES = 50
# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
# generated by dot. A depth value of 3 means that only nodes reachable from the
# root by following a path via at most 3 edges will be shown. Nodes that lay
# further from the root node will be omitted. Note that setting this option to 1
# or 2 may greatly reduce the computation time needed for large code bases. Also
# note that the size of a graph can be further restricted by
# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
# Minimum value: 0, maximum value: 1000, default value: 0.
# This tag requires that the tag HAVE_DOT is set to YES.
MAX_DOT_GRAPH_DEPTH = 0
# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
# background. This is disabled by default, because dot on Windows does not seem
# to support this out of the box.
#
# Warning: Depending on the platform used, enabling this option may lead to
# badly anti-aliased labels on the edges of a graph (i.e. they become hard to
# read).
# The default value is: NO.
# This tag requires that the tag HAVE_DOT is set to YES.
DOT_TRANSPARENT = NO
# Set the DOT_MULTI_TARGETS tag to YES to allow dot to generate multiple output
# files in one run (i.e. multiple -o and -T options on the command line). This
# makes dot run faster, but since only newer versions of dot (>1.8.10) support
# this, this feature is disabled by default.
# The default value is: NO.
# This tag requires that the tag HAVE_DOT is set to YES.
DOT_MULTI_TARGETS = NO
# If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
# explaining the meaning of the various boxes and arrows in the dot generated
# graphs.
# The default value is: YES.
# This tag requires that the tag HAVE_DOT is set to YES.
GENERATE_LEGEND = YES
# If the DOT_CLEANUP tag is set to YES, doxygen will remove the intermediate dot
# files that are used to generate the various graphs.
# The default value is: YES.
# This tag requires that the tag HAVE_DOT is set to YES.
DOT_CLEANUP = YES
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 1 - introduction.html
================================================
1. Introduction
This manual contains reference information for programming the open hardware/open source EEZ programmable PSU (Power Supply Unit) over the remote interface using the SCPI programming language.
The SCPI (Standard Commands for Programmable Instruments, often pronounced “skippy”) is an open standard freely available on the IVI Foundation web pages. The current version is SCPI 1999.0.
SCPI is a pure software standard, and can be used over many communication interfaces. SCPI communications are ASCII text, and therefore can be supported in programs written in almost any computer language, such as C, C++, etc.
The physical communications link is not defined by SCPI. It was originally created with the IEEE 488 (GPIB) environment in mind, but it can also be used with RS-232 (serial), Ethernet, USB, VXIbus, HiSLIP, etc. The EEZ PSU supports Serial (via USB) and Ethernet communication.
The application software that uses SCPI commands is called a Controller and that in a SCPI enabled device – such as the EEZ PSU – is called an Instrument.
Please note that IEEE 488 standard documents are not freely available, and when it's mentioned in this manual we do so only for reference purposes. Those who with to research the GPIB for better understanding or possible modification/improvement of the PSU remote control may wish to purchase standards documents from the IEEE.
1.1. About SCPI
The SCPI 1999.0 standard document says (Section 1.3) the goal of SCPI is to reduce Automatic Test Equipment (ATE) program development time. SCPI does this goal by providing a consistent programming environment for instrument control and data usage. This is achieved by use of defined program messages, instrument responses, and data formats across all SCPI instruments, regardless of manufacturer.
A consistent program environment uses the same commands and parameters to control instruments that have the same function.
SCPI programming consistency is both vertical and horizontal. Vertical programming consistency defines program messages within an instrument class. An example of vertical consistency is using the same command for reading DC voltage from different multimeters supporting SCPI. Horizontal consistency uses the same command to control similar functions across instrument classes. For example, the trigger command would be the same for trigger functions found in conforming counters, oscilloscopes, function generators, etc.
A key to consistent programming is the reduction of multiple ways to control similar instrument functions. The philosophy of SCPI is that the same instrument functions are to be controlled by the same SCPI commands. To simplify learning, SCPI uses industry-standard names, and terms that are manufacturer and customer supported.
SCPI is designed to be expanded with new defined commands in the future without causing programming problems. As new instruments are introduced, the intent is to maintain program compatibility with existing SCPI instruments.
Additional links:
Implementation links:
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 10 - Programming examples.html
================================================
10. Programming examples
10.1. Set channel output values and working with the OCP
This is a SCPI commands sequence that sets a voltage, current, and the over-current protection (OCP) on the channel two:
|
INST?
|
Check currently selected output
|
|
1
|
|
|
INST CH2
|
Select channel two as current channel
|
|
VOLT 10
|
Set output voltage
|
|
CURR
|
Set output current
|
|
CURR:PROT:STAT?
|
Check OCP status
|
|
0
|
|
|
CURR:PROT:STAT 1
|
Enable OCP
|
|
CURR:PROT:DEL 100ms
|
Set OCP delay
|
|
OUTP 1
|
Enable output
|
|
MEAS?
|
Measure output voltage
|
|
10.00
|
|
|
MEAS:CURR?
|
Measure output current
|
|
0.00
|
Current is zero since no load is connected
|
If software simulator is used, connection of the load can be also simulated:
|
SIMU:LOAD 20
|
Define connected load impedance
|
|
MEAS?
|
Measure voltage once again
|
|
10.00
|
|
|
MEAS:CURR?
|
Measure current once again
|
|
0.50
|
Measured current
|
The following command sequence could be used to test channel mode with load previously defined and after the load impedance is lowered enough that output current reach programmed value. The OCP has to be disabled because previously defined 100ms delay does not give us enough time to execute the whole sequence for testing channel mode and output voltage and current values:
|
OUTP:MODE?
|
Check mode of operation
|
|
"CV"
|
The channel is in constant-voltage mode since output current is below previously programmed level
|
|
SIMU:LOAD?
|
Check load value
|
|
10
|
|
|
CURR:PROT:STAT?
|
Check OCP status
|
|
1
|
|
|
CURR:PROT:STAT OFF
|
Disable OCP
|
|
SIMU:LOAD 4
|
Decrease load impedance
|
|
OUTP:MODE?
|
Check once again mode of operation
|
|
"CC"
|
Channel enters constant-current mode since Imax = U / R = 10 / 4 = 2.5A and current is limited to the 1A
|
|
MEAS:CURR?
|
Measure output current
|
|
1.00
|
|
|
MEAS?
|
Measure output voltage
|
|
4.00
|
Output voltage is decreased since U = I * R = 1 * 4 = 4V
|
The OCP will “trip” when output current reach programmed value and channel stay in the CC mode for more then programmed OCP delay time. To test that with e.g. the software simulator we’ll disable channel output first, enable OCP and when change channel output back to enabled state:
|
OUTP OFF
|
Disable channel output
|
|
CURR:PROT:TRIP?
|
Check OCP status
|
|
0
|
OCP is not activated
|
|
CURR:PROT:STAT ON
|
Enable OCP
|
|
VOLT?
|
Check programmed output voltage
|
|
10.00
|
|
|
CURR?
|
Check programmed output current
|
|
1.00
|
|
|
SIMU:LOAD?
|
Check simulated load value
|
|
4
|
|
|
OUTP ON
|
Enable channel output
|
|
CURR:PROT:TRIP?
|
Check OCP status once again
|
|
1
|
OCP has been tripped
|
|
OUTP?
|
Check channel output state
|
|
0
|
Channel output is changed to OFF stated by the OCP
|
The channel output state cannot be changed to enabled until any of protection is active. We have to clear protection first. If the same load that caused the first protection trip is still connected the channel output will be disabled immediately after the protection programmed delay time expired. Therefore we also have to disconnect load or disable protection. The later method will be used in the command sequence that follows:
|
OUTP ON
|
First attempt to enable channel output
|
|
OUTP?
|
|
|
0
|
This attempt failed, the channel output remain disabled
|
|
OUTP:PROT:CLE
|
Channel protections reset
|
|
OUTP ON
|
Second to enable channel output
|
|
0
|
Channel output was enabled for a short time (100ms) and returns back to OFF state
|
|
CURR:PROT:TRIP?
|
Check OCP status
|
|
1
|
OCP has been tripped
|
|
OUTP:PROT:CLE
|
Reset channel protections once again
|
|
CURR:PROT:STAT OFF
|
Disable OCP
|
|
OUTP ON
|
Third attempt to enable channel output
|
|
OUTP?
|
|
|
1
|
Output is finally enabled
|
|
OUTP:MODE?
|
|
|
"CC"
|
Channel enters CC mode of operation
|
10.2. Voltage and current calibration
For optimum calibration results the following condition are recommended:
- the calibration ambient temperature is stable and between 20 °C and 30 °C.
- ambient relative humidity is less than 80%.
- Allow a one hour warm-up period before verification or calibration (use e.g. SYST:CHAN:INFO:ONT:LAST? or SYST:CPU:INFO:ONT:LAST? to get that info).
- Use short and thick cables to connect test setups.
|
|
|
|
|
1
|
*RST
|
|
|
2
|
SYST:RWL
|
Make sure that PSU is in remote mode and cannot be unlock from local console (TFT display)
|
|
3
|
INST {CH1|CH2}; OUTP ON
|
Select the channel to be calibrated and enable the channel output.
|
|
4
|
VOLT:PROT:STAT OFF
CURR:PROT:STAT OFF
POW:PROT:STAT OFF
|
Disable if required the voltage, current and power protections.
|
|
5
|
CAL ON, "<password>"
|
PSU enters calibration mode on the channel selected in step 1. Both voltage and current on the selected channel are set to the MINimum value. The VOLT? and CURR? commands can be optionally used here to test channel output values.
|
|
6
|
|
For voltage calibration, connect a digital voltmeter (DVM) across the PSU’s output terminals.
|
|
7
|
CAL:VOLT:LEV MIN
|
Set the channel to the low-end (MIN) calibration point.
|
|
8
|
CAL:VOLT 81.8MV
|
Enter the reading you obtained from the external DVM.
|
|
9
|
CAL:VOLT:LEV MID
|
Set the channel to the middle (MID) calibration point.
|
|
10
|
CAL:VOLT 19.68
|
Enter the reading you obtained from the DVM.
|
|
11
|
CAL:VOLT:LEV MAX
|
Set the channel to the high (MAX) calibration point.
|
|
12
|
CAL:VOLT 39.2
|
Enter the reading you obtained from the DVM.
|
|
13
|
|
For current calibration, connect current monitoring resistor (shunt) across the output terminals and connect the DVM across the shunt resistor. Its resistance has to be less then 5 Ω and rated for 25 W or more for measuring MAX current level.
|
|
14
|
|
Repeat step 7 through step 12 by substituting CURR for VOLT for current calibration. For example, CAL:CURR:LEV MIN.
|
|
15
|
CAL_CURR:RANG LOW
|
Power board r5B12 only: for low current range (i.e. 0 – 500 mA) calibration use this command to change the range and repeat once again procedure mentioned in step 14.
|
|
16
|
CAL:REM "<string>"
|
Record calibration information such as next calibration due date for future reference. The calibration string may contain up to 40 characters. You don’t need to enter current date and time since that information will be recorded automatically.
|
|
17
|
CAL:SAVE
|
Save to non-volatile memory new calibration data.
|
|
18
|
CAL OFF, "<password>"
|
PSU exit calibration mode. Both voltage and current on the selected channel are again set to the MINimum value.
|
|
19
|
SYST:REM
|
Enable local console unlock. Alternatively SYST:LOC can be executed to make local console enabled again.
|
10.3. Working with profiles
The following command sequence could be used to store current set of parameters to the profile location 4 in the non-volatile memory:
|
MEM:STAT:VAL? 4
|
Check to see if profile selected location is empty
|
|
0
|
|
|
MEM:STAT:NAME? 4
|
We can also check that by querying profile location name
|
|
"--Not used--"
|
|
|
INST CH1
VOLT?;:CURR?;:OUTP?
|
Examine currently programmed output values of the first channel
|
|
0.00;0.00;0
|
|
|
INST CH2
VOLT?;:CURR?;:OUTP?
|
Examine currently programmed output values of the second channel
|
|
0.00;0.00;0
|
|
|
VOLT 12;:CURR 300mA
INST CH1
VOLT 12;:CURR 300mA
OUTP 1;:OUTP 1, CH2
|
Reprogram both channel output values that will be stored as a new profile
|
|
*SAV 4
|
All profile parameters is now storing on the selected location
|
|
MEM:STAT:NAME? 4
|
Check profile name
|
|
""
|
|
|
MEM:STAT:NAME 4, "Dual 12V/300mA, Output ON"
|
Set the profile name (only ASCII characters are allowed!)
|
|
MEM:STAT:NAME? 4
|
Check the profile name once again
|
|
"Dual 12V/300ma, Output ON"
|
|
We can now turn the PSU off (when it enters the Stand-by mode) turn it on again and check some of the programmed parameters:
|
SYST:POW 0
|
The PSU enters the Stand-by mode
|
|
SYST:POW 1
|
Returns back from the Stand-by mode. Please note that this command can be executed with the minimum of 5 seconds delay otherwise a -200,"Execution error" will be generated (you can check that with the SYST:ERR? command)
|
|
VOLT?;:CURR?;:OUTP?
|
Query programmed voltage, current and output state of the currently selected channel
|
|
0.00;0.00;0
|
Returned data indicate that previously saved values in profile number 4 were not used
|
|
*RCL 4
VOLT?;:CURR?;:OUTP?
|
Recall parameters from desired location and execute query once again
|
|
12.00;0.30;1
|
The channel output values are now programmed using the selected profile
|
We can automate above mentioned process that channel profile parameters stored in non-volatile memory are using on power up. First we’ll check what is a current status of automatic recall and what profile will be used in the case of automatic recall:
|
MEM:STAT:REC:AUTO?
|
Query status of automatic profile recall during power on sequence
|
|
0
|
Automatic recall is turned off
|
|
MEM:STAT:REC:AUTO ON
|
Turn on automatic recall
|
|
MEM:STAT:REC:SEL?
|
Query which profile will be used when automatic recall is turned on
|
|
0
|
Selected profile was 0
|
|
MEM:STAT:REC:SEL 4
|
Change power on profile to 4
|
|
SYST:POW 0
|
Switch the PSU to the Stand-by mode once again
|
|
SYST:POW 1
|
Returns back from the Stand-by mode. Again wait at least 5 seconds before enters this command
|
|
VOLT?;:CURR?;:OUTP?
|
Query programmed voltage, current and output state of the currently selected channel
|
|
12.00;0.30;1
|
The channel output values are programmed using the selected profile
|
10.4. Get identification info and self-test results
The PSU’s identification information could be beneficial when more then one instrument are controlled. Additionally in the following example information about self-test will be queried:
|
*IDN?
|
Query identification string
|
|
EEZ,1/50/03-1/40/05 (Due),00001,M1.0.93
|
PSU with two different channels is identified, the first channel is 0-50V/3A and the second is 0-40V/5A. Serial number is 00001, and firmware version M1.0.93
|
|
*TST?
|
Execute self-test and query result
|
|
0
|
Self-test is passed
|
|
DIAG:TEST?
|
Query additional information about self-test
|
|
"1, EEPROM, installed, passed","1, Ethernet, installed, passed","1, RTC, installed, passed","1, DateTime, installed, passed","2, BP option, installed, skipped","1, CH1 IOEXP, installed, passed","1, CH1 DAC, installed, passed","1, CH1 ADC, installed, passed","1, CH2 IOEXP, installed, passed","1, CH2 DAC, installed, passed","1, CH2 ADC, installed, passed"
|
|
The self-test could be performed even when the PSU is in the Stand-by mode. We’ll first switch the PSU into the Stand-by mode. At the end of this example we are using additional diagnostic command that allows us to query information about channel’s ADC measurements.
|
SYST:POW 0
|
The PSU enters the Stand-by mode
|
|
DIAG:TEST?
|
Query additional information about self-test
|
|
"1, EEPROM, installed, passed","1, Ethernet, installed, passed","1, RTC, installed, passed","1, DateTime, installed, passed","2, BP option, installed, skipped"
|
Only Arduino Shield +BP module diagnostic information is returned
|
|
SYST:POW 1
|
Returns back from the Stand-by mode
|
|
DIAG:ADC?
|
Additional information about currently selected channel ADC inputs
|
|
"U_SET=12.02 V","U_MON=12.00 V","I_SET=0.30 A","I_MON=0.00 A"
|
U_SET and I_SET are measured values of the DAC outputs, U_MON and I_MON are actual output values. I_MON is 0 because no load is connected. A small difference between set and actual output voltage exists because calibration data are currently in use.
|
10.5. Programming output voltage using the list of values
The PSU comes with simple “arbitary waveform generator” functionality that can be accomplished using the LIST commands. The following example changes in the loop output voltage between five output values each half a second long while current is set to 3 A.
|
INST CH1
|
Select the channel that has to be programmed
|
|
VOLT:MODE LIST
|
Set voltage programming mode to the list of values
|
|
LIST:VOLT 5, 10, 20, 40, 0
|
Define sequence of output voltage (could be up to 256 steps)
|
|
CURR:MODE LIST
|
Set current programming mode to the list of values.
|
|
LIST:CURR 3
|
Only one output current value is defined. Single value or number of values equivalent to other parameters (LIST:VOLT and LIST:DWEL) is allowed.
|
|
LIST:DWEL 0.5
|
Only one value for the duration of each step is chosen. Single value or number of values equivalent to other parameters (LIST:VOLT and LIST:CURR) is allowed.
|
|
LIST:COUN INF
|
Repeat continuously LIST sequence
|
|
TRIG:SOUR IMM
|
Define type of trigger. In this case the list execution will start immediately after INIT command is received.
|
|
INIT
|
Start the trigger.
|
Resulting output voltage and current waveform with connected load of 15 Ω is shown on the picture below.
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 12 - SCPI commands summary.html
================================================
SCPI commands summary
|
|
|
|
*CLS
|
Clears all status data structures
|
|
*ESE {<value>}
|
Programs the Standard Event Status Enable register bits
|
|
*ESR?
|
Reads the Standard Event Status Register
|
|
*IDN?
|
Returns the UNIQUE identification of the PSU
|
|
*OPC
|
Operation Complete Command used for program synchronization
|
|
*RCL {<profile>}
|
Recalls the PSU state stored in the specified storage location
|
|
*RST
|
Reset PSU to the initial state
|
|
*SAV {<profile>}
|
Stores the current PSU state in the specified storage location
|
|
*STB?
|
Reads the Status Byte register
|
|
*TRG
|
Generates a software trigger
|
|
*TST?
|
Returns Self-Test results
|
|
*WAI
|
Waits until all pending commands are completed
|
|
|
|
|
ABORt
|
Resets the trigger system to the Idle state
|
|
:DLOG
|
Stops the internal data logging session
|
|
CALibrate[:MODE] {<bool>, <password>}
|
Enables/disables calibration mode
|
|
:CLEar {<password>}
|
Clears all calibration parameters
|
|
:CURRent
|
|
|
[:DATA] {<new value>}
|
Enters the calibration value
|
|
:LEVel {<level>}
|
Calibrates the output current programming
|
|
:RANGe {<range>}
|
Sets current range for multiple current range model
|
|
:PASSword
|
|
|
:NEW {<old>, <new>}
|
Changes calibration password
|
|
:REMark {<string>}
|
Saves calibration information
|
|
:SAVE
|
Saves the new cal constants in non-volatile memory
|
|
:STATe {<bool>, <password>}
|
Enables calibration parameters
|
|
:VOLTage
|
|
|
[:DATA] {<new value>}
|
Enters the calibration value
|
|
:LEVel {<level>}
|
Calibrates the output voltage programming
|
|
DIAGnostic
|
|
|
[:INFOrmation]
|
|
|
:ADC?
|
Returns the latest values acquired by ADC
|
|
:CALibration?
|
Returns a list of the calibration parameters
|
|
:FAN?
|
Returns status of the cooling fan.
|
|
:PROTection?
|
Returns the information about all protections.
|
|
:TEST?
|
Returns results of the most recent self-test
|
|
DISPlay
|
|
|
:BRIGhtness {<value>}
|
Sets the intensity of the front panel TFT display
|
|
:MODE {<mode>}
|
Sets the main page appearance
|
|
[:WINdow]
|
|
|
[:STATe] {<bool>}
|
Sets the front panel TFT display state
|
|
:TEXT {<message>}
|
Displays a message on the front panel TFT display
|
|
:CLEar
|
Clear a message on the front panel TFT display
|
|
INITiate
|
|
|
[:IMMediate]
|
Completes one full trigger cycle
|
|
:DLOG {<filename>}
|
Enables internal data log session
|
|
:CONTinuous {<bool>}
|
Enables/disables continuous transient triggers
|
|
INSTrument
|
|
|
[:SELect] {<channel>}
|
Selects the output to be programmed
|
|
:COUPle
|
|
|
:TRACking {<type>}
|
Selects independent, parallel-tracking, or series-tracking mode
|
|
:DISPlay
|
|
|
:TRACe[<n>] {<value>}
|
Selects output value on the specified display trace
|
|
:SWAP
|
Swaps positions of selected output values
|
|
:YT
|
|
|
:RATE {<duration>}
|
Selects YT view sample duration
|
|
:NSELect {<channel>}
|
Selects the output to be programmed
|
|
MEASure
|
|
|
[:SCALar]
|
|
|
:CURRent
|
|
|
[:DC]? [<channel>]
|
Takes a measurement; returns the average current
|
|
:POWer
|
|
|
[:DC]? [<channel>]
|
Takes a measurement; returns the average power
|
|
:TEMPerature
|
|
|
[:DC]? {<sensor>}
|
Takes a measurement; returns the average temperature
|
|
[:VOLTage]
|
|
|
[:DC]? [<channel>]
|
Takes a measurement; returns the average voltage
|
|
MEMory
|
|
|
:NSTates?
|
Returns total number of state storage memory locations
|
|
:STATe
|
|
|
:CATalog?
|
Lists the names associated with all ten state storage locations
|
|
:DELete {<profile>}
|
Deletes the contents of a state storage location
|
|
:ALL
|
Deletes the contents of all state storage locations
|
|
:NAME {<profile>, <name>}
|
Assigns a custom name to a state storage locations
|
|
:RECall
|
|
|
:AUTO {<bool>}
|
Specifies whether the power-down state is recalled from location 0 on power-on
|
|
:SELect {<profile>}
|
Specifies which PSU state will be used at power on
|
|
:VALid? {<profile>}
|
Determines whether a storage location contains a valid state
|
|
MMEMory
|
|
|
:CATalog [<directory>]
|
Returns a list of items in the specified directory (folder)
|
|
:LENgth [<directory>]
|
Returns the number of items in the specified directory
|
|
:CDIRectory {<directory>}
|
Changes the current directory
|
|
:COPY {<source>}, {<destination>}
|
Copies <source> to <destination>
|
|
:DATE? {<filename>}
|
Returns date that the specified file was last saved
|
|
:DELete {<filename>}
|
Deletes an existing file
|
|
:DOWNload
|
|
|
:ABORt
|
Aborts current download session
|
|
:DATA :DATA {#<length>,<encoding>,<block>}
|
Downloads data from the host computer
|
|
:FNAMe {<filename>}
|
Creates or opens the specified filename for download data
|
|
:SIZE {<filesize>}
|
Sets information about file size used for progress bar
|
|
:LOAD
|
|
|
:LIST[<n>] {<filename>}
|
Loads stored LIST to the specified channel
|
|
:PROFile {<filename>}
|
Loads stored user profile
|
|
:STATe {<filename>}
|
Loads the instrument setup
|
|
:LOCK {<password>}
|
Sets write protection
|
|
:MDIRectory {<directory>}
|
Makes a new directory
|
|
:MOVE {<source>}, {<destination>}
|
Moves or renames <source> to <destination>
|
|
:RDIRectory {<directory>}
|
Removes the specified directory
|
|
:STORe
|
|
|
:LIST[<n>] {<filename>}
|
Saves specified channel LIST
|
|
:PROFile {<filename>}
|
Saves specified user profile
|
|
:STATe {<filename>}
|
Saves the instrument setup
|
|
:TIME? {<filename>}
|
Returns time that the specified file was last saved
|
|
:UNLock {<password>}
|
Clears write protection
|
|
:UPLoad? {<filename>}
|
Uploads data to the host computer
|
|
OUTPut
|
|
|
[:STATe] {<bool>}
|
Enables the specified output channel(s)
|
|
TRIGgered {<bool>} [, <channel>]
|
Controls channel output state with trigger
|
|
:MODE?
|
Returns the channel mode of operation
|
|
:PROTection
|
|
|
:CLEar
|
Resets latched protection
|
|
:COUPle {<bool>}
|
Enables channel coupling for protection faults
|
|
:TRACk[:STATe] {<bool>}
|
Enables channels to operate in the track mode
|
|
SIMUlator
|
|
|
:EXIT
|
Closes simulator
|
|
:GUI
|
Starts simulator’s GUI
|
|
:LOAD {<value>}
|
Sets value of the virtual load
|
|
:STATe {<bool>}
|
“Connects” virtual load to the channel output
|
|
:PIN1 {<bool>}
|
Sets value of the PIN1 input
|
|
:PWRGood {<bool>}
|
Sets the PWRGOOD signal state
|
|
:RPOL {<bool>}
|
Sets the RPOL signal state
|
|
:TEMP {<value>}
|
Sets the temperature sensor value
|
|
:VOLT:PROG:EXT {<voltage>}
|
Sets the output voltage when channel is in external programming mode
|
|
SENSe
|
|
|
:CURRent
|
|
|
[:DC]
|
|
|
RANGe[:UPPer] {<range>}
|
Selects a DC current measurement range
|
|
AUTO {<bool>}
|
Enables/disables seamless measurement auto ranging
|
|
:DLOG
|
|
|
:FUNCtion
|
|
|
:CURRent {<bool>}, {<channel>}
|
Enables/disables output current internal data logging
|
|
:POWer {<bool>}, {<channel>}
|
Enables/disables output power internal data logging
|
|
:VOLTage {<bool>}, {<channel>}
|
Enables/disables output voltage internal data logging
|
|
:PERiod {<time>}
|
Sets the sample period for internal data logging
|
|
:TIME {<time>}
|
Sets the sample duration for internal data logging
|
|
[SOURce[<n>]]
|
|
|
:CURRent
|
|
|
[:LEVel]
|
|
|
[:IMMediate][:AMPLitude] {<current>}
|
Sets the output current
|
|
:STEP[:INCRement] {<step>}
|
Sets the step of the current change
|
|
:TRIGgered [:AMPLitude] {<current>}
|
Sets the triggered output current
|
|
:LIMit
|
|
|
[:POSitive][:IMMediate][:AMPLitude] {<current>}
|
Sets the output current limit
|
|
:PROTection
|
|
|
:DELay
|
|
|
[:TIME] {<time>}
|
Sets the over-current protection (OCP) programming delay
|
|
:STATe {<bool>}
|
Enables/disables over-current protection on the selected channel
|
|
:TRIPped?
|
Returns status of over-current protection activation
|
|
:LIST
|
|
|
:COUNt
|
Sets the number of times that the list is executed
|
|
:CURRent[:LEVel]
|
Specifies the current setting for each list step
|
|
:DWELl
|
Specifies the dwell time for each list step
|
|
:VOLTage[:LEVel]
|
Specifies the voltage setting for each list step
|
|
:LRIPple {<bool>}
|
Sets low output ripple (noise) mode of operation
|
|
:AUTO {<bool>}
|
Sets automatic changing to the low output ripple (noise) mode of operation
|
|
:POWer
|
|
|
:LIMit {<power>}
|
Sets the output power limit
|
|
:PROTection[:LEVel]
|
Sets the over-power protection (OPP) level
|
|
:DELay
|
|
|
[:TIME] {<time>}
|
Sets the over-power protection programming delay
|
|
:STATe {<bool>}
|
Enables/disables over-power protection on the selected channel
|
|
:TRIPped?
|
Returns status of over-power protection activation
|
|
:VOLTage
|
|
|
[:LEVel]
|
|
|
[:IMMediate][:AMPLitude] {<voltage>}
|
Sets the output voltage
|
|
:STEP[:INCRement] {<step>}
|
Sets the step of the voltage change
|
|
:TRIGgered [:AMPLitude] {<voltage>}
|
Sets the triggered output voltage
|
|
:LIMit
|
|
|
[:POSitive][:IMMediate][:AMPLitude] {<voltage>}
|
Sets the output voltage limit
|
|
:PROGram[:SOURce] {<source>}
|
Sets voltage programming source
|
|
:PROTection[:LEVel]
|
Sets the over-voltage protection (OVP) level
|
|
:DELay
|
|
|
[:TIME] {<time>}
|
Sets the over-voltage protection (OVP) programming delay
|
|
:STATe {<bool>}
|
Enables/disables over-voltage protection on the selected channel
|
|
:TRIPped?
|
Returns status of over-voltage protection activation
|
|
:SENSe[:SOURce] {<source>}
|
Sets voltage sense inputs source
|
|
STATus
|
|
|
:OPERation
|
|
|
[:EVENt]?
|
Returns the value of the Operation Event register
|
|
:CONDition?
|
Returns the value of the Operation Instrument Condition register
|
|
:ENABle {<value>}
|
Enables specific bits in the Operation Event register
|
|
:INSTrument[<n>]
|
|
|
[:EVENt]?
|
Returns the value of the Operation Instrument Event register
|
|
:CONDition?
|
Returns the value of the Operation Instrument Condition register
|
|
:ENABle {<value>}
|
Enables specific bits in the Operation Instrument Event register
|
|
:ISUMmary<n>
|
|
|
[:EVENt]?
|
Returns the value of the Operation Instrument Isummary Event register
|
|
:CONDition?
|
Returns the value of the Operation Instrument Isummary Condition register
|
|
:ENABle {<value>}
|
Enables specific bits in the Operation Instrument Isummary Event register
|
|
:PREset
|
Presets all enable registers to power-on state
|
|
:QUEStionable
|
|
|
[:EVENt]?
|
Returns the value of the Questionable Event register
|
|
:CONDition?
|
Returns the value of the Questionable Condition register
|
|
:ENABle {<value>}
|
Enables specific bits in the Questionable Event register
|
|
:INSTrument[<n>]
|
|
|
[:EVENt]?
|
Returns the value of the Questionable Instrument Event register
|
|
:CONDition?
|
Returns the value of the Questionable Instrument Condition register
|
|
:ENABle {<value>}
|
Enables specific bits in the Questionable Instrument Event register
|
|
:ISUMmary<n>
|
|
|
[:EVENt]?
|
Returns the value of the Questionable Instrument Isummary Event register
|
|
:CONDition?
|
Returns the value of the Questionable Instrument Isummary Condition register
|
|
:ENABle {<value>}
|
Enables specific bits in the Questionable Instrument Isummary Event register
|
|
SYSTem
|
|
|
:BEEPer[:IMMediate]
|
Issues a single beep immediately
|
|
:STATe {<bool>}
|
Enables beeper function
|
|
:KEY
|
|
|
:STATe {<bool>}
|
Enables click tone for local control
|
|
:CAPability?
|
Returns an <instrument_specifier>
|
|
:CHANnel
|
|
|
[:COUNt]?
|
Returns the number of output channels
|
|
:INFOrmation
|
|
|
:AHOur
|
|
|
TOTal?
|
Returns channel’s total delivered energy in Ah
|
|
:CURRent?
|
Returns output current capability
|
|
:ONtime
|
|
|
LAST?
|
Returns time passed after last output enable
|
|
TOTal?
|
Returns channel’s total active time
|
|
:POWer?
|
Returns output power capability
|
|
:PROGram?
|
Returns programmable features of the channel
|
|
:VOLTage?
|
Returns output voltage capability
|
|
:WHOur
|
|
|
TOTal?
|
Returns channel’s total delivered energy in Wh
|
|
:MODel?
|
Returns the channel model identification
|
|
:COMMunicate
|
|
|
:ENABle {<bool>, <interface>}
|
Enables the remote interface
|
|
:ETHernet
|
|
|
:ADDRess {<ip_address>}
|
Sets the static LAN (IP) address
|
|
:DHCP {<bool>}
|
Enables the use of the Dynamic Host Configuration Protocol (DHCP)
|
|
:DNS <ip_address>
|
Sets the IP address of the DNS server.
|
|
:GATEway {<ip_address>}
|
Sets the IP address of the default gateway
|
|
:MAC?
|
Returns the MAC address
|
|
:PORT {<number>}
|
Sets the port number
|
|
:SMASk {<mask>}
|
Sets the static subnet mask
|
|
:NTP {<server>}
|
Set s NTP service server address
|
|
:RLSTate {<state>}
|
Places the instrument in remote or local mode
|
|
:SERial
|
|
|
:BAUD {<speed>}
|
Sets the baud rate (speed)
|
|
:PARity {<parity>}
|
Sets the parity mode
|
|
CPU
|
|
|
:INFOrmation
|
|
|
:ETHernet
|
|
|
:TYPE?
|
Returns the type of Ethernet controller
|
|
:ONtime
|
|
|
LAST?
|
Returns time passed after last power on
|
|
TOTal?
|
Returns PSU’s total active time
|
|
:TYPE?
|
Returns the type of CPU
|
|
:MODel?
|
Returns the control board model identification
|
|
:OPTion?
|
Returns information about installed options on the control board
|
|
:DATE {<yyyy>,<mm>,<dd>}
|
Sets the date of the system clock
|
|
:DIGital
|
|
|
:INPut:DATA? [<pin>]
|
Reads the state of the digital port pins
|
|
:OUTPut:DATA [<pin>] {<state>}
|
Sets the state of the digital port pins
|
|
:PIN<n>
|
|
|
:FUNCtion {<function>}
|
Sets the selected pin’s function
|
|
:POLarity {<polarity>}
|
Sets the selected pin’s polarity
|
|
:TOUTput
|
|
|
:BUS[:ENABle] {<Bool>}
|
Enables/disables BUS-generated triggers on digital pins
|
|
:ERRor
|
|
|
[:NEXT]?
|
Queries and clears errors from the error queue
|
|
:COUNt?
|
Queries the error/event queue for the number of unread items
|
|
:INHibit?
|
Queries system inhibit state
|
|
:KLOCk
|
Disables front panel [lock/unlock] icon
|
|
:LOCal
|
Places the PSU in the local mode
|
|
:PASSword
|
|
|
:CALibration
|
|
|
:RESet
|
Resets the calibration password to initial value
|
|
:FPANel
|
|
|
:RESet
|
Resets the front panel lock password to initial value
|
|
:NEW {<old>, <new>}
|
Changes system password
|
|
:POWer {<bool>}
|
Enters the PSU into the Stand-by mode
|
|
:PROTection:TRIP {<bool>}
|
Enters the PSU into the Stand-by mode in case of protection trip
|
|
:REMote
|
Places the PSU in the remote mode
|
|
:RWLock
|
Places the PSU in the remote mode and disables front panel [lock/unlock] icon
|
|
:TEMPerature
|
|
|
:PROTection
|
|
|
[:HIGH]
|
|
|
[:LEVel] {<temperature>[, <sensor>]}
|
Sets the OTP value
|
|
:CLEar [, {<sensor>}]
|
Clears the latched protection status of the over-temperature protection (OTP)
|
|
:DELay
|
Sets time-out period
|
|
[:TIME] {<delay>[, <sensor>]}
|
Sets the OTP programming delay
|
|
:STATe {<bool>[, <sensor>]}
|
Enables/disables OTP on the selected temperature sensor
|
|
:TRIPped? [<sensor>]
|
Returns status of OTP activation
|
|
:TIME {<hh>,<mm>,<ss>}
|
Sets the time of the system clock
|
|
:DTS {rules}
|
Defines daylight saving time (DST) rules
|
|
:ZONE {zone}
|
Defines time zone
|
|
:VERSion?
|
Returns the SCPI version number
|
|
TRIGger
|
|
|
[:SEQuence]
|
|
|
[:IMMediate]
|
|
|
:DELay {<delay>}
|
Sets the time delay between the detection of a trigger event and the start of any corresponding trigger action
|
|
:EXIT
|
|
|
:CONDition {<condition}
|
Sets channel’s condition when LIST execution stopped
|
|
:SOURce {<source>}
|
Sets the trigger source
|
|
:DLOG
|
|
|
[:IMMediate]
|
|
|
:SOURce {<source>}
|
Sets the internal data logger trigger source
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 2 - syntax and style.html
================================================
2. Syntax and style
Throughout this document, the following conventions are used for the SCPI command syntax:
- Square brackets ([]) indicate optional keywords or parameters. The braces are not sent with the command string.
- Braces ({}) enclose parameters within a command string.
- Triangle brackets (<>) indicate that you must substitute a value or a code for the enclosed parameter.
- A vertical bar (|) separates one of two or more alternative parameters.
2.1. Root Specifier
When it precedes the first header of a message unit, the colon becomes the root specifier. It tells the command parser that this is the root or the top node of the command tree.
2.2. Command termination
A command string sent to the PSU must terminate with a <new line>character. A <carriage return>
followed by a <new line>is also accepted. Command string termination will always reset the current SCPI command path to the root level.
2.3. Command separators
A colon (:) is used to separate a command keyword from a lower-level keyword as shown below:
SOURce1:CURRent:PROTection:STATe
A semicolon (;) is used to separate two commands within the same subsystem, and can also minimize typing. For example, sending the following command string,
SOURce1:VOLTage 20;CURRent 300mA
is the same as sending the following two commands:
SOURce1:VOLTage 20
SOURce1:CURRent 1.5
Use a colon and a semicolon to link commands from different subsystems. For example, in the following command string, an error is generated if you do not use the colon and semicolon:
SYSTem:BEEP;:SOURce1:CURRent 2.5
2.4. Querying parameter settings
You can query the value of most parameters by adding a question mark (?) to the command. For example, the following command sets the output voltage to 45.5V:
VOLTage 45.5
You can query the value by executing:
VOLTage?
If error is occurred use SYSTem:ERRor[:NEXT]? to get more information about error.
2.5. Using the MIN, MAX, and DEF Parameters
For many commands, you can substitute "MIN" or "MAX" in place of a parameter. In some cases you may also substitute "DEF". For example, consider the following command:
[SOURce[<n>]]:VOLTage[:LEVel][:IMMediate][:AMPLitude] {<voltage>|MIN|DEF|MAX|UP|DOWN}
Instead of selecting a specific value for the <voltage> parameter, you can substitute MIN to set the voltage to its minimum value, MAX to set the voltage to its maximum value, or DEF to set the voltage to its default value. For list of parameter values see Section 8.1
2.6. Command and message types
SCPI commands can be divided to common and subsystem commands.
- Common commands are defined by the IEEE 488.2 standard to perform common interface functions. They begin with an * and consist of three letters (command) or three letters and a ? (query). Description of supported common commands can be found in Section 4
- Subsystem commands are specific to instrument (PSU in this case) functions. They can be a single command or a group of commands. The groups are comprised of commands that extend one or more levels below the root. See Section 5 for commands that is created in accordance to the SCPI 1999.0 standard. Commands that is not defined by SCPI 1999.0 is labeled "unclassified" and are presented in Section 6
There are two types of SCPI messages, program and response.
- A program message consists of one or more properly formatted SCPI commands sent from the controller to the instrument. The message, which may be sent at any time, requests the instrument to perform some action.
- A response message consists of data in a specific SCPI format sent from the instrument to the controller. The instrument sends the message only in response to a query header.
2.7. Required Commands
The following commands are required in all SCPI instruments (see SCPI 1999.0 Section 4.2.1):
|
|
|
|
|
:SYSTem
|
|
|
|
:ERRor
|
21.8
|
|
|
[:NEXT]?
|
21.8.3e
|
1996
|
|
:VERSion?
|
19.16
|
1991
|
|
:STATus
|
18
|
5
|
|
:OPERation
|
|
|
|
[:EVENt]?
|
|
|
|
:CONDition?
|
|
|
|
:ENABle
|
|
|
|
:ENABle?
|
|
|
|
:QUEStionable
|
|
|
|
[:EVENt]?
|
|
|
|
:CONDition?
|
|
|
|
:ENABle
|
|
|
|
:ENABle?
|
|
|
|
:PRESet
|
|
|
2.7.1. Base functionality for the Power supply instrument class
|
|
|
|
OUTPut
|
|
|
[:STATe] <bool>
|
Enables the specified output channel(s)
|
|
[SOURce[<n>]]
|
|
|
CURRent
|
|
|
[:LEVel]
|
|
|
[:IMMediate][:AMPLitude] <current>
|
Sets the output current
|
|
VOLTage
|
|
|
[:LEVel]
|
|
|
[:IMMediate][:AMPLitude] <voltage>
|
Sets the output voltage
|
All SCPI power supplies shall implement the status reporting structure. STATus Subsystem defines the commands which shall be used to control the status reporting structure.
For a power supply, the bits of interest in the QUEStionable status structure are VOLTage and CURRent. When a power supply is operating as a voltage source, bit 1 (CURRent) shall be set. When a power supply is operating as a current source, bit 0 (VOLTage) shall be set. When the output is unregulated, both bits shall be set (for example, while the output is changing to a new programmed value).
2.8. Multiple Commands in a Message
Multiple SCPI commands can be combined and sent as a single message with one message terminator. There are two important considerations when sending several commands within a single message:
- Use a semicolon to separate commands within a message.
- There is an implied header path that affects how commands are interpreted by the PSU.
The header path can be thought of as a string that gets inserted before each command within a message. For the first command in a message, the header path is a null string. For each subsequent command the header path is defined as the characters that make up the headers of the previous command in the message up to and including the last colon separator. An example of a message with two commands is:
OUTPut:STATe ON,CH1;PROTection:CLEar CH1
which shows the use of the semicolon separating the two commands, and also illustrates the header path concept. Note that with the second command, the leading header OUTPut was omitted because after the OUTPut:STATe ON command, the header path became defined as OUTPut and thus the instrument interpreted the second command as:
OUTPut:PROTection:CLEar CH1
In fact, it would have been syntactically incorrect to include the OUTPut explicitly in the second command, since the result after combining it with the header path would be:
OUTPut:OUTPut:PROTection:CLEar CH1
which is incorrect.
You can combine common commands (IEEE488) with subsystem commands in the same message. Treat the common command as a message unit by separating it with a semicolon (the message unit separator). Common commands do not affect the header path; you may insert them anywhere in the message.
*TST?;SYSTem:ERRor?
2.9. Moving Among Subsystems
In order to combine commands from different subsystems, you need to be able to reset the header path to a null string within a message. You do this by beginning the command with a colon (:), which discards any previous header path. For example, you could clear the output protection and check the status of the Operation Condition register in one message by using a root specifier as follows:
OUTPut:PROTection:CLEar CH1;:STATus:OPERation:CONDition?
The following message shows how to combine commands from different subsystems as well as within the same subsystem:
SOURce1:VOLTage:LEVel 7.5;:VOLTage:PROTection:DELay 10;:CURRent:LEVel 0.5
Note the use of the optional header LEVel to maintain the correct path within the subsystems, and the use of the root specifier to move between subsystems.
2.10. SCPI parameter types
The SCPI language defines several different data formats to be used in program messages and response messages:
|
Numeric
|
Commands that require numeric parameters will accept all commonly used representations of numbers like integer (also known as NR1 format specified in ANSI X3.42-1990) or decimal representations of numbers including optional signs, decimal points (NR2 format), and scientific notation (i.e. 10E3 or NR3 format). Special values for numeric parameters like MINimum, MAXimum, and DEFault are also accepted. You can also send engineering unit suffixes (V, A, or SEC) with numeric parameters. If only specific numeric values are accepted, the PSU will automatically round the input numeric parameters. The following command uses a numeric parameter:
VOLT:STEP {<step>}
|
|
Discrete
|
Used to program settings that have a limited number of values such as BUS and IMM or CH1 and CH2. Query responses will always return the short form in all uppercase letters. The following command uses discrete parameters:
CAL:CURR:LEV {MIN|MID|MAX}
|
|
Boolean
|
Represent a single binary condition that is either true or false. For a false condition, the PSU will accept OFF or 0. For a true condition, the PSU will accept ON or any nonzero value (i.e. 1 but also 2.34 or -3). When you query a Boolean setting, the PSU will always return 0 or 1. The following command uses a Boolean parameter:
OUTP {OFF|ON}
|
|
String
|
Can contain virtually any set of ASCII characters. A string must begin and end with matching quotes, either with a single quote or with a double quote. You can include the quote delimiter as part of the string by typing it twice without any characters in between. The following command uses a string parameter:
CAL:REM <quoted string>
|
|
Data block
|
#<length-digits><length><block>
|
|
<length-digits>
|
NR1
|
<length> number of digits (e.g. 2 for two digit number)
|
|
<length>
|
NR1
|
Limited only with available space on SD card
|
|
<block>
|
Discrete
|
Only exact size is allowed as defined with <length>
|
|
Downloads text Hello world and store into the file "test file" in the current directory. Digit 2 denotes two digits of data length (11).
MMEM:DOWN:FNAM "test file"
MMEM:DOWN:DATA #211Hello world
MMEM:DOWN:FNAM ""
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 3 - registers and queue.html
================================================
3. Registers and queues
SCPI requires the status mechanism described in Section 11 of IEEE 488.2, including full implementation of the status register structure. Summary of implemented registers structure for the PSU is shown on Fig. 1. (commands used to access registers are written in parentheses).
All SCPI instruments have to implement status registers in the same way. The status system records various instrument conditions in the following register groups:
- the Status Byte register,
- the Standard Event register,
- the QUEStionable Status register group, and
- the OPERation Status register group.
The Status Byte register records high-level summary information reported in the other register groups.
Message interchanging between Controller and Instrument is accomplished by using input buffer and Output queue and Error queue. The length of the Input buffer is 48 characters. Both Output and Error queue can handle up to 20 messages.
Fig. 1: Summary of status structure registers
3.1. Standard Event Status Register
An status register group is consist of Condition, Event and Enable registers (see Fig. 1):
- The Condition register is a read-only register, which holds the live (unlatched) operational status of the instrument. Reading the Condition register does not clear it.
- The Event register is a read-only that reports defined conditions within the PSU. Bits in an event register are latched. Once an event bit is set, subsequent state changes are ignored. Bits in the Event register are automatically cleared by a query of that register (such as *ESR? or STATus:QUEStionable:EVENt?) or by sending the *CLS (clear status) command. A reset (*RST) or device clear will not clear bits in event registers (See Section 8.2). Querying an event register returns a decimal value which corresponds to the binary-weighted sum of all bits set in the register.
- The ENABle register is used to define which bits of the Event Status register will latch ESB (bit 5) of the Status byte register.
An error status (bit 2, 3, 4 or 5) records one or more errors in the PSU error queue. The SYSTem:ERRor? command can be used to read the error queue.
Implementation of the Standard Event Status register follows IEEE 488.2 Section 11.5.1.1:
|
|
|
|
|
0
|
1
|
Operation Complete (OPC) – This event bit is generated in response to the *OPC command. It indicates that the PSU has completed all selected pending operations (including *OPC).
|
|
1
|
2
|
Not used
|
|
2
|
4
|
Query ERROR (QYE) – Query Errors are detected by the Output Queue Control. This event bit indicates that either
- An attempt is being made to read data from the Output Queue when no output is either present or pending, or
- Data in the Output Queue has been lost.
Events that generate Query Errors do not generate Execution Errors, Command Errors, or Device-Specific Errors.
|
|
3
|
8
|
Device-Specific ERROR (DDE) – This event bit indicates that an error has occurred that is neither a Command Error, a Query Error, nor an Execution Error. A Device-Specific Error is any executed device operation that did not properly complete due to some condition, such as over-range, a self-test or calibration error.
Following a Device-Specific Error, the PSU will continue to process the input stream.
Events that generate Device-Specific Errors do not generate Command Errors, Query Errors, or Execution Errors.
|
|
4
|
16
|
Execution ERROR (ERR) – This event bit indicates that:
- A <PROGRAM DATA> element following a header was evaluated by the PSU as outside of its legal input range or is otherwise inconsistent with the PSU’s capabilities.
- A valid program message could not be properly executed due to some PSU condition.
Following an Execution Error, the PSU will continue parsing the input stream. Execution Errors will be reported by the PSU after rounding and expression evaluation operations have taken place. Rounding a numeric data element, for example, will not be reported as an Execution Error.
Events that generate Execution Errors do not generate Command Errors, Query Errors, or Device-Specific Errors.
|
|
5
|
32
|
Command ERROR (CME) – Command Errors are detected by the parser. This event bit indicates that one of the following events has occurred:
- An IEEE 488.2 syntax error has been detected by the parser. That is, a controller-to-device message was received that is in violation of this standard. Possible violations include a data element that violates the device listening formats or whose type is unacceptable to the device (see also IEEE 488.2 Section 7.1.2.2).
- A semantic error has occurred indicating that an unrecognized header was received. Unrecognized headers include incorrect device-specific headers and incorrect or unimplemented common commands described in Section 4
When the PSU detects a Command Error, parser synchronization may be lost.
When a Command Error is detected, any prior parsable elements of the same <PROGRAM MESSAGE> will be executed. That is also true for all parsable elements that follows after detected Command Error.
The Command Error bit not be set to report any other device-specific condition. Events that are reported as Command Errors cannot be reported as Execution Errors, Query Errors, or Device-Specific Errors.
|
|
6
|
64
|
User Request (URQ) – This event bit indicates that the PSU input device (TFT Touch screen) has been for any reason activated. The setting of this event-bit occur regardless of the IEEE 488.1 Remote/Local state of the device (not implemented yet)
|
|
7
|
128
|
Power On (PON) – This event bit indicates that an off-to-on transition has occurred in the device’s power supply. See also SYSTem:POWer.
|
|
8 – 15
|
–
|
Not used, always zero
|
3.2. Status Byte Register
The Status Byte summary register reports conditions from the other status registers (see Fig. 1). Query data that is waiting in the PSU’s output buffer is immediately reported through the "Message Available" (MAV) bit (bit 4) of the Status Byte register. Bits in the summary register are NOT latched. Clearing an event register will clear the corresponding bits in the Status Byte summary register. Reading all messages in the output buffer, including any pending queries, will clear the message available bit (MAV).
The Status Byte summary register is cleared when the *CLS (clear status) command has been executed.
The Status Byte enable register (request service) is cleared when the *SRE 0 command has been executed.
Querying the Standard Event register (*ESR? command) will clear only bit 5 (ESR) in the Status Byte summary register. For example, 24 (8 + 16) is returned when you have queried the status of the Status Byte register, QUES and MAV conditions have occurred.
|
|
|
|
|
0 – 1
|
–
|
Not used, always zero
|
|
2
|
4
|
ERR – Error queue bit indicates that one or more errors have been stored in the Error queue.
|
|
3
|
8
|
QUES – One or more bits are set in the QUEStionable Status register (bits must be enabled in the enable register).
|
|
4
|
16
|
MAV – The Message Available bit indicates whether or not the Output Queue is empty. Whenever the device is ready to accept a request by the controller to output data bytes, the MAV is TRUE. The MAV is FALSE when the Output Queue is empty.
This bit is used to synchronize information exchange with the controller. The controller can, for example, send a query command to the device and then wait for MAV to become TRUE.
|
|
5
|
32
|
ESB – One or more bits are set in the Standard Event register (bits must be enabled in the enable register, see *ESE command).
|
|
6
|
64
|
MMS – Master Status summary bit indicates that one or more bits are set in the Status Byte Register (bits must be enabled, see *SRE command). Also used to indicate a request for service (RQS).
|
|
7
|
128
|
OPER – One or more bits are set in the OPERation Status register.
|
3.3. OPERation Status Register
The OPERation status register contains conditions which are part of the instrument’s normal operation.
Each channel of the PSU is considered as separate "instrument". The two logical outputs (channels) of the PSU include an INSTrument summary status register and an individual instrument ISUMmary register for each logical output.
The bit definition of OPERation Status register shown on Fig.1.:
|
|
|
|
|
0 – 7
|
–
|
Not used, always zero
|
|
8
|
256
|
COUPle PARAllel indicate that PSU’s channels are connected in parallel.
|
|
9
|
512
|
COUPle SERial indicate that PSU’s channels are connected in serial.
|
|
10
|
1024
|
Internal data logging is in progress.
|
|
11 – 12
|
–
|
Not used, always zero
|
|
13
|
8192
|
INSTrument Summary Bit – One of n multiple logical instruments is reporting OPERational status.
|
|
14 – 15
|
–
|
Not used, always zero
|
The Event Status Enable register is cleared when the STAT:EVEN:ENAB 0 command is executed. The *CLS command can be also used to clear the register.
Fig. 2: OPERation Status registers summary
3.3.1. Operation INSTrument Status register
The bit definition of OPERation INSTrument Status register shown on Fig.2.:
|
|
|
|
|
0
|
–
|
Not used, always zero
|
|
1
|
2
|
INST1 – Instrument1 summary bit indicate that one or more bits are changed in the Channel 1 OPERation INSTrument Summary register
|
|
2
|
4
|
INST2 – Instrument2 summary bit indicate that one or more bits are changed in the Channel 2 OPERation INSTrument Summary register
|
|
3 – 15
|
–
|
Not used, always zero
|
3.3.2. Operation Instrument SUMmary status register
The ISUMmary registers report to the INSTrument register, which in turn reports to bit 13 of the Operation Status register. This is illustrated on Fig. 2. Using such a status register configuration allows a status event to be cross- referenced by output channel and type of event. The INSTrument register indicates which channel(s) have generated an event. The ISUMmary register represent a pseudo-operation Status register for a particular logical output.
The bit definition of OPERation INSTrument ISUMmary Status register shown on Fig.2.:
|
|
|
|
|
0
|
1
|
CALibrating – Channel is performing calibration
|
|
1 – 3
|
–
|
Not used, always zero
|
|
4
|
16
|
MEASuring – Channel is performing measurement (not implemented yet)
|
|
5
|
32
|
Waiting for TRIGger – Channel is waiting for the trigger event
|
|
6 – 7
|
–
|
Not used, always zero
|
|
8
|
256
|
CV – Channel is entered CV operation mode
|
|
9
|
512
|
CC – Channel is entered CC operation mode
|
|
10
|
1024
|
OE – Output is switched off
|
|
11
|
2048
|
DP – Down-programmer is switched off
|
|
12
|
4096
|
RSENSE – Remote voltage sense is switched on
|
|
13
|
8192
|
RPROG – Remote voltage programming is switched on
|
|
14 – 15
|
–
|
Not used, always zero
|
3.4. QUEStionable Status Register
The Questionable Status register provides information about unexpected operations of the PSU. Each channel of the PSU is considered as separate "instrument". The two logical outputs (channels) of the PSU include an INSTrument summary status register and an individual instrument ISUMmary register for each logical output.
The ISUMmary registers report to the INSTrument register, which in turn reports to bit 13 of the Questionable Status register. This is illustrated on Fig. 3. Using such a status register configuration allows a status event to be cross-referenced by output channel and type of event. The INSTrument register indicates which channel(s) have generated an event. The ISUMmary register represent a pseudo-Questionable Status register for a particular logical output.
Fig. 3: QUEStionable INSTrument registers summary
For example, if one of the two channels is in constant voltage (CV) mode and due to an overload looses regulation, bit 13 is set (latched). To read the register, the command STATus:QUEStionable? is required. To make use of bit 13 (ISUM), enable register must be correctly set. The command STAT:QUES:INST:ENAB 6 (2 + 4) has to be send to enable the Questionable instrument register, followed by the command STAT:QUES:INST:ISUM<n>:ENAB 19 for each channel to enable the QUEStionable INSTrument SUMmary register, where n is 1 or 2.
Bit definition for QUEStionable Status register shown on Fig.1.:
|
|
|
|
|
0 – 2
|
–
|
Not used, always zero
|
|
3
|
8
|
TIME – indicate abnormal time/date situation due to RTC failure or conflict between current and time/date retrieved from the stored configuration.
|
|
4
|
16
|
TEMPerature – temperature measurement that use the AUX temperature sensor on the Arduino Shield board require attention (i.e. over-temperature condition is detected, sensor is not functional, etc.).
Do not confuse this sensor with that are connected to a PSU channels.
|
|
5 – 11
|
–
|
Not used, always zero
|
|
12
|
4096
|
FAN – cooling fan failure is detected
|
|
13
|
8192
|
INSTrument summary, is described later in this chapter in association with multiple logical instruments.
|
|
14 – 15
|
–
|
Not used, always zero
|
The Questionable Status Enable register is cleared when the STAT:QUES:ENAB 0 command is executed. The *CLS command can be also used to clear the register.
3.4.1. Questionable INSTrument Status register
Bit definition for QUEStionable INSTrument register:
|
|
|
|
|
0
|
–
|
Not used, always zero
|
|
1
|
2
|
INST1 – Instrument1 summary bit indicate that one or more bits are changed in the Channel 1 OPERation INSTrument Summary register.
|
|
2
|
4
|
INST2 – Instrument2 summary bit indicate that one or more bits are changed in the Channel 2 OPERation INSTrument Summary register.
|
|
3 – 15
|
–
|
Not used, always zero
|
3.4.2. Questionable Instrument SUMmary status register
There are two questionable instrument summary registers, one for each PSU output. These registers provide information about voltage and current regulation.
Bit definition for QUEStionable INSTrument SUMmary register:
|
|
|
|
|
0
|
1
|
VOLTage – This bit is set when the voltage becomes unregulated, therefore a channel enters CC operation mode.
If the over-voltage protection (OVP) is activated (see VOLTage:PROTection:STATe) channel output will be switched off.
|
|
1
|
2
|
CURRent – This bit is set when the current becomes unregulated, therefore a channel enters CV operation mode.
If the over-current protection (OCP) is activated (see CURRent:PROTection:STATe) channel output will be switched off.
|
|
2 – 3
|
–
|
Not used, always zero
|
|
4
|
16
|
TEMPerature – the temperature sensor on the channel power board require attention (i.e. over-temperature condition is detected, sensor is not functional, etc.).
Do not confuse this sensor with one that is connected to the Arduino shield board.
|
|
5 – 6
|
–
|
Not used, always zero
|
|
7
|
128
|
RPOL – Remote sense reverse polarity is detected.
|
|
8
|
256
|
OVP – Over-voltage protection is activated. The query VOLT:PROT:TRIP? returns value of this bit. See also STAT:QUES.
|
|
9
|
512
|
OCP – Over-current protection is activated. The query CURR:PROT:TRIP? returns value of this bit. See also STAT:QUES.
|
|
10
|
1024
|
OPP – Over-power protection is activated. The query POW:PROT:TRIP? returns value of this bit. See also STAT:QUES.
|
|
11 – 15
|
–
|
Not used, always zero
|
Please note here that CURRent bit is use for questionable Voltage operating mode and vice versa.
If 0 and 1 bits is true that indicate neither the voltage nor the current is regulated (so-called unregulated or UR mode), and both bits false indicate the PSU channel are off.
To read the register for each PSU channel, the command STAT:QUES:INST:ISUM[<n>]? has to be send, where [<n>] is 1 or 2. If [<n>] is not specified the currently selected channel is used.
Use STAT:QUES:INST:ISUM<n>:COND? to determine operating mode (CV or CC) for the PSU channel (where n is 1 or 2 depending on the output).
The Questionable Status event register is cleared with:
- the *CLS (clear status) command or
- the event register is queried using the STAT:QUES? (status questionable event register) command.
3.5. Error queue
The error queue contains items that include a numerical and textual description of the error or event.
The <Error/event_number> is a unique integer in the range [-32 768, 32 767]. All positive numbers are instrument-dependent. All negative numbers are reserved by the SCPI standard with certain standard error/event codes. The value, zero, is also reserved to indicate that no error or event has occurred.
The second parameter of the full response is a quoted string containing an <Error/event_description>. Each <Error/event_number> has a unique and fixed <Error/event_description> associated with it. An example:
-113,"Undefined header"
The maximum string length of <Error/event_description> plus <Device-dependent_info> is 255 characters. List of all error/event messages can be found in Section 7 of this document.
As errors and events are detected, they are placed in a queue. This queue is first in, first out. If the queue overflows, the last error/event in the queue is replaced with error:
-350,"Queue overflow"
Any time the queue overflows, the least recent errors/events remain in the queue, and the most recent error/event is discarded. Reading an error/event from the head of the queue removes that error/event from the queue, and opens a position at the tail of the queue for a new error/event, if one is subsequently detected.
If the error queue is not empty, bit 2 of the Instrument Summary Status Register is set. A query returns only the oldest error code and associated error description information from the error queue. To return all error codes and associated description information, use repetitive queries until an error value of zero is returned, or until bit 2 of the status register is 0.
The error queue is cleared when any of the following occur (IEEE 488.2, section 11.4.3.4):
- Upon power up
- Upon receipt of a *CLS command
- Upon reading the last error message from the queue
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 4 - common comand reference.html
================================================
4. Common command reference
This section summarizes the mandatory subset of IEEE 488.2 commands required for any SCPI compliant instrument.
|
|
|
|
*CLS
|
Clears all status data structures
|
|
*ESE {<value>}
|
Programs the Standard Event Status Enable register bits
|
|
*ESR?
|
Reads the Standard Event Status Register
|
|
*IDN?
|
Returns the UNIQUE identification of the PSU
|
|
*OPC
|
Operation Complete Command used for program synchronization
|
|
*RCL {<profile>}
|
Recalls the PSU state stored in the specified storage location
|
|
*RST
|
Reset PSU to the initial state
|
|
*SAV {<profile>}
|
Stores the current PSU state in the specified storage location
|
|
*SRE
|
Enables bits in the Status Byte enable register.
|
|
*STB?
|
Reads the Status Byte register
|
|
*TRG
|
Generates a software trigger
|
|
*TST?
|
Returns Self-Test results
|
|
*WAI
|
Waits until all pending commands are completed
|
4.1. *CLS
|
Syntax
|
*CLS
|
|
Description
|
Clear Status Command. This command clears all status data structures in the PSU:
- Standard Event Status Register
- OPERation Event Status Register
- QUEStionable Event Status Register
- Error/Event Queue
The corresponding condition and enable registers are unaffected. If *CLS immediately follows a program message terminator (<NL>), then the output queue and the MAV bit are also cleared.
|
|
Return
|
None
|
|
Related Commands
|
*ESR?
STATus:OPERation[:EVENt]
STATus:OPERation:INSTrument[:EVENt]
STATus:OPERation:INSTrument:ISUMmary[<n>][:EVENt]
STATus:QUEStionable[:EVENt]
STATus:QUEStionable:INSTrument[:EVENt]
STATus:QUEStionable:INSTrument:ISUMmary[<n>][:EVENt]
SYSTem:ERRor
|
4.2. *ESE
|
Syntax
|
*ESE {<value>}
*ESE?
|
|
Description
|
Standard Event Status Enable Command. This command sets the Standard Event Status Enable register bits in the PSU. Those settings determine which events of the Standard Event Status Event register (see *ESR?) are allowed to set the ESB (Event Summary Bit) of the Status Byte register. A 1 in the bit position enables the corresponding event. All of the enabled events of the Standard Event Status Event Register are logically ORed sets the Event Summary Bit (ESB) of the Status Byte Register.
A STATus:PRESet command does not clear the bits in the Status Byte register.
See also Section 3.1 in this document.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
|
<value>
|
NR1
|
0 – 255 (A decimal value which corresponds to the binary-weighted sum of the bits in the register. See also table in Section 3.1).
|
–
|
|
Return
|
The query reads the enable register and returns a decimal value which corresponds to the binary-weighted sum of all bits set in the register.
|
|
Usage example
|
To enable bit 2 (decimal value = 4), bit 3 (decimal value = 8), and bit 7 (decimal value = 128), the corresponding decimal value would be 140 (4 + 8 + 128):
*ESE 140
Read value of the Standard Event Status Enable register:
*ESE?
140
|
|
Errors
|
-200,"Execution error"
|
|
Related Commands
|
*CLS
*ESR
*RST
STATus:PRESet
|
4.3. *ESR?
|
Syntax
|
*ESR?
|
|
Description
|
Standard Event Status Register (see Section 3.2) Query. Reading the Standard Event Status Event register clears it.
|
|
Return
|
The PSU returns a decimal value which corresponds to the binary-weighted sum of all bits in the register.
|
|
Usage example
|
If ERRor (bit 2) is set:
ESR?
4
|
4.4. *IDN?
|
Syntax
|
*IDN?
|
|
Description
|
Identification query for the UNIQUE identification of the PSU. (see also IEEE 488.2 10.14).
|
|
Return
|
The following system parameters will be displayed: <vendor>, <model>, <serial number>, <firmware>. The <model> include information about the CPU in use in brackets and could be Due or Simulator. More information about the simulator can be found in Section 9.
|
|
Usage example
|
*IDN?
Envox,EEZ H24005 (Due),CS17001,v1.1
|
4.5. *OPC
|
Syntax
|
*OPC
*OPC?
|
|
Description
|
Operation Complete Command. The command is mainly used for program synchronization. It causes the PSU to set the OPC bit (bit 0) of the Standard Event Status register when the PSU has completed all pending operations *OPC. Pending operations are complete when:
- All commands sent before *OPC is received, including paralleled commands, have been completed. Most commands are sequential and are completed before the next command is executed. Commands that affect output voltage, current, or state, relays, and trigger actions are executed in parallel with subsequent commands. *OPC provides notification that all parallel commands have completed.
- All triggered actions are completed.
Query whether the current operation is completed and the query returns 1.
See also IEEE 488.2 Section 12.5 – 12.8.
|
|
Return
|
Query causes the PSU to place a 1 in the output buffer when all pending operations are completed. *OPC? does not suspend processing of commands.
|
|
Usage example
|
*OPC?
1
if current operation is not completed:
*OPC?
0
|
4.6. *RCL
|
Syntax
|
*RCL {<profile>}
|
|
Description
|
This command recalls the PSU state stored in the specified storage location. The PSU has ten storage locations in non-volatile memory to store PSU states.
It is not possible to recall the PSU state from a storage location that is empty or was deleted (Error 400 will be generated). When the firmware is started for the first time, storage locations 1 through 9 are empty (location 0 has the power-on state).
The PSU uses location 0 to automatically save the state of the PSU at power down.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
|
<profile>
|
NR1
|
0 – 9
|
–
|
|
Return
|
None
|
|
Usage example
|
*RCL 2
|
|
Errors
|
400,"Cannot load empty profile"
|
|
Related Commands
|
*SAV
MEMory:STATe:DELete
MEMory:STATe:RECall:AUTO
MEMory:STATe:RECall:SELect
SYSTem:POWer
|
4.7. *RST
|
Syntax
|
*RST
|
|
Description
|
Reset Command. Restores the PSU to its initial state (as predefined in the PSU firmware, see Section 8.2) and clears the error queue. The reset command does NOT affect calibration data, nor any of saved configuration profiles (0 to 9).
When *RST is issued, all outputs are set to OFF, and voltage and current are programmed to 0. The power up sequence is started. All SPI peripherals are reinitialize except the controller if an active Ethernet connection exists.
|
|
Return
|
None
|
|
Usage example
|
*RST
MEMory:RECall:AUTO
SYSTem:POWer
|
|
Related Commands
|
*RST
*SAV
MEMory:STATe:CATalog?
|
4.8. *SAV
|
Syntax
|
*SAV {<profile>}
|
|
Description
|
This command stores the current instrument state in the specified storage location. Any state previously stored in the same location is overwritten without generating any errors. The PSU has nine storage locations in non-volatile memory which are available to the user for storing PSU states. The following channel and system parameters are stored in the non-volatile memory:
Users can assign an arbitrary name to each of locations 1 through 9 using the MEMory:STATe:NAME command.
A reset (*RST command) does not affect the configurations stored in memory. Once a state is stored, it remains constant until it is overwritten using this command or specifically deleted using the MEMory:STATe:DELete command.
The PSU uses location 0 to automatically hold the state of the PSU at power down.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<profile>
|
NR1
|
1 – 9
|
–
|
|
Return
|
None
|
|
Usage example
|
*SAV 2
|
|
Related Commands
|
*RCL
*RST
MEMory:STATe:CATalog?
MEMory:STATe:NAME
MEMory:STATe:DELete
|
4.9. *SRE
|
Syntax
|
*SRE {<value>}
*SRE?
|
|
Description
|
Enable bits in the Status Byte enable register (see Section 3.2).
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
|
<value>
|
NR1
|
0 – 255 (A decimal value which corresponds to the binary-weighted sum of the bits in the register. See also table in Section 3.1).
|
–
|
|
Return
|
Query the Status Byte enable register. The PSU returns a decimal value which corresponds to the binary-weighted sum of all bits set in the enable register.
|
|
Usage example
|
*SRE 32
|
|
Related Commands
|
*STB
|
4.10. *STB?
|
Syntax
|
*STB?
|
|
Description
|
Read Status Byte Query. This query reads the Status Byte register (see Section 3.2), which contains the status summary bits and the Output Queue MAV bit. The Status Byte is a read-only register and its bits are not cleared when it is read.
A serial poll also returns the value of the Status Byte register, except that bit 6 returns Request for Service (RQS) instead of Master Status Summary (MSS). A serial poll clears RQS, but not MSS. When the MSS bit is set, the PSU has one or more reasons for requesting service.
|
|
Return
|
The PSU returns a decimal value which corresponds to the binary-weighted sum of all bits in the register.
|
|
Usage example
|
If OPER (bit 7) is set:
*STB?
128
|
|
Related Commands
|
*SRE
|
4.11. *TRG
|
Syntax
|
*TRG
|
|
Description
|
This command generates a trigger to the trigger subsystem which has selected a bus
(software) trigger as its source (TRIGger[:SEQuence]:SOURce BUS).
|
|
Return
|
None
|
|
Usage example
|
Generate a trigger operation after 5 seconds:
TRIG:SOUR BUS
TRIG:DEL 5
INIT
*TRG
|
|
Errors
|
-211, "Trigger ignored"
304,"Incompatible transient modes"
307,"List lengths are not equivalent"
|
|
Related Commands
|
*WAI
ABORt
INITiate
TRIGger[:SEQuence]:DELay
TRIGger[:SEQuence]:SOURce
|
4.12. *TST?
|
Syntax
|
*TST?
|
|
Description
|
Self-Test Query. The self-test query causes an internal self-test, and places a response into the Output Queue indicating whether or not the PSU completed the self-test without detected errors.
Note: All all terminal connections must be removed while the internal self-test is being performed.
If an active Ethernet connection exists, testing of the Ethernet controller will be skipped. You can use DIAGnostic[:INFOrmation]:TEST? for to produce a detailed report of the latest self-test.
If a fan is installed, and not running, this command will start it for the short time to obtain speed information.
|
|
Return
|
0 or 1 depends of the self-test results. See also DIAGnostic[:INFOrmation]:TEST?.
|
|
Usage example
|
If all tests passed:
*TST?
0
If one or more tests failed:
*TST?
1
|
|
Related Commands
|
DIAGnostic[:INFOrmation]:TEST?
SYSTem:BEEP:STATe
|
4.13. *WAI
|
Syntax
|
*WAI
|
|
Description
|
Not implemented yet
The Wait-to-Continue Command causes the PSU to wait until all pending commands are completed before executing any other commands.
Pending operations are as defined under the *OPC command.
|
|
Return
|
None
|
|
Usage example
|
For example, the *WAI command can be used to make a voltage measurement after an OUTPut ON command has completed:
OUTPut ON;*WAI;:MEASure:VOLTage?
|
|
Related Commands
|
*OPC
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.1 - ABORt.html
================================================
5.1. ABORT
Abort commands cancel any triggered actions.
|
|
|
|
ABORt
|
Resets the trigger system to the Idle state
|
|
:DLOG
|
Stops the internal data logging session
|
5.1.1. ABORt
|
Syntax
|
ABORt
|
|
Description
|
The ABORt command resets the trigger system and places all trigger sequences in the IDLE state. Any actions related to the trigger system that are in progress will be also aborted as quickly as possible. As a result, subsequent triggers have no effect on the input level.
ABORt is also executed at power-on and upon execution of the *RST command.
|
|
Usage example
|
ABOR
|
|
Related Commands
|
*RST
INITiate
[SOURce[<n>]]:CURRent:TRIGgered
[SOURce[<n>]]:VOLTage:TRIGgered
[SOURce[<n>]]:LIST:COUNt
|
5.1.2. ABORt:DLOG
|
Syntax
|
ABORt:DLOG
|
|
Description
|
This command stops the internal data logging session.
ABORt:DLOG is also executed at power-on and upon execution of the *RST command.
|
|
Usage example
|
ABOR:DLOG
|
|
Related Commands
|
*RST
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.10 - MMEMory.html
================================================
5.10. MMEMory
The MMEMory commands are used to store, read or delete file in the PSU’s SD card. It can also query SD card information. In addition it is used for storing and recalling values used by [SOURce[<n>]]:LIST subsystem. File and directory (folder) names cannot contain the following characters:\ / : * ? " < > |
5.10.1. MMEMory:CATalog
|
Syntax
|
MMEMory:CATalog? [<directory>]
|
|
Description
|
Returns the list of files and directories (folders) names, types and sizes in the current or specified directory. Number of items (files/directories) corresponds to the value returned by the MMEMory:CATalog:LENgth? command.
To read out the information in the root directory (folder), specify "\" (backslash) or "/". If <directory> is not set, this function is applied to the current directory. If directory=<path>, this function is applied to <current directory>\<path>.
Error occurs if the specified directory does not exist.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<directory>
|
Quoted string
|
Directory name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Return
|
Returns all files in the directory as list of comma delimited quoted strings of <filename>, <filetype> and <filesize>. The following file types are supported:
- BIN – binary data
- CSV – textual data (comma separated)
- FOLD – directory (folder)
- LIST – LIST program data
- LOG – trace (display) or logged data (file extension .log)
- PROF – user profile data (file extension .profile)
- STAT – instrument (setting) state or user profiles (file extension .conf)
|
|
Usage example
|
MMEM:CAT?
"USER,FOLD,0","SCPI.PDF,BIN,1274844","SCH5B13A.PDF,BIN,296589",
"Documents,FOLD,0","Lists,FOLD,0","Videos,FOLD,0",
"profile0.profile,PROF,264"
MMEM:CAT? "USER"
"LST_2_3.CSV,BIN,88","FERY2.PDF,BIN,2443"
|
|
Errors
|
-250,"Mass storage error"
-251,"Missing mass storage"
-252,"Missing media"
-256,"File name not found"
|
|
Related Commands
|
MMEMory:CATalog:LENgth?
MMEMory:INFOrmation?
MMEMory:DATE?
MMEMory:TIME?
|
5.10.2. MMEMory:CATalog:LENgth
|
Syntax
|
MMEMory:CATalog:LENgth? [<directory>]
|
|
Description
|
This command returns the number of items in the current or specified directory (folder). The result corresponds to the number of files returned by the MMEMory:CATalog? command.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<directory>
|
Quoted string
|
Directory name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Return
|
The query command returns number (NR1) of items (files and directories).
|
|
Usage example
|
MMEM:CAT:LEN? "USER"
2
|
|
Errors
|
-256,"File name not found"
|
|
Related Commands
|
MMEMory:CATalog?
|
5.10.3. MMEMory:CDIRectory
|
Syntax
|
MMEMory:CDIRectory {<directory>}
MMEMory:CDIRectory?
|
|
Description
|
Changes the current directory to the specified directory (folder). This directory must exist otherwise an error will be generated.
At *RST, this value is set to the root path.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<directory>
|
Quoted string
|
Directory name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Return
|
This query returns the full path of the current directory.
|
|
Usage example
|
MMEM:CDIR "TEST/Test folder2"
MMEM:CDIR?
"TEST/Test folder2"
|
|
Errors
|
-256,"File name not found"
|
|
Related Commands
|
*RST
MMEMory:CATalog?
MMEMory:MDIRectory
MMEMory:RDIRectory
|
5.10.4. MMEMory:COPY
|
Syntax
|
MMEMory:COPY {<source>}, {<destination>}
|
|
Description
|
Makes a copy of an existing file in the current directory. The file names must include any file extension.
If <destination> is a file name, the copy file is created in the current directory. When <destination> is a <path> (e.g. “test lists/test022”) the source file is duplicated in <current directory>/<path>.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<source>
|
Quoted string
|
Source file name, 1 to 255 characters
|
–
|
|
<destination>
|
Quoted string
|
Copy file name or directory name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Usage example
|
MMEM:COPY "test.bin", "new2/test_new.bin"
|
|
Errors
|
-253,"Corrupt media"
-254,"Media full"
-256,"File name not found"
-258,"Media protected"
|
|
Related Commands
|
MMEMory:CATalog?
MMEMory:CDIRectory
MMEMory:LOCK
MMEMory:MDIRectory
MMEMory:MOVE
|
5.10.5. MMEMory:DATE
|
Syntax
|
MMEMory:DATE? {<filename>}
|
|
Description
|
Returns the (year, month, day) that the specified file was last saved.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<filename>
|
Quoted string
|
File name or directory name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Return
|
Comma-separated numbers (NR1) of year, month, day formated as yyyy, mm, dd
|
|
Usage example
|
MMEM:DATE? "test.002"
2017, 10, 1
|
|
Errors
|
-256,"File name not found"
|
|
Related Commands
|
MMEMory:TIME
|
5.10.6. MMEMory:DELete
|
Syntax
|
MMEMory:DELete {<filename>}
|
|
Description
|
Use this command to delete a file in the current directory. If SD card is locked using the MMEMory:LOCK command, an error -258 will be generated.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<filename>
|
Quoted string
|
File name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Usage example
|
MMEM:DEL "test.002"
|
|
Errors
|
-256,"File name not found"
-258,"Media protected"
|
|
Related Commands
|
MMEMory:CATalog?
MMEMory:CDIRectory
MMEMory:RDIRectory
MMEMory:LOCK
|
5.10.7. MMEMory:DOWNload:ABORt
|
Syntax
|
MMEMory:DOWNload:ABORt
|
|
Description
|
Use this command to abort currenlty running file transfer from the host initiated with the MMEMory:DOWNload:DATA command. If not active file transfer exists, the PSU will ignore this command without generating any error.
|
|
Usage example
|
MMEM:ABOR
|
|
Related Commands
|
MMEMory:DOWNload:DATA
|
5.10.8. MMEMory:DOWNload:DATA
|
Syntax
|
MMEMory:DOWNload:DATA {<block>}
|
|
Description
|
Downloads data from the host computer to a file in the SD card. This is a multiple steps process:
- The filename must have been previously specified by MMEMory:DOWNload:FNAMe.
- The data can be transferred in single or more blocks. Receiving of first block will erase all previously stored, and each consecutive block will be appended to the end
- Download is finished when MMEMory:DOWNload:FNAMe with empty name was sent
Use MMEMory:INFOrmation? command first to check available space.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<block>
|
Data block
|
–
|
–
|
|
Usage example
|
Downloads text Hello world and store into the file "test file" in the current directory. Digit 2 denotes two digits of data length (11).
MMEM:DOWN:FNAM "test file"
MMEM:DOWN:DATA #211Hello world
MMEM:DOWN:FNAM ""
|
|
Errors
|
-253,"Corrupt media"
-254,"Media full"
-258,"Media protected"
|
|
Related Commands
|
MMEMory:DOWNload:FNAMe
MMEMory:INFOrmation?
MMEMory:LOCK
|
5.10.9. MMEMory:DOWNload:FNAMe
|
Syntax
|
MMEMory:DOWNload:FNAMe {<filename>}
|
|
Description
|
Creates or opens the specified filename prior to writing data to that file with MMEMory:DOWNload:DATA.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<filename>
|
Quoted string
|
File name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Usage example
|
MMEMory:DOWNload:FNAMe "new_list.bin"
|
|
Errors
|
-258,"Media protected"
|
|
Related Commands
|
MMEMory:DOWNload:DATA
|
5.10.10. MMEMory:DOWNload:SIZE
|
Syntax
|
MMEMory:DOWNload:SIZE {<filesize>}
|
|
Description
|
This command define filesize used by progress bar displayed on the local console during the file transfer. If filesize is not provided, progress bar will not be displayed.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<filesize>
|
NR1
|
0 to 2.147.483.648 (2 GiB) as limited by SD Card FAT
|
0
|
|
Usage example
|
MMEMory:DOWNload:SIZE 124000
|
|
Related Commands
|
MMEMory:DOWNload:DATA
MMEMory:DOWNload:FNAMe
|
5.10.11. MMEMory:INFOrmation
|
Syntax
|
MMEMory:INFOrmation?
|
|
Description
|
Use this command to find out total amount of storage currently used and storage available on the SD card. The sum of that two amounts represents SD card capacity in bytes.
|
|
Return
|
The command returns used space and free space as two comma separated integers.
|
|
Usage example
|
MMEM:INFO?
3932160,7732461568
|
|
Related Commands
|
MMEMory:DOWNload:DATA
|
5.10.12. MMEMory:LOAD:LIST
|
Syntax
|
MMEMory:LOAD:LIST<n> {<filename>}
|
|
Description
|
Load stored LIST program from SD card location defined by <filename> to the channel defined with <n>.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<filename>
|
Quoted string
|
File name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Usage example
|
MMEM:LOAD:LIST1 "DC_DC conv testing.list"
MMEM:LOAD:LIST2 "DC_DC conv testing.list"
TRIG:SOUR BUS
INIT
*TRG
|
|
Errors
|
-200,"Execution error"
-256,"File name not found"
|
|
Related Commands
|
MMEMory:STORe:LIST[<n>]
[SOURce[<n>]]:LIST:COUNt
[SOURce[<n>]]:LIST:CURRent[:LEVel]
[SOURce[<n>]]:LIST:DWELl
[SOURce[<n>]]:LIST:VOLTage[:LEVel]
|
5.10.13. MMEMory:LOAD:PROFile
|
Syntax
|
MMEMory:LOAD:PROFile {<filename>}
|
|
Description
|
This command loads data from user profile file to the user profile 0.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<filename>
|
Quoted string
|
File name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Usage example
|
MMEM:LOAD:PROF "old settings.profile"
|
|
Errors
|
-256,"File name not found"
|
|
Related Commands
|
*RCL
*SAV
MEMory:STATe:RECall:AUTO
MMEMory:STORe:PROFile
|
5.10.14. MMEMory:LOCK
|
Syntax
|
MMEMory:LOCK {<password>}
MMEMory:LOCK?
|
|
Description
|
Use this command to enable write protection of SD card. All writing, deleting or modifying attempts on files or directories will generate an error if SD card is locked.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<password>
|
Quoted string
|
System password (4 to 16 characters)
|
–
|
|
Return
|
This query returns 0 if SD card is unlocked, or 1 if SD card is locked.
|
|
Usage example
|
MMEM:LOCK "test123"
MMEM:LOCK?
1
|
|
Errors
|
122,"Invalid sys password"
|
|
Related Commands
|
MMEMory:UNLock
SYSTem:PASSword:NEW
|
5.10.15. MMEMory:MDIRectory
|
Syntax
|
MMEMory:MDIRectory {<directory>}
|
|
Description
|
This command creates a new directory. If directory=<path>, this command creates a <current directory>/<path> directory.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<directory>
|
Quoted string
|
Directory name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Usage example
|
MMEM:MDIR "test folder"
|
|
Errors
|
-258,"Media protected"
|
|
Related Commands
|
MMEMory:CDIRectory
MMEMory:RDIRectory
|
5.10.16. MMEMory:MOVE
|
Syntax
|
MMEMory:MOVE {<source>}, {<destination>}
|
|
Description
|
This command moves or renames an existing file. If destination is a file name, the source file is renamed to the new file name in the current directory. When destination=<path>, the source file is moved to <current directory>/<path>.
Error occurs if the source file does not exist or the destination file already exists.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<source>
|
Quoted string
|
Source file name, 1 to 255 characters
|
–
|
|
<destination>
|
Quoted string
|
New file name or directory name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Usage example
|
Rename file:
MMEM:MOVE "old name","new name"
Move file from current directory to “/Test” directory:
MMEM:MOVE "new name","/Test/new name"
Move and rename file:
MMEM:MOVE "/Test/new name","/Documents/new doc"
|
|
Errors
|
-256,"File name not found"
-258,"Media protected"
|
|
Related Commands
|
MMEMory:CDIRectory
MMEMory:COPY
|
5.10.17. MMEMory:RDIRectory
|
Syntax
|
MMEMory:RDIRectory {<directory>}
|
|
Description
|
Removes the specified empty directory.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<directory>
|
Quoted string
|
Directory name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Usage example
|
MMEM:CDIR?
"Test folder2"
MMEM:CAT:LEN?
0
MMEM:RDIR "Test folder2"
|
|
Errors
|
-250,"Mass storage error"
-258,"Media protected"
|
|
Related Commands
|
MMEMory:CATalog?
MMEMory:CDIRectory
MMEMory:MDIRectory
|
5.10.18. MMEMory:STORe:LIST
|
Syntax
|
MMEMory:STORe:LIST<n> {<filename>}
|
|
Description
|
Store LIST program of channel defined with <n> to SD card location defined by <filename>. Stored file type will be TRAC. Default file extension is .list
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<filename>
|
Quoted string
|
File name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Usage example
|
MMEM:STOR:LIST1 "DC_DC conv testing.list"
|
|
Errors
|
-258,"Media protected"
|
|
Related Commands
|
MMEMory:LOAD:STATe
[SOURce[<n>]]:LIST:COUNt
[SOURce[<n>]]:LIST:CURRent[:LEVel]
[SOURce[<n>]]:LIST:DWELl
[SOURce[<n>]]:LIST:VOLTage[:LEVel]
|
5.10.19. MMEMory:STORe:PROFile
|
Syntax
|
MMEMory:STORe:PROFile {<filename>}
|
|
Description
|
This command stores the PSU state (i.e. user profile 0) to SD card location defined by <filename>. Stored file type will be STAT. Default file extension is .conf
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<filename>
|
Quoted string
|
File name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Usage example
|
MMEM:STOR:PROF "Both channels 5V_3A.profile"
|
|
Errors
|
-258,"Media protected"
|
|
Related Commands
|
*RCL
*SAV
MEMory:STATe:RECall:AUTO
MMEMory:LOAD:PROFile
|
5.10.20. MMEMory:TIME
|
Syntax
|
MMEMory:TIME? {<filename>}
|
|
Description
|
Returns the (hours, minute, seconds) that the specified file was last saved.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<filename>
|
Quoted string
|
File name or directory name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Return
|
Comma-separated numbers (NR1) of hours, minute, seconds formatted as hh, mm, ss
|
|
Usage example
|
MMEM:TIME? "test.002"
22, 10, 14
|
|
Errors
|
-256,"File name not found"
|
|
Related Commands
|
MMEMory:DATE
|
5.10.21. MMEMory:UNLock
|
Syntax
|
MMEMory:UNLock {<password>}
|
|
Description
|
Disable write protection of SD card activated by the MMEMory:LOCK command.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<password>
|
Quoted string
|
System password (4 to 16 characters)
|
–
|
|
Usage example
|
MMEM:LOCK?
1
MMEM:UNL "test123"
MMEM:LOCK?
0
|
|
Errors
|
122,"Invalid sys password"
|
|
Related Commands
|
MMEMory:LOCK
SYSTem:PASSword:NEW
|
5.10.22. MMEMory:UPLoad
|
Syntax
|
MMEMory:UPLoad? {<filename>}
|
|
Description
|
This command uploads the contents of a file from the instrument to the host computer.
The format for <file> is "[<path>]<file_name>", where <path> must be an absolute folder path. If <path> is omitted, the folder specified by the MMEMory:CDIRectory command is used. Absolute paths begin with a "\" or "/" and start at the root folder of SD card.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<filename>
|
Quoted string
|
File name or directory name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Return
|
The query returns the file contents are returned as an IEEE 488.2 definite-length block.
|
|
Usage example
|
MMEM:UPL? "test file"
#211Hello world
|
|
Errors
|
-257,"File name error"
|
|
Related Commands
|
MMEMory:DOWNload:DATA
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.11 - OUTPut.html
================================================
5.11. OUTPut
The OUTPut subsystem controls the output state, coupling outputs and protections, protection clear and tracking state.
5.11.1. OUTPut[:STATe]
|
Syntax
|
OUTPut[:STATe] {<bool>} [, <channel>]
OUTPut[:STATe]? [<channel>]
|
|
Description
|
This command enables or disables the specified output channel(s). The enabled state is ON (1); the disabled state is OFF (0). The state of a disabled output is a condition of zero output voltage and zero source current.
Execution of this command also affects bit 10 (OE) and bit 11 (DP) of the Operation Instrument Isummary register (see Section 3.3.2).
Self-test operation initiated by *TST? command will put all PSU channels into disable state.
When the BP_OPTION is enabled and the channels are not coupled together (INSTrument:COUPle:TRACking) this command sets LED indicators above binding posts in the following manner:
- Turn on/off Out1 green indicator (LED_O1) when CH1 is selected
- Turn on/off Out2 indicator (LED_O2) when CH2 is selected
Execution of the OUTP ON command on the channel with tripped one or more protection (OCP, OVP, OPP or OTP) will generate error 201. Use OUTPut:PROTection:CLEar command to clear all tripped protections.
This command also affects Sense+/Sense- indicators (LED_S1+, LED_S1-, LED_S2+, LED_S2-) controlled by the [SOURce:]VOLTage:SENSe[:SOURce] command.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
–
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Return
|
The query command returns 0 if the output is OFF, and 1 if the output is ON.
|
|
Usage example
|
OUTP ON, CH1
OUTP? CH1
1
|
|
Errors
|
108,"Cal output disabled"
201,"Cannot execute before clearing protection"
|
|
Related Commands
|
*TST
INSTrument:COUPle:TRACking
OUTPut:PROTection:CLEar
[SOURce:]VOLTage:SENSe[:SOURce]
|
5.11.2. OUTPut[:STATe]:TRIGgered
|
Syntax
|
OUTPut[:STATe]:TRIGgered {<bool>} [, <channel>]
OUTPut[:STATe]:TRIGgered? [<channel>]
|
|
Description
|
This command programs the pending triggered channel’s output state. The pending triggered output state is a stored value that is transferred to the output terminals when a trigger occurs.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
–
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Return
|
Query the triggered output state presently programmed. If no triggered level is programmed, the OUTPut? state is returned.
|
|
Usage example
|
OUTP?
0
OUTP:TRIG ON
TRIG:SOUR IMM
INIT
OUTP?
1
|
|
Errors
|
108,"Cal output disabled"
201,"Cannot execute before clearing protection"
|
|
Related Commands
|
*TST
OUTPut:PROTection:CLEar
[SOURce:]VOLTage:SENSe[:SOURce]
|
5.11.3. OUTPut:DELay:ON
Not implemented yet
5.11.4. OUTPut:DELay:OFF
Not implemented yet
5.11.5. OUTPut:DPRog
|
Syntax
|
OUTPut:DPRog {<bool>}
OUTPut:DPRog?
|
|
Description
|
Not implemented yet
A down-programmer is a circuit built into the channel’s output of a PSU that actively pulls the output voltage down when the PSU’s channel is moving from a higher setting to a lower setting.
The down-programmer circuit is active by default and only rare situation requires to be turned off. One such situation is when battery is connected as a load. Another one is connecting two channel in parallel when only one down-programmer circuit is enough for actively pulls the output voltage down while lower voltage is set.
Execution of this command also affects bit 11 (DP) of the Operation Instrument Isummary register (see Section Section 3.3.2).
Despite of the down-programmer state programmed by this command, it will be deactivated when the channel output is turned off (i.e. OUTPut[:STATe] OFF) after DP_OFF_DELAY_PERIOD seconds). When the channel output is turned on again, down-programmer will be set back to the state programmed with this command.
If negative output power (DP_NEG_LEV) is measured and last more then DP_NEG_DELAY seconds the down-programmer will be switched off and an error 500 will be generated.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
ON
|
|
Return
|
This query returns 0 (OFF) if down-programmer is disabled, or 1 (ON) when down-programmer is enabled.
|
|
Usage example
|
OUTP:DPR?
1
|
|
Errors
|
500,"Down-programmer on CH1 switched off"
501,"Down-programmer on CH2 switched off"
|
|
Related Commands
|
OUTPut[:STATe]
|
5.11.6. OUTPut:MODE?
|
Syntax
|
OUTPut:MODE? [<channel>]
|
|
Description
|
This command simplify resolving a results that can be obtained reading the bit 8 (CV) and 9 (CC) of the read-only Instrument Isummary Operation Status register for a specific channel (see table in the Section 3.3.2). The PSU can works in one of the three output modes:
- CV (Constant Voltage), when the output voltage equals the voltage setting value and the output current is determined by the load
- CC (Constant Current), when the output current equals the current setting value and the output voltage is determined by the load and
- UR (Unregulated) that is critical mode between CV and CC modes that could be noticed when the output voltage is close to the one end of the full scale (i.e. somewhere below 2 V and above 48 V for the 50 V model that depends of the connected load).
The UR mode is not supported in software simulator.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Return
|
The query returns CV, CC or UR.
|
|
Usage example
|
Set output voltage to 20 V and max. current, check that output voltage is as defined that indicate the constant voltage mode of operation:
VOLT 20; CURR MAX
MEAS:VOLT?
20.0
OUTP:MODE?
CV
|
|
Related Commands
|
STATus:OPERation:INSTrument:ISUMmary[<n>][:EVENt]
STATus:OPERation:INSTrument:ISUMmary[<n>]:CONDition
STATus:OPERation:INSTrument:ISUMmary[<n>]:ENABle
|
5.11.7. OUTPut:PROTection:CLEar
|
Syntax
|
OUTPut:PROTection:CLEar [<channel>]
|
|
Description
|
This command clears the latched protection status that disables the output when an over-voltage, over-current or a power-limit condition is detected.
All conditions that generate the fault must be removed before the latched status can be cleared. The output is restored to the state it was in before the fault condition occurred.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
The following command clears the latched protection status on all channels:
OUTP:PROT:CLE
|
|
Related Commands
|
[SOURce[<n>]]:CURRent:PROTection:STATe
[SOURce[<n>]]:POWer:PROTection:STATe
[SOURce[<n>]]:VOLTage:PROTection:STATe
|
5.11.8. OUTPut:PROTection:COUPle
|
Syntax
|
OUTPut:PROTection:COUPle {<bool>}
OUTPut:PROTection:COUPle?
|
|
Description
|
This command enables or disables output coupling for protection faults. When enabled, all output channels are disabled when a protection fault occurs on any output channel. When disabled, only the affected output channel is disabled when a protection fault is triggered.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Return
|
The query command returns 0 if the protection coupling is OFF (disabled), and 1 if the protection coupling is ON (enabled).
|
|
Usage example
|
OUTP:PROT:COUP ON
OUTP:PROT:COUP?
1
|
|
Related Commands
|
OUTPut:PROTection:CLEar
|
5.11.9. OUTPut:PROTection:MEASure
|
Syntax
|
OUTPut:PROTection:MEASure {<bool>}
OUTPut:PROTection:MEASure?
|
|
Description
|
Not implemented yet
This command enables or disables measuring of output voltage before channel output will be enabled.
If non-zero voltage is present on the output due to e.g. intentionally connected battery or wrong wiring that brings some other power source to the output terminals an error message will be generated.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Return
|
The query command returns 0 if the voltage measuring is disabled (OFF) before output is going to be enabled, and 1 if voltage measuring is ON (enabled).
|
|
Usage example
|
OUTP:PROT:MEAS ON
|
|
Errors
|
505,"External voltage on CH1 detected"
506,"External voltage on CH2 detected"
|
|
Related Commands
|
OUTPut[:STATe]
|
5.11.10. OUTPut:TRACk[:STATe]
|
Syntax
|
OUTPut:TRACk[:STATe] {<bool>}
OUTPut:TRACk[:STATe]?
|
|
Description
|
This command enables or disables the PSU to operate in the track mode. When the track mode is first enabled, the CH2 output will be set to the same voltage level as the CH1 output. Once enabled, any change of the programmed voltage level in either CH1 or CH2 will be reflected in the other channel. The TRACk OFF command returns the PSU to the non-track mode.
A device-specific error 312 will be generated if this command is tried to executed when channels are in any of coupled mode.
The following commands will affect the both channel regardless of which channel is currently selected using the INSTrument[:SELect] or INSTrument:NSELect command):
- OUTPut:PROTection:CLEar
- [SOURce[<n>]]:CURRent, [SOURce[<n>]]:CURRent:STEP, [SOURce[<n>]]:CURRent:TRIGgered, [SOURce[<n>]]:CURRent:LIMit, [SOURce[<n>]]:CURRent:PROTection:DELay, [SOURce[<n>]]:CURRent:PROTection:STATe, [SOURce[<n>]]:CURRent:PROTection:TRIPped?, [SOURce[<n>]]:LIST:COUNt, [SOURce[<n>]]:LIST:CURRent, [SOURce[<n>]]:LIST:DWELl, [SOURce[<n>]]:LIST:VOLTage[:LEVel], [SOURce[<n>]]:LRIPple:AUTO, [SOURce[<n>]]:POWer:LIMit, [SOURce[<n>]]:POWer:PROTection[:LEVel], [SOURce[<n>]]:POWer:PROTection:DELay[:TIME], [SOURce[<n>]]:POWer:PROTection:STATe, [SOURce[<n>]]:POWer:PROTection:TRIPped?, [SOURce[<n>]]:VOLTage, [SOURce[<n>]]:VOLTage:LIMit, [SOURce[<n>]]:VOLTage:STEP, [SOURce[<n>]]:VOLTage:TRIGgered, [SOURce[<n>]]:VOLTage:MODE, [SOURce[<n>]]:VOLTage:PROTection[:LEVel], [SOURce[<n>]]:VOLTage:PROTection:DELay, [SOURce[<n>]]:VOLTage:PROTection:STATe, [SOURce[<n>]]:VOLTage:PROTection:TRIPped?
- TRIGger[:SEQuence][:IMMediate], TRIGger[:SEQuence]:DELay, TRIGger[:SEQuence]:SLOPe, TRIGger[:SEQuence]:SOURce
The following channel specific commands will generate a device-specific error 313 when channels are in tracking mode:
- CALibrate,
- INSTrument:COUPle:TRACking,
- OUTPut:TRACk[:STATe],
- SIMUlator:RPOL, SIMUlator:VOLTage:PROGram,
- [SOURce[<n>]]:LRIPple, [SOURce[<n>]]:LRIPple:AUTO
- [SOURce[<n>]]:VOLTage:PROGram,
At *RST, the tracking mode is disabled.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Return
|
Query the tracking mode state of the PSU. The returned value is 0 (OFF) or 1 (ON).
|
|
Usage example
|
OUTP:TRAC ON
VOLT 12
MEAS?
12.00
MEAS? CH2
12.00
|
|
Errors
|
312,"Cannot execute when the channels are coupled"
313,"Cannot execute in tracking mode"
|
|
Related Commands
|
*RST
INSTrument:COUPle:TRACking
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.12 - SENSe.html
================================================
5.12. SENSe
The SENSe control the current measurement range, energy counting/window, and the data acquisition sequence.
5.12.1. SENSe:AHOur:RESet
|
Syntax
|
SENSe:AHOur:RESet {<channel>}
|
|
Description
|
Not implemented yet
Use this command to reset the amp-hour counter to zero of the specified channel. If channels are coupled (in series or parallel) or in tracking mode, both channel’s counters will be reset to zero.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SENSE:AHO:RES
|
|
Related Commands
|
FETCh:WHOur?
INSTrument:COUPle:TRACking
OUTPut:TRACk[:STATe]
SENSe:AHOur:RESet
SYSTem:CHANnel:INFOrmation:AHOur:TOTal?
|
5.12.2. SENSe:CURRent[:DC]:RANGe[:UPPer]
|
Syntax
|
SENSe:CURRent[:DC]:RANGe[:UPPer] {<range>}
SENSe:CURRent[:DC]:RANGe[:UPPer]?
|
|
Description
|
This command selects a DC current measurement range when Power board with multiple current ranges is installed (e.g. r5B12 that can be find out with the SYSTem:CHANnel:MODel? command). The entered value must be higher than the maximum current that you expect to measure. Units are in amperes.
If selected range is lower then measured current, when load is connected, an error -220 will be generated.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<range>
|
NR2|Discrete
|
0.5, 5, MIN|MAX|DEFault
|
DEF
|
|
Return
|
The query command returns the maximum DC current that can be measured on the range that is presently set.
|
|
Usage example
|
SENS:CURR:RANG?
0.5
|
|
Errors
|
-220,"Cannot set range"
|
|
Related Commands
|
SENSe:CURRent[:DC]:RANGe:AUTO
SYSTem:CHANnel:MODel?
|
5.12.3. SENSe:CURRent[:DC]:RANGe:AUTO
|
Syntax
|
SENSe:CURRent[:DC]:RANGe:AUTO {<bool>}
SENSe:CURRent[:DC]:RANGe:AUTO?
|
|
Description
|
This command enables/disables current measurement autoranging. Autoranging provides seamless measurement ranging, which results in a wide dynamic range with no data being lost across ranges.
When enabled, this command overrides the SENSe:CURRent[:DC]:RANGe setting.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Return
|
The query command returns 0 if current measurement autoranging is OFF, and 1 if current measurement autoranging is ON.
|
|
Usage example
|
SENS:CURR:RANG:AUTO?
0
|
|
Related Commands
|
SENSe:CURRent[:DC]:RANGe
SYSTem:CHANnel:MODel?
|
5.12.4. SENSe:DLOG:FUNCtion:CURRent
|
Syntax
|
SENSe:DLOG:FUNCtion:CURRent {<bool>}, {<channel>}
SENSe:DLOG:FUNCtion:CURRent? {<channel>}
|
|
Description
|
Use this command to enable or disable output current internal data logging on the specified channel.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Return
|
The query command returns the status (0 or 1) of the output current internal data logging enabled on the specified channel
|
|
Usage example
|
SENS:DLOG:FUNC:CURR ON, CH1
|
|
Related Commands
|
INIT:DLOG
SENSe:DLOG:FUNCtion:POWer
SENSe:DLOG:FUNCtion:VOLTage
SENSe:DLOG:PERiod
SENSe:DLOG:TIME
|
5.12.5. SENSe:DLOG:FUNCtion:POWer
|
Syntax
|
SENSe:DLOG:FUNCtion:POWer {<bool>}, {<channel>}
SENSe:DLOG:FUNCtion:POWer? {<channel>}
|
|
Description
|
Use this command to enable or disable output power internal data logging on the specified channel.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Return
|
The query command returns the status (0 or 1) of the output power internal data logging enabled on the specified channel
|
|
Usage example
|
SENS:DLOG:FUNC:VOLT OFF, CH2
|
|
Related Commands
|
INIT:DLOG
SENSe:DLOG:FUNCtion:CURRent
SENSe:DLOG:FUNCtion:VOLTage
SENSe:DLOG:PERiod
SENSe:DLOG:TIME
|
5.12.6. SENSe:DLOG:FUNCtion:VOLTage
|
Syntax
|
SENSe:DLOG:FUNCtion:VOLTage {<bool>}, {<channel>}
SENSe:DLOG:FUNCtion:VOLTage? {<channel>}
|
|
Description
|
Use this command to enable or disable output voltage internal data logging on the specified channel.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Return
|
The query command returns the status (0 or 1) of the output voltage internal data logging enabled on the specified channel
|
|
Usage example
|
SENS:DLOG:FUNC:VOLT OFF, CH2
|
|
Related Commands
|
INIT:DLOG
SENSe:DLOG:FUNCtion:CURRent
SENSe:DLOG:FUNCtion:POWer
SENSe:DLOG:PERiod
SENSe:DLOG:TIME
|
5.12.7. SENSe:DLOG:PERiod
|
Syntax
|
SENSe:DLOG:PERiod {<time>}
SENSe:DLOG:PERiod?
|
|
Description
|
Use this command to set the sample period in seconds. For the sample period, the
minimum is 20 ms, and it has to be in integral of 20 ms, while the maximum is 120 s. The entered value will be rounded to the nearest 20 ms integral.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<time>
|
NR2
|
0.02 – 120
|
0.02
|
|
Return
|
The query command returns the sample period in seconds.
|
|
Usage example
|
SENS:DLOG:PER 1
|
|
Related Commands
|
SENSe:DLOG:TIME
|
5.12.8. SENSe:DLOG:TIME
|
Syntax
|
SENSe:DLOG:TIME {<time>}
SENSe:DLOG:TIME?
|
|
Description
|
This command sets the sample duration, the entered value is in seconds. For sample duration, the maximum is 86 400 000 seconds or 24 000 hours or 1000 days (depending of the available space on the installed SD Card, see the MMEMory:INFOrmation? command).
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<time>
|
NR1
|
1 – 86400000
|
60
|
|
Return
|
The query command returns the sample duration in seconds.
|
|
Usage example
|
SENS:DLOG:TIME 3600
|
|
Related Commands
|
MMEMory:INFOrmation?
SENSe:DLOG:PERiod
|
5.12.9. SENSe:WHOur:RESet
|
Syntax
|
SENSe:WHOur:RESet {<channel>}
|
|
Description
|
Not implemented yet
Use this command to reset the watt-hour counter to zero of the specified channel. If channels are coupled (in series or parallel) or in tracking mode, both channel’s counters will be reset to zero.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SENS:WHO:RES
|
|
Related Commands
|
FETCh:AHOur?
INSTrument:COUPle:TRACking
OUTPut:TRACk[:STATe]
SENSe:WHOur:RESet
SYSTem:CHANnel:INFOrmation:WHOur:TOTal
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.13 - SOURce.html
================================================
5.13. SOURce
The SOURce commands are used to set the output voltage and current values, remote voltage sensing, and implemented protection mechanisms on the specified channel. Although the APPLy command provides the most straightforward method to program the PSU over the remote interfaces, the SOURce commands give you more flexibility to change individual parameters.
5.13.1. [SOURce[<n>]]:CURRent
|
Syntax
|
[SOURce[<n>]]:CURRent[:LEVel][:IMMediate][:AMPLitude] {<current>}
[SOURce[<n>]]:CURRent[:LEVel][:IMMediate][:AMPLitude]? [<query current>]
|
|
Description
|
This command sets the immediate current level of the channel. Units are in amperes. When [:SOURce[<n>]] or [<n>] is omitted, the currently selected channel will be affected by this command.
This command also increases or decreases the immediate current level using the ‘UP’ or DOWN parameter by a predetermined amount. The command CURRent:STEP sets the amount of increase or decrease. A new increment setting will not cause an execution error -222,"Data out of range" when the maximum or the minimum rated current is exceeded – the output value will be set to the maximum or the minimum value instead.
At *RST, the signal being sourced will be set to a "safe" condition. This is achieved by setting the amplitude to its MINimum value (see Section 8.1).
|
|
Return
|
The query command returns the programmed current level. CURR? MIN, CURR? DEF and CURR? MAX can be used to obtain minimum, default and maximum current level on the currently selected channel. For actual output current value use MEASure:CURRent command.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<current>
|
NR2|Discrete
|
0 to MAXimum, MIN|DEF|MAX|UP|DOWN
The maximum value is dependent on the PSU current rating. See Section 8.1
|
–
|
|
|
<query current>
|
Discrete
|
MIN|DEF|MAX
|
–
|
|
Usage example
|
A 10 ohm load is connected and voltage is set to 20 V. With MAX current set measured current will be 2 A. When new current value is set to 1.2 A, voltage will drop to 12 V (the channel enters the CC mode of operation):
INST CH1
VOLT 20
CURR MAX
MEAS:VOLT?
20.00
CURR 1.2
MEAS:VOLT?
12.00
Query that returns maximum current of the currently selected channel:
CURR? MAX
5.00
|
|
Errors
|
150,"Power limit exceeded"
-222,"Data out of range"
|
|
Related Commands
|
*SAV
*RST
APPLy
MEASure[:SCALar]:CURRent[:DC]?
[SOURce[<n>]]:CURRent[:LEVel][:IMMediate]:STEP[:INCRement]
|
5.13.2. [SOURce[<n>]]:CURRent:STEP
|
Syntax
|
[SOURce[<n>]]:CURRent[:LEVel][:IMMediate]:STEP[:INCRement] {<step>}
[SOURce[<n>]]:CURRent[:LEVel][:IMMediate]:STEP[:INCRement]? [<query step>]
|
|
Description
|
Set the step of the current change of the channel. When [SOURce[<n>]] or [<n>] is omitted, the currently selected channel will be affected by this command. Step change is performed by using UP and DOWN as parameter for the [SOURce[<n>]]:CURRent command.
|
|
Return
|
The query returns the step of the current change of the specified channel.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<step>
|
NR2|Discrete
|
0.01 to 1|DEFault
|
0.05
|
|
|
<query step>
|
Discrete
|
DEFault
|
–
|
|
Usage example
|
Return default step value:
CURR:STEP? DEF
0.05
When a 10 ohm load is connected with voltage set to 20 V and current to 1 A the first channel enters CC mode of operation. Current is then increased from 1 A in two steps to 1.2 A:
APPL CH1, 20,1
MEAS:VOLT?
10.00
CURR:STEP 0.1
CURR UP
MEAS:CURR?
1.10
CURR UP
MEAS:CURR?
1.20
MEAS:VOLT?
12.00
|
|
Related Commands
|
*SAV
[SOURce[<n>]]:CURRent
|
5.13.3. [SOURce[<n>]]:CURRent:TRIGgered
|
Syntax
|
[SOURce[<n>]]:CURRent[:LEVel]:TRIGgered[:AMPLitude] {<current>}
[SOURce[<n>]]:CURRent[:LEVel]:TRIGgered[:AMPLitude]? [<query current>]
|
|
Description
|
This command programs the pending triggered current level. The pending triggered current level is a stored value that is transferred to the output terminals when a trigger occurs.
A pending triggered level is not affected by subsequent CURRent commands.
|
|
Return
|
Query the triggered current level presently programmed. If no triggered level is programmed, the CURRent level is returned. CURR:TRIG? MIN and CURR:TRIG? MAX return the lowest and highest programmable triggered current levels.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<current>
|
NR2|Discrete
|
0 to maximum, MIN|DEF|MAX
The MAXimum value is dependent on the PSU current rating. See Section 8.1
|
0.00
|
|
|
<query current>
|
Discrete
|
MIN|DEF|MAX
|
–
|
|
Usage example
|
On the currently selected channel voltage will be set to 3.3 V and current to 1 A when INITiate command is executed:
VOLT:TRIG 3.3
CURR:TRIG 1
TRIG:SOUR IMM
INIT
|
|
Related Commands
|
ABORt
|
5.13.4. [SOURce[<n>]]:CURRent:LIMit[:POSitive][:IMMediate][:AMPLitude]
|
Syntax
|
[SOURce[<n>]]:CURRent:LIMit[:POSitive][:IMMediate][:AMPLitude] {<current>}
[SOURce[<n>]]:CURRent:LIMit[:POSitive][:IMMediate][:AMPLitude]? [<query current>]
|
|
Description
|
This command sets the channel’s output current limit. Units are in amperes.
When [:SOURce[<n>]] or [<n>] is omitted, the currently selected channel will be affected by this command.
This command could be used as mean of protection against incidental programming of too high output current that can be set for example with [SOURce[<n>]]:CURRent:STEP command.
Maximum limit value will be affected with detected failure of cooling fan or channel’s temperature sensor. Use CURR:LIM? MAX to query actual value.
|
|
Return
|
The query returns the max. allowed output current of the specified channel. Querying MAX on an output channel returns the maximum current limit.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<current>
|
NR2|Discrete
|
0 to MAXimum, MIN|DEF|MAX
The MAXimum value is dependent on the PSU current rating. See Section 8.1
|
MAXimum
|
|
|
<query current>
|
Discrete
|
MIN|DEF|MAX
|
–
|
|
Usage example
|
Normal mode of operation for 5 A model:
CURR:LIM MAX?
5.00
Max. allowable current with faulty cooling fan or temperature sensor:
CURR:LIM MAX?
1.00
|
|
Related Commands
|
*SAV
[SOURce[<n>]]:CURRent:STEP
[SOURce[<n>]]:POWer:LIMit
[SOURce[<n>]]:VOLTage:LIMit[:POSitive][:IMMediate][:AMPLitude]
|
5.13.5. [SOURce[<n>]]:CURRent:MODE
|
Syntax
|
[SOURce[<n>]]:CURRent:MODE {<mode>}
[SOURce[<n>]]:CURRent:MODE?
|
|
Description
|
This command determines what happens to the output current when the transient system is initiated and triggered:
- FIXed – the output current remains at the immediate value
- LIST – the output follows the list values when a trigger occurs.
- STEP – the output goes to the triggered level when a trigger occurs.
|
|
Return
|
The query command returns the current mode of the currently selected channel.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<mode>
|
Discrete
|
FIXed|LIST|STEP
|
FIXed
|
|
Usage example
|
CURR:MODE?
FIX
|
|
Related Commands
|
[SOURce[<n>]]:LIST:CURRent[:LEVel]
[SOURce[<n>]]:VOLTage:MODE
|
5.13.6. [SOURce[<n>]]:CURRent:SLEW:FALLing
Not implemented yet
5.13.7. [SOURce[<n>]]:CURRent:SLEW:RISing
Not implemented yet
5.13.8. [SOURce[<n>]]:CURRent:PROTection:DELay[:TIME]
|
Syntax
|
[SOURce[<n>]]:CURRent:PROTection:DELay[:TIME] {<time>}
[SOURce[<n>]]:CURRent:PROTection:DELay[:TIME]? [<query time>]
|
|
Description
|
This command sets the over-current protection delay. The over-current protection function will not be triggered on the selected output channel during the delay time. After the delay time has expired, the over-current protection function will be active.
This prevents momentary changes in output status from triggering the over-current protection function. Programmed values can range from 0 to 10 seconds. See also Section 8.1
|
|
Return
|
The query command returns the programmed delay time.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<time>
|
NR2|Discrete
|
0 – 10|DEFault
|
20 ms
|
|
|
<query time>
|
Discrete
|
DEFault
|
–
|
|
Usage example
|
Get default OCP delay of 20 milliseconds:
CURR:PROT:DEL? DEF
0.02
|
|
Related Commands
|
*SAV
OUTPut:PROTection:CLEar
|
5.13.9. [SOURce[<n>]]:CURRent:PROTection:STATe
|
Syntax
|
[SOURce[<n>]]:CURRent:PROTection:STATe {<bool>}
[SOURce[<n>]]:CURRent:PROTection:STATe?
|
|
Description
|
This command enables or disables the over-current protection (OCP) function. The enabled state is ON (1); the disabled state is OFF (0).
Since the PSU do not have a dedicated over-current protection circuit that can be programmed independently of output current level, entering the CC (constant current) mode of operation is used as a trigger to start OCP sequence. When delay time specified with the [SOURce[<n>]]:CURRent:PROTection:DELay[:TIME] command expired the output turns off and the Questionable Condition status register OCP bit 9 is set. An error tone will also follow if beeper is enabled (see SYSTem:BEEPer:STATe).
[SOURce[<n>]]:CURRent:PROTection:TRIPped? command can be used to query whether over-current protection occurred on the selected channel.
|
|
Return
|
The query command returns 0 if the current protection state is OFF, and 1 if the current protection state is ON.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Usage example
|
CURR:PROT:STAT?
0
|
|
Related Commands
|
*SAV
OUTPut:PROTection:CLEar
OUTPut:PROTection:COUPle
[SOURce[<n>]]:CURRent:PROTection:DELay[:TIME]
[SOURce[<n>]]:CURRent:PROTection:TRIPped
SYSTem:BEEPer:STATe
|
5.13.10. [SOURce[<n>]]:CURRent:PROTection:TRIPped?
|
Syntax
|
[SOURce[<n>]]:CURRent:PROTection:TRIPped?
|
|
Description
|
Query whether OCP occurred on the currently selected channel. When protection is tripped bit 9 (OCP) of the Questionable Instrument Isummary register will be set (see Section 3.4.2).
The OUTPut:PROTection:CLEar command can be send to clear OCP condition on the selected channel.
|
|
Return
|
This query returns a 1 if the protection circuit is tripped and a 0 if it is untripped.
|
|
Usage example
|
CURR:PROT:TRIP?
1
|
|
Related Commands
|
OUTPut:PROTection:CLEar
|
5.13.11. [SOURce[<n>]]:LIST:COUNt
|
Syntax
|
[SOURce[<n>]]:LIST:COUNt {<count>}
[SOURce[<n>]]:LIST:COUNt?
|
|
Description
|
This command sets the number of times that the list is executed before it is completed. The list count range is 1 through 255. Use the INFinity parameter or 0 to execute a list continuously.
Use ABORt to stop the list at any time. When the list is aborted, the output returns to the settings that were in effect before the list started.
|
|
Return
|
The query command returns the list count. Multiple responses are separated by commas. If a repeat count of 0 is returned, it means the list is set to repeat continuously.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<count>
|
NR1|Discrete
|
0|1 – 65535|INFinity
|
1
|
|
Usage example
|
LIST:COUN?
10
|
|
Related Commands
|
ABORt
INITiate[:IMMediate]
MMEMory:LOAD:LIST[<n>]
MMEMory:STORe:LIST[<n>]
|
5.13.12. [SOURce[<n>]]:LIST:CURRent[:LEVel]
|
Syntax
|
[SOURce[<n>]]:LIST:CURRent[:LEVel] {<current>}[, ...]
[SOURce[<n>]]:LIST:CURRent[:LEVel]?
|
|
Description
|
This command specifies the current setting for each list step in amperes. A comma-delimited list of up to 256 steps may be programmed.
The order in which the current values are entered determines the sequence when the list executes.
To create a valid list, the VOLTage, CURRent and DWELl lists must either all be the same length, or have a length of 1, which is interpreted as having the same length as the list with the maximum length.
This command overwrites any previously programmed current list; it does not append to the previous list.
|
|
Return
|
The query command returns the programmed current level. Multiple responses are separated by commas.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<current>
|
NR2|Discrete
|
0 to maximum, MIN|DEF|MAX|UP|DOWN
The MAXimum value is dependent on the PSU current rating. See Section 8.1
|
–
|
|
Usage example
|
LIST:CURR 0.25
|
|
Errors
|
306,"Too many list points"
|
|
Related Commands
|
MMEMory:LOAD:LIST[<n>]
MMEMory:STORe:LIST[<n>]
[SOURce[<n>]]:CURRent:MODE
[SOURce[<n>]]:LIST:COUNt
|
5.13.13. [SOURce[<n>]]:LIST:DWELl
|
Syntax
|
[SOURce[<n>]]:LIST:DWELl {<time>}[, ...]
[SOURce[<n>]]:LIST:DWELl?
|
|
Description
|
This command specifies the dwell time for each list step. A comma-delimited list of up to 256 steps may be programmed. Dwell time is the time that the output will remain at a specific step. Dwell times can be programmed from 0 through 65535 seconds.
Note that min. dwell time that can be achieved during the list execution depends of MCU activity and waveform shape. Therefore one have to find that out experimentally while list is executed on desired number of channels (one or two). Usage of oscilloscope is recommended for fast transitions since e.g. YT view resolution cannot be set to less then 20 ms. The expected usable min. dwell time goes well below 10 ms (down to 1 ms).
|
|
Return
|
The query command returns the programmed dwell times. Multiple responses are separated by commas.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<time>
|
NR2
|
0 – 65535
|
–
|
|
Usage example
|
LIST:DWEL 20ms,10ms,10ms,50ms
|
|
Errors
|
306,"Too many list points"
|
|
Related Commands
|
MMEMory:LOAD:LIST[<n>]
MMEMory:STORe:LIST[<n>]
[SOURce[<n>]]:LIST:COUNt
|
5.13.14. [SOURce[<n>]]:LIST:VOLTage[:LEVel]
|
Syntax
|
[SOURce[<n>]]:LIST:VOLTage[:LEVel] {<voltage>}[, ...]
[SOURce[<n>]]:LIST:VOLTage[:LEVel]?
|
|
Description
|
This command specifies the voltage setting for each list step in volts. A comma-delimited list of up to 256 steps may be programmed.
The order in which the voltage values are entered determines the sequence when the list executes.
To create a valid list, the VOLTage, CURRent and DWELl lists must either all be the same length, or have a length of 1, which is interpreted as having the same length as the list with the maximum length.
This command overwrites any previously programmed voltage list; it does not append to the previous list.
|
|
Return
|
The query command returns the programmed voltage level. Multiple responses are separated by commas.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<voltage>
|
NR2|Discrete
|
0 to maximum, MIN|DEF|MAX|UP|DOWN
The maximum value is dependent on the PSU voltage rating. See Section 8.1
|
–
|
|
Usage example
|
Programming the list that contain 4 steps and will be executed 20 times on the channel 2. Execution will start by receiving remote command (*TRG) since BUS is selected as a trigger source:
INST CH2
LIST:COUN 20
LIST:VOLT 0,1.5,3,4.5
LIST:CURR 0.25
LIST:DWEL 20ms,10ms,10ms,50ms
OUTP ON
*OPC?
0
TRIG:SOUR BUS
INIT
*TRG
|
|
Errors
|
306,"Too many list points"
|
|
Related Commands
|
MMEMory:LOAD:LIST[<n>]
MMEMory:STORe:LIST[<n>]
[SOURce[<n>]]:LIST:COUNt
[SOURce[<n>]]:VOLTage:MODE
|
5.13.15. [SOURce[<n>]]:LRIPple
|
Syntax
|
[SOURce[<n>]]:LRIPple {<bool>}
[SOURce[<n>]]:LRIPple?
|
|
Description
|
This command enables or disables low output ripple (noise) mode of operation when it’s supported by installed channel board (use the SYSTem:CHANnel[:INFOrmation]:PROGram? to query channel functionality).
When low ripple mode of operation is selected the power pre-regulator is bypassed by setting so-called Duty cycle of the SMPS controller to 100 %. That will disable switching frequency and therefore that otherwise hard to filter component disappear entirely from the channel output. In that case the remaining noise mainly comes from the low power bias switching pre-regulator.
The maximum output power in this mode of operation is limited to stay within SOA (Safe operating area) of the pre-regulator and post-regulator regulation elements. The maximum output power is limited by the first of the following conditions that is met:
- The pre-regulator regulation element (switching mosfet) capability is limited with max. allowed continuous current (SOA_PREG_CURR value) for the applied input voltage (SOA_VIN value). The set output current cannot exceeds this value in any moment.
- The post-regulator regulation element (pass mosfet) could dissipate finite power (SOA_POSTREG_PTOT value) while load is connected. Therefore output power cannot exceed product of voltage difference (SOA_VIN and output voltage) and output current.
For example, when output voltage is set to 12 V and SOA_VIN = 50 V, SOA_PREG_CURR = 0.8 A and SOA_POSTREG_PTOT = 20 W, the max. output current in low ripple mode cannot exceed 0.526 A because SOA_VIN-VOLT = 50-12 = 38 V and Imax=SOA_POSTREG_PTOT/38 = 20/38 = 0.526 A.
If output voltage is set to 36 V with the same SOA values as in example above the max. output current cannot exceed 0.8 A (limited by SOA_PREG_CURR) regardless of the fact that max. power dissipation of 20 W allows output current of up to 1.428 A or 20/(50-36).
If low ripple mode is set an error will be generated when any of the limits are exceeded. The AUTOmatic mode should be used to avoid error conditions. Also if AUTOmatic mode disables low ripple, an attempt to enable it using the [SOURce[<n>]]:LRIPple ON command will generate an execution error.
An attempt to enter low ripple mode while remote (EXTernal) voltage programming is active ([SOURce[<n>]]:VOLTage:PROGram[:SOURce]) will generate -221 error.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Return
|
The query command returns 1 if the low ripple mode is active, and 0 if the low ripple mode is not active.
|
|
Usage example
|
VOLT:LRIP?
0
|
|
Errors
|
-200,"Execution error"
-221,"Settings conflict"
-241,"Hardware missing"
|
|
Related Commands
|
*SAV
[SOURce[<n>]]:LRIPple:AUTO
SYSTem:CHANnel:INFOrmation:PROGram?
|
5.13.16. [SOURce[<n>]]:LRIPple:AUTO
|
Syntax
|
[SOURce[<n>]]:LRIPple:AUTO {<bool>}
[SOURce[<n>]]:LRIPple:AUTO?
|
|
Description
|
Use this command to allow automatic changing to the low ripple (noise) mode of operation.
If AUTOmatic mode of operation is enabled, the channel will stay in low ripple mode of operation as long as output power does not exceed calculated limitations allowed for that mode of operation. The [SOURce[<n>]]:LRIPple? query can be used to determine current status.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Return
|
The query command returns 1 if the low ripple automatic mode is active, and 0 if the low ripple automatic mode is not active.
|
|
Usage example
|
VOLT:LRIP:AUTO 1
VOLT:LRIP?
1
|
|
Errors
|
-241,"Hardware missing"
312,"Cannot execute when the channels are coupled"
|
|
Related Commands
|
*SAV
INSTrument:COUPle:TRACking
SOURce[<n>]]:LRIPple
SYSTem:CHANnel:INFOrmation:PROGram?
|
5.13.17. [SOURce[<n>]]:POWer:LIMit
|
Syntax
|
[SOURce[<n>]]:POWer:LIMit {<power>}
[SOURce[<n>]]:POWer:LIMit? [<query power>]
|
|
Description
|
This command sets the channel’s output power limit. Units are in Watts. Such limitation is required if main transformer (or AC/DC adapter if DC power input is used) cannot provide the same power as connected channel power module. For example if power module can deliver 200 W but main transformer offer only 160 W then MAXimum allowable continuous power is only 160 W.
|
|
Return
|
The query returns the max. allowed output power of the specified channel. Querying MAX on an output channel returns the maximum rated power limit.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<power>
|
NR2|Discrete
|
0 to MAXimum, MIN|DEF|MAX
The MAXimum value is dependent on the PSU power rating. See Section 8.1
|
MAXimum
|
|
|
<query power>
|
Discrete
|
MIN|MAX
|
–
|
|
Usage example
|
POW:LIM DEF
POW:LIM?
150.00
|
|
Related Commands
|
*SAV
[SOURce[<n>]]:CURRent:LIMit[:POSitive][:IMMediate][:AMPLitude]
[SOURce[<n>]]:VOLTage:LIMit[:POSitive][:IMMediate][:AMPLitude]
|
5.13.18. [SOURce[<n>]]:POWer:PROTection[:LEVel]
|
Syntax
|
[SOURce[<n>]]:POWer:PROTection[:LEVel] {<power>}
[SOURce[<n>]]:POWer:PROTection[:LEVel]?
|
|
Description
|
Set the over-power protection (OPP) value of the channel. When [:SOURce[<n>]] or [<n>] is omitted, the currently selected channel will be affected by this command. When the over-power protection function of the specified channel is enabled ([SOURce[<n>]]:POWer:PROTection:STATe), the output turns off automatically when the output power exceeds the over-power protection value currently set.
[SOURce[<n>]]:POWer:PROTection:TRIPped? command can be used to query whether over-power protection occurred on the selected channel.
|
|
Return
|
Query the over-power protection (OPP) value of the selected channel.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<power>
|
NR2|Discrete
|
0 to MAXimum, MIN|DEF|MAX
The maximum value is dependent on the PSU power rating. See Section 8.1
|
DEFault
|
|
Usage example
|
Set power protection to 50 W on the channel 2:
SOUR2:POW:PROT 50
|
|
Related Commands
|
*SAV
OUTPut:PROTection:COUPle
[SOURce[<n>]]:POWer:PROTection:TRIPped?
[SOURce[<n>]]:POWer:PROTection:STATe
|
5.13.19. [SOURce[<n>]]:POWer:PROTection:DELay[:TIME]
|
Syntax
|
[SOURce[<n>]]:POWer:PROTection:DELay[:TIME] {<time>}
[SOURce[<n>]]:POWer:PROTection:DELay[:TIME]? [<query time>]
|
|
Description
|
This command sets the over-power protection (OPP) delay. The over-power protection function will not be triggered on the selected output channel during the delay time. After the delay time has expired, the over-power protection function will be active.
This prevents momentary changes in output status from triggering the over-power protection function. Programmed values can range from 0 to 300 seconds. See also Section 8.1
|
|
Return
|
The query command returns the programmed delay time.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<time>
|
NR2|Discrete
|
0 – 300|DEFault
|
10
|
|
|
<query time>
|
Discrete
|
DEFault
|
–
|
|
Usage example
|
Get default OPP delay of 10 seconds:
POW:PROT:DEL? DEF
10
|
|
Related Commands
|
*SAV
OUTPut:PROTection:CLEar
|
5.13.20. [SOURce[<n>]]:POWer:PROTection:STATe
|
Syntax
|
[SOURce[<n>]]:POWer:PROTection:STATe {<bool>}
[SOURce[<n>]]:POWer:PROTection:STATe?
|
|
Description
|
This command enables or disables the over-power protection (OPP) function. The enabled state is ON (1); the disabled state is OFF (0). If the over-power protection function is enabled and the measure output power reach value set by [SOURce[<n>]]:POWer:PROTection[:LEVel] the output is disabled and the Questionable Condition status register OPP bit 10 is set.
|
|
Return
|
The query command returns 0 if the current protection state is OFF, and 1 if the current protection state is ON.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Usage example
|
POW:PROT:STAT ON
POW:PROT:STAT?
1
|
|
Related Commands
|
*SAV
OUTPut:PROTection:CLEar
[SOURce[<n>]]:POWer:PROTection[:LEVel]
|
5.13.21. [SOURce[<n>]]:POWer:PROTection:TRIPped?
|
Syntax
|
[SOURce[<n>]]:POWer:PROTection:TRIPped?
|
|
Description
|
Query whether OPP occurred on the currently selected channel. When protection is tripped bit 10 (OPP) of the Questionable Instrument Isummary register will be set (see Section 3.4.2).
The OUTPut:PROTection:CLEar command can be send to clear OPP condition on the selected channel.
|
|
Return
|
This query returns a 1 if the protection circuit is tripped and a 0 if it is untripped.
|
|
Usage example
|
POW:PROT:TRIP?
0
|
|
Related Commands
|
OUTPut:PROTection:CLEar
|
5.13.22. [SOURce[<n>]]:VOLTage
|
Syntax
|
[SOURce[<n>]]:VOLTage[:LEVel][:IMMediate][:AMPLitude] {<voltage>}
[SOURce[<n>]]:VOLTage[:LEVel][:IMMediate][:AMPLitude]? [<query voltage>]
|
|
Description
|
This command sets the immediate voltage level of the output channel. Units are in volts. When [:SOURce[<n>]] or [<n>] is omitted, the currently selected channel will be affected by this command.
This command also increases or decreases the immediate voltage level using the ‘UP’ or DOWN parameter by a predetermined amount. The command VOLTage:STEP sets the amount of increase or decrease. A new increment setting will not cause an execution error -222,"Data out of range" when the maximum or the minimum rated current is exceeded – the output value will be set to the maximum or the minimum value instead.
At *RST, the signal being sourced will be set to a "safe" condition. This is achieved by setting the amplitude to its MINimum value (see Section 8.1).
|
|
Return
|
The query command returns the programmed voltage level. VOLT? MIN, VOLT? DEF and VOLT? MAX can be used to obtain minimum, default and maximum voltage level on the currently selected channel. For actual output voltage value use MEASure:VOLTage? command.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<voltage>
|
NR2|Discrete
|
0 to MAXimum, MIN|DEF|MAX|UP|DOWN
The maximum value is dependent on the PSU voltage rating. See Section 8.1
|
–
|
|
|
<query voltage>
|
Discrete
|
MIN|DEF|MAX
|
–
|
|
Usage example
|
A 10 ohm load is connected and current is set to 1 A. With MAX voltage set measured voltage will be 10 V. When new voltage value is set to 5 V, current will drop to 0.5 A (the channel enters the CV mode of operation):
INST CH1
VOLT MAX
CURR 1
MEAS:CURR?
1.00
VOLT 5
MEAS:CURR?
0.50
Query that returns maximum current of the currently selected channel:
CURR? MAX
5.00
|
|
Errors
|
150,"Power limit exceeded"
-222,"Data out of range"
|
|
Related Commands
|
*SAV
*RST
APPLy
MEASure[:SCALar]:VOLTage[:DC]?
[SOURce[<n>]]:VOLTage[:LEVel][:IMMediate]:STEP[:INCRement]
|
5.13.23. [SOURce[<n>]]:VOLTage:LIMit[:POSitive][:IMMediate][:AMPLitude]
|
Syntax
|
[SOURce[<n>]]:VOLTage:LIMit[:POSitive][:IMMediate][:AMPLitude] {<voltage>}
[SOURce[<n>]]:VOLTage:LIMit[:POSitive][:IMMediate][:AMPLitude]? [<query voltage>]
|
|
Description
|
This command sets the channel’s output voltage limit. Units are in volts.
When [:SOURce[<n>]] or [<n>] is omitted, the currently selected channel will be affected by this command.
This command could be used as mean of protection against incidental programming of too high output voltage that can be set for example with [SOURce[<n>]]:VOLTage:STEP command.
|
|
Return
|
The query returns the max. allowed output voltage of the specified channel. Querying MAX on an output channel returns the maximum voltage limit.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<voltage>
|
NR2|Discrete
|
0 to MAXimum, MIN|DEF|MAX
The MAXimum value is dependent on the PSU current rating. See Section 8.1
|
MAXimum
|
|
|
<query voltage>
|
Discrete
|
MIN|MAX
|
–
|
|
Usage example
|
VOLT:LIM 20
|
|
Related Commands
|
*SAV
[SOURce[<n>]]:CURRent:STEP
[SOURce[<n>]]:POWer:LIMit
[SOURce[<n>]]:VOLTage:LIMit[:POSitive][:IMMediate][:AMPLitude]
|
5.13.24. [SOURce[<n>]]:VOLTage:STEP
|
Syntax
|
[SOURce[<n>]]:VOLTage[:LEVel][:IMMediate]:STEP[:INCRement] {<step>}
[SOURce[<n>]]:VOLTage[:LEVel][:IMMediate]:STEP[:INCRement]? [<query step>]
|
|
Description
|
Set the step of the voltage change of the channel. When [SOURce[<n>]] or [<n>] is omitted, the currently selected channel will be affected by this command. Step change is performed by using UP and DOWN as parameter for the [SOURce[<n>]]:VOLTage command.
|
|
Return
|
The query returns the step of the voltage change of the specified channel.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<step>
|
NR2|Discrete
|
0.01 to 10|DEFault
|
0.1
|
|
|
<query step>
|
Discrete
|
DEFault
|
–
|
|
Usage example
|
Return default step value:
VOLT:STEP? DEF
0.10
By connecting a 10 ohm load and current set to 2 A and voltage to 10 V the first channel enters the CV mode of operation. Voltage is then decreased from 10 V in two steps to 6 V:
APPL CH1, 10,2
MEAS:CURR?
1.0
VOLT:STEP 2
VOLT DOWN
VOLT DOWN
MEAS:VOLT?
6.0
MEAS:CURR?
0.60
|
|
Related Commands
|
*SAV
[SOURce[<n>]]:VOLTage
|
5.13.25. [SOURce[<n>]]:VOLTage:TRIGgered
|
Syntax
|
[SOURce[<n>]]:VOLTage[:LEVel]:TRIGgered[:AMPLitude] {<voltage>}
[SOURce[<n>]]:VOLTage[:LEVel]:TRIGgered[:AMPLitude]? [<query voltage>]
|
|
Description
|
This command programs the pending triggered voltage level. The pending triggered current level is a stored value that is transferred to the output terminals when a trigger occurs.
A pending triggered level is not affected by subsequent VOLTage commands.
|
|
Return
|
Query the triggered voltage level presently programmed. If no triggered level is programmed, the VOLTage level is returned. VOLT:TRIG? MIN and VOLT:TRIG? MIN return the lowest and highest programmable triggered voltage levels.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<voltage>
|
NR2|Discrete
|
0 to maximum, MIN|DEF|MAX
The maximum value is dependent on the PSU voltage rating. See Section 8.1
|
0.00
|
|
|
<query voltage>
|
Discrete
|
MIN|MAX
|
|
|
Usage example
|
On the currently selected channel voltage will be set to 3.3V and current to 1A when INITiate command is executed:
VOLT:TRIG 3.3
CURR:TRIG 1
TRIG:SOUR IMM
INIT
|
|
Related Commands
|
ABORt
|
5.13.26. [SOURce[<n>]]:VOLTage:MODE
|
Syntax
|
[SOURce[<n>]]:VOLTage:MODE {<mode>}
[SOURce[<n>]]:VOLTage:MODE?
|
|
Description
|
This command determines what happens to the output voltage when the transient system is initiated and triggered:
- FIXed – the output current remains at the immediate value
- LIST – the output follows the list values when a trigger occurs.
- STEP – the output goes to the triggered level when a trigger occurs.
|
|
Return
|
The query command returns the voltage mode of the currently selected channel.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<mode>
|
Discrete
|
FIXed|LIST|STEP
|
FIXed
|
|
Usage example
|
VOLT:MODE?
LIST
|
|
Related Commands
|
[SOURce[<n>]]:LIST:VOLTage[:LEVel]
[SOURce[<n>]]:CURRent:MODE
|
5.13.27. [SOURce[<n>]]:VOLTage:PROGram[:SOURce]
|
Syntax
|
[SOURce[<n>]]:VOLTage:PROGram[:SOURce] {<source>}
[SOURce[<n>]]:VOLTage:PROGram[:SOURce]?
|
|
Description
|
Use this command to define source for output voltage programming if channel support this option (use the SYSTem:CHANnel[:INFOrmation]:PROGram? to query channel programming capability).
A channel’s D/A converter controlled by CPU is used by default for voltage output programming. That source can be calibrated (see the CALibrate subsystem) and provide output within safe limits.
The external voltage programming could be used when fast interaction with an external process is required. For example if tracking output of the connected D.U.T. (i.e. a power supply) is needed the PSU effectively becomes a pre-regulator keeping its output voltage in relation with changes of the D.U.T. output keeping constant difference between connected D.U.T input and output and in that way its max. power dissipation.
Max. D/A converter programmed voltage of 2.5 V would results with MAXimal voltage output regardless of the channel’s voltage range (see Section 8.1). Therefore if EXTernal programming source is selected, any voltage value higher then 2.5 V could produce unexpected results and eventually damage the PSU and/or connected load.
To limit possible damage when programming source is set to EXTernal, the over-voltage protection (OVP) will be activated and set to MAXimum ([SOURce[<n>]]:VOLTage:PROTection[:LEVel]) with protection delay time set to zero ([SOURce[<n>]]:VOLTage:PROTection:DELay[:TIME]). Further adjustment of OVP level and delay is also allowed (e.g. to decrease OVP level or increase delay time).
The enabled state is EXTernal (1); the disabled state is INTernal (0). Execution of this command also affects bit 13 (RPROG) of the Operation Instrument Isummary register (see Section 3.3.2).
Self-test operation initiated by *TST? command will reset voltage programming on all PSU channels to the internal/local source.
If external programming source is selected the DIAGnostic[:INFOrmation]:ADC? Query returns 0.00 value for U_SET.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<source>
|
Discrete
|
INTernal|EXTernal
|
INTernal
|
|
Return
|
The query command returns 0 if the local (internal) voltage programming is selected, and 1 if the remote (external) sense is selected.
|
|
Usage example
|
VOLT:PROG EXT
VOLT:PROG?
1
|
|
Errors
|
-241,"Hardware missing"
312,"Cannot execute when the channels are coupled"
|
|
Related Commands
|
*TST
DIAGnostic[:INFOrmation]:ADC?
INSTrument:COUPle:TRACking
OUTPut:[:STATe]
[SOURce[<n>]]:VOLTage:PROTection[:LEVel]
[SOURce[<n>]]:VOLTage:PROTection:DELay[:TIME]
[SOURce[<n>]]:VOLTage:PROTection:TRIPped?
SYSTem:CHANnel[:INFOrmation:PROGram?
|
5.13.28. [SOURce[<n>]]:VOLTage:PROTection[:LEVel]
|
Syntax
|
[SOURce[<n>]]:VOLTage:PROTection[:LEVel] {<voltage>}
[SOURce[<n>]]:VOLTage:PROTection[:LEVel]?
|
|
Description
|
Set the over-voltage protection (OVP) value of the channel. When [:SOURce[<n>]] or [<n>] is omitted, the currently selected channel will be affected by this command. When the over-votlage protection function of the specified channel is enabled ([SOURce[<n>]]:VOLTage:PROTection:STATe), the output turns off automatically when the output voltage exceeds the over-voltage protection value currently set.
[SOURce[<n>]]:VOLTage:PROTection:TRIPped? command can be used to query whether over-voltage protection occurred on the selected channel.
An execution error -222,"Data out of range" will be generated when output voltage is controlled internally ([SOURce[<n>]]:VOLTage:PROGram[:SOURce]) and OVP value is set below programmed output voltage ([SOURce[<n>]]:VOLTage).
|
|
Return
|
Query the over-voltage protection (OVP) value of the selected channel.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<voltage>
|
NR2|Discrete
|
0 to maximum, MIN|DEF|MAX
The maximum value is dependent on the PSU voltage rating. See Section 8.1
|
–
|
|
Usage example
|
Set voltage protection to 10.2 V on the channel 1:
SOUR1:VOLT:PROT 10.2
|
|
Errors
|
-222,"Data out of range"
|
|
Related Commands
|
*SAV
OUTPut:PROTection:COUPle
[SOURce[<n>]]:VOLTage
[SOURce[<n>]]:VOLTage:PROGram[:SOURce]
[SOURce[<n>]]:VOLTage:PROTection:TRIPped?
[SOURce[<n>]]:VOLTage:PROTection:STATe
|
5.13.29. [SOURce[<n>]]:VOLTage:PROTection:DELay[:TIME]
|
Syntax
|
[SOURce[<n>]]:VOLTage:PROTection:DELay[:TIME] {<time>}
[SOURce[<n>]]:VOLTage:PROTection:DELay[:TIME]? [<query time>]
|
|
Description
|
This command sets the over-voltage protection delay. The over-voltage protection function will not be triggered on the selected output channel during the delay time. After the delay time has expired, the over-voltage protection function will be active.
This prevents momentary changes in output status from triggering the over-voltage protection function. Programmed values can range from 0 to 10 seconds. See also Section 8.1
|
|
Return
|
The query command returns the programmed delay time.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<time>
|
NR2|Discrete
|
0 – 10|DEFault
|
5 ms
|
|
|
<query time>
|
Discrete
|
DEFault
|
–
|
|
Usage example
|
Get default OVP delay of 50 milliseconds:
VOLT:PROT:DEL? DEF
0.050
|
|
Related Commands
|
*SAV
OUTPut:PROTection:CLEar
|
5.13.30. [SOURce[<n>]]:VOLTage:PROTection:STATe
|
Syntax
|
[SOURce[<n>]]:VOLTage:PROTection:STATe {<bool>}
[SOURce[<n>]]:VOLTage:PROTection:STATe?
|
|
Description
|
This command enables or disables the over-voltage protection (OVP) function. The enabled state is ON (1); the disabled state is OFF (0).
Since the PSU do not have a dedicated over-voltage protection circuit that can be programmed independently of output current level, entering the CV (constant voltage) mode of operation is used as a trigger to start OVP sequence. When delay time specified with the [SOURce[<n>]]:VOLTage:PROTection:DELay[:TIME] command expired the output turns off and the Questionable Condition status register OCP bit 8 is set. An error tone will also follow if beeper is enabled (see SYSTem:BEEPer:STATe).
[SOURce[<n>]]:VOLTage:PROTection:TRIPped? command can be used to query whether over-voltage protection occurred on the selected channel.
|
|
Return
|
The query command returns 0 if the voltage protection state is OFF, and 1 if the voltage protection state is ON.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Usage example
|
VOLT:PROT:STAT?
0
|
|
Related Commands
|
*SAV
OUTPut:PROTection:CLEar
[SOURce[<n>]]:VOLTage:PROTection:DELay[:TIME]
[SOURce[<n>]]:VOLTage:PROTection:TRIPped
SYSTem:BEEPer:STATe
|
5.13.31. [SOURce[<n>]]:VOLTage:PROTection:TRIPped?
|
Syntax
|
[SOURce[<n>]]:VOLTage:PROTection:TRIPped?
|
|
Description
|
Query whether OVP occurred on the currently selected channel. When protection is tripped bit 8 (OVP) of the Questionable Instrument Isummary register will be set (see Section 3.4.2).
When channel’s output voltage is controlled remotely ([SOURce[<n>]]:VOLTage:PROGram[:SOURce]) this protection will change voltage control back to INTernal source.
The OUTPut:PROTection:CLEar command can be send to clear OVP condition on the selected channel.
|
|
Return
|
This query returns a 1 if the protection circuit is tripped and a 0 if it is untripped.
|
|
Usage example
|
VOLT:PROT:TRIP?
0
VOLT:PROG?
0
|
|
Related Commands
|
OUTPut:PROTection:CLEar
[SOURce[<n>]]:VOLTage:PROGram[:SOURce]
|
5.13.32. [SOURce[<n>]]:VOLTage:SENSe[:SOURce]
|
Syntax
|
[SOURce[<n>]]:VOLTage:SENSe[:SOURce] {<source>}
[SOURce[<n>]]:VOLTage:SENSe[:SOURce]?
|
|
Description
|
This command enables or disables remote sensing. The enabled state is EXTernal (1); the disabled state is INTernal (0). Execution of this command also affects bit 12 (RSENSE) of the Operation Instrument Isummary register (see Section 3.3.2).
Self-test operation initiated by *TST? command will put remote sense on all PSU channels into disable state.
When the BP_OPTION is enabled and the channels are not coupled together (INSTrument:COUPle:TRACking) this command sets LED indicators above binding posts and sense relays in the following manner:
- Turn on/off Sense1 indicator (LED_S1) and sense relay K_S1 when CH1 is selected
- Turn on/off Sense2 indicators (LED_S2) and sense relay K_S2 when CH2 is selected
Remote sensing has no effect during CC (Constant Current) operation. Sense+/Sense- indicators (LED_S1, LED_S2) will not be affected if output state is off (OUTPut OFF command).
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<source>
|
Discrete
|
INTernal|EXTernal
|
INTernal
|
|
Return
|
The query command returns 0 if the internal sense is selected, and 1 if the remote (external) sense is selected.
|
|
Usage example
|
VOLT:SENS EXT
VOLT:SENS?
1
|
|
Errors
|
-241,"Hardware missing"
312,"Cannot execute when the channels are coupled"
|
|
Related Commands
|
*SAV
*TST
INSTrument:COUPle:TRACking
OUTPut:[:STATe]
SYSTem:CHANnel[:INFOrmation]:PROGram?
|
5.13.33. [SOURce[<n>]]:VOLTage:SLEW:FALLing
Not implemented yet
5.13.34. [SOURce[<n>]]:VOLTage:SLEW:RISing
Not implemented yet
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.14 - STATus.html
================================================
5.14. STATus
Status register programming lets you determine the operating condition of the instrument at any time.
This subsystem controls the SCPI-defined status-reporting structures. SCPI defines, in addition to those in IEEE 488.2, QUEStionable, OPERation, Instrument SUMmary and INSTrument registers. These registers conform to the IEEE 488.2 specification and each may be comprised of a condition register, an event register, an enable register. The purpose and definition of the SCPI-defined registers is described in "Volume 1: Syntax and Style". SCPI also defines an IEEE 488.2 queue for status. The queue provides a human readable record of instrument events. The application programmer may individually enable events into the queue.
STATus:PRESet enables errors and disables all other events.
|
|
|
|
STATus
|
|
|
:OPERation
|
|
|
[:EVENt]?
|
Returns the value of the Operation Event register
|
|
:CONDition?
|
Returns the value of the Operation Instrument Condition register
|
|
:ENABle {<value>}
|
Enables specific bits in the Operation Event register
|
|
:INSTrument[<n>]
|
|
|
[:EVENt]?
|
Returns the value of the Operation Instrument Event register
|
|
:CONDition?
|
Returns the value of the Operation Instrument Condition register
|
|
:ENABle {<value>}
|
Enables specific bits in the Operation Instrument Event register
|
|
:ISUMmary<n>
|
|
|
[:EVENt]?
|
Returns the value of the Operation Instrument Isummary Event register
|
|
:CONDition?
|
Returns the value of the Operation Instrument Isummary Condition register
|
|
:ENABle {<value>}
|
Enables specific bits in the Operation Instrument Isummary Event register
|
|
:PREset
|
Presets all enable registers to power-on state
|
|
:QUEStionable
|
|
|
[:EVENt]?
|
Returns the value of the Questionable Event register
|
|
:CONDition?
|
Returns the value of the Questionable Condition register
|
|
:ENABle {<value>}
|
Enables specific bits in the Questionable Event register
|
|
:INSTrument[<n>]
|
|
|
[:EVENt]?
|
Returns the value of the Questionable Instrument Event register
|
|
:CONDition?
|
Returns the value of the Questionable Instrument Condition register
|
|
:ENABle {<value>}
|
Enables specific bits in the Questionable Instrument Event register
|
|
:ISUMmary<n>
|
|
|
[:EVENt]?
|
Returns the value of the Questionable Instrument Isummary Event register
|
|
:CONDition?
|
Returns the value of the Questionable Instrument Isummary Condition register
|
|
:ENABle {<value>}
|
Enables specific bits in the Questionable Instrument Isummary Event register
|
5.14.1. STATus:OPERation[:EVENt]?
|
Syntax
|
STATus:OPERation[:EVENt]?
|
|
Description
|
This query returns the value of the read-only Operation Status Event register The bits are latched and reading the register will clear it. The *CLS command can be also used to clear the register.
|
|
Return
|
The value returned is the binary-weighted sum of all bits set in the register. For example, if bit 9 (decimal value = 512) and bit 13 (decimal value = 8192) are set, this command will return 8704. See table in the Section 3.3 for bits description.
|
|
Usage example
|
If GROUp PARallel (bit 8) is set (next query returns 0 since the first query clears the event register):
STAT:OPER?
256
STAT:OPER?
0
|
|
Errors
|
|
|
Related Commands
|
*CLS
*STB?
STATus:OPERation:ENABle
|
5.14.2. STATus:OPERation:CONDition?
|
Syntax
|
STATus:OPERation:CONDition?
|
|
Description
|
This query returns the value of the read-only Operation Status Condition register.
|
|
Return
|
The value returned is the binary-weighted sum of all bits set in the register. For example, if bit 9 (decimal value = 512) and bit 13 (decimal value = 8192) are set, this command will return 8704. See table in the Section 3.3 for bits description.
|
|
Usage example
|
If GROUp PARallel (bit 8) is set:
STAT:OPER:COND?
256
|
|
Errors
|
|
|
Related Commands
|
STATus:OPERation:ENABle
|
5.14.3. STATus:OPERation:ENABle
|
Syntax
|
STATus:OPERation:ENABle {<value>}
STATus:OPERation:ENABle?
|
|
Description
|
This command and its query set and read the value of the Operation Status Enable register. The Enable register is a mask for enabling specific bits from the Operation Event register to set the operation summary bit 7 (OPER) of the Status Byte register. This bit is the logical OR of all the Operational Event register bits that are enabled by the Operation Status Enable register.
|
|
Return
|
Query the Operation Status Enable register. The PSU returns a binary-weighted decimal representing the bits set in the enable register.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<value>
|
NR1
|
A decimal value which corresponds to the binary-weighted sum of the bits in the register (see the table in Section 3.3)
|
PREset=0
|
|
Usage example
|
Enable ISUM (bit 13):
STAT:OPER:ENAB 8192
|
|
Errors
|
|
|
Related Commands
|
*CLS
*STB?
STATus:OPERation[:EVENt]?
|
5.14.4. STATus:OPERation:INSTrument[:EVENt]?
|
Syntax
|
STATus:OPERation:INSTrument[:EVENt]?
|
|
Description
|
This query returns the value of the read-only Instrument Operation Status Event register. The bits are latched and reading the register will clear it. The *CLS command can be also used to clear the register.
|
|
Return
|
The value returned is the binary-weighted sum of all bits set in the register. For example, if bit 1 (decimal value = 2) and bit 2 (decimal value = 4) are set, this command will return 6. See table in the Section 3.3.1 for bits description.
|
|
Usage example
|
If bit 2 (INST2) is set:
STAT:OPER:INST?
4
|
|
Errors
|
|
|
Related Commands
|
*CLS
STATus:PREset
|
5.14.5. STATus:OPERation:INSTrument:CONDition?
|
Syntax
|
STATus:OPERation:INSTrument:CONDition?
|
|
Description
|
This query returns the value of the read-only Instrument Operation Status Condition register.
|
|
Return
|
The value returned is the binary-weighted sum of all bits set in the register. For example, if bit 1 (decimal value = 2) and bit 2 (decimal value = 4) are set, this command will return 6. See table in the Section 3.3.1 for bits description.
|
|
Usage example
|
If bit 2 (INST2) is set:
STAT:OPER:INST:COND?
4
|
|
Errors
|
|
|
Related Commands
|
STATus:PREset
|
5.14.6. STATus:OPERation:INSTrument:ENABle
|
Syntax
|
STATus:OPERation:INSTrument:ENABle {<value>}
STATus:OPERation:INSTrument:ENABle?
|
|
Description
|
Enable bits in the Instrument Operation Status Enable register. The selected bits are then reported to the Operation Status Event register.
|
|
Return
|
Query the Instrument Operation Status Enable register. The PSU returns a binary-weighted decimal representing the bits set in the enable register.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<value>
|
NR1
|
A decimal value which corresponds to the binary-weighted sum of the bits in the register (see the table in Section 3.3.1)
|
PREset=0
|
|
Usage example
|
Enable INST1 (bit 1) and INST2 (bit 2):
STAT:OPER:INST:ENAB 6
|
|
Errors
|
|
|
Related Commands
|
*CLS
STATus:PREset
|
5.14.7. STATus:OPERation:INSTrument:ISUMmary[<n>][:EVENt]?
|
Syntax
|
STATus:OPERation:INSTrument:ISUMmary[<n>][:EVENt]?
|
|
Description
|
This query returns the value of the read-only Instrument Isummary Operation Status Event register for a specific channel of the PSU represented by numeric value [<n>]. When [<n>] is omitted, the system queries the Instrument Isummary Operation Status Event register of the current channel. The bits are latched and reading the register will clear it. The *CLS command can be also used to clear the register.
|
|
Return
|
The value returned is the binary-weighted sum of all bits set in the register. See table in the Section 3.3.2 for bits description.
|
|
Usage example
|
If bit 8 (CV1) and bit 10 (OE1) on the channel 1 are set (256+1024=1280):
STAT:OPER:INST:ISUM1?
1280
|
|
Errors
|
|
|
Related Commands
|
*CLS
OUTPut:MODE?
|
5.14.8. STATus:OPERation:INSTrument:ISUMmary[<n>]:CONDition?
|
Syntax
|
STATus:OPERation:INSTrument:ISUMmary[<n>]:CONDition?
|
|
Description
|
This query returns the value of the read-only Instrument Isummary Operation Status Condition register for a specific channel of the PSU represented by numeric value [<n>]. When [<n>] is omitted, the system queries the Instrument Isummary Operation Status Condition register of the current channel.
|
|
Return
|
The value returned is the binary-weighted sum of all bits set in the register. See table in the Section 3.3.2 for bits description.
|
|
Usage example
|
If bit 8 (CV1) and bit 10 (OE1) on the channel 1 are set (256+1024=1280):
STAT:OPER:INST:ISUM1:COND?
1280
|
|
Errors
|
|
|
Related Commands
|
OUTPut:MODE?
|
5.14.9. STATus:OPERation:INSTrument:ISUMmary<n>:ENABle
|
Syntax
|
STATus:OPERation:INSTrument:ISUMmary[<n>]:ENABle {<value>}
STATus:OPERation:INSTrument:ISUMmary[<n>]:ENABle?
|
|
Description
|
Enable bits in the Instrument Isummary Operation Status Enable register for a specific channel of the PSU represented by numeric value [<n>]. When [<n>] is omitted, the system queries the Instrument Isummary Operation Status Enable register of the current channel. The selected bits are then reported to the Status Byte.
This command and its query set and read the value of the Operation Status Enable register. The Enable register is a mask for enabling specific bits from the Operation Event register to set the operation summary bit (OPER) of the Status Byte register. This bit (bit 7) is the logical OR of all the Operational Event register bits that are enabled by the Operation Status Enable register
|
|
Return
|
Query the Instrument Isummary Operation Status Enable register. The PSU returns a binary-weighted decimal representing the bits set in the enable register.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<value>
|
NR1
|
A decimal value which corresponds to the binary-weighted sum of the bits in the register (see the table in Section 3.3.2)
|
PREset=0
|
|
Usage example
|
The query returns that VOLT1 (bit 0), CURR1 (bit 1) and TEMP1 (bit 4) are set (1+2+16=19):
INST?
CH2
INST CH1
STAT:OPER:INST:ISUM:ENABLE?
19
|
|
Errors
|
|
|
Related Commands
|
*CLS
STATus:PREset
|
5.14.10. STATus:PREset
|
Syntax
|
STATus:PREset
|
|
Description
|
This command clears all bits in the Enable registers.
|
|
Return
|
None
|
|
Usage example
|
STAT:PRE
|
|
Errors
|
|
|
Related Commands
|
*CLS
|
5.14.11. STATus:QUEStionable[:EVENt]?
|
Syntax
|
STATus:QUEStionable[:EVENt]?
|
|
Description
|
Query the Questionable Status event register. The bits are latched and reading the register will clear it. The *CLS command can be also used to clear the register.
|
|
Return
|
The PSU returns a decimal value which corresponds to the binary-weighted sum of all bits in the register. See table in the Section 3.4 for bits description.
|
|
Usage example
|
If the error is detected in RTC (Real-time clock) circuit, the bit 3 (TIME) is set and this command returns 8:
STAT:QUES?
8
|
|
Errors
|
|
|
Related Commands
|
*CLS
|
5.14.12. STATus:QUEStionable:CONDition?
|
Syntax
|
STATus:QUEStionable:CONDition?
|
|
Description
|
Query the Questionable Status condition register.
|
|
Return
|
The PSU returns a decimal value which corresponds to the binary-weighted sum of all bits in the register. See table in the Section 3.4 for bits description.
|
|
Usage example
|
If the error is detected in RTC (Real-time clock) circuit, the bit 3 (TIME) is set and this command returns 8:
STAT:QUES:COND?
8
|
|
Errors
|
|
|
Related Commands
|
|
5.14.13. STATus:QUEStionable:ENABle
|
Syntax
|
STATus:QUEStionable:ENABle {<value>}
STATus:QUEStionable:ENABle?
|
|
Description
|
Enable bits in the Questionable Status Enable register. The selected bits are then reported to the Status Byte.
When <enable value> is set to 0, executing this command will clear the Questionable Status Enable register.
|
|
Return
|
Query the Questionable Status Enable register. The PSU returns a binary-weighted decimal representing the bits set in the enable register.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<value>
|
NR1
|
A decimal value which corresponds to the binary-weighted sum of the bits in the register (see table in Section 3.4)
|
PREset=0
|
|
Usage example
|
The query returns that TIME (bit 3), TEMPerature (bit 4) and ISUM (bit 13) are enabled (8+16+8192=8216):
STAT:QUES:ENAB?
8216
|
|
Errors
|
|
|
Related Commands
|
*CLS
STATus:PREset
|
5.14.14. STATus:QUEStionable:INSTrument[:EVENt]?
|
Syntax
|
STATus:QUEStionable:INSTrument[:EVENt]?
|
|
Description
|
Query the questionable instrument event register. The bits are latched and reading the register will clear it. The *CLS command can be also used to clear the register.
|
|
Return
|
The PSU returns a decimal value which corresponds to the binary-weighted sum of all bits in the register and clears the register. See table in the Section 3.4.1 for bits description.
|
|
Usage example
|
Result of the query when INST1 (bit 1) and INST2 (bit 2) are set (2+4=6):
STAT:QUES:INST?
6
|
|
Errors
|
|
|
Related Commands
|
*CLS
|
5.14.15. STATus:QUEStionable:INSTrument:CONDition?
|
Syntax
|
STATus:QUEStionable:INSTrument:CONDition?
|
|
Description
|
Query the questionable instrument condition register.
|
|
Return
|
The PSU returns a decimal value which corresponds to the binary-weighted sum of all bits in the register and clears the register. See table in the Section 3.4.1 for bits description.
|
|
Usage example
|
Result of the query when INST1 (bit 1) and INST2 (bit 2) are set (2+4=6):
STAT:QUES:INST:COND?
6
|
|
Errors
|
|
|
Related Commands
|
|
5.14.16. STATus:QUEStionable:INSTrument:ENABle
|
Syntax
|
STATus:QUEStionable:INSTrument:ENABle {<value>}
STATus:QUEStionable:INSTrument:ENABle?
|
|
Description
|
Set the value of the questionable instrument enable register. This register is a mask for enabling specific bits from the questionable instrument event register to set the instrument summary bit 13 (ISUM) of the Questionable Status register. The ISUM bit of the Questionable Status register is the logical OR of all the questionable instrument event register bits that are enabled by the questionable instrument enable register.
|
|
Return
|
Query the Questionable Instrument Enable register. The PSU returns a binary-weighted decimal representing the bits set in the enable register.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<value>
|
NR1
|
A decimal value which corresponds to the binary-weighted sum of the bits in the register (see table in Section 3.4.1)
|
PREset=0
|
|
Usage example
|
Set INST1 (bit 1) and INST2 (bit 2):
STAT:QUES:INST:ENAB 6
|
|
Errors
|
|
|
Related Commands
|
*CLS
|
5.14.17. STATus:QUEStionable:INSTrument:ISUMmary[<n>][:EVENt]?
|
Syntax
|
STATus:QUEStionable:INSTrument:ISUMmary[<n>][:EVENt]?
|
|
Description
|
Return the value of the Questionable Instrument Isummary Event register for a specific channel of the PSU represented by numeric value [<n>]. When [<n>] is omitted, the system queries the questionable instrument Isummary enable register of the current channel. The event register is a read-only register which holds (latches) all events. Reading the Questionable Instrument Isummary Event register clears it. The *CLS command can be also used to clear the register.
When the PSU is operating as a voltage source, bit 1 (CURRent) is set. When the PSU is operating as a current source, bit 0 (VOLTage) is set. When the output is unregulated (UR), both bits are set (for example, while the output is changing to a new programmed value or when the PSU is sinking instead of sourcing because down-programmer is active with battery with higher voltage then set output is connected).
|
|
Return
|
The PSU returns a binary-weighted decimal representing the bits set in the enable register. See table in the Section 3.4.2 for bits description.
|
|
Usage example
|
Result of the query when over-current protection (OCP) condition is detected (bit 9):
STAT:QUES:INST:ISUM1?
512
|
|
Errors
|
|
|
Related Commands
|
*CLS
|
5.14.18. STATus:QUEStionable:INSTrument:ISUMmary[<n>]:CONDition?
|
Syntax
|
STATus:QUEStionable:INSTrument:ISUMmary[<n>]:CONDition?
|
|
Description
|
Return the value of the Questionable Instrument Isummary Condition register for a specific channel of the PSU represented by numeric value [<n>]. When [<n>] is omitted, the system queries the questionable instrument Isummary enable register of the current channel.
When the PSU is operating as a voltage source, bit 1 (CURRent) is set. When the PSU is operating as a current source, bit 0 (VOLTage) is set. When the output is unregulated (UR), both bits are set (for example, while the output is changing to a new programmed value or when the PSU is sinking instead of sourcing because down-programmer is active with battery with higher voltage then set output is connected).
|
|
Return
|
The PSU returns a binary-weighted decimal representing the bits set in the enable register. See table in the Section 3.4.2 for bits description.
|
|
Usage example
|
Result of the query when over-current protection (OCP) condition is detected (bit 9):
STAT:QUES:INST:ISUM1:COND?
512
|
|
Errors
|
|
|
Related Commands
|
|
5.14.19. STATus:QUEStionable:INSTrument:ISUMmary[<n>]:ENABle
|
Syntax
|
STATus:QUEStionable:INSTrument:ISUMmary[<n>]:ENABle {<value>}
STATus:QUEStionable:INSTrument:ISUMmary[<n>]:ENABle?
|
|
Description
|
Set the value of the Questionable Instrument Isummary Enable register for a specific channel of the PSU represented by numeric value [<n>]. When [<n>] is omitted, the system queries the Questionable Instrument Isummary Enable register of the current channel. The *CLS command can be used to clear the register.
This register is a mask for enabling specific bits from the Questionable Instrument Isummary Event register to set the Instrument Summary bit (bits 1 and 2) of the Questionable Instrument register. These bits are the logical OR of all the Questionable Instrument Isummary Event register bits that are enabled by the Questionable Instrument Isummary Enable register.
|
|
Return
|
Query the value of the Questionable Instrument Isummary Enable register.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<value>
|
NR1
|
A decimal value which corresponds to the binary-weighted sum of the bits in the register (see table in Section 3.4.2)
|
PREset=0
|
|
Usage example
|
Enable bits for all events on channel 2 – VOLT2 (bit 0, value=1), CURR (bit 1, decimal value=2), TEMP2 (bit 4, value 16), OVP1 (bit 8, value=256), OCP2 (bit 9, value=512), OPP2 (bit 10, value=1024), therefore the enable value is 1+2+16+256+512+1024=1811:
STAT:QUES:INST:ISUM2:ENAB 1811
|
|
Errors
|
|
|
Related Commands
|
*CLS
STATus:PREset
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.15 - SYSTem.html
================================================
5.15. SYSTem
System commands control system functions that are not directly related to output control, measurement, or status functions.
|
|
|
|
SYSTem
|
|
|
:BEEPer[:IMMediate]
|
Issues a single beep immediately
|
|
:KEY
|
|
|
:STATe {<bool>}
|
Enables click tone for local control
|
|
:STATe {<bool>}
|
Enables beeper function
|
|
:CAPability?
|
Returns an <instrument_specifier>
|
|
:CHANnel
|
|
|
[:COUNt]?
|
Returns the number of output channels
|
|
:INFOrmation
|
|
|
:AHOur
|
|
|
TOTal?
|
Returns channel’s total delivered energy in Ah
|
|
:CURRent?
|
Returns output current capability
|
|
:ONTime
|
|
|
LAST?
|
Returns time passed after last output enable
|
|
TOTal?
|
Returns channel’s total active time
|
|
:POWer?
|
Returns output power capability
|
|
:PROGram?
|
Returns programmable features of the channel
|
|
:VOLTage?
|
Returns output voltage capability
|
|
:WHOur
|
|
|
:TOTal?
|
Returns channel’s total delivered energy in Wh
|
|
:MODel?
|
Returns the channel model identification
|
|
:COMMunicate
|
|
|
:ENABle {<bool>}, {<interface>}
|
Enables the remote interface
|
|
:ETHernet
|
|
|
:ADDRess {<ip_address>}
|
Sets the static LAN (IP) address
|
|
:CONTrol?
|
Returns the control connection port
|
|
:DHCP {<bool>}
|
Enables the use of the Dynamic Host Configuration Protocol (DHCP)
|
|
:DNS <ip_address>
|
Sets the IP address of the DNS server.
|
|
:GATEway {<ip_address>}
|
Sets the IP address of the default gateway
|
|
:MAC?
|
Returns the MAC address
|
|
:PORT {<number>}
|
Sets the port number
|
|
:SMASk {<mask>}
|
Sets the static subnet mask
|
|
:NTP {<server>}
|
Set s NTP service server address
|
|
:RLSTate {<state>}
|
Places the instrument in remote or local mode
|
|
:SERial
|
|
|
:BAUD {<speed>}
|
Sets the baud rate (speed)
|
|
:PARity {<parity>}
|
Sets the parity mode
|
|
:CPU
|
|
|
:INFOrmation
|
|
|
:ETHernet
|
|
|
:TYPE?
|
Returns the type of Ethernet controller
|
|
:ONtime
|
|
|
LAST?
|
Returns time passed after last power on
|
|
TOTal?
|
Returns PSU’s total active time
|
|
:TYPE?
|
Returns the type of CPU
|
|
:MODel?
|
Returns the control board model identification
|
|
:OPTion?
|
Returns information about installed options on the control board
|
|
:DATE {<year>}, {<month>}, {<day>}
|
Sets the date of the system clock
|
|
:DIGital
|
|
|
:INPut:DATA? {<pin>}
|
Reads the state of the digital port pins
|
|
:OUTPut:DATA {<pin>}, {<state>}
|
Sets the state of the digital port pins
|
|
:PIN<n>
|
|
|
:FUNCtion {<function>}
|
Sets the selected pin’s function
|
|
:POLarity {<polarity>}
|
Sets the selected pin’s polarity
|
|
:ERRor
|
|
|
[:NEXT]?
|
Queries and clears errors from the error queue
|
|
:COUNt?
|
Queries the error/event queue for the number of unread items
|
|
:INHibit?
|
Queries system inhibit state
|
|
:KLOCk
|
Disables front panel [lock/unlock] icon
|
|
:LOCal
|
Places the PSU in the local mode
|
|
:PASSword
|
|
|
:CALibration
|
|
|
:RESet
|
Resets the calibration password to initial value
|
|
:FPANel
|
|
|
:RESet
|
Resets the front panel lock password to initial value
|
|
:NEW {<old>}, {<new>}
|
Changes system password
|
|
:PON:OUTPut:DISable {<bool>}
|
Sets output state on power up
|
|
:POWer {<bool>}
|
Enters the PSU into the Stand-by mode
|
|
:PROTection:TRIP {<bool>}
|
Enters the PSU into the Stand-by mode in case of protection trip
|
|
:REMote
|
Places the PSU in the remote mode
|
|
:RWLock
|
Places the PSU in the remote mode and disables front panel [lock/unlock] icon
|
|
:TEMPerature
|
|
|
:PROTection
|
|
|
[:HIGH]
|
|
|
[:LEVel] {<temperature>} [, <sensor>]
|
Sets the OTP value
|
|
:CLEar {<sensor>}
|
Clears the latched protection status of the over-temperature protection (OTP)
|
|
:DELay
|
|
|
[:TIME] {<delay>} [, <sensor>]
|
Sets the OTP programming delay
|
|
:STATe {<bool>} [, <sensor>]
|
Enables/disables OTP on the selected temperature sensor
|
|
:TRIPped? [<sensor>]
|
Returns status of OTP activation
|
|
:TIME {<hours>}, {<minutes>}, {<seconds>}
|
Sets the time of the system clock
|
|
:DTS {rules}
|
Defines daylight saving time (DST) rules
|
|
:ZONE {zone}
|
Defines time zone
|
|
:VERSion?
|
Returns the SCPI version number
|
5.15.1. SYSTem:BEEPer
|
Syntax
|
SYSTem:BEEPer[:IMMediate]
|
|
Description
|
This command issues a single beep immediately.
|
|
Usage example
|
SYST:BEEP
|
5.15.2. SYSTem:BEEPer:KEY:STATe
|
Syntax
|
SYSTem:BEEPer:KEY:STATe {<bool>}
SYSTem:BEEPer:KEY:STATe?
|
|
Description
|
Use this command to enable or disable generation of audiable “click” sound when front panel option is selected.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Usage example
|
SYST:BEEP:KEY:STAT ON
|
|
Related Commands
|
SYSTem:BEEPer[:IMMediate]
SYSTem:BEEPer:STATe
|
5.15.3. SYSTem:BEEPer:STATe
|
Syntax
|
SYSTem:BEEPer:STATe {<bool>}
SYSTem:BEEPer:STATe?
|
|
Description
|
When the beeper is enabled, the PSU generates audible sound in any of the following situations:
- the power is turns on or off (see SYSTem:POWer),
- when error occurs during front panel operation or remote operation (see Section 7 for the list of error messages),
- self-test is failed and
- any of the protection function is “tripped”
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
ON
|
|
Usage example
|
SYST:BEEP:STAT ON
SYST:BEEP:STAT?
1
|
|
Related Commands
|
SYSTem:BEEPer[:IMMediate]
SYSTem:POWer
|
5.15.4. SYSTem:CAPability?
|
Syntax
|
SYSTem:CAPability?
|
|
Description
|
This query returns the PSU’s capabilities and outputs the appropriate specifiers.
See also SCPI Volume 4: Section 7.1, 1.4.1, 7.2.1, 7.2.2, and 7.2.3
|
|
Usage example
|
SYSTem:CAPability?
DCSUPPLY WITH (MEASURE|MULTIPLE|TRIGGER)
|
5.15.5. SYSTem:CHANnel[:COUNt]?
|
Syntax
|
SYSTem:CHANnel[:COUNt]?
|
|
Description
|
This query returns the number of output channels in a mainframe.
|
|
Usage example
|
SYSTem:CHANnel?
2
|
|
Related Commands
|
INSTrument[:SELect]
INSTrument:NSELect
|
5.15.6. SYSTem:CHANnel:INFOrmation:AHOur:TOTal?
|
Syntax
|
SYSTem:CHANnel:INFOrmation:AHOur:TOTal? [<channel>]
|
|
Description
|
This query returns total delivered energy in amp-hours (Ah) of the currently selected channel. This information is stored every 10 minutes in non-volatile memory. Therefore it’s possible that up to the last 10 minutes of calculated energy is lost after restart caused with power outage or system reset.
Energy specified in amp-hours can be easily converted into e.g. Coulumbs (1 Ah = 3600 C).
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SYST:CHAN:INFO:AHO:TOT? CH1
1344.35
|
|
Related commands
|
FETCh:AHOur?
FETCh:WHOur?
SENSe:AHOur:RESet
SYSTem:CHANnel:INFOrmation:WHOur:TOTal?
|
5.15.7. SYSTem:CHANnel:INFOrmation:CURRent?
|
Syntax
|
SYSTem:CHANnel:INFOrmation:CURRent? [<channel>]
|
|
Description
|
Use this query to get currently selected channel output current capability.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SYST:CHAN:INFO:CURR? CH2
5.00
|
5.15.8. SYSTem:CHANnel:INFOrmation:ONTime:LAST?
|
Syntax
|
SYSTem:CHANnel:INFOrmation:ONTime:LAST? [<channel>]
|
|
Description
|
This query returns time passed after last activation of the currently selected channel. Resolution is 1 minute and this information is stored every 10 minutes in non-volatile memory. Therefore it’s possible that up to 10 minutes is lost after restart caused with power outage or system reset.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SYST:CHAN:INFO:ONT:LAST?
15m
|
5.15.9. SYSTem:CHANnel:INFOrmation:ONTime:TOTal?
|
Syntax
|
SYSTem:CHANnel:INFOrmation:ONTime:TOTal? [<channel>]
|
|
Description
|
This query returns total active time of the currently selected channel. Resolution is 1 minute and this information is stored every 10 minutes in non-volatile memory. Therefore it’s possible that up to 10 minutes is lost after restart caused with power outage or system reset.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SYST:CHAN:INFO:ONT:TOT?
1h 45m
|
5.15.10. SYSTem:CHANnel:INFOrmation:POWer?
|
Syntax
|
SYSTem:CHANnel:INFOrmation:POWer? [<channel>]
|
|
Description
|
Use this query to get currently selected channel output power capability.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SYST:CHAN:INFO:POW?
160.00
|
5.15.11. SYSTem:CHANnel:INFOrmation:PROGram?
|
Syntax
|
SYSTem:CHANnel:INFOrmation:PROGram? [<channel>]
|
|
Description
|
This query returns names of all channel board functionality that can be controlled by firmware. Depending of the board model (see the SYSTem:CHANnel:MODel? query) various combination of the following features can be returned:
- Volt – program the output voltage while channel is in the CV mode of operation (see [SOURce[<n>]]:VOLTage and APPLy commands)
- Current – program the output current while channel is in the CC mode of operation (see [SOURce[<n>]]:CURRent and APPLy commands)
- Power – set max. allowed output power regardless of the channel mode of operation (see [SOURce[<n>]]:POWer:LIMit)
- OE – set channel power output (see OUTPut[:STATe])
- Dprog – control down-programmer circuit (see OUTPut:DPRog)
- LRipple – set low power mode of operation when SMPS pre-regulator is switched off (see OUTPut:LRIPple)
- Rprog – control output voltage programming source (see [SOURce[<n>]]:VOLTage:PROGram[:SOURce])
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SYST:CHAN:INFO:PROG? CH1
"Volt", "Current", "Power", "OE", "DProg", "LRipple", "Rprog"
|
|
Related Commands
|
APPLy
OUTPut:DPRog
OUTPut:MODE?
OUTPut[:STATe]
OUTPut:LRIPple
[SOURce[<n>]]:CURRent
[SOURce[<n>]]:POWer:LIMit
[SOURce[<n>]]:VOLTage
[SOURce[<n>]]:VOLTage:PROGram[:SOURce])
SYSTem:CHANnel:MODel?
|
5.15.12. SYSTem:CHANnel:INFOrmation:VOLTage?
|
Syntax
|
SYSTem:CHANnel:INFOrmation:VOLTage? [<channel>]
|
|
Description
|
Use this query to get currently selected channel output voltage capability.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SYST:CHAN:INFO:VOLT?
40.00
|
5.15.13. SYSTem:CHANnel:INFOrmation:WHOur:TOTal?
|
Syntax
|
SYSTem:CHANnel:INFOrmation:WHOur:TOTal? [<channel>]
|
|
Description
|
This query returns total delivered energy in watt-hours (Wh) of the currently selected channel. This information is stored every 10 minutes in non-volatile memory. Therefore it’s possible that up to the last 10 minutes of calculated energy is lost after restart caused with power outage or system reset.
Energy specified in watt-hours can be easily converted into e.g. Joules (1 Wh = 3600 J).
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SYST:CHAN:INFO:WHO:TOT? CH1
2044.15
|
|
Related commands
|
FETCh:AHOur?
FETCh:WHOur?
SENSe:WHOur:RESet
SYSTem:CHANnel:INFOrmation:AHOur:TOTal?
|
5.15.14. SYSTem:CHANnel:MODel?
|
Syntax
|
SYSTem:CHANnel:MODel? [<channel>]
|
|
Description
|
This query returns the model identification string of the specified channel.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SYST:CHAN:MOD?
"Power_r5B12"
|
|
Related Commands
|
SYSTem:CPU:MODel?
|
5.15.15. SYSTem:COMMunicate:ENABle
|
Syntax
|
SYSTem:COMMunicate:ENABle {<bool>}, {<interface>}
SYSTem:COMMunicate:ENABle? {<interface>}
|
|
Description
|
Enables or disables the remote interface Serial (via USB), Ethernet, NTP service, or the remote service Sockets. The setting is effective after rebooting the PSU. This command setting is not changed by power off or the *RST command.
Remote service Sockets is not supported yet
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
–
|
|
<interface>
|
Discrete
|
SERial|ETHernet|NTP|SOCKets
|
–
|
|
Return
|
This query returns the status of the selected interface that could be 0 (OFF) or 1 (ON).
|
|
Usage example
|
SYST:COMM:ENAB 1, ETH
SYST:COMM:ENAB 0, SER
|
5.15.16. SYSTem:COMMunicate:ETHernet:ADDRess
|
Syntax
|
SYSTem:COMMunicate:ETHernet:ADDRess {<ip_address>}
SYSTem:COMMunicate:ETHernet:ADDRess?
|
|
Description
|
Set the IP address of the system manually if the DHCP mode is not enabled. If the DHCP mode is enabled setting the IP address using this command will be ignored.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<ip_address>
|
Quoted string
|
15 characters max. formatted as four groups of up to 3 digits (range 0–255), separated by “.”
|
–
|
|
Return
|
The query returns the current IP address sets manually or assigned by the DHCP server.
|
|
Usage example
|
SYST:COMM:ETH:ADDR?
"192.168.10.100"
|
|
Related Commands
|
SYSTem:COMMunicate:ETHernet:DHCP
|
5.15.17. SYSTem:COMMunicate:ETHernet:DHCP
|
Syntax
|
SYSTem:COMMunicate:ETHernet:DHCP {<bool>}
SYSTem:COMMunicate:ETHernet:DHCP?
|
|
Description
|
Enable or disable the DHCP mode. In DHCP mode, the DHCP server in the current network assigns network parameters (IP ADdress, DNS address, GATEway address and the Subnet MASk) for the PSU.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
ON
|
|
Return
|
Query the status of the DHCP mode.
|
|
Usage example
|
SYST:COMM:ETH:DHCP?
1
|
5.15.18. SYSTem:COMMunicate:ETHernet:DNS
|
Syntax
|
SYSTem:COMMunicate:ETHernet:DNS {<ip_address>}
SYSTem:COMMunicate:ETHernet:DNS?
|
|
Description
|
Set the DNS (Domain Name Service) address if the DHCP mode is not enabled. If the DHCP mode is enabled setting the DNS address using this command will be ignored.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<ip_address>
|
Quoted string
|
15 characters max. formatted as four groups of up to 3 digits (range 0–255), separated by “.”
|
–
|
|
Return
|
The query returns the DNS address sets manually or assigned by the DHCP server.
If DHCP is used query will return “unknown”.
|
|
Usage example
|
SYST:COMM:ETH:DNS "192.168.1.200"
|
|
Related Commands
|
SYSTem:COMMunicate:ETHernet:DHCP
|
5.15.19. SYSTem:COMMunicate:ETHernet:GATEway
|
Syntax
|
SYSTem:COMMunicate:ETHernet:GATEway {<ip_address>}
SYSTem:COMMunicate:ETHernet:GATEway?
|
|
Description
|
Set the network gateway address if the DHCP mode is not enabled. If the DHCP mode is enabled setting the network gateway address using this command will be ignored.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<ip_address>
|
Quoted string
|
15 characters max. formatted as four groups of up to 3 digits (range 0–255), separated by “.”
|
–
|
|
Return
|
The query returns the network gateway address sets manually or assigned by the DHCP server. If DHCP is used query will return “unknown”.
|
|
Usage example
|
SYST:COMM:ETH:GATE?
"192.168.10.1"
|
|
Related Commands
|
SYSTem:COMMunicate:ETHernet:DHCP
|
5.15.20. SYSTem:COMMunicate:ETHernet:MAC
|
Syntax
|
SYSTem:COMMunicate:ETHernet:MAC {<mac_address>}
SYSTem:COMMunicate:ETHernet:MAC?
|
|
Description
|
Use this command to set Ethernet controller IC (W5500) MAC. You can set any combination of six hexadecimal values separated by “-”. Ethernet will work as long as two different machine in the LAN don't have the same MAC address.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<mac_address>
|
Quoted string
|
17 characters formatted as six groups of 2 digits separated by “-”
|
74-69-69-2D-30-00
|
|
Return
|
The query returns the MAC address as a quoted string (six hexadecimal values separated by “-”).
|
|
Usage example
|
SYST:COMM:ETH:MAC?
"70-60-50-40-30-20"
|
5.15.21. SYSTem:COMMunicate:ETHernet:PORT
|
Syntax
|
SYSTem:COMMunicate:ETHernet:PORT {<number>}
SYSTem:COMMunicate:ETHernet:PORT?
|
|
Description
|
Use this command to change default (5025) Ethernet communication port for SCPI.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<number>
|
NR1
|
1-65535
|
5025
|
|
Return
|
The query returns the Ethernet communication port number.
|
|
Usage example
|
SYST:COMM:ETH:PORT?
5025
|
|
Related Commands
|
SYSTem:COMMunicate:ENABle
SYSTem:COMMunicate:ETHernet:CONTrol?
|
5.15.22. SYSTem:COMMunicate:ETHernet:SMASk
|
Syntax
|
SYSTem:COMMunicate:ETHernet:SMASk {<mask>}
SYSTem:COMMunicate:ETHernet:SMASk?
|
|
Description
|
Set the subnet mask if the DHCP mode is not enabled. If the DHCP mode is enabled setting the network gateway address using this command will be ignored.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<mask>
|
Quoted string
|
15 characters max. formatted as four groups of up to 3 digits (range 0–255), separated by “.”
|
–
|
|
Return
|
The query returns the subnet mask sets manually or assigned by the DHCP server. If DHCP is used query will return “unknown”.
|
|
Usage example
|
SYST:COMM:ETH:SMAS "255.255.255.0"
|
|
Related Commands
|
SYSTem:COMMunicate:ETHernet:DHCP
|
5.15.23. SYSTem:COMMunicate:NTP
|
Syntax
|
SYSTem:COMMunicate:NTP {<server>}
SYSTem:COMMunicate:NTP?
|
|
Description
|
Use this command to set the NTP service server network address. The PSU will try to establish connection with selected NTP service on each power up (hard reset), when *RST is issued or once per day (24h as defined with CONF_NTP_PERIOD_SEC parameter in firmware)
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<server>
|
Quoted string
|
IP address or NTP server host name up to 32 characters
|
europe.pool.ntp.org
|
|
Return
|
The query command returns the NTP service server network address.
|
|
Usage example
|
SYST:COMM:ENAB NTP
SYST:COMM:NTP "ntp.ubuntu.com"
|
|
Related Commands
|
*RST
SYSTem:COMMunicate:ENABle
SYSTem:DATE
SYSTem:TIME
|
5.15.24. SYSTem:COMMunicate:RLSTate
|
Syntax
|
SYSTem:COMMunicate:RLSTate {<state>}
SYSTem:COMMunicate:RLSTate?
|
|
Description
|
This command configures the remote/local state of the PSU according to the following settings:
- LOCal – The PSU is set to front panel and remote interface control.
- REMote – The PSU is set to front panel and remote interface control.
- RWLock – The front panel keys are disabled. The PSU can only be controlled via the remote interface. This programmable setting is completely independent from the front panel lock/unlock function that is available from the front panel menu. If you use this command to lock the front panel, the front panel will be unlocked when AC power is cycled.
The LOCal parameter is the same as SYSTem:LOCal, the REMote parameter is the same as SYSTem:REMote, and the RWLock parameter is the same as SYSTem:RWLock.
The remote/local state is unaffected by *RST or any SCPI commands other than SYSTem:COMMunicate:RLState.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<state>
|
Discrete
|
LOCal|REMote|RWLock
|
LOCal
|
|
Return
|
The query command returns control state of the PSU that could be LOC, REM, or RWL.
|
|
Usage example
|
SYST:COMM:RLST?
"LOC"
|
|
Related Commands
|
*RST
SYSTem:LOCal
SYSTem:REMote
SYSTem:RWLock
|
5.15.25. SYSTem:COMMunicate:SERial:BAUD
|
Syntax
|
SYSTem:COMMunicate:SERial:BAUD {<speed>}
SYSTem:COMMunicate:SERial:BAUD?
|
|
Description
|
Set the baud rate of the serial (via USB) interface and the unit is Baud.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<speed>
|
NR1
|
4800|9600|19200|38400|57600|115200
|
9600
|
|
Return
|
Query the baud rate of the serial interface.
|
|
Usage example
|
SYST:COMM:SER:BAUD 38400
SYST:COMM:SER:BAUD?
38400
|
|
Related Commands
|
SYSTem:COMMunicate:ENABle
|
5.15.26. SYSTem:COMMunicate:SERial:PARity
|
Syntax
|
SYSTem:COMMunicate:SERial:PARity {<parity>}
SYSTem:COMMunicate:SERial:PARity?
|
|
Description
|
Set the parity mode of the serial (via USB) interface.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<parity>
|
Discrete
|
EVEN|MARK|NONE|ODD|SPACE
|
NONE
|
|
Return
|
Query the parity mode of the serial interface.
|
|
Usage example
|
SYST:COMM:SER:PAR?
NONE
|
|
Related Commands
|
SYSTem:COMMunicate:ENABle
|
5.15.27. SYSTem:CPU:INFOrmation:ETHernet:TYPE?
|
Syntax
|
SYSTem:CPU:INFOrmation:ETHernet:TYPE?
|
|
Description
|
This query returns the name of Ethernet controller installed on the control board (Arduino Shield). If simulator is used it returns “Simulator”.
|
|
Return
|
The information will be returned as a list of quoted strings.
|
|
Usage example
|
SYST:CPU:INFO:ETH:TYPE?
"W5500"
|
5.15.28. SYSTem:CPU:INFOrmation:ONTime:LAST?
|
Syntax
|
SYSTem:CPU:INFOrmation:ONTime:LAST? [<channel>]
|
|
Description
|
This query returns time passed after last activation of the PSU. Resolution is 1 minute and this information is stored every 10 minutes in non-volatile memory. Therefore it’s possible that up to 10 minutes is lost after restart caused with power outage or system reset.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SYST:CPU:INFO:ONT:LAST?
15m
|
5.15.29. SYSTem:CPU:INFOrmation:ONTime:TOTal?
|
Syntax
|
SYSTem:CPU:INFOrmation:ONTime:TOTal? [<channel>]
|
|
Description
|
This query returns total active time of the PSU. Resolution is 1 minute and this information is stored every 10 minutes in non-volatile memory. Therefore it’s possible that up to 10 minutes is lost after restart caused with power outage or system reset.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
SYST:CPU:INFO:ONT:TOT?
"1h 45m"
|
5.15.30. SYSTem:CPU:INFOrmation:TYPE?
|
Syntax
|
SYSTem:CPU:INFOrmation:TYPE?
|
|
Description
|
This query returns the name of CPU installed on the control board (Arduino Shield). If simulator is used it returns “Simulator”.
|
|
Usage example
|
SYST:CPU:INFO:TYPE?
"Due"
|
|
Related Commands
|
*IDN?
|
5.15.31. SYSTem:CPU:MODel?
|
Syntax
|
SYSTem:CPU:MODel?
|
|
Description
|
This query returns the name of the control board (Arduino Shield). If simulator is used it returns “Simulator” and its version.
|
|
Usage example
|
If revision 1 Arduino Shield is detected:
SYST:CPU:MOD?
"Arduino, r5B12"
If firmware is running on simulator:
SYST:CPU:MOD?
"Simulator, v1.1"
|
|
Related Commands
|
SYSTem:CPU:OPTion?
|
5.15.32. SYSTem:CPU:OPTion?
|
Syntax
|
SYSTem:CPU:OPTion?
|
|
Description
|
This query returns a list of all installed options on the control board. The information will be returned as a list of quoted strings.
|
|
Usage example
|
SYST:CPU:OPT?
"BPost, EEPROM, RTC, SDcard, Ethernet, Display, Watchdog"
|
|
Related Commands
|
SYSTem:CPU:MODel?
|
5.15.33. SYSTem:DATE
|
Syntax
|
SYSTem:DATE {<year>}, {<month>}, {<day>}
SYSTem:DATE?
|
|
Description
|
Sets the date of the system clock (RTC). Specify the year, month, and day.
The self-test procedure compare date and time stored in RTC registers with values stored in the non-volatile memory (EEPROM). When the later is greater then former or any of them lost integrity (i.e. any of value is outside allowed range: for example seconds are higher then 60 or months are higher then 12, etc.) self-test will failed. The *TST? will return 1 and detailed report could be queried using the DIAGnostic:TEST? command.
The bit 3 (TIME) of the Questionable Status register will be set (see Section 3.4) if datetime self-test failed or datetime was never set.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<year>
|
NR1
|
2000 – 2099
|
–
|
|
<month>
|
NR1
|
1 – 12
|
–
|
|
<day>
|
NR1
|
1 – 31
|
–
|
|
Return
|
Query the current date of the system clock in YYYY, MM, DD format.
|
|
Usage example
|
SYST:DATE?
2015, 10, 24
|
|
Related Commands
|
*TST?
DIAGnostic[:INFOrmation]:TEST?
SYSTem:TIME
|
5.15.34. SYSTem:DIGital:INPut:DATA
|
Syntax
|
SYSTem:DIGital:INPut:DATA? {<pin>}
|
|
Description
|
This query reads the state of the digital control port.
Applies only to pin 1.
|
|
Return
|
The query returns the value of the state of input pin.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<pin>
|
NR1
|
1
|
1
|
|
Usage example
|
SYST:DIG:INP:DATA? 1
1
|
|
Related Commands
|
SYSTem:DIGital:PIN<n>:FUNCtion
SYSTem:DIGital:PIN<n>:POLarity
|
5.15.35. SYSTem:DIGital:OUTPut:DATA
|
Syntax
|
SYSTem:DIGital:OUTPut:DATA {<pin>}, {<state>}
SYSTem:DIGital:OUTPut:DATA? {<pin>}
|
|
Description
|
This command sets the output data on the digital output pin.
Applies only to pin 2 and pin 3. This command is supported on Arduino Shield r5B11 or newer revision.
|
|
Return
|
The query returns the last programmed value on the selected pin.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<pin>
|
NR1
|
2 – 3
|
–
|
|
|
<state>
|
Discrete
|
ON|OFF|0|1
|
–
|
|
Usage example
|
SYST:DIG:OUTP:DATA 2, 0
|
|
Errors
|
-114,"Header suffix out of range"
|
|
Related Commands
|
SYSTem:DIGital:PIN<n>:FUNCtion
SYSTem:DIGital:PIN<n>:POLarity
|
5.15.36. SYSTem:DIGital:PIN<n>:FUNCtion
|
Syntax
|
SYSTem:DIGital:PIN<n>:FUNCtion {<function>}
SYSTem:DIGital:PIN<n>:FUNCtion?
|
|
Description
|
Use this command to set function of the selected digital port pin. The pin function is saved in non-volatile memory.
All input functions applies only to pin1 and all output functions applies only to pin 2 and pin 3.
- DINPut – The pin is in digital input mode.
- DOUTput – The pin is in digital output mode.
- FAULt – Setting FAULt means that pin functions as an isolated fault output. The fault signal is true when any output is in a protected state (from OCP, OVP, OTP, OPP) or Fan fault is detected.
- INHibit – When pin is configured as an inhibit input, a true signal at the pin will disable all output channels.
- ONCouple – output pin synchronize channel output state.
- TINPut – The pin is configured as a trigger input. When configured as a trigger input, the pin can be selected as the source for trigger signals. See TRIGger[:SEQuence]:SOURce.
- TOUTput – This allows a BUS trigger to be sent to any digital port pin that has been configured as a trigger output. A trigger out pulse is generated when the state is on and a bus trigger is received. A BUS trigger is generated using the *TRG command.
|
|
Return
|
The query command returns DINP, DOUT, FAUL, INH or TINP.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
|
<function>
|
Discrete
|
DINP|DOUT|FAUL|INH|ONC|TINP|TOUT
|
–
|
|
Usage example
|
SYST:DIG:PIN1:FUNC INH
SYST:DIG:PIN2:FUNC FAUL
SYST:DIG:PIN3:FUNC ONC
|
|
Errors
|
-114,"Header suffix out of range"
|
|
Related Commands
|
TRIGger[:SEQuence]:SOURce
SYSTem:DIGital:INPut:DATA
SYSTem:DIGital:OUTPut:DATA
|
5.15.37. SYSTem:DIGital:PIN<n>:POLarity
|
Syntax
|
SYSTem:DIGital:PIN<n>:POLarity {<polarity>}
SYSTem:DIGital:PIN<n>:POLarity?
|
|
Description
|
This command sets the polarity of the selected digital port pin. The pin polarity is saved in non-volatile memory.
- POSitive – a logical true signal is a voltage high at the pin. For trigger inputs and outputs, POSitive means a rising edge.
- NEGative – a logical true signal is a voltage low at the pin. For trigger inputs and outputs, NEGative means a falling edge.
|
|
Return
|
The query command returns POS or NEG.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
|
<polarity>
|
Discrete
|
POSitive|NEGative
|
–
|
|
Usage example
|
SYST:DIG:PIN1:POL POS
SYST:DIG:PIN2:POL NEG
|
|
Errors
|
-114,"Header suffix out of range"
|
|
Related Commands
|
TRIGger[:SEQuence]:SOURce
SYSTem:DIGital:INPut:DATA
SYSTem:DIGital:OUTPut:DATA
|
5.15.38. SYSTem:ERRor
|
Syntax
|
SYSTem:ERRor[:NEXT]?
|
|
Description
|
This query command reads and clear errors from the error queue. A record of up to 20 errors can be stored in the PSU’s error queue. See also “Error Messages” in Section 7.
Errors are retrieved in first-in-first-out (FIFO) order. The first error returned is the first error that was stored. The PSU beeps once each time an error is generated. The error queue is cleared when power has been off or after a *CLS command.
|
|
Return
|
SYSTem:ERRor[:NEXT]? queries and clears the error messages in the error queue. The query returns the number and content of the error message.
|
|
Usage example
|
SYST:ERR?
-113,"Undefined header"
|
|
Errors
|
If more than 20 errors have occurred, the last error stored in the queue (the most recent error) is replaced with:
-350,"Queue overflow"
No additional errors are stored until you remove errors from the queue.
|
|
Related Commands
|
*CLS
*RST
SYSTem:ERRor:COUNt
|
5.15.39. SYSTem:ERRor:COUNt?
|
Syntax
|
SYSTem:ERRor:COUNt?
|
|
Description
|
This query command queries the error/event queue for the number of unread items. As errors and events may occur at any time, more items may be present in the queue at the time it is actually read.
|
|
Usage example
|
SYST:ERR:COUN?
10
|
|
Related Commands
|
*CLS
*RST
SYSTem:ERRor[:NEXT]
|
5.15.40. SYSTem:INHibit?
|
Syntax
|
SYSTem:INHibit?
|
|
Description
|
Use this command to query PSU’s inhibit state that is controlled with digital input (see [SOURce]:DIGital:PIN<n>:FUNCtion command). When PSU is in inhibited state, all channel’s output will be disabled (OFF) and triggered action (e.g. LIST) will be paused.
Channel output state command (OUTPut[:STATe]) can be used when PSU is in inhibited mode but it will not affect output (i.e. change it to enable state).
|
|
Return
|
Returns 0 if inhibit is not active or 1 if inhibit is active.
|
|
Usage example
|
SYST:INH?
0
|
|
Related Commands
|
OUTPut[:STATe] {<bool>} [, <channel>]
[SOURce]:DIGital:PIN<n>:FUNCtion
|
5.15.41. SYSTem:KLOCk
|
Syntax
|
SYSTem:KLOCk
|
|
Description
|
This command similar to the SYSTem:REMote command disables all front-panel options except for [Lock/Unlock] icon. You can push and hold the [Lock/Unlock] for a few seconds to unlock the front panel. The system password may be needed if it is set.
Lock state is saved in non-volatile memory. Therefore, the front panel remains locked even after AC power is cycled.
|
|
Usage example
|
SYST:KLOC
|
|
Related Commands
|
SYSTem:COMMunicate:RLSTate
SYSTem:REMote
|
5.15.42. SYSTem:LOCal
|
Syntax
|
SYSTem:LOCal
|
|
Description
|
This command places the PSU in the local mode during remote operation. All options on the front panel are fully functional.
|
|
Usage example
|
SYST:LOC
|
|
Related Commands
|
SYSTem:COMMunicate:RLSTate
SYSTem:REMote
SYSTem:RWLock
|
5.15.43. SYSTem:PASSword:CALibration:RESet
|
Syntax
|
SYSTem:PASSword:CALibration:RESet
|
|
Description
|
This command resets the calibration password to the firmware default setting, which is “eezpsu”. This command does not reset the system password.
|
|
Usage example
|
SYST:PASS:CAL:RES
|
|
Related Commands
|
CALibration[:MODE]
CALibration:PASSword:NEW
|
5.15.44. SYSTem:PASSword:FPANel:RESet
|
Syntax
|
SYSTem:PASSword:FPANel:RESet
|
|
Description
|
This command resets the front panel lockout password to the firmware default setting, which is empty space (“”). This command does not reset the calibration password.
|
|
Usage example
|
SYST:PASS:FPAN:RES
|
|
Related Commands
|
SYSTem:KLOCk
SYSTem:PASSword:NEW
|
5.15.45. SYSTem:PASSword:NEW
|
Syntax
|
SYSTem:PASSword:NEW {<old>}, {<new>}
|
|
Description
|
Enter a new system password. To change the password, first unsecure the PSU using the old password. Then, the new code has to be entered. The calibration code may contain up to 16 characters over the remote interface. Minimum length is 4 characters.
The new password is automatically stored in non-volatile memory
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<old>
|
Quoted string
|
0 to 16 characters
|
–
|
|
<new>
|
Quoted string
|
4 to 16 characters
|
–
|
|
Usage example
|
SYST:PASS:NEW "","mypass2016"
|
|
Errors
|
122,"Invalid sys password"
125,"Sys password too long"
126,"Sys password too short"
|
|
Related Commands
|
SYSTem:KLOCk
|
5.15.46. SYSTem:PON:OUTPut:DISable
|
Syntax
|
SYSTem:PON:OUTPut:DISable {<bool>}
SYSTem:PON:OUTPut:DISable?
|
|
Description
|
This command controls status off all channel outputs on power up. If enabled (ON), all outputs will be disabled regardless of what is stored in user profile selected for auto recall.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Return
|
Query returns status of forced output disabling on power up.
|
|
Usage example
|
OUTP?
1
SYST:PON:OUTP:DIS 1
(Restart)
OUTP?
0
|
|
Related Commands
|
MEMory:STATe:RECall:AUTO
SYSTem:POWer
|
5.15.47. SYSTem:POWer
|
Syntax
|
SYSTem:POWer {<bool>}
SYSTem:POWer?
|
|
Description
|
This command controls powering down and powering up sequence of the AC power inputs. The “Stand-by” indicator (LED_PWR, TLC5925 Out15) will be switched on when the PSU enters the Stand-by mode.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Return
|
Query returns PSU power Stand-by status.
|
|
Usage example
|
SYST:POW ON
SYST:POW?
1
|
|
Related Commands
|
*RST
*TST?
SYSTem:BEEP:STATe
|
5.15.48. SYSTem:POWer:PROTection:TRIP
|
Syntax
|
SYSTem:POWer:PROTection:TRIP {<bool>}
SYSTem:POWer:PROTection:TRIP?
|
|
Description
|
Use this command to shut down (stand-by) the PSU when any of channel’s protection tripped. The SYSTem:POWer command has to be used to power the PSU on again.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
Return
|
Query returns status of shutdown when tripped mode.
|
|
Usage example
|
SYST:POW:PROT:TRIP?
1
|
|
Related Commands
|
SYSTem:POWer
|
5.15.49. SYSTem:REMote
|
Syntax
|
SYSTem:REMote
|
|
Description
|
Use this command to place the PSU into remote mode for serial (via USB) or Ethernet remote control. All front-panel options are disabled except for [Lock/Unlock] icon. You can push and hold the [Lock/Unlock] for a few seconds to unlock the front panel. The system password may be needed if it is set.
|
|
Usage example
|
SYST:REM
|
|
Related Commands
|
SYSTem:COMMunicate:RLSTate
SYSTem:LOCal
SYSTem:RWLock
|
5.15.50. SYSTem:RWLock
|
Syntax
|
SYSTem:RWLock
|
|
Description
|
Places the PSU in the remote mode for serial (via USB) or Ethernet remote control. This command is the same as SYSTem:REMote, except that all front panel options are disabled, including the [Lock/Unlock] icon.
|
|
Usage example
|
SYST:RWL
|
|
Related Commands
|
SYSTem:COMMunicate:RLSTate
SYSTem:LOCal
SYSTem:REMote
|
5.15.51. SYSTem:TEMPerature:PROTection[:HIGH][:LEVel]
|
Syntax
|
SYSTem:TEMPerature:PROTection[:HIGH][:LEVel] {<temperature>} [, <sensor>]
SYSTem:TEMPerature:PROTection[:HIGH][:LEVel]? [<sensor>]
|
|
Description
|
Set the over-temperature protection (OTP) value in degrees Celsius (oC) of the selected temperature sensor. When the over-temperature protection function of the specified temperature sensor is enabled (SYSTem:TEMPerature:PROTection[:HIGH]:STATe), one of the following action will be performed when the temperature exceeds the over-temperature protection value currently set:
- AUX – Switch off power of the main transformer and set bit 4 of the Questionable Status register
- CH1, CH2 – Disable channel output (OUTPut OFF) and set bit 4 of the Questionable Instrument Isummary registerIf any of above mentioned temperature sensors cause over-temperature condition an error tone will also follow if beeper is enabled (see SYSTem:BEEPer:STATe).
SYSTem:TEMPerature:PROTection[:HIGH]:TRIPped? command can be used to query whether over-temperature protection occurred on the selected temperature sensor.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<temperature>
|
NR2
|
0 – 100
|
70 for CH1, CH2, 50 for AUX
|
|
<sensor>
|
Discrete
|
AUX|CH1|CH2
|
AUX
|
|
Return
|
Query the over-temperature protection (OTP) value of the selected temperature sensor.
|
|
Usage example
|
SYST:TEMP:PROT 50, AUX
SYST:TEMP:PROT?
50
|
|
Related Commands
|
*RST
SYSTem:TEMPerature:PROTection[:HIGH]:STATe
SYSTem:TEMPerature:PROTection[:HIGH]:TRIPped?
|
5.15.52. SYSTem:TEMPerature:PROTection[:HIGH]:CLEar
|
Syntax
|
SYSTem:TEMPerature:PROTection[:HIGH]:CLEar [<sensor>]
|
|
Description
|
This command clears the latched protection status when an over-temperature is detected.
All conditions that generate the fault must be removed before the latched status can be cleared. The output is restored to the state it was in before the fault condition occurred.
|
|
|
Name
|
Type
|
Range
|
Default
|
|
<sensor>
|
Discrete
|
AUX|CH1|CH2
|
AUX
|
|
Usage example
|
SYST:TEMP:PROT:CLE
|
|
Related Commands
|
SYSTem:TEMPerature:PROTection[:HIGH]:TRIPped
|
5.15.53. SYSTem:TEMPerature:PROTection[:HIGH]:DELay[:TIME]
|
Syntax
|
SYSTem:TEMPerature:PROTection[:HIGH]:DELay[:TIME] {<delay>} [, <sensor>]
SYSTem:TEMPerature:PROTection[:HIGH]:DELay[:TIME]? [<sensor>]
|
|
Description
|
This command sets the over-temperature protection delay. The over-temperature protection function will not be triggered during the delay time. After the delay time has expired, the over-temperature protection function will be active.
Programmed values can range from 0 to 300 seconds. See also Section 8.1
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<delay>
|
NR1
|
0 – 300 seconds
|
10
|
|
<sensor>
|
Discrete
|
AUX|CH1|CH2
|
AUX
|
|
Return
|
The query returns programmed over-temperature protection delay.
|
|
Usage example
|
SYST:TEMP:PROT:DEL 30, CH2
|
|
Related Commands
|
*RST
SYSTem:TEMPerature:PROTection[:HIGH][:LEVel]
|
5.15.54. SYSTem:TEMPerature:PROTection[:HIGH]:STATe
|
Syntax
|
SYSTem:TEMPerature:PROTection[:HIGH]:STATe {<bool>} [, <sensor>]
SYSTem:TEMPerature:PROTection[:HIGH]:STATe? [<sensor>]
|
|
Description
|
This command enables or disables the over-temperature protection (OTP) function. The enabled state is ON (1); the disabled state is OFF (0). If the over-temperature protection function is enabled and the measured output power reach value set by [SOURce[<n>]]:POWer:PROTection[:LEVel] the output is disabled and the Questionable Condition status register OPP bit 10 is set.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
<sensor>
|
Discrete
|
AUX|CH1|CH2
|
AUX
|
|
Return
|
The query command returns 0 if the current protection state is OFF, and 1 if the current protection state is ON.
|
|
Usage example
|
SYST:TEMP:PROT:STAT? CH1
0
|
|
Related Commands
|
*RST
SYSTem:TEMPerature:PROTection[:HIGH]:CLEar
|
5.15.55. SYSTem:TEMPerature:PROTection[:HIGH]:TRIPped?
|
Syntax
|
SYSTem:TEMPerature:PROTection[:HIGH]:TRIPped? [<sensor>]
|
|
Description
|
Query whether OTP occurred on the selected temperature sensor. When protection is tripped bit 4 (TEMPerature) of the Questionable Status register will be set (see Section 3.4).
The SYSTem:TEMPerature:PROTection[:HIGH]:CLEar command can be send to clear OTP condition caused by the selected temperature sensor.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<sensor>
|
Discrete
|
AUX|CH1|CH2
|
AUX
|
|
Return
|
This query returns a 1 if the protection circuit is tripped and a 0 if it is untripped.
|
|
Usage example
|
SYST:TEMP:PROT:TRIP?
0
|
|
Related Commands
|
SYSTem:TEMPerature:PROTection[:HIGH]:CLEar
SYSTem:TEMPerature:PROTection[:HIGH]:STATe
|
5.15.56. SYSTem:TIME
|
Syntax
|
SYSTem:TIME {<hours>}, {<minutes>}, {<seconds>}
SYSTem:TIME?
|
|
Description
|
Sets the time of the system clock (RTC). Specify the hours, minutes, and seconds.
The self-test procedure compare date and time stored in RTC registers with values stored in the non-volatile memory (EEPROM). When the later is greater then former or any of them lost integrity (i.e. any of value is outside allowed range: for example seconds are higher then 60 or months are higher then 12, etc.) self-test will failed. The *TST? will return 1 and detailed report could be queried using the DIAGnostic:TEST? command.
The bit 3 (TIME) of the Questionable Status register will be set (see Section 3.4) if datetime self-test failed or datetime was never set.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<hours>
|
NR1
|
0 – 23
|
–
|
|
<minutes>
|
NR1
|
0 – 59
|
–
|
|
<seconds>
|
NR1
|
0 – 59
|
–
|
|
Return
|
Query the current time of the system clock in HH, MM, SS format.
|
|
Usage example
|
SYST:TIME?
15, 10, 33
|
|
Related Commands
|
*TST?
DIAGnostic[:INFOrmation]:TEST?
SYSTem:DATE
|
5.15.57. SYSTem:TIME:DST
|
Syntax
|
SYSTem:TIME:DST {<rules>}
SYSTem:TIME:DST?
|
|
Description
|
Use this command to define daylight saving time (DST) rules used in your region.
Firmware v1.0 support limited number of region: Europe, US/Canada and Australia/New Zealand.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<rules>
|
Discrete
|
OFF|EU|USA|AUS
|
OFF
|
|
Return
|
Query the DTS rule name used for adjust time.
|
|
Usage example
|
SYST:TIME:DST EU
|
|
Related Commands
|
SYSTem:COMMunicate:ENABle
SYSTem:COMMunicate:NTP
SYSTem:TIME
|
5.15.58. SYSTem:TIME:ZONE
|
Syntax
|
SYSTem:TIME:ZONE {<zone>}
SYSTem:TIME:ZONE?
|
|
Description
|
Use this command to define time zone as offset from GMT.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<zone>
|
Quoted string
|
-12:00 to 14:00
|
–
|
|
Return
|
Query the time zone as offset from GMT in the following format: “[sign]hh:mm GMT”
|
|
Usage example
|
SYST:TIME:ZONE 1
SYST:TIME:ZONE?
"+01:00 GMT"
|
|
Related Commands
|
SYSTem:COMMunicate:ENABle
SYSTem:COMMunicate:NTP
SYSTem:TIME
|
5.15.59. SYSTem:VERSion?
|
Syntax
|
SYSTem:VERSion?
|
|
Description
|
This command returns the version of the SCPI (Standard Commands for Programmable Instruments) standard with which the instrument is in compliance
|
|
Return
|
The command returns a string in the form “YYYY.V”, where YYYY represents the year of the version and V represents a version for that year.
|
|
Usage example
|
SYST:VERS?
1999.0
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.16 - TRIGger.html
================================================
5.16. TRIGger
The PSU's triggering system allows a change in output voltage, current or start internal data logging when receiving a trigger, to select a trigger source, and to insert a trigger. Triggering the PSU is a multi-step process, for example:
- An output has to be selected (the INSTrument:SELect command) following by configuring the PSU for the triggered output level by using CURRent:TRIGgered and VOLTage:TRIGgered commands.
- The source from which the PSU will accept the trigger must be specified. The PSU could accept e.g. a BUS (software) trigger or an IMMediate trigger from the remote interface.
- The time delay between the detection of the trigger on the specified trigger source and the start of any corresponding output change can be programmed if needed. Such time delay is valid only for the BUS trigger source.
- Trigger programming is completed by providing an INITiate[:IMMediate] command. If the IMMediate source is selected, the selected output is set to the triggered level immediately. But if the trigger source is the BUS, the PSU is set to the triggered level after receiving the *TRG command.
5.16.1. TRIGger[:SEQuence][:IMMediate]
|
Syntax
|
TRIGger[:SEQuence][:IMMediate]
|
|
Description
|
This event command causes a defined LIST to immediately start without the selected trigger occurring.
|
|
Usage example
|
TRIG
|
|
Related Commands
|
*TRG
|
5.16.2. TRIGger[:SEQuence]:DELay
|
Syntax
|
TRIGger[:SEQuence]:DELay {<delay>}
TRIGger[:SEQuence]:DELay?
|
|
Description
|
This command sets the time delay between the detection of an event on the specified
trigger source and the start of any corresponding trigger action on the PSU output.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<delay>
|
NR1|Discrete
|
0 – 3600|MIN|MAX
|
MIN
|
|
Return
|
The query command returns the programmed delay in seconds.
|
|
Usage example
|
TRIG:DEL 10
|
5.16.3. TRIGger[:SEQuence]:EXIT:CONDition
|
Syntax
|
TRIGger[:SEQuence]:EXIT:CONDition {<condition>}
TRIGger[:SEQuence]:EXIT:CONDition?
|
|
Description
|
This command sets channels condition when LIST execution is not prematurely stopped (e.g. with ABORt command or by user action).
Use [SOURce[<n>]]:LIST:COUNt to set finite number of LIST loops.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
|
<condition>
|
Discrete
|
OFF|FIRSt|LAST|STANdby
|
OFF
|
|
Return
|
The query command returns the programmed exit condition.
|
|
Usage example
|
TRIG:EXIT:COND STAN
|
|
Related Commands
|
ABORt
INITiate
[SOURce[<n>]]:LIST:COUNt
[SOURce[<n>]]:CURRent:MODE
[SOURce[<n>]]:VOLTage:MODE
|
5.16.4. TRIGger[:SEQuence]:SOURce
|
Syntax
|
TRIGger[:SEQuence]:SOURce {<source>}
TRIGger[:SEQuence]:SOURce?
|
|
Description
|
This command selects the source from which the PSU will accept a trigger.
- BUS – enables LAN and serial (via USB) triggering using the *TRG command.
- IMMediate – the PSU executes a complete trigger operation immediately after executing the INITiate command without delay.
- MANual – enables triggering by selecting the encoder knob switch.
- PIN<n> – selects a digital port pin configured as a trigger input. <n> specifies the pin number (it’s always 1).
When the trigger source is set to BUS, the *WAI command can ensure the synchronization. After executing the *WAI command, the PSU will only execute new command when all the pending operations are completed.
Also when the trigger source is set to BUS, you can use the *OPC command to report that the operation is completed. The *OPC? command will return “1” to the output buffer and the *OPC command will set the bit 0 (OPC bit, operation complete) in the standard event register when the operation is finished.
The wait for the BUS, EXTernal, or KEY trigger can be bypassed by sending the
TRIGger[:SEQuence][:IMMediate] command.
The APPLy command automatically sets the source to IMMediate.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
|
<source>
|
Discrete
|
BUS|IMM|MAN|PIN1
|
–
|
|
Return
|
The query command returns the programmed trigger subsystem source.
|
|
Usage example
|
TRIG:SOUR BUS
TRIG:SOUR?
BUS
|
|
Related Commands
|
*OPC
*RST
*TRG
*WAI
ABORt
APPLy
INITialize
TRIGger[:SEQuence][:IMMediate]
|
5.16.5. TRIGger:DLOG[:IMMediate]
|
Syntax
|
TRIGger:DLOG[:IMMediate]
|
|
Description
|
The command sends an immediate trigger signal to the data logger. This will trigger the internal data log session regardless of the selected trigger source. You must initiate (see the INIT:DLOG command) the data logger before you trigger it.
|
|
Usage example
|
TRIG:DLOG
|
|
Related Commands
|
*TRG
INITialize:DLOG
|
5.16.6. TRIGger:DLOG:SOURce
|
Syntax
|
TRIGger:DLOG:SOURce {<source>}
TRIGger:DLOG:SOURce?
|
|
Description
|
The command selects the trigger source for the data logger in the same fashion as the TRIGger[:SEQuence]:SOURce command.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
|
<source>
|
Discrete
|
BUS|IMM|MAN|PIN1
|
–
|
|
Return
|
The query command returns the programmed trigger subsystem source.
|
|
Usage example
|
TRIG:DLOG:SOUR PIN1
TRIG:SOUR?
PIN1
|
|
Related Commands
|
INITialize
TRIGger[:SEQuence]:SOURce
TRIGger:DLOG[:IMMediate]
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.2 - CALibrate.html
================================================
5.2. CALibration
This subsystem provides commands for the PSU calibration. Only one channel can be calibrated at a time. If calibration mode has not been enabled with CALibration:STATe, the calibration commands will generate an error. Use CALibration:SAVE to save any changes, otherwise all changes will be lost on exit from calibration mode. Within the same calibration session both output voltage and current can be calibrated for the currently selected channel.
Calibration cannot start if channel output is not enabled (OUTPut[:STATe] ON). During calibration process three points has to be entered: MIN, MID and MAX. But in practice two point calibration is performed to re-scale the output programmed and measured values by correcting both slope and offset errors. MID point is used only as an additional validation that between entered MIN and MAX values it’s possible to “draw” a line within allowed minor tolerance.
5.2.1. CALibration[:MODE]
|
Syntax
|
CALibration[:MODE] {<bool>}, {<password>}
CALibration[:MODE]?
|
|
Description
|
This command enables or disables calibration mode. Calibration mode must be enabled for the channel to accept any calibration commands. The first parameter specifies the ON (1) or OFF (0) state. The second parameter is the password. Successful execution of this command set both output VOLTage and CURRent of the selected channel to the MINimum value (see Section 8.1).
Execution of this command also affects bit 0 (CALibrating) of the Operation Instrument Isummary register (see Section 3.3.2).
If both voltage and current calibration parameters exists on calibration mode exit (CALibration[:MODE] OFF) the CALibration:STATe ON command will automatically follows.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
OFF
|
|
|
<password>
|
Quoted string
|
4 to 16 characters
|
"eezpsu"
|
|
Return
|
The returned parameter is 0 (OFF) or 1 (ON).
|
|
Usage example
|
See Section 10.2
|
|
Errors
|
102,"Invalid cal password"
104,"Bad sequence of calibration commands"
312,"Cannot execute when the channels are coupled"
|
|
Related Commands
|
CALibration:STATe
DIAGnostic[:INFOrmation]:OTIMe?
INSTrument:COUPle:TRACking
|
5.2.2. CALibration:CLEar
|
Syntax
|
CALibration:CLEar {<password>}
|
|
Description
|
Clear all calibration parameters stored in the non-volatile memory for the currently selected channel. After successful execution of this command CALibration:STATe will be set to OFF (0) and further usage of the calibration data will be disabled. This command will be also filled calibration remark with the date and note that calibration data has been cleared.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<password>
|
Quoted string
|
4 to 16 characters
|
"eezpsu"
|
|
Return
|
None
|
|
Usage example
|
DIAG:CAL?
"remark=20170331 new cal","u_cal_params_exists=1","u_min_level=0.150V","u_min_data=0.1
06V","u_min_adc=0.165V","u_mid_level=19.100V","u_mid_data=19.056V
","u_mid_adc=18.500V","u_max_level=38.000V","u_max_data=37.956V",
"u_max_adc=36.791V","u_min_range=0.000V","u_max_range=40.000V","i
_5A_cal_params_exists=1","i_5A_min_level=0.050A","i_5A_min_data=0
.057A","i_5A_min_adc=0.050A","i_5A_mid_level=2.425A","i_5A_mid_da
ta=2.438A","i_5A_mid_adc=2.368A","i_5A_max_level=4.800A","i_5A_ma
x_data=4.811A","i_5A_max_adc=4.686A","i_5A_min_range=0.000A","i_5
A_max_range=5.000A","i_500mA_cal_params_exists=1","i_500mA_min_le
vel=0.0050A","i_500mA_min_data=0.0060A","i_500mA_min_adc=0.0051A"
,"i_500mA_mid_level=0.2425A","i_500mA_mid_data=0.2617A","i_500mA_
mid_adc=0.2368A","i_500mA_max_level=0.4800A","i_500mA_max_data=0.
5170A","i_500mA_max_adc=0.4686A","i_500mA_min_range=0.0000A","i_5
00mA_max_range=0.0000A"
CAL:STAT?
1
CAL:CLE “eezpsu”
CAL:STAT?
0
DIAG:CAL?
"remark= Not calibrated","u_cal_params_exists=0","i_cal_params_exists=0"
|
|
Errors
|
102,"Invalid cal password"
|
|
Related Commands
|
CALibration:STATe
DIAGnostic[:INFOrmation]:CALibration?
|
5.2.3. CALibration:CURRent[:DATA]
|
Syntax
|
CALibration:CURRent[:DATA] {<new value>}
|
|
Description
|
This command can only be used when calibration is enabled and the output state of the currently selected channel is ON. It enters a current value that is obtained by reading an external meter. The minimum calibration level (CAL:CURR:LEV MIN) has to be selected first for the value being entered, then the middle and maximum calibration levels (CAL:CURR:LEV MID and CAL:CURR:LEV MAX) for the value being entered. Three successive values must be selected and entered. Data values are expressed in base units – either volts or amperes, depending on which function is being calibrated.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<new value>
|
NR2
|
-0.2A to MAX + 0.2A
The maximum value is dependent on the PSU current rating. See Section 8.1
|
–
|
|
Return
|
None
|
|
Usage example
|
See Section 10.2
|
|
Errors
|
104,"Bad sequence of calibration commands"
107,"Cal value out of range"
|
5.2.4. CALibration:CURRent:LEVel
|
Syntax
|
CALibration:CURRent:LEVel {<level>}
|
|
Description
|
This command can only be used when calibration is enabled and the output state of the currently selected channel is ON. It sets the PSU to a calibration point that is entered with the CAL:CURR command. During calibration, three points must be entered and the low-end point (MIN) must be selected and entered first.
This command will set output voltage to MAXimum / 2 (for example 25V for the PSU model with 0-50V).
When calibration LEVel is set it’s possible to override its default value using the CURRent command. That could be especially useful when LOW range is calibrating with average 3½-digit multimeter with full scale of 200 mA that is not enough to measure MID and MAX level. Therefore instead of predefined 242.5 mA and 480 mA one can set e.g. 100 mA and 200 mA to stay within multimeter’s low current range (next one is usually 10 A or 20 A that cannot be used to get satisfactory results).
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<level>
|
Discrete
|
MIN|MID|MAX (see also Section 8.1)
|
–
|
|
Return
|
None
|
|
Usage example
|
See Section 10.2
|
|
Errors
|
101,"Calibration state is off"
104,"Bad sequence of calibration commands"
|
|
Related Commands
|
CALibration:STATe
INSTrument:NSELect
INSTrument[:SELect]
[SOURce[<n>]]:CURRent
|
5.2.5. CALibration:CURRent:RANGe
|
Syntax
|
CALibration:CURRent:RANGe {<range>}
|
|
Description
|
When PSU is equipped with Power boards that has multiple current range (e.g. r5B12 that can be find out with the SYSTem:CHANnel:MODel? command) it’s recommended to perform calibration of both range. Use this command to select current range on which calibration will be accomplished.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<range>
|
Discrete|NR2
|
HIGH|LOW|5|0.5
|
HIGH|5
|
|
Return
|
None
|
|
Usage example
|
See Section 10.2
|
|
Errors
|
101,"Calibration state is off"
-241,"Hardware missing"
|
|
Related Commands
|
CALibration:CURRent:LEVel
CALibration:STATe
SYSTem:CHANnel:MODel?
|
5.2.6. CALibration:PASSword:NEW
|
Syntax
|
CALibration:PASSword:NEW {<old>}, {<new>}
|
|
Description
|
Enter a new calibration password. To change the password, first unsecure the PSU using the old password. Then, the new code has to be entered. The calibration code may contain up to 16 characters over the remote interface. Minimum length is 4 characters.
The new password is automatically stored in non-volatile memory and does not have to be stored with CALibration:SAVE.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<old>
|
Quoted string
|
4 to 16 characters
|
eezpsu
|
|
|
<new>
|
Quoted string
|
4 to 16 characters
|
–
|
|
Return
|
None
|
|
Usage example
|
CAL:PASS:NEW "eezpsu", "mycal1234"
|
|
Errors
|
102,"Invalid cal password"
105,"Cal password too long"
106,"Cal password too short"
|
5.2.7. CALibration:REMark
|
Syntax
|
CALibration:REMark {<user remark>}
CALibration:REMark?
|
|
Description
|
Record calibration information about the PSU. The calibration message is consist of two parts:
- datetime stamp in format yyyymmdd and
- up to 32 characters.
The PSU should be in calibration mode before sending a calibration message.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<user remark>
|
Quoted string
|
0 to 32 characters
|
"Calibration passed"
|
|
Return
|
Query the calibration message.
|
|
Usage example
|
When CAL:REM with text "Calibrated by EEZ" is executed at 2015-09-14:
CAL:REM "Calibrated by EEZ"
CAL:REM?
"20150904 Calibrated by EEZ"
See also Section 10.2
|
|
Errors
|
The following errors could be generated by command but not query:
101,"Calibration state is off"
104,"Bad sequence of calibration commands"
|
|
Related Commands
|
CALibration:STATe
|
5.2.8. CALibration:SAVE
|
Syntax
|
CALibration:SAVE
|
|
Description
|
This command saves calibration constants in non-volatile memory after the calibration procedure has been completed. If calibration mode is exited by programming CALibration:STATe OFF without first saving the new constants, the previous constants are restored. Execution of this command also affects bit 0 (CALibrating) of the Operation Instrument Isummary register (see Section 3.3.2).
|
|
Return
|
None
|
|
Usage example
|
See Section 10.2
|
|
Errors
|
-340,"Calibration failed"
101,"Calibration state is off"
104,"Bad sequence of calibration commands"
111,"No new cal data exists"
|
5.2.9. CALibration:SCReen:INIT
|
Syntax
|
CALibration:SCReen:INIT
|
|
Description
|
Use this command to initiate calibration procedure when touchscreen calibration data are lost or corrupted. Calibration has to be performed locally on the PSU.
New calibration procedure can be initiated also by touching the screen and hold for more then 30 seconds.
|
|
Return
|
None
|
|
Usage example
|
CAL:SCR:INIT
|
5.2.10. CALibration:STATe
|
Syntax
|
CALibration:STATe {<bool>}
CALibration:STATe?
|
|
Description
|
This command enables or disables usage of calibration parameters if they exists.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
OFF|ON|0|1
|
ON
|
|
Return
|
The returned parameter is 0 (OFF) or 1 (ON).
|
|
Usage example
|
CAL:STAT OFF
|
|
Errors
|
110,"Cal params missing or corrupted"
|
|
Related Commands
|
DIAGnostic[:INFOrmation]:OTIMe?
|
5.2.11. CALibration:VOLTage[:DATA]
|
Syntax
|
CALibration:VOLTage[:DATA] {<new value>}
|
|
Description
|
This command can only be used when calibration is enabled and the output state of the currently selected channel is ON. It enters a voltage value that you obtained by reading an external meter. You must first select the minimum calibration level (CAL:VOLT:LEV MIN) for the value being entered. You must then select the middle and maximum calibration levels (CAL:VOLT:LEV MID and CAL:VOLT:LEV MAX) for the value being entered. Three successive values must be selected and entered. The PSU then computes new voltage calibration constants. These constants has to be stored in non-volatile memory with CALibration:SAVE command.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<new value>
|
NR2
|
-0.5V to MAX + 0.5V
The maximum value is dependent on the PSU voltage rating. See Section 8.1
|
–
|
|
Return
|
None
|
|
Usage example
|
See Section Section 10.2
|
|
Errors
|
104,"Bad sequence of calibration commands"
107,"Cal value out of range"
|
|
Related Commands
|
CALibration:SAVE
CALibration:STATe
INSTrument:NSELect
INSTrument[:SELect]
|
5.2.12. CALibration:VOLTage:LEVel
|
Syntax
|
CALibration:VOLTage:LEVel {<level>}
|
|
Description
|
This command can only be used when calibration is enabled and the output state of the currently selected channel is ON. It sets the PSU to a calibration point that is entered with the CAL:VOLT[:DATA] command. During calibration, three points must be entered and the low-end point (MIN) must be selected and entered first.
This command will set output current to 50mA.
When calibration LEVel is set it’s possible to override its default value using the VOLTage command.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<level>
|
Discrete
|
MIN|MID|MAX (see also Section 8.1)
|
–
|
|
Return
|
None
|
|
Usage example
|
See Section Section 10.2
|
|
Errors
|
101,"Calibration state is off"
104,"Bad sequence of calibration commands"
|
|
Related Commands
|
CALibration:STATe
INSTrument:NSELect
INSTrument[:SELect]
[SOURce[<n>]]:VOLTage
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.3 - DIAGnostic.html
================================================
5.3. DIAGnostic
The purpose of the DIAGnostic subsystem is to provide a tree node for all of the PSU service and diagnostic routines used in routine maintenance and repair.
|
|
|
|
DIAGnostic
|
|
|
[:INFOrmation]
|
|
|
:ADC?
|
Returns the latest values acquired by ADC
|
|
:CALibration?
|
Returns a list of the calibration parameters
|
|
:FAN?
|
Returns status of the cooling fan.
|
|
:PROTection?
|
Returns the information about all protections.
|
|
:TEST?
|
Returns results of the most recent self-test
|
5.3.1. DIAGnostic[:INFOrmation]:ADC?
|
Syntax
|
DIAGnostic[:INFOrmation]:ADC? [<channel>]
|
|
Description
|
This query returns the latest values acquired by ADC (Analog-to-Digital Converter) of the currently selected channel.
|
|
Return
|
Return a list of quoted strings. The U_SET and I_SET are values measure on DAC outputs, and U_MON and I_SET on the channel output binding posts.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
n/a
|
|
Usage example
|
DIAG:ADC? CH2
"U_SET=10.1202", "U_MON=10.12", "I_SET=3.00", "I_MON=1.23"
|
|
Related Commands
|
MEASure[:SCALar]:CURRent[:DC]
MEASure[:SCALar][:VOLTage][:DC]
[SOURce[<n>]]:CURRent[:LEVel][:IMMediate][:AMPLitude]
[SOURce[<n>]]:VOLTage[:LEVel][:IMMediate][:AMPLitude]
|
5.3.2. DIAGnostic[:INFOrmation]:FAN?
|
Syntax
|
DIAGnostic[:INFOrmation]:FAN?
|
|
Description
|
Use this query to obtain information about cooling fan state.
|
|
Return
|
Returns -1 if cooling fan is not installed (see SYSTem:CPU:[INFOrmation]?), 0 if fan is stalled (fault condition) or measured fan speed in rpm.
Cooling fan is periodically tested while it’s working (that depends of measured channel’s temperature sensor value). When it does not passed the test, programmed output current is automatically limited to value defined with ERR_MAX_CURRENT constant (conf_advanced.h). If load that draws more current then ERR_MAX_CURRENT value output current will be set to zero.
|
|
Usage example
|
DIAG:FAN?
1205.00
|
|
Related Commands
|
MEASure[:SCALar]:TEMPerature[:THERmistor][:DC]
SYSTem:CPU:[INFOrmation]
|
5.3.3. DIAGnostic[:INFOrmation]:CALibration?
|
Syntax
|
DIAGnostic[:INFOrmation]:CALibration? [<channel>]
|
|
Description
|
This query returns a list of calibration parameters for the currently selected channel. If the selected channel is in the calibration mode (CALibration[:MODE] ON) then all calibration information collected to the current calibration step will be returned. Otherwise the calibration data stored in non-volatile memory will be returned.
|
|
Return
|
The information will be returned as a list of quoted strings.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
n/a
|
|
Usage example
|
Calibration parameters for H24005 PSU model when the channel 1 is not in the calibration mode:
DIAG:INFO:CAL? CH1
"remark=20161211 he2","u_cal_params_exists=1","u_min_level=0.15V","u_min_data=0.13
V","u_min_adc=0.11V","u_mid_level=19.10V","u_mid_data=19.07V","u_
mid_adc=18.75V","u_max_level=38.00V","u_max_data=37.90V","u_max_a
dc=37.35V","u_min_range=0.019735V","u_max_range=39.997578V","i_ca
l_params_exists=1","i_min_level=0.05A","i_min_data=0.04A","i_min_
adc=0.04A","i_mid_level=2.42A","i_mid_data=2.42A","i_mid_adc=2.42
A","i_max_level=4.80A","i_max_data=4.81A","i_max_adc=4.79A","i_mi
n_range=0.012135A","i_max_range=4.999954A"
The query results when a channel is just entered the calibration mode:
DIAG:INFO:CAL?
"u_level=none", "i_level=none"
The query results when a channel is at the step MIDdle of the voltage calibration:
DIAG:INFO:CAL?
"u_min=0.11V", "u_level=mid", "u_level_value=24.05V", "u_adc=24.14V", "i_level=none"
|
|
Related Commands
|
CALibration:REMark
CALibration:SAVE
|
5.3.4. DIAGnostic[:INFOrmation]:PROTection?
|
Syntax
|
DIAGnostic[:INFOrmation]:PROTection?
|
|
Description
|
This query returns information about all supported output protection mechanisms.
|
|
Return
|
The information will be returned as a list of quoted strings.
|
|
Usage example
|
DIAG:PROT?
"CH1 u_tripped=0","CH1 u_state=0","CH1 u_delay=5.00 ms","CH1 u_level=39.99 V","CH1 i_tripped=0","CH1 i_state=1","CH1 i_delay=20.00 ms","CH1 p_tripped=0","CH1 p_state=1","CH1 p_delay=10.00 s","CH1 p_level=155.00 W","CH2 u_tripped=0","CH2 u_state=0","CH2 u_delay=5.00 ms","CH2 u_level=39.99 V","CH2 i_tripped=1","CH2 i_state=1","CH2 i_delay=20.00 ms","CH2 p_tripped=0","CH2 p_state=1","CH2 p_delay=10.00 s","CH2 p_level=155.00 W","temp_AUX_tripped=0","temp_AUX_state=0","temp_AUX_delay=10.00 s","temp_AUX_level=55.00 oC","temp_CH1_tripped=0","temp_CH1_state=1","temp_CH1_delay=30.00 s","temp_CH1_level=75.00 oC","temp_CH2_tripped=0","temp_CH2_state=1","temp_CH2_delay=30.00 s","temp_CH2_level=75.00 oC"
|
|
Related Commands
|
[SOURce[<n>]]:CURRent:PROTection:DELay[:TIME]
[SOURce[<n>]]:CURRent:PROTection:STATe
[SOURce[<n>]]:CURRent:PROTection:TRIPped?
[SOURce[<n>]]:POWer:PROTection
[SOURce[<n>]]:POWer:PROTection:DELay[:TIME]
[SOURce[<n>]]:POWer:PROTection:STATe
[SOURce[<n>]]:POWer:PROTection:TRIPped?
[SOURce[<n>]]:VOLTage:PROTection:DELay[:TIME]
[SOURce[<n>]]:VOLTage:PROTection:STATe
[SOURce[<n>]]:VOLTage:PROTection:TRIPped?
SYSTem:TEMPerature:PROTection[:HIGH][:LEVel]
SYSTem:TEMPerature:PROTection[:HIGH]:DELay[:TIME]
SYSTem:TEMPerature:PROTection[:HIGH]:STATe
SYSTem:TEMPerature:PROTection[:HIGH]:TRIPped?
|
5.3.5. DIAGnostic[:INFOrmation]:TEST?
|
Syntax
|
DIAGnostic[:INFOrmation]:TEST?
|
|
Description
|
This query returns results of the most recent self-test (see *TST? command).
|
|
Return
|
The information will be returned in the following format: "<return code, device name, installed, return message>" where the return code could be one of the following values:
- 0 – failed
- 1 – passed
- 2 – skipped
This information format will repeat with as many iterations as the number of devices found in configuration parameters of the PSU. While in the Stand-by mode this command will returns only test results for the Arduino shield devices.
Return code for the BP option will always be 2 (skipped).
|
|
Usage example
|
Return self-test results when SD card is not found:
DIAG:TEST?
"1, EEPROM, installed, passed","0, SD card, installed, failed","2, Ethernet, installed, skipped","1, RTC, installed, passed","1, DateTime, installed, passed","2, BP option, installed, skipped","1, Fan, installed, passed","1, AUX temp, installed, passed","1, CH1 temp, installed, passed","1, CH2 temp, installed, passed","1, CH1 IOEXP, installed, passed","1, CH1 DAC, installed, passed","1, CH1 ADC, installed, passed","1, CH2 IOEXP, installed, passed","1, CH2 DAC, installed, passed","1, CH2 ADC, installed, passed"
Return self-test results while PSU is in the Stand-by mode:
DIAG:TEST?
"1, EEPROM, installed, passed","1, SD card, installed, passed","2, Ethernet, installed, skipped","1, RTC, installed, passed","1, DateTime, installed, passed","2, BP option, installed, skipped","1, Fan, installed, passed","1, AUX temp, installed, passed","1, CH1 temp, installed, passed","1, CH2 temp, installed, passed","1, CH1 IOEXP, installed, passed","1, CH1 DAC, installed, passed","1, CH1 ADC, installed, passed","1, CH2 IOEXP, installed, passed","1, CH2 DAC, installed, passed","1, CH2 ADC, installed, passed"
|
|
Related Commands
|
*TST?
SYSTem:POWer
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.4 - DISPlay.html
================================================
5.4. DISPlay
The DISPlay commands are used to set the display mode, turn on or off the front panel TFT display, select main page appearance, display and clear the text sent using a controller application. DISPlay is independent of, and does not modify, how data is returned to the controller application.
5.4.1. DISPlay:BRIGhtness
|
Syntax
|
DISPlay:BRIGhtness {<value>}
DISPlay:BRIGhtness?
|
|
Description
|
Controls the intensity of the front panel TFT display. The range of the parameter is 1 to 20, where 20 is full intensity and 1 is fully blanked.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<value>
|
NR1
|
1 – 20
|
20
|
|
Return
|
This query returns set front panel's TFT display brightness value.
|
|
Usage example
|
DISP:BRIG?
20
|
|
Related Commands
|
*RST
|
5.4.2. DISPlay:VIEW
|
Syntax
|
DISPlay:VIEW {<mode>}
DISPlay:VIEW?
|
|
Description
|
Use this command to set front panel TFT display main page appearance. The following modes are available:
- 1 – Digits
- 2 – Bar graph horizontal
- 3 – Bar graph vertical
- 4 – YT view
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<mode>
|
NR1|Discrete
|
1 – 4|DEFault
|
DEFault
|
|
Return
|
This query returns set front panel's TFT display main page appearance numeric value (NR1).
|
|
Usage example
|
DISP:VIEW 2
|
|
Related Commands
|
*RST
|
5.4.3. DISPlay[:WINdow][:STATe]
|
Syntax
|
DISPlay[:WINdow][:STATe] {<bool>}
DISPlay[:WINdow][:STATe]?
|
|
Description
|
Turn the front panel TFT display off or on. When the display is turned off, outputs are not sent to the display and all indicators are disabled except the Event view indicator. The display state is automatically turned on when you return to the local mode.
Press and hold the display for about a second to return to the LOCal from the REMote control.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
–
|
|
Return
|
DISPlay? query the front panel TFT display state. Returns 0 (OFF) or 1 (ON).
|
|
Usage example
|
DISP ON
|
|
Related Commands
|
SYSTem:LOCal
SYSTem:REMote
|
5.4.4. DISPlay[:WINdow]:TEXT
|
Syntax
|
DISPlay[:WINdow]:TEXT {<text message>}
DISPlay[:WINdow]:TEXT?
|
|
Description
|
Display a message on the front panel TFT display. The PSU will display up to 32 characters in a message.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<text message>
|
Quoted string
|
–
|
–
|
|
Return
|
Query the message sent to the front panel TFT display and returns a quoted string.
|
|
Usage example
|
Send "Hello world" textual message:
DISP:TEXT "Hello world"
|
5.4.5. DISPlay[:WINdow]:TEXT:CLEar
|
Syntax
|
DISPlay[:WINdow]:TEXT:CLEar
|
|
Description
|
Clear the message displayed on the front panel TFT display.
|
|
Return
|
None
|
|
Usage example
|
DISP:TEXT:CLE
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.5 - FETCh.html
================================================
5.5. FETCh
Fetch commands return measurement data that has been previously acquired. FETCh queries do not generate new measurements, but allow additional measurement calculations from the same acquired data.
5.5.1. FETCh:AHOur?
|
Syntax
|
FETCh:AHOur? {<channel>}
|
|
Description
|
Not implemented yet
Use this command to query delivered energy on the specified channel in amp-hours accumulated after last power-on or SENSe:AHOur:RESet command.
This value is measured independently of channel’s total delivered energy in amp-hours stored in non-volatile memory that can be queried using the SYSTem:CHANnel:INFOrmation:AHOur:TOTal? Command.
If channels are coupled (in series or parallel) or in tracking mode, this command will return a sum of delivered energy on both channels.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
FETC:AHO? CH1
1340.30
|
|
Related Commands
|
FETCh:WHOur?
INSTrument:COUPle:TRACking
OUTPut:TRACk[:STATe]
SENSe:AHOur:RESet
SYSTem:CHANnel:INFOrmation:AHOur:TOTal?
|
5.5.2. FETCh:WHOur?
|
Syntax
|
FETCh:WHOur? {<channel>}
|
|
Description
|
Not implemented yet
Use this command to query delivered energy on the specified channel in watt-hours accumulated after last power-on or SENSe:AHOur:RESet command.
This value is measured independently of channel’s total delivered energy in watt-hours stored in non-volatile memory that can be queried using the SYSTem:CHANnel:INFOrmation:WHOur:TOTal? Command.
If channels are coupled (in series or parallel) or in tracking mode, this command will return a sum of delivered energy on both channels.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Usage example
|
FETC:WHO? CH1
100.30
OUTP 0
FETC:WHO:RES CH1
FETC:WHO? CH1
0
|
|
Related Commands
|
FETCh:AHOur?
INSTrument:COUPle:TRACking
OUTPut:TRACk[:STATe]
SENSe:WHOur:RESet
SYSTem:CHANnel:INFOrmation:WHOur:TOTal?
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.6 - INITiate.html
================================================
5.6. INITiate
INITiate commands initialize the trigger system. This enables the trigger system to receive triggers.
5.6.1. INITiate
|
Syntax
|
INITiate[:IMMediate]
|
|
Description
|
The INITiate command is used to initialize the trigger system of the PSU. This command completes one full trigger cycle when the trigger source is an IMMediate and initiates the trigger subsystem when the trigger source is BUS.
For example, when the IMMediate is selected as a trigger source, an INITiate command
immediately transfers the VOLTage:TRIGgered[:AMPLitude] and CURRent:TRIGgered[:AMPLitude] values to VOLTage[:LEVel][:IMMediate][:AMPLitude] and CURRent[:LEVel][:IMMediate][:AMPLitude] values. Any delay is ignored.
Execution of this command also affects bit 5 (Waiting for TRIGger) of the Operation Instrument Isummary register (see Section 3.3.2).
|
|
Usage example
|
Generate a trigger operation after 5 seconds:
TRIG:SOUR BUS
TRIG:DEL 5
INIT
*TRG
|
|
Errors
|
-213,"Init ignored"
307,"List lengths are not equivalent"
308,"Cannot be changed while transient trigger is initiated"
309,"Cannot initiate while in fixed mode"
|
|
Related Commands
|
*TRG
INSTrument:COUPle:TRIGger
|
5.6.2. INITiate:DLOG
|
Syntax
|
INITiate:DLOG {<filename>}
|
|
Description
|
The command starts the internal data logging session. All selected measurements defined with SENSe:DLOG:FUNCtion:CURRent and SENSe:DLOG:FUNCtion:VOLTage commands will be saved periodically in the specified filename. The data logging session will last until time specified with the SENSe:DLOG:TIME not expired or is interrupted prematurely (e.g. using the ABORt:DLOG or *RST command).
Data log file contains header and data section. The header is 28 bytes long and include the following information in little-endian format, i.e. the least significant byte (LSB) value is at the lowest address:
|
|
|
Position
|
Name
|
Description
|
|
|
0 – 7
|
FILE_ID
|
Always contains 0x45 0x45 0x5a 0x2d 0x44 0x4c 0x4f 0x47 (i.e. EEZ-DLOG text in ASCII format)
|
|
|
8 – 9
|
VERSION
|
File format version (e.g. 0x01 0x00)
|
|
|
10 – 11
|
FLAGS
|
0 – jitter column not included
1 – jitter column included
|
|
|
12 – 15
|
COLUMNS
|
Information about measured values that will be stored. A four bits per channel are used in the following manner (up to 8 channels can be supported):
|
|
|
|
|
Bit
|
Output value
|
|
|
|
|
0
|
Channel 1 Voltage
|
|
|
|
|
1
|
Channel 1 Current
|
|
|
|
|
2
|
Channel 1 Power
|
|
|
|
|
3
|
Channel 1 Reserved for future use
|
|
|
|
|
4
|
Channel 2 Voltage
|
|
|
|
|
...
|
|
|
|
16 – 19
|
PERIOD
|
Sampling frequency as specified with the SENSe:DLOG:PERiod command written as float (e.g. IEEE-754 32-bit floating point number in little-endian format)
|
|
|
20 – 23
|
DURATION
|
Internal data logging duration as defined with the SENSe:DLOG:TIME command. If data logging is interrupted prematurely (e.g. using the ABORt:DLOG or *RST command) recorded duration can be calculated from the log file size:
(FILE_SIZE - HEADER_SIZE) / (1 + NUM_COLUMNS) * PERIOD
|
|
|
24 – 27
|
START_TIME
|
Date and time when internal data logging session started written using the Unix time format.
|
|
|
The Log file data section contains multiple rows recorded with sampling frequency (every PERIOD) for the max. duration specified in DURATION field in the header. Number of recorded columns in each row depends of selected values for data logging as specify in COLUMNS and FLAGS fields in the header. For example:
|
|
|
Position
|
Description
|
|
|
0 – 3
|
Jitter (if Jitter flag is set in FLAG field)
|
|
|
4 – 7
|
First value (e.g. output voltage on Channel 1)
|
|
|
8 – 11
|
Second value (e.g. output current on Channel 2)
|
|
|
...
|
|
|
|
|
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
|
<filename>
|
Quoted string
|
File name, either / (slash) or \ (backslash) can be used as the path separator. 1 to 255 characters
|
–
|
|
Usage example
|
INIT:DLOG "test_log.dlog"
|
|
Related Commands
|
*RST
ABORt:DLOG
MMEMory:INFOrmation?
SENSe:DLOG:FUNCtion:CURRent
SENSe:DLOG:FUNCtion:VOLTage
SENSe:DLOG:PERiod
SENSe:DLOG:TIME
|
5.6.3. INITiate:CONTinuous
|
Syntax
|
INITiate:CONTinuous {<bool>}
INITiate:CONTinuous?
|
|
Description
|
This command is used to select whether the trigger system is continuously initiated or not. With CONTinuous set to OFF, the trigger system remain in the IDLE state until CONTinuous is set to ON or INITiate:IMMediate is received.
Once CONTinuous is set to ON, the trigger system will be initiated and exit the IDLE state. On completion of each trigger cycle, with CONTinuous ON, the trigger system immediately commence another trigger cycle without entering the IDLE state.
When INITiate:CONTinuous is set to OFF, the current trigger cycle will be completed before entering the IDLE state. The return to IDLE also occur as the result of an ABORt or *RST command.
The ABORt command force the trigger system to the IDLE state; however, the value of INITiate:CONTinuous is unaffected.
If INITiate:CONTinuous was set to ON prior to receiving ABORt, it remains ON and the trigger system immediately exit the IDLE state.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
|
<bool>
|
Boolean
|
OFF|ON|0|1
|
OFF
|
|
Return
|
The query command returns 0 if continuous transients are disabled (OFF), and 1 if continuous transients are enabled (ON).
|
|
Usage example
|
INIT:CONT ON
|
|
Related Commands
|
*RST
ABORt
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.7 - INSTrument.html
================================================
5.7. INSTrument
Each channel of the PSU is considered as separate (logical) instrument, which is required by the SCPI standard. The INSTrument subsystem provides a mechanism to identify and select instruments and establish coupling to simplify programming of more channels at once.
5.7.1. INSTrument[:SELect]
|
Syntax
|
INSTrument[:SELect] {<channel>}
INSTrument[:SELect]?
|
|
Description
|
This command selects the output to be programmed by the output identifier. The outputs of the PSU are considered as two logical instruments. The INSTrument command provides a mechanism to identify and select an output.
When one output is selected, the other output is unavailable for programming until selected. The following commands are affected by the INSTrument command: SOURce, MEASure, and CALibration.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Return
|
Query returns the currently selected output by the INSTrument[:SELect] or INSTrument:NSELect command. The returned value is CH1 or CH2.
|
|
Usage example
|
INST?
CH1
INST:SEL?
CH1
|
|
Related Commands
|
INSTrument:NSELect
|
5.7.2. INSTrument:COUPle:TRACking
|
Syntax
|
INSTrument:COUPle:TRACking {<type>}
INSTrument:COUPle:TRACking?
|
|
Description
|
This command selects how channel’s outputs will be internally connected:
- independent (NONE)
- parallel-tracking (PARallel) controls K_PAR power relay state when max. output current is doubled (e.g. 10 A instead of 5 A), or
- series-tracking (SERies) that controls K_SER power relay state and max. output voltage is doubled (e.g. 80 V instead of 40 V).
When channels are coupled, resulting output will be present on different binding posts as indicated with LED_SP (red) instead of LED_OUT1 (green) and/or LED_OUT2 (green).
Coupled channels will be seen as single channel. Therefore the following commands will affect the both channel regardless of which channel is currently selected using the INSTrument[:SELect] or INSTrument:NSELect command):
- OUTPut[:STATe], OUTPut:DPRog, OUTPut:PROTection:CLEar
- MEASure[:SCALar]:CURRent[:DC], MEASure[:SCALar]:POWer[:DC], MEASure[:SCALar][:VOLTage][:DC]
- SIMUlator:LOAD, SIMUlator:LOAD:STATe
- [SOURce[<n>]]:CURRent, [SOURce[<n>]]:CURRent:STEP, [SOURce[<n>]]:CURRent:TRIGgered, [SOURce[<n>]]:CURRent:LIMit, [SOURce[<n>]]:CURRent:MODE, [SOURce[<n>]]:CURRent:PROTection:DELay, [SOURce[<n>]]:CURRent:PROTection:STATe, [SOURce[<n>]]:CURRent:PROTection:TRIPped?, [SOURce[<n>]]:LIST:COUNt, [SOURce[<n>]]:LIST:CURRent, [SOURce[<n>]]:LIST:DWELl, [SOURce[<n>]]:LIST:VOLTage[:LEVel], [SOURce[<n>]]:LRIPple, [SOURce[<n>]]:LRIPple:AUTO, [SOURce[<n>]]:POWer:LIMit, [SOURce[<n>]]:POWer:PROTection[:LEVel], [SOURce[<n>]]:POWer:PROTection:DELay[:TIME], [SOURce[<n>]]:POWer:PROTection:STATe, [SOURce[<n>]]:POWer:PROTection:TRIPped?, [SOURce[<n>]]:VOLTage, [SOURce[<n>]]:VOLTage:LIMit, [SOURce[<n>]]:VOLTage:STEP, [SOURce[<n>]]:VOLTage:TRIGgered, [SOURce[<n>]]:VOLTage:MODE, [SOURce[<n>]]:VOLTage:PROTection[:LEVel], [SOURce[<n>]]:VOLTage:PROTection:DELay, [SOURce[<n>]]:VOLTage:PROTection:STATe, [SOURce[<n>]]:VOLTage:PROTection:TRIPped?
- TRIGger[:SEQuence][:IMMediate], TRIGger[:SEQuence]:DELay, TRIGger[:SEQuence]:SLOPe, TRIGger[:SEQuence]:SOURce
The following channel specific commands will generate a device specific error 312 when channels are coupled:
- CALibrate,
- OUTPut:TRACk[:STATe],
- SIMUlator:RPOL, SIMUlator:VOLTage:PROGram,
- [SOURce[<n>]]:LRIPple, [SOURce[<n>]]:LRIPple:AUTO
- [SOURce[<n>]]:VOLTage:PROGram,
- [SOURce:]VOLTage:SENSe (series-tracking only)
Channels coupled in parallel could have only one down-programmer circuit active that is on the channel 1. State of the channel 2 down-programmer will always be off regardless of what is set with the OUTPut:DPRog command.
If channels are calibrated (CAL:STAT? 1) a max. value of the channel that has lower calibrated value will be used as a reference and multiplied by two. For example, if channel 1 max. voltage is 39.98 and channel 2 max. voltage is 40.00 the new max. value for the SERies-tracking will become 79.96 V instead of 80.00 V.
Two conditions requires special attention: that is entering CC mode while channels are coupled in SERies or entering CV mode when PARallel coupling is active.
For example when coupled in SERies and output voltage is set to 60 V and current to 1.7 A with connected load of 1 Ω the PSU will enter the CC mode of operation (see OUTPut:MODE?) and output voltage will drop to 1.7 V. Coupling mechanism will set both channels to 30 V (inital value divided by two) but that value cannot be maintained on any output and there is no warranty that new voltage will be equally shared between channels (i.e. 1.7 / 2 = 1.35 V per channel). It’s even possible that outputs become unbalanced in a way that one of the channels becomes negative like -0.6 V on one channel and +2.3 V on another that still resulting in required +1.7 V limited by max. current. To avoid such situation coupling mechanism also include balancing to ensure that such deviation when one channel is pushed to sink instead of source power is rectified. That is accomplished by calculating and set more appropriate output voltage values during the CC mode of operation. The measured output voltage (using the MEASure[:SCALar][:VOLTage][:DC]? Command) will return that newly programmed value, that could be e.g. 30.93 V instead of 60 V. When output come back to CV mode of operation (e.g. load is disconnected), initial set 60 V will be measured again.
Execution of this command also affects bit 8 (PARAlell) or bit 9 (SERies) of the Operation status register (see Section 3.3).
At *RST, channels will be uncoupled (NONE).
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<type>
|
Discrete
|
NONE|PARallel|SERies
|
NONE
|
|
Return
|
Query returns the currently selected output coupling state.
|
|
Usage example
|
INST:COUP:TRAC SER
VOLT 70
VOLT?
70.00
INST:COUP:TRAC PAR
CURR 9
CURR?
9.00
|
|
Errors
|
312,"Cannot execute when the channels are coupled"
|
|
Related Commands
|
*SAV
MEASure[:SCALar]:CURRent[:DC]
MEASure[:SCALar][:VOLTage][:DC]
OUTPut:DPRog
OUTPut:MODE?
OUTPut:TRACk[:STATe]
|
5.7.3. INSTrument:DISPlay:TRACe[<n>]
|
Syntax
|
INSTrument:DISPlay:TRACe[<n>] {<value>}
INSTrument:DISPlay:TRACe[<n>]?
|
|
Description
|
This command sets the output value that will be displayed on the display position (trace) defined with [<n>]. This command affects only display modes 2, 3 and 4 (see the DISPlay:VIEW command).
An attempt to select the same value on both positions (traces) will generate an execution error.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<value>
|
Discrete
|
VOLTage|CURRent|POWer
|
–
|
|
Return
|
Query returns the currently selected displayed output value on the selected display position (trace).
|
|
Usage example
|
INST:DISP:TRAC2?
CURR
|
|
Errors
|
-200,"Execution error"
|
|
Related Commands
|
DISPlay:VIEW
INSTrument:DISPlay:TRACe:SWAP
INSTrument:DISPlay:YT:RATE
|
5.7.4. INSTrument:DISPlay:TRACe:SWAP
|
Syntax
|
INSTrument:DISPlay:TRACe:SWAP
|
|
Description
|
Use this command to swap output values display positions.
|
|
Usage example
|
INST:DISP:TRAC1?
VOLT
INST:DISP:TRAC2?
CURR
INT:DISP:TRAC:SWAP
INST:DISP:TRAC1?
CURR
INST:DISP:TRAC2?
VOLT
|
|
Related Commands
|
DISPlay:VIEW
INSTrument:DISPlay:TRACe[<n>] {<value>}
INSTrument:DISPlay:YT:RATE
|
5.7.5. INSTrument:DISPlay:YT:RATE
|
Syntax
|
INSTrument:DISPlay:YT:RATE {<duration>}
INSTrument:DISPlay:YT:RATE?
|
|
Description
|
This command sets the sample duration in seconds when YT (mode 4, see the DISPlay:VIEW command) display view is selected.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<duration>
|
NR2
|
0.02 – 300
|
0.1
|
|
Return
|
The query command returns the programmed sample duration in seconds.
|
|
Usage example
|
INST:DISP:YT:RATE 10
|
|
Related Commands
|
DISPlay:VIEW
INSTrument:DISPlay:TRACe[<n>] {<value>}
INSTrument:DISPlay:TRACe:SWAP
|
5.7.6. INSTrument:COUPle:TRIGger
|
Syntax
|
INSTrument:COUPle:TRIGger {<mode>}
INSTrument:COUPle:TRIGger?
|
|
Description
|
Not implemented yet
This command defines a coupling between channels trigger systems. Use ALL parameter to couple or NONE to remove coupling.
At *RST, trigger systems are uncoupled.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<mode>
|
Discrete
|
ALL|CH1|CH2|NONE
|
ALL
|
|
Return
|
This query returns the currently coupled output.
|
|
Usage example
|
INST:SEL CH1
VOLT:TRIG 12
CURR:TRIG 1.5
INST:SEL CH2
VOLT:TRIG 5
CURR:TRIG MAX
INST:COUP:TRIG ALL
TRIG:SOUR IMM
INIT
|
|
Related Commands
|
*RST
INSTrument:COUPle:TRACking
|
5.7.7. INSTrument:NSELect
|
Syntax
|
INSTrument:NSELect {<channel>}
INSTrument:NSELect?
|
|
Description
|
This command is used in conjunction with the SELect command. It serves the same purpose, except that it uses a numeric value instead of the identifier used in the SELect command.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
NR1
|
1|2
|
–
|
|
Return
|
When queried it returns the logical instrument number of the currently selected PSU channel. Note that the numbering used for logical instruments directly corresponds to the numbers used in status reporting for multiple instruments; specifically the STATus:QUEStionable:INSTrument and STATus:OPERation:INSTrument commands.
|
|
Usage example
|
INST:NSEL 2
INST:NSEL?
2
|
|
Related Commands
|
STATus:QUEStionable:INSTrument
STATus:OPERation:INSTrument
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.8 - MEASure.html
================================================
5.8. MEASure
Measure commands measure the output voltage, current, power or temperature. They trigger the acquisition of new data before returning the reading. Measurements are performed by digitizing the instantaneous output voltage, current or temperature. Output power is calculated as product of measured voltage and current. Keyword [:DC] is optional since all measurement are by default of the DC level of the signal.
5.8.1. MEASure[:SCALar]:CURRent[:DC]
|
Syntax
|
MEASure[:SCALar]:CURRent[:DC]? [<channel>]
|
|
Description
|
Query the current measured across the current sense resistor inside the PSU.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
Return
|
Returns the average output current in amperes as decimal number (NR2).
|
|
Usage example
|
Measure current on the currently selected channel (CH1) and CH2:
MEAS:CURR?;:MEAS:CURR? CH2
1.23;0.12
|
|
Related Commands
|
INSTrument:COUPle:TRACking
|
5.8.2. MEASure[:SCALar]:POWer[:DC]
|
Syntax
|
MEASure[:SCALar]:POWer[:DC]? [<channel>]
|
|
Description
|
Query the output power calculated as product of measured voltage and current value.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
n/a
|
|
Return
|
Returns the average output power in watts as decimal number (NR2).
|
|
Usage example
|
MEAS:POW? CH2
80.44
|
|
Related Commands
|
|
5.8.3. MEASure[:SCALar]:TEMPerature[:THERmistor][:DC]
|
Syntax
|
MEASure[:SCALar]:TEMPerature[:THERmistor][:DC]? {<sensor>}
|
|
Description
|
Query the temperature measured using the specified temperature sensors as follows:
- AUX – auxiliary temperature sensor connected to Arduino Shield board (can be used to monitor e.g. “ambient” or chassis temperature)
- CH1, CH2 – temperature sensor connected to channel power board used to regulate fan speed (if installed)
- BATT – isolated V/F (Voltage-to-frequency converter) temperature sensor connected to Arduino Shield board (can be used to monitor e.g. connected battery temperature during the charging cycle)
All installed sensors are periodically tested. When sensor does not passed the test, programmed output current is automatically limited to value defined with ERR_MAX_CURRENT constant (conf_advanced.h). If load that draws more current then ERR_MAX_CURRENT value output current will be set to zero.
BATT sensor support is not implemented yet.
|
|
Return
|
Returns the average temperature value in degrees Celsius (oC) as decimal number (NR2). If self-test detect selected temperature sensor failure or sensor is not installed a -240 or -241 error will be generated.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<sensor>
|
Discrete
|
AUX|CH1|CH2|BATT
|
AUX
|
|
Usage example
|
MEAS:TEMP? AUX
39.50
|
|
Errors
|
-240,"Hardware error"
-241,"Hardware missing"
|
|
Related Commands
|
DIAGnostic[:INFOrmation]:FAN?
SYSTem:CPU:OPTion?
SYSTem:TEMPerature:PROTection[:HIGH][:LEVel]
SYSTem:TEMPerature:PROTection[:HIGH]:DELay[:TIME]
SYSTem:TEMPerature:PROTection[:HIGH]:STATe
SYSTem:TEMPerature:PROTection[:HIGH]:TRIPped?
|
5.8.4. MEASure[:SCALar][:VOLTage][:DC]
|
Syntax
|
MEASure[:SCALar][:VOLTage][:DC]? [<channel>]
|
|
Description
|
Query the voltage measured at the sense terminals of the selected channel.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
n/a
|
|
Return
|
Returns the average output voltage in volts as decimal number (NR2).
|
|
Usage example
|
MEAS:VOLT? CH1
43.25
Query voltage of the channel 2 that is currently selected:
INST CH2
MEAS?
12.40
|
|
Related Commands
|
INSTrument:COUPle:TRACking
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 5.9 - MEMory.html
================================================
5.9. MEMory
The MEMory subsystem works with PSU state files that are saved to (*SAV) and recalled from (*RCL) non-volatile storage locations numbered 0 through 9. The storage location 0 named “Power down state” is used to store the current PSU parameters.
|
|
|
|
MEMory
|
|
|
:NSTates?
|
Returns total number of state storage memory locations
|
|
:STATe
|
|
|
:CATalog?
|
Lists the names associated with all ten state storage locations
|
|
:DELete {<profile>}
|
Deletes the contents of a state storage location
|
|
:ALL
|
Deletes the contents of all state storage locations
|
|
:NAME {<profile>}, {<name>}
|
Assigns a custom name to a state storage locations
|
|
:RECall
|
|
|
:AUTO {<bool>}
|
Specifies whether the power-down state is recalled from location 0 on power-on
|
|
:SELect {<profile>}
|
Specifies which PSU state will be used at power on
|
|
:VALid? {<profile>}
|
Determines whether a storage location contains a valid state
|
5.9.1. MEMory:NSTates
|
Syntax
|
MEMory:NSTates?
|
|
Description
|
Returns the total number of *SAV/*RCL states available in the PSU.
|
|
Return
|
Returns numeric value (NR1) which is one greater than the maximum that can be sent as a parameter to the *SAV and *RCL commands.
|
|
Usage example
|
MEM:NST?
10
|
5.9.2. MEMory:STATe:CATalog
|
Syntax
|
MEMory:STATe:CATalog?
|
|
Description
|
This query requests a list of defined names in the MEMory:STATe subsystem.
|
|
Return
|
The PSU returns a list of defined <name>’s in a comma separated list. Each <name> is returned in a quoted string.
|
|
Usage example
|
MEM:STAT:CAT?
"Power down state", "All outputs on", "dual 15V/300mA", "Power protection at 100W", "--Not used--", "--Not used--", "--Not used--", "--Not used--", "--Not used--", "--Not used--"
|
|
Related Commands
|
MEMory:STATe:NAME
|
5.9.3. MEMory:STATe:DELete
|
Syntax
|
MEMory:STATe:DELete {<profile>}
MEMory:STATe:DELete:ALL
|
|
Description
|
When used with a profile number this command deletes the contents of the specified storage location. The MEMory:STATe:DELete:ALL deletes the contents of storage locations 1 through 9.
An error is generated on an attempt to recall a deleted state.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<profile>
|
NR1
|
1 – 9
|
–
|
|
Return
|
None
|
|
Usage example
|
MEM:STAT:DEL 2
|
|
Related Commands
|
*RCL
*SAV
|
5.9.4. MEMory:STATe:NAME
|
Syntax
|
MEMory:STATe:NAME {<profile>}, {<name>}
MEMory:STATe:NAME? {<profile>}
|
|
Description
|
This command associates a <name> with a *SAV/*RCL register number. May assign same name to different locations and state names are unaffected by *RST. Deleting a storage location's contents MEMory:STATe:DELete resets associated name to “--Not used--”
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<profile>
|
NR1
|
1 – 9
|
–
|
|
<name>
|
Quoted string
|
0 to 32 characters
|
–
|
|
Return
|
Returns a *SAV/*RCL register number associates with profile number.
|
|
Usage example
|
MEM:STAT:DEF, 2, "All outputs on"
MEM:STAT:DEF? 2
"All outputs on"
|
|
Related Commands
|
MEMory:STATe:DELete
|
5.9.5. MEMory:STATe:RECall:AUTO
|
Syntax
|
MEMory:STATe:RECall:AUTO {<bool>}
MEMory:STATe:RECall:AUTO?
|
|
Description
|
This command disables or enables the automatic recall of a specific stored PSU state selected using the MEMory:STATe:RECall:SELect command when power is turned on.
Select ON to automatically recall one of the ten stored states or the “power-down” state (location 0) when power is turned on. Select OFF to issue a reset (*RST) when power is turned on.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
–
|
|
Return
|
The query command returns 0 (OFF) or 1 (ON).
|
|
Usage example
|
MEM:STAT:REC:AUTO?
1
|
|
Related Commands
|
*SAV
MEMory:STATe:RECall:SELect
SYSTem:POWer
|
5.9.6. MEMory:STATe:RECall:SELect
|
Syntax
|
MEMory:STATe:RECall:SELect {<profile>}
MEMory:STATe:RECall:SELect?
|
|
Description
|
This command selects which PSU state will be used at power on if the automatic recall mode is enabled (see MEMory:STATe:RECall:AUTO ON command). If the automatic recall mode is disabled (MEMory:STATe:RECall:AUTO OFF), then a “factory reset” (return to the default values) is issued when power is turned on.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<profile>
|
NR1
|
0 – 9
|
–
|
|
Return
|
The query command returns numeric value (NR1) for 0 to 9 indicating which instrument state will be used at power on.
|
|
Usage example
|
MEM:STAT:REC:SEL?
2
|
|
Related Commands
|
*SAV
MEMory:STATe:RECall:AUTO
SYSTem:POWer
|
5.9.7. MEMory:STATe:VALid
|
Syntax
|
MEMory:STATe:VALid? {<profile>}
|
|
Description
|
This command queries the specified storage location to determine if a valid state is currently stored in this location.
Use this command before sending the *RCL command to determine if a valid state has been previously stored on queried location.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<profile>
|
NR1
|
0 – 9
|
–
|
|
Return
|
Returns 0 if no state has been stored or if it has been deleted. It returns 1 if a valid state is stored in this location.
|
|
Usage example
|
MEM:STAT:VAL? 2
1
|
|
Related Commands
|
*RCL
*SAV
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 6 - Device-specific commands.html
================================================
6. Device-specific (unclassified) commands
The commands in this section are specific to the PSU, and so are not included in the 1999.0 version of the SCPI standard. However, these commands are designed with the SCPI standard in mind, and they follow all of the command syntax rules defined by the standard.
6.1.1. APPLy
The APPLy command provides the most straightforward method to program the PSU remotely.
|
Syntax
|
APPLy {<channel>}, {<voltage>} [, <current>]
APPLy? {<channel>} [, <query param>]
|
|
Description
|
This command is a combination of the INSTrument:SELect (or INSTrument:NSELect), [SOURce[<n>]]:VOLTage and [SOURce[<n>]]:CURRent commands.
The APPLy changes the PSU’s output to the newly programmed values only if the programmed values are valid within the presently selected PSU operating range. An execution error will occur if the programmed values are not valid within the selected range. You can substitute MINimum, MAXimum, or DEFault in place of a specific value for the voltage and current parameters (see table below).
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<channel>
|
Discrete
|
CH1|CH2
|
–
|
|
<voltage>
|
NR2|Discrete
|
0 to MAXimum, MIN|DEF|MAX|UP|DOWN
The MAXimum value is dependent on the PSU voltage rating. See Section 8.1
|
–
|
|
<current>
|
NR2|Discrete
|
0 to MAXimum, MIN|DEF|MAX|UP|DOWN
The MAXimum value is dependent on the PSU current rating. See Section 8.1
|
–
|
|
<query param>
|
Discrete
|
CURR|VOLT
|
–
|
|
Return
|
APPLy? query the voltage/current of the specified channel.
|
|
Usage example
|
Set the voltage and current of CH1 to 35.5V and 0.5A respectively:
APPL CH1,35.5,0.5
Query the voltage and current settings of the first channel:
APPL? CH1
CH1:50V/3A, 35.500, 0.500
Query only current setting of the second channel:
APPL? CH2, CURR
0.25
|
|
Errors
|
-221,"Power limit exceeded"
-222,"Data out of range"
|
|
Related Commands
|
INSTrument:NSELect
INSTrument[:SELect]
[SOURce[<n>]]:VOLTage[:LEVel][:IMMediate][:AMPLitude]
[SOURce[<n>]]:CURRent[:LEVel][:IMMediate][:AMPLitude]
TRIGger[:SEQuence]:SOURce
|
6.1.2. DEBUg
|
Syntax
|
DEBUg?
|
|
Description
|
Use this command to collect various runtime information that can be used in debugging process.
|
|
Usage example
|
DEBU?
CH1 U_DAC = 0
CH2 U_DAC = 32768
CH1 U_MON = 0
CH2 U_MON = 4095
CH1 U_MON_DAC = 0
CH2 U_MON_DAC = 16383
CH1 I_DAC = 39321
CH2 I_DAC = 6554
CH1 I_MON = 0
CH2 I_MON = 3276
CH1 I_MON_DAC = 19660
CH2 I_MON_DAC = 3276
AUX TEMP = 373
CH1 TEMP = 561
CH2 TEMP = 373
MAIN_LOOP_DURATION = 15998 16696 17409 / 0 0 0 / 1844 346805388
ADC_COUNTER = 120 / 0 / 296
|
|
Related Commands
|
DIAGnostic[:INFOrmation]:ADC?
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 7 - Error messages.html
================================================
7. Error messages
The system-defined error/event numbers are chosen on an enumerated (“1 of N”) basis. The SCPI-defined error/event numbers and the <error/event_description> portions of the full queue item are listed here. The first error/event described in each class (for example, -100, -200, -300, -400) is a “generic” error.
7.1. Command Error [-199, -100]
An <error/event number> in the range [-199, -100] indicates that a syntax error has been detected by the PSU’s SCPI command parser. The occurrence of an error in this class cause the command error bit (CME, bit 5) in the Standard Event Status Register (see Section 3.1) to be set.
|
|
|
|
0,"No error"
|
The queue is completely empty. Every error/event in the queue has been read, or the queue was purposely cleared by a power-on event, *CLS, etc.
|
|
−100,"Command error"
|
Generic syntax error.
|
|
-101,"Invalid character"
|
An invalid character was found in the command string. There may be a character such as #, $, or % in the command keyword or within a parameter.
Example:
OUTP:STAT #ON
|
|
-103,"Invalid separator"
|
An invalid separator was found in the command string. There may be a comma instead of a colon, semicolon, or blank space, or a blank space instead of a comma.
Example:
TRIG:SOUR,BUS
|
|
-104,"Data type error"
|
The wrong parameter type was found in the command string. A string might have been sent when a string was expected, or vice versa.
Example (the password must be a quoted string):
CAL ON, 123
|
|
-108,"Parameter not allowed"
|
More parameters were received than expected for the command. There may be an extra parameter, or parameter added to a command that does not accept a parameter.
Example:
INST CH1, CH2
|
|
-109,"Missing parameter"
|
Fewer parameters were received than expected for the command. One or more parameters that are required for this command was not received.
Example:
APPL
|
|
-113,"Undefined header"
|
A command was received that is not valid for this PSU. The command may have been misspelled, or it may not be a valid command. Short forms of commands, may contain up to four letters.
Example:
MEASU:CURR?
|
|
-114,"Header suffix out of range"
|
The numeric suffix attached to a command header is not one of the allowable values.
Example:
STAT:QUES:INST:ISUM3?
|
|
-131,"Invalid suffix"
|
A suffix was incorrectly specified for a numeric parameter. It may have been misspelled.
Example (use A instead of V):
VOLT 3A
|
|
-138,"Suffix not allowed"
|
A suffix was received following a numeric parameter which does not accept a suffix.
Example (SEC is not a valid suffix):
STAT:QUES:ENAB 10 SEC
|
|
-151,"Invalid string data"
|
An invalid character string was received. Check to see if you have enclosed the character string in single or double quotes.
Example:
DISP:TEXT ’ON
|
7.2. Execution Error [-299, -200]
An <error/event number> in the range [-299, -200] indicates an error has been detected by the PSU’s execution control block. The occurrence of any error in this class sets the execution error bit (EXE, bit 4) in the Standard Event Status Register (see Section 3.1). One of the following events has occurred:
- A <PROGRAM DATA> element following a header was evaluated by the PSU as outside of its legal input range, or as otherwise inconsistent with the PSU’s capabilities.
- A valid program message could not be properly executed. Probably due to some PSU condition.
Execution errors will be reported by the PSU after rounding and expression evaluation has taken place. Rounding a numeric data element, for example, will not be reported as an execution error. Events that generate execution errors will not generate Command Errors, device-specific errors, or Query Errors; see the other error definitions in this section.
|
|
|
|
-200,"Execution error"
|
This is the generic execution error when more specific error is not assigned in the case that command execution failed.
|
|
-221,"Settings conflict"
|
Indicates that a legal program data element was parsed but could not be executed due to the current device state.
Example (an attempt to enter low ripple mode while remote programming is activated):
VOLT:PROG EXT
LRIP ON
|
|
-222,"Data out of range"
|
A numeric parameter value is outside the valid range for the command.
Example:
VOLT 166
|
|
-223,"Too much data"
|
A character string was received but could not be executed because the string length was more than 32 characters. This error can be generated by the CALibration:REMark command.
|
|
-224,"Illegal parameter value"
|
A discrete parameter was received which was not a valid choice for the command. You may have used an invalid parameter choice.
Example:
VOLT ON
|
|
-230,"Digital pin function mismatch"
|
Operation with digital pin is not possible due to incorrect function definition.
Example:
DIG:PIN1:FUNC INH
DIG:INP:DATA? 1
|
|
-240,"Hardware error"
|
Command or query could not be executed because failure is detected during power-up self-test. Use the *TST? command to query self-test results. See also Section 7.3.1
|
|
-241,"Hardware missing"
|
Command or query could not be executed because of missing PSU hardware.
Example (remote sense cannot be activated when BP_OPTION is false):
OUTP:SENS ON
|
|
-242,"CH1 fault detected"
|
A POWERGOOD signal failure has been detected on Channel 1. If such a condition has happened, PSU firmware will be immediately put into the stand-by mode.
|
|
-243,"CH2 fault detected"
|
A POWERGOOD signal failure has been detected on Channel 2. If such condition has happened, the PSU firmware will be immediately put into the stand-by mode.
|
|
-245,"CH1 output fault detected"
|
A prohibited state has been detected on the Channel 1 output (e.g., negative power is measured for extended period of time). The Channel 1 output will be turned off.
|
|
-246,"CH2 output fault detected"
|
A prohibited state has been detected on the Channel 2 output (e.g., negative power is measured for extended period of time). The Channel 2 output will be turned off.
|
|
-250,"Mass storage error"
|
Indicates that a SD card error occurred. This error message is generated when the firmware cannot detect the more specific errors described for errors -251 through -258.
|
|
-251,"Missing mass storage"
|
Command or query could not be executed because of missing mass storage; SD card option was not installed. (Not implemented yet)
|
|
-252,"Missing media"
|
Command or query could not be executed because of a missing SD card. (Not implemented yet)
|
|
-253,"Corrupt media"
|
Command or query could not be executed because of corrupt media; for example, bad SD card or wrong format. (Not implemented yet)
|
|
-254,"Media full"
|
Command or query could not be executed because the SD card is full. (Not implemented yet)
|
|
-256,"File name not found"
|
Command or query could not be executed because the file name on the device media was not found; for example, an attempt was made to read or copy a nonexistent file.
|
|
-257,"File name error"
|
Command or query could not be executed because the file name on the device media was in error; for example, an attempt was made to copy to a duplicate file name.
|
|
-258,"Media protected"
|
Command or query could not be executed because the SD card access is locked (MMEMory:LOCK command).
|
|
-259,"File transfer aborted"
|
Command or query for file transfer is aborted before transfer is completed.
|
7.3. Device-Specific Error [-399, -300], [1, 32767]
An <error/event number> in the range [-399, -300] or [1, 32767] indicates that the PSU has detected an error which is not a command error, a query error, or an execution error. Most likely, some PSU operations did not properly complete, possibly due to an abnormal hardware or firmware condition. These codes are also used for self-test response errors. The occurrence of any error in this class sets the device-specific error bit (DDE, bit 3) in the Standard Event Status Register (see Section 3.1).
Events that generate device-specific errors do not generate command errors, execution errors, or query errors; see the other error definitions in this section.
|
|
|
|
-211,"Trigger ignored"
|
A *TRG was received but the trigger was ignored. The trigger source should be set to the BUS and the trigger subsystem should be initiated by the INITiate[:IMMidate] command.
|
|
-213,"Init ignored"
|
An INITiate command was received but could not be executed because a measurement was already in progress.
|
|
-220,"Cannot set range"
|
The measurement range cannot be set because the currently measured value is higher then range max value.
Example:
CURR?
2.33
SENS:CURR:RANG 0.5
|
|
-310,"System error"
|
An internal firmware error has been detected.
|
|
-330,"Self-test failed"
|
The PSU’s complete self-test failed from the remote interface (*TST? command). In addition to this error, more specific self-test errors are also reported. See also Section 7.3.1
|
|
-350,"Queue overflow"
|
The error queue is full because more than 16 errors have occurred. No additional errors will be stored until errors have been removed from the queue. The error queue is cleared when power has been turned off, or after a *CLS (clear status) command has been executed.
|
|
-363,"Input buffer overrun"
|
Input buffer overrun. The Serial or Ethernet port input buffer has lost data due to an overflow.
|
|
100,"Channel not found"
|
A non existing channel number has been specified.
Example:
SOUR3:VOLT?
|
|
101,"Calibration mode is off"
|
Calibration is not enabled. The PSU will not accept calibration commands.
|
|
102,"Invalid password"
|
The calibration password is incorrect.
|
|
104,"Bad sequence of cal commands"
|
Calibration commands have not been entered in the proper sequence.
|
|
105,"Password too long"
|
A calibration password was received which contained more than 16 characters.
|
|
106,"Password too short"
|
A calibration password was received which contained less than 4 characters.
|
|
107,"Cal value out of range"
|
The specified calibration value (CALibration:CURRent:DATA or CALibration:VOLTage:DATA) is not valid for the PSU's present measurement function and range.
|
|
108,"Cal output disabled"
|
The Calibration operation has been aborted by sending the OUTPut OFF command during an output calibration.
|
|
109,"Invalid cal data"
|
One or more calibration data values are impossible or out of range, and will prohibit the calibration parameters calculation.
For example the MID value is lower then MIN, or the MIN value is higher then MAX, or the MID value is so out of accepted tolerance that it cannot be predicted with newly calculated calibration parameters.
|
|
110,"Cal params missing or corrupted"
|
Calibration parameters activation started by the CALibration:STATe ON, "<password>" command failed because calibration has never been conducted or existing parameters are corrupted.
|
|
111,"No new cal data exists"
|
There was an attempt to save calibration data with the CALibration:SAVE command without calibration data.
|
|
150,"Power limit exceeded"
|
The product of voltage and current exceeds channel power limitation.
For example if channel power limit is 160 W and the following sequence is executed:
VOLT 38
CURR 4.4
|
|
151,"Voltage limit exceeded"
|
Set voltage exceeds channel capability.
Example:
VOLT 60
|
|
152,"Current limit exceeded"
|
Set current exceeds channel capability.
Example:
CURR 5.5
|
|
201,"Cannot execute before clearing protection"
|
Example: a command such as OUTP ON cannot be executed on a channel where one or more protections will be tripped.
|
|
270,"CH1 ADC timeout detected"
|
Channel 1 has been switched off after 3 consecutive ADC timeouts were detected.
|
|
304,"Incompatible transient modes"
|
For example, VOLTage and CURRent cannot be in both STEP and LIST modes at the same time (see [SOURce[<n>]]:CURRent:MODE and [SOURce[<n>]]:VOLTage:MODE)
|
|
306,"Too many list points"
|
Too many list points have been specified.
|
|
307,"List lengths are not equivalent"
|
One or more lists are not the same length.
For example, number of CURRent steps is not equal to one or number of VOLTage steps
LIST:VOLT 0, 5, 10, 15, 20
LIST:CURR 1, 2
|
|
308,"Cannot be changed while transient trigger is initiated"
|
An attempt to change a setting which cannot be changed while the instrument is waiting for or executing a trigger sequence.
|
|
309,"Cannot initiate while in fixed mode"
|
Cannot initiate transient generator. Either the VOLTage or CURRent function is set to FIXed mode.
|
|
310,"List not found"
|
A list cannot be found on the SD card.
|
|
311,"List is empty"
|
A list cannot be started because it’s empty.
|
|
312,"Cannot execute when the channels are coupled"
|
Cannot execute a command when the channel outputs are coupled.
|
|
313,"Cannot execute in tracking mode"
|
Cannot execute a command when the tracking mode is active.
|
|
320,"Firmware update error"
|
An attempt to upload firmware via LAN has failed due to communication error, checksum error, etc. (Not implemented yet).
|
|
400,"Cannot load empty profile"
|
An attempt has been made to recall an empty or erased user profile with *RCL command.
|
|
500,"Down-programmer on CH1 switched off"
|
The down programmer has been switched off because a negative output power (DP_NEG_LEV) has been measured on Channel 1 that has lasted more then DP_NEG_DELAY seconds.
|
|
501,"Down-programmer on CH2 switched off"
|
The down programmer has been switched off because a negative output power (DP_NEG_LEV) has been measured on Channel 2 that has lasted more then DP_NEG_DELAY seconds.
|
|
505,"External voltage on CH1 detected"
|
An external voltage has been measured (e.g., from a battery or other power source intentionally or mistakenly left connected) on Channel 1 while output is switched from off to on. (Not implemented yet).
|
|
506,"External voltage on CH2 detected"
|
An external voltage has been measured (e.g., from a battery or other power source intentionally or mistakenly left connected) on Channel 2 while output is switched from off to on. (Not implemented yet).
|
|
615,"External EEPROM save failed"
|
If non-volatile memory (an external EEPROM) is not installed, damaged or not responsive, and OPTION_EXT_EEPROM is set to 1 (conf.h) this error will be reported.
|
7.3.1. Self-Test Error Messages
During power-up, the PSU will start self-test sequences when communication with all SPI devices that is marked as installed will be established. The scope of the self-test depends on device capability and it could vary from simply reading device registers, and waiting for expected responses to more complex operations such as setting DAC registers and reading back those values using the ADC (if ADC test passed). Every test failure will be announced by an error beep, and one error message per failed test will be inserted into the error queue. The device-specific error bit (DDE, bit 3) in the Standard Event Status Register (see Section 3.1) will also be set.
|
|
|
|
210,"CH1 IOEXP test failed"
|
Communication with the Channel 1 I/O expander is not possible. Probably because the I/O expander is not functional.
|
|
211,"CH2 IOEXP test failed"
|
Communication with the Channel 2 I/O expander is not possible. Probably because the I/O expander is not functional.
|
|
220,"CH1 ADC test failed"
|
Communication with the Channel 1 ADC is not possible. Probably because values written into various registers are not equal to the returned values.
|
|
221,"CH2 ADC test failed"
|
Communication with the Channel 2 ADC is not possible. Probably because values written into various registers are not equal to the returned values.
|
|
230,"CH1 DAC test failed"
|
The Channel 1 DAC is not functional. Possibly because communication has failed, or because there's a difference between the test voltage data sent to the Channel 1 DAC and that read back.
|
|
231,"CH2 DAC test failed"
|
The Channel 2 DAC is not functional. Possibly because communication has failed, or because there's a difference between the test voltage data sent to the Channel 2 DAC and that read back.
|
|
240,"External EEPROM test failed"
|
The non-volatile memory on the Arduino board has failed the checksum integrity test.
|
|
250,"RTC test failed"
|
The RTC (real time clock) on the Arduino board is not present, or the date or time values returned are not valid, or the last datetime value stored into non-volatile memory is greater then RTC datetime.
|
|
260,"Ethernet test failed"
|
The Ethernet controller on the Arduino Shield board test failed.
|
|
630,"Fan test failed"
|
The measured fan speed during the self-test procedure is not within expected range.
|
For example, if SPI-bus cable is accidentally not connected, or wrongly wired, on Channel 1 two errors will be generated and placed into the error queue which can be checked using the following command sequence:
SYST:ERR:COUN?
2
SYST:ERR?
210,"CH1 IOEXP test failed"
SYST:ERR?
220,"CH1 ADC test failed"
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 8 - Parameters and settings.html
================================================
8. Parameters and settings
8.1. Programming parameters
The PSU firmware can be used to control its channels with various characteristics. For example, the voltage range could be set from 0 to 30 V, 0 to 40 V or 0 to 50 V, and the current range could vary from 0 to 3.12 A, 0 to 4.16 A or 0 to 5 A. It’s also possible to mix two channels with different voltage and current ranges e.g. 0 – 40 V/0 – 5 A and 0 – 50 V/0 – 3.12 A. Use the *IDN? command to find out what channels are defined in the PSU's firmware.
8.1.1. Voltage
|
|
|
|
|
|
MAXimum [V]
|
30
|
40
|
50
|
|
MINimum [V]
|
0
|
0
|
0
|
|
DEFault [V]
|
0
|
0
|
0
|
|
Value after *RST or *TST?
|
0
|
0
|
0
|
|
STEP MINimum [V]
|
10m
|
10m
|
10m
|
|
STEP MAXimum [V]
|
5
|
5
|
5
|
|
STEP DEFault [V]
|
100m
|
100m
|
100m
|
|
PROTection DELay MINimum [s]
|
0
|
0
|
0
|
|
PROTection DELay MAXimum [s]
|
10
|
10
|
10
|
|
PROTection DELay DEFault [s]
|
5m
|
5m
|
5m
|
|
CALibration VALue MINimum[V]
|
0.15
|
0.15
|
0.15
|
|
CALibration VALue MIDdle[V]
|
14.1
|
19.1
|
24.1
|
|
CALibration VALue MAXimum[V]
|
28
|
38
|
48
|
8.1.2. Current
|
|
|
|
|
MAXimum [A]
|
3.12
|
5
|
|
MINimum [A]
|
0
|
0
|
|
DEFault [A]
|
0
|
0
|
|
Value after *RST or *TST?
|
0
|
0
|
|
STEP and STEP MINimum [A]
|
10m
|
10m
|
|
STEP MAXimum [A]
|
1
|
1
|
|
STEP DEFault [A]
|
50m
|
50m
|
|
PROTection DELay MINimum [s]
|
0
|
0
|
|
PROTection DELay MAXimum [s]
|
10
|
10
|
|
PROTection DELay DEFault [s]
|
20m
|
20m
|
|
CALibration VALue MINimum[A]
|
50m
|
50m
|
|
CALibration VALue MIDdle[A]
|
1.525
|
2.425
|
|
CALibration VALue MAXimum[A]
|
3
|
4.8
|
8.1.3. Power
The total number of possible combinations for the PSU's power parameters is 6, of which two typical examples are given below:
|
|
|
|
|
MINimum [W]
|
0
|
0
|
|
DEFault [W]
|
100
|
155
|
|
MAXimum [W]
|
150
|
160
|
|
PROTection LEVel DEFault [W]
|
100
|
155
|
|
PROTection DELay MINimum [s]
|
1
|
1
|
|
PROTection DELay MAXimum [s]
|
300
|
300
|
|
PROTection DELay DEFault [s]
|
10
|
10
|
8.2. Reset Settings (*RST)
At power-on or after execution of the *RST common command, device settings will be set to the states listed in the following table. See also the MEMory:STATe:RECall:AUTO command.
|
|
|
|
|
*ESE
|
0
|
Not affected
|
|
*ESR
|
0
|
Not affected
|
|
*SRE
|
0
|
Not affected
|
|
*STB?
|
0
|
???
|
|
CAL[:MODE]
|
OFF
|
|
CAL:STAT
|
ON if valid calibrating data for both voltage and current exists in the non-volatile memory, otherwise OFF.
|
|
DISP:BRIG
|
Power down state
|
20
|
|
DISP:VIEW
|
Power down state
|
1
|
|
DISP[:STAT]
|
Power down state
|
Not affected
|
|
INST:NSEL
|
1
|
|
INST:SEL
|
CH1
|
|
MEMM:CDIR
|
/
|
|
MEMM:DOWN:FNAM
|
""
|
|
MMEM:LOCK
|
Power down state
|
Not affected
|
|
OUTP[:STAT]
|
Power down state
|
OFF
|
|
OUTP:PROT:COUP
|
Power down state
|
OFF
|
|
OUTP:TRAC
|
Power down state
|
OFF
|
|
SENS:CURR:RANG
|
Power down state
|
DEF (Best)
|
|
SENS:CURR:RANG:AUTO
|
Power down state
|
ON
|
|
SENS:DLOG:FUNC:CURR
|
Power down state
|
OFF
|
|
SENS:DLOG:FUNC:POW
|
Power down state
|
OFF
|
|
SENS:DLOG:FUNC:VOLT
|
Power down state
|
OFF
|
|
SENS:DLOG:PER
|
Power down state
|
0.02
|
|
SENS:DLOG:TIME
|
Power down state
|
60
|
|
[SOUR[n]]:CURR
|
Power down state
|
DEF (see Section 8.1)
|
|
[SOUR[n]]:CURR:PROT:DEL
|
Power down state
|
DEF (see Section 8.1)
|
|
[SOUR[n]]:CURR:PROT:STAT
|
Power down state
|
OFF
|
|
[SOUR[n]]:CURR:PROT:TRIP?
|
0
|
|
[SOUR[n]]:CURR:STEP
|
Power down state
|
DEF (see Section 8.1)
|
|
[SOUR[<n>]]:LRIP:AUTO
|
Power down state
|
Not affected
|
|
[SOUR[n]]:POW:PROT[:LEV]
|
Power down state
|
DEF (see Section 8.1)
|
|
[SOUR[n]]:POW:PROT:DEL
|
Power down state
|
DEF (see Section 8.1)
|
|
[SOUR[n]]:POW:PROT:STAT
|
Power down state
|
ON
|
|
[SOUR[n]]:POW:PROT:TRIP?
|
0
|
|
[SOUR[n]]:VOLT
|
Power down state
|
DEF (see Section 8.1)
|
|
[SOUR[<n>]]:VOLT:PROG[:SOUR]
|
INT
|
|
[SOUR[n]]:VOLT:PROT:DEL
|
Power down state
|
DEF (see Section 8.1)
|
|
[SOUR[n]]:VOLT:PROT:STAT
|
Power down state
|
OFF
|
|
[SOUR[n]]:VOLT:PROT:TRIP?
|
0
|
|
[SOUR[n]]:VOLT:STEP
|
Power down state
|
DEF (see Section 8.1)
|
|
[SOUR[<n>]]:VOLT:SENS[:SOUR]
|
Power down state
|
OFF
|
|
STAT:OPER[:EVEN]
|
0
|
Not affected
|
|
STAT:OPER:COND
|
0
|
Not affected
|
|
STAT:OPER:ENAB
|
0
|
Not affected
|
|
STAT:OPER:INST[:EVEN]
|
0
|
Not affected
|
|
STAT:OPER:INST:COND
|
0
|
Not affected
|
|
STAT:OPER:INST:ENAB
|
0
|
Not affected
|
|
STAT:OPER:INST:ISUM[:EVEN]
|
0
|
Not affected
|
|
STAT:OPER:INST:ISUM:COND
|
0
|
Not affected
|
|
STAT:OPER:INST:ISUM:ENAB
|
0
|
Not affected
|
|
STAT:QUES[:EVEN]
|
0
|
Not affected
|
|
STAT:QUES:COND
|
0
|
Not affected
|
|
STAT:QUES:ENAB
|
0
|
Not affected
|
|
STAT:QUES:INST[:EVEN]
|
0
|
Not affected
|
|
STAT:QUES:INST:COND
|
0
|
Not affected
|
|
STAT:QUES:INST:ENAB
|
0
|
Not affected
|
|
STAT:QUES:INST:ISUM[:EVEN]
|
0
|
Not affected
|
|
STAT:QUES:INST:ISUM:COND
|
0
|
Not affected
|
|
STAT:OPER:INST:ISUM:ENAB
|
0
|
Not affected
|
|
SYST:CHAN:INFO:ONT:LAST?
|
0
|
|
SYST:CHAN:INFO:ONT:TOT?
|
Power down state
|
Not affected
|
|
SYST:CPU:INFO:ONT:LAST?
|
0
|
|
SYST:CPU:INFO:ONT:TOT?
|
Power down state
|
Not affected
|
|
SYST:ERR:COUN?
|
0
|
|
SYST:POW
|
Power down state
|
ON
|
|
SYST:TEMP:PROT [AUX]
|
Power down state
|
55
|
|
SYST:TEMP:PROT:DEL [AUX]
|
Power down state
|
30
|
|
SYST:TEMP:PROT:STAT [AUX]
|
Power down state
|
ON
|
|
SYST:TEMP:PROT CH1|CH2
|
Power down state
|
75
|
|
SYST:TEMP:PROT:DEL CH1|CH2
|
Power down state
|
30
|
|
SYST:TEMP:PROT:STAT CH1|CH2
|
Power down state
|
ON
|
|
TRIG:DEL
|
Power down state
|
0
|
|
TRIG:SLOP
|
Power down state
|
POS
|
|
TRIG:SOUR
|
Power down state
|
IMM
|
|
TRIG:SOUR:DLOG
|
Power down state
|
IMM
|
8.3. Special modes of operation
Operations will differ when tracking or any of coupling modes between channels have been selected. Please note that some of features must be disabled because they are impossible for the PSU hardware or its software. The following table shows how special modes of operation affects some features:
|
|
|
|
|
|
|
|
|
TRACking
|
Disabled
|
|
|
Disabled
|
|
Disabled
|
|
Coupled in PARallel
|
Disabled
|
|
|
Disabled
|
Disabled
|
|
|
Coupled in SERies
|
Disabled
|
Disabled
|
Disabled
|
Disabled
|
Disabled
|
|
8.4. Default settings (in the distributed firmware)
|
|
|
|
|
Over-current protection (OCP)
|
OFF
|
CURR:PROT:STAT
|
|
Over-voltage protection (OVP)
|
OFF
|
VOLT:PROT:STAT
|
|
Over-power protection (OPP)
|
ON
|
POW:PROT:STAT
|
|
OPP trip level
|
155.00 W
|
POW:PROT:TRIP
|
|
OPP delay
|
10 s
|
POW:PROT:DEL
|
|
Channel Over-temperature protection (OTP)
|
ON
|
SYST:TEMP:PROT:STAT
|
|
Channel OTP trip level
|
75.00 oC
|
SYST:TEMP:PROT:TRIP
|
|
Channel OTP delay
|
30 s
|
SYST:TEMP:PROT:DEL
|
|
AUX sensor OTP
|
ON
|
SYST:TEMP:PROT:STAT AUX
|
|
AUX sensor OTP trip level
|
50 oC
|
SYST:TEMP:PROT:TRIP AUX
|
|
AUX sensor OTP delay
|
10 s
|
SYST:TEMP:PROT:DEL AUX
|
|
Shutdown when protection tripped
|
OFF
|
SYST:POW:PROT:TRIP
|
|
Switch off all outputs when protection tripped
|
OFF
|
OUTP:PROT:COUP
|
|
Low ripple mode
|
OFF
|
LRIP
|
|
Remote voltage programming
|
OFF
|
VOLT:PROG
|
|
Remote voltage sense
|
OFF
|
VOLT:SENS
|
|
Coupling mode
|
NONE
|
INST:COUP:TRAC
|
|
Tracking mode
|
OFF
|
OUTP:TRAC
|
|
Calibration password
|
eezpsu
|
CAL:PASS:NEW
|
|
System password
|
Not defined
|
SYST:PASS:NEW
|
|
Communication mode
|
Local
|
SYST:LOC
|
|
Front panel lock
|
OFF
|
SYST:KLOC
|
|
Front panel display
|
ON
|
DISP:STAT
|
|
Ethernet communication
|
OFF
|
SYST:COMM:ENAB 0, ETH
|
|
Force disabling of all outputs on power up
|
OFF
|
SYST:PON:OUTP:DIS
|
|
Beeper
|
ON
|
SYST:BEEP:STAT
|
|
“Key pressed” click tone
|
OFF
|
SYST:BEEP:KEY:STAT
|
|
Ethernet port communication
|
5025
|
SYST:COMM:ETH:PORT
|
|
Ethernet MAC
|
74-69-69-2D-30-00
|
SYST:COMM:ETH:MAC
|
|
Serial port communication
|
OFF
|
SYST:COMM:ENAB 0, SER
|
|
Serial port speed
|
9600
|
SYST:COMM:SER:BAUD
|
|
Serial port parity bit
|
NONE
|
SYST:COMM:SER:PAR
|
|
NTP service
|
OFF
|
SYST:COMM:ENAB 0, NTP
|
|
NTP server
|
europe.pool.ntp.org
|
SYST:COMM:NTP
|
================================================
FILE: doc/SCPI reference guide/Commands/EEZ PSU SCPI reference 9 - Software simulator.html
================================================
9. Software simulator
The PSU firmware can be compiled and executed on a Windows, Linux or OS X system. The software simulator is a terminal application that can respond to any currently supported SCPI command described in this document. SCPI commands could be entered directly in the simulator’s terminal window (Fig. 1) or remotely by using the e.g. a Telnet client (Fig. 2).
Fig. 1: Simulator welcome screen
Fig. 2: Remote connection using a telnet client
The simulator also has an internal GUI. When started, open a separate window with the picture of the PSU front panel. The GUI depends of which PSU revision is used that can be set in conf_user_revision.h file before simulator compilation.
Fig. 3: Simulator GUI for portrait front panel (r1B9)
Fig. 4: Simulator GUI for landscape front panel (r3B4)
The GUI simulator front panel currently displays only changes in LED indicators and indicates whether load is applied on the output terminals or not. For example if an 8.2 Ohm load is connected to channel 2 and causes that channel to enter CC mode, the GUI front panel will indicate that in the following way:
Fig. 5: Simulator GUI with a connected load on channel 2 (r5B12)
9.1. SIMUlator
The SIMUlator software subsystem implements a set of unclassified SCPI commands for managing external parameters and events such as load impedance, connection and disconnection of the load, sensor temperature or the PSU control circuit power supply state. Thus it is possible to exercise the measuring and protection commands that depend on external events.
For example, a MEASure:CURRent? command without a connected load will always return zero, or activation of the VOLTage:PROTection:STATe will automatically trip the OVP signal since a channel in CC operation cannot start when output is switched on, etc.
9.1.1. SIMUlator:EXIT
|
Syntax
|
SIMUlator:EXIT
|
|
Description
|
This command close all Simulator windows (terminal and GUI if started).
|
|
Usage example
|
SIMU:EXIT
|
9.1.2. SIMUlator:GUI
|
Syntax
|
SIMUlator:GUI
|
|
Description
|
This command starts the GUI simulation in a new window (see Fig. 3 and Fig. 4).
|
|
Usage example
|
SIMU:GUI
|
|
Related Commands
|
SIMUlator:EXIT
|
9.1.3. SIMUlator:LOAD
|
Syntax
|
SIMUlator:LOAD {<resistance>}
SIMUlator:LOAD?
|
|
Description
|
This command define the impedance of a simulated load connected to a channel output. Units are in ohms. With a load connected it is possible to simulate several PSU operations: e.g., CC mode of operation, current and power measurement, OCP and OPP functionality, etc.
The simulated load value can be also changed by clicking and dragging the load’s image. Move to the left to decrease, or to the right to increase the simulated value in increments of 1 Ω.
The simulator currently cannot emulate the “UR” mode of operation (see the OUTPut:MODE? command).
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<resistance>
|
NR2|Discrete
|
0 – 9999999|INFinite
|
–
|
|
Return
|
The query command returns the programmed load value.
|
|
Usage example
|
SIMU:LOAD 8.2
|
|
Related Commands
|
OUTPut:MODE?
|
9.1.4. SIMUlator:LOAD:STATe
|
Syntax
|
SIMUlator:LOAD:STATe {<bool>}
SIMUlator:LOAD:STATe?
|
|
Description
|
This command “connects” or “disconnects” the simulated load on the channel output. If the GUI simulator has been started (via the SIMUlator:GUI command) a load symbol with the currently selected value in Ohms will be displayed (See Fig. 5).
Another possibility to connect (or disconnect) a load is by click on its image.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
–
|
|
Return
|
The query command returns the load state.
|
|
Usage example
|
SIMU:LOAD:STAT?
0
MEAS:CURR?
0.00
SIMU:LOAD:STAT ON
MEAS:CURR?
1.50
|
|
Related Commands
|
OUTPut:MODE?
SIMUlator:GUI
SIMUlator:LOAD
|
9.1.5. SIMUlator:PIN1
|
Syntax
|
SIMUlator:PIN1 {<bool>}
SIMUlator:PIN1?
|
|
Description
|
This command can be used to simulate the state of the PIN1 input on the PSU front panel push-in connector that can be used for initiate trigger.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
–
|
|
Return
|
The query command returns the state of the simulated PIN1 input.
|
|
Usage example
|
VOLT:TRIG 12.00
CURR:TRIG 2.50
TRIG:SOUR PIN1
OUTP 1
INIT
SIMU:PIN1
|
|
Related Commands
|
ABORt
INITiate[:IMMediate]
TRIGger[:SEQuence]:DELay
TRIGger[:SEQuence]:SLOPe
TRIGger[:SEQuence]:SOURce
|
9.1.6. SIMUlator:PWRGood
|
Syntax
|
SIMUlator:PWRGood {<bool>}
SIMUlator:PWRGood?
|
|
Description
|
This command can be used to simulate an internal power supply failure. When the PWRGOOD signal is changed from 1 to 0 the PSU will go into the Stand-by mode (equal to the command SYSTem:POW OFF).
The simulated PSU mode cannot be changed until PWRGOOD is not changed to 1.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
ON
|
|
Return
|
The query command returns the PWRGOOD signal state.
|
|
Usage example
|
SYST:POW?
1
SIMU:PWRG 0
SYST:POW?
0
|
|
Related Commands
|
SYSTem:POWer
|
9.1.7. SIMUlator:QUIT
|
Syntax
|
SIMUlator:QUIT
|
|
Description
|
Same as SIMUlator:EXIT
|
|
Usage example
|
SIMU:QUIT
|
9.1.8. SIMUlator:RPOL
|
Syntax
|
SIMUlator:RPOL {<bool>}
SIMUlator:RPOL?
|
|
Description
|
This command can be used to simulate detection of a remote sensing reverse polarity condition.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<bool>
|
Boolean
|
ON|OFF|0|1
|
ON
|
|
Return
|
The query command returns the RPOL signal state.
|
|
Usage example
|
STAT:QUES:INST:ISUM2?
0
SIMU:RPOL 1
STAT:QUES:INST:ISUM2?
128
|
|
Errors
|
312,"Cannot execute when the channels are coupled"
|
|
Related Commands
|
INSTrument:COUPle:TRACking
[SOURce[<n>]]:VOLTage:SENSe[:SOURce]
STATus:QUEStionable:INSTrument[:EVENt]?
|
9.1.9. SIMUlator:TEMPerature
|
Syntax
|
SIMUlator:TEMPerature {<temperature>} [, <sensor>]
SIMUlator:TEMPerature? [<sensor>]
|
|
Description
|
This command sets the simulated temperature in degrees Celsius (oC), and then reads it from the simulated temperature sensor.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<temperature>
|
NR2
|
0 – 100
|
–
|
|
<sensor>
|
Discrete
|
AUX|CH1|CH2
|
AUX
|
|
Return
|
The query command returns the set temperature value.
|
|
Usage example
|
SIMU:TEMP 45, CH2
MEAS:TEMP? CH2
45.00
|
|
Related Commands
|
MEASure[:SCALar]:TEMPerature[:THERmistor][:DC]
|
9.1.10. SIMUlator:VOLTage:PROGram:EXTernal
|
Syntax
|
SIMUlator:VOLTage:PROGram:EXTernal {<voltage>}
SIMUlator:VOLTage:PROGram:EXTernal?
|
|
Description
|
This command sets the simulated voltage that will be used for output voltage programming when the simulated channel is set in external / remote programming mode (see [SOURce[<n>]]:VOLTage:PROGram[:SOURce]). For full range, apply 2.5 V; if a higher value is entered channel’s OVP will trip.
|
|
Parameters
|
Name
|
Type
|
Range
|
Default
|
|
<voltage>
|
NR2
|
Positive value
|
0.00
|
|
Return
|
The query command returns the simulated external output voltage programming value.
|
|
Usage example
|
VOLT:PROG EXT
SIMU:VOLT:PROG:EXT 1.25
MEAS?
20.00
|
|
Errors
|
312,"Cannot execute when the channels are coupled"
|
|
Related Commands
|
INSTrument:COUPle:TRACking
[SOURce[<n>]]:VOLTage:PROGram[:SOURce]
[SOURce[<n>]]:VOLTage:PROTection:TRIPped?
|
================================================
FILE: doc/SCPI reference guide/Registers/SCPI registers (v1.1).sch
================================================
Logical OR
ESB
4
8
16
32
128
1
4
8
16
32
128
MAV
MMS (RQS)
ERR
QUES
S t a t u s b y t e
Standard Event Status group
E v e n t
Operation Complete (OPC)
Query Error (QYE)
Device Dependent Error (DDE)
Execution Error (EXE)
Command Error (CME)
Power On (PON)
OPER
Logical OR
OPERation Status group
256
512
8192
Output queue
Data
Data
Data
Data
Data
Error queue
Error
Error
Error
Error
Error
Queue not empty
Queue not empty
Logical OR
4
8
16
32
128
Enable
Service Request
INSTrument Summary (ISUM)
Logical OR
8
16
QUEStionable Status group
E n a b l e
E v e n t
INSTrument Summary (ISUM)
TEMPerature
COUPle PARAllel
COUPle SERial
TIME
(STAT:QUES:EVEN?)
(STAT:OPER:EVEN?)
(STAT:QUES:ENAB <value>)
(STAT:QUES:ENAB?)
(STAT:OPER:ENAB <value>)
(STAT:OPER:ENAB?)
(*ESR?)
(*ESE <value>)
(*ESE?)
(*STB?)
(*SRE <value>)
(*SRE?)
(SYSTem:ERRor?)
8192
User Request (URQ)
64
E n a b l e
E n a b l e
C o n d i t i o n
(STAT:QUES:COND?)
3
4
13
8
9
13
E v e n t
C o n d i t i o n
(STAT:OPER:COND?)
0
2
3
4
5
6
7
2
3
4
5
6
7
2
3
4
5
7
FAN
12
4096
DLOG active
10
Logical OR
1
2
16
(STATus:QUEStionable:INSTrument:ISUMmary<n>)
Logical OR
1
2
16
Logical OR
2
4
(STATus:QUEStionable:INSTrument)
INSTrument1 Event Summary (INST1)
INSTrument2 Event Summary (INST2)
To QUESTionable Status register
INSTrument register
ISUMmary registers
INSTrument Summary bit 13 (ISUM)
TEMPerature1
VOLTage1
CURRent1
VOLTage2
CURRent2
TEMPerature2
(STAT:QUES:INST:ENAB <value>)
(STAT:QUES:INST:ENAB?)
(STAT:QUES:INST:EVEN?)
(STAT:QUES:INST:ISUM1:ENAB <value>)
(STAT:QUES:INST:ISUM1:ENAB?)
(STAT:QUES:INST:ISUM1:COND?)
(STAT:QUES:INST:ISUM2:ENAB <value>)
(STAT:QUES:INST:ISUM2:ENAB?)
(STAT:QUES:INST:ISUM2:COND?)
OVP1
OCP1
256
512
OVP2
OCP2
256
512
OPP2
1024
1024
OPP1
E n a b l e
E v e n t
C o n d i t i o n
E n a b l e
E v e n t
C o n d i t i o n
0
1
4
8
9
10
(STAT:QUES:INST:ISUM1:EVEN?)
(STAT:QUES:INST:ISUM2:EVEN?)
0
1
4
8
9
10
E n a b l e
E v e n t
C o n d i t i o n
2
1
(STAT:QUES:INST:COND?)
RPOL1
7
RPOL2
7
128
128
(STATus:OPERation:INSTrument:ISUMmary<n>)
Logical OR
2
4
(STATus:OPERation:INSTrument)
INSTrument1 Event Summary (INST1)
INSTrument2 Event Summary (INST2)
To OPERation Status register
INSTrument register
ISUMmary registers
INSTrument Summary bit 13 (ISUM)
Logical OR
16
32
MEASuring2
Remote SENSe ON (RSENSE2)
Waiting for TRIGger2
Constant Voltage (CV2)
Constant Current (CC2)
Output Enable OFF (OE2)
Down-Programmer OFF (DP2)
256
512
1024
2048
4096
1
CALibrating2
Logical OR
16
32
MEASuring1
Remote SENSe ON (RSENSE1)
Waiting for TRIGger1
Constant Voltage (CV1)
Constant Current (CC1)
Output Enable OFF (OE1)
Down-Programmer OFF (DP1)
256
512
1024
2048
4096
1
CALibrating1
(STAT:OPER:INST:ENAB <value>)
(STAT:OPER:INST:ENAB?)
(STAT:OPER:INST:EVEN?)
(STAT:OPER:INST:ISUM1:ENAB <value>)
(STAT:OPER:INST:ISUM1:ENAB?)
(STAT:OPER:INST:ISUM1:EVEN?)
(STAT:OPER:INST:ISUM2:ENAB <value>)
(STAT:OPER:INST:ISUM2:ENAB?)
(STAT:OPER:INST:ISUM2:EVEN?)
E n a b l e
E v e n t
C o n d i t i o n
0
5
4
8
9
10
11
E n a b l e
E v e n t
C o n d i t i o n
0
5
12
11
10
9
4
8
(STAT:OPER:INST:ISUM2:COND?)
(STAT:OPER:INST:ISUM1:COND?)
12
E n a b l e
E v e n t
C o n d i t i o n
2
1
(STAT:OPER:INST:COND?)
Remote PROGram ON (RPROG1)
8192
13
Remote PROGram ON (RPROG2)
8192
13
Logical OR
ESB
4
8
16
32
128
1
4
8
16
32
128
MAV
MMS (RQS)
ERR
QUES
S t a t u s b y t e
Standard Event Status group
E v e n t
Operation Complete (OPC)
Query Error (QYE)
Device Dependent Error (DDE)
Execution Error (EXE)
Command Error (CME)
Power On (PON)
OPER
Logical OR
OPERation Status group
256
512
8192
Output queue
Data
Data
Data
Data
Data
Error queue
Error
Error
Error
Error
Error
Queue not empty
Queue not empty
Logical OR
4
8
16
32
128
Enable
Service Request
INSTrument Summary (ISUM)
Logical OR
8
16
QUEStionable Status group
E n a b l e
E v e n t
INSTrument Summary (ISUM)
TEMPerature
COUPle PARAllel
COUPle SERial
TIME
(STAT:QUES:EVEN?)
(STAT:OPER:EVEN?)
(STAT:QUES:ENAB <value>)
(STAT:QUES:ENAB?)
(STAT:OPER:ENAB <value>)
(STAT:OPER:ENAB?)
(*ESR?)
(*ESE <value>)
(*ESE?)
(*STB?)
(*SRE <value>)
(*SRE?)
(SYSTem:ERRor?)
8192
User Request (URQ)
64
E n a b l e
E n a b l e
C o n d i t i o n
(STAT:QUES:COND?)
3
4
13
8
9
13
E v e n t
C o n d i t i o n
(STAT:OPER:COND?)
0
2
3
4
5
6
7
2
3
4
5
6
7
2
3
4
5
7
Logical OR
1
2
16
(STATus:QUEStionable:INSTrument:ISUMmary<n>)
Logical OR
1
2
16
Logical OR
2
4
(STATus:QUEStionable:INSTrument)
INSTrument1 Event Summary (INST1)
INSTrument2 Event Summary (INST2)
INSTrument register
ISUMmary registers
TEMPerature1
VOLTage1
CURRent1
VOLTage2
CURRent2
TEMPerature2
(STAT:QUES:INST:ENAB <value>)
(STAT:QUES:INST:ENAB?)
(STAT:QUES:INST:EVEN?)
(STAT:QUES:INST:ISUM1:ENAB <value>)
(STAT:QUES:INST:ISUM1:ENAB?)
(STAT:QUES:INST:ISUM1:COND?)
(STAT:QUES:INST:ISUM2:ENAB <value>)
(STAT:QUES:INST:ISUM2:ENAB?)
(STAT:QUES:INST:ISUM2:COND?)
OVP1
OCP1
256
512
OVP2
OCP2
256
512
OPP2
1024
1024
OPP1
E n a b l e
E v e n t
C o n d i t i o n
E n a b l e
E v e n t
C o n d i t i o n
0
1
4
8
9
10
(STAT:QUES:INST:ISUM1:EVEN?)
(STAT:QUES:INST:ISUM2:EVEN?)
0
1
4
8
9
10
E n a b l e
E v e n t
C o n d i t i o n
2
1
(STAT:QUES:INST:COND?)
(STATus:OPERation:INSTrument:ISUMmary<n>)
Logical OR
2
4
(STATus:OPERation:INSTrument)
INSTrument1 Event Summary (INST1)
INSTrument2 Event Summary (INST2)
INSTrument register
ISUMmary registers
Logical OR
16
32
MEASuring2
Remote SENSe ON (RSENSE2)
Waiting for TRIGger2
Constant Voltage (CV2)
Constant Current (CC2)
Output Enable OFF (OE2)
Down-Programmer OFF (DP2)
256
512
1024
2048
4096
1
CALibrating2
Logical OR
16
32
MEASuring1
Remote SENSe ON (RSENSE1)
Waiting for TRIGger1
Constant Voltage (CV1)
Constant Current (CC1)
Output Enable OFF (OE1)
Down-Programmer OFF (DP1)
256
512
1024
2048
4096
1
CALibrating1
(STAT:OPER:INST:ENAB <value>)
(STAT:OPER:INST:ENAB?)
(STAT:OPER:INST:EVEN?)
(STAT:OPER:INST:ISUM1:ENAB <value>)
(STAT:OPER:INST:ISUM1:ENAB?)
(STAT:OPER:INST:ISUM1:EVEN?)
(STAT:OPER:INST:ISUM2:ENAB <value>)
(STAT:OPER:INST:ISUM2:ENAB?)
(STAT:OPER:INST:ISUM2:EVEN?)
E n a b l e
E v e n t
C o n d i t i o n
0
5
4
8
9
10
11
E n a b l e
E v e n t
C o n d i t i o n
0
5
12
11
10
9
4
8
(STAT:OPER:INST:ISUM2:COND?)
(STAT:OPER:INST:ISUM1:COND?)
12
E n a b l e
E v e n t
C o n d i t i o n
2
1
(STAT:OPER:INST:COND?)
FAN
12
4096
Remote PROGram ON (RPROG1)
8192
13
Remote PROGram ON (RPROG1)
8192
13
RPOL1
7
128
RPOL2
7
128
DLOG active
10
================================================
FILE: doc/build.bat
================================================
dot -Tpng components.dot -o components.png
================================================
FILE: doc/components.dot
================================================
digraph hierarchy {
nodesep=1.0 // increases the separation between nodes
node [color=Red,fontname=Courier,shape=box] //All nodes will this shape and colour
edge [color=Blue, style=dashed] //All the lines look like this
Headteacher->{Deputy1 Deputy2 BusinessManager}
Deputy1->{Teacher1 Teacher2}
BusinessManager->ITManager
{rank=same;ITManager Teacher1 Teacher2} // Put them on the same level
}
================================================
FILE: doc/files.md
================================================
# File system structure
|Folder/File|Description|
|-|-|
|`doc/`|Documentation related stuff.|
| `html/`|Autogenerated HTML documentation using doxygen tool.|
| `template/`|Doxygen template files.|
| `Doxyfile`|Doxygen configuration file.|
| `*.dot`|Diagrams described using [dot](www.graphviz.org/doc/info/lang.html) language.|
| `*.md`|Articles writen in markdown.|
|`eez_psu_sketch/`|Arduino EEZ PSU sketch source code.|
| `eez_psu_sketch.ino`|EEZ PSU sketch.|
| `*.cpp`|Sketch source files.|
| `*.h`|Sketch header files.|
|`libraries/`|Arduino libraries required by the EEZ PSU sketch.|
| `eez_psu_lib/`|This library contains pin definitions for the EEZ PSU hardware.|
| `scpi-parser/`|[scpi-parser](https://github.com/mvladic/scpi-parser/tree/avr_progmem)|
| `UIPEthernet/`|[UIPEthernet](https://github.com/mvladic/arduino_uip/tree/Arduino_1.5.x)|
|`simulator/`|Simulator source code.|
| `fonts/`|Fonts used by the simulator GUI.|
| `images/`|Images used by the simulator GUI.|
| `platform/`|Platform specific source and make files.|
| `Win32/`|Windows platform files.|
| `eez_psu/`|Visual Studio 2015 solution for simulator executable.|
| `eez_imgui/`|Visual Studio 2013 solution for EEZ IMGUI DLL.|
| `linux/`|Linux (and Mac) platform files.|
| `src/`|Simulator source code.|
| `arduino/`|Arduino API emulation.|
| `front_panel/`|Simulator GUI Front panel.|
| `imgui/`|EEZ immediate mode GUI library.|
| `third_party/`|Third party libraries used by simulator.|
| `SDL2/`|SDL2 for Windows.|
| `SDL2_image/`|SDL2 image module for Windows.|
| `SDL2_ttf/`|SDL2 TTF module for Windows.|
================================================
FILE: doc/template/customdoxygen.css
================================================
/* Custom Look and feel - Can be edited
----------------------------------- */
#navrow1, #navrow2, #navrow3, #navrow4, #navrow5{
border-bottom: 1px solid #EEEEEE;
}
.adjust-right {
margin-left: 30px !important;
font-size: 1.15em !important;
}
/* DOXYGEN Code Styles - These are from doxygen but can be changed to fit the theme
----------------------------------- */
a.qindex {
font-weight: bold;
}
a.qindexHL {
font-weight: bold;
background-color: #9CAFD4;
color: #ffffff;
border: 1px double #869DCA;
}
.contents a.qindexHL:visited {
color: #ffffff;
}
a.code, a.code:visited, a.line, a.line:visited {
color: #4665A2;
}
a.codeRef, a.codeRef:visited, a.lineRef, a.lineRef:visited {
color: #4665A2;
}
/* @end */
dl.el {
margin-left: -1cm;
}
pre.fragment {
border: 1px solid #C4CFE5;
background-color: #FBFCFD;
padding: 4px 6px;
margin: 4px 8px 4px 2px;
overflow: auto;
word-wrap: break-word;
font-size: 9pt;
line-height: 125%;
font-family: monospace, fixed;
font-size: 105%;
}
div.fragment {
padding: 4px 6px;
margin: 4px 8px 4px 2px;
border: 1px solid #C4CFE5;
}
div.line {
font-family: monospace, fixed;
font-size: 13px;
min-height: 13px;
line-height: 1.0;
text-wrap: unrestricted;
white-space: -moz-pre-wrap; /* Moz */
white-space: -pre-wrap; /* Opera 4-6 */
white-space: -o-pre-wrap; /* Opera 7 */
white-space: pre-wrap; /* CSS3 */
word-wrap: break-word; /* IE 5.5+ */
text-indent: -53px;
padding-left: 53px;
padding-bottom: 0px;
margin: 0px;
-webkit-transition-property: background-color, box-shadow;
-webkit-transition-duration: 0.5s;
-moz-transition-property: background-color, box-shadow;
-moz-transition-duration: 0.5s;
-ms-transition-property: background-color, box-shadow;
-ms-transition-duration: 0.5s;
-o-transition-property: background-color, box-shadow;
-o-transition-duration: 0.5s;
transition-property: background-color, box-shadow;
transition-duration: 0.5s;
}
div.line.glow {
background-color: cyan;
box-shadow: 0 0 10px cyan;
}
span.lineno {
padding-right: 4px;
text-align: right;
border-right: 2px solid #0F0;
background-color: #E8E8E8;
white-space: pre;
}
span.lineno a {
background-color: #D8D8D8;
}
span.lineno a:hover {
background-color: #C8C8C8;
}
div.groupHeader {
margin-left: 16px;
margin-top: 12px;
font-weight: bold;
}
div.groupText {
margin-left: 16px;
font-style: italic;
}
/* @group Code Colorization */
span.keyword {
color: #008000
}
span.keywordtype {
color: #604020
}
span.keywordflow {
color: #e08000
}
span.comment {
color: #800000
}
span.preprocessor {
color: #806020
}
span.stringliteral {
color: #002080
}
span.charliteral {
color: #008080
}
span.vhdldigit {
color: #ff00ff
}
span.vhdlchar {
color: #000000
}
span.vhdlkeyword {
color: #700070
}
span.vhdllogic {
color: #ff0000
}
blockquote {
background-color: #F7F8FB;
border-left: 2px solid #9CAFD4;
margin: 0 24px 0 4px;
padding: 0 12px 0 16px;
}
/* ------------------------------------------------------------------ */
.navbar-header {
padding: 5px 0;
}
.navbar-header>img {
display: block;
float: left;
}
.navbar-header>span {
display: block;
}
================================================
FILE: doc/template/doxy-boot.js
================================================
$( document ).ready(function() {
$("div.headertitle").addClass("page-header");
$("div.title").addClass("h1");
$('li > a[href="index.html"] > span').before(" ");
//$('li > a[href="index.html"] > span').text("EEZ PSU");
$('li > a[href="modules.html"] > span').before(" ");
$('li > a[href="namespaces.html"] > span').before(" ");
$('li > a[href="annotated.html"] > span').before(" ");
$('li > a[href="classes.html"] > span').before(" ");
$('li > a[href="inherits.html"] > span').before(" ");
$('li > a[href="functions.html"] > span').before(" ");
$('li > a[href="functions_func.html"] > span').before(" ");
$('li > a[href="functions_vars.html"] > span').before(" ");
$('li > a[href="functions_enum.html"] > span').before(" ");
$('li > a[href="functions_eval.html"] > span').before(" ");
$('img[src="ftv2ns.png"]').replaceWith('N ');
$('img[src="ftv2cl.png"]').replaceWith('C ');
$("ul.tablist").addClass("nav nav-pills nav-justified");
$("ul.tablist").css("margin-top", "0.5em");
$("ul.tablist").css("margin-bottom", "0.5em");
$("li.current").addClass("active");
$("iframe").attr("scrolling", "yes");
$("#nav-path > ul").addClass("breadcrumb");
$("table.params").addClass("table");
$("div.ingroups").wrapInner("");
$("div.levels").css("margin", "0.5em");
$("div.levels > span").addClass("btn btn-default btn-xs");
$("div.levels > span").css("margin-right", "0.25em");
$("table.directory").addClass("table table-striped");
$("div.summary > a").addClass("btn btn-default btn-xs");
$("table.fieldtable").addClass("table");
$(".fragment").addClass("well");
$(".memitem").addClass("panel panel-default");
$(".memproto").addClass("panel-heading");
$(".memdoc").addClass("panel-body");
$("span.mlabel").addClass("label label-info");
$("table.memberdecls").addClass("table");
$("[class^=memitem]").addClass("active");
$("div.ah").addClass("btn btn-default");
$("span.mlabels").addClass("pull-right");
$("table.mlabels").css("width", "100%")
$("td.mlabels-right").addClass("pull-right");
$("div.ttc").addClass("panel panel-primary");
$("div.ttname").addClass("panel-heading");
$("div.ttname a").css("color", 'white');
$("div.ttdef,div.ttdoc,div.ttdeci").addClass("panel-body");
$('#MSearchBox').parent().remove();
$('div.fragment.well div.line:first').css('margin-top', '15px');
$('div.fragment.well div.line:last').css('margin-bottom', '15px');
$('table.doxtable').removeClass('doxtable').addClass('table table-striped table-bordered').each(function(){
$(this).prepend('');
$(this).find('tbody > tr:first').prependTo($(this).find('thead'));
$(this).find('td > span.success').parent().addClass('success');
$(this).find('td > span.warning').parent().addClass('warning');
$(this).find('td > span.danger').parent().addClass('danger');
});
if($('div.fragment.well div.ttc').length > 0)
{
$('div.fragment.well div.line:first').parent().removeClass('fragment well');
}
$('table.memberdecls').find('.memItemRight').each(function(){
$(this).contents().appendTo($(this).siblings('.memItemLeft'));
$(this).siblings('.memItemLeft').attr('align', 'left');
});
function getOriginalWidthOfImg(img_element) {
var t = new Image();
t.src = (img_element.getAttribute ? img_element.getAttribute("src") : false) || img_element.src;
return t.width;
}
$('div.dyncontent').find('img').each(function(){
if(getOriginalWidthOfImg($(this)[0]) > $('#content>div.container').width())
$(this).css('width', '100%');
});
$(".memitem").removeClass('memitem');
$(".memproto").removeClass('memproto');
$(".memdoc").removeClass('memdoc');
$("span.mlabel").removeClass('mlabel');
$("table.memberdecls").removeClass('memberdecls');
$("[class^=memitem]").removeClass('memitem');
$("span.mlabels").removeClass('mlabels');
$("table.mlabels").removeClass('mlabels');
$("td.mlabels-right").removeClass('mlabels-right');
$(".navpath").removeClass('navpath');
$("li.navelem").removeClass('navelem');
$("a.el").removeClass('el');
$("div.ah").removeClass('ah');
$("div.header").removeClass("header");
$('.mdescLeft').each(function(){
if($(this).html()==" ") {
$(this).siblings('.mdescRight').attr('colspan', 2);
$(this).remove();
}
});
$('td.memItemLeft').each(function(){
if($(this).siblings('.memItemRight').html()=="") {
$(this).attr('colspan', 2);
$(this).siblings('.memItemRight').remove();
}
});
});
================================================
FILE: doc/template/footer.html
================================================