Problem w/ loopback client

[hyperritual]

I am trying to use FlowStone's Client component to read OSC messages from an Emotiv EPOC via Mind Your OSCs, but am having some trouble.

Mind Your OSCs is configured for 127.0.0.1:7400. Here is my test client configuration:

capture.png (127.65 KiB) Viewed 33519 times

When I leave IP blank, I can send/receive messages to/from the Server component (which defaults to 192.168.2.3), but nothing is retrieved from Mind Your OSCs. If I specify IP 127.0.0.1, the client log returns, "Could not connect to server."

I have verified that Mind Your OSCs is transmitting over 127.0.0.1:7400, by creating a UPD client in Processing.

Any ideas? I would love to create and share a working FlowStone module for the EPOC. I have successfully created "mind-controlled" robots using EPOC + OSC + Processing + Arduino. I could create a server outside of FS, to forward OSC messages to FS over another IP, but for obvious reasons I prefer to connect directly between FS and Mind Your OSCs.

Thank you,
Joshua

[sal]

hello,
standing on my tests, the client and server modules can only communicate between them, so communication with any other kind of network or server will fail.
Sal

[hyperritual]

Sal, thank you for your reply. I was able to create a TCP client in Processing and successfully receive data from FlowStone's Server component across port 7400 on the component's default IP of 192.168.2.3. Still not sure why I cannot connect FS's Client component to 127.0.0.1, or if there is another way to accomplish what I want to do...

[sal]

it's because the client component can only communicate with the flowstone's server component which automatically gets the ip address of your ethernet connection, so if it doesn't find a flowstone server on 127.0.0.1, it fails.
Sal

[hyperritual]

Thanks again, Sal. Hopefully, this is something FS developers will address. If the client listens only to the FS server, and there is no way (that I can see) to change the server's IP from that of my router, then I find no functionality in having an IP string as an input to the client component. If I add another server component to the schematic, it uses the same IP.

Am I looking at this the wrong way, and there is another/better way to accomplish what I am trying to (i.e. receive UDP data from a server outside of FS)?

[Embedded]

Sal this is not correct?
I have used the FlowStone Client and Server to communicate with all sorts of different IP hardware. The FlowStone modules use the TCP and UDP standards so it should work!

[sal]

it would be interesting to see some example of your successfull network communication with networks not using flowstone server.
Sal