On 2013-02-19 10:33 -0800, Adrian Chadd wrote Sujith Manoharan: AC>It's easy enough to diagnose - just enable NF cal logging. Look at AC>what's being read back from the initial NF cal and what's being AC>written into the time-series average. AC> AC>It may be that something dumb is happening, like there's no AC>per-channel history, or the history from the wrong channel is being AC>used on a new channel. AC> AC>I know the reference driver has a couple of options (per-channel NF AC>history or shared NF history with a "scan" not using the history AC>buffer..) i do this already, in my case i dont see anything strange on NF claibration. C уважением With Best Regards Георгиевский Юрий. Georgiewskiy Yuriy +7 4872 711666 +7 4872 711666 факс +7 4872 711143 fax +7 4872 711143 Компания ООО "Ай Ти Сервис" IT Service Ltd http://nkoort.ru http://nkoort.ru JID: GHhost@xxxxxxxxxx JID: GHhost@xxxxxxxxxx YG129-RIPE YG129-RIPE
