On 2012-11-25 15:51, 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
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 martin.peach@sympatico.cawrote:
On 2012-11-25 15:51, 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
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 < 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 martin.peach@sympatico.cawrote:
On 2012-11-25 15:51, 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
-- www.onyx-ashanti.com
Better to use [tcpclient] / [tcpserver] or [udpreceive] / [udpsend]. A single [tcpserver] or [tcpclient] can send and receive.
Martin
On 2012-11-30 16:45, onyx@onyx-ashanti.com wrote:
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:onyx@onyx-ashanti.com <onyxashanti@gmail.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 <martin.peach@sympatico.ca <mailto:martin.peach@sympatico.ca>> wrote: On 2012-11-25 15:51, onyx@onyx-ashanti.com <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 -- www.onyx-ashanti.com <http://www.onyx-ashanti.com>-- www.onyx-ashanti.com http://www.onyx-ashanti.com
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Fri, Nov 30, 2012 at 11:03 PM, Martin Peach martin.peach@sympatico.cawrote:
Better to use [tcpclient] / [tcpserver] or [udpreceive] / [udpsend]. A single [tcpserver] or [tcpclient] can send and receive.
ok, i am experimenting with that now, per your suggestions (thank you, by the way). the real issues now are that i am learning how to set up ports and i only just discovered what udp is, this week. i am going to toy around with UDP settings and ports and i will report my findings.
cheers!
Onyx
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:onyx@onyx-ashanti.com <onyxashanti@gmail.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 <martin.peach@sympatico.ca <mailto:martin.peach@**sympatico.ca<martin.peach@sympatico.ca>>>wrote:
On 2012-11-25 15:51, onyx@onyx-ashanti.com <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 -- www.onyx-ashanti.com <http://www.onyx-ashanti.com>-- www.onyx-ashanti.com http://www.onyx-ashanti.com
______________________________**_________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/** listinfo/pd-list http://lists.puredata.info/listinfo/pd-list
so, late last week i gave away my systems xbee radios in hopes that it would spur me into making the rn-xv's work. i was able to get them working using udp and properly configured ports. [udpsend] transmits to teh arduino but the issue was getting communication from the arduino/rn-xv side. at first the [udpreceive] didnt work, but i fiddled with it until it was sending blocks of numbers which i could see had a sequence so i tried to send that block and it didnt work so i read the data coming out of comport using one xbee radio i have left and saw that it was coming out as a stream, so i put [list-drip-quick2], which i found online in a forum thread some of you guys had, underneath the udpreceive object and viola! it works! not only that, but i increased the baud rate for firmata (no other changes neccessary)and the uart of the rn-xv to 115200 and set a flush timer to shoot those packets over to the computer every 5ms, which works beautifully. the playable resolution is wildly faster in both directions. i havent used it in a live performance situation so i cant give it top marks yet, but so far it is everything i had hoped the xbees would be, but better in everyway.
i just wanted to update you on the progress of this issue, and thank everyone for your help! i will be posting a more detailed blog post later.
onyx
On Sat, Dec 1, 2012 at 4:51 PM, onyx@onyx-ashanti.com <onyxashanti@gmail.com
wrote:
On Fri, Nov 30, 2012 at 11:03 PM, Martin Peach martin.peach@sympatico.cawrote:
Better to use [tcpclient] / [tcpserver] or [udpreceive] / [udpsend]. A single [tcpserver] or [tcpclient] can send and receive.
ok, i am experimenting with that now, per your suggestions (thank you, by the way). the real issues now are that i am learning how to set up ports and i only just discovered what udp is, this week. i am going to toy around with UDP settings and ports and i will report my findings.
cheers!
Onyx
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:onyx@onyx-ashanti.com <onyxashanti@gmail.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 <martin.peach@sympatico.ca <mailto:martin.peach@**sympatico.ca<martin.peach@sympatico.ca>>>wrote:
On 2012-11-25 15:51, onyx@onyx-ashanti.com <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 -- www.onyx-ashanti.com <http://www.onyx-ashanti.com>-- www.onyx-ashanti.com http://www.onyx-ashanti.com
______________________________**_________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/** listinfo/pd-list http://lists.puredata.info/listinfo/pd-list
-- www.onyx-ashanti.com
-
Martin Peach -
onyx＠onyx-ashanti.com