Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
You are correct. You can connect as many inputs as you want.
If you want to reduce the external wires, 6 of the 8 projects have an additional schematic page that is currently disabled.
This disabled page internally routes the stimuli to the inputs without need of external connections.
To use the disabled page, you need to first disable the page with the pins. Next enable the 0 pins page. It will give some warnings. Answer "OK". Rebuild the project and ... viola! All the inputs will have stimuli. Although the input pins are eliminated, the stimuli is still routed to the output pins.
It appears you compiled Project#1 using Polling strategy. CPU utilization: Scan = 99%. Highly inaccurate results at higher frequency inputs.
Spoiler Alert: Projects #8 has the best performance. CPU utilization: DMA = 0.05% ISR=0.0% Task = 4.8% The application can have 95.1% CPU cycles available.
It also provided the best measurement performance even for high frequencies.
Len "Engineering is an Art. The Art of Compromise."