(My first guess for this would be to look at former students from the mechanical or biomedical departments at the local Universities, but the feedback I have had so far on that is that the top students from UC and OU typically get recruited quickly and relocate...and that perhaps this would better fit someone with a computer science background...)

The work involves data acquisition, signal analysis and motion control which are things LabVIEW-developers often have experience with, and hearing about this recruitment challenge I first thought about JKI e.g., but the company in question wants to  recruit someone to work in-house, be located in Cincinnati (no relocation package)...and implement some heavy lifting using CUDA/OptiX or similar, so it is not a LabVIEW or consultancy job.

Any tips (apart from hiring a local recruitment firm...), or someone who knows any suitable candidates (again - US citizens only)?

Once upon a time in a land far, far away, I was a LabVIEW Partner (don't think it was Partner in those days, but that's what it's called now).

As my professional activities drifted in a different direction, I've not done any LabVIEW in a while, but it's aways been near and dear to my heart.

Life brought retirement about 2 1/2 years ago, and I've been dabbling with a number of things in my "spare" time.

One of which is Home Assistant. Somehow, somewhy, HA has exploded as the thing in home automation.

It's support of devices is amazing. There are some 10,000 "integrations" available and more being developed every day.

The downside is the "programming" as they call it.

Oi.

I'm not a programmer, and don't play one on TV, but I'm conversant in a plethora of programming tools, including LabVIEW.

HA purports to be able to do everything via it's UI, but the ugly truth is, the really useful screen elements (they call them cards) don't have UI connections. It's all YAML. (Yet Another Markdown Language)

OMG. This stuff hurts my head in a spectacularly large and significant way.

There are two "segments" to HA, Dashboards and Automations. Automations I can "kinda" do, but Dashboards are a nine line cluster.

It took me over a week to build a simple UI with 5 screen elements to control the volume on three audio devices in my house. And that was with the help of some kind soul on the forum that took pity on me. Without his help, it simply wouldn't have happened. I could have crafted this in 20 minutes with LabVIEW, or python.

So, what I have been doing is some automation stuff for the house. Due to my lack of knowledge of the ins and outs of automations, and the documentation is 12-24 months behind schedule at any point, I've had to break up what is effectively a state machine into about 10 discrete automations. And as you would expect, I'm running into issues with them interacting with each other.

So, I've put together a textual descriptive of what I want to do and have been investigating the best way to do this in HA. What virtually everyone uses for these types of "flows" as they call them is NODE-Red. There is much to like about NODE-Red, but the first thing it reminded me of was LabVIEW. So, for laughs, this morning I went looking, and lo and behold found the Community Edition, and a version to run on Linux as a cherry on top. I'm migrating all my activities that I can away from Windows, as none of the computers in my house will run Windows 11.

So, while I wait for NI to figure out why my e-mail is not verified, I have to ask:

Has anyone had any interaction with HA? Any thoughts about interaction between LV and HA?

Take care

All my LabVIEW code is in SVN.

I need to use git to manage the Python modules that are called from LabVIEW. My group had a pretty simple process and I squeaked by.

Now the modules are in a repository where all sorts of black/flake8 and pull request activity are making me crazy.

I'm spending way too much time googling "how to" with git and end up breaking or losing my Python changes. Everyone tells me "Its easy if I use PyCharm" but now I just end up googling "how to git in PyCharm" instead (with worse results).

My git expertise is almost zero and I use git from the command line under Windows.

Unfortunately my company uses named user licensing and when I start LV as my admin user, I can't get a license. Oof...

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000001DqWxCAK&l=en-US

https://www.linkedin.com/feed/update/urn:li:activity:7212115164492353541/

We will miss you, mate.

 

Sorry if this is rambly I rarely have the opportunity to talk to other career LabVIEW developers. Thanks for your input!

Maybe someone misunderstandood and NI went to 'be bald'

Is it just me or today's webcast was desperately empty?

After roughly a decade away from LabVIEW thanks to changes in jobs, I'm hoping to maybe have an opportunity to get back into image acquisition automation with my new employer.  

I'm happy to see so many familiar names still hanging around here.  Now if I can only figure out how to get access again to my old account: https://lavag.org/profile/4344-gary-rubin/

Gary

I currently support/maintain LabVIEW / TestStand solutions created by Contract Manufacturers. These are being slowly replaced by ODMs developing their own test solutions.

Is there enough demand out in the world for someone like me to make it to retirement, or do I need to learn to test inside the world of Python / GRPC / Go?

I don't mind learning new things, but the sheer size and complexity of the systems I see are depressing. Everyone seems to have thier specific editor, build envoronment, source control, format checker and Jira implementation that creates Docker containers that need signing to install on the product to run. WTF? 

A senior software engineer who doesn't understand LV/TS asked me to document how to deploy my solution and dismissed it because It doesn't create WHLs or get tested with approved checkers like black or flake8.

Do I learn to work in their world, or follow in the footsteps of Cobol and Fortran programmers and ride LV/TS into the sunset?

No more comments in my LabVIEW code.

No icon customization.

All VIs named 'untitled<n>.vi'

On 1/30/2023 at 5:55 AM, ShaunR said:

We shall see. The "Fat Lady" hasn't sung yet and Emerson shareholders seem more than a little unhappy about the takeover. I'm still bullish on this failing despite Dr T's intervention.

The more I look at it, the more this seems like taking out the competition as opposed to diversifying and entering new markets. I think System Link was probably the trigger for this as it could, in the future, take Emersons offerings head-on and provide a far more superior top-to-bottom solution given NI's driver, LabVIEW and Test Stand support.

Well 2 years ago I saw a demo of System Link by a Ni salesman and that was a huge buggy disaster, absolutely giant failure.

I convinced my company to use WATS of Virinco instead : best choice ever.

https://eu.statesman.com/story/business/technology/2023/01/13/austin-national-instruments-exploring-possible-sale-technology-sector/69807646007/

https://www.reuters.com/markets/deals/ni-explore-options-including-sale-amid-interest-emerson-electric-sources-2023-01-13/

What design feature in LabVIEW most annoys you? The one that you constantly bang your head against, and wish that it had been developed differently, but it's probably too late to do anything about?

In the code I write, it would have to be the separate Image datatype. Why could it not just be an array? Sure, there are benefits to having a separate type - some very fast image processing code, and handling of image borders. But it is so restrictive if what I want to do is not already coded as an IMAQ routine, for example, taking the square root as part of computing the standard deviation of an image region, or wanting to use 3D images. Either I ignore all the really useful image routines, or I use twice the memory and keep swapping back and forth.

OK, your turn.

For a company conference I'm arranging a LabVIEW quiz like the TV-show Family Feud and I would very much appreciate your help to gather response material.

If you haven't seen the show, this is how it works in short:

Before the show, 100 people are asked a bunch of questions, like "Name a fruit"
The 100 people might then have answered:
Apple: 43
Orange: 22
Pineapple: 21
Banana: 14

On the show the team then have to guess what people answered. If they guess "Apple", they get 43 points etc.

I'm now looking for 100 people (or as many as I can find ) and have made a Google forms with 12 questions. The idea is not to think long and hard about the answers but write the first thing you think of and it might take about 3-5 minutes to answer all of them. If you would take some time to answer the questions I would very much appreciate it!

https://forms.gle/QAnjTETdGGoXkyA79

If anyone is interested I can share the results later on.

Thank you in advance!

Maybe you didn’t know that? Jeff still slings code, from big features to small bugs. He’s been a developer most of the years, happy to have others manage the release and delivery of his software. 
 

I spent over two decades working at his side. He taught me to look for what customers needed that they weren’t asking for, to understand what problems they didn’t talk about because they thought the problems were unsolvable. And he built a team culture that made us all collaborators instead of competitors. 
 

Thank you, Jeff, for decades of brilliant ideas and staying the course to see those develop into reality. Your work will continue on as one of the key tools on humanity’s expansion to Mars. 

This news went public with customers at NI Connect this week. I figured I should post to the wider LabVIEW community here on LAVA. 

I want to thank you all for being amazing customers and letting me participate vicariously in so many cool engineering projects over the years. I'm still going to be a part of the LabVIEW community, but I'm not going to be making quite such an impact on G users going forward... until the day that they start needing developers on Mars -- remote desktop with a multi-minute delay between mouse clicks is such a pain! 🙂 

But this reminded me of a presentation I saw a couple years ago about how PowerPoint has lots of unused powerful features.

It is an hour long, so maybe skip out on some in the middle.  But experimenting with the morph features, 3D models, fractals, context aware designs, and using it for full screen programs are some of the topics.  I especially love the library of 3D models.

I spent 20 years building this G language of ours. It’s time for me to go enjoy the fruits of that labor as a user!

I will still be employed by NI, but I will be working full time for Blue Origin. As part of the NI “Engineer in Residence” program, I will be on loan to Blue Origin to revise their engine and support test systems. They wanted a Certified LabVIEW Architect with deep knowledge of LVOOP, multiple years of experience with Actor Framework, and deep knowledge of cRIO and PXI. I asked, “Can we negotiate on that last part?” They said, “Yes, yes we can.” Turns out, based on the interview, I know more than I thought – apparently some hardware knowledge does rub off just by sitting near it for a couple decades. This new job runs for six months, but it is extensible through the end of 2021 at the discretion of myself and Blue Origin. When I come back, I do not know if I will be returning to LabVIEW.

Spaceflight has long been a passion of mine. Over my 20 years with LabVIEW R&D, I have had the chance to help out with various Mars rovers, large telescopes, and rocket launches. It has been awesome, and I’m proud of the language advances I brought to LabVIEW that helped so many users along the way. Now, I am going to focus on just one customer for a while... a customer with very large rocket engines!

My last day will be Friday, October 23. I will not have the same availability to respond to posts as I have in the past, but Aristos Queue will still be around on the forums.

“And, walking, I went beyond the fence.”
   -- ending of “R is for Rocket”

I am now in my 40s with youngish kids, so despite the fact that all I got for Christmas this year was a Pickle Rick cushion I am not actually complaining. However, I would like to get my order in to the Elves as early as possible. This is my wishlist, in no particular order. I expect this list will not be to everyone's taste, this is ok, this is just my opinion.

• Make LabVIEW free forever. The war is over, Python has won. If you want to be relevant in 5 to 10 years you need to embrace this. The community edition is a great start but is is probably not enough. Note: I accept it might be necessary to charge for FPGA stuff where I presume you license Xilinx tools. NI is and has always been a hardware company.
• Make all toolkits free. See the above point.
• Remove all third party licensing stuff. Nobody makes any money from this anyway. Encourage completely open sharing of code and lead by example.
• Take all the software engineering knowledge gained during the NXG experiment and start a deep refactor of the current gen IDE. Small changes here please though... we should not have to wait 10 years.
• Listen to the feedback of your most passionate users during this refactor. NXG failed because you ignored us and just assumed we would consume whatever was placed in front of us. I am talking about the people like those reading this post on Christmas day and their spare time because they are so deeply committed to LabVIEW
• My eyes are not what they used to be, so please bring in the NXG style vector graphic support so I can adjust the zoom of my block diagram and front panel to suit accordingly
• As part of the deep refactor, the run-time GUI needs to be modernised. We need proper support for resizable GUIs that react sensible to high DPI environments.
• Bring the best bits of NXG over to current gen. For example the dockable properties pane. (Sorry not much else comes to mind)
• Remove support for Linux and Mac and start to prune this cross compatibility from the codebase. I know this is going to get me flamed for eternity from 0.1 % of the users. (You pretty much made this decision for NXG already). Windows 10 is a great OS and has won the war here.
• Get rid of the 32-bit version and make RT 64-bit compatible. You are a decade overdue here.
• Add unicode support. I have only needed this a few times, but it is mandatory for a multicultural language in 2021 and going forward
• Port the Web Module to Current Gen. All the news I have heard is that the Web Module is going to become a standalone product. Please bring this into Current Gen. This has so much potential.
• Stop adding features for a few years. Spend the engineering effort polishing.
• Fix the random weirdness we get when deploying to RT
• Open source as many toolkits as you can.
• Move the Vision toolkit over to OpenCV and make it open source
• Sell your hardware a bit cheaper. We love your hardware and the integration with LabVIEW but when you are a big multiple more expensive than a competitor it is very hard to justify the cost.
• Allow people to source NI hardware through whatever channel makes most sense to them. Currently the rules on hardware purchasing across regions are ridiculous.
• Bring ni.com into the 21st century. The website is a dinosaur and makes me sad whenever I have to use it
• Re-engage with universities to inspire the next generation of young engineers and makers. This will be much easier if the price is zero
• Re-engage with the community of your most passionate supporters. Lately it has felt like there is a black hole when communicating with you
• Engineer ambitiously? What does this even mean? The people using your products are doing their best, please don't patronise us with this slogan.
• Take the hard work done in NXG and make VIs into a non-binary format human readable so that we can diff and merge with our choice of SCC tools
• Remove all hurdles to hand-editing of these files (no more pointless hashes for "protection" of .lvlibs and VIs etc)
• Openly publish the file formats to allow advanced users to make toolkits. We have some seriously skilled users here who already know how to edit the binary versions! Embrace this, it can only help you.
• Introduce some kind of virtualenv ala Python. i.e. allow libraries and toolkits to be installed on a per-project basis. (I think this is something JKI are investigating with their new Project Dragon thing)
• For the love of all that is holy do not integrate Git deeply into LabVIEW. Nobody wants to be locked into someone else's choice of SCC. (That said, I do think everyone should use Git anyway, this is another war that has been won).

That is about it for now.

All I want is for you guys to succeed so my career of nearly 20 years does not need to be flushed down the toilet like 2020.

Love you

Neil

(Edited: added a few more bullets)

Open the block diagram and see for yourself. (Make sure you have everything saved in case LabVIEW crashes.)

Do you know/have some nice GUI designs or examples?
In google search, awesome or clean equals cluttered. I guess tab control means unawesomeness...

I'd love to see nice stuff.

L.

See for yourself

Cool grey instead of boring beige.

Still waiting for a green chassis though.

Will NI be offering compatability stickers to allow older modules and cover plates to match the new graphic profile? Will they update older modules? Or will we have to live with mismatched colour combinations for the coming decades? 😜

(posting this in the lounge section instead of hardware for obvious reasons)

• Solidering hardware (Irons, solider, solider suckers)
• PSUs (20V, 4A, analog controls)
• Frequency generator (analog controls)
• Engine hoist (brand new)
• Laptops (newest one I got was a 10th gen I5)
• Cell phones (newest one I got was a Samsung S7)
• Rack mount routers
• Rack mount PCs
• PC components (fans, power supplies, cases)
• Old NI Hardware (USB hardware, old FPGA card)
• Monitors and TVs
• Cables (USB, Power, Monitor)
• Hard drives (often on the smaller side, largest was 1TB)
• GPUs (very old ones)
• Keyboards and mice
• Voltage adapters (as if I needed more)

That last one was fun.  We bought 10 USB serializes that had 8 RS-232 on each.  Well each of our 10 devices came with a voltage adapter for the US.  But it also came with 4 other voltage adapters for other countries hard mounted.  They all accepted 110-220VAC at 50/60hz but had the wrong plug for US.  So I took all 40 extra for other small projects.

I retired from the gov't (US Navy) around August of 2019.  Since the gov't is the gov't they didn't think about replacing me until after I retired.  So being a good little civil servant I came back part time as a contractor to fill the gap.  The basic requirements for my replacement were: 5+ years LV work, engineering degree, experience working with large data sets, experience working with large (2500+ vi) code sets, able to work independently (I have always been a team of 1).

The gov't finally hired my replacement and they started work in January of 2021.  It still being pandemic time, I didn't have a lot of face-to-face (or mask-to-mask) interaction with them, but I got more and more worried when I did.  While they had a lot of fundamentals down, there were glaring gaps in their technical knowledge.  They were more of a okay beginner programmer than the solid intermediate to expert level that we needed.  And they had obviously only ever worked in a team where everything was spoon-fed to them and then someone cleaned up after them.  They were let go.

This person had 6 years of programming LabVIEW on their resume.  But it was obviously 6 years of programming LV badly.

Going forward, how do I not repeat this mistake?  Should NI certification be required, and if so, is CLD good enough or should it be CLA?  Any other suggestions?  I really want to retire!!

Cat

tl;dr the ground based decoder for some of the comms on Voyager was built *after* the craft was launched, and it still to this day reliably receives data. Wow!

We are looking for presentations. Here are some details on what we are looking for

• Original content. We are not looking for recycled NI Week or CLA Summit Presentations (essentially never presented). If you have presented on this topic before explain to us how your new presentation is different. What new insights will you share?
• Promote learning over self-promotion. It is ok to mention your company and what you do or some cool product you’ve created, but it should not be the main focus. We are not interested in sales pitches.
• Are biased towards team-based development. We are interested in exploring team dynamics and the collaboration tools and processes used.
• Are grounded in real-world examples. Theories are great. Having a deep understanding of what you are doing can be very useful, but if you are going to do a presentation on theory, bring it down to earth. Give us some applications.
• Engage the audience. This is supposed to be a collaborative learning experience, not a lecture. If you’ve got ideas for roundtables or group discussions, those are certainly welcome.

Where to submit:

https://gdevconna.org/present/

https://www.nintendo.com/games/detail/game-builder-garage-switch/

🤨

Get your own snake.
Create an algorithm and realize it with LabVIEW.
Declare your abilities and compete with other opponents, get prizes!

The Olympiad will be online. Anybody from any country can join the competition. Official communication languages are English and Russian

A team size from 1 to 3 members and registration is available until deadline for solutions. Use the following topic to register:

The task will be published on April 12 2021 on the website labviewportal.org, and teams will have 2 weeks for experiments and create their solutions.

Competitions will be held in one stage. To determine the winners we will use a modified Swiss system (details will be in the Competition rules).

We tried to make the task more algorithmic, so we hope to see programmers from all areas among the participants.
So, welcome!

By agreement with the certification committee, this event is subject to the rule
************************
The following certification points may be awarded to existing Certified LabVIEW Developers and Certified LabVIEW Architects to be applied toward their recertification (by points).
5 points for participating in the coding challenge. To be eligible for these must complete the coding challenge but do not need to win or place for an award.
5 additional points if partisipants also place for an award in the challenge.
************************

Best regards from the organizing committee of the LabVIEW Portal 2021 Olympiad

What design feature in LabVIEW do you most appreciate? The one that when you use it, you think "this is just so easy". Or that you'd most miss if you had to program in another language.

For me, it would be the ease with which multiple cores/threads can be used, either with concurrent loops, or with the Parallel For Loop - having done some OpenMP and MPI programming (in Fortran of all things!), LabVIEW just makes this so much more straight-forward. Huge kudos to all who developed these features over the years.

OK, what about you?

I'm new to the forum and I'd like to show you my last creation as a presentation.

It is called Hackman, and it is a PacMan clone I've made while trying some OOP in Labview.

I have programmed chasing and moving methods as in the original arcade.

From the website http://hackyourpack.altervista.org/

you can download the executable... If anybody's interested I can provide source.

It is keeping track of the global high score.. so try it and put your name on it, so everybody will know your mastery!

Ciao!

Ubbi

http://blog.interfacevision.com/design/design-visual-progarmming-languages-snapshots/

I just wish I had time (and the brainpower!) to do a deep dive.

https://arstechnica.com/science/2021/01/the-curious-observers-guide-to-quantum-mechanics/

Howdy from Tulsa, OK 🤠

Long way to go but gotta start somewhere.Video is of the work I did several years ago before two babies arrived.

LabMelee 2017_11_11 21_59_15.mp4

Best regards
Tom

Apparently there is no option to support anything outside of the /Users folders

I've decided to connect a USB-C 3.2 drive to my Dell dock and use that as a local backup device.

Windows backup sucks. Anyone have a good suggestion for a reliable incremental backup utility?

So is LabVIEW just fading in popularity? Being relegated to some obscure language nobody cares about? Or have the cool kids gone somewhere else? Where do you go to discuss exciting LabVIEW topics, or even boring ones? I really want to know because I want to hang out there too!

LAVA served a purpose to connect people in an independent forum where none existed before. Does LAVA still need to exist in this age of hundreds of ni.com communitiues? Has LAVA's glory passed? Or is it simply that we need some restructuring to get interest back again?

Honest feedback welcome.

Really good value and a real chance of not being vapourware!

Has there been a better RPN compatible calculator since then?

That is all.

http://www.banggood.com/DSO068-DIY-Oscilloscope-Kit-With-Digital-Storage-Frequency-Meter-ATmega64-AVR-Microcontrol-p-981017.html

https://www.humblebundle.com/books/data-analysis-machine-learning-books?partner=gamefromscratch

• National Instruments Releases LabVIEW 7 Espresso (April 2004)
  

  

  
  

  
  

• New PXI Module Transfers Engineering Knowledge into Marketing Brains (April 2003)
  

  

  
  

  
  

• New eIeI/O Software Suite Introduces eFarming (April 2002)
  

  

  
  

  
  

• President Bush Nominates Jeff Kodosky to Cabinet Post (April 2001)
  

  

  
  

  
  

• New MXI Interface Kit for Palm Pilot IIIc (April 2000)
  

  

  

  
  

  
  

• Spousal Acquisition Toolkit Version 2.0 -- Now Featuring Undo! (April 1999)
  

  

  
  

  
  

• National Instruments Announces PC-Based Solution for Matrimonially Inept (April 1998)
  

  

  
  

  
  

I know you have them. Freebie T-shirts handed out by NI at various trade shows. Most of you wear them to sleep, or to hang aroung the house on weekends but I know you never even think of throwing them away right? Post pictures of the ones you have so we can try to fill-in the collection. I'm hoping someone has a LV2 T-shirt. Let's not just limit it to T-shirts. Why not thow in a few mugs and mouse pads...

Honestly, I had no idea that I'd dropped my post frequency down so low. What happened was that in May the forums that I monitor exploded with content. This is generally a good thing -- says the community is vibrant. But it meant that I went from having tens of posts in each forum to hundreds of posts, and the deluge overwhelmed me, and I started ignoring the backlog. That's just turned into a natural attrition. 

I'm going to try to get back to reading (and posting) the forums. I doubt I get back to the high rate of read that I had before -- I've got a lot more internal-to-NI stuff that I deal with on a daily basis these days -- but I intend to get back to posting at least every couple days instead of every couple months. 

And, just to be clear: no, I'm not dead. :-) 

I seem to remember several people on this forum talking about ISO8601 a while back, the more you get into it the deeper the problem goes!

I'd like to announce the launch of a new service that could be of interest to you.

Over at Launcher while building a rocket engine we built a software workflow that worked so well we decided to turn it into a service.

We call it CURVE. It’s a tool to visualize, share and manipulate DAQ data in the cloud. We make it easy to share your experiment results online, either privately with your team or for a public audience. We’ve just added support for National Instruments / LabVIEW TDMS files, so giving your experiment data a home online is as easy as drag & drop. 

We’re now looking for beta-testers, we’re offering a free year of usage after then end of the beta phase for our active early adopters.

Check it out! Feel free to shoot me an email if you have any questions: paul@getcurve.io.

Thanks for listening!
Paul
 

I have a DLL written in C++/CLI and have a property available to LabVIEW to access the native memory space, but from the property I can't use examples described in this link: https://forums.ni.com/t5/Developer-Center-Resources/Calling-C-C-DLLs-Containing-Simple-and-Complex-Datatypes-from/ta-p/3522649

Is it because the DLL must be written in pure C/C++ instead of C++/CLI (.NET) ? 

Thanks!

I try some of our usual debug approaches and don't find anything, so I hack up AppBuilder a bit so that when I get to the end of the build, I can open up the broken VIs and see what they look like. And I see this:

Where the heck have all the class methods gone? They're in memory at the start, missing at the end. That shouldn't happen! So I set up a trap to detect when the VIs go missing. I'm working in a debug build of LV with a lot of extra guards and logging turned on, so it takes about two hours to run this build. And I get nothing. So I rework my trap, thinking I've coded something wrong. Four times I do this over the course of yesterday, working on other issues while the build runs. Four times -- roughly 8 hours -- nothing. The VIs swear they're all in memory and the caller should know about them. 

This morning I come in and, for some reason, I happen to double-click on one of those ? nodes. And, lo, the missing VI opens. Say what? Turns out, AppBuilder had stripped all the VI icons out (saves space in the built EXE to ditch all those unneeded images), so they all render as the ? icon.

I have no idea what's actually broken, but it ain't that all the class methods have gone away. One wasted day. *head bang*  *head bang*  *head bang*

Yet another reminder -- as if I needed it -- that computers only do what we tell them to do. And they do it very precisely.

https://quickdroppodcast.wordpress.com

https://hackaday.com/2018/08/29/faded-beauty-dmm-gets-an-oled-makeover/

It makes me want to try to find some scrap hardware on ebay and see if I can repair it.  Of course I don't really need another random piece of half broken equipment in my office.

Thanks, I consider all of you as friends and one of the reasons I love LabVIEW.

Please click here to fill out the application to present.

Deadline for submissions: May 31, 2018

Presentation Options

We are making a few changes to the overall 2018 format in response to community feedback, but the three types of presentations remain the same as for 2017. We hope we can accommodate the kind of presentation you are comfortable presenting!

1. Large Audience, 50 minutes: You will present once to the entire conference, expected to be ~250 CLAs. These are good for lecture-style presentations with big graphics.
2. Small Audience, 50 minutes: You will present at most twice on the same day (only once if we have enough submissions). You will be addressing 2 different small audiences of ~50 CLAs. These are good for demo-oriented presentations with more of a Q&A style.
3. Large Audience, 7 minutes: You will present once to the entire conference as part of a 7x7 rapid-fire topic presentation. Have your presentation rehearsed exactly as the 7 minutes is a hard cutoff! We will have a 7x7 on each of Wednesday and Thursday, and we prefer that the presentations be on that day’s theme.

Themes

There will be two themes for the 2018 Americas CLA Summit, one on each of the two main days.

Wednesday: Solutions to Complicated Programming Problems

In this theme, we want to hear about solutions to the most difficult problems you have encountered while developing applications, specifically with the actual code design.  We are looking for topics that present the context of the problem and discuss the solution that you came up with.

Some sample titles to inspire you:

• “How we got data from point A to point B in record time”
• “A common algorithm you might not recognize because we’ve optimized it so much”
• “Even our plug-ins had to have plug-ins”
• “The most insane customer requirement ever and the code that satisfied it”

Thursday: Learning To Build Tools and Toolchains

In this theme, we are looking for topics covering software tools you have written or workflows you have adopted to simplify your development process. Whereas past CLA Summits have asked for tools in a specific arena for people to use, here we want to focus on how tools get built. Specifically, we’d like you to discuss how those tools work on their insides. The focus on how to build tools is as important this year as what any particular tool does. Be prepared to explore design decisions and to discuss the pros and cons of the decisions you made when creating the tool. Ideally, we want either tools that are open for the community to help extend or instructions on how people can build their own to cover their own unique situations.

Some sample titles to inspire you:

• “Custom VI Analyzer tools”
• “Get your CI Toolchain Up and Running in Under an Hour”
• “The MEAN stack and LabVIEW”
• “A tool for managing PPLs”

Please click here to fill out the application to present.

— The 2018 Organizers
(Jon McBee, Stephen Loftus-Mercer, Jeremy Marquis)

I don't know if you have seen/heard about the GDevCon @Steve Watts and his chums (as he calls them) are organizing. 

It is GDevCon#1, some of the things I think our LAVA friends will love are:

• It is independent from NI, created and driven by the community
• Two day conference
• Focused on real problems encountered everyday by LabVIEW developers
• Open to everyone (you don't need to have any certification like CLAD, CLD, CLA, etc).

The conference will take place in September 2018 somewhere in the UK.

If you want to learn more, register at: https://www.gdevcon.com/ 

Regards,

Fab

There's a new LabVIEW stack exchange proposal started on stack exchange (surprisingly enough!).

Just thought I'd post here in case anyone is interested in joining.

https://area51.stackexchange.com/proposals/114168/labview-and-ni-applications

Ciao,

Seán

• 3 open
• 1 RMA
• 3 CARs
• 12 created in the last 12 months

Thanks NI for giving me a resource to help me through the tough spots. I'm never leaving SSP if I can avoid it.

Thanks everyone else for all the CARs you generate before I have to generate my own reproduce case.

My name is Nick Brown, and I wanted to reach out to you as soon as possible. I am with Triple Crown Consulting, and we are a staffing agency that specializes in placing senior level hardware/software engineers into a variety of different contract positions. I would love to connect with those of you that are looking for work and would like to be a possible resource for you either now or in the near future. If you are interested, or if you know anyone that might be on the job market looking for work, feel free to call me at any time. I hope to hear from you soon!

Thank You,

Nick Brown

Technical Recruiter | Triple Crown Consulting

1999 S. Bascom Ave, Suite 500

Campbell, CA 95008

P: 408-680-2564 | F: 408-608-0398

nick@tripleco.com| linkedin.com/in/nick-brown-238460aa

tripleco.com

All kidding aside, I am just now poking around to see what is there, and there are definitely some things to be thankful for.  Other things...not so much.  Extremely radical changes to the graphics on the palettes and root functions, along with major palette restructuring.  Looks like navigation by sight will have to be learned all over again.

I will post more thoughts on this thread when I get the chance.  Oh, and manual tool selection is gone, along with the tools palette, if I am not mistaken.

What's the longest project you've worked on or projects where you hit burnout way before the end.  How did you keep up motivation and keep slogging through it to completion?

Might be interesting to hear peoples thoughts on getting through those long projects or the last few weeks/months of a project when things seem to take forever.

Cheers,

Tim

One company I worked with had locked down the work laptops to where you couldn't really do anything other then answer emails and write Word documents.  So when we needed to install LabVIEW which required administrator privileges, there was a whole approval process to get the IDE and some of the DAQ drivers installed.  This included several levels of approvals, and justification for why you wanted to be an admin.  You would apply to have administrator privileges given to you but you only had a 2 hour time slot, and after that the credentials you were given wouldn't work, and you had to apply again.  Of course the first thing we would do in that 2 hours, is use the administrator account we were given to promote our user as a local administrator, so we never had to apply for it again.  This company also had an app store for PC software.  To me the concept of having a PC app store seemed odd.  I sorta consider the whole internet the app store, and the concept that an offline app store can be up to date with all of the internet, with the newest software seemed silly.

So tell us about yourself.  How often do you use LabVIEW?  What is your technical background?  What is your favorite project you've done with LabVIEW?  Ever been to NI Week or the LAVA BBQ?  And if nothing else have you heard about LabVIEW NXG?  NI has been teasing a new IDE for LabVIEW for a few years and 1.0 is finally out, what are your initial impressions?  Also feel free to also post in the recent thread about NXG.

I just did a search and over 30,000 users have 0 or 1 posts on LAVA.

A warm hello from beyond the veil of the corporate firewall. He is still alive...

Clueless Cat

Cheers,

Certainly a big loss for NI or any company when one of the founders retires.  NI has certainly changed over the years and this is certainly going to be an inflection point when we look back a few years from now.  I'd like to think that the process and company structure in place will allow NI to grow after the end of this year.  From my interactions with him, Davern does not seem like the 'typical' businessperson, and though not technical I am not sure you need a technical CEO. Was wondering on the forum's thoughts on this.

I have dusted off a PIC microcontroller that I have had lying around in my drawer for years, and am attempting to stop old-age brain rot my making it do stuff, but purposely limiting myself to assembler.

So far I have the (12-bit) ADC working, and sending the upper 8 bits back to the PC over RS-232 as an ASCII character.

Now all I want to do is display the analogue voltage on the PC. Should be simple. I am using the 5V supply as the reference, so a 12-bit ADC has a step size of 1.22 mV. Conversion from 12-bit hex value to human readable value should be reasonably straightforward: scale the ADC value by 1.22 mV, convert to say 5 digit BCD and chuck out over the serial port one character at a time. I figure the first step is to implement a fixed point multiplication, keeping things simple I can have the ADC reading as <+,16,0> and the scaling factor as <+16, 3>.

 This is the bit that is making my brain hurt... I have done some reasearch and it turns out that fixed point multiplication does not really care about the format of the number, only the bit-width. So you can use exactly the same algorithm to scale <+16,0> and <+16,3>. Anybody know if this is correct?

Now, I know I can take all sorts of shortcuts to get the ADC value in human readable format, I have decided for the purpose of the exercise I really want to figure this out using fixed point maths (I have no actual application in mind other than curiosity).

I thought I would pass this across the community to get a pulse on if y'all think this is a well balanced list and no massive misses on my part.

I know that we have a great document at LAVA Forum Guidelines https://docs.google.com/document/d/1Ce1aE4Kz6h1W5vdQER8LIc_9ZvW8QhHLQoqoVjcWw10/edit
But we all have our little peeves, and this might be a fun airing of the grievances.

It's for a 7 minute presentation, so the idea is 30 seconds each on average.
The idea is to hit things for people who are newbs and veterans.

DON"T

1. Abuse the Private Message (PM) Feature
2. Admonish a newb publicly
3. Turn a commuinty forum post into a 2 person flame war
4. Presume that people have knowledge of what hardware your using and how it's API / Interface works
5. Be a 1 hit wonder
6. Post Across multiple forum sub-forums
7. Be a clueless homework hustler; we know what you're doing, do it the right way

DO

1. Search the best you can with site:lavag.org {your search}
2. Remember what it was like when you were young and clueless
3. Be apprecaitive
4. Give ample detail in the form of: high level diagrams, videos, pictures, code and big picture purpose
5. Share novel things that you figure out
6. Start out saving for previous and make everyone's lives easier
7. Be an active participant and share the love!

In the end it might be a flop, but I hope it encourages those CLA in India to kick things up a notch.
Your short term feedback will be appreciated and rolled right in.

~,~
The Captain Was Here

/EDIT :: Presentation Added Make Friends, Not Flames.pptx