Contributions:MicroLeadsADC - Revision history

Dmehta: /* Known Issues */

2024-04-11T19:28:12Z

Known Issues

← Older revision		Revision as of 19:28, 11 April 2024
Line 22:		Line 22:
	There are a few known issues with the MicroLeads device system.		There are a few known issues with the MicroLeads device system.

	Sometimes when the device has been commanded to stop recording or stimulating, further commands to it will not work as the device is unresponsive. The solution for this has been to let the device lose power completely, and then recharge it. \n		Sometimes when the device has been commanded to stop recording or stimulating, further commands to it will not work as the device is unresponsive. The solution for this has been to let the device lose power completely, and then recharge it.

	There are some issues with getting consistent data from stimulation. At times, the stimulation will abruptly stop as well. When using the associated GUI from MicroLeads, this was usually accompanied by a "Compliance" error.		There are some issues with getting consistent data from stimulation. At times, the stimulation will abruptly stop as well. When using the associated GUI from MicroLeads, this was usually accompanied by a "Compliance" error.

	Communication for commands is not consistent either. It may take several attempts to get the device to start working.		Communication for commands is not consistent either. It may take several attempts to get the device to start working.

Dmehta: /* Known Issues */

2024-04-11T19:27:45Z

Known Issues

← Older revision		Revision as of 19:27, 11 April 2024
Line 22:		Line 22:
	There are a few known issues with the MicroLeads device system.		There are a few known issues with the MicroLeads device system.

	Sometimes when the device has been commanded to stop recording or stimulating, further commands to it will not work as the device is unresponsive. The solution for this has been to let the device lose power completely, and then recharge it.		Sometimes when the device has been commanded to stop recording or stimulating, further commands to it will not work as the device is unresponsive. The solution for this has been to let the device lose power completely, and then recharge it. \n
	There are some issues with getting consistent data from stimulation. At times, the stimulation will abruptly stop as well. When using the associated GUI from MicroLeads, this was usually accompanied by a "Compliance" error.		There are some issues with getting consistent data from stimulation. At times, the stimulation will abruptly stop as well. When using the associated GUI from MicroLeads, this was usually accompanied by a "Compliance" error.
	Communication for commands is not consistent either. It may take several attempts to get the device to start working.		Communication for commands is not consistent either. It may take several attempts to get the device to start working.

Dmehta: /* Known Issues */

2024-04-11T19:27:34Z

Known Issues

← Older revision		Revision as of 19:27, 11 April 2024
Line 22:		Line 22:
	There are a few known issues with the MicroLeads device system.		There are a few known issues with the MicroLeads device system.

	~~First, sometimes~~ when the device has been commanded to stop recording or stimulating, further commands to it will not work as the device is unresponsive. The solution for this has been to let the device lose power completely, and then recharge it.		Sometimes when the device has been commanded to stop recording or stimulating, further commands to it will not work as the device is unresponsive. The solution for this has been to let the device lose power completely, and then recharge it.
	~~Second, there~~ are some issues with getting consistent data from stimulation. At times, the stimulation will abruptly stop as well. When using the associated GUI from MicroLeads, this was usually accompanied by a "Compliance" error.		There are some issues with getting consistent data from stimulation. At times, the stimulation will abruptly stop as well. When using the associated GUI from MicroLeads, this was usually accompanied by a "Compliance" error.
	~~Third, communication~~ for commands is not consistent either. It may take several attempts to get the device to start working.		Communication for commands is not consistent either. It may take several attempts to get the device to start working.

	==Using the MicroLeads ADC==		==Using the MicroLeads ADC==

Dmehta: /* Known Issues */

2024-04-11T19:27:14Z

Known Issues

← Older revision		Revision as of 19:27, 11 April 2024
Line 23:		Line 23:

	First, sometimes when the device has been commanded to stop recording or stimulating, further commands to it will not work as the device is unresponsive. The solution for this has been to let the device lose power completely, and then recharge it.		First, sometimes when the device has been commanded to stop recording or stimulating, further commands to it will not work as the device is unresponsive. The solution for this has been to let the device lose power completely, and then recharge it.

	Second, there are some issues with getting consistent data from stimulation. At times, the stimulation will abruptly stop as well. When using the associated GUI from MicroLeads, this was usually accompanied by a "Compliance" error.		Second, there are some issues with getting consistent data from stimulation. At times, the stimulation will abruptly stop as well. When using the associated GUI from MicroLeads, this was usually accompanied by a "Compliance" error.

	Third, communication for commands is not consistent either. It may take several attempts to get the device to start working.		Third, communication for commands is not consistent either. It may take several attempts to get the device to start working.

Dmehta: /* Known Issues */

2024-04-11T19:27:03Z

Known Issues

← Older revision		Revision as of 19:27, 11 April 2024
Line 19:		Line 19:

	===Known Issues===		===Known Issues===

			There are a few known issues with the MicroLeads device system.

			First, sometimes when the device has been commanded to stop recording or stimulating, further commands to it will not work as the device is unresponsive. The solution for this has been to let the device lose power completely, and then recharge it.

			Second, there are some issues with getting consistent data from stimulation. At times, the stimulation will abruptly stop as well. When using the associated GUI from MicroLeads, this was usually accompanied by a "Compliance" error.

			Third, communication for commands is not consistent either. It may take several attempts to get the device to start working.

	==Using the MicroLeads ADC==		==Using the MicroLeads ADC==

Dmehta: /* Proper Charging */

2023-11-02T21:43:07Z

Proper Charging

← Older revision		Revision as of 21:43, 2 November 2023
Line 172:		Line 172:
	</gallery>		</gallery>

	There may be dead zones on the powerpad, so there might be some trial and error required for optimal placement.		Essentially, you want to make sure there is enough surface area for the implant relative to the powerpad to be able to charge. You also want to make sure that the implant is not too far from the powerpad to be able to charge. There may be dead zones on the powerpad, so there might be some trial and error required for optimal placement.

	====Micro-Leads GUI====		====Micro-Leads GUI====

Dmehta: /* How to set up with BCI2000 */

2023-07-11T17:08:02Z

How to set up with BCI2000

← Older revision		Revision as of 17:08, 11 July 2023
Line 248:		Line 248:

	Now we will set up the research PC. First, follow the BCI2000 installation guide found [[Programming_Howto:Building_and_Customizing_BCI2000\|here]] to install BCI2000 and compile the solution on your PC.		Now we will set up the research PC. First, follow the BCI2000 installation guide found [[Programming_Howto:Building_and_Customizing_BCI2000\|here]] to install BCI2000 and compile the solution on your PC.

			===Connecting to the Devices===

			when using BCI2000, the research PC will replace the provided laptop from MicroLeads. First, we will have to connect the PC to the devices using the ethernet adapter. Simply plug it in to an empty USB port.

			Next, we have to make sure that the ethernet connection is on the same network subnet mask and that the IPv4 address is able to communicate with the basestation.

			To do this, first open up a command prompt and type
			ipconfig /all

			A list of IP connections should show up now. Scroll and find the connection that lists ethernet and might have Realtek USB controller as the connection.

			Check to see if the IPv4 configuration starts with 192.168.1.X where X is any number. Also check to make sure that the default gateway is set.

			If it does, great! You can move on to the next step. If not, all we need to do is change the IPv4 configuration.

			In the Windows toolbar, search control panel. Then click on Network and Internet. Then click on Network and Sharing Center.

			On the left hand side, you should see "Change adapter settings". Click on that, and then right click on the Ethernet connection associated with the adapter. It should say "Realtek USB controller" or something similar. Click on "Properties" in the popup.

			Find "Internet Protocol Version 4 (TCP/IPv4)" and double-click. Toggle the section "Use the following IP address" on.

			For IP address, use any IP address that isn't in use currently and starts with 192.168.1 .
			For subnet mask, use 255.255.255.0.
			For default gateway, use 192.168.1.1.

			Make sure no warnings popup after validating, and you should be able to continue!

	===Creating a Batch File===		===Creating a Batch File===

Dmehta: /* Verifying Device Properties */

2023-06-25T19:46:46Z

Verifying Device Properties

← Older revision		Revision as of 19:46, 25 June 2023
Line 224:		Line 224:
	The meaning of each parameter corresponds to the following diagram.		The meaning of each parameter corresponds to the following diagram.

	<gallery mode="packed" heights=~~300px~~>		<gallery mode="packed" heights=400px>
	File:microleads_pulse_definition.png\|Pulse Definition		File:microleads_pulse_definition.png\|Pulse Definition
	</gallery>		</gallery>

Dmehta: /* Python API */

2023-06-25T19:25:27Z

Python API

← Older revision		Revision as of 19:25, 25 June 2023
Line 186:		Line 186:
	====Python API====		====Python API====

	If you have access to the Python API, you can use a Powershell script to ensure charging. ~~You must also have~~		If you have access to the Python API, you can use a Powershell script to ensure charging.

	First, make sure that the wheel file you received is installed in a python environment properly.		First, make sure that the wheel file you received is installed in a python environment properly.

Dmehta: /* Initial Setup */

2023-06-25T19:24:51Z

Initial Setup

← Older revision		Revision as of 19:24, 25 June 2023
Line 140:		Line 140:
	Next, we will connect to the basestation. Click the pulldown menu that says "Select Base Station", and then click connect once you have it selected.		Next, we will connect to the basestation. Click the pulldown menu that says "Select Base Station", and then click connect once you have it selected.

	Next, click on the button in the lower left corner that says "Select Devices". A pop-up menu should appear ~~that looks like this:~~		Next, click on the button in the lower left corner that says "Select Devices". A pop-up menu should appear.

	~~<gallery mode="packed" heights=500px>~~
	~~File:microleads_select_devices_gui~~.~~png~~
	~~</gallery>~~

	In this menu, select the devices on the left and click the middle arrow button. The devices should appear in the columns on the right like this:		In this menu, select the devices on the left and click the middle arrow button. The devices should appear in the columns on the right like this: