...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-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

________________________________________
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