Hi,
This is my unassuming contribution to this thread that Dave started long ago. I'm sure that if he had had access to this table his life would have been a lot easier (but surely less fun!). Nonetheless, and for historical/reference reasons, i attach below a table of all the IDs that the 1000X app code (WinCE and Linux) accepts.
(Don't bash me, i know that most of this information is now old news for the more knowledgeable.)
My analysis is based mainly on the appcode analysis and validated with all the information shared by all of you throughout this thread (specially with the videos that started all of this). Unfortunately, I don't have any of these instruments.
All the Product_Configs that are not in the table have no significance whatsoever and result in invalid configurations. (As you see, there aren't so many scenarios as one might think.)
As you all know, executing the resistors_mod sets the
voltage levels read by ADCs 0-7 (ADC 4 value is not used anywhere in the code).
Of course, one thing that is possible to do with a software patch, that the resistors_mod is unable to achieve, is that, by tweaking the table params, we can further change the behavior of each Product_Config setup. With that we can try different configurations that have not been tried before...
I marked in red the 2 cases that Dave found strange in his video and the parameters, that in my analysis, affected them. For example, further sample rates of 2.5GHz could be attempted by placing 0 in the SampleRate field of the "usual" Product_Configs 21-24.
It's also perfectly visible which are all the configs "FPR (Final Production Run)".
WinCE versions only go up to Product_Config 27. The remaining ones are only visible in the new Linux software.
If you see any errors please report. If you would like to test some software tweaks, maybe I can help.
![](https://www.eevblog.com/forum/blog/eevblog-978-keysight-1000x-hacking/?action=dlattach;attach=1615900;image)