Open Pro140 opened 2 months ago
@Pro140 could you use an external trigger instead?
@Pro140 The external trigger work for you? I want to know so that I can close this issue.
Hi. I tried with external trigger but still the same. I think the error was due to the fact that the mcu was not giving big enough pulse to cross the 2.31 V mark and thus was not getting recognised. Currently I had to put the project on hold till other amplification parts arrive. Thankyou for your response!!
Please let me know your findings.
Also add proper decoupling capacitor as the ASIC is very sensitive.
It's a pity that the first release of this library works and was tested with both internal and external tools. But after some comments from other users I modified it but with little to no test. Currently, I don't have access to the hardware setup anymore so I want to avoid modifying it without confirming with an external trigger because internal triggers might be prone to noise.
Your contributions would be greatly appreciated Thanks in advance
Hi! Just wanted to ask and make sure are there any changes in the code required if the start and stop signal are external(i.e not given from arduino/teensy itself)? Also are there any changes in the physical connections, like any extra connection other than changing the start and stop wire? Thank you in advance for your time!
The only changes would be to connect the external source to the start and stop pins of the TDC. You'll get interrupts for new measurements
I am using teensy 4.0 (very similar connections like arduino) in place of arduino along with tdc7201 ZAX EVM board. Initially I am aiming to produce start and stop pulse using the teensy itself to check whether or not the tdc7201 gives the correct time difference in between the two pulses generated by the mcu, i.e the very same thing which is performed in the example folder of yours. In this I am facing the following message
"TDC720X Time-to-Digital Converter (TDC) Dual Core example
Time between pulses (given): 100
CLOCK_CNTR_OVF_INT
CLOCK_CNTR_OVF_INT too many stops too many stops too many stops too many stops too many stops too many stops
NO NEW_MEAS_INT
NO NEW_MEAS_INT"
This is the message being displayed on the serial monitor and the 100 increments after each second. I am using the exact same code and the exact same pin config (as teensy and arduino pro mini have almost all the same pinouts). What could possibly be wrong due to which the time of flight is not being displayed and instead these error debug script are being displayed. Thankyou for your assistance in advance.