Problems with OscP5 TCP client server and Android mode

rick206

Problems with OscP5 TCP client server and Android mode

in Contributed Library Questions • 25 days ago

Has anybody used the OscP5 tcpclientserver in Android mode? I have a sketch that communicates with a remote server serial device using socat as an interface on the server. My two way connection is stable with when using udp client mode, but I do have issues now and again with dropped packets. I'd like to try tcp. When I switch my sketch over to tcp mode using

tcpclient=new OscP5(this,"192.168.0.15",1234,OscP5.TCP);

The sketch compiles and initializes correctly, but the app aborts on the first sent OSC message. The message is received on the server end and parsed correctly, but my android app stops. In debugging mode, I get the following error:

FATAL EXCEPTION: Thread-1768
java.lang.OutOfMemoryError
    at netP5.Bytes.toByteArray(Unknown Source)
    at netP5.AbstractTcpClient.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:856)

Any ideas why this is? The problem doesn't seem to be with Socat or the server.

Replies(2)

cageehv

Re: Problems with OscP5 TCP client server and Android mode

25 days ago

I use OscP5 with my Android using UDP and that works fine!

What is socat? Don't know that app...

rick206

Re: Problems with OscP5 TCP client server and Android mode

24 days ago

Socat is a unix utility for bidirectional data transfer and redirection. It is used for lot of different things, but I'm using it to listen to a port on a server and redirect input to/from a USB device. Here is info on socat: http://www.dest-unreach.org/socat/doc/socat.html

After a little more troubleshooting, I find that my problem is not really related to Android at all. Something similar happens in Java mode. Here is some stripped down code:

import oscP5.*;
import netP5.*;
OscP5 op5;
void setup() {
op5=new OscP5(this,"192.168.0.15",1234, OscP5.TCP);
}
void draw() {
background(0);
}
void mousePressed() {
OscBundle bndl = new OscBundle();
OscMessage msg = new OscMessage("/TEST");
msg.add("text");
msg.add(100);
bndl.add(msg);
op5.send(bndl);
}

This does in fact send the test OSC bundle to my remote server:port. The initial message is redirected by socat to the configured USB port, and my target device correctly parses the message, but the sketch then crashes, be it in java or android. Here is the java error that is returned:

java.lang.NullPointerException
    at processing.mode.java.runner.Runner.findException(Runner.java:947)
    at processing.mode.java.runner.Runner.reportException(Runner.java:892)
    at processing.mode.java.runner.Runner.exceptionEvent(Runner.java:818)
    at processing.mode.java.runner.Runner$2.run(Runner.java:707)

Anybody have an idea? Like I said, this same code works when configured for udp transmission, but I'd prefer a handshaking protocol. Obviously the handshaking requirement must be causing my problems. Am I missing something in my processing sketch to get a tcp client to work?