Antoine Chalons

Do you do that? In 15 years I only met one LabVIEW Dev who was in a job where management organised pair programming. I'd like to hear feedback from people who do that 🧐

Is NI sharing public information to support this statement? LAVA might not be a good indicator of LV's user base mood, but I find it hard to be confident/positive about LabVIEW's future - and I'm trying hard because I do love LabVIEW.

I think it’s a pattern at NI, only scratching the surface. lots of products or support for standards are superficial. They exhort us to engineer ambitiously because they don’t.

For that kind of Ui elements property management I use the QControls toolkit (homepage, download link) I've never really looked at the property browser, so I'm not sure if it could help.

Maybe you can still find the openg commander on sourceforge No idea if it supports Linux but I believe it's open source

Yep, I remember when Tim Dehne left NI, rumor I heard at the time was he wanted to become CEO and understood he would never make it, then left. Indeed it took a long time for Dr T to retire. But hey, pretty sure the rumor was not the full story, so many VPs were competing for that.

If I remember well, windows 10 iot was the default option with the industrial computer from Advantech, at least that's what the reseller told me. We ordered one to try (with a return option if it didn't work), we tested for a few days, we were happy. We were only interested in in having something that worked like windows 10, came pre-installed and didn't have all the media/game nonsense that comes on "normal" computers.

Maybe for xmas

I'm pretty sure I read somewhere that he started from the erdosmiller TOML library Edit : I knew :

A CAR already existed : 1103060 R&D is planning to fix it in LV 2022. Recommended work-around is a mass compile after installing any new version / patch.

On Windows 10, I had LV 2020 SP1 32-bit working fine I installed the f1 patch using NIPM Then this : I noticed because these VIs are use by the File Checksum VI It's not too difficult to fix, see this video I made :

Yeah... bit cryptic this comment, please elaborate.

I'm quite sure the answer is yes. Are you having issues with this?

Indeed, Advantech offers Win 10 IoT Enterprise. If you take a look at this product : https://advdownload.advantech.com/productfile/PIS/AIMB-587/file/AIMB-587_DS(082721)20210827160444.pdf This is the equivalent up-to-date version of what I was using, it does mention Win 10 IoT Ent (not sure about the difference HL and VL though.

Never had any issue with LabVIEW on windows 10 iot I changed job 3 years ago, I don't do vision anymore, that's why I said I used to use Advantech, I never had problems with IPC-720.

Well "good option" is a bit broad... it was great for my application There production line was producing 60 part par minute There were 3 C-Link camera, therefore 2 PCIe-1430 frmaegrabbers Each cam was acquiring 10 images of each part The time available for image acquisition + processing was ~800ms so the acquisition was done in parallel to the processing for each camera. At the time (3 years ago almost) we were getting the most powerfull IPC-720 available with 32Gb of RAM and Windows 10 IOT. The application did not require fanless or RT and it was working 24/7. We also had similar application with GigE cameras but I never liked GigE.

Indeed the IC line of product was supposed to stand between the cRIO and PXI in term of perf - without offering the modularity that cRIO and PXI offer of course, but for Vision application it was ok with usb3 and GigE. But even then, the perf was disappointing for heavy vision application. I use to use Advantech IPC range, updated every 6 month with new CPUs etc. Supporting 3rd party hardware with NI Linux RT would probably require a huge effort for NI, not sure they're ready for that. And where NI is disappointing me a bit more is by not telling us what their plan is for Hardware between cRIO and PXI, at least if they were to say they are only going to maintain cRIO and PXI in the future at least we'd stop hopping a find a different solution.

I understand your concern, NI's commitment to industrial vision has always been a bit loose I think. RT vision controllers come and go a bit fast. And there was the fiasco of the EVS, whose long term replacement was the IC-31xx, but when was the last update of that line? Many years ago and there's no communication around the future of this product. My advice is to find a different hardware supplier for "vision industrial computer" and use Windows 10 iot, otherwise NI will soon tell you to use a PXI! At some point NI was considering allowing to install NI Linux RT on non NI hardware, but I seriously doubt they'll ever to that, it would be in huge contradiction with their business model.

My first idea would be to use the 2D picture control for this. Go to "Help > Find example..." this will launch rhe example finder, then browse to "Build User Interfaces >> Generating 2D Pictures" and take a look at the examples I think this one is cool

I do too... choice was not mine. We got mixed feelings from the customers but the "product owner" loved it.

If any change was made while on the config panel, a "revert changes" button would show-up. I admit it might not be obvious for everyone - of course what is important is : habit / expectation of the actual targeted users.

Also these custom graphs, 100% 2D picture control. The lad who did that is a ninja!

I use to work at qmt (Qualimatest), a lot of effort was spent on UI/UX

Similarly, a few years ago, I was requested to add 2 buttons, "apply" & "cancel" before leaving a config panel. I tried to argue that they were useless because authentication was required to access the config panel, and user who got there knew what they're doing when changing a value ; if they change and close, why would the app not keep and apply the changed settings? It turned out users felt safer or rather "more in control" with explicit apply/cancel buttons. Meh.

The lvanlys will return an error code if there is a NaN in the array, this extra feature probably explains a part of the difference in exec time.