Leaderboard

Hi Guys; Now that the Arduino Compatible Compiler for LabVIEW has been launched for a few months, it is time to tackle the next challenge; having LabVIEW code deployed to my favorite dessert: Raspberry Pi. http://www.tsxperts.com/labviewforraspberrypi/ My personal favorite thing to do lately has been to watch LabVIEW GUIs running on a Raspberry Pi connected to a small monitor. We got a cool demo of a Vibration Monitoring and Alarm system using an Arduino and a Raspberry Pi; both programmed in LabVIEW. If you are making to NIWeek this year, make sure to stop by our booth to check it out. Once the NIWeek madness is out of the way I will post a video of it. Cheers Filipe

Back on the third page of the discussion is CAR #313508.

Regarding your original problem with TCP loopback, take a look at: https://lavag.org/topic/14609-issues-tcp-ing-with-a-c-program-on-the-same-computer/ I was having what sounds like a very similar problem to yours. Bottom line from NI was that there was some issue with the TCP stack in LabVIEW when running on Windows 7 and doing TCP loopback. That was in LV11. By LV13 it still wasn't fixed. It does seem to be working in LV15, however. Cat

I was wading through an old SCC repo today, and stumbled upon some of our old tools - the ones that existed before VI Analyzer, execution trace toolkits, complexity metrics, Requirements Gateway, et al. Here's a few screenshots for those that have been in the LabVIEW world long enough to remember the VISTA offerings from V I Engineering, in the days of old - enjoy a trip down memory lane!

Oh, it was modular enough, it just wasn't aligned enough with our core businesses anymore (the screenshots I shared were of components, there was a top-level framework and UI experience that tied everything together). And a lot of the features had appeared in others' tools, so we left it where it was. LOL, yeah I was wondering who'd be the first to call that out. So yes, the project in this example was, indeed, 98% reuse. Only because I threw together a bunch on internal reuse library and OpenG VIs on an empty block diagram Nice work - I like this! Interesting you mention that: I've had people ask me in the past about what level of complexity and/or how many GOBs that they should be aiming for - which misses the point entirely. They're relative, and that's why I insisted in having the histograms in there - you're not looking for absolute values, you're looking for out-liers. And yes, some of these out-liers can be logically explained away. Broken VIs et al are quantitative attributes, complexity et al are qualitative. Right. Mined-from-previous-projects is one thing, formally-released-components is another. But yes, they're still both reuse. Open source, I doubt it. But... if someone were to release a framework (like ShaunR has), we could probably release a plug-in or two...

Yeah some of us are dumb enough to actually host our first crapware. To be fair I think that is probably my second crapware attempt since my first attempt is gone forever. Once I discovered LAVA I realized that would be a better home for cleaned up code so I haven't put anything new on there other than the tray launcher which has EXEs and installers that I don't think LAVA would like.