Hobbyist Toolkit

cancel
Showing results for 
Search instead for 
Did you mean: 

LVMH repository down? 404 error installing RPI firmware

Solved!
Go to solution

I have a fresh piece of 8GB Pi and I am unable to put the firmware on it. Looks like the server is down or perhaps the path has changed. 

Is the data available anywhere else? I mean, it's Friday night and this is the big date I've been waiting for all week.

 

Snippet from log:


Ign:1 http://feeds.labviewmakerhub.com/debian binary/ InRelease
Err:2 http://feeds.labviewmakerhub.com/debian binary/ Release
404 Not Found [IP: 54.86.245.246 80]
Hit:3 https://deb.nodesource.com/node_16.x bullseye InRelease
Hit:4 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:5 http://archive.raspberrypi.org/debian bullseye InRelease
Reading package lists...
Installing LabVIEW...

0 Kudos
Message 1 of 12
(1,832 Views)

I probably should have posted this at Makerhub, huh?

0 Kudos
Message 2 of 12
(1,829 Views)

This is the home for the package formerly known as linx/makerhub now. I can definitely get to http://feeds.labviewmakerhub.com/debian/binary/ in the browser so not sure what else is in your system that's giving the 404. If I nslookup the domain, that IP comes up and I have no problem hitting it.

 

Is other internet access from the Pi working fine?

~ The wizard formerly known as DerrickB ~
Gradatim Ferociter
0 Kudos
Message 3 of 12
(1,802 Views)

Hi

This happens when I try to install the firmware on the target.

 

Maybe it would help if I posted the whole log:

 

Connecting to target...
Successfully connected to target.
Successfully connected to the target.
Target configuration updated.
OS Version: 11.6
CPU: BCM2835
Systemd Version:
Has Internet Access: True
Device Type: Raspberry Pi 2 B

Connecting to target...
Successfully connected to target.
Successfully connected to the target.
Target configuration updated.
OS Version: 11.6
CPU: BCM2835
Systemd Version:
Has Internet Access: True
Device Type: Raspberry Pi 2 B

blacklist spi-bcm2708is not present.dtparam=spi=on already exists.i2c-dev already exists.i2c-bcm2708
blacklist i2c-bcm2708is not present.dtparam=i2c1=on
dtparam=i2c_arm=on already exists.
Adding MakerHub feed...
MakerHub Feed Already Exists
Updating package index. This may take over 30 seconds depending on your internet speed...
Ign:1 http://feeds.labviewmakerhub.com/debian binary/ InRelease
Err:2 http://feeds.labviewmakerhub.com/debian binary/ Release
404 Not Found [IP: 54.86.245.246 80]
Hit:3 https://deb.nodesource.com/node_16.x bullseye InRelease
Get:4 http://raspbian.raspberrypi.org/raspbian bullseye InRelease [15.0 kB]
Hit:5 http://archive.raspberrypi.org/debian bullseye InRelease
Reading package lists...
Installing LabVIEW...
Reading package lists...
Building dependency tree...
Reading state information...
Rebooting Target...
Successfully connected to target.
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: 11.6
CPU: BCM2835
Systemd Version:
Has Internet Access: True
Device Type: Raspberry Pi 2 B

0 Kudos
Message 4 of 12
(1,757 Views)
Solution
Accepted by mikeslaney@gmail.com

I didn't have anything else to do today so I tried removing and reinstalling the makerhub toolkit and all the other linx stuff I've installed through ViPM.

Nothin.

Then I removed and installed through the NI Package manager and BLAMMO! back in business.

I'm using the 2023Q3 Pro dev system

0 Kudos
Message 5 of 12
(1,739 Views)

Sounds like you made the traditional mishap explained already in other posts. The Linx Toolkit from the VIPM installer list is in almost all versions NOT the right thing to install when you have LabVIEW 2020 or newer. You need the Hobbyist Toolkit instead and make sure that no incarnation of any Linx Toolkit gets installed alongside.

 

Or install the Community Edition which already comes with the right version of the Hobbyist Toolkit pre installed (and really does not like if you try to install on top if it either the Linx nor the Hobbyist Toolkit).

Rolf Kalbermatter
My Blog
0 Kudos
Message 6 of 12
(1,730 Views)

Minor detail  🤣

And now  the 2023 professional version is available and I'm doing a full sanitize and install on my personal and work LV installations. Pretty exciting.

 

Semi related rant...

Between Digilent, MCC, Ni, Linx itself, and all the other half hearted parties,  combined with the full-hearted, supportive parties such as yourself, all coupled to the apparent lack of interest and support from The Company..... It's Madness.

But I can't let go. 

I mean LV on the RPI et al., was supposed to happen. TS Experts compiler was supposed to happen.

Linx happened because somebody saw the value while he or she saw support for the very idea die on the vine.

I don't know who it was or what they did but I'd love to hear the real story and thank them.

What killed it? "The Comany" and their relationship with Digilent? Was Digilent acquired to squash Linx? It's too small for them to worry about. Was it a lack of interest from users?

It could have been stellar. 

Stellar.

And I still can't let go.

0 Kudos
Message 7 of 12
(1,669 Views)

You get your timeline mixed a lot here.

 

Digilent was acquired by NI in January 2013, at a time NI still had high ambitions to win the education market with its products, to get them into the hands of young engineers who then will surely want to use them when they enter the professional world. Pretty good thinking actually. 🙂

In the same time frame someone at NI got enough support from management to actually work on something called Linx and make it available as an open source project. So far so good. He later moved to Digilent as it seemed more in place under that umbrella than under the slowly changing NI.

 

But at about that same time NI management also got alarmed because their standard double digit yearly sales growth seemed to start flattening out. They hired some consultants who analyzed the whole situation and came with a lengthy report of what was the problem.

 

The short version of it was: You have acquired MCC, which has acquired Data Translation and some other subsidiaries and that is pretty much what the whole data acquisition market is. There is little competition left to acquire and little market share that you don't already own. You need to go boldly for new frontiers.

 

One would have been to go after markets held by traditional T&M companies like Keithley, Fluke, Tektronix, and maybe even Keysight. That most likely seemed to troublesome and possibly also ridden with anti-competitions concerns.

 

Instead they did go for another frontier, maybe not as boldly and definitely not as loudly as NI marketing used to do other things, by going to invest into building complete test and measurement systems for semiconductor, transportation and later EV and energy systems. Compared to the possible market they can get in these areas, the traditional DAQ boxes, and PXI/PCI plugin cards are just peanuts. And with NI software always having been a means to sell their hardware, and not to make money in itself, these also were more and more marginalized.

 

That's what basically happened. There is still a large investment into NI cRIO, PXI and LabVIEW by many big guns in the industry, so NI can't just pull the plug or they might get bulldozered by companies who have a lot more money on hand than NI is worth.

 

And about Linx itself. Yes it could have been great, for people tinkering with stuff. But they are typically not interested to spend $ 1000 for stuff, and for a $ 1000 sale a company like NI does not even call you back.

Rolf Kalbermatter
My Blog
0 Kudos
Message 8 of 12
(1,661 Views)

Hi, Rolf. I am really interested in this timeline issue. if I understand well your words, NI is changing (has changed) its course. I am working in an educational institution and seems that NI has lost its interest in education. As you say, there is still a large investment into NI cRIO, PXI and LabVIEW by many big guns in the industry. But, are the basic and more modest applications of LV under risks? Will be those new big applications the absolute priority  ? 

0 Kudos
Message 9 of 12
(1,627 Views)

We have gone way off the first two tangents....

Who was that gut John Harvey "And that's the rest of the story"

Ha!! Data Translation! I remember their gear! I liked it but replaced it all with Fieldpoint for more I/O.

 

That was EXACTLY the kind of thing I wanted to learn. 

Really, ROlf, thank you so much for that history. Quite a series of events. It sounds like you were knee deep in the whole thing. 

 

data translation. Wow.

 

 

0 Kudos
Message 10 of 12
(1,636 Views)