Electronics for Neuroscience

Getting started

Already have Deuteron loggers and want to start experimenting?

General Instructions

We recommend you read the general instructions before starting your experiment. It gives a brief summary of the set up instructions, and outlines other important concerns such as general care for your loggers, the radio range of your loggers, information about batteries and more.

Setting up your experiment

Ready to set up your experiment? You can find instructions here on how to get started with recording in the post below.

Using the LoggerCommand3 software

If you have followed the instructions in the section on Setting up Deuteron Logging Systems, and have successfully established communication between the PC and the transceiver and logger, the system is fully set up and ready to use. You will use the LoggerCommand3 program to communicate with the logger throughout the experiment – for example, to start and stop recordings, to log events, etc. You can find the manual for the LoggerCommand3 program below.

Getting started with your data

A first look

You’ve finished your recording and are ready to start looking at your data. We recommend getting an overview of your data starting with the NeuralFileExplorer program (v2.6).


Get started with your events using the Event File Viewer. You can use the utility program to view events or you can use the provided DLLs to integrate the processing of event data into your data processing pipeline in Matlab or Python. For the manual and download links, see the page below.

Neural and other types of data

There are two ways you can look at your data: the FileViewer utility program, which is intended to view your data, and Matlab/Python scripts demonstrating how to extract and organize the non-event data found in your files. There is a manual describing the precise organization of the data in the flat and block file formats here.

For the FileViewer utility program, see below

For Matlab and Python scripts demonstrating how to extract and organize the non-event data, see below