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? <div>
<br></div><div>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?</div><div><br></div><div>cheers,</div><div>
<br></div><div>Onyx<br><br><div class="gmail_quote">On Mon, Nov 26, 2012 at 4:33 PM, <a href="mailto:onyx@onyx-ashanti.com">onyx@onyx-ashanti.com</a> <span dir="ltr"><<a href="mailto:onyxashanti@gmail.com" target="_blank">onyxashanti@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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<div>
<div><div class="h5">
<br><br><div class="gmail_quote">On Sun, Nov 25, 2012 at 10:59 PM, Martin Peach <span dir="ltr"><<a href="mailto:martin.peach@sympatico.ca" target="_blank">martin.peach@sympatico.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On 2012-11-25 15:51, <a href="mailto:onyx@onyx-ashanti.com" target="_blank">onyx@onyx-ashanti.com</a> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
if comport could accept an ip port argument, as well as a serial port<br>
argument, all would be lovely and nothing would have to change. it<br>
would simply recieve itsport from the ip. is there anything like this?<br>
<br>
</blockquote>
<br></div>
In pd-extended there are [udpsend] and [udpreceive] as well as [tcpclient] and [tcpserver] that can be used instead of [comport].<br>
Probably you'll need to add a [import net] to get them.<span><font color="#888888"><br>
<br>
Martin<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div><div><a href="http://www.onyx-ashanti.com" target="_blank">www.onyx-ashanti.com</a></div>
<br></div><a title="phone number" style="color:rgb(0,0,63);background-color:rgb(255,255,191)"><br>
</a><br>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div><a href="http://www.onyx-ashanti.com" target="_blank">www.onyx-ashanti.com</a></div><br></div><a title="phone number" style="color:rgb(0,0,63);background-color:rgb(255,255,191)"><br>
</a><br>
</div>