• Content Count

  • Joined

  • Last visited

  1. @JColvin, thanks for getting back to me. Through trial and error I've found that version 8.4 dated 2016-05-13 was the only one I could get to work reliably with LINX. Again, this was downloaded from and the simple blink example has been running without any hiccups. I haven't gone to anything more complex yet as I them moved on to do the same experiment with my Pi 3B+. Unfortunately that was an utter failure. Versions of Raspbian from that date simply would not boot with the newer hardware. I guess if I need to go the Pi route, I'll have to try a Pi 2B instead. Thanks again!
  2. LOL yeppers! I've been struggling to dredge up my Unix experience from 30 years ago and apply it to this board as well as a RPi 3B+ in an effort to get them to run LabView. In the process, I had flashed the BBB's eMMC with the most current software only to find it broke LINX. I then back-rev'd the software to 8.6 2016-11-06 which seems to work so far. But, I'd like to know what it originally shipped with in order to fill out the revision continuum. -Scott
  3. What is the current version of Debian that is shipping in BeagleBone Blacks from Digilent? I've been messing around with one I purchased last month and have flashed the eMMC numerous times and don't know what I started with. I tried asking customer service and they said it was too technical for them. Thanks!
  4. @JColvin, thanks for the Raspbian link. It's too bad a direct link to the archives isn't available on the main download page. I did go back to the BBB download page, ,scrolled down a bit and found the whole history. From my tests yesterday, 8.6 is the latest version that actually allows the LabView blink vi to work. I didn't have to mess with anything else and the deployment worked just like in the tutorial videos. My goal for today is to do the same with the Pi. Definitely have to say that through all of my mistakes, I am learning something new. I'm sure I'll be back!
  5. @JColvin Thanks for responding. Disappointed in the answer, but it is what it is. Can you or someone else point me in a direction to go regarding back-reving both the Pi and the BBB to known viable software? From what I have read, it seems the Pi 3B+'s hardware breaks the old software and there were specific files that had to be moved from the old software to the new (or vice versa) to get around the hardware. Hardware incompatibility should not be a problem with the BBB, because that design hasn't apparently changed for a few years? This style of computing is pretty foreign to this old dog, so if anyone can be of help, please use small words and lots of steps! The last time I dabbled in this style of operating system was back in the days I was running my Commodore Amiga (anyone remember that? 😉) and its flavor of UNIX. Thanks again!
  6. Bumping this thread hopefully for some resolution... I'm seeing this exact same behavior and cannot determine how to fix it. I am using an RPi 3B+ with the current (2019-04-10) Raspbian version. I am trying to simply run the Blink (Advanced) demo vi found in the LINX examples. This behavior is also the same if I'm using a BeagleBone Black with the current Debian version. I can add either board to a LabView project containing the modified (as per ) vi. I can connect to either board by right-clicking on it in the project and it shows as connected. I then try to run the vi. A window showing the deployment progress streams through the vi deployment that has been described throughout this thread. It ends with "Deployment completed successfully". When I close the deployment window (I have previously unchecked the "Close on successful completion" box), that window closes and is replaced with an error saying "Warning: Connection to the target (Raspberry Pi 3B+) has been lost". The Pi (or BBB) is definitely disconnected when inspected in the project explorer window. Reconnection attempts are met with errors "Failed to connect to the target". I can only reconnect after rebooting the Pi (or BBB). I have gotten to this point by working through all of the other errors described in this thread. I see this behavior either when the boards are connected via a network switch to my computer or directly to the USB port on the BBB. Also, when LabView cannot connect to the board(s), I can still communicate via direct connection or via SSH using a terminal program such as PuTTY. If any information other than what has already been provided in this thread is needed, I will be happy to oblige. Thanks for reading!
  7. Thanks for the link! Believe me, I have scoured it looking for help. Unfortunately that forum seems to be dead, because I joined but can't post questions, nor contact administrators asking to become a full member with posting privileges. I can read to my heart's content, but posting new questions is impossible. What a waste.
  8. 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!!
  9. Greetings! Sticking my toe into the BeagleBone Black and Raspberry Pi worlds and wanting to interface them with LabView. I've been using LabView for a few years now but the BBB and Pi (and Linux) are all new territories. I am coming up with a LOT of newbie questions and will be posting them shortly! Be warned! 🙂