Forum thread: forum.pjrc.com... An earlier version of this video had a few rookie editing mistakes. I also put readable text in the max frequency test, since the function generator screen has low contrast white-on-blue text.
Brilliant, I shelved a teensy 3.2 interrupt-based project around the time you uploaded this (3 yrs ago), because of missed interrupts, but decided to revisit it this week I wish I'd seen this then! (I was also swamping the serial upload to my pc, also solved here🤷♂️)
On these videos, please start by saying what board you are using. I finally saw it on the forum post but needed to look for that. Thanks for all you do. Much appreciated.
your hitting the capacitive coupling on the breadboard, IIRC breadboards are good till about 10MHz due to stray capacitance on the fingers inside the breadboard (2-20 pF per pin pair)
Considering your square wave is closer to a sinewave maybe the counter correctly drops a few where the gatevoltage wasn't reached? Your teensy would be more forgiving.
no prior count will only happen when serial prints if new count changes within the delay(10) then prior count will be different from new count and it will be updated at the next loop cycle. basically 10 milliseconds after new interrupt the last new count value is guaranteed to be the correct value.
@@jerrymk6846 So, if the interrupts are coming in faster than the Serial.print function can be executed, that's when they stop being displayed in the console, correct? It'd still be counting in the background, but wouldn't be printing it out.
@@toastrecon The counter is basically always up-to-date (because changing a variable doesn't take any significant time). The value will only stop getting printed when the previously printed value is the same as the current counter. The "previously printed value(prior count in the code)" is guaranteed to update when a serial print happen. If the counter got updated while serial print is running, the counter will be up-to-date, but the "previously printed value" will not be same as the counter, and then the value will be printed out within 10ms after. EDIT: Oh yeah I re-read the code and you are correct. If prior_count = new_count; line is moved to before Serial.printf then it will be less likely to happen. Serial print actually takes quite some time and may lose a lot of counts... Basically an oopsie happens when counts happen within Serial.print function
I think vids where something didn’t work are far more useful! It calls into question if the freq counter is accurate...... I use the same line of argument with my wife
I am trying to run a similar test with a MKR 1400. I have found the section of code in variants.cpp that shows the mapping between the physical pins on the MKR 1400 and the interrupt numbers. However I don't know how to set the priority for a specific hardware pin, #4, to priority 1 using the function NVIC_SetPriority( (IRQn_Type) int_num, int_prio). Pin #4 maps to PortB10 and extint 10. When I try NVIC_SetPriority( 10, 1) I get a compiler error: invalid conversion from 'int' to 'IRQn_Type {aka IRQn}. Am I missing some function call that gets me to the right type of interrupts? Thank you for your video. Dan
Hi Paul! Thanks for your video and also your library. I have a question, so I am trying to figure out the frequency of my incremental encoder, which has 2 phases(A&B), with arduino UNO. Using the freqCount library then I have to hook one of the phase to the digital pin (6)? Is that right?
Would this work for external switches? For example if I have a toggle switch operating a motor (forward and revers directions) and have two limit switches to bound the distance the motor can move. Can I give the limit switches the highest priority so that the movement of the motor is halted when limit switches are closed ? Thanks!
i want to use (Sensor generated ) interrupts as a counter for fast moving objects. like seed counter. but i need to know which sensor will be most useful to detect the small grain sized particle to trigger the sensor and cause interrupt.
So far nobody has ported this code to the SAM chip used on Due. In theory it could be done, if someone familiar with that chip's timers puts a lot of work into porting the code. That chip also supports interrupt priorities, but Arduino's core lib and all the other libs for that chip don't make use of the priorities, so to get the interrupt priority part working would require a lot more coding work...
Nice your video. Good job. You please helping sir. I have a Mike one project but one problem. Am Arduino programing ( I'm just starting to learn) Unable to write program.?
RU-vid comments aren't the place to get this sort of technical help. Forums are where to ask. If whatever board you're using has a forum, ask there. If you have a generic board which doesn't have a support forum, but you're using the Arduino software, ask on Arduino's forum. forum.arduino.cc/
#1 - Make a good first impression. The main way is showing you are trying. People want to help others who make a sincere effort, even if that effort is just trying Google searches and not yet knowing the correct words.
#2 - Give context. Explain your goals or what you are trying to accomplish. People who understand your needs can answer much better than if you ask a narrowly focused or overly vague question without any explanation.
#3 - Share details. Say which software, hardware you're using and give screenshots, photos, exact code or error messages. Details matter for solving tech issues. People who see your question will be able to help only if you give enough info.
Yes, NVIC_SET_PRIORITY is a Teensy only thing. Other 32 bit ARM chips have interrupt priority with their own ways, but Uno's interrupt hardware doesn't have priority capability, so there is no way to do this on Uno.
Longer answer: best to ask on the forum, where you can write a more detailed question which gives context to understand what you're really trying to accomplish with your project, and specific details like the hardware and code you're already using. Comments on social media sites like RU-vid are good for only quick questions and simple answers. Forums are where you go for more in depth discussion of how to do a design a project and structure your code.
@@lovermonkey Well, there are 3 things to do when writing a forum question that greatly improve your chances. 1: make a good 1st inpression, 2: give context about what you're really trying to accomplish, and 3: share specific details so people can at least see and maybe even reproduce whatever technical issue is at hand.
The 2 ways to make a good first impression are 1: demonstrate you've made some effort (photos are best) and 2: appear to be genuinely interested in learning.
I am sorry, i cant find it in that relatively short link(single page). Maybe you want me to ask the specific question on the forum ? Maybe i can be a bit more specific. The loop and millis interrupt are not declared by me, they are probably done somewhere behind the screens by the IDE? If i want to make sure the interrupt that i define by: attachInterrupt( ...) goes before serial but after loop, what priorities are available to me? Or alternatively what is the syntax for changing the interrupt priorty of loop and millis ? I found default Serial interrupt is 64? USB is 112 ? systick is 0? Then what happens if i set pin_interrupt priority to 0 as well?
SysTick defaults to 32. When an interrupt runs, it blocks all others at the same or higher (lower number) priority. So if you have two interrupts at priority 0 (the highest you can set for normal interrupts), then whichever happens first gets serviced and the other waits until the first completes. The same is true for any pair at the same priority.
