Beaglebone connectivity using Linx

[adithya76]

Hi,

Following the tutorials, I was able to install labview and linx. I had developed a program, and it was running quite well. But whenever I turn my computer off and on, beaglebone fails to connect.

In the sense, I'm able to connect to the beaglebone through the Linx target configuration and I can even ssh using putty. But when I go into my project and try and run the VI on BBB, it regularly pops up the error saying "Failed to connect to Target". I have vigourosly searched the entire linx forum for such an issue. And have tried everything that has been suggested but to no avail. My question is how can it show connectivity in Target configuration, but fail to connect inside the project when I try to run the VI?

I am seeing another peculiar event too. Sometimes, if I reinstall the software using Target Configuration, BBB connects perfectly temporarily. And it disconnects pretty soon. But the process of reinstalling also does not happen regularly. It often fails and the message that says to post in the forum pops up. I have viewed the log and wasn't able to find anything substantial. I have tried manual installation and it fails too. This irregularity in connection is something that bothers me. I am not able to figure out a pattern too. When it connects, it is perfect.

 

[JColvin]

Hi @adithya76,

How are connected to your BBB? Via USB cable or are you connected to the BBB over ethernet? I've also asked another engineer more familiar with LINX to see if they have some thoughts on this as well.

Thanks,
JColvin

[adithya76]

Hi @JColvin

Thanks for your reply. I am connecting through USB.

After I posted earlier, I found that LabVIEW runtime fails to install for some reason (which had been successful previously and I was able to deploy the code BBB).

 

This is the log

OS Version: 8.4
CPU:
Systemd Version:
Has Internet Access: True
Device Type: BeagleBone Black

Connecting to target...
Successfully connected to target.
Successfully connected to the target.
Target configuration updated.
OS Version: 8.4
CPU:
Systemd Version:
Has Internet Access: True
Device Type: BeagleBone Black

No led_aging.sh scritp on target.
Adding MakerHub feed...
MakerHub Feed Already Exists
Updating package index.  This may take over 30 seconds depending on your internet speed...
Ign http://feeds.labviewmakerhub.com binary/ InRelease
Hit http://repos.rcn-ee.com jessie InRelease
Ign http://feeds.labviewmakerhub.com binary/ Release.gpg
Get:1 http://security.debian.org jessie/updates InRelease [44.9 kB]
Ign http://security.debian.org jessie/updates InRelease
Ign http://feeds.labviewmakerhub.com binary/ Release
Ign http://repos.rcn-ee.com jessie InRelease
Installing LabVIEW...
Reading package lists...
Checking target status...

Installation failed.  If this is the first time the installation has failed try again.  If this error persists search, then post on the LabVIEW MakerHub forumsat labviewmakerhub.com/forums/linx.
Target configuration updated.
OS Version: 8.4
CPU:
Systemd Version:
Has Internet Access: True
Device Type: BeagleBone Black

 

It looks like things are unraveling which I am not able to figure out why.

[LazerBoi64]

Bumping this thread...

I am seeing this exact same problem.  As of today, I have just gotten my BeagleBone Black to successfully install the LabView runtime v14.1-11.  My BBB has been updated to all the current software, and SSH root access has been re-enabled.  I can connect via SSH/PuTTY through either the onboard USB or network without issue.  I can connect to the BBB through the LabView demo project Blink and it remains connected right up until the very end of the deployment progress.  It disconnects right after I close the progress window, so it has gone through all (apparent) steps needed.  Even after it errors out here, I can still connect via SSH and directly without problem (from what I can tell).  But to get LV to connect again, I have to reboot the BBB.  Would definitely like to figure this out!!

[JColvin]

Hi @LazerBoi64,

I responded to your other thread here.

Thanks,
JColvin