I'm currently using A.09.42.12 firmware. I have a .csa file where I want to to set the group trigger to 10 for all the measurement channels. However, everytime I recall the file, it reverts back to 1. So that setting is not being saved for some reason. It is a pain, since I have about 30+ channels and I have to change it back to 10 again one by one.
Also, here are some other minor firmware issues I have encountered:
1) In the IM spectrum measurement class, if you specify a 10kHz span, the frequency listed at the right edge is incorrect. (see attached for details). For the example, it should be 999.995Mhz to 1.000005 Ghz, not 1.00001Ghz.
2) When using the PNA with the older firmware version, it would list the smoothing amount used in the 'Trace Attributes Table' when generating a pdf printout. But with the new firmware, that information seems to have disappeared!
3) For a single trace with several markers, if I enable trace statistics on it, it will only show 1 of the markers and cover the rest up with the statistics table. I don't see why you can't show all the markers and the statistics table at the same time.
4) When performing a calibration with an e-cal unit using the wizard, during some steps, I noticed the blue light on the ports already lit on before even having a chance to click the 'Measure' button and connecting it to the e-cal port! I am worried this might pose some radiation risk, especially when calibrating at high power and frequency levels.
If someone can looking into the group triggering settings not being saved and address the other minor issues, that would be greatly appreciated.
You are correct, the trigger count for groups is not restored during recall. I'm submitting a defect against this and we will fix it in our next release.
With regard to your itemized comments:
1) IMD frequency: this is an artifact of display annotation rounding. We have limited space on the display, consequently we have to limit the resolution of all amplitude and stimulus numbers written on this surface. This is not peculiar to IM Spectrum, but in IMD and IMS you'll tend to notice it more due to the way frequency is configured for those channels.
2) Smoothing number missing from the print trace attributes table.
This feature is available in our standard sparameter channel but is missing from the print outs for the rest of our channel types.
3) Marker display limited when trace statistics is displayed.
I will forward all three of the above comments to our user interface engineer.
4) Cal ports on before pressing "Measure". This is done to provide the user with a live trace that can be used to ensure that the next standard is connected properly. The remote interface does not behave this way. But the graphical cal wizard intentionally has this behavior. The native port power is quite low compared with many consumer devices such as cell phones.
Thanks for the reply. I have another UI comment to pass along that my operator discovered today. For an SMC channel, if I pick the S11 measurement trace to get RF return loss, the x axis displayed by default is that of the IF output frequency range, instead of the RF input frequency range. I know I can manually change it, but it would be nice if the firmware can be made to automatically default to the right x axis range just for that case, to match the behavior of the normal s-parameter measurement class.
thank you for your comment. we have toyed with this idea before about letting the input or output nature of the parameter decide what the appropriate x-axis is. in the case of SMC for parameters like S11 or IPwr, the choice seems obvious, but it is not so obvious for the transmission parameters like SC21 or SC12. there are also other implications resulting from having different x-axis on different parameters in the same channel. As an example imagine you have an S11 and SC21 trace in the window and the S11 is using the input range as the x-axis and the SC21 is using the output range. on your SC21 trace, you notice a large anomaly and you place a marker on the location. you might think that the anomaly is due to a bad mismatch at the input and want to know what the return loss is at the same frequency where the anomaly occurs. if you try the coupled markers approach, it won't work because marker positions are keyed off of the x-axis selection and the two traces have different x-axes.
my point wasn't to make an excuse, but to illustrate that this particular choice of behavior is one of those that no matter what we decided to do by default, would make some people happy and some people not so happy. our compromise in the SMC channel was to default all the x-axis range selections to one range (namely output), but allow the users to actually change the x-axis range on individual traces.
Another alternative for dealing with the limited number of markers visible when showing Trace Statistics is to view the individual markers in the Marker Table. There are several ways to turn on the Marker Table. Here's one way: press Marker, More Markers, Marker Table ON.
Thank daras for the pro/cons of the x axis default behavior or not. I guess you can't please all the people all the time.
Thank djm for the suggestion. What I'm doing now is just creating a duplicate trace where I put all the markers, and use the other trace to display statistics. It's just annoying that I have to resort to this when it should be straightforward to just put the statistics table after all the marker display.
I was evaluating the A.09.50.13 firmware which is the latest release for the PNA-X N5244 model we have to see if the group triggering settings not being saved bug was fixed or not. However, it seems to work for S-parameter measurement class channels only! When I tried it for other types of measurement classes such as noise figure for converters and SMC type channels, the group triggering settings were still not being saved properly. (default to a value of 1). Can Agilent verify this and flag it to fix in future firmware releases?