MoBI: Troubleshooting

Jump to: navigation, search

This page is under construction

Under the Purview of Rita Beransky




1. Actiview gives an error message (see image below) when you press Start

Actiview error screen.jpg
a. Check the speed mode
i. For a 1-person experiment, check that the speed mode to the left of the DC input on the amplifier is set to 4 (arrow points to 4, need a screwdriver to move it)
ii. For a 2-person experiment where the amplifiers are daisy-chained together the master 128 channel amplifier speed mode should be set to 0 and the slave amplifier (256 channel) speed mode should be set to 1
b. Check that the battery is turned on and the optical fiber cable is connected to both the amplifier and the receiver
c. Check that the USB is plugged in far enough into the computer. Also try changing the USB port (not all recognize the BioSemi driver)
d. Close and reopen Actiview and if there is still an error message, the CMS/DRL cable may be shorted; get a different one and replace the one in the cap and repeat.
e. If doing all of the above does not help (and you are using the MoBI Impedance Laptop), it’s possible that Actiview is malfunctioning (if someone copied over or updated the previous version). Check impedances on the Control computer and later do the following to fix the problem:
i. Go to C:\Program Files\ActiView605 (Biosemi)\Windows 32bit\Windows 32bit\Developers kit\C-code
ii. Copy the file called Laview_DLL.dll
iii. Paste it in C:\Program Files\ActiView605 (Biosemi)
iv. If Actiview still doesn’t recognize the amplifier, go to the Biosemi forum online ( under the topic Biosemi Software (ActiView executable) and try the various fixes described in thread #488 “error 500 on laptops”
2. In the Electrode offsets tab, all the electrodes are at the highest impedance and are flashing in unison; the blue light (CM in range) is blinking
a. This means that an electrode that is plugged into the cap is broken.
b. Remove the offending electrodes from the cap and take note of them.
c. If it’s unclear which is broken, you will have to take each out one by one until the light stops blinking; however, all known broken electrodes will be wrapped in tape so do not put them into the electrode wells


Configuration Manager

1. The Configuration Manager doesn’t open after clicking the shortcut
a. Make sure that the address listed in the small window that pops up is' and not localhost. Press Go.
b. Otherwise, do it manually
i. Open Internet Explorer
ii. In a blank tab, type in the PhaseSpace server IP address listed above and press enter
c. If it still doesn’t connect to the server, do the following:
i. Ping the server IP address
ii. Open Run, type cmd', press Enter
iii. In the Command window, type ping, press Enter
d. If it says Destination host unreachable check that the Ethernet cable from the server is plugged into the local network modem sitting on top of it
e. If it is able to ping the IP, reset the OWL server on the front of the Hub (small button labeled Reset), try to connect to Configuration Manager again
2. While encoding a driver, the error message “Cannot encode while the system is streaming” pops up when I press Encode
a. This means that PhaseSpace is streaming data.
b. Check that all instances of Master and calibration windows are closed (or, disconnect in Master)

Camera Calibration

1. All 16 cameras are not listed under Ports 2, 3, and 4 in the SYSTEM DEVICES section of the System tab.
Note: Before you attempt any of the steps below, it is important that you either do it under the supervision of an SRA or call one to let them know you are attempting this because the wrong decision may do damage to the system.
a. IMPORTANT: Shut off the PhaseSpace server before connecting and disconnecting cameras in the testing room ; restart the server once you are done making changes to the camera configuration
b. Check that all camera Ethernet cable strings are plugged into the front of the server (3 strings)
c. Every camera in the testing room should have only the green light on the left side of every camera on for all Ethernet cables connected to it (cameras at the end of the chain will only have cables plugged into the Previous camera port indicated by the red arrow facing towards the front of the camera; see below)

PhaseSpace camera.jpg
i. Reminder: The cameras are connected serially, so if camera number 2 isn’t working in the series of 1 through 6, then 2, 3, 4, 5 and 6 will not show up under System Devices
ii. Scenario:
a) Camera 8: Previous and Next both only have the green light on
b) Camera 9: Previous is only green, Next has no light on
c) Camera 10 & 11: both green and yellow lights are on for all ports with an Ethernet cable connected
d) Diagnosis: The connection from camera 8 to camera 9 needs to be checked. The yellow light on 10 & 11 indicates that both cameras are on standby because the previous camera connection is not functioning properly.
e) Solution: Check that the cable is firmly connected in to Next of Camera 9 and Previous of Camera 10. Press Scan Ports in the System Configuration page. If all cameras still don’t show, consider changing the cable. Press Scan Ports again.
d. If the Scan Ports function doesn’t show all cameras or if no changes were made to the camera strings during step c (none were found to be disconnected, or poorly connected), click on the tab Owl Server on the top, to the left of the System tab.
i. Under Server Control, select Calibration Backup if you haven’t moved the cameras and want to save the previous calibration and not have to redo it again. Save a calibration on that page.
ii. Under Server Control, click on the Reset Owl Server button.
iii. Go back to the System tab and Scan Ports again. If this fails, call for help.
e. DO NOT TRY THIS PART UNLESS UNDER SUPERVISION OF ONE OF THE SRAs If all else fails, switch to the PhaseSpace Server computer input on the monitor connected to the Control computer (input 1), restart the PhaseSpace server manually; once the server has booted up switch back to Control, refresh the internet page with the Configuration Manager and press Scan Ports again.

PhaseSpace Master Program

1. Some or all of the markers are grey rather than green when using the full body suit and LED strings.
a. If ALL of the markers are grey
i. Check that the driver is plugged in properly to the breakout adapter in the back of the suit. The rectangle that is jutting out of the adapter must fit into the notch on the driver connector (see section c of the MoBI Mocap page)
ii. Otherwise, try re-encoding the profile onto the driver.
b. If only a few of them are grey, check that all markers are placed correctly on the suit and are connected properly (try to disconnect and connect facing the other way). If particular markers are still grey, pinpoint which ones they are using the LED profile information and try replacing them with ones of the same letter.
2. Not all LED strings are showing up (legs and/or arms, etc, are missing) or the LEDs seemed to be numbered incorrectly in the 3D display (Ex: 48 is on the arm when it should be on the leg)
a. Disconnect the driver from the suit and re-encode the profile again
b. If that still doesn’t help, try to remember if the profile you are using was created “from scratch” in Create Profile or was created by copying another profile and then editing the copy. If it is the case that it was copied over, you will need to create a new profile using the Create Profile option and delete this faulty one because the copy profile function (copy button to the far right of each profile listing) does not work properly.


General Troubleshooting

  • If one of the DataSuite programs does not seem to be working appropriately, the first thing to check is if there are multiple instances of the same program open
  • There should only be ONE instance of each program open; if there is more than one, close the program and reopen it (you may need to close and reopen other programs and reinitialize data streams depending on where in the process of setting up the DataSuite series you are)

General Computer

1. Shortcuts do not show on Desktop
a. Right-click on the Desktop
b. Select Show desktop icons (second from top)
2. Monitor does not turn on even though the computer seems to be on and you have tried pressing the keyboard multiple times and clicking the mouse
a. On the tower, press and hold the power button until it shuts down.
b. Press again to start the computer.


1. When first opening Producer, multiple windows pop up with the error message “ARG[…]”
a. On the Desktop, go to the folder X32 and open the Producer folder
b. Look for a file named producer.par and delete it
c. Reopen Producer
2. There has been an error and I need to stop the experiment script that is already running
a. Press Esc on the keyboard
b. Select Cancel when prompted (vs Continue which will keep running the script)


1. On Projecting, EventCode.(#) does not appear as an option in dropdown menu of Send stream in DataPipe
a. Option 1: Check that there is only ONE instance of DataPipe open on Projecting. Close the ones in which there is no EventCode.(#) option; the very first one opened should have it
b. Option 2: If there is only 1 DataPipe open on Projecting, check that Producer is open. If not, open it and load your paradigm.
c. Option 3: If Producer is open, close and reopen both Producer and DataPipe.
2. EventCode.(#) stream does not show up in DataPipe on Control even though the event code stream was sent
a. Option 1: Wait a minute. Sometimes it takes a little longer to send the stream over to Control
b. Option 2: Close and reopen DataPipe on both computers and send the stream over again
c. Option 3: Check that producer and other DataSuite programs are all the same version
i. Go to and copy the Producer folder in place of the one you currently have in your personal folder to verify that you have the latest version
ii. Or, on the Desktop, open the folder x32 and right-click in the folder and select VNC update. This will synch with the DataSuite folders on the ftp site and update the folder on the desktop.
3. Two eventcode.(#) streams appear in DataPipe on Control
a. Turn off Local Area Connection 1 on both Projecting and Control by following the steps in section B of the MoBI DataSuite page.
b. Restart DataPipe on both computers and send the stream over again.


  • When selecting Connect in the PhaseSpace tab of DataSource to start the PhaseSpace stream, the program freezes and then crashes.
a. Option 1: Check that the PhaseSpace program Master is open and connected (green light on Connect button on top left)
b. Option 2: Make sure that the mode is set to 1 in both the Master program (NOT default) and in the PhaseSpace tab of Datasource; if changes were made in Master proceed to next option
c. Option 3: In Master, disconnect and connect (press the green Connect button on the top left so that it’s grey to disconnect, press again to connect and make it green); do this even if Option 2 above does not apply and modes in both programs are set to 1!

Wireless EEG

  • biosemi.(#) stream does not show up in DataPipe on Control even though the stream was sent over
a. Option 1: Wait a minute. Sometimes it takes a little longer to send the stream over to Control
b. Option 2: Close and reopen DataPipe on the Netbook and Control and send the streams over again


1. There is no DataRiver box on the bottom left corner of StreamSaver to drag a stream into
a. This means that StreamSaver was not opened before sending streams through DataPipe.
b. Close all DataSuite programs on Control (DataPipe, DataSource, StreamSaver)
c. Repeat steps listed in DataSource (setting up data streams) with StreamSaver opened before ANY other program
2. After opening a new file and pressing the red play button in StreamSaver, the red numbers counting the number of samples are increasing in value faster than normal (i.e. increasing by more than 1 every ~500ms)
a. Check that there is only one instance of DataSource open
b. If there is more than one open, close both DataSource windows and repeat steps in DataSource (setting up data streams)


1. Only 3 channels appear in the 3-D box of StreamViewer for the phasespace stream
a. Close StreamViewer.
b. Check that the number of channels entered in the PhaseSpace tab of DataSource is not more than 72
c. If it is, close and reopen DataSource.
d. Enter the number of channels to be less than 72, and reconnect. Resume the stream.
e. Repeat steps in the StreamSaver section to start recording in StreamSaver.
2. When switching from the 3-D tab to the Time tab, the program freezes/crashes
a. With StreamViewer newly opened, check that you have selected a stream to view from the bottom left drop-down menu
b. To view all streams concurrently, select the datariver stream
3. When viewing the biosemi stream, the data looks unusual/strange (at small scale, straight lines punctuated by small blips) but looks normal when viewed in Actiview.
a. Check that the speed mode setting (bottom right, next to DC Input) on the amplifier is set to 4
b. If not, get a small screwdriver and change gently to 4 (make sure it sits firmly on the number 4 and not off slightly)

Video Recording


1. I click on the OcularisClient shortcut, but the program doesn’t open and there is no instance of Ocularis already open.
a. Open Task Manager (Cntrl+Alt+Delete), go to the Processes tab
b. Find OcularisClient.exe and end the process
c. Try starting the Ocularis Client again
2. The group of control buttons at the bottom of the Ocularis program do not have the left/right arrows and I can’t navigate through the recordings as described in the Browsing section of the Video Recording page
a. If instead of the magnifying glass on the far left of the group of controls there is the following icon:Ocularis magn icon.jpg, click on it
b. It will revert to normal playback mode with the magnifying glass now in its place


1. There is no observed connection to the cameras in Ocularis on Surveillance (you are given an error message in place of the camera views in the program)
a. Check if the 3COM OfficeConnect Gigabit Switch, on the audio equipment rack next to the desks, is on (check if lights are on)
i. If not, trace the power cable from the router and unplug and plug in again
ii. If still not on, check that the connections from the camera cables into the back are secure
b. If the switch is working, check if there is a live stream in Netguard
i. If not in Ocularis but in Netguard, try restarting Ocularis (terminate process in Task Manager if necessary to close both the viewer and the client)
ii. If there is no connection in both programs, check Netguard on 'Watching and if there is no connection on Watching either, call for help
2. When pressing the scroll-lock button on the keyboard to toggle between the Surveillance and Watching computers, there is no input for either one or both computers
a. Trace the connections between the computer(s) in question and the monitor and make sure that everything is securely plugged in
b. If this doesn’t remedy the situation, call for help


A. No images are displayed on the walls of the testing room either when running the Test through the Screen Resolution section of Control Panel or when dragging stimuli to the extended desktop portions of the screen to display

1. Check that the projectors are turned on in the testing room (indicator light is green under I/O)
2. Repeat steps in section A.6 to verify that preset 2 is selected

Created: --Rita Beransky 14:21, 11 February 2011 (UTC)

Return to MoBI Lab Wiki Home