Re: OpenEEG Questions

--===============3116853958874617165==
Content-Type: multipart/alternative; boundary="000000000000e0cefe05afc46527"

--000000000000e0cefe05afc46527
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I am sorry for the spam, but in my previous e-mail I said: "any of those
changes you proposed are possible" - that is false. One change you
mentioned was to feed raw data onto GPIO pins of RPi. That will not work,
because what you need to do with the signal is to convert it from analog to
digital data through ADC and RPi doesn't have an ADCs. You can avoid using
ATmega microcontrollers, but you still would have to use some external chip
with ADC functions. And then you would have to program your own firmware
and protocol, so you can use the data in applications running on RPi.
Though what you can do with RPi is to feed the data directly from ATmega
through native UART interface on RPi without the need for USB-UART chip.
But about that, I am not really sure about the signalling voltage mismatch
5V/3.3V. So it is still preferred to use a USB interface with UART bridge
like CP2102.

S pozdravom,
Dami=C3=A1n Filo


so 5. 9. 2020 o 21:49 Yonah Elorza <[email protected]> nap=C3=ADsal(a):

> Hello!
>
> I'm a computer engineer interested in making some modifications to the
> OpenEEG circuit, and had a few questions, if anyone is available to answe=
r
> them. I've read through all the documentation on the website, and have
> worked with the OpenEEG platform for a few years now, and wanted to see i=
f
> the following was possible:
>
> -Designing better noise cancelling to reduce commons noise, as well as
> noise between electrodes.
> -Integrating an FPGA into the design which acts as a hardware Fast Fourie=
r
> Transform
> -Making the circuit modular enough that you can stack multiple together t=
o
> have 4, 8, 16, etc. electrodes reading at the same time.
> -Long term: modifying the design of the circuit to work without the AT
> processor, instead having hardware control from the GPIO of a Raspberry P=
i,
> and all data being fed raw to either the GPIO or USB interface of the Pi.
>
> If anyone has reasons this wouldn't be possible, or if you have
> suggestions for any of these changes, please let me know. I absolutely lo=
ve
> this project, and would love to be able to contribute my own work to it.
>
> --
> Best Regards,
> Yonah Elorza
> Columbia School of Engineering | Class of 2018
> Computer Engineering
> Tel: ( <%28786%29%20205%20-%204304>305)-542-1735
> _______________________________________________
> Openeeg-list mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openeeg-list
> Go to the above address to change your
> subscription options, e.g unsubscribe.
>

--000000000000e0cefe05afc46527
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I am sorry for the spam, but in my previous e-mail I =
said: &quot;any of those changes you proposed are possible&quot; - that is =
false. One change you mentioned was to feed raw data onto GPIO pins of RPi.=
 That will not work, because what you need to do with the signal is to conv=
ert it from analog to digital data through ADC and RPi doesn&#39;t have an =
ADCs. You can avoid using ATmega microcontrollers, but you still would have=
 to use some external chip with ADC functions. And then you would have to p=
rogram your own firmware and protocol, so you can use the data in applicati=
ons running on RPi.<br></div><div>Though what you can do with RPi is to fee=
d the data directly from ATmega through native UART interface on RPi withou=
t the need for USB-UART chip. But about that, I am not really sure about th=
e signalling voltage mismatch 5V/3.3V. So it is still preferred to use a US=
B interface with UART bridge like CP2102.<br></div><div><br></div><div><div=
><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signatu=
re"><div dir=3D"ltr"><div>S pozdravom,</div><div>Dami=C3=A1n Filo<br></div>=
</div></div></div><br></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">so 5. 9. 2020 o=C2=A021:49 Yonah Elorza &lt;<=
a href=3D"mailto:[email protected]">[email protected]</a>&gt; nap=C3=ADsal(=
a):<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"=
ltr"><div>Hello!</div><div><br></div><div>I&#39;m a computer engineer inter=
ested in making some modifications to the OpenEEG circuit, and had a few qu=
estions, if anyone is available to answer them. I&#39;ve read through all t=
he documentation on the website, and have worked with the OpenEEG platform =
for a few years now, and wanted to see if the following was possible:</div>=
<div><br></div><div>-Designing better noise cancelling to reduce commons no=
ise, as well as noise between electrodes.</div><div>-Integrating an FPGA in=
to the design which acts as a hardware Fast Fourier Transform</div><div>-Ma=
king the circuit modular enough that you can stack multiple together to hav=
e 4, 8, 16, etc. electrodes reading at the same time.<br></div><div>-Long t=
erm: modifying the design of the circuit to work without the AT processor, =
instead having hardware control from the GPIO of a Raspberry Pi, and all da=
ta being fed raw to either the GPIO or USB interface of the Pi. <br><br></d=
iv><div>If anyone has reasons this wouldn&#39;t be possible, or if you have=
 suggestions for any of these changes, please let me know. I absolutely lov=
e this project, and would love to be able to contribute my own work to it.<=
br></div><div><br>-- <br><div dir=3D"ltr"><div dir=3D"ltr"><div><div dir=3D=
"ltr"><div dir=3D"ltr" style=3D"font-size:12.8px"><div>Best Regards,<br></d=
iv>Yonah Elorza<br></div><div dir=3D"ltr" style=3D"font-size:12.8px"><div s=
tyle=3D"font-size:12.8px">Columbia School of Engineering | Class of 2018</d=
iv><div style=3D"font-size:12.8px">Computer Engineering</div><div style=3D"=
font-size:12.8px">Tel:=C2=A0<a href=3D"tel:%28786%29%20205%20-%204304" valu=
e=3D"+17862054304" style=3D"color:rgb(17,85,204)" target=3D"_blank">(</a><s=
pan><span title=3D"Call with Google Voice">305)-542-1735</span></span></div=
></div></div></div></div></div></div></div>
_______________________________________________<br>
Openeeg-list mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">Ope=
[email protected]</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/openeeg-list" rel=
=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/listi=
nfo/openeeg-list</a><br>
Go to the above address to change your<br>
subscription options, e.g unsubscribe.<br>
</blockquote></div>

--000000000000e0cefe05afc46527--


--===============3116853958874617165==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============3116853958874617165==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline