05-14-2010 09:13 PM
HI again,
The self test doesnot work, I mean it always returns 0(error) even usng it individually. so I remoced it and used the similar code to one that you posted me to regulate the current(of course with out the case structure). it works but the same error as before due to overrun buffer, I added a delay as well as output enable-disable, but the errors still remain.
Really I got stuck with this PSU!:(
Anyway appreciate your helps.
05-19-2010 07:30 AM
Hi Ela,
the selftest is supposed to return 0 which is no error. So self test is ok. I made a mistake in my example...
At this point, personnally I wouldn't have used a big power supply to regulate a Peltier, especially when speed is needed. I believe there exist power circuits that would deliver high current faster with op-Amp (or simple transistor circuit) that you would set with a simple DAQ card that would be much more faster.
For the moment I have no solution. I'm sure I've seen this kind of problem with the IVI driver (IVI-DCpwr layer that uses the xanxtr) but my conditions are different, not the same model using serial port.
Just for sake of good debugging, what is the GPIB card used (was it a usb to gpib, if yes verify if on a usb2 "enhanced" port)? Have you updated its driver to the latest? Is there an api where you can adjust its speed (sometimes its fixed 1Mb but there is also jumpers on certain cards)? You're PSU is alone on the node or is there other GPIB instruments(verify that addresses are all different)?
Have you tried your vi on serial port (if any on psu)?
On my side I'm using serial port, so I might not have this problem if problem is related to communication port.
If I get an idea of a solution I'll come back with it.
Regards,
05-19-2010 10:58 AM
Thanksssss Richard,
Meanwhile I started to use power circuit and today I am going to test it and hope it works.
For your information, I am using serial communication like you , I just now remembered that I have the option to work with higher baud rate. it may help.
About self test, I checked it again now, it should passes 1 if it works, 0 means it fails and I think it is right because when I used self test in the code, the code's stuck when running and the next functions don't work.
Anyway, thanks for your help and suggestions, and it is great if you get and idea, share it with me.
thanksssss,
Elahe
11-30-2010 11:41 AM
Hello All,
I am having the exact same problem. Ela or anyone else, how did the basic communication get solved. I am using the usb and I am also trying to get hyper terminal to communicate with the xtr power supply but I get back nothing.
Regards,
sal_c
12-01-2010 09:16 AM
Hello Sal,
Have you had a chance to go through all of the steps in the Instrument Driver Troubleshooting Guide?
Cheers,
NathanT
12-02-2010 04:02 PM
Coudn't have said better than Nathan. Check the basics, haven't seen any problem with the xtr for at least the *IDN? request.
Problem relied on the ability of the XTR to daisy chain and making your power supply the master of all requests with the IVI driver.
Try to make this work first if there is a problem after you've accomplished this come back with your questions.
Regards,
Richard Aubin
05-19-2011 10:20 AM
Hi elahetal,
I'm using an ACsource Chroma 61604, and I have the same problem, error -1074135030. How do you to solve your problem?
I don't have error when I close the instrument chr616xx but when I want initialize I have the error -1074135030.
Could you help me please?
Thanks in advance
05-20-2011 05:12 AM
Hi
I reinstall the driver of chroma and now it works fine