When all options are set and done, you can now select to compute the raw count values that would be printed by the selected controller, if it was connected with the selected sensor or the acquisition time of the setup. This analysis is a Spice analysis.

From the “Analysis” tab you choose Controller Counts Analysis and you are prompted in a new screen with more options.

In this new screen, you are asked to select the System configuration of your choice (usually this is the one that you just set up), as well as to select the Max Count value of the controller; this is the maximum value of Counts that can be measured and has to do with the duration of the analysis. The default value of 10,000 Max Counts is enough for most cases.

In the next screen you may choose to include conducted noise in the analysis. let's skip it for now, since you can read more about noise simulation here and also in this extensive use case.

Next you are now prompted to choose the Resources. 8 cores and 16 GB memory are usually enough for this type of analysis. In a few minutes the Spice simulation is complete and the Counts for each Pin that was active are printed.

In case you have added a Pointer, you can also get the Delta Counts, that is, the difference in Counts between cases of pointer and no pointer. As expected, higher values of DeltaCounts are observed when the pointer touches each specific button:

Furthermore, you can view the Acquisition Time, that is, the time needed for one charge-discharge cycle of the sampling capacitor for each button:

Did this answer your question?