Help Needed: Using Interrupts for DIN0 on GEVCU Board
- Thread starter Lucifer D
- Start date
- Status
PaulStoffregen
Well-known member
Did you ask this same question just yesterday?
Thank you for your feedback. I realize that creating a duplicate thread might not have been the best approach, and I sincerely apologize if it caused any inconvenience or frustration. The question is genuinely important to me, and I felt that the responses in the previous thread didn’t fully address the specifics of my concern.
If there’s a better way to approach this or provide more context to make the question clearer, I’m open to any suggestions. I truly value the knowledge and expertise of this community and appreciate any guidance you can offer.
If there’s a better way to approach this or provide more context to make the question clearer, I’m open to any suggestions. I truly value the knowledge and expertise of this community and appreciate any guidance you can offer.
Rezo
Well-known member
I think maybe it didn't get enough exposure yet. It's the weekend after all.
All you need to do is figure out which Teensy pin DIN0 is, then you can use the sample code that Paul provided on the other thread.
If you load the GEVCU7 codebase into Visual Studio Code, or Sublime Text for example, you will easily be able to backtrack the code to the Teensy pins
All you need to do is figure out which Teensy pin DIN0 is, then you can use the sample code that Paul provided on the other thread.
If you load the GEVCU7 codebase into Visual Studio Code, or Sublime Text for example, you will easily be able to backtrack the code to the Teensy pins
PaulStoffregen
Well-known member
Duplicate questions do not help. This only annoys people who might try to help. This new question also lacks the info which was found on the first one, so anyone trying to help has to start back at the beginning without the benefit of that info!
If your original question goes quiet, the best thing you can do is add another comment on the original question. Try something, like another test with a small Arduino-only program and show what happened, even if the wrong result. People who help tend read many questions on this forum, and probably many other websites. They have to choose which places to spend their time helping. If you show that you're trying things, even if they are wrong or not working (the reason you're asking for help), people tend to choose your question when they see you are making a real effort. Even just sharing a photo of your not-yet-working project can make a really good first impression. Remember, everyone sees your question among many others. Make a good impression rather than re-asking the same short question again.
If your original question goes quiet, the best thing you can do is add another comment on the original question. Try something, like another test with a small Arduino-only program and show what happened, even if the wrong result. People who help tend read many questions on this forum, and probably many other websites. They have to choose which places to spend their time helping. If you show that you're trying things, even if they are wrong or not working (the reason you're asking for help), people tend to choose your question when they see you are making a real effort. Even just sharing a photo of your not-yet-working project can make a really good first impression. Remember, everyone sees your question among many others. Make a good impression rather than re-asking the same short question again.
- Status