Thank you Jonwitts for getting back to me. Yes I am using a Pi3..
So the PureData file I am using controls using open sound then via a different PD file (called o.io.slipserial.pd) converts to TTY data to communicate with the teensy, which to me looks to output to “devicename /dev/tty.usbmodem12341, pollintervall 1” (although I am not sure. But if it helps I am following the control setup at: https://github.com/DropletKitchen/pumpsn17
flexible version at the bottom of the page.)
The Teensy is plugged into a USB port. But in the Pure Data control front end (which should feed into the o.io.slipserial.pd file), I can only really choose between /ttyAMA0 /ttyACM0 or /ttyS0.
I understand that the Pi 3 has changed from previous raspberry Pis so /dev/ttyAMA0 is Bluetooth and /dev/ttyS0 is the GPIO serial port. As per discussion here https://spellfoundry.com/2016/05/29/con ... ding-pi-3/
Arduino apparently expects the serial communications to be on /dev/ttyS0 and for me when I plug in my teensy via the USB this seems to work and I can program it using the raspberry pi. But when it comes to controlling the teensy on the raspberry Pi via Pure Data is when I come into problems.
Sorry if this seems very disjointed, I’m trying to learn as I go here, and am likely missing something very obvious. I feel I do need to go back and learn some of the basics, but am stuck for time at the moment so would love to be able to get this working soon. I’m wondering if the problems may be related to differences between Rasberry pi 3 vs 2 and Jessie vs wheezy. Since these Pure data files and the teensy code is apparently tried and tested, and should work as is.
Any light on the matter would be much appreciated.