06-27-2008 10:26 AM
Alex,
Are you seeing the Undefined Header error on the screen of the OSA? I will review the code and the SCPI commands and see if I see the error. Also, did you confirm that the GPIB address between the OSA and the application were the same? Likely they are as we ususally don't get a TO error if we didn't at least get info to the instrument.
I will modify the driver to use the LabView native VISA functions, and I think you will see what I am talking about. I don't really have anything against the instrument driver per se, but there with this example, there is no real reason for it. I find with as much instrument control as I do, sometimes I use the drivers (typically ones developed NI), and sometimes I do my own. Usually when I do my own, the available instrument driver VIs either do too much having other functions or they don't go far enough to get the setup or data I need. So I typically end up about 70% available drivers, and 30% my own overall.
I have some stuff on my plate this morning, so I will try to get this out this afternoon, or sometime Monday if things fall apart around here today.
06-27-2008 10:35 AM
Alex,
I was able to make a quick modification to the New Example 2.vi that may fix the GPIB errors. Looking at the programming manual you sent, and my experience with SCPI, I added a : to the beginning of each command. The commands themselves looked to be correct, so I am hoping you were getting the unterminated header errors and this will fix it. Let me know what you find.
06-27-2008 10:41 AM
06-27-2008 11:35 AM - edited 06-27-2008 11:37 AM
06-29-2008 10:09 PM
I will modify the driver to use the LabView native VISA functions, and I think you will see what I am talking about. I don't really have anything against the instrument driver per se, but there with this example, there is no real reason for it. I find with as much instrument control as I do, sometimes I use the drivers (typically ones developed NI), and sometimes I do my own. Usually when I do my own, the available instrument driver VIs either do too much having other functions or they don't go far enough to get the setup or data I need. So I typically end up about 70% available drivers, and 30% my own overall.I have some stuff on my plate this morning, so I will try to get this out this afternoon, or sometime Monday if things fall apart around here today.
06-30-2008 09:54 AM
Sorry this took so long. Busy day on Friday.
Attached should be a simplified version of the same example. Let me know if you have problems with it running. As you can see, we should be able to accomplish the exact same functionality as we did with the instrument drivers, but we used the native VISA functions within LabView. If you run this and get the error popup, please let me know what the instrument itself did. Did it display any error messages on the screen such as unterminated header or query?
As for your final solution let me make sure I understand your goal. You want to continuously pull marker points from the analyzer and plot them into a strip chart, is that correct? If so, do the markers need to be repositioned each time or do you place them and just want to watch them for a period of time?
Just an FYI, I have a pretty busy week this week. I will try my best to keep the communications coming as quickly as possible, but I may get delayed here and there, so please accept my apologies in advance.
06-30-2008 10:28 AM
06-30-2008 10:49 AM
Your second option is going to be what you are going to use most likely. I am not sure if the OSA has the ability to peak track, but even if it does, if it works like I have seen on our RF spec ans its not the best, and it cannot track multiple peaks. So yes, best thing to do is pull the trace via GPIB, then write some analysis to find the two peaks.
I was looking at the Agilent trace capture LLB that you sent, and you can likely use the VIs in it, specifically the trace plot. Dont use the HCOPY version as that will just generate a useless GIF of the screen, and it takes 30 seconds or so to do that. You just want the formated trace data.
I don't really have any specific times I am available, but ususally I am more active here in the evenings. Since it will be a couple of days for you to get to the equipment I think things will work out just fine.
06-30-2008 05:44 PM - edited 06-30-2008 05:47 PM
06-30-2008 07:36 PM