Showing results for 
Search instead for 
Did you mean: 

Can't connect to raspberry pi by TCP/IP

Hello everyone


I want to use a raspberry pi 2 as a cheap external digital output module for switching relays.
I installed LINX and set up my Raspberry Pi 2 like the tutorials explain.

Also I use the recommended Labview 2013 32bit SP1 version.

The pi is found at the LINX target configuration menu.
When I create a new project, I can add it the raspberry pi a target in my project and connect to it, everything fine.
I also can run VIs, like the examples, on it without problems when putting the VI's into the Pi tree (instead of My Computer), so connection and setup of the raspberry should be fine.
But when I move the VI to My Computer and change the source of LINX to TCP, I got error 5003

LabVIEW was unable to connect to the LINX device using the following settings:

Interface: TCP/IP
IP Address: ( like set up in the LINX configuration)
Port: 3363

I tried port 3363 and 44300 because I found these ports when searching for a solution, but I can't connect.
I enabled TCP in the Pi settings -> VI Server, also I added the IP of my desktop to VI Server -> machine access and to User access as well, but still can't connect.
Is this an access problem, or wrong port number, or what can I do to connect to the Pi by TCP?

The pi is pingable with this IP, also I can connect by putty to it.

I can't run the VI local on the Pi by moving it to the raspberry in the project tree because I have to use other VISA devices as well.

Also I guess the communication by ethernet or serial is implemented in LINX so it can actually be used.


Thanks in advance

0 Kudos
Message 1 of 9

Is the PC's IP address in the same IP range?

0 Kudos
Message 2 of 9

Yes, the PC's IP address is static.

 Also the same subnet mask.

0 Kudos
Message 3 of 9

Firewall (temporarily) off?

0 Kudos
Message 4 of 9
(4,094 Views) sure sounds like the IP address of a router.  Are you sure you should be setting the PI to this address?

(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 5 of 9

Pi and desktop are only wired with one ethernet cable, no routers / switches involved.

Both devices have static IP configured as shown above.

Pi is pingable and can be accessed by SSH by putty.

0 Kudos
Message 6 of 9

Are you just trying to use a Pi because it is the hardware you have on hand?  Because an Arduino is probably a more reliable, and cheap solution for a digital out device.  LINX, and LIFA support talking to an Arduino over USB, and there are several relay shields made that snap right on the top.  I only suggest this because I have no experience with Pi and LINX.

0 Kudos
Message 7 of 9

I want to use the Pi because I tested it with local settings, then I build up the whole settings around it, thinking it will run all nice, and now I put too much time in it to start again.

Next time maybe I will try the arduino.

0 Kudos
Message 8 of 9
0 Kudos
Message 9 of 9