Ok, so i got the [tcpsend]to work. i connected it at the point where
the comport would usually get info. it is connected to the ip
xxx.xxx.xxx.xxx 3000 and when i turn the patch on, it sends the
appropriate data to the arduino fio/rn-xv over wifi. the problem now is
that the [tcpreceive 3000] isnt receiving anything. from what i have
read, tcpsen and tcp recieve work on the same port so if that port is an
ip address, what would be the prefered means of getting the data from
the fio?
I am experimenting with port forwarding on my router right now. Is
there anything you might know of that i could/should try, that might
sort the port conflict out?
cheers,
Onyx
On Mon, Nov 26, 2012 at 4:33 PM,
onyx@onyx-ashanti.com
<mailto:
onyxashanti@gmail.com>
> wrote:
I am going to investigate the updated wifly, wiflyserial and
ethernet libraries onto the sketch for the rn-xv/arduino. this
should allow me create a "serial socket" or something, once i grasp
all that stuff a bit better. tcpclient, in place of [comport]
connects and shows data sent but nothing is happening in pd or the
arduino fio. i have begun toying with udpsend/udprecieve but that
isnt working because i am sure that i havent connected the i/o in a
manner that provides [comport] replacement functionality. i should
have some results from that shortly. from what i have read, the way
udp works might be better and if i can get one of the above
libraries to see it, maybe my problem will be solved. i will let
you what i come with in a few hours
On Sun, Nov 25, 2012 at 10:59 PM, Martin Peach
<mailto:
onyx@onyx-ashanti.com> wrote:
if comport could accept an ip port argument, as well as a
serial port
argument, all would be lovely and nothing would have to
change. it
would simply recieve itsport from the ip. is there anything
like this?
In pd-extended there are [udpsend] and [udpreceive] as well as
[tcpclient] and [tcpserver] that can be used instead of [comport].
Probably you'll need to add a [import net] to get them.
Martin
--