User manual

2.12 Basic, Standard and Advanced Mode Capabilities

When you enter the WinLTP program for the first time in the Demotrial period you are running in the

Advanced Mode with a fully functioning Protocol builder (Fig. 2.12.1, left) including automated perfusion.

In this mode you can write any number of advanced protocols including this automated perfusion protocol

using ‘Slow0’ and ‘Slow1 Perfuse’ events. All the Protocol Builder events can be used and are shown in

green, including the ‘Run’, ‘ElseRun’, ‘AvgLoop’, and ‘Loop’ events, the ‘Slow0’, ‘Slow1’, ‘Fast0’ and

‘Fast1’ Perfuse events, the P0, P1, T0 and T1sweep events, and the Delay event. The Advanced Mode

capabilities include:

1) A fully functional Protocol Builder

2) Run fully Automated Perfusion Control (which uses the Perfuse events Protocol Builder)

3) Save Continuous Acquisition files while running the Main Protocol

4) Save the Experimental Log file

5) Convert WinLTP ADsweep files to Axon Binary (*.abf) files

6) 2 AD channels

7) 4 different Pulse/Train Sweep stimulations

8) Impose single and averaged sweeps

9) View neighboring sweeps

If you have not purchased and installed a Standard or Advanced Version USB dongle, at the end of the

60 day Demotrial Period you will automatically enter the free Basic Mode partially functional Protocol

Builder (Fig. 2.12.1, middle). Only the green Insert Event buttons can be used and still save ADsweep

data. These include ‘AvgLoop’, ‘Loop’, ‘P0sweep’ and P1sweep events. If you use the yellow Insert

Event buttons, the ‘Run’, ‘ElseRun’, ‘Tosweep’ ‘T1sweep’ and ‘Delay’ events, your protocol will run

perfectly OK, except that the ADsweep data will not be saved. This allows you to easily test the

Advanced Mode functions to see if it is worthwhile upgrading to the Advanced Version. The Basic Mode

functionality includes:

1) A partially functional Protocol Builder

2) No Automated Perfusion Control (which uses the Perfuse events Protocol Builder)

3) Cannot save Continuous Acquisition files while running the Main Protocol (Fig. 2.12.2 B)

4) Cannot save the Experimental Log file (Fig. 2.12.2A)

5) Cannot convert WinLTP ADsweep files to Axon Binary (*.abf) files

6) Only 1 AD channel (Fig. 2.12.2B)

7) Only 3 different Pulse/Train Sweep stimulations - T1sweeps cannot be evoked (Fig. 2.12.2C)

8) Impose single and averaged sweeps

9) View neighboring sweeps

However, even with the Basic Mode, partially functional Protocol Builder, you can run basic LTP

experiments. By clicking the ‘Init’ Protocol button (top panel), you can immediately do repetitive

P0sweeps, by clicking on the Init ‘Avg Protocols’ button (bottom panel)or you could do repetitive

P0sweeps with Signal Averaging. You can also get alternating P0/P1sweeps you press down the

LeftMouseButton to click on the ‘P1sweep’ Insert button, hold the LeftMouseButton down to drag the

P1sweep down to just below the P0sweep in the MainProtocol script, and then release the

LeftMouseButton to insert the P1sweep just below the P0sweep.

And by clicking on the Evoked ‘Single’ and ‘Repetitive Sweeps’ buttons while the MainProtocol is

running, you can evoke Single or Repetitive P0, P1 and T0 (but not T1) sweeps, which allows you to run

basic LTP type experiments.