You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
first things first: Thanks so much for conceiving this data logger and also for sharing your design files and firmware code with the community. Keep up the spirit!
I found a short opportunity to quickly look at the code and found a specific thing I would like to mention here. As we can see with these lines initializing the ADC
The text was updated successfully, but these errors were encountered:
amotl
changed the title
Use pyb.ADC.read_timed() interface for more robust audio sampling
Use "pyb.ADC.read_timed()" interface for more robust audio sampling
Feb 17, 2019
amotl
changed the title
Use "pyb.ADC.read_timed()" interface for more robust audio sampling
Use "pyb.ADC.read_timed()" interface for more robust audio sampling?
Feb 17, 2019
Hi @jacobron,
first things first: Thanks so much for conceiving this data logger and also for sharing your design files and firmware code with the community. Keep up the spirit!
I found a short opportunity to quickly look at the code and found a specific thing I would like to mention here. As we can see with these lines initializing the ADC
EasyHive_Pycom_Shield/V1.0/software/main.py
Line 12 in cc5b18d
EasyHive_Pycom_Shield/V1.0/software/main.py
Lines 157 to 160 in cc5b18d
and later code for stuffing data into the buffer, this uses the highlevel ADC interface from the
machine
package.On the other hand, I found the lowlevel ADC interface from the pyboard package provides convenient
read_timed()
and evenread_timed_multi()
methods. This feels a little bit like it would be more efficient when shuffling data around. What do you think about this?With kind regards,
Andreas.
The text was updated successfully, but these errors were encountered: