所有返回到2000年引入的第一个PNA都使用相同的核心固件。
当然,在引入新功能时会添加新命令,但是为早期的E8358A编写的代码仍然可以在最新的PNA或PNA-X上工作(只有少数例外)。
您可能遇到的唯一问题是,如果司机首先进行* IDN?
查询并将型号与预期结果进行比较。
我知道有些司机可以选择忽略这种比较。
但除此之外,司机应该工作得很好。
我们的编程页面上列有一个驱动程序,但它的日期是2010年,也不包括N5234A。
http://na.support.keysight.com/pna/programming/
以上来自于谷歌翻译
以下为原文
All PNAs going back to the first one introduced in 2000 use the same core firmware. Of course, new commands are added as new features are introduced, but code written for an early E8358A will still work on even the latest PNA or PNA-X (with only a few exceptions).
The only issue you could have is if the driver first does a *IDN? query and compares the model number to the what it expects. I know some drivers have the option to ignore this comparison. But except for this, the driver should work just fine.
We have a driver listed on our programming page, but it is dated in 2010 and will also not include the N5234A.
http://na.support.keysight.com/pna/programming/
所有返回到2000年引入的第一个PNA都使用相同的核心固件。
当然,在引入新功能时会添加新命令,但是为早期的E8358A编写的代码仍然可以在最新的PNA或PNA-X上工作(只有少数例外)。
您可能遇到的唯一问题是,如果司机首先进行* IDN?
查询并将型号与预期结果进行比较。
我知道有些司机可以选择忽略这种比较。
但除此之外,司机应该工作得很好。
我们的编程页面上列有一个驱动程序,但它的日期是2010年,也不包括N5234A。
http://na.support.keysight.com/pna/programming/
以上来自于谷歌翻译
以下为原文
All PNAs going back to the first one introduced in 2000 use the same core firmware. Of course, new commands are added as new features are introduced, but code written for an early E8358A will still work on even the latest PNA or PNA-X (with only a few exceptions).
The only issue you could have is if the driver first does a *IDN? query and compares the model number to the what it expects. I know some drivers have the option to ignore this comparison. But except for this, the driver should work just fine.
We have a driver listed on our programming page, but it is dated in 2010 and will also not include the N5234A.
http://na.support.keysight.com/pna/programming/
举报