LabVIEW
Can't read markers from Agilent PNA
@hammer3 wrote:
Since these fellows were little help with lots of sarcasm, I eliminated the limit lines and checked limits with post processing.
I think you chose the right way of doing this anyway because it is much more scalable, flexible and less of a pain to program. Markers and limit lines are good for manual measurements, but the way you did it is much better for automated measurements. 🙂
As for the RTM comments, I prefer to cobble together something then RTM after the first command doesn't work. 😉
@nyc_(is_out_of_here) wrote:
@billko wrote:
@hammer3 wrote:
Since these fellows were little help with lots of sarcasm, I eliminated the limit lines and checked limits with post processing.
I think you chose the right way of doing this anyway because it is much more scalable, flexible and less of a pain to program. Markers and limit lines are good for manual measurements, but the way you did it is much better for automated measurements. 🙂
As for the RTM comments, I prefer to cobble together something then RTM after the first command doesn't work. 😉
For the PNA, it helps to understand how that $100K piece of equipment actually works. It isn't a power supply.
If you think it is pointless to RTM, so be it.
As for the limit lines, the OP was the one who wanted to use markers and limit lines in the first place.
When he couldn't figure out how to program it it, he changed his mind, and decided to do the sensible thing with post processing of data.
While I usually try to mimic a manual measurement when automating it, this was a good argument for trying something different.
I didn't say it was pointless to RTM. Actually, if it is a new piece of equipment - like in the case of the OP - the first thing I do is crack open the programmer and the user guides. Then I cobble something together and RTM more when it doesn't work right. 😉
