| Electronics > Projects, Designs, and Technical Stuff |
| Using ESP32 and Neo-7N for precise frequency measurement |
| << < (9/11) > >> |
| mino-fm:
--- Quote from: imo on September 15, 2018, 08:38:02 am ---fyi: STM32F334 only - "high res timers" - 217ps resolution available for all operating modes, variable duty cycle, variable frequency, transition mode,… Those high res timers are used for fine adjustments of pwm in critical applications. It does not relate to the "precise freq measurments".. --- End quote --- This is right. --- Quote ---Otherwise the PLL's of all MCUs are a crap, so I would not use them for something called "precise frequency measurement".. ;) --- End quote --- That is wrong. There is no problem using an internal 100 - 200 MHz reference clock (period 5 ns) with less than 1 ns jitter to get 8 digits/s. STM32F407, ..411, ..427, ..429 work well and reliable. |
| ogden:
--- Quote from: tggzzz on September 15, 2018, 07:20:46 am ---Please don't invent strawman arguments. --- End quote --- LOL. You sound like hobbyist running all your projects including LED blinker on highest performance embedded hardware you have in your bin, most likely never had to think about BOM cost optimization. I can assure you: xCORE wins stm32 in all the categories you listed - in case you for some strange reason think that this is contest between two. Yet I do not see why frequency meter builder shall move to xCORE. IMHO it's gigantic overkill to use multicore MCU aimed at hard realtime applications for such a simple task as counting pulses using two timers. I can repeat - few timers of stm32 is enough for the task. [edit] Yes, I missed fact that hi res timers 217ps are output only resolution. |
| tggzzz:
--- Quote from: ogden on September 15, 2018, 04:53:20 pm --- --- Quote from: tggzzz on September 15, 2018, 07:20:46 am ---Please don't invent strawman arguments. --- End quote --- LOL. You sound like hobbyist running all your projects including LED blinker on highest performance embedded hardware you have in your bin, most likely never had to think about BOM cost optimization. I can assure you: xCORE wins stm32 in all the categories you listed - in case you for some strange reason think that this is contest between two. Yet I do not see why frequency meter builder shall move to xCORE. IMHO it's gigantic overkill to use multicore MCU aimed at hard realtime applications for such a simple task as counting pulses using two timers. I can repeat - few timers of stm32 is enough for the task. [edit] Yes, I missed fact that hi res timers 217ps are output only resolution. --- End quote --- Again you try to shift the argument away from your invalid, losing position. It would help if you comprehended what I did write and didn't write. And, again, don't fantasise what my position on subjects actually is! Have a look at the strapline in the blog in my .Sig, viz "doing more with less" |
| ogden:
--- Quote from: tggzzz on September 15, 2018, 07:51:29 pm ---Again you try to shift the argument away from your invalid, losing position. --- End quote --- Please explain. Am I losing to your stronger xCORE card or what? --- Quote ---It would help if you comprehended what I did write and didn't write. --- End quote --- What I did not comprehend? Explain! - Other readers of our conversation for sure would like to know. |
| tggzzz:
--- Quote from: ogden on September 15, 2018, 08:13:00 pm --- --- Quote from: tggzzz on September 15, 2018, 07:51:29 pm ---Again you try to shift the argument away from your invalid, losing position. --- End quote --- Please explain. Am I losing to your stronger xCORE card or what? --- Quote ---It would help if you comprehended what I did write and didn't write. --- End quote --- What I did not comprehend? Explain! - Other readers of our conversation for sure would like to know. --- End quote --- See my previous messages. Read what they contain. Do not read what they don't contain. |
| Navigation |
| Message Index |
| Next page |
| Previous page |