DATA TRANSFER USER GUIDE

MAGPRO G3 DATA TRANSFER USER GUIDE

MagPro G3 Data Transfer User Guide

The contents of this manual are the property of Tonica Elektronik A/S. Any reproduction in whole or in part is strictly prohibited. Tonica Elektronik A/S has a continued development of its products. Tonica Elektronik A/S re-serves the right to change and improve the products described in this document. Furthermore Tonica Elektronik A/S reserves the right to make changes to this document at any time without previous warning. At the time of printing, this manual correctly described the device and its functions. However, as modifications may have been carried out since the production of this manual, the system package may contain one or more addenda to the manual. This manual including any such addenda must be thoroughly read, before using the device. The following situations void any guarantee(s) and obligations for Tonica Elektronik A/S: - The device is not used according to the enclosed manuals and other accompanying documentation - The device is installed or modified by persons other than Tonica Elektronik A/S service techni-cians


Introduction 3

Contents Introduction....................................................................................................................... 4

Features...........................................................................................................................................................................................4

New Symbols and Connections........................................................................................ 4 Rear Panel.......................................................................................................................................................................................4

Software Controls.............................................................................................................. 5 Status Area .....................................................................................................................................................................................5

Getting Started .................................................................................................................. 5 Service Mode..................................................................................................................................................................................5 Using service mode: ......................................................................................................................................................................6 Basic Use ........................................................................................................................................................................................7 Log data on Monitor.....................................................................................................................................................................7 Log data on USB memory stick ..................................................................................................................................................7

Subsequent processing of log data.................................................................................... 9 Interpreted Log Files (*.txt) .........................................................................................................................................................9 Comma Separated Log Files (*.csv)..........................................................................................................................................10 Amplitude Data ...........................................................................................................................................................................11 MEP Data ....................................................................................................................................................................................15 Explaining the reference numbering system ...........................................................................................................................19

Advanced User section ................................................................................................... 20 Event log format .........................................................................................................................................................................20 Log Event Design – Header and Data.....................................................................................................................................21 Event: Train start ........................................................................................................................................................................22 Event: Train Start – Pulse mode – Revision 2 ........................................................................................................................24 Event: Train Start – Continuous mode (only R100) ..............................................................................................................26 Event: Train Start – Train mode (only R100) .........................................................................................................................28 Event: Train Start – Sweep Mode (only R100) .......................................................................................................................30 Event: Train Start – Traverse Mode (only R100) ...................................................................................................................32 Event: Manual Stimuli revision 2 ..............................................................................................................................................34 Event: Protocol Start ..................................................................................................................................................................36 Event: Protocol Stopped............................................................................................................................................................37 Event: Protocol Delay ................................................................................................................................................................38 Event: Protocol Line Start .........................................................................................................................................................39 Event: Protocol Amplitude Adjust ...........................................................................................................................................41 Event: Train Stop ........................................................................................................................................................................42 Event: Coil Temperature............................................................................................................................................................43 Event: Coil Type .........................................................................................................................................................................44 Event: Model identification .......................................................................................................................................................45 Event: Date ..................................................................................................................................................................................46 Event: System Status...................................................................................................................................................................47 Event: New Session ....................................................................................................................................................................48 Event: MEP Data Recording.....................................................................................................................................................49 Event: Amplitude Curve Recording .........................................................................................................................................50 Appendix 1: Amplitude Curve Data .........................................................................................................................................51 Appendix 2: MEP Data ..............................................................................................................................................................52 Appendix 3: Coil Type (See Also Accessories Catalogue) .....................................................................................................55


4 Introduction

Introduction The purpose of the MagPro G3 Data Transfer is to give the user the possibility to extract data for documentation purposes.

Features The MagPro G3 Data Transfer gives the possi-bility to extract data for documentation to an USB memory stick. The Event log contains de-tails as:

when did a train start how many stimuli did it produce and at which amplitude did the train run

This makes the user able to manually repeat the same train sequence. For documentation the following is available:

Event log MEP log (if MEP monitor available) Amplitude log

The MEP log contains all necessary data to re-construct the recorded MEP curve and the Amplitude log contains data to reconstruct the Amplitude curves of the stimuli. All logs (Event log, Amplitude log and MEP log) are generated in a comma separated format for further data treatment in e.g. a spreadsheet. The Event log is also available in an interpreted text format for direct print out. The upper right corner of the Status Area (see Software Controls) displays the USB memory stick status (an icon), the latest 3 events and the Date and Time. All the displayed information is easily readable. It is, through the service Mode (see later), pos-sible to choose between:

- which of the above logs is to be written to the USB memory stick

- set the Time and Date - choose the Language

- choose whether the MagPro should start up in service mode or not at next startup.

The MagPro G3 Data Transfer also gives the possibility to update the software on the Mag-netic Stimulator (see separate manual for this).

New Symbols and Con-nections

Rear Panel

1 USB port 1 (to be used) 2 USB port 2 (for future use)

This upgrade introduces 2 new USB ports. Port 1 is the port that has to be used for data trans-fer. Port 2 is not connected and will not be opera-tional (is for future use)

This symbol signifies the USB con-nections.

WARNING Only connect USB memory sticks to the USB ports as showed in the manual. Do not connect anything to USB port 2.


Software Controls 5

Software Controls

The general user interface in MagPro G3 is logical and well organized, enabling the opera-tor to overview all functions. The new feature in the general user interface is located in the status area.

Status Area The Status Area at the upper right corner now also shows:

- Availability of USB memory stick - Log data (newest data on the bottom line) - Time and date

Getting Started

Service Mode In Service Mode it is possible to adjust: • The language. • Which data is to be logged. • The Date and Time • Whether the MagPro should start up in ser-

vice mode or not at next startup.

The first time the MagPro will start up in the Service Mode automatically.

To exit Service Mode just activate the soft but-ton Exit in the lower left corner. How to activate the service menu differs be-tween MagPro R100 and the rest of the MagPro family. MagPro family: (R30, X100, R30+Option and X100+Option) The service mode will always be available in the soft button menu at the bottom of the user in-terface – activate the configure button and then activate the service button – and the service menu will appear. R100 only: The setup mode becomes available in the R100 by holding the footswitch down while doing start up.


6 Getting Started

Using service mode:

Language Select the language of the MagPro.

Important note: A restart of the MagPro is necessary, when a new language is chosen. Event Log It is possible to decide if the Event Log (that is both the text file (txt) and the comma separated file (csv)) should be saved on the USB memory stick. If event data logging is needed the Event Log Enabled should be ON. If Amplitude logging and/or Coil Temperature logging is also wanted please set them ON as well. Amplitude Log Enabled Decide if the Amplitude Log (comma separated file) should be saved on the USB memory stick. Coil Temperature events Choose if the Coil Temperature events should be logged in the Event Log and saved on the USB memory stick. Three different choices in Coil Temperature are available: • OFF – no coil Temperatures events are

logged and saved • ON - Coil temperature events are only

logged when the MagPro are active and run-ning a sequence of stimulations

• Advanced – all Coil temperature events are logged; also the temperature events between stimulations (be aware that the MagPro will save to memory stick when logging and an error will occur if the memory stick is re-moved when the MagPro is writing data to it)

Start with Service Mode active The decision whether the MagPro should start up in service mode can be made here. Date and Time Highlight the field that is to be changed and use the right wheel to adjust. Exit Press Exit to leave service mode and enter the user menu of the MagPro:


Getting Started 7

Basic Use Log status on Monitor

Insert an USB memory stick (formatted with the FAT16 file formatting system and maxi-mum 2 GB) in USB port 1 on the rear panel of the MagPro. WARNING The USB memory stick must maximum be of size 2 GB. It must be formatted with the FAT16 file allo-cation system.

If there is no USB memory stick inserted or the USB memory stick inserted is incompatible a gray disk symbol (icon) will be shown on the display:

USB memory stick not available or incompati-

ble

When no USB memory stick is inserted in USB Port 1.

If the USB memory stick is formatted correct; have the correct size and enough available memory (more than 5MB), the following icon will appear in the upper right corner of the monitor:

USB memory stick

available

When a USB memory stick is inserted in USB Port 1.

Files are being written to USB memory stick

When the MagPro are writing data to the USB memory stick, this icon will be visible (flashing).

Error on USB mem-

ory stick

If an error occurs when writing to the USB memory stick a

will appear.

Insufficient USB

memory stick space

If USB memory stick space gets lower than 5MB, a will appear.

WARNING When the MagPro is Writing data to the disk, the disk must not be removed. If the USB memory stick is removed when writing an error message can appear on the MagPro display. A restart of the MagPro is then necessary.

Log data on Monitor Oldest

data ↑

Newest data

All events chosen in the Service Mode are logged and saved on the USB memory stick when inserted. The latest three events will also be displayed in a shorter format on the monitor with the newest event pushed in at the bottom line.

Log data on USB memory stick Event log data is saved as a raw data file (comma separated file) and an interpreted file for directly printout (text file). If chosen in the Service Mode an Amplitude Log and a MEP log (only if a MEP monitor is available) will be available on the USB memory stick. The files are organized on the USB mem-ory stick as follows:


8 Getting Started

The name of the root folder holding the Log files is build upon the type and the Serial Num-ber (S/N) of the MagPro. The picture above is a X100 + Option with Serial Number 777. In this folder another two folders will be cre-ated (if MEP and/or Amplitude log is chosen in the Service Menu): • In the “MEP Data” folder the MEP data is

saved as a raw data file (comma separated file) - only if a MEP monitor is available

• In the “Amplitude Data” folder the ampli-

tude data is saved as a raw data file (comma separated file)

Log event data At the directory root the Log event data are saved as a raw comma separated file (csv) and an interpreted text file (txt) (here the files X100+Option SN777.csv and X100+Option SN777.txt). Log MEP data When the MEP curve is created on the MagPro monitor just move the cursor to “save” and turn the right side wheel.

When turning the right side wheel, the file will be saved under the name specified in the field below (in the example below it is “MEP Data 1-2.csv”) and placed in the folder “MEP data”. Log Amplitude data The amplitude data are automatically saved in the “Amplitude data” folder. For further information about the above de-scribed, please see the chapter “subsequent processing of log data”.


Subsequent processing of log data 9

Subsequent processing of log data This chapter is explaining the different features of the data export part that is present in the Mag-Pro G3 Data Transfer package.

Interpreted Log Files (*.txt) The Interpreted Log File is the MagPro interpretation of the Comma Separated Files lined up to be easily readable in an text editor and ready for a print out. The relationship between the Interpreted Log Files and the Comma Separated Log Files can be seen in the Advanced User Section where short examples are given. Example from X100 with Option (See next chapter for the matching comma separated files):

Example from R100 (See next chapter for the matching comma separated files):


10 Subsequent processing of log data

Comma Separated Log Files (*.csv) The Comma Separated Log Files is meant to be used by technicians and developers to create their own report interface. As it is a comma separated file, it is possible to extract information into spreadsheets and databases for further data processing. In the Advanced User Section Event Log Format it is described how to extract exactly those in-formation’s that is needed for a custom made Log Report.

Example from X100 with Option:

Example from R100:



Amplitude Data The Comma Separated Amplitude Data gives the user a possibility to see di/dt values during the train(s). It is saved as a Comma Separated File to make it easy to import data into a spreadsheet application to make a graph for visually data inspection and documentation. For advanced informa-tion on the structure of the comma separated Amplitude Data please refer to Appendix 1. Below is explained how to import data into a spreadsheet application to make a graph for visually data inspection and documentation. If chosen in the Service Mode an Amplitude Log will be available on the USB memory stick in the folder named “Amplitude Data”. In this folder all recorded Amplitude Data can be found with a reference number.

Here a new and formatted USB memory stick was inserted and a new Session ID = 11 was created and logged.

Example from MagPro R100.

To find the needed Amplitude Data look in the Interpreted Log File. In the example to the left an event with two trains in Con-tinuous Mode have been re-corded (Entry=9). The event with Entry=10 the Amplitude Data has been re-corded and given a reference number (11-9) which means that this Amplitude recording belongs to the event with Ses-sion ID 11 and Entry 9). The event with Entry=11 tells that the train has stopped and gives these information’s - The train completed over a period of 5,9 seconds and gave 59 pulses.

COMMENT The reference number in the Amplitude File (Entry 10 – Record Ampl. (11-9) ) is made up of the Session ID and the Entry ID given to the event that caused the Amplitude File. In the above example the Session ID was 11 – find this number in the start of the log file. The event that caused the Amplitude File (with Entry ID = 10) had the Entry ID = 9. A more thorough explanation of this reference numbering system is given under the chapter “Ex-plaining the reference numbering system”.



How to extract data from the amplitude data file and visualize it in a spreadsheet Use the reference number (in the above case 11-9) to find the needed amplitude data under the folder “Amplitude Data”.

Here Entry ID 28, 29 and 30 caused Amplitude Data. All these events were generated under the Session ID number 34.

To create a graph constructed upon the data open the file in a spreadsheet application. Here it is explained with the use of Excel (Microsoft): Step 1

Open the file - here it is “Ampl Data (34-28).csv” - in a spreadsheet program (here Excel). Data in the file is build up with up to 4 or 5 columns:

• Column A is the train number • Column B tells whether it is only A (1) or both

A&B (2) (i.e. twin/dual/biburst mode or not) • Column C is the time in [ms] • Column D is the amplitude (di/dt) for A [A/μs] • Column E is the amplitude (di/dt) for B [A/μs] –

(not existing in this example) Be aware that the timestamp of pulse A and pulse B in this log are the same. In reality pulse A and pulse B are separated in time by the Inter Pulse Interval (IPI).

Highlight the data in C and D (or C+D+E, if data in column E) rightmost rows – the Time data and the Am-plitude data. For advanced information on the structure of the comma separated Amplitude Data please refer to Ap-pendix 1.



Step 2

Press the button or choose Insert, Chart… in the menu and a wizard will appear.

Step 3 Choose XY (Scatter) and a curve sub-type and press finish.

The Amplitude Curve will be drawn and can be used for print out.



Step 4 If needed, the X and Y Axis of the Amplitude Curve can have units: The X-axis are in [ms] The Y-axis are in [A/μs] To write the units on the curve drawings; right click in the chart area and choose Chart Options.

Step 5 Here a Chart title, Value (X) axis and Value (Y) axis can be defined if needed.

This gives the final curve drawing:



MEP Data The Comma Separated MEP Data gives the user a possibility to export the MEP data. It is saved as a Comma Separated File to make it easy to import data into a spreadsheet application to make a graph for visually data inspection and documentation. For advanced information on the structure of the comma separated MEP Data please refer to Appendix 2. If chosen in the Service Mode a MEP data Log will be available on the USB memory stick in the folder named “MEP Data” (see the chapter “Basic use”). In this folder all recorded MEP Data can be found with a reference number.

To find the needed File look in the Inter-preted Log File. In the example to the left a manual stimuli has been fired (Entry ID = 13). The next event (Entry ID = 14) the MEP Data was recorded (the user has turned the knob when the cursor was over the field “Save” in the MEP Menu) and given a ref-erence number: 12-1.

COMMENT The reference number from the MEP File is numbered consecutively from when the Session ID was created – i.e when a newly formatted USB memory stick was inserted. A more thorough ex-planation of this reference numbering system is given under the chapter “Explaining the reference numbering system”. How to extract data from the MEP data file and visualize it in a spreadsheet

Use the reference number – here 12-1 - from the Interpreted Log File to find the needed MEP data under the folder “MEP Data”.

To create a graph constructed upon the data; open the file - here “MEP Data 12-1.csv” - in a spreadsheet application. Here it is explained with the use of Excel (Microsoft):



Step 1

Open the file - here it is “MEP Data 12-1.csv” - in a spreadsheet program (here Ex-cel).The first 22 rows are the settings. The first set (row 1-5) is the general informa-tion from the stimulator. The second set of data (row 7-14) is the set-tings from the MEP monitor. The third set of data (row 16-22) is informa-tion about the data. Curve data (from row 23) in the file is build up in 2-11 columns:

• Column 1 is the time in [μs] • Column 2 is the EMG Curve Ampli-

tude in [μV] for Curve no. 1 • Column 3-11 is the EMG Curve Ampli-

tude in [μV] for Curve no. 2-10 Now highlight the data in the two (or more) rows – the Time data and the MEP Amplitude data for the one (or more) curve(s). For advanced information on the structure of the comma separated MEP Data; please refer to Appendix 2.

Step 2 Press the button or choose Insert, Chart… in the menu and a wizard will appear.



Step 3 Choose XY (Scatter) and a curve sub-type and press finish.

The MEP Curve will be drawn from the highlighted data and can be used for print out. The X-axis is in [μs]. The Y-axis is in [μV].



Step 4 If needed, the X and Y Axis of the MEP Curve can have units: The X-axis in [μs] The Y-axis in [μV] To write the units on the curve drawing ⇒ right click in the chart area and choose Chart Options.

Step 5 Here a Chart title, Value (X) axis and Value (Y) axis can be defined if needed.

This gives the final curve drawing:



Explaining the reference numbering system To be able to reference to an event uniquely a reference numbering system is developed. The refer-ence numbering system for the log event is made of two separate index keys - the Session ID and the Entry ID. Every log event has these two index keys to give a database programmer the option to choose between which schemes to use for storing log events:

Broadly spoken the above means: When a blank/empty USB memory stick is inserted, the MagPro generates a new Session ID. Added to that number every event is given an Entry ID when written to the USB memory stick. A special case to the Entry ID is MEP and Amplitude Data recording: These entries are given their own folders (“MEP data” and “Amplitude Data”) and filenames (MEP Data xx-No and Ampli-tude Data (xx-yy) ).

Session ID: • Consecutive numbering when a new

formatted memory stick is inserted [1,2,3…]

• Are incremented when the data on the memory stick is erased or formatted.

• Are only reset at factory. • For database use.

Entry ID: • Consecutive numbering at each new

entry [1,2,3…] • Are reset when the data on the mem-

ory stick is erased or formatted – i.e. a new Session starts.

• Entries are events in the system such as train start/stop

• Amplitude data recording and MEP data recording are also events that create Entries.

Special Cases of Entry ID: Amplitude Data Recording:

• Have their own folder and files • The file name is constructed of:

Amplitude Data (xx-yy) where xx is the session ID and yy is the Entry ID for the event associated with this Amplitude Data Recording.

MEP Data Recording: • Have their own folder and files • The file name is constructed of:

MEP Data xx-No where xx is the session ID and No is consecutive numbered from start of session [1,2,3…]

• A reference to the associated events can be found inside the file.

The Session ID and the Entry ID works as a pair.



Advanced User section This section is aimed at users who want to design their own log report interface. In this section all the event formatting is described

Event log format All events relative to the use of the stimulator are logged as comma separated values (csv). These events are saved on the USB memory stick in folders named after its use and the events have the following properties:

• The events are stored in a csv file. Data entries are separated by a ; sign. • Each event has its own line in the csv file. • Each event has a common header with an identical layout for all the events. • The events can have different amount of data attached to them and thus are of different

length. • The individual events can have a dynamic length depending on the attached data. • The events are build up by encapsulating the data finer and finer details. • The key to unwrapping the encapsulating is always a unique id with a single well-defined

meaning and a corresponding length entry. • For the “header” layer the encapsulation is done by the Entry ID and the event data length.

Encapsulating data

Header (Layout type, Session ID, Entry ID, …)

Event Dependent Data

Sub Event Dependent Data



Log Event Design – Header and Data The header is common for all log entries. The shortest valid log event entry record contains 10 cells. A cell is an integer value separated from the other cells by a; sign. The number of digits in the individual cells can be no bigger then the value represented by a signed 4 byte integer. But in many cases it can be represented by less. Cell Offset Data Cell Values Assumed

1 Layout type The Layout type identifier is a number telling which for-mat the following entries have. (this version is layout type = 0)

2 Session ID The session id is incremented each time the system creates a new file on the external media (when the external media is formatted or erased). The session id is unique from the date of birth of the system.

3 Entry ID The Entry ID is a unique identifier added to each event log entry. Resetting to 1 for the first log event stored in a new Session.

4 Year The year the event occurred 5 Month The month the event occurred 6 Date The date the event occurred 7 Hour The hour the event occurred 8 Minute The minute the event occurred 9 Second The second the event occurred 10 Event type id The event type id is an unique identifier for the event

1 = Train start 2 = Train stop 3 = Manual Stimuli 4 = Coil temperature 5 = amplitude curve recording 6 = amplitude curve recording continuous 7 = coil type 8 = Model Identification 9 = MEP Curve Recording 10 = Date 11 = System Status 12 = new session 13 = Protocol start 14 = Protocol Stop 15 = protocol delay 16 = protocol line 17 = protocol amplitude adjusted manual 18 = train start rev 2 19 = Manual stimuli rev 2

11 Event data length The event data length field contains the number of event data

12 Event data+0 Event data is depending on the event type id. The number of event data is stored in the event data length.

13 Event data+1 .. 14 Event data+2 .. … Event data+… .. … Event data+N-1 ..



Event: Train start The log event “Train Start” is logged each time the user starts a train. The “Train Start” event has dynamic length depending on the Mode Type and Wave Form.

Cell Offset

Data Cell Values Assumed

… … … 10 Event type id 1 = Train Start

Header

11 Event data length The length of the train start command is de-pending on which mode it was started in. The following data fields are mandatory in the for-mat.

• Coil type identification • Mode • Current Direction • Wave form • Sequence Mode

So the length field will always be at least 5.

12 Coil type id The coil type id is a unique identifier of the coil type.

13 ModeType 0 = Unknown 1 = Continuous (only R100) 2 = Pulse (all MagPro Family) 3 = Train (only R100) 4 = Sweep (only R100) 5 = Traverse (only R100)

14 Mode Data Length Length of the data attached to the Mode Type. 15 Mode 0 = Standard (all MagPro Family)

1 = Power (only X100 w. Option) 2 = Twin (only R30 w. Option, X100 w. option) 3 = Dual (only R30 w. Option, X100 w. option)

16 Current direction 0 = Normal 1 = Reversed (only X100, X100 w. option)

Fixed Data

17 Wave form 0 = Half sine (only X100 w. Option) 1 = Biphasic (all MagPro Family) 2 = Monophasic (only X100, R30 w. Option and X100 w. option) 3 = Biphasic Burst (only X100, X100 w. option)

(18) inter pulse interval Only If mode = Twin

Inter pulse interval in [μs]. Mode extra

(19) B/A Ratio Only If mode = Twin

B/A ratio are the difference in amplitude be-tween the first and the last pulse times 10. Value = 10*B/A Ratio.

(18 or 20)

Inter pulse interval Only If Wave form = Bi-phasic burst.

Inter pulse interval in [μs]. Wave form extra

(19 or 21)

Number of pulses Only If Wave form = Bi-

The number of pulses in the burst [2,3,4,5]



phasic Burst. (18, 20 or 22)

Mode data+0 …

(19, 21 or 23)

Mode data+1 …

… Mode data+2 … … Mode data+3 …

Dynamic data

… Mode data+N-1 …



Event: Train Start – Pulse mode – Revision 2 Cell Offset Data Cell Values Assumed

… … … 10 Event type id 18 = Train Start (revision 2)

Header

11 Event data length 12-14 *depending on Mode and Wave Form settings

12 ModeType 2 = Pulse Mode 13 Mode data length 10-12 14 Coil type id The coil type id is a unique identifier of

the coil type. 15 Mode 0 = Standard (all MagPro Family)

1 = Power (only X100 w. Option) 2 = Twin (only R30 w. Option, X100 w. option) (3=Dual) (only R30 w. Option, X100 w. option)

16 Current direction 0 = Normal 1 = Reversed (only X100, X100 w. op-tion)

Fixed Data


(18) inter pulse interval

Only If Mode = Dual inter pulse interval in [μs]. Mode

extra Dual (19) B Amplitude (%)

Only If Mode = Dual 1-100 (1=1%)

(18) inter pulse interval Only If Mode = Twin

inter pulse interval in [μs]. Mode extra Twin (19) B/A Ratio

Only If Mode = Twin B/A ratio are the difference in ampli-tude between the first and the last pulse times 10. Value = 10*B/A Ratio.

(18) Inter pulse interval Only If Wave form = Bi-phasic burst.

Inter pulse interval in [μs]. Wave form extra (19) Number of pulses

Only If Wave form = Bi-phasic Burst.


[18, 20 or 22] Amplitude (%) 1-100 (1=1%) [19, 21 or 23] Repetition Rate 1-100000 (1=mHz) [20, 22 or 24] Pulses per seq. 1-1000 (steps = 1) [21, 23 or 25] Number of Trains 1-500 (steps = 1) [22, 24 or 26] Inter train interval 1-120 (seconds)

Fixed data for train start Pulse mode [23, 25 or 27] Estimated Time 0 – n (ms)



Csv Log file entry example: 0; 190; 9; 2007; 12; 14; 10; 44; 51; 18; 12; 2; 10; 82; 0; 0; 1;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Mod

eTyp

e

Mod

e da

ta L

engt

h

Coil

Type

Id

Mod

e

Curr

ent D

irect

ion

Wav

e Fo

rm

17; 10000; 31; 1; 0; 3000,

Am

plitu

de

Repe

titio

n Ra

te

Pulse

s per

seq.

Num

ber o

f seq

.

Inte

r tra

in in

terv

al

Est

imat

ed tI

me

Txt Log file entry example: 10:44:51 - Entry 9 - Started in Pulse Mode - Coil Type is MC-B70 - Mode set to Standard - Current Direction set to Normal - Wave Form set to Biphasic - Amplitude set to 17% - Repetition Rate set to 10Hz - Number of Pulses in train 31 - Number of Trains set to 1 - Inter Train Interval set to 0.0s - Estimated Time 3s



Event: Train Start – Continuous mode (only R100) The log event “Train start – Continuous” is logged each time the user starts a train in continuous mode. Cell

Offset Data Cell Values Assumed

… … … 10 Event type id 1= Train start

Header

11 Event data length 8-10-12 * depending on Mode and Wave Form settings

12 ModeType 1 = Continuous 13 Mode data length 2 14 Coil type id The coil type id is a unique identifier of the coil

type (for values - see later) 15 Mode 0 = Standard 16 Current direction 0 = Normal

Fixed Data

17 Wave form 1 = Biphasic

18 Amplitude (%) 1-100 (1=1%) Fixed data for Train start Continu-ous Mode

19 Repetition Rate 1-100 (1=Hz)

Csv Log file entry example: 0; 34; 11; 2007; 6; 20; 13; 20; 5; 1; 8;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

1; 2; 82; 0; 0; 1; 16; 10;

Mod

eTyp

e

Mod

e da

ta L

engt

h

Coil

Type

Id

Mod

e

Curr

ent D

irect

ion

Wav

e Fo

rm

Am

plitu

de

Repe

titio

n Ra

te



Txt Log file example: 13:20:05 – Entry 11 - Started in continuous - Coil Type is MC-B70 - Mode set to standard - Current direction set to normal - Wave form set to biphasic - Amplitude set to 16% - Repetition rate set to 10Hz



Event: Train Start – Train mode (only R100) Cell Offset Data Cell Values Assumed


Header

11 Event data length 14-16-18 *depending on Mode and Wave Form settings

12 ModeType 3 = Train Mode 13 Mode data length 8 14 Coil type id The coil type id is a unique identi-

fier of the coil type. 15 Mode 0 = Standard

Fixed Data

16 Current direction 0 = Normal 17 Wave form 1 = Biphasic (all MagPro Family)

18 Amplitude (%) 1-100 (1=1%) 19 Repetition Rate 1-100 (1=Hz) 20 Duration 0.0-10.0 (seconds) 21 Ramp up duration 0-10000 (ms) in steps of 100ms 22 Ramp down duration 0-10000 (ms) in steps of 100ms 23 Number of Trains 1-500 24 Inter train interval 1-120 (seconds)

Fixed data for Train start – Train mode

25 Estimated time 0 – n (ms)


Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

3; 8; 82; 0; 0; 1; 11; 11; 13; 1300; 1500; 2; 3; 3000;

Mod

eTyp

e

Mod

e da

ta L

engt

h

Coil

Type

Id

Mod

e

Curr

ent D

irect

ion

Wav

e Fo

rm

Am

plitu

de

Repe

titio

n Ra

te

Dur

atio

n

Ram

p up

dur

atio

n

Ram

p D

own

dura

tion

Num

ber o

f Tra

ins

Inte

r tra

in in

terv

al

Est

imat

ed ti

me



Txt Log file example: 13:22:42 - Entry 17 - Train Started in train mode - Coil Type is MC-B70 - Mode set to standard - Current direction set to normal - Wave form set to biphasic - Amplitude set to 11% - Repetition Rate set to 11Hz - Duration set to 13s - Ramp up time set to 1.3s - Ramp down time set to 1.5s - Number of Trains set to 2 - Inter train interval set to 3 - Estimated Time 30.0s



Event: Train Start – Sweep Mode (only R100) Cell Offset Data Cell Values Assumed


Header


12 ModeType 4 = Sweep Mode 13 Mode data length 7 14 Coil type id The coil type id is a unique identi-

fier of the coil type. 15 Mode 0 = Standard

Fixed Data

16 Current direction 0 = Normal 17 Wave form 1 = Biphasic (all MagPro Family)

18 Amplitude (%) 1-100 (1=1%) 19 Lower Repetition Rate 1-100 (1=Hz) 20 Upper Repetition Rate 1-100 (1=Hz) 21 Duration [1-120.0] (seconds) 22 Ramp up duration 0-10000 (ms) in steps of 100ms 23 Ramp down duration 0-10000 (ms) in steps of 100ms 24 Number of Trains 1-500 25 Inter train interval 1-120 (seconds)

Fixed data for train Start – Sweep mode

26 Estimated time 0 – n (ms) Csv Log file entry example: 0; 34; 34; 2007; 6; 20; 13; 56; 40; 1; 15;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

4; 9; 82; 0; 0; 1; 18; 1; 26; 10; 8900; 9100; 3; 1; 32000;

Mod

eTyp

e

Mod

e da

ta L

engt

h

Coil

Type

Id

Mod

e

Curr

ent D

irect

ion

Wav

e Fo

rm

Am

plitu

de

Low

er R

epet

ition

Rat

e

Upp

er R

epet

ition

Rat

e

Dur

atio

n

Ram

p up

dur

atio

n

Ram

p do

wn

Dur

atio

n

Num

ber o

f Tra

ins

Inte

r tra

in in

terv

al

Est

imat

ed ti

me



Txt Log file example: 13:56:40 - Entry 34 - Train Started in Sweep mode - Coil Type is MC-B70 - Mode set to standard - Current direction set to normal - Wave form set to biphasic - Amplitude set to 18% - Lower Repetition Rate set to 1Hz - Upper Repetition Rate set to 26Hz - Duration set to 10s - Ramp up time set to 8.9s - Ramp down time set to 9.1s - Number of Trains set to 3 - Inter train interval set to 1 - Estimated time 32.0s



Event: Train Start – Traverse Mode (only R100) Cell Offset Data Cell Values Assumed


Header


12 ModeType 5 = Traverse Mode 13 Mode data length 6 14 Coil type id The coil type is the unique identifier of

the coil type. 15 Mode 0 = Standard (all MagPro Family) 16 Current direction 0 = Normal

Fixed Data

17 Wave form 1 = Biphasic (all MagPro Family)

18 Amplitude (%) 1-100 (1=1%) 19 Repetition Rate 1-100 (1=Hz) 20 Traverse length [1,5,10,15-100] (cm) 21 Number of Trains 1-500 22 Inter train interval 1-120 (seconds)

Fixed data for train start: Traverse Mode 23 Elapsed Time 0 – n (ms) Txt Log file entry example: 0; 34; 37; 2007; 6; 20; 13; 58; 1; 1; 12;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

5; 6; 82; 0; 0; 1; 9; 10; 15; 2; 1; 31000;

Mod

eTyp

e

Mod

e da

ta L

engt

h

Coil

Type

Id

Mod

e

Curr

ent D

irect

ion

Wav

e Fo

rm

Am

plitu

de

Repe

titio

n Ra

te

Trav

erse

Len

gth

Num

ber o

f Tra

ins

Inte

r tra

in in

terv

al

Est

imat

ed ti

me



Txt Log file example: 13:58:01 - Entry 37 - Train Started in Traverse mode - Coil Type is MC-B70 - Mode set to standard - Current direction set to normal - Wave form set to biphasic - Amplitude set to 9% - Repetition Rate set to 10Hz - Traverse length set to 15cm - Number of Trains set to 2 - Inter train interval set to 1 - Estimated Time 31.0s



Event: Manual Stimuli revision 2 This event stores the information of manual fired stimuli. Its records the amplitude setting and the number of event fired within the last “sample” period (ie. 1 second) Cell offset Data Cell Values Assumed

10 Event type id 3 = Manual stimuli (rev. 2) Header 11 Event data length 7-11 (depending on Mode and Wave

Form settings)

12 Coil type id The coil type is the unique identifier of the coil type.

13 Stimulation count [1-X] 14 Mode 0 = Standard (all MagPro Family)

1 = Power (only X100 w. Option) 2 = Twin (only R30 w. Option, X100 w. option)* 3=Dual (only R30 w. Option, X100 w. option)*

15 Current direction 0 = Normal 1 = Reversed (only X100, X100 w. option)

16 Wave form 0 = Half sine (only X100 w. Option) 1 = Biphasic (all MagPro Family) 2 = Monophasic (only X100, R30 w. Option and X100 w. option) 3 = Biphasic Burst (only X100, X100 w. option)*

17 Pulse A Amplitude (%) 0-100 in 1% increments.

Fixed Data

18 Pulse A di/dt [A/μs]

(19) Pulse B Amplitude (%) 0-100 in 1% increments. (20) inter pulse interval

Only If mode = Dual inter pulse interval in [μs].

Extra if Mode=Dual

(21) Pulse B di/dt [A/μs] (19) B/A Ratio

Only If mode = Twin B/A ratio are the difference in ampli-tude between the first and the second pulse in the train. [%] Value=10*B/A ratio.

(20 ) Inter pulse interval Only If Wave form = Twin

Inter pulse interval in [μs].

Extra if Mode=Twin

(21) Pulse B di/dt [A/μs] (19) Number of pulses

Only If Wave form = Bi-phasic Burst.


(20 ) Inter pulse interval Only If Wave form = Bi-phasic Burst

Inter pulse interval in [μs].

Extra if Mode=Biphasic burst

(21) Pulse B di/dt (last pulse) [A/μs] * The device cannot be in Mode = Twin and Wave Form = Biphasic burst at the same time. The two settings are multiple exclusive.



Txt Log file entry example:

0; 190; 87; 2007; 12; 17; 14; 33; 28; 19; 7; 82; 1; 0; 0; 1; 13; 17;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Coil

Type

Id

Stim

ulat

ion

Coun

t

Mod

e

Curr

ent D

irect

ion

Wav

e Fo

rm

Am

plitu

de

Di/

dt (

a/us

)

Txt Log file example: 14:33:28 - Entry 87 - Manual Stimuli - Coil Type is MC-B70 - Stimuli Count 1 - Mode set to Standard - Current Direction set to Normal - Wave Form set to Biphasic - Amplitude set to 13 (%) - di/dt 17(A/us) Txt Log file entry example:

0;

190;

87;

2007

;

12;

17;

14;

36;

58;

19;

10;

82;

1;

2;

0;

1;

20;

28;

1000

0;

15;

44;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Coil

Type

Id

Stim

ulat

ion

Coun

t

Mod

e

Curr

ent D

irect

ion

Wav

e Fo

rm

Am

plitu

de A

A D

i/dt

Inte

r pul

se in

terv

al

B/A

ratio

B di

/dt

Txt Log file example: 14:36:58 - Entry 90 - Manual Stimuli - Coil Type is MC-B70 - Stimuli Count 1 - Mode set to Twin - Current Direction set to Normal - Wave Form set to Biphasic - Amplitude A set to 20 (%) - Pulse A di/dt 28(A/us) - B/A ratio set to 1.5 - Inter Pulse Interval set to 10.0ms - Pulse B di/dt 44(A/us)



Event: Protocol Start The system adds a log event then it starts a protocol. Cell offset Data type Comment

10 Event type id 13 = Protocol Start

Header

11 Event data length 4 Line count 12 1-n Number of lines in the protocol.

Each line holds a delay and a train setup.

Total estimated time

13 0-n seconds Total estimated time for the whole protocol.

Amplitude 14 0-100% The Main Amplitude dial position. Coil Type 15 Coil Type id See the coil Type Id appendix Csv Log file entry example: 0; 190; 114; 2007; 12; 17; 15; 16; 55; 13; 4; 3; 24; 20; 82;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Line

cou

nt

Tota

l est

imat

ed

time

Am

pltiu

de

Coil

type

Txt Log file entry example: 15:16:55 - Entry 114 - Protocol started - Number of Lines 3 - Total Estimated Time 24s - Set Amplitude 20% - Coil Type is MC-B70



Event: Protocol Stopped The system adds a log event then the protocol stops. Cell offset Data type Comment

10 Event type id 14 = Protocol Stopped.

Header

11 Event data length 3 12 Completion status 0 = success (the train ran to its end)

1 = user break ( the user stopped the train) 2 = disabled ( the machine stopped the train) 3 = overheating (The coil tempera-ture extended the maximum allowed value) 4 = overheating (The intelligent thermal protection algorithm disabled the device to protect the coil from rapid overheating)

13 Total elapsed time Total elapsed time in milliseconds 14 Lines remaining Number of protocol lines remaining

to be executed at the time of comple-tion. This will only be different from zero if the completion status is differ-ent from success.

Csv Log file entry example: 0; 190; 123; 2007; 12; 17; 15; 17; 22; 14; 3; 0; 23500; 0;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Com

plet

ion

stat

us

Tota

l elap

sed

time

Line

s rem

ainin

g

Txt Log file entry example: 15:17:22 - Entry 123 - Protocol stopped - Completion status - Successful - Elapsed Time 24s - Lines remaining 0



Event: Protocol Delay The system adds a log event then a delay in the protocol is started. Please notice the delay between trains is listed an part of a line in the protocol. Cell offset Data type Comment

10 Event type id 15 = Protocol Delay

Header

11 Event data length 1 12 Protocol delay The delay between trains in millisec-

onds. Csv Log file entry example: 0; 190; 120; 2007; 12; 17; 15; 17; 8; 15; 1; 10000;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Prot

ocol

dela

y

Txt Log file entry example: 15:17:08 - Entry 120 – Delay 10s



Event: Protocol Line Start Cell offset Data type Comment

… … … 10 Event type id 16 = Protocol Line start

Header

11 Event data length 12-14 *depending on Mode and Wave Form set-tings

12 ModeType 2 = Pulse Mode (only valid) 13 Mode data length 10-12 14 Coil type id The coil type id is a unique identifier of the coil

type. 15 Line number 1-n The current executed protocol line. 16 Estimated time 0-n seconds. The Estimated time for the line to

execute. 17 Amplitude A 0-100% - The amplitude of the Main dial. 18 Amplitude gain The amplitude gain factor. 19 Repetition rate The repletion rate in mHz 20 Pulses in train 1 – 1000 – Number of pulses in the train. 21 Current direction 0 = Normal

1 = Reversed (only X100, X100 w. option) 22 Mode 0 = Standard (all MagPro Family)

1 = Power (only X100 w. Option) 2 = Twin (only R30 w. Option, X100 w. option) 3 = Dual (only R30 w. Option, X100 w. option)

Fixed Data


(24) Inter pulse interval In micro seconds Mode = Twin (25) B/A ratio Twin Mode B/A ratio in 1/10 of fraction.

I.e. to get the factor divide by 10. (24) inter pulse interval

Inter pulse interval in μs. Biphasic

burst (25) Number of pulses





Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

2; 10; 82; 3; 1000; 30; 15; 12000; 12; 0; 0; 1;

Mod

eTyp

e

Mod

e da

ta L

engt

h

Coil

Type

Id

Line

num

ber

Est

imat

ed ti

me

Am

plitu

de A

Am

plitu

de g

ain

Repe

titio

n ra

te

Pulse

in tr

ain

Curr

ent d

irect

ion

Wav

e m

ode

Wav

e fo

rm

Txt Log file entry example: 15:17:18 - Entry 121 - Protocol Line (3) - Amplitude set to 30% - Amplitude gain 1.5 - Estimated Time <1s - Repetition Rate set to 12Hz - Pulses in Train set to 12 - Current Direction set to Normal - Mode set to Standard - Wave Form set to Biphasic



Event: Protocol Amplitude Adjust Cell off-

set Data Cell Values Assumed

… … … 10 Event type id 17 = Protocol Amplitude Adjust

Header

11 Event data length 1 Fixed data 12 Amplitude A 0 – 100% Csv Log file entry example: 0; 190; 129; 2007; 12; 17; 15; 17; 43; 17; 1; 30;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Am

plitu

de A

Txt Log file entry example: 15:17:43 - Entry 129 - Amplitude Adjust 30%



Event: Train Stop These event logs the information under which condition the train was stopped. Cell off-

set Data Cell Values Assumed

… … … 10 Event type id 2 = Train Stop

Header

11 Event data length 5

12 ModeType 0 = Unknown Mode 1 = Continuous Mode (only R100) 2 = Pulse mode 3 = Train mode (only R100) 4 = Sweep Mode (only R100) 5 = Traverse Mode (only R100)

13 Completion status 0 = success (the train ran to its end) 1 = user break ( the user stopped the train) 2 = disabled ( the machine stopped the train) 3 = overheating (The coil temperature extended the maximum allowed value) 4 = overheating (The intelligent thermal protection algorithm disabled the device to protect the coil from rapid overheating)

14 Elapsed time [0.0-X] ms 15 Stimulation count [0-X]

Fixed data for Train stop events.

16 Trains remaining [0-X] Csv Log file entry example:

2; 0; 3000; 31; 0;

Mod

eTyp

e

Com

plet

ion

stat

us

Elap

sed

Tim

e

Stim

ulat

ion

coun

t

Train

s rem

ainin

g

Txt Log file example: 10:44:57 - Entry 12 - Stopped in Pulse Mode - Completion status - Successful - Elapsed Time 3s - Stimulation Count 31 pulses - Trains Remaining 0

0; 190; 12; 2007; 12; 14; 10; 44; 57; 2;

5;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th



Event: Coil Temperature This event stores the coil Temperature. Cell Offset Data Cell Values Assumed

… … … 10 Event type id 4 = Coil Temperature

Header

11 Event data length 1 Fixed data for event – Coil Temperature

12 Coil Temperature 5,6,7,8 … 50 [°C]

Csv Log file entry example: 0; 34; 85; 2007; 6; 20; 14; 12; 54; 4; 1; 38;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Coil

Tem

pera

ture

Txt Log file example: 14:12:54 - Entry 85 - Coil Temperature is 38°C



Event: Coil Type This event is logged each time the machine detects a change in the coil type. Cell offset Data Cell Values Assumed

… … … 10 Event type id 7 = Coil Type

Header

11 Event data length 1 Fixed data for event – Ampli-tude Curve Re-cording

12 Coil Type id Unique number for the coil type: 00 = No Coil 255 = Unknown Coil 51 = "MCR-B40" 52 = "MC-80" 53 = "MC-60" 60 = "Cool-B65” 61 = "MCF-125" 62 = "MCF-B65" 63 = "MCO-200" 64 = "MCO-300” 65 = "MCF-Racetrack" 66 = "MCF-75"67 = "URO-1" 71 = "C-100”72 = "C-B60" 81 = "MC-125" 82 = "MC-B70" 83 = "MCP-B70" 84 = "MMC-140" 85 = "MC-B65-HO" 86 = "D-B80"87 = "Racetrack"


Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Coil

Type

Id

Txt Log file example: 13:15:41 - Entry 4 - Coil Type is MC-B70



Event: Model identification This event stores the information of machine type and its serial number. Together the machine type and serial number makes up a unique identification signature. Cell offset Data Cell Values Assumed

… … … 10 Event type id 8 = Model Identification

Header


12 Model type 0 = Unknown model 1 = MagPro G3 R30 2 = MagPro G3 R30 Option 3 = MagPro G3 X100 4 = MagPro G3 X100 Option 5 = MagPro G3 R100

Fixed data for event – Model Identification

13 serial number Integer number representing the serial number.

Csv Log file entry example: 0; 34; 51; 2007; 6; 20; 13; 15; 47; 8; 2; 5; 534;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Mod

el ty

pe

Seria

l Num

ber

Txt Log file example: 13:15:47 - Entry 51 - Model is R100 - Serial number is 534



Event: Date This event is stored in the log then the date changes. And every time the USB media is connected to the machine. Cell offset Data Cell Values Assumed

… … … 10 Event type id 10 = Date

Header

11 Event data length 3 Fixed data for event - Amplitude Curve Re-cording

12 Year The year the event occurred.

13 Month The month the event occurred 14 Day The day the event occurred. Csv Log file entry example: 0; 34; 62; 2007; 6; 20; 13; 15; 47; 10; 3; 2007; 6; 20;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Yea

r

Mon

th

Dat

e Txt Log file example: 13:15:47 - Entry 62 - Date 2007-06-20



Event: System Status When the system detects an internal error or warning condition it creates a system status event. Cell offset Data type Values Assumed

… … … 10 Event type id 11 = System status

Header

11 Event data length 1 Error Code 12 0 = No errors

1 = Current Error 2 = Discharge Hot 3 = Heat sink Hot 4 = Mono Resistor Hot

Current Error = Fatal error in cur-rent, cannot charge the capacitor. Discharge Hot = The thermal sensor at the discharge circuit report hot. Either in the main or in the option part. Heat Sink Hot = The thermal sensor in the power supply reports hot Mono Resistor Hot = The thermal sensor at the mono resistor circuit reports hot


Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Err

or C

ode

Txt Log file example: 14:09:40 - Entry 81 - System Status (Mono resistor hot)



Event: New Session When the system creates a new log file (e.g. a new formatted USB memory stick is inserted), the session id is incremented and a log event is added to the newly created file. Cell offset Data type Comment

… … … 10 Event type id 12 = New Session

Header

11 Event data length 1 Session id 12 1-n Incremented each time a new log file

is created. Csv Log file entry example: 0; 34; 1; 2007; 6; 20; 13; 15; 38; 12; 1; 34;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Sess

ion

id

Txt Log file example: 13:15:38 - Entry 1 - New Session (34)



Event: MEP Data Recording This event means that the user is saving the current displayed curve in the MEP menu. The MEP Data recording event stores the number identifying unique file name for the curve csv data file. Cell offset Data Cell Values Assumed

… … … 10 Event type id 9 = MEP Data recording

Header


12 Session id Session id is a number which is incremented each time the system find an empty USB disk (no prior csv log file)

Fixed data for event – MEP data Recording

13 Unique id for the corre-sponding MEP Data file.

The event stores the unique id for the corresponding MEP Data file. The number is reset to 1 each time a new session starts.

Csv Log file entry example: 0; 34; 95; 2007; 6; 20; 14; 14; 29; 9; 1; 34; 79

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Curr

ent s

essio

n id

Uni

que

id fo

r the

co

rres

pond

ing

ME

P D

ata

file.

Txt Log file example: 14:14:29 - Entry 95 - Rec MEP Data (34-79)



Event: Amplitude Curve Recording This event means that an amplitude curve is being recorded in a separate csv file for the current train sequence. Cell offset Data Cell Values Assumed

… … … 10 Event type id 5 = Amplitude Curve Recording

Header


12 Current session id 1-x Fixed data for event – Ampli-tude Curve Re-cording

13 Log event id for the corresponding Train Start event

The log event id for the corre-sponding Train Start event.

Csv Log file entry example:

0; 34; 68; 2007; 6; 20; 14; 8; 35; 5; 2; 34; 67;

Layo

ut ty

pe

Sess

ion

id

Ent

ry ID

Yea

r

Mon

th

Dat

e

Hou

r

Min

ute

Seco

nd

Eve

nt ty

pe id

Eve

nt d

ata

Leng

th

Curr

ent s

essio

n id

Log

even

t id

for t

he

corr

espo

ndin

g Tr

ain

Star

t eve

nt

Txt Log file example: 14:08:35 - Entry 68 - Record Ampl. (34-67)



Appendix 1: Amplitude Curve Data The Comma Separated Amplitude Data gives the user a possibility to see di/dt values during the train(s). It is saved as a Comma Separated File to make it easy to import data into a spreadsheet application to make a graph for visually data inspection and documentation. The Amplitude Curve Data are designed with 4 or 5 data columns and the content of the cells are: Column number

Data type Comment

1 Train number The modes can all repeat these base patterns. The train number tells the number of the current repeated base pattern. The first pat-tern is always marked 1.

2 Data code 1 = The device was in single stimuli mode. Meaning only one col-umn of amplitude samples was made. 2 = the device was in twin / dual or biphasic burst mode. Meaning two Columns of Amplitude samples was made.

3 Elapsed Time The elapsed time relative to the start of the train in milliseconds [ms]

4 Amplitude for A 5 Amplitude for B

The di/dt Amplitude measured in [A/μs]. The B amplitude is only available if the Data code is = 2. Meaning the device was in twin/dual - or biphasic burst mode. Example:

Twin/Dual mode

Biphasic Burst mode (shows only the first and last

pulse in Burst mode)



Appendix 2: MEP Data MEP Data is the measured motor threshold response curve. The Comma Separated MEP Data are saved as a Comma Separated File to make it easy to import data into a spreadsheet application to make a graph for visually data inspection and documentation. Example of MEP Data Line

numberFormat Model ;

Layout Type ; Data offset ; Date ; Time ;

X100 0 23 2007-08-21 12:23:45

1 2 3 4 5

6 MEP Settings

Time Base ; Sensitivity ; Pan ; Curve no ; Common BaseLine ; Lower Frequency limit ; Upper Frequency limit ; Trigger Mode ;

8 ms/div 100 μV/div 1000 us 1-5 off 20 Hz 10 kHz Stimulus

7 8 9 10 11 12 13 14

15 MEP data

Curve no ; 1 ; 2 ; 3 ; 4 ; 5 ; Session ID ; 36 ; 36 ; 36 ; 36 ; 36 ; Entry ID; 28 ; 32 ; 34 ; 36 ; 39 ; Data Code; 1; 1; 1; 1; 1; Amplitude (%);5; 10; 15; 20; 25; Didt (A/us) 5; 10; 16; 22; 28; Time in [μs] ; Amplitude in [μV]; 1000 ; -60 ; -60 ; 50 ; 60 ; 50 ; 1200 ; -50 ; -30 ; 60 ; 40 ; -30 ; 1400 ; -30 ; -20 ; -60 ; -40 ; 50 ; 1600 ; -60 ; -60 ; -20 ; -30 ; -40 ; 1800 ; -30 ; -66 ; -30 ; -20 ; 60 ; 2000 ; -20 ; -20 ; -40 ; -60 ; -20 ; 2200 ; -10 ; -50 ; 60 ; -40 ; -30 ; …

16 17 18 19 20 21 22 23 24 …

Format: Line 1 – Model The model tells the type of the MagPro machine used to create the MEP Data file. Because the R100 revision was the first edition the model was added to the file, to give the possibility to make the data format model depended. Line 2 – Layout type The layout type is an identification number telling the order and the data contest of the csv file. For this revision of the csv file the layout type is zero. If there is added more content to the csv file in the future the layout will change and the layout type number must change. Line 3 – Data offset The data offset gives the line position of the first MEP Data line. This can be used for automatic extracting the data because it tells how many lines must be skipped to get to the data.



Line 4 – Date The Date tells the date the curve was created. The Date is always written in yyyy-mm-dd format. Where yyyy is a 4 digit representation of the year, mm is a 2 digit representation of the month and dd is a 2 digit representation of the day. Line 5 – Time The Time tells the time the data was created. The Time is always written in hh-mm-ss format. Where hh is a 2 digit representation of the hour, mm is a 2 digit representation of the minute and ss is a 2 digit representation of the second. Blank Line: Line 6: - Blank Line number 6 is intentional left blank to give an easier read able report. Settings: Line 7 – Time Base The Time Base is the setting on the MEP Monitor at the time the data is stored. This info can be used to figure out how much zoom was active at the time the data was stored. Line 8 – Sensitivity The Sensitivity is the setting on the MEP Monitor at the time the data is stored. This info can be used to figure out how much zoom was active at the time the data was stored. Line 9 – Pan The Pan is the setting on the MEP Monitor at the time the data is stored. This info can be used to figure out how much zoom was active at the time the data was stored. Line 10 – Curve No The Curve No is the setting on the MEP Monitor at the time the data is stored. Line 11 – Common BaseLine The Common BaseLine is the setting on the MEP Monitor at the time the data is stored. Line 12 – Lower Frequency Limit The Lower Frequency Limit is the setting on the MEP Monitor at the time the data is stored. Line 13 – Upper Frequency Limit The Upper Frequency Limit is the setting on the MEP Monitor at the time the data is stored. Line 14 – Trigger Mode The Trigger Mode is the setting on the MEP Monitor at the time the data is stored. Blank Line: Line 15: - Blank Line number 15 is intentional left blank to give an easier read able report.



MEP data: Line 16: - Curve No Line number 16 tells the curve no for the column. The number of columns depends on which Curve No setting the user has selected. Cell no 1: Curve No is a text added to explain the context of the line. Cell no 2-11: Cells which holds the Curve no for the column. Line 17: - Session ID Line number 17 tells the Session id of the manual stimuli log event which was the stimuli used to generate the MEP Data. Cell no 1: “Session ID” is text added to explain the context of the line. Cell no 2-11: Cells which holds the session id for the stimuli which generated the MEP Data. Line 18: - Entry ID; Line number 18 tells the Entry ID of the manual stimuli log event which was the stimuli used to generate the MEP Data. Cell no 1: “Entry ID” text is added to explain the context of the line. Cell no 2-11: Cells which holds the Entry ID for the stimuli which generated the MEP Data. Line 19 – Data Code The Data Code is an identification number telling the order and the data content of the following rows. For this revision of the csv file the layout type is one. If there is added more content to the csv file in the future the layout will change and the layout type number must change. Line 20 – Amplitude (%) This is the Amplitude in % for the stimuli which generated the MEP Data. Line 21 – di/dt (A/μs) This is the di/dt in A/μs for the stimuli which generated the MEP Data. Line 22: - Time in [μs] ; Amplitude in [μV] Line number 22 tells the user the unit of the data. The time is given in micro seconds and the Am-plitude in micro Volt (column 2-11). Line 23 to 422: Line number 23 tells the Time and Amplitude. There are always 400 samples. Cell no 1: The first Cell holds the time of the MEP Data for the same line. The time is relative to the start of the stimuli pulse. The unit is always in micro seconds [μs]. Cell no 2-11: Cells which holds the amplitude measured in micro Volt [μV] for curve No. 1-10.



Appendix 3: Coil Type (See Also Accessories Catalogue) 0 No Coil

255 Unknown Coil

51 MCR-B40 52 MC-80 53 MC-60

60 Cool-B65 61 MCF-125 62 MCF-B65 63 MCO-200 64 MCO-400 65 MCF-RaceTrack 66 MCF-75 67 URO-1

71 C-100 72 C-B60

81 MC-125 82 MC-B70 83 MCP-B70 84 MMC-140 85 MC-B65-HO 86 D-B80 87 Racetrack

The above mentioned data for Coils are susceptible for updates.

MagPro and accessories are manufactured by:

Tonica Elektronik A/S Lucernemarken 15 DK-3520 Farum Denmark Telephone: +45 44 99 84 44 Fax: +45 44 99 15 44 www.tonica.dk Distributed by:

Alpine BioMed ApS Tonsbakken 16-18 DK-2740 Skovlunde Denmark Telephone: +45 44 57 90 00 Fax: +45 44 57 90 10 www.alpinebiomed.com

Alpine Biomed Corp. 17800 Newhope St., Suite B Fountain Valley, CA 92708 USA Toll-free 800-222-0074 Direct +1 714-839-8426 Fax +1 714-839-8429

Issued in Denmark, January 2008. P/N: 501-0722, rev. 2.0

DATA TRANSFER USER GUIDE

Documents

Transcript of DATA TRANSFER USER GUIDE