Contact Login
  • Home
    • About
  • Learn
    • LabVIEW
      • Basics
    • LINX
      • BeagleBone Black and Raspberry Pi
      • Digilent Physical Computing Kit
      • Sparkfun Inventors Kit
      • All LINX Tutorials
      • Reference
    • Kinect One
  • Libraries
    • LabVIEW
    • Android / iOS
    • LINX - Arduino, Raspberry Pi and BeagleBone Black
    • LEGO Mindstorms
    • Leap Motion
    • Kinect One
    • Nest Thermostat
    • PS4 Controller
    • Xbox One Controller
    • See All Libraries
  • Projects
    • Share Your Project
    • See All Projects
  • Forums
  • Get LabVIEW
  • Board index ‹ General ‹ LabVIEW Programming
  • Change font size
  • Print view
  • FAQ
  • Register
  • Login

Setting up TCP fails

LabVIEW Programming Help And Discussions
Post a reply
2 posts • Page 1 of 1

Setting up TCP fails

Postby B. Hackert » Wed Oct 18, 2017 5:18 am

Hello everyone
I installed LINX and set up my Raspberry Pi 2.
I can add it as a target in my project and connect to it, everything fine.
I also can run VIs on it without problems when putting them into the RPi 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: 192.168.0.1
Port: 3363

I tried port 3363 and 44300 but can't connect.
I enabled TCP in the Pi settings -> VI Server, also I added my IP 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?

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.
B. Hackert
 
Posts: 1
Joined: Wed Oct 18, 2017 4:41 am
Top

Re: Setting up TCP fails

Postby labuseful » Tue Aug 21, 2018 6:29 pm

If using Windows, turn OFF the firewall entirely. See if this is the problem. Also, TCP/IP error 62, or 54 is a fatal TCP error, error 56 is timeout - which is normal, just wait until a message is received.
labuseful
 
Posts: 2
Joined: Sun Dec 25, 2016 12:55 am
Top


Post a reply
2 posts • Page 1 of 1

Return to LabVIEW Programming

Who is online

Users browsing this forum: Google [Bot] and 3 guests

  • Board index
  • The team • Delete all board cookies • All times are UTC - 6 hours [ DST ]
LabView Hacker LabVIEW MakerHub
Driven by LabVIEW users. Created by NI.