Shortest time readable on interrupt - Netduino Plus 2 (and Netduino Plus 1) - Netduino Forums
   
Netduino home hardware projects downloads community

Jump to content


The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.
Photo

Shortest time readable on interrupt

Started by Julien, Aug 21 2013 06:16 PM

Best Answer Julien, 03 September 2013 - 12:54 PM

Hi,

Thank you for your answers, this is explain why I get some strange values around 10ms on netduino V1.

 

Go to the full post


  • Please log in to reply
3 replies to this topic

#1 Julien

Julien

    New Member

  • Members
  • Pip
  • 2 posts

Posted 21 August 2013 - 06:16 PM

Hi, Considering timers, I try to find what is the shortest time measurable with the netduino. For example, I press a button which starts a timer, and stops on release. Sure for a button, i will read the time precisely. Now if I want to measure response time of something quicker : a relay turn on time (µs). The Linux or Windows scanning time is around 25ms. Here it's different, we have a light embedded OS which is probably faster. What will be the shortest time measurable with IO interrupt ? I mean will I be able to measure precisely 1µs or rather 1ms ?

 

Many thanks

Julien

 


#2 Heroduino

Heroduino

    Member

  • Members
  • PipPip
  • 14 posts
  • LocationGermany

Posted 22 August 2013 - 10:22 AM

Hello Julien,

 

look this http://forums.netdui...h-class/However

 

You can call the ticks from netduino and calculate to microsecounds.

 

 

sincerely

Heroduino


#3 CW2

CW2

    Advanced Member

  • Members
  • PipPipPip
  • 1592 posts
  • LocationCzech Republic

Posted 26 August 2013 - 04:42 PM

.NET MF uses so called Slow Clock timer for interrupt timestamps, so the resolution (shortest time measurable) for Netduino is 1/46875 Hz = ~21.3µs, for Netduino 2 it is 1/1000000 Hz = 1 µs. But, in general, .NET MF is not really suitable for precise measurements in microsecond range, due to its non real-time nature (e.g. there can be shared interrupt for multiple pins, interrupt events are queued, garbage collector can run etc.).

#4 Julien

Julien

    New Member

  • Members
  • Pip
  • 2 posts

Posted 03 September 2013 - 12:54 PM   Best Answer

Hi,

Thank you for your answers, this is explain why I get some strange values around 10ms on netduino V1.

 


Back to Netduino Plus 2 (and Netduino Plus 1)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

  1. Netduino Forums
  2. → Hardware
  3. → Netduino Plus 2 (and Netduino Plus 1)
  4. Privacy Policy
home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.