Deployment Error When Deploying Labview to Raspberry Pi through LINX

[amey191]

I have one problem in same domain i want to connect raspberry pi 3 B to lab view and switch on led connected to ras pi but i got error like this 

labview 2014 sp1 

PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian

[billko]

---

@amey191 wrote:

I have one problem in same domain i want to connect raspberry pi 3 B to lab view and switch on led connected to ras pi but i got error like this 

labview 2014 sp1 

PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian

---

What's up with the "not genuine" Windows?  Anyway, I just found it easier to assign a static IP address to it and address it that way.  Are you aware of this forum?  You might find better solutions there.

[amey191]

hey thanks for reply i have tried that after setting static IP in rasp pi terminal after reboot i verified that by typing hostname -I i get the changed IP but when i ping that in cmd in windows it is showing like this 

[billko]

Looks like you're not connected to a DHCP server.

[amey191]

u r right but now i have enable it still it is showing same error as 1st one

[billko]

What IP address is your PI?  What IP address is your computer?  It's strange you should be using the 169.254.x.x, as this is reserved for Automatic Private IP address, which Network cards will give themselves when no DHCP server is present, so you can just plug two computers together and get them talking to each other.

[rolfk]

You have a basic network problem and as long as that is not solved LabVIEW will not be able to do anything.

Could you show us the output of running "ipconfig /all" in a command line window? This will show what network addresses your computer uses. The fact that the Raspi defaulted to using an address from the Automatic Private IP Addressing range indicates that there is no DHCP server available on your network. But that also means that your Windows computer also gets an address from that range for the network card connected to the Raspi.

And unless both adapters work in the same subnet, they can't communicate with each other. So when you change the Raspi to use an explicit address from the 192.168/16 private address range, you also have to make sure to change the network card in Windows to do the same although it of course can't be exactly the same address but needs to be slightly different. After that your ping command should succeed and then you can go back into your LabVIEW project and change the IP address in the properties for your Raspi to match what you assigned to the Raspi.