@whale-av I think you are right on the packet size being the teensy talking back, since the data to the teensy (and hence pump speeds) all seem to be correct. Thanks again David. You have been a great help.

@whale-av Thank you David! The Pi is talking to the teensy!!! Your help and persistence with my problem is really appreciated! Like you suggested I added [import mrpeach] as an object in the Flexible3or4PumpsGOP file and it is now talking! My stepper motors step, and my pumps are working!. And it seems to work on both extended and L2Ork. Yet to test whether they are running at the correct speed as per the controls though.
I do however still get some errors saying [import mrpeach] …couldn’t create. Maybe I added it wrong, should I not be adding it as an object? Also when I play with the control sliders it reports that “packet size is not a multiple of 4 bytes: dropping packet” And then sometimes “unpackOSC: dataafteralignedstring: incorrectly padded string” and “Bad message name string:Dropping entire message”.
I’ll have to check physically if my pumps are running at the correct flow rates to see if this is effecting performance, but sadly this will be after the weekend.
I’m so happy that I have them communicating now though. Thank you. It's been a long time and I was beginning to loose hope.
It is communicating with the teensy through ttyACM0 at the moment. I had previously done some swapping around of ttyS0 and AMA0 on the pi, since apparently on the Pi3 the Bluetooth steals the AMA0, when I did this ttyS0 became available as a port. But before trying your fix I changed it back to as the Pi was and now only the ACM0 and AMA0 are available (Yes the devices button was very helpful).

Thanks David, gave this a go, but still no luck. Looking at the errors on Pd i'm thinking it may be a problem with the different .pd files communicating with each other. If I open PD L2Ork on the Raspberry pi I initially get an error saying “audio I/0 error…”. If I open the PD extended program instead, I used to get the same error but then since typing:

sudo apt install alsa-oss
sudo modprobe snd-pcm-oss

in the command to create a /dev/dsp device as per the advice of another raspberry pi user. Not sure why there is the difference with Pd extended and Pd L2Ork but I don't think this is where my problem is.
If I actually open the Pure Data files that I need, in either of the Pd program versions I get:
UnpackOSC
… couldn’t create
routeOSC /derection
… couldn’t create
And then a bunch of other could not create warnings for all the OSC parameters. It seems like the OSC elements are not working. The PD L2Ork also identifies that the helper file o.io.slipserial.pd 5 0 4 0 (bng->loadbang) connection failed
Suggesting the communication between the “loadbang” control in the PD file and the helper file. although I am assured the PD files work. I’m trying to get in touch with the creators (to no avail). But if anyone here has any helpful suggestions I am all ears.

@whale-av thanks for your reply. It looks like the [slipserial.pd] isn't finding the teensy. It's output looks to be addressed to:
/dev/tty.usbmodem12341 , pollintervall 1
when I look for my USB teensy using lsusb i find it here:
Bus 001 Device 006: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial
although I dont know how this would translate into an address to give in the [slipserial.pd]. Doesn't it need to be a dev/tty... format?

Thanks again for your reply, entered those commands and got the permissions. But looking into it more, it seems that permissions might not be my problem. Since it looks like I have the wrong output. It’s trying to communicate with the teensy through a pin out (/dev/ttyS0) rather than a USB port (like ttyUSB0). The problem is I’m not quite sure where or how to change where the OSC data is sent and received.

Thanks for the suggestion Th8a. Since i am working as the user "pi" I am already a member of the dialout group. .. Just to update, I have now managed to install PD L2Ork. just using the same instructions as i mentioned before (so I don't know what happened first few times round). But I still get the same problems of not communicating with the right port, and also a number of errors stating "could not create" unpackOSC and a number of routeOSC elements

@alexandros Thanks for your reply. I'm using extended as the PD file i am using requires a number of externals for it to work. PD-L2ORK would be great, but after a number of attempts, I can’t seem to get it working on raspbian Jessie, using step 3 on http://l2ork.music.vt.edu/main/make-your-own-l2ork/software/raspberry-pi/ (since I am not running it headless as I have a screen mouse and keyboard for the pi) the install seems to run smoothly but then after there is no trace of the program anywhere on my raspberry pi, just the download file sitting there. So I ended up settling for extended instead.
I should have the udev rules, since I installed teensyduino using the script here https://github.com/cmcmurrough/cse2100/blob/master/teensy/install_teensyduino.sh which also installs the udev rules.
Might the problems be with identifying/permissions for the correct output? In my case this is a USB to the teensy. I’m a newbie to both raspberry pi and PD, so don’t know if I need to/ how to pre-configure these (if I need to that is).
Thanks

Hi,

I’m new to raspberry pi and am trying to run Pure data on it to control a teensy 3.2 using Open Sound Control which in turn controls some stepper motors for a pump just like here https://github.com/DropletKitchen/pumpsn17 (using the teensy code and PD files provided at the end of the page). I’ve finally managed to install PD extended on my raspberry pi 3 (Raspbian Jessie). But I don’t think PD is able to use the USB to communicate with the teensy, since if I try to run the PD file, PD gives me the error “could not open device /dev/ttyS0: failure(13): Permission denied. Could someone help me please to get PD communicating with OSC through my USB?

Also when I open PD I get this message
“/dev/dsp (read/write): No such file or directory
(now will try write-only…)
/dev/dsp (writeonly): No such file or directory
/dev/dsp (read only): No such file or directory”
and
“Audio I/O stuck… closing audio”
Do I need to do some further configuration to get Pure Data running properly?
Like I mentioned I am very new to using the raspberry pi so any help would be appreciated and please do explain as if I were an idiot, that would be very helpful.
Thank you