Differences

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

--- analyzer:manual:export [2010/04/29 19:39] – sestst
+++ analyzer:manual:export [2010/06/06 22:54] – sestst
@@ Line 4: / Line 4: @@
 The ProtocolAnalyzer allows you to save sessions of signals via the file menu. These save files are binary representations of the session and cannot be used from other programs.
-There are however other ways to save data from the received signals. One way is to save data from decoded messages via the "Export Data" function the other is to save the raw pulse data.
+There are however other ways to save data from the received signals. One way is to save data from decoded messages via the "Export Data" function the other is to export the raw pulse data.
 ===== Export Data =====
@@ Line 19: / Line 19: @@
 All the decoded signals are now saved in a text file according to the template.
+===== Export Pulse Data =====
+You can also export the raw pulse data from an undecoded signal. In the main window you right click on a raw sample line. On the context menu you select "Export Pulse Data":
+{{:analyzer:manual:raw_context.png| Context Menu}}
+Select a file name and press "Save". This will save a text file containing the lengths of the pulses in the signal in the following format:
+  s198980
+  m8501
+  s4152
+  m587
+  s1499
+  m542
+  s1567
+  m587
+  s1522
+Each line consists of a letter, //s// or //m//, meaning "Space" or "Mark". After the letter comes a figure which is the length of the pulse in micro seconds.
+\\
+\\
+\\
+----
+[[analyzer:manual:start|{{ :analyzer:manual:arrow_up_blue.png |Up - Start}}]]\\
+[[analyzer:manual:undecoded_window|{{:analyzer:manual:arrow_left_blue.png |Previous - Signal Analysis}}]] [[analyzer:hardware|{{ :analyzer:manual:arrow_right_blue.png|Next - Hardware}}]]