Hello
I want to use the arduino pro mini with pure data on the serial pins on the raspberry pi2 board for a project i am working on. My Arduino Uno works fine but i assume that is i assume because i am getting the serial data sent on the USB which seems to show up as
/dev/ttyAMA0 in raspberry pi debian
what i assume i need is it to work on /dev/ttyS0 /dev/ttyS1
I already turned off the serial to console stuff in raspberry and commented out the commandline stuff as well as modified the innittab getty things according to the interwebs, but i cannot get Pduino or comport to recognize the device when it's connected to the analog serial pins directly on the raspberry
i moved the whole shebang over to MAC and tested it after installingthe FTDI USB Serial drivers and loaded the ALLINPUTS Firmata and it works there but that is again USB.
Does anyone have any ideas to share, though i know this might be more of a linux issue, but it seems like pd is only seeing USB serial for pduino and comport
GAH...
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020
On Mon, Sep 21, 2015 at 10:55 AM, Pagano, Patrick <pat@digitalworlds.ufl.edu
wrote:
Hello
I want to use the arduino pro mini with pure data on the serial pins on the raspberry pi2 board for a project i am working on. My Arduino Uno works fine but i assume that is i assume because i am getting the serial data sent on the USB which seems to show up as
/dev/ttyAMA0 in raspberry pi debian
what i assume i need is it to work on /dev/ttyS0 /dev/ttyS1
I already turned off the serial to console stuff in raspberry and commented out the commandline stuff as well as modified the innittab getty things according to the interwebs, but i cannot get Pduino or comport to recognize the device when it's connected to the analog serial pins directly on the raspberry
You can send [comport] a [devices( message and it will print the list of
ports to the Pd console. You can send [comport] a [devicename /dev/ttyS0( message to open /dev/ttyS0. Pduino may have the port names hard-coded either in the Pd patch or the Arduino code, so you'd need to edit those.
Martin
?i sent that message to it ]devicename /dev/ttyS1/S0 and it does not exist so i tried to create it with mknod and it created the names in /dev but they are not accessible.
selecting device in the toggles in the pduino stuff only finds device 0
I am wondering if it's a linux issue because the only serial port at all is
serial 0 /dev/ttyAMA0
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020 ________________________________ From: Martin Peach chakekatzil@gmail.com Sent: Monday, September 21, 2015 11:04 AM To: Pagano, Patrick Cc: pd-list@iem.at Subject: Re: [PD] Pduino and arudino mini pro/raspi debian- Pduino or Comport?
On Mon, Sep 21, 2015 at 10:55 AM, Pagano, Patrick <pat@digitalworlds.ufl.edumailto:pat@digitalworlds.ufl.edu> wrote:
Hello
I want to use the arduino pro mini with pure data on the serial pins on the raspberry pi2 board for a project i am working on. My Arduino Uno works fine but i assume that is i assume because i am getting the serial data sent on the USB which seems to show up as
/dev/ttyAMA0 in raspberry pi debian
what i assume i need is it to work on /dev/ttyS0 /dev/ttyS1
I already turned off the serial to console stuff in raspberry and commented out the commandline stuff as well as modified the innittab getty things according to the interwebs, but i cannot get Pduino or comport to recognize the device when it's connected to the analog serial pins directly on the raspberry
You can send [comport] a [devices( message and it will print the list of ports to the Pd console. You can send [comport] a [devicename /dev/ttyS0( message to open /dev/ttyS0. Pduino may have the port names hard-coded either in the Pd patch or the Arduino code, so you'd need to edit those.
Martin
On 09/21/2015 05:17 PM, Pagano, Patrick wrote:
?i sent that message to it ]devicename /dev/ttyS1/S0 and it does not exist so i tried to create it with mknod and it created the names in /dev but they are not accessible.
mknod? this sounds like you are following advice from the 1990s. these days mknod is hardly ever needed: instead any devicefiles will be created on the fly by the resp. drivers.
selecting device in the toggles in the pduino stuff only finds device 0
I am wondering if it's a linux issue because the only serial port at all is
serial 0 /dev/ttyAMA0
a little bit of googling hints that /dev/ttyAMA0 is indeed the name for the serial interface on the GPIO ports - which afaiu is what you want.
so you just use that device.
then you need to get the permissions correct. check whether the device is already setup to allow group-members to write to it, and which group that is: $ ls -l /dev/ttyAMA0 crw-rw---- 1 root dialout 4, 67 Sep 3 16:12 /dev/ttyAMA0
and eventually add the user running Pd to that group: pd@raspbian $ sudo bash root@raspbian # adduser pd dialout
after that you only need to re-login as that user to let the new group membership have any effect.
gadsr IOhannes
I have done all of that for use with the ardunio uno, it's when the raspi2 is directly connected to the serial pins that it does not connect. I tested the device on mac and used the ALLINPUTS firmata and it works with a virtual serial created by FTDI just can't seem to talk to it with Linux debian running vanilla
comport works fine with the UNO
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020
From: Pd-list pd-list-bounces@mail.iem.at on behalf of IOhannes m zmölnig zmoelnig@iem.at Sent: Monday, September 21, 2015 1:47 PM To: pd-list@mail.iem.at Subject: Re: [PD] Pduino and arudino mini pro/raspi debian- Pduino or Comport?
On 09/21/2015 05:17 PM, Pagano, Patrick wrote:
?i sent that message to it ]devicename /dev/ttyS1/S0 and it does not exist so i tried to create it with mknod and it created the names in /dev but they are not accessible.
mknod? this sounds like you are following advice from the 1990s. these days mknod is hardly ever needed: instead any devicefiles will be created on the fly by the resp. drivers.
selecting device in the toggles in the pduino stuff only finds device 0
I am wondering if it's a linux issue because the only serial port at all is
serial 0 /dev/ttyAMA0
a little bit of googling hints that /dev/ttyAMA0 is indeed the name for the serial interface on the GPIO ports - which afaiu is what you want.
so you just use that device.
then you need to get the permissions correct. check whether the device is already setup to allow group-members to write to it, and which group that is: $ ls -l /dev/ttyAMA0 crw-rw---- 1 root dialout 4, 67 Sep 3 16:12 /dev/ttyAMA0
and eventually add the user running Pd to that group: pd@raspbian $ sudo bash root@raspbian # adduser pd dialout
after that you only need to re-login as that user to let the new group membership have any effect.
gadsr IOhannes
If connecting to serial port works when you run pd with sudo privileges, you will need to add your user is to the dialout group. See http://unix.stackexchange.com/questions/14354/read-write-to-a-serial-port-wi... for more info. HTH
On 9/21/2015 1:56 PM, Pagano, Patrick wrote:
I have done all of that for use with the ardunio uno, it's when the raspi2 is directly connected to the serial pins that it does not connect. I tested the device on mac and used the ALLINPUTS firmata and it works with a virtual serial created by FTDI just can't seem to talk to it with Linux debian running vanilla
comport works fine with the UNO
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020
From: Pd-list pd-list-bounces@mail.iem.at on behalf of IOhannes m zmölnig zmoelnig@iem.at Sent: Monday, September 21, 2015 1:47 PM To: pd-list@mail.iem.at Subject: Re: [PD] Pduino and arudino mini pro/raspi debian- Pduino or Comport?
On 09/21/2015 05:17 PM, Pagano, Patrick wrote:
?i sent that message to it ]devicename /dev/ttyS1/S0 and it does not exist so i tried to create it with mknod and it created the names in /dev but they are not accessible.
mknod? this sounds like you are following advice from the 1990s. these days mknod is hardly ever needed: instead any devicefiles will be created on the fly by the resp. drivers.
selecting device in the toggles in the pduino stuff only finds device 0
I am wondering if it's a linux issue because the only serial port at all is
serial 0 /dev/ttyAMA0
a little bit of googling hints that /dev/ttyAMA0 is indeed the name for the serial interface on the GPIO ports - which afaiu is what you want.
so you just use that device.
then you need to get the permissions correct. check whether the device is already setup to allow group-members to write to it, and which group that is: $ ls -l /dev/ttyAMA0 crw-rw---- 1 root dialout 4, 67 Sep 3 16:12 /dev/ttyAMA0
and eventually add the user running Pd to that group: pd@raspbian $ sudo bash root@raspbian # adduser pd dialout
after that you only need to re-login as that user to let the new group membership have any effect.
gadsr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Two more considerations: making sure you have the right firmware on the Arduino (sometimes it gets corrupt for seemingly no apparent reason and you need to reupload it), and finally making sure that it's getting enough power through RPi's USB port to provide stable operation.
On 9/21/2015 6:15 PM, Ivica Ico Bukvic wrote:
If connecting to serial port works when you run pd with sudo privileges, you will need to add your user is to the dialout group. See http://unix.stackexchange.com/questions/14354/read-write-to-a-serial-port-wi... for more info. HTH
On 9/21/2015 1:56 PM, Pagano, Patrick wrote:
I have done all of that for use with the ardunio uno, it's when the raspi2 is directly connected to the serial pins that it does not connect. I tested the device on mac and used the ALLINPUTS firmata and it works with a virtual serial created by FTDI just can't seem to talk to it with Linux debian running vanilla
comport works fine with the UNO
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020
From: Pd-list pd-list-bounces@mail.iem.at on behalf of IOhannes m zmölnig zmoelnig@iem.at Sent: Monday, September 21, 2015 1:47 PM To: pd-list@mail.iem.at Subject: Re: [PD] Pduino and arudino mini pro/raspi debian- Pduino or Comport?
On 09/21/2015 05:17 PM, Pagano, Patrick wrote:
?i sent that message to it ]devicename /dev/ttyS1/S0 and it does not exist so i tried to create it with mknod and it created the names in /dev but they are not accessible.
mknod? this sounds like you are following advice from the 1990s. these days mknod is hardly ever needed: instead any devicefiles will be created on the fly by the resp. drivers.
selecting device in the toggles in the pduino stuff only finds device 0
I am wondering if it's a linux issue because the only serial port at all is
serial 0 /dev/ttyAMA0
a little bit of googling hints that /dev/ttyAMA0 is indeed the name for the serial interface on the GPIO ports - which afaiu is what you want.
so you just use that device.
then you need to get the permissions correct. check whether the device is already setup to allow group-members to write to it, and which group that is: $ ls -l /dev/ttyAMA0 crw-rw---- 1 root dialout 4, 67 Sep 3 16:12 /dev/ttyAMA0
and eventually add the user running Pd to that group: pd@raspbian $ sudo bash root@raspbian # adduser pd dialout
after that you only need to re-login as that user to let the new group membership have any effect.
gadsr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
...and connect Tx to Rx and Rx to Tx and don't forget to connect the grounds together.
Martin
On Mon, Sep 21, 2015 at 6:16 PM, Ivica Ico Bukvic ico@vt.edu wrote:
Two more considerations: making sure you have the right firmware on the Arduino (sometimes it gets corrupt for seemingly no apparent reason and you need to reupload it), and finally making sure that it's getting enough power through RPi's USB port to provide stable operation.
On 9/21/2015 6:15 PM, Ivica Ico Bukvic wrote:
If connecting to serial port works when you run pd with sudo privileges, you will need to add your user is to the dialout group. See http://unix.stackexchange.com/questions/14354/read-write-to-a-serial-port-wi... for more info. HTH
On 9/21/2015 1:56 PM, Pagano, Patrick wrote:
I have done all of that for use with the ardunio uno, it's when the raspi2 is directly connected to the serial pins that it does not connect. I tested the device on mac and used the ALLINPUTS firmata and it works with a virtual serial created by FTDI just can't seem to talk to it with Linux debian running vanilla
comport works fine with the UNO
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020
From: Pd-list pd-list-bounces@mail.iem.at on behalf of IOhannes m zmölnig zmoelnig@iem.at Sent: Monday, September 21, 2015 1:47 PM To: pd-list@mail.iem.at Subject: Re: [PD] Pduino and arudino mini pro/raspi debian- Pduino or Comport?
On 09/21/2015 05:17 PM, Pagano, Patrick wrote:
?i sent that message to it ]devicename /dev/ttyS1/S0 and it does not exist so i tried to create it with mknod and it created the names in /dev but they are not accessible.
mknod? this sounds like you are following advice from the 1990s. these days mknod is hardly ever needed: instead any devicefiles will be created on the fly by the resp. drivers.
selecting device in the toggles in the pduino stuff only finds device 0
I am wondering if it's a linux issue because the only serial port at all is
serial 0 /dev/ttyAMA0
a little bit of googling hints that /dev/ttyAMA0 is indeed the name for
the serial interface on the GPIO ports - which afaiu is what you want.
so you just use that device.
then you need to get the permissions correct. check whether the device is already setup to allow group-members to write to it, and which group that is: $ ls -l /dev/ttyAMA0 crw-rw---- 1 root dialout 4, 67 Sep 3 16:12 /dev/ttyAMA0
and eventually add the user running Pd to that group: pd@raspbian $ sudo bash root@raspbian # adduser pd dialout
after that you only need to re-login as that user to let the new group membership have any effect.
gadsr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Ivica Ico Bukvic, D.M.A. Associate Professor Computer Music ICAT Senior Fellow Director -- DISIS, L2Ork Virginia Tech School of Performing Arts – 0141 Blacksburg, VA 24061 (540) 231-6139 ico@vt.edu www.performingarts.vt.edu disis.icat.vt.edu l2ork.icat.vt.edu ico.bukvic.net
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Funny I was just working on this this morning looking for a simple solution for my students.
I found this http://colinzyskowski.com/?page_id=503 to access analogRead.
It kind of works. The third pot interferes with the other two and when I modified to code to add a fourth it interfers or doesn't work at all. Seems to be something to do with the map function Arduino code not workign correctly because when I poll [comport] with [print] each analogRead seems to be on it's own "channel". I can't figure out how to separate them any better than using [split] with there mapped values (not great). I tried [unpack] and [route] but neither of these separate the data streams.
On the hardware side I just have each 10k pot wiper connected it's own analog pin on the Uno and each pot is powered and grounded from the Uno via the rails on my breadboard. I'm guessing but adding in some resistors might stabilise the circuit a bit, I don't know if this would help with the interference or not.
As mentioned above I also had to add a dialout to access the serial port as outlined by Rinzwind here http://askubuntu.com/questions/58119/changing-permissions-on-serial-port
On Tue, Sep 22, 2015 at 8:45 AM, Martin Peach chakekatzil@gmail.com wrote:
...and connect Tx to Rx and Rx to Tx and don't forget to connect the grounds together.
Martin
On Mon, Sep 21, 2015 at 6:16 PM, Ivica Ico Bukvic ico@vt.edu wrote:
Two more considerations: making sure you have the right firmware on the Arduino (sometimes it gets corrupt for seemingly no apparent reason and you need to reupload it), and finally making sure that it's getting enough power through RPi's USB port to provide stable operation.
On 9/21/2015 6:15 PM, Ivica Ico Bukvic wrote:
If connecting to serial port works when you run pd with sudo privileges, you will need to add your user is to the dialout group. See http://unix.stackexchange.com/questions/14354/read-write-to-a-serial-port-wi... for more info. HTH
On 9/21/2015 1:56 PM, Pagano, Patrick wrote:
I have done all of that for use with the ardunio uno, it's when the raspi2 is directly connected to the serial pins that it does not connect. I tested the device on mac and used the ALLINPUTS firmata and it works with a virtual serial created by FTDI just can't seem to talk to it with Linux debian running vanilla
comport works fine with the UNO
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020
From: Pd-list pd-list-bounces@mail.iem.at on behalf of IOhannes m zmölnig zmoelnig@iem.at Sent: Monday, September 21, 2015 1:47 PM To: pd-list@mail.iem.at Subject: Re: [PD] Pduino and arudino mini pro/raspi debian- Pduino or Comport?
On 09/21/2015 05:17 PM, Pagano, Patrick wrote:
?i sent that message to it ]devicename /dev/ttyS1/S0 and it does not exist so i tried to create it with mknod and it created the names in /dev but they are not accessible.
mknod? this sounds like you are following advice from the 1990s. these days mknod is hardly ever needed: instead any devicefiles will be created on the fly by the resp. drivers.
selecting device in the toggles in the pduino stuff only finds device 0
I am wondering if it's a linux issue because the only serial port at all is
serial 0 /dev/ttyAMA0
a little bit of googling hints that /dev/ttyAMA0 is indeed the name for
the serial interface on the GPIO ports - which afaiu is what you want.
so you just use that device.
then you need to get the permissions correct. check whether the device is already setup to allow group-members to write to it, and which group that is: $ ls -l /dev/ttyAMA0 crw-rw---- 1 root dialout 4, 67 Sep 3 16:12 /dev/ttyAMA0
and eventually add the user running Pd to that group: pd@raspbian $ sudo bash root@raspbian # adduser pd dialout
after that you only need to re-login as that user to let the new group membership have any effect.
gadsr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Ivica Ico Bukvic, D.M.A. Associate Professor Computer Music ICAT Senior Fellow Director -- DISIS, L2Ork Virginia Tech School of Performing Arts – 0141 Blacksburg, VA 24061 (540) 231-6139 ico@vt.edu www.performingarts.vt.edu disis.icat.vt.edu l2ork.icat.vt.edu ico.bukvic.net
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
I could not get the arduino pro mini to work with just comport no matter how i tried, so i installed "Pduino" and after installing
pd-mapping, pd-pure, pd-moocow [pdstring] i got it to work
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020 ________________________________ From: Pd-list pd-list-bounces@mail.iem.at on behalf of Richie Cyngler glitchpop@gmail.com Sent: Monday, September 21, 2015 10:35 PM To: Martin Peach Cc: pd-list@mail.iem.at; IOhannes m zmölnig Subject: Re: [PD] Pduino and arudino mini pro/raspi debian- Pduino or Comport?
Funny I was just working on this this morning looking for a simple solution for my students.
I found this http://colinzyskowski.com/?page_id=503 to access analogRead.
It kind of works. The third pot interferes with the other two and when I modified to code to add a fourth it interfers or doesn't work at all. Seems to be something to do with the map function Arduino code not workign correctly because when I poll [comport] with [print] each analogRead seems to be on it's own "channel". I can't figure out how to separate them any better than using [split] with there mapped values (not great). I tried [unpack] and [route] but neither of these separate the data streams.
On the hardware side I just have each 10k pot wiper connected it's own analog pin on the Uno and each pot is powered and grounded from the Uno via the rails on my breadboard. I'm guessing but adding in some resistors might stabilise the circuit a bit, I don't know if this would help with the interference or not.
As mentioned above I also had to add a dialout to access the serial port as outlined by Rinzwind here http://askubuntu.com/questions/58119/changing-permissions-on-serial-port
On Tue, Sep 22, 2015 at 8:45 AM, Martin Peach <chakekatzil@gmail.commailto:chakekatzil@gmail.com> wrote: ...and connect Tx to Rx and Rx to Tx and don't forget to connect the grounds together.
Martin
On Mon, Sep 21, 2015 at 6:16 PM, Ivica Ico Bukvic <ico@vt.edumailto:ico@vt.edu> wrote: Two more considerations: making sure you have the right firmware on the Arduino (sometimes it gets corrupt for seemingly no apparent reason and you need to reupload it), and finally making sure that it's getting enough power through RPi's USB port to provide stable operation.
On 9/21/2015 6:15 PM, Ivica Ico Bukvic wrote: If connecting to serial port works when you run pd with sudo privileges, you will need to add your user is to the dialout group. See http://unix.stackexchange.com/questions/14354/read-write-to-a-serial-port-wi... for more info. HTH
On 9/21/2015 1:56 PM, Pagano, Patrick wrote: I have done all of that for use with the ardunio uno, it's when the raspi2 is directly connected to the serial pins that it does not connect. I tested the device on mac and used the ALLINPUTS firmata and it works with a virtual serial created by FTDI just can't seem to talk to it with Linux debian running vanilla
comport works fine with the UNO
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020tel:%28352%29294-2020
From: Pd-list <pd-list-bounces@mail.iem.atmailto:pd-list-bounces@mail.iem.at> on behalf of IOhannes m zmölnig <zmoelnig@iem.atmailto:zmoelnig@iem.at> Sent: Monday, September 21, 2015 1:47 PM To: pd-list@mail.iem.atmailto:pd-list@mail.iem.at Subject: Re: [PD] Pduino and arudino mini pro/raspi debian- Pduino or Comport?
On 09/21/2015 05:17 PM, Pagano, Patrick wrote: ?i sent that message to it ]devicename /dev/ttyS1/S0 and it does not exist so i tried to create it with mknod and it created the names in /dev but they are not accessible. mknod? this sounds like you are following advice from the 1990s. these days mknod is hardly ever needed: instead any devicefiles will be created on the fly by the resp. drivers.
selecting device in the toggles in the pduino stuff only finds device 0
I am wondering if it's a linux issue because the only serial port at all is
serial 0 /dev/ttyAMA0
a little bit of googling hints that /dev/ttyAMA0 is indeed the name for the serial interface on the GPIO ports - which afaiu is what you want.
so you just use that device.
then you need to get the permissions correct. check whether the device is already setup to allow group-members to write to it, and which group that is: $ ls -l /dev/ttyAMA0 crw-rw---- 1 root dialout 4, 67 Sep 3 16:12 /dev/ttyAMA0
and eventually add the user running Pd to that group: pd@raspbian $ sudo bash root@raspbian # adduser pd dialout
after that you only need to re-login as that user to let the new group membership have any effect.
gadsr IOhannes
Pd-list@lists.iem.atmailto:Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-- Ivica Ico Bukvic, D.M.A. Associate Professor Computer Music ICAT Senior Fellow Director -- DISIS, L2Ork Virginia Tech School of Performing Arts - 0141 Blacksburg, VA 24061 (540) 231-6139tel:%28540%29%20231-6139 ico@vt.edumailto:ico@vt.edu www.performingarts.vt.eduhttp://www.performingarts.vt.edu disis.icat.vt.eduhttp://disis.icat.vt.edu l2ork.icat.vt.eduhttp://l2ork.icat.vt.edu ico.bukvic.nethttp://ico.bukvic.net
Pd-list@lists.iem.atmailto:Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.atmailto:Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
--
www.glitchpop.comhttp://www.glitchpop.com
On 2015-09-22 04:47, Pagano, Patrick wrote:
I could not get the arduino pro mini to work with just comport no matter how i tried, so i installed "Pduino" and [...] got it to work.
i'm not sure i understand what you are trying to say here. "Pduino" is really just an *abstraction* built around [comport], so does this mean that the problem was simply your patch?
after installing pd-mapping, pd-pure, pd-moocow [pdstring]
btw, Debian now also has a package "pd-pduino" (but only since recently), which will pull in all needed packages.
gfmser IOhannes
i am saying i was using raspberry pi with an arduino uno and the comport help patch was working fine when i switched to the arduino pro mini that patch was not importing the values from the device in a readable format, when i switched to the pduino patch for whatever reason the values were showing up. So i assume it has to do with the patches and perhaps the pduino patch is more suited for the newer arduinos. I will try the pd-pduino stuff tonight
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020
From: Pd-list pd-list-bounces@mail.iem.at on behalf of IOhannes m zmoelnig zmoelnig@iem.at Sent: Tuesday, September 22, 2015 3:26 AM To: pd-list@mail.iem.at Subject: Re: [PD] Pduino and arudino mini pro/raspi debian- Pduino or Comport?
On 2015-09-22 04:47, Pagano, Patrick wrote:
I could not get the arduino pro mini to work with just comport no matter how i tried, so i installed "Pduino" and [...] got it to work.
i'm not sure i understand what you are trying to say here. "Pduino" is really just an *abstraction* built around [comport], so does this mean that the problem was simply your patch?
after installing pd-mapping, pd-pure, pd-moocow [pdstring]
btw, Debian now also has a package "pd-pduino" (but only since recently), which will pull in all needed packages.
gfmser IOhannes
i am trying to apt-get that pd-pduino and it cannot locate it is there a repo i need to update?
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020
From: Pd-list pd-list-bounces@mail.iem.at on behalf of Pagano, Patrick pat@digitalworlds.ufl.edu Sent: Tuesday, September 22, 2015 1:56 PM To: IOhannes m zmoelnig; pd-list@mail.iem.at Subject: Re: [PD] Pduino and arudino mini pro/raspi debian- Pduino or Comport?
i am saying i was using raspberry pi with an arduino uno and the comport help patch was working fine when i switched to the arduino pro mini that patch was not importing the values from the device in a readable format, when i switched to the pduino patch for whatever reason the values were showing up. So i assume it has to do with the patches and perhaps the pduino patch is more suited for the newer arduinos. I will try the pd-pduino stuff tonight
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020
From: Pd-list pd-list-bounces@mail.iem.at on behalf of IOhannes m zmoelnig zmoelnig@iem.at Sent: Tuesday, September 22, 2015 3:26 AM To: pd-list@mail.iem.at Subject: Re: [PD] Pduino and arudino mini pro/raspi debian- Pduino or Comport?
On 2015-09-22 04:47, Pagano, Patrick wrote:
I could not get the arduino pro mini to work with just comport no matter how i tried, so i installed "Pduino" and [...] got it to work.
i'm not sure i understand what you are trying to say here. "Pduino" is really just an *abstraction* built around [comport], so does this mean that the problem was simply your patch?
after installing pd-mapping, pd-pure, pd-moocow [pdstring]
btw, Debian now also has a package "pd-pduino" (but only since recently), which will pull in all needed packages.
gfmser IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 09/22/2015 07:58 PM, Pagano, Patrick wrote:
i am trying to apt-get that pd-pduino and it cannot locate it is there a repo i need to update?
when i said "but only since recently", i really meant it: the package has entered Debian/unstable on august 26, and has migrated to Debian/testing (aka stretch) two weeks ago.
but you don't need it, as the package won't provide anything you don't already have. i was just doing some advertisments on recent progress in Debian land.
fmdars IOhannes
On Mon, Sep 21, 2015 at 10:35 PM, Richie Cyngler glitchpop@gmail.com wrote:
Funny I was just working on this this morning looking for a simple solution for my students.
I found this http://colinzyskowski.com/?page_id=503 to access analogRead.
It kind of works. The third pot interferes with the other two and when I modified to code to add a fourth it interfers or doesn't work at all. Seems to be something to do with the map function Arduino code not workign correctly because when I poll [comport] with [print] each analogRead seems to be on it's own "channel". I can't figure out how to separate them any better than using [split] with there mapped values (not great). I tried [unpack] and [route] but neither of these separate the data streams.
That method loses a lot of resolution. Also the reason the third pot interferes is that the data is sent as bytes and values greater than 255 can't be represented as bytes. One way to do it is to use a value (like 0 ) that never occurs in the data stream and use that as the marker for the start of a packet. If the data is zero, just add 1. On the Pd side, make a counter that increments with each character and resets when the character is zero. Pack the count with each received character and then route them by number into the correct slot.
A better method to delimit serial packets is SLIP encoding, which uses a special character as the end of a packet and escape characters in case the special character (or the escape character) occurs in the data.
On the hardware side I just have each 10k pot wiper connected it's own analog pin on the Uno and each pot is powered and grounded from the Uno via the rails on my breadboard. I'm guessing but adding in some resistors might stabilise the circuit a bit, I don't know if this would help with the interference or not.
A small capacitor to ground might help with electrical interference from long wires but I think your interference is software-based.
Martin
Another alternative--if you need Arduino for connecting GPIO (including software PWM for analog out) and potentially analog inputs, you may be better off getting Modern Device LOP shield for RPi (I worked with it on RPi 1 rev. B model, and according to online RPi2 specs it should be also compatible with RPi2 GPIO) which gives you 10 digital I/O that can be also used as PWM analog outs, and 8 analog ins, with each connector offering ground and 3.3V pin right next to it, plus a 5V lead if you need one straight off the GPIO pin and 4 optional microswitches linked with 4 GPIOs.
https://moderndevice.com/product/lots-of-pots-lop-board-for-raspberry-pi/ (the $23 NOP version comes without the pots, assuming you don't need the pots to begin with)
Best,
Ico
On 9/21/2015 6:45 PM, Martin Peach wrote:
...and connect Tx to Rx and Rx to Tx and don't forget to connect the grounds together.
Martin
On Mon, Sep 21, 2015 at 6:16 PM, Ivica Ico Bukvic <ico@vt.edu mailto:ico@vt.edu> wrote:
Two more considerations: making sure you have the right firmware on the Arduino (sometimes it gets corrupt for seemingly no apparent reason and you need to reupload it), and finally making sure that it's getting enough power through RPi's USB port to provide stable operation. On 9/21/2015 6:15 PM, Ivica Ico Bukvic wrote: If connecting to serial port works when you run pd with sudo privileges, you will need to add your user is to the dialout group. See http://unix.stackexchange.com/questions/14354/read-write-to-a-serial-port-without-root for more info. HTH On 9/21/2015 1:56 PM, Pagano, Patrick wrote: I have done all of that for use with the ardunio uno, it's when the raspi2 is directly connected to the serial pins that it does not connect. I tested the device on mac and used the ALLINPUTS firmata and it works with a virtual serial created by FTDI just can't seem to talk to it with Linux debian running vanilla comport works fine with the UNO Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020 <tel:%28352%29294-2020> ________________________________________ From: Pd-list <pd-list-bounces@mail.iem.at <mailto:pd-list-bounces@mail.iem.at>> on behalf of IOhannes m zmölnig <zmoelnig@iem.at <mailto:zmoelnig@iem.at>> Sent: Monday, September 21, 2015 1:47 PM To: pd-list@mail.iem.at <mailto:pd-list@mail.iem.at> Subject: Re: [PD] Pduino and arudino mini pro/raspi debian- Pduino or Comport? On 09/21/2015 05:17 PM, Pagano, Patrick wrote: ?i sent that message to it ]devicename /dev/ttyS1/S0 and it does not exist so i tried to create it with mknod and it created the names in /dev but they are not accessible. mknod? this sounds like you are following advice from the 1990s. these days mknod is hardly ever needed: instead any devicefiles will be created on the fly by the resp. drivers. selecting device in the toggles in the pduino stuff only finds device 0 I am wondering if it's a linux issue because the only serial port at all is serial 0 /dev/ttyAMA0 a little bit of googling hints that /dev/ttyAMA0 is indeed the name for the serial interface on the GPIO ports - which afaiu is what you want. so you just use that device. then you need to get the permissions correct. check whether the device is already setup to allow group-members to write to it, and which group that is: $ ls -l /dev/ttyAMA0 crw-rw---- 1 root dialout 4, 67 Sep 3 16:12 /dev/ttyAMA0 and eventually add the user running Pd to that group: pd@raspbian $ sudo bash root@raspbian # adduser pd dialout after that you only need to re-login as that user to let the new group membership have any effect. gadsr IOhannes _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list -- Ivica Ico Bukvic, D.M.A. Associate Professor Computer Music ICAT Senior Fellow Director -- DISIS, L2Ork Virginia Tech School of Performing Arts – 0141 Blacksburg, VA 24061 (540) 231-6139 <tel:%28540%29%20231-6139> ico@vt.edu <mailto:ico@vt.edu> www.performingarts.vt.edu <http://www.performingarts.vt.edu> disis.icat.vt.edu <http://disis.icat.vt.edu> l2ork.icat.vt.edu <http://l2ork.icat.vt.edu> ico.bukvic.net <http://ico.bukvic.net> _______________________________________________ Pd-list@lists.iem.at <mailto:Pd-list@lists.iem.at> mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Ivica Ico Bukvic -
Martin Peach -
Pagano, Patrick -
Richie Cyngler