Device Troubleshooting

These are addition tips and troubleshooting advice and help contact information for various devices and software (if needed).


MITes





Wockets

    • When a wocket is disconnected, the screen will look like this:

ppc_wockets_api_screen_5.jpg

    • If plotting, the data stream from that sensor will cease. Also, the antenna image next to that wocket’s ID will turn red. Look at the disconnected wocket (you can tell which is disconnected by shaking them all a little and using the process of elimination or you can keep track of which ID corresponds to which sensor).
    • If the yellow LED is flashing, just leave it alone and it should reconnect on its own. This might take up to 20 seconds. If it does not reconnect, you might try pressing the reset button (black button with “RST” above it). If this does not cause the yellow LED to flash, the wocket is likely out of battery or broken, and it should be replaced.
    • Please let us know of the problem.



Oxycon

  • For a full Oxycon restart:
    • remove the battery from the mobile unit. Disconnect the USB cable attached to the laptop, remove the power source from the PC unit (this is very important), and disconnect the yellow cables from the DEx unit. Also shut down the laptop.
    • This should solve the problem if the Oxycon unit gives an error during warmup: "Failure to initialize".

  • Problem with the Oxycon report.
    • If you have problems generating the oxycon report (e.g. some times the oxycon report is sent to a printer rather than a file), make sure that your default printer is set to "Generic/Text Only".
oxycon_troubleshooting_printer.jpg


  • Technical Support.
    • Oxycon Tech Support can be contacted at 800-231-2466 extension 8500. Press 2 for Metabolic, 2 for Jeager. They will help with a variety of technical issues.



Actigraphs

It is definitely the case that the Actigraph software is picky about which physical USB port you are using. On some computers, the GT1M is working with one physical port, and the GT3X on the other. Plugging in other USB devices may cause it to break. Bottom line: if it stops working try plugging into other USB ports and maybe it will fix it.

If your computer is unable to detect the Actigraphs, please go to http://support.theactigraph.com/downloads/?fw, select Firmware, and download the necessary driver.

  • For GT1M, the name of the file should be "Lynx 07.02.00"
  • For GT3X, it should be "Matrix 04.01.00"
  • Be sure to save the files as "All files"! Saving them as text files will not do anything.

If your computer is able to detect the Actigraphs, but the software is not, you might need to change your COM port number to a lower one. (http://support.theactigraph.com/kb/?p=37)
  • Navigate to Control Panel then Device Manager
  • Right click on your device and select Properties, then Port Settings and Advanced
  • Change your COM port number to something lower (preferably to the COM port number you had used before with an Actigraph that worked)

If your computer is unable to update ActiLife to the newest version (currently 4.4.1) because of an administrator issue and you are running Windows 7 or Vista, you need to change your settings:

Vista
  • Go the the Control Panel and choose User Accounts
controlpanel.jpg

  • Choose Turn User Account Control On or Off
  • Uncheck the box next to Use User Account Control (UAC) to help protect your computer and click OK
uac.jpg

  • Next time you open ActiLife, there should be no problem updating.

Windows 7
  • Click Start Menu and type in "UAC" into the Search bar at the bottom of the menu
  • Select the option "Change User Account Control settings"
  • Drag the rectangular knob all the way down to "Never notify" and click OK. (You may need to restart your computer afterwards)
UAC_turnoff.PNG

Wockets Data Merger Program: We had to make some changes in the Data Merger program, because the application was not able to find our correctly labeled Actigraph or Zephyr data.

Actigraphs (GT3X)

Open up the CSV file and check to see how many columns of data you have for a single actigraph. If you have 5, you should be fine, but if you have any other number you just need to make 2 simple changes in the Data Merger Form1.cs (in your Google code, wockets > projects > PC > DataMerger).
In the Read Actigraph section, wherever it references tokens.Length with the number 5, change the number 5 to your number of columns (most likely 4 as shown below in bold type):

else if (actigraph_line.Contains("GT3X"))
...
do
{
...
} while (tokens.Length!=4);

...
do
{
tokens = actigraph_line.Split(',');
if (tokens.Length == 4)
...
} while ((actigraph_line = actigraphReader.ReadLine()) != null);
...
catch (Exception e)
{
throw new Exception("Actigraphs: Parsing failed " + e.Message);
}
for (int r = 0; (r < actigraphData.Length); r++)
{
if (hasActigraph == false)
hasActigraph = (actigraphData[r].Count > 0);
actigraphRecords += actigraphData[r].Count;
}
#endregion Read Actigraph data


Zephyr

First look at your data. If it’s saved as an excel spreadsheet, you’ll need to convert it to a csv file. Also you need to make sure the format of the date in the first column is correct. Select the cells, right click to Format cells. In the Number tab, choose the Custom category and make the format mm/dd/yyyy hh:mm:ss. Make sure to save the file as *-zephyr*.csv.
The reason for this change is that the DateTime function in Matlab takes parameters in this order: (year, month, day, hour, minute, second), but usually Excel formats the date as month/day/year.
Modify this line in the Read Zephyr section of Form1.cs in the Data Merger program (in your Google code, wockets > projects > PC > DataMerger):

zephyrTime = new DateTime(Convert.ToInt32(dateTokens[0]), Convert.ToInt32(dateTokens[1]), Convert.ToInt32(dateTokens[2]), Convert.ToInt32(timeTokens[0]), Convert.ToInt32(timeTokens[1]), Convert.ToInt32(timeTokens[2]));

To:

zephyrTime = new DateTime(Convert.ToInt32(dateTokens[2]), Convert.ToInt32(dateTokens[0]), Convert.ToInt32(dateTokens[1]), Convert.ToInt32(timeTokens[0]), Convert.ToInt32(timeTokens[1]), Convert.ToInt32(timeTokens[2]));