Jordan Kuehn

Hooovah, I appreciate this toolkit and the work you've done to make it. I have a common problem that I run into and eventually just have to bit the bullet and roll my own solution. When streaming large datasets to disk I have to use the TDMS Advanced vis to get it to avoid a memory leak. It is even worse with waveforms, though I would like to be able to write those directly you can't with the Advanced vis. So I wind up stripping the t0 and dt off and saving as waveform components, flushing the file to apply them, configuring block sizes, etc. Could this library be adapted to use the more performant vis, with some preconditions, say that all subsequent writes must be identical in size/composition, so that I can stream waveforms to disk? I attempted to use your size based file writer and ran into the same memory leaks I encountered when using the regular tdms files, described here.

Anyone have any news if NI will be bringing this conference back? I see the Austin Convention center has a listing for May 24-26, 2022.

I was unaware of this bug until today, but I figured it might be appreciated as a heads up in this sub-forum. There is an issue with LINX (or whatever it is now) and LV2021. The link below has detailed instructions for configuring a fresh pi as well as updating one that is already set up for 2020. https://forums.ni.com/t5/Hobbyist-Toolkit/Labview-CE-2020-connects-to-raspberry-but-CE-2021-does-not/td-p/4198964

What if you created an open source tool kit via CE and then someone else profited utilizing it? Arguably the best use case for CE to built out the community code could get legally murky? I am not a lawyer, just an engineer.

I agree with you here. Community edition of LV is one step forward, while SaaS is a few steps back in terms of pursuing market adoption. Python is ubiquitous because it is free and people can copy/paste code bits they find on sourceforge together to get something to work while playing around with a Pi at home/university. Then they find those skills actually have value in the market.

At risk of derailing this topic I've seen you make many arguments as such, but they rely on the assumption that the user is utilizing an HTML "View" and can plug and play LV or Python or whatever behind it. In your workflow I 100% believe that is the case. However, I do not think that is common. Certainly I will admit my knowledge of python driven UIs is lacking. However, flawed and outdated as LV UIs are, they are still an advantage from my perspective. I have dabbled with your approach and do see the positives there, but it's not dissimilar to having to program a host application for an RT target and adding an additional layer to every application.

Gotcha. That's with the pricing structure as it stands today right? Theoretically they could meet in the middle or change things in other ways as that lock-in rate starts expiring for *lots* of users all at once.

I think we said the same thing here, albeit mine was far less comprehensive. Are there other caveats other than the switch getting flipped off on the software when you stop paying? I'm not diminishing that one, but in terms of practical impact if you currently maintain an SSP there is no real change.

It seems to me that if you already maintain SSP it's not a big change aside from the point above should you choose to stop and no longer have access to LV.

You may have better luck on ni's forums. Especially if your IT needs an answer from NI staff.

No. But you could host a web app and then view it from within the pi in a browser. Here is an example application you may be able to use for inspiration. Credit Sam Sharp I think. https://www.mediamongrels.com/democracybot-rpi-linx-websockets-nxg-webvis/

I think if you can reach an NTP server you’ll be ok if sub-second accuracy is tolerable. If so, see my comment on this KB article. The whole thing is worth going through and there are a few different ways to go about it. I think mine combines them all including disabling NI-Sync. Note that this is only available on version 20.1 or higher. This has bit me since I have many systems with 20.0. https://forums.ni.com/t5/Example-Code/Installing-and-Configuring-NTP-on-NI-Linux-Real-Time-Devices/tac-p/4165930/highlight/true#M14787

I agree with all of this.

If they do not do this they need to beef up their offerings. Right now the 9047 is the most powerful cRIO platform (-40C) and we are reaching limitations with it, but the only more powerful platform is a PXI controller. Lettings us put Linux RT on hardware we source would also help with the current lead times that are stretching out past 6 months for some of this hardware.

How is your disk usage? I've had systems lock up when filling the drive.

Could you expand on this? Are you seeing poor service regarding support requests? Or something else?

This website is old, but has some information. https://www.labviewmakerhub.com/doku.php?id=libraries:linx:start You might also find some useful things here: https://forums.ni.com/t5/Hobbyist-Toolkit/bd-p/linx-toolkit?profile.language=en

When using GigE make sure your network adapter supports jumbo frames. Or at least be aware that this is necessary at times. https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019Lj9SAE&l=en-US

This may be of some help: https://zone.ni.com/reference/en-XX/help/370281AG-01/nivisionlvbasics/acquire_or_read_an_image/

What chip is it? There are several libraries out there for some common hardware. This link may be helpful. https://www.vipm.io/package/mediamongrels_lib_linx_raspberry_pi_addons/

We have had some similar issues. In general we could get in touch within a few days of pestering, but occasionally we escalated to the (3rd Party) sales rep as well. Support has certainly taken a noticeable hit in the last couple years.

It took NI decades to release a community version of LV and IMO (and I've heard echoed often) it has really hurt the language and wide adoption. Hopefully this shift in mindset can carry over into other products like TestStand. Or opening FPGA up to non NI hardware as another example.

I used toggl a lot myself when consulting. I did not find the timer useful, but at the end of the day I would try to make entries in round numbers (.5 hour resolution) of how much time was spent per project and a short summary of what item(s) I worked on. It was fantastic when submitting invoices for hourly work. No questions asked, very transparent, and it made producing the invoice quite easy.

A 9039 may be of interest, but I don’t think the 9038. Thank you for checking. Still looking for 9047s.

I was looking for one of your old tools the other day and I couldn't find it. Now I stumble across this several months after you posted the "trick". You are evil! 😆