All Activity

I managed to post the issue there, but it's very cumbersome because I only get one post per password reset (and their Contact Us link is broken). I did get a reply and was able to solve that problem, but now it throws error 1357. Maybe it's time to throw in the towel on VIPM.

Nice! Thank you.

thanks @hooovahh its help me a lot I am very thankful.

Gee, I put all my ideas into Y Controls. Attached is my help file (still under construction) for Y Controls. Y Controls.chm

I just added an explanation of how to add to the New dialog on the LabVIEW Wiki: https://labviewwiki.org/wiki/New_dialog If you have any ideas to help me make QControls better, let me know. I have a thread on the QControl Enthusiasts page: https://forums.ni.com/t5/QControl-Enthusiasts/QControl-Usability-Improvements/td-p/4101397?profile.language=en

I've been developing it alone, but I'll take any help I can get.

Calling a function or use of a datatype from <opencv2/opencv.hpp> result in a name mangling or undefined variable issues.

I'm using labview on Linux, which does not support dotnet. So EmguCv is not an option. I thought about only using the C API in opencv to avoid name mangling and undefined variables issues, but the later version of opencv doesn't support C API. i'm now stuck at figuring out how to call the c++ function in a c calling conventtion. example code: #include <stdio.h> #include <opencv2/opencv.hpp> using namespace cv; using namespace std; extern "C"{ int displayimage() { Mat image(400,400, CV_8UC3, Scalar(0,0,255)); image = imre

This looks interesting, I've created a QControl and really enjoyed the concept, haven't dug too much into Y controls but it looks interesting, are you developing this alone or as an open source project? I get the same error when building the VIP, you should post here I think : https://forums.jki.net/forum/5-vi-package-manager-vipm/ to get some support, JKI is usually quite responsive.

Sometimes I get this (which makes no sense because that VI is not a dependency of Y Controls, and it is not missing)

Hello I'm starting a project using LabVIEW +LINX Toolkit but I have a problem with my RPI. For example when I upload solution I have this error. I can't solve it

Better check your sense of humour detector, I think it might be faulty.

Just be really careful if you intend to used packed libraries. Start building the exe & ppls now. It is not trivial. It's of limited use if it can't be deployed. This is the best documentation I've found yet. Effectively_Using_Packed_Project_Libraries_SEPAD.pdf ‏2772 KB https://forums.ni.com/t5/NIWeek-Session-Content/Software-Engineering-Processes-Architecture-and-Design-nbsp/ta-p/3929895?profile.language=en

I have invented Y Controls and I am trying to create a VI Package for installing them. I would like it to result in "Y Control" being an option when selecting File -> New from the LabVIEW menu. But my .vipb file doesn't seem to do anything; no output, no errors, just a big NOP. Any help would be appreciated. Y Controls.zip

You have obviously never done Agile Development proper then since it is an iterative process which starts with the design step just after requirements acquisition. It's not a fear of failure, it is a fast-track route to failure which usually ends up with the software growing like a furry mold. But anyway. It's your baby. You know best. Good luck :)

I believe this now referred to as "Agile" 😉 But in all seriousness, not attempting something for fear of failure is not something I have ever really worried about. Also, it is pretty much impossible to fail on 100% hobby/pet-project/learning experience.

What Neil said. Looks like you've got it worked out. The hardest thing to get your head around is the factory instrument creation. This is the only place where you might not use dynamic dispatch to call instrument specific vis containing their specific configuration. But as @drjdpowell said, you can use JSON for that.

Uhuh. Seat-of-your pants design; the fastest way to project failure.

We modify code while LV is running all the time 🙂 We even have a Quick Drop shortcut that toggles a Sub-VI's Loading Option between "Load with callers" and "Reload for each call".

According to NI, it is possible to resale the licence. Do you have any suggestions where to look for it? Best regards Tom

I think what Thomas meant is that if you are going to use Dynamic Dispatch (DD) then you are forced to have the same data type as the connector pane of the concrete DD VIs all have to be identical. If you already have something working its probably ok. As an example you cannot have Instrument 1 return an array of DBL and Instrument 2 return an array of SGL for a "Read.vi".

Hey Rob (UncleFungus🤣🤣) I actually moved away from that library in the end as I have my own actor style so wanted something more low level. I now cannot find my old code that was working with this library. I now use the MQTT library from daq.io as it gives me the low level access I need. Looking at your screenshot though I think I remember. Just at the bottom you have the cluster with User Name. I am pretty sure the private key string (as copied directly out of Azure) goes there or in one of the elements of that cluster. Now, in my production system I have moved away from this t

Hi Neil. Long time no see. I am trying to do something similar to what you have done above - I have my Azure hub set up and can talk to it via my Beaglebone ok (trying to open the door of my Chicken Coop). What I'm not getting is where the Primary Key/Connection String gets inserted using the MQTT (Cowen71). I seem to connect to the hub ok, just not the device. Can you offer any assistance? Thanks, Rob (FIF1)

@MikaelH Thanks for the links good sir, I appreciate it! @ThomasGutzler What do you mean by "Returning different data types from classes of the same instrument type is something you don't want."? I'm assuming you mean something like use the parent "Power Supply" object for my connector panes and define the child (such as TDK Lambda) during the initialization section of my test. This way the if I wanted to change the PS from TDK Lambda to say Sorenson, all I'd have to do is change the test's initialization section since all my connector panes are using the Power Supply parent clas

This is the standard way to do service discovery. My "Dispatcher" implementation had a "broker" that ran on the local machine to act as a gateway to services that registered with it on that machine. External (or local) clients would then contact it to discover services and it would hand off comms to the service for direct communication. It behaved as a router rather than the usual broker and meant it didn't become a bottleneck for high speed transfers. Your framework would be a good match for the above implementation since it already has all the publish, subscribe and routing feature