All Activity

Guess who made online shopping easier? Yours truly and the only shopping friend; Clipper Extension. Just download and enjoy the magical process of coupon and money-saving promo code application. In addition, have access to effortless shopping effortless and hassle-free online shopping. Best Online Shopping And best deals online and Clipper Coupons and Clipper and How to use Clipper Extension | Clipper Coins | Visit Here :- How To Get Healthy On A Budget and Which Color Teddy Bear Is Best | Which Online Site Is Best For Shopping Clothes and How To Get Healthy On A Budget and Which Color Teddy Bear Is Best and Which Is The Best Online Shopping Site For Cleaning Products and Which Is The Best Online Shopping Site For Buying Laptops Visit Here :- Which Is The Best Online Shopping Site For Cleaning Products

Well I never have submitted anything to vipm.io and Github for such libraries feels more like a FINO (first in never out) than anything else. 🙂 May have to check the vipm.io submission procedure. After hacking above version I did look into it more and am considering to improve it to support some more operators and make it more C like in operator syntax (but no variable type support nor arrays or pointers). The main difference would be that the current exponent operator "^" would change to be the EXOR operator instead and for exponent one would need to call the according function.

My guess is that the library name in the CLN itself should be slightly faster if they would implement it the way I would. For a passed in library name they do need to verify that the library name hasn't changed compared to the previous execution so there is some overhead to compare the new name with the old one. It shouldn't even be in the uSec range however as comparing paths is mainly just a MemCompare for most of it, although in a loop for each path element itself. if the paths are the same, it doesn't need to do anything more. If there is no path wired in, that check can be entirely skipped and LabVIEW nodes certainly have the option to check for that as it is an attribute of the node if it has the path input enabled. As to calculating the path dynamically: You do want to cache the path in a Feedback node and only calculate it on first call. Recalculating it each and every time should be only necessary with very strange external DLLs, but not for platform and bitness differences only.

Do you have any plans to put this up on Github and/or vipm.io?

Thanks Rolf Kalbermatter! I worked well after changing another usb port.

Try another USB port or a powered hub. It seems that something in the USB communication is getting messed up somehow. There are many possible reasons aside from actual firmware bugs in the Keysight device. - your USB bridge in the computer is messed up, faulty or has bad drivers - the USB port you have your device connected to is a low power USB connector and the Keysight likes to draw more power than your computer can provide. Many USB ports perform not as they should according to the specs (and so do devices, sometimes drawing high transient power surges that are not allowed according to the USB specs). - The device might have a firmware bug, try to find if Keysight has a newer firmware available and upgrade your device if that is possible. NI-VISA is one of the few software drivers that never was critical in having to match the LabVIEW version closely. I would be very surprised if that has anything to do with your problem.

Basically you should attempt to use each class that you wan't to use from another class NOT in the same PPL into its own PPL. Then relink the source code of each class lib to reference to the PPL version of the class. And be VERY, VERY strict about that. If you call VIs that are not already part of an existing PPL (or don't enable the Exclude dependent library/typedef etc build option), the PPL build will include those VIs in the PPL itself and that will be a completely different VI and class in terms of name space, since myGreatLib.lvlib:myGreaterClass.lvclass is NOT the same as myGreatLib.lvlibp:myGreaterClass.lvclass as far as LabVIEW is concerned. The library name gets part of the fully qualified class name and that p at the end of lvlibp is enough to make both classes completely different implementations.

Hello, I am using Keysight MSOX3054A with LabVIEW 2020 via USB communication. It works fine when I grap a single moment of waveform however, It always encountered an Error 1073807298: Could Not Perform Operation Because of I/O Error if I try to acquire a waveform continuously with "Agilent 2000 3000 X-Series Acquire Waveform Continuously.vi". I matched LabVIEW 2020 and NI-VISA 20.0 for compatibility. Has anyone an idea for this issue? Thank you for your help!

Could you help to share your latest labview driver of CL-500A? thank you very much

You're library is great. I like your implementation. Thanks for sharing with us.😃

That was specifically during debugging to see what I could pack and unpack through the variant. The only one that worked was the U32 if I stripped it out when it was accessible. That portion I left to show things I had already attempted to get to pass through.

Sometimes some weird locking of classes/libraries can occur if you dont perfectly close all opened resources. Totally off-topic, why do you have a reference to the class and also the class object itself? I see you don't actually do anything with this cluster so it could be throw-away code, was just curious about your use case.

Hmm. it would not let me move the class into the project library yesterday, but it will allow it now. <shrug> At any rate I do currently have it working by wrapping the functions and putting them in a library. Hopefully that means that if the PQ library gets updated, I may just need to repack the wrapped library.

You cannot directly create PPLs from classes. Instead, put the class inside a project library to create a PPL.

Again, I've never used PPLs, but that seems wrong. Why can't you put a class in a library/PPL?

Ahhh I misunderstood you. I thought you were referring to my own library that I had attached. But you are referring to the muParser library however. Can't help you with that one as I don't know the details of the actual muParser library that implements the logic in the background.

This is apparently easier said than done. It seems that you can not just insert a class into a library. I'll probably have to wrap each of the class functions in a higher vi and see if I can get that to work.

I definitely can echo what @JKSHsaid. Several years ago I implemented a data dashboard with WebVI tech (in NXG) and the overall experience was so painful I will never try it again.

I understand. However, i have tried to run a simple expression in one of the examples of the library containing the function "rand", but an error was raised. Here´s the image attached.

Ah ok - thanks for pointing this out. I tried something trivial with it a few years back, haven't been keeping up to date with it & had thought it would have gotten out of prototype stage by now.

As someone who used this for a large-ish project -- after 9 years as a full-time LabVIEW programmer at a Silver Alliance Partner -- I cannot recommend this route. Neither can others who replied to my post. Your future self will thank you.

Hmmm, that's interesting, I'll search out some of your other posts on UI's. That sounds like a better longer term approach. Yeah, I meant the WebVI's bit that has survived. But tbh will probably skip that and just do the html/js. Good to know, I'll keep this as a plan B. Thanks, Martin

You know NXG has been discontinued, right? Then Bitman is what you want. The native LabVIEW image tools can be very cumbersome but Vugies toolkit allows layering, advanced processing and filtering (if you want to try it) Then you are almost there by the sounds of it. As I have said in many other threads, I have dispensed with LabVIEW UI's completely in favour of HTML/Javascript. I use a proper web browser (not the LabVIEW UI or embedded browser widget) and use LabVIEW as a back-end linked with websockets.

Thanks all for the feedback! I think the consensus is to look for an HTML/Javascript toolkit. Is it a request we should implement? I've gone back & forth on this - as it seems like a nice to have feature. But we do get requests from major customers, they tell me it takes them a lot of time switching tools when using an external image editor. Also most of our competitors have an embedded image editor, so I'd like to have it as an option. Functionality - the bit that I struggle with & I don't think LV is well suited for is building composite images (sorry that wasn't clear in my first post) - they want to import several images, then crop, resize and reposition them. Javascript editor in an embedded browser. Yeah that may be the way to go, we tried this about 18 months ago, and struggled when using IE within the WebBrowser - as most JS toolkits are geared up for a modern chromium browser, they don't work well with IE. I do actually have a prototype that uses Edge within the WebBrowser now - so maybe it's time to revisit that. Is it NXG? No, it's a hybrid monster! LV15 mixed with the embedded WebBrowser displaying html & js for parts of the UI we can't do in pure LV. It started in pure LV with a more basic UI, then has grown & grown. It's getting refactored & split into multiple projects, I'm aiming to split of one of those smaller projects into NXG.

I have never used PPLs, but my understanding is that you would first need to put the PQ library in its own PPL, and have all other code call that PPL. It looks like you have instead made independent copies of PQ in each PPL.