07-16-2015 09:45 AM - edited 07-16-2015 09:46 AM
I have read the manual,there are 2 commands ERRS,ESR.
There is a vi for ESR and one for ERRS.Both are used in my code.So now tell me what change is appropriate.
07-16-2015 09:48 AM
07-16-2015 09:51 AM
I guess at this point I've lost track of what is and isn't working for you. So, here's a checklist, and if you could please indicate which steps worked and which didn't:
1) Send command over RS232 to instrument from MAX (no response required). Change the frequency or something like that.
2) Send query from MAX and receive response. *IDN? is the usual test string.
3) Send command to instrument from LabView. Instrument executes command. Again, change the oscillator frequency.
4) Send query from LabView and receive response. Again, send a *IDN? and look at the response string.
Have you successfully executed all four steps? If not, there's no point in trying to diagnose the details of why reading a particular status register byte isn't working.
07-16-2015 09:53 AM
As per the original driver SW from ni webpage,the Single Parameter vi has both ESR and ERRS.
I am taking it as such,as i feel there is no change required.
The only change which i suppose is making it compatible with serail comm.
Deleting a Vi(ESR/ERRS),whether this is required???If so,does it not give further error??
07-16-2015 09:56 AM
I already Queried for IDN from MAx,Labview.I got the responsse too.
07-16-2015 09:58 AM
If you send the string 'SNAP? 1,2', what comes back?
07-16-2015 10:00 AM
Thanks for your response.They closed the lab just now.I can try with this command and let share the response here by tomorrow.
Thanks for your continued support.
07-20-2015 05:52 AM - edited 07-20-2015 05:59 AM
I tried with SNAP? 1,2,i was able to read X,Y values.
I tried with a Basic Serial Write and Read.vi.
May i know what exact changes in required in Stanford Research 830 Acquire Measurement - 1 Parameter.vi to get Serial data comm. with proper response for the commands??
07-20-2015 08:54 AM
Please reply to me previous post and also to this.
Why there is always a TimeOut error when ESR is queried.20bytes are read,as mentioned in the driver.
I change it to Read bytes from Port,which also throws error.
Whats the issue here and how to fix??
07-20-2015 09:19 AM
The most recent version of your error-query routine that you posted ('more_change.png' on July 13th) uses the Bytes At Port property. Did you follow Dennis's advice about eliminating that and using a proper termination character instead?
Similarly, if you use the Basic Serial Read Write command to query the status and error registers, do you get a sensible string back?