Keithley DMM IVI Read Timeout
We are controlling a Keithley 2000 series DMM using the IVI Dmm Step in TestStand version 3.0.
The logical name has been set-up using MAX version 3.0.2, the logical name references the ke2000 driver session. When run under TestStand the DMM configures correctly and will take a first reading correctly but subsequent reads fail with a timeout error. We’ve tried using the LabWindows example code found in directory \program files\ivi\drivers\ividmm\examples\cvi, this exhibits the same problem found use TestStand. Is this a MAX set-up problem, any help will be appreciated.
Below is listed the software/environment we are using with the DMM:
Software Version
IVI Compliance Package 2.1
NI VISA 3.0.1
NI-488.2 1.7
Instrume
nt Driver (LabWindows/CVI 6.0) 3.02
Measurement and Automation Explorer 3.0.2.3005
TestStand 3.0
CVI Runtime 7.0.0.393
LabWindows/CVI 7.0
WindowsXP Pro
Hello Steve Penny �
What is the exact error code you are receiving? You can find a list of common GPIB error codes and solutions here.
Make sure you are using the correct driver for your GPIB board. Windows XP also uses NI 488.2 version 2.1. Click here for a list of current drivers by platform.
If these suggestions do not solve your problem, please post the error code so the matter can be further investigated. Have a great day!
Becky B.
Applications Engineer
National Instruments
Becky Linton
National Instruments
Field Engineer
Office: 734-464-2463
Cell: 248-709-2822
Email: [email protected]
Similar Messages
-
DMM IVI read measurement update
Hi,
I am using Teststand DMM IVI step to measure voltage to ground via 100K ohm pull-up resistance to 20V supply. While monitoring this voltage using external DMM it shows 13.4V however after "DMM IVI Read" step is ran the external DMM voltage shows 19.7V!! Any idea why this is happening, I'm using:
NI DMM 4070
TestStand 4.1
Labview 2010
and Switch Executive 3.0
Many Thanks
Mehran
Mehran Fard
Solved!
Go to Solution.Hi Andy,
It is just an step with "DMM IVI" to measure voltage, attached is the image of the sequence I am using with simplified cct.
Unfortunately I won't be able to post you the complete sequence.
Regards
Mehran fard
Mehran Fard
Attachments:
DMM IVI.JPG 151 KB -
Keithley 2000 DMM AC Read Overflow
I’ve been having problems controlling a Keithley 2000 DMM during AC volts measurement using IVI. When reading AC Volts the DMM will intermittently sense an ‘overflow’ and return the value NaN. I’m using IVI and TestStand 3.0 but get the same problem with IVI and LabWindows 7.0.
The set-up is as follows:
Device: Keithley 2000 DMM, GPIB device number 6
Device interface: GPIB, DMM set-up in MAX as GIPB0::6::INSTR
IVI Driver version: 3.02, downloaded from the NI web site
IVI Compliance Package version: 2.1
NI-488.2 version: 1.70
NI-DAQ version: 7.1.0f1
MAX version: 3.0.2.3005
For test purposes I’ve connected the DMM front panel input high and low and set the inputs mode on the Keithley to front, this should mean that I get a very low Voltage reading. I’ve then run the LabWindows/CVI IVI control sample code provided with the IVI driver. At the initialisation panel I’ve entered the logical name. At the configuration panel I’ve selected Volt AC measurement but left everything else as default. The second configuration panel I’ve left as default. At the Read panel I’ve left all setting as default. Pressing the read button up to about 20 times with about a second gap in between each press will eventually lead to an ‘overflow’ reading.
Any help/explantion will be appreciated
SteveHere are the results of my investigation into this problem, it’s two fold:
1. Keithley have informed me that their engineers in the US have just seen the problem I’ve been seeing and are working on a firmware update. Currently here is no date for the release of the updated firmware but I’ll be informed when this it’s ready.
Note: I’ve found that the read AC Volts overflow problem only occurs when the read trigger delay is set to zero seconds.
2. The TestStand DMM IVI configuration step always sends a trigger delay of zero seconds regardless of the trigger delay set.
In my TestStand sequence the DMM IVI configuration sets the read trigger delay to 3 seconds but as noted above this is sent a zero seconds thus invoking the Keithley DMM AC Volts read overflow problem.
See attached VISA call log captured by NI Spy. The first 22 call are made when the DMM IVI configuration step is called form TestStand the next 22 calls are made by the IVI DMM sample code configuration provided by National Instruments when DMM configuration is run thorough LabWindows. Note call 12 (IVI DMM TestStand) has the trigger delay set to zero seconds (should be 3 seconds) and call 34 (IVI DMM LabWindows) has a delay of three seconds.
I’ve found a workaround as follows:
After each call to the TestStand DMM IVI configuration step an additional step that calls the TestStand IVI Tools step can be added. The IVI Tools step can be set-up to specifically configure the DMM Trigger Delay to 3 seconds. I’ve proven that this individual call does in fact send the correct trigger delay command to the DMM thus alleviating the AC Volts read overflow problem.
Can NI confirm that this problem does exist with the DMM IVI step and when they plan to fix it. I’ve attached the TestStand sequence file that I’ve been using to investigate the problem.
Thanks
Steve
Attachments:
DMM Overflow.zip 9 KB -
TestStand IVI Read Numeric Limit Test
Hey all,
How can I turn a IVI DMM reading into a test step pass / fail based on a numeric limit test?
I'm a TestStand newbie so be gentle. Searches on the forum for TestStand IVI and pass fail don't return anything useful.
I can call the DMM via IVI Read wich returns a Step.Result.Reading value but I need to turn this into a pass fail on a limit range.
Any ideas would be very gratefully appreciated.
Thanks,
Solved!
Go to Solution.You could insert an none_adapter numeric limit step after it and set the data source to PreviousStep.Result.Reading.
-Doug -
Read Timeout is not working with business service in OSB 11.6
HI All,
We have set below configuration in "Http Transport Configuration" of a business service.
Read Timeout- 8
Connection Timeout - 8
Authentication - None
Proxy Serve
Follow HTTP redirects - Disable
Use Chunked Streaming Mode - Enable
Even though backend is taking more than the configured value in Read Timeout but timeout is not happening in OSB, Connection time out also not worked, when we tested with wrong backend URL.
Any help for this configuration would appreciated.
Thanks,.Hi,
Have you invoked any Services before calling the Business Service.
If Yes, then the problem with the Invoked service.In this scenario even if you set the time out period it will not work..
If No, your request payload is high
Regards,
Kiran -
In need of a KEITHLEY 2001 single read .vi that is compatible with LabVIEW 7
I am updating from LabVIEW 5.1.1 to 7. The KEITHLEY 2001 Single Read .vi has coercion errors, and does not function. Where can I get updated KEITHLEY 2001 .vi's that are compatible with LabVIEW 7?
You can visit http://ni.com/idnet/, click the "Search Drivers" button
and select "Keithley" as the manufacturer and hit the "Go" button.
Look down the list, and you'll find the LabVIEW Certified Plug and
Play driver for this multimeter scanner.
I hope this helps.
Brian -
I have a timeout question about RT FIFO Read in Producer/Consumer system. Here is the scenario.
Producer writes data to RT FIFO via RT FIFO Write;
Consumer read data from RT FIFO via RT FIFO Read with timeout 100ms;
If RT FIFO is empty, returns 100ms timeout and stops Producer and Consumer.
If RT FIFO is not empty, process the data from FIFO and continue Producer/Consumer.
As I understand, RT FIFO empty means 100ms timeout. But the 100ms timeout condition does not behave properly as expected.
Am I understanding the FIFO Read timeout correctly?
Thanks!MileP,
I find the best way to learn about Real-Time FIFOs is to run some examples of them, check these out and let me know what you think:
https://decibel.ni.com/content/docs/DOC-2303
https://decibel.ni.com/content/docs/DOC-9893
http://zone.ni.com/devzone/cda/tut/p/id/3934
I hope this helps get you going
Sam S
Applications Engineer
National Instruments -
OSB Business Service is not timing out on Connection/Read timeout
I have a weird problem with my business service in OSB. I have set the read timeout value as 1 sec and Connection timeout value as 1 sec. The response from backend is taking more than 2 seconds or even 3 seconds but still my business service is not timing out..! My service is still listening to the response from backend even if it comes after 3 seconds. I expect it to timeout after 2 seconds. Any ideas?
Business Service Configurations:
Service Type: Any type
Protocol: http
Retry count : 0
Retry Application Errors: No
Read Timeout: 0
Connection Timeout: 0
HTTP Request Method: POST
Result Caching: No
Let me know if you need any more information. Thanks in Advance.
Regards
KaleemAbhishekJ wrote:
Maximum possible successful response time of the service will be less than Read TO + Connection TO.
Alas, this is not true.
Maximum possible response time is infinity.
There are two reasons for that.
1. Read timeout is not counted as time from the successful connection establishing to the current moment. It is measured as time from the last received byte to now. Imagine a backend service that sends a single byte in a data packet every 500ms. Despite you have read timeout set to 1, the receiving of 3K message will take 25 minutes, and yet your Biz service will not timeout.
2. In HTTPS, handshake is handled by a separate library which has its own quirks. Specifically, if the key exchange is broken at particular point of handshake, the library re-establishes the connection and does it few times; in my experiements, the largest I could delay the eventual fault was about 3 minutes.
Having said that, in the OP message the configuration is Read=0, Connect=0, so I wonder why the timeout is expected. -
Read Timeout on non-blocking sockets
Hi,
I was wondering if there is a way to specify a read timeout (like setSoTimeout for synchronous sockets) when using a non-blocking socket.
I'd like to have the select() method return is a sockets timeout expires, puting in the selected key set the timedout socket and have it's read operation return -1, something like what happens when a socket is closed by the other side.
The thing is I need this to be a timeout specific to each socket, thus the select(millis) isn't apropriate.
Anyone knows of something like this?
Thanks....Yeah, select() is the only thing built in for that, and you have to do the bookkeeping yourself. You would start something like forming the disjunction of the ready keys and the registered keys after each select, to get the unready keys, and then looking at their history to see how long they have been unready via a Map{key,Long(time)).
-
SMTP postfix crashing - network_biopair_interop read timeout
Periodically, my mail server goes into a crash cycle. Error messages like those below appear, and very quickly, the machine becomes unresponsive (I believe because it can't fork any more process - so OD won't authenticate, and any command which requires authentication (like a restart or service restart) hangs indefinitely).
The machine will crash every ~12 hours after being rebooted, for maybe 2-3 days before the problem mysteriously goes into remission. I don't know what confluence of events causes this, or how to see it coming sooner so I can stop and restart the mail service.
Any insight or solutions would be greatly appreciated.
/var/log/system.log:
Apr 25 07:37:43 mercury postfix/smtpd[8213]: warning: Read failed in networkbiopairinterop with errno=0: num_read=0, want_read=5
Apr 25 07:48:39 mercury postfix/smtpd[8475]: warning: Read failed in networkbiopairinterop with errno=0: num_read=0, want_read=5
Apr 25 07:50:06 mercury postfix/master[51]: warning: unixtriggerevent: read timeout for service public/flush
Apr 25 07:55:50 mercury postfix/pipe[8467]: warning: pipecommandwrite: write time limit exceeded
Apr 25 07:55:50 mercury postfix/pipe[8470]: warning: pipecommandread: read time limit exceeded
Apr 25 07:57:08 mercury postfix/pipe[8479]: warning: pipecommandread: read time limit exceededThe output of postconf -n:
mercury:/ root# postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
html_directory = no
inet_interfaces = all
mail_owner = postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
messagesizelimit = 15728640
mydestination = $myhostname,localhost.$mydomain,tjs.org,staff.tjs.org,mercury.tjs.org,info.tjs. org
mydomain = tjs.org
mydomain_fallback = localhost
myhostname = mail.tjs.org
mynetworks = 127.0.0.1/32,10.1.1.0/24,66.148.181.0/24,66.90.0.0/16,192.168.1.0/24,66.93.192. 247/32,66.93.193.247/32
mynetworks_style = host
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpdpw_server_securityoptions = cram-md5,gssapi
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdtls_certfile = /etc/certificates/*.tjs.org.crt
smtpdtls_keyfile = /etc/certificates/*.tjs.org.key
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550
And here's a more full version of the logs. I think the increasing pids is a symptom of the problem:
Apr 27 10:34:58 mercury pop3[7164]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:34:58 mercury pop3[7369]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:35:18 mercury pop3[7164]: starttls: TLSv1 with cipher AES256-SHA (256/256 bits new) no authentication
Apr 27 10:35:19 mercury pop3[7164]: login: ppp-70-245-234-7.dsl.stlsmo.swbell.net [70.245.234.7] YYY APOP+TLS User logged in
Apr 27 10:35:28 mercury pop3[7369]: login: c-69-241-232-137.hsd1.mi.comcast.net [69.241.232.137] XXX APOP User logged in
Apr 27 10:35:59 mercury pop3[7164]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:36:10 mercury pop3[7369]: login: dsl093-192-247.stl1.dsl.speakeasy.net [66.93.192.247] XXX APOP User logged in
Apr 27 10:36:11 mercury pop3[7164]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:37:01 mercury pop3[7164]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:37:01 mercury pop3[7369]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:37:01 mercury pop3[7833]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:37:07 mercury ctl_cyrusdb[7836]: checkpointing cyrus databases
Apr 27 10:37:08 mercury ctl_cyrusdb[7836]: done checkpointing cyrus databases
Apr 27 10:37:15 mercury pop3[7164]: login: dsl093-192-247.stl1.dsl.speakeasy.net [66.93.192.247] XXX APOP User logged in
Apr 27 10:37:26 mercury pop3[7833]: login: dsl093-192-247.stl1.dsl.speakeasy.net [66.93.192.247] XXX APOP User logged in
Apr 27 10:37:38 mercury pop3[7369]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:37:52 mercury imap[7842]: login: localhost [::1] jroth CRAM-MD5 User logged in
Apr 27 10:37:52 mercury pop3[7164]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:38:03 mercury imap[7842]: login: localhost [::1] XXX CRAM-MD5 User logged in
Apr 27 10:38:13 mercury imap[7842]: login: localhost [::1] XXX CRAM-MD5 User logged in
Apr 27 10:38:15 mercury imap[7842]: login: localhost [::1] XXX CRAM-MD5 User logged in
Apr 27 10:38:26 mercury pop3[7833]: login: 66.148.181.178.nw.nuvox.net [66.148.181.178] XXX APOP User logged in
Apr 27 10:38:30 mercury imap[7842]: login: localhost [::1] XXX CRAM-MD5 User logged in
Apr 27 10:40:18 mercury pop3[7871]: TLS server engine: cannot load CA data
Apr 27 10:40:19 mercury pop3[7871]: TLS server engine: No CA file specified. Client side certs may not work
Apr 27 10:40:19 mercury pop3[7871]: starttls: TLSv1 with cipher AES256-SHA (256/256 bits new) no authentication
Apr 27 10:41:41 mercury postfix/master[51]: warning: unixtriggerevent: read timeout for service public/flush
Apr 27 10:50:18 mercury pop3[7913]: TLS server engine: cannot load CA data
Apr 27 10:50:18 mercury pop3[7913]: TLS server engine: No CA file specified. Client side certs may not work
Apr 27 10:50:18 mercury pop3[7913]: starttls: TLSv1 with cipher AES256-SHA (256/256 bits new) no authentication
And then the crash. Note this is a more recent crash cycle than the last one which I posted logs from.
Interesting that SSL certificates might be the issue. The one user, shown above as YYY, always triggers the log messages about TLS, which none of the other users seem to use. I haven't enabled SSL for email, but I wouldn't mind doing it to fix this problem.
Thanks for your thoughts and time.
Brian Howard -
read-timeout-seconds not working
(WL 5.1, SP 11)
Hi all,
I'm playing around with Read-Only entity beans, and I get a problem
with the read-timeout-seconds property. I've set my
weblogic-ejb-jar.xml like this:
<ejb-name>product.entity</ejb-name>
<caching-descriptor>
<max-beans-in-cache>1000</max-beans-in-cache>
<cache-strategy>Read-Only</cache-strategy>
<read-timeout-seconds>60</read-timeout-seconds>
</caching-descriptor>
The first call to the EJB caches the database record, and subsequent
calls use the cache. My problem: Even if I delete the database record
directly (I know, I shouldn't do that... but like I said, I'm playing
around here... ;)) and wait for more than 60 seconds, the next call to
the bean still returns the same cached entry.
I tried with <idle-timeout-seconds> set to 60, and it doesn't work
neither.
I've seen in previous messages that this problem (or similar) was
fixed in SP4, but I use SP11, so it shouldn't be the problem.
Thanks for your help!
PhilHi,
Have you invoked any Services before calling the Business Service.
If Yes, then the problem with the Invoked service.In this scenario even if you set the time out period it will not work..
If No, your request payload is high
Regards,
Kiran -
Modbus TCP/IP read timeout
The code below was taken from the NI Modbus library:
The first TCP Read VI, reads 7 bytes as a binary string. The data string is then cast to the MBAP_Header data type.
The MBAP header contains a length field, that is used to determine the length of the Modbus PDU (i.e. remaining part of the TCP message)
The second TCP Read VI then gets the remaining part of the message.
Can I set the second read timeout to 0?
For reqular Ethernet, the maximum packet payload is 1500 bytes.
1500 bytes is larger than any Modbus message, so I would not expect segmentation of Modbus messages.
Is this correct?
In general, if the application data is less than 1500 bytes (on regular Ethernet) and data is read in two parts, is it a good idea to set the second read timeout to 0.
Is there any other reason why I should not do this?
Thanks.
Message Edited by sparkymark567 on 01-28-2010 03:59 AM
Message Edited by sparkymark567 on 01-28-2010 04:01 AMHey,
The second read should not have a time out of 0. The first read only gets the first 8 bits of data, it does not buffer the rest of the package so the second read still needs time to receive the remaining data and hence will need at least some sort of time out value.
On the subject of segmentation, I believe you are correct. As long as your message doesn't excede 1492 bytes (I think the 1500 includes the overhead of the Ethernet package), it should come down in one package.
The best thing you can do is to try it out.
Kind regards,
Dominic Walker
Cardiff University
Electrical and Electronic Engineering Student -
How to run vi continuous​ly when VISA read timeout happens
Hello,
I am using LabView 2010 to read an Agilent 6000 series Oscilloscope. The Oscilloscope reads data from another experimental machine which fails occasionally due to sample failure. When the machine fails, it stops sending signal to the oscilloscope and leads to the VISA read timeout error and the whole vi is terminated. Is there a way that I can continuously run the vi when the error happens? For example, when the error happens, it stores the error in the error wire. When the vi read the error code from the wire, it sends a command to stop my experimental machine then stop the vi.
So far, it just simply stops during executing the visa read function. In this case, why do we have error in and out? The vi simply stops when the error happens.
Thanks
Lawrence
Solved!
Go to Solution.I'll start of with automatic error handling. By default, LabVIEW enables the automatic error handling. So consider the case like the one below,
If let's say the VISA Read returns an error, but you did you pass the error information to VISA Close, what will happen is that LabVIEW will highlight the VISA Read (since the error comes from that function), pause the execution at the VISA Read and an error dialog box will appear. From the dialog box, it will prompt to either continue (Move on to the VISA Close) or stop (LabVIEW will stop the VI at VISA Read)
Now, consider another scenario like this,
By passing the error information from one function to another, let's say if VISA Read returns an error, that error will pass to VISA Close and finally to Simple Error Handler.vi. So Simple Error Handler will generate error dialog box after all the VISA operation is completed. This is called manual error handling (It can be enabled by just wiring the error information from one function to another and terminates at Simple Error Handler).
http://www.ni.com/gettingstarted/labviewbasics/handlingerrors.htm
As for VISA Close, here is the information about VISA Close.
http://zone.ni.com/reference/en-XX/help/371361K-01/lvinstio/visa_close/
See that button on the left side of this post...
If you feel my post is helpful, all you need is just (at most) 2 seconds to click that button, to show your appreciation. Thank you~~ -
Hi!
What happens if I set <read-timeout-seconds> to some value
for a read only bean, according to bea's docs the ejbLoad() is called initially when the EJB is created and afterwards, WebLogic Server calls ejbLoad() only at intervals defined by the read-timeout-seconds. Does this mean that Weblogic always runs ejbLoad() every x seconds or ONLY if some client runs findByPrimaryKey() and the interval has expired?
Thanks,
A.It's done lazily. When you access the bean, WLS checks if currentTime -
lastLoadedTime is > read-timeot-seconds. If so, it calls ejbLoad.
-- Rob
bnmbn ghjhg wrote:
Hi!
What happens if I set <read-timeout-seconds> to some value
for a read only bean, according to bea's docs the ejbLoad() is called initially when the EJB is created and afterwards, WebLogic Server calls ejbLoad() only at intervals defined by the read-timeout-seconds. Does this mean that Weblogic always runs ejbLoad() every x seconds or ONLY if some client runs findByPrimaryKey() and the interval has expired?
Thanks,
A. -
Anyone knows how to achieve SerialPort Read Timeout? Or in another way to say it, stop reading from the SerialPort.
Remove the Serialport listener Maybe !
Maybe you are looking for
-
Only partial songs downloaded when I purchased an album. How do I fix this without having the buy the whole album again?
-
Hi Can anyone provide me with the MM process life cycle . please forward me the documents on [email protected] Thanks and Regards Naval
-
UTC Warning Message each second in log file
Hi, i'm running a Oracle NoSQL Store (2.0.23) in a 2 node environment. In the web admin interface under "logs" i find the message +"UTC WARNING [rg1-rn2] Exception in ResolveHandlerThread when contacting:rg1-rn2"+ repeating each second. A more detail
-
Even after a system restart, FFX either won't respond to an open, or if it opens, frequently won't follow a hypertext link. I have to use the W7 Task Manager to end the FFX process, then start over. This is recent, perhaps for 3 months, and is gettin
-
Condition type for Opportunity
Hi all, My client requirement is to calculate net value of the product automatically. and condition tab is deactivated in the opportunity. any one suggest to how can i activate the condition tab. and condition for an opportunity regards sat