If I didn't mention I'm actually using a Teensy 3.0 not an arduino. Read on pjrc.com that the teensy runs at full USB speed all the time unlike arduino. So that seems like the comport speed should be irrelevant?

In any case yesterday I turned the rip and teensy on and pd was reading from it immediately every time I opened a patch. Maybe it worked itself out? I'm using ccrma satellite which is a raspbian distro. I'll check the user permissions also

On Nov 12, 2013, at 2:38 AM, "kubriel" <kubriel@servus.at> wrote:

baud rate _should_ be the same in your arduino code and in your comport object, otherwise you get messed up characters.
i dont have rpi here, but i didnt noticed any chenges between running comport on rpi, or standard pc.
when you send [devices( you usually get list of connected serial devices - arduinos with usb2serial and com ports if you have.

also check, ig your user is in uucp group, i think it is necessary,
and maybe also dialout group can be important. probably it depense if you are using debian fedora or arch on this rpi

kub


On 11.11.2013 18:13, Alexandros Drymonitis wrote:
Are you sure the baud rate you set to [comport] is the same as the code you load on your Arduino? That could be a problem..
If you send the [devices( message to [comport] what do you get in the console?


On Mon, Nov 11, 2013 at 11:19 AM, kubriel <kubriel@servus.at> wrote:

It won?t receive data.
Hi! i was using RPi plenty of times headless without any problems with comport in pd, but usually running armarch linux.
but i was not using device name, but device nr, like [comport 0 9600] for uno, or [comport 4 9600] for duemilanove.

kub

--
http://kubriel.servus.at


_______________________________________________
Pd-list@iem.at mailing list
UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list


-- 
http://kubriel.servus.at