Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
en:netzer:impulse [2014/08/16 18:14]
svesch [Generating impulses in IO0 triggered mode]
en:netzer:impulse [2014/08/17 16:10]
svesch Reordered headlines
Line 3: Line 3:
 Netzer is able to generate and capture signals at IO3 and SPI_INT. Netzer is able to generate and capture signals at IO3 and SPI_INT.
  
-{{ :​en:​netzer:​impulse_overview.gif?​direct&​600 |}}+{{ :​en:​netzer:​impulse_overview.gif?​direct&​700 |}}
  
 The image shows the structure of the impulse generator/​capture. The image shows the structure of the impulse generator/​capture.
Line 21: Line 21:
  
  
-===== Unsynchronized mode =====+===== Examples ​=====
  
-The impulse timer is free running in this mode.  +Some of the examples below show both signals IO3 and SPI_INT.
-Changes on IO0 will not reset the impulse timer. +
- +
-The examples below show both signals IO3 and SPI_INT.+
 Of course impulse module can be configured to use only one of them. Of course impulse module can be configured to use only one of them.
  
-The examples only show positive logic.+The examples ​below only show positive logic.
 Simply invert the signals to get negative logic examples. Simply invert the signals to get negative logic examples.
  
 +In the IO0 examples the IO0 trigger is configured for rising edge.
 +Simply invert the IO0 signal to get falling edge examples.
  
-==== Generating impulses in continuous mode ====+ 
 +==== Generating impulses in continuous mode (Unsynchronized) ​==== 
 + 
 +The impulse timer is free running in this mode.  
 +Changes on IO0 will not reset the impulse timer.
  
 {{ :​en:​netzer:​impulse_compare_cont_unsync.gif?​direct |}} {{ :​en:​netzer:​impulse_compare_cont_unsync.gif?​direct |}}
  
  
-==== Generating impulses in single mode ====+==== Generating impulses in single mode (Unsynchronized) ​==== 
 + 
 +The impulse timer is free running in this mode.  
 +Changes on IO0 will not reset the impulse timer.
  
 {{ :​en:​netzer:​impulse_compare_single_unsync.gif?​direct |}} {{ :​en:​netzer:​impulse_compare_single_unsync.gif?​direct |}}
  
  
-==== Generating impulses in "​Triggered by IO0" mode ====+==== Generating impulses in "​Triggered by IO0" mode (Unsynchronized) ​====
  
 This mode shall not be used. This mode shall not be used.
  
- +==== Generating impulses in continuous mode (IO0 synchronized) ​====
-===== IO0 synchronized mode ===== +
- +
-The impulse timer is reset (set to 0) by IO0 trigger.  +
- +
-The examples below show the IO0 signal and both signals IO3 and SPI_INT. +
-The impulse module can be configured to use only one of them. +
- +
-IO0 is configured for rising edges in examples. +
-Simply invert the IO0 signal to get falling edge examples. +
- +
-The examples only show positive logic. +
-Simply invert the signals to get negative logic examples. +
- +
- +
-==== Generating impulses in continuous mode ====+
  
 This mode shall not be used. This mode shall not be used.
  
  
-==== Generating impulses in single mode ====+==== Generating impulses in single mode (IO0 synchronized) ​====
  
 {{ :​en:​netzer:​impulse_compare_single_sync.gif?​direct |}} {{ :​en:​netzer:​impulse_compare_single_sync.gif?​direct |}}
  
  
-==== Generating impulses in "​Triggered by IO0" mode ====+==== Generating impulses in "​Triggered by IO0" mode (IO0 synchronized) ​====
  
 {{ :​en:​netzer:​impulse_compare_io0_sync.gif?​direct |}} {{ :​en:​netzer:​impulse_compare_io0_sync.gif?​direct |}}

QR Code
QR Code Impulse handling with Netzer IO (generated for current page)